Database Develop

[Q] Bionic will not properly FXZ flash

I am having an issue trying to FXZ flash my friends Droid Bionic using RSD Lite. The flashing process keeps stalling at the point where the phone is supposed to reboot into recovery mode and flash the 2 radios. When it reboots I get the screen that show a droid laying on it's back with a red triangle with an exclaimation point in it above the open chest of the droid. After a few minutes the phone resets and then tries to boot normally and gets stuck at the last boot screen that has the transforming red droid logo. The screen showing the droid laying on its back also shows up when I try to boot into recovery mode manually, I am able to get past this screen by pressing both volume buttons and the recovery mode is then available. I have tried wiping data and cache before and after attemping to FXZ flash. I am at a loss at this point it seems to me there is something wrong with the stock recovery mode since the droid on his back is showing up instead of the droid standing next to the yellow triangle with the exclaimation point. Any help with this issue would be greatly appreciated.
To clarifiy I am using RSD lite 5.7 and the 6.7.246 FXZ flash file (downloaded copies from multiple sites). I have attempted to flash on 2 different computers that have successfully flashed other motorola model phone in the past using RSD lite. The Bionic has never been rooted and just randomly got stuck in a boot loop the other day.

I had the same problem. I had the update .zip file on my sdcard and I went into recovery mode after one of the failed reboots and took a chance on installing it that way. It worked for me.

examan said:
I am having an issue trying to FXZ flash my friends Droid Bionic using RSD Lite. The flashing process keeps stalling at the point where the phone is supposed to reboot into recovery mode and flash the 2 radios. When it reboots I get the screen that show a droid laying on it's back with a red triangle with an exclaimation point in it above the open chest of the droid. After a few minutes the phone resets and then tries to boot normally and gets stuck at the last boot screen that has the transforming red droid logo. The screen showing the droid laying on its back also shows up when I try to boot into recovery mode manually, I am able to get past this screen by pressing both volume buttons and the recovery mode is then available. I have tried wiping data and cache before and after attemping to FXZ flash. I am at a loss at this point it seems to me there is something wrong with the stock recovery mode since the droid on his back is showing up instead of the droid standing next to the yellow triangle with the exclaimation point. Any help with this issue would be greatly appreciated.
To clarifiy I am using RSD lite 5.7 and the 6.7.246 FXZ flash file (downloaded copies from multiple sites). I have attempted to flash on 2 different computers that have successfully flashed other motorola model phone in the past using RSD lite. The Bionic has never been rooted and just randomly got stuck in a boot loop the other day.
Click to expand...
Click to collapse
SamuriHL's House of BIONIC should be able t fix your broken recovery for you.
Sent from my ASUS Transformer Infinity TF700 running Android JB (rooted) via Tapatalk

Just to clarify my post, I used HOB when I had the same issue. If you try it, I would also suggest having the .246 zip file on the sd card and try installing it from recovery if you get stuck again. I'm certainly open to hearing other ideas from any of the experts out there.

But the OP cannot get into recovery.....
Sent from my ASUS Transformer Infinity TF700 running Android JB (rooted) via Tapatalk

If you use the HoB I recommend trying fast boot mode instead of rsd mode.
Sent from my Xoom using Tapatalk HD

Thanks I'll give those ideas a try and let you know if i have any luck.
Sent from my DROID RAZR using Tapatalk

I keep getting thus logo when it attempts to install the radios.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This happened when i was using rsd before trying to use HoB and HoB yielded the same result. Any more ideas?
Sent from my DROID RAZR using Tapatalk

There's a radio fix in the HoB you may try. Check the utility menu. Once you do that, then try the 246 FXZ again.

I tried the radio fix in the utilities but got the same result, the little dead Droid screen then the phone reboots after about 5 minutes of inactivity.
Sent from my DROID RAZR using Tapatalk

Then I would say you have physical problems with the phone.

That's what I was beginning to think...thanks for the help.
Sent from my DROID RAZR using Tapatalk

johnlgalt said:
But the OP cannot get into recovery.....
Sent from my ASUS Transformer Infinity TF700 running Android JB (rooted) via Tapatalk
Click to expand...
Click to collapse
examan said:
The screen showing the droid laying on its back also shows up when I try to boot into recovery mode manually, I am able to get past this screen by pressing both volume buttons and the recovery mode is then available.
Click to expand...
Click to collapse
I took this to mean he can get into recovery and this was exactly my situation as well. This was the point I got it to install from the sd card. Maybe I just got lucky this time. Hopefully not a sign I'm going to be screwed next attempt.
Samuri, thanks for the tip on using fast boot mode instead, I'm probably going to need that advice.

examan said:
I tried the radio fix in the utilities but got the same result, the little dead Droid screen then the phone reboots after about 5 minutes of inactivity.
Sent from my DROID RAZR using Tapatalk
Click to expand...
Click to collapse
Hmmm. I wonder if it tried to flash the radio during the ICS update and got FUBARd in the process? Either that, or the radio hardware is kaput.
I know your friend said it was not rooted but was it already upgraded to ICS? Did he, per chance, try to take the RAZR JB leak?
Sent from my ASUS Transformer Infinity TF700 running Android JB (rooted) via Tapatalk HD

He said it installed the Ota update just fine then a few weeks later it just stopped working. I think it's most likely a hardware issue.
Sent from my DROID RAZR using Tapatalk

sounds like it, if it was already working on ICS before.
Sent from my ASUS Transformer Infinity TF700 running Android JB (rooted) via Tapatalk HD

[Q] Help needed kindle fire HD (TATE) not booting

Hi everybody
I've been running a rooted kindle fire hd for about a year with cyanogenmod and no problems. Tonight I downloaded the latest nightly update installed it with TWRP and re booted fine.
I kept getting google play services errors so decided to factory reset and clean everything up. Now I cannot get past the teamwin boot logo.
I see the orange kindlefire, blue kindlefire, then the teamwin logo flashes every 5 seconds.
Any ideas on how to recover this?
Regards
KP

kpugh162 said:
Hi everybody
I've been running a rooted kindle fire hd for about a year with cyanogenmod and no problems. Tonight I downloaded the latest nightly update installed it with TWRP and re booted fine.
I kept getting google play services errors so decided to factory reset and clean everything up. Now I cannot get past the teamwin boot logo.
I see the orange kindlefire, blue kindlefire, then the teamwin logo flashes every 5 seconds.
Any ideas on how to recover this?
Regards
KP
Click to expand...
Click to collapse
i have the same problem and there seems to be no way to get the kindle in any state to do anything, all I've found out so far is that its stuck trying to factory reset and there should be a way to reverse this, i hope someone can give us a solution or i might as well call my kindle a paperweight.

laharl_chaos said:
i have the same problem and there seems to be no way to get the kindle in any state to do anything, all I've found out so far is that its stuck trying to factory reset and there should be a way to reverse this, i hope someone can give us a solution or i might as well call my kindle a paperweight.
Click to expand...
Click to collapse
Thanks for letting me know, I purchased a factory cable today. Seems to be recognised by my laptop, but the kindle doesnt go into fastboot. There seems to be a few people with this problem. I've not seen any help offered yet. I'm not holding out much hope, doesn't seem any way to communicate with it.
Where did you get your info?

kpugh162 said:
Thanks for letting me know, I purchased a factory cable today. Seems to be recognised by my laptop, but the kindle doesnt go into fastboot. There seems to be a few people with this problem. I've not seen any help offered yet. I'm not holding out much hope, doesn't seem any way to communicate with it.
Where did you get your info?
Click to expand...
Click to collapse
i've found out a lot about bootloop issues and in most cases it seems like the first thing needed to fix the problem is a factory cable, i didn't get mine yet so i can't see if it will work but since your pc can see your kindle now you can try out kindle fire first aid 4.1.88-beta.
let me know if it works for you.

laharl_chaos said:
i've found out a lot about bootloop issues and in most cases it seems like the first thing needed to fix the problem is a factory cable, i didn't get mine yet so i can't see if it will work but since your pc can see your kindle now you can try out kindle fire first aid 4.1.88-beta.
let me know if it works for you.
Click to expand...
Click to collapse
I'd already tried that. Seems because the kindle is not fully booting up then kindle fire first aid doesnt recognise it. Unless what i've been sent is actually a normal usb, then I dont see any way of sorting this. I'll wait to see if you have better luck

kpugh162 said:
I'd already tried that. Seems because the kindle is not fully booting up then kindle fire first aid doesnt recognise it. Unless what i've been sent is actually a normal usb, then I dont see any way of sorting this. I'll wait to see if you have better luck
Click to expand...
Click to collapse
OK I may have cracked it here. I am no expert ( I wouldnt be in this mess if I was) i was playing with the adb commands with the factory cable connected.
Typed:
ADB devices
showed a device called D025A0A024540SF0 recovery
Typed:
ADB Reboot-Bootloader
Kindle fire boots into FASTBOOT screen. YEY ME!!!
Now i'm not really sure where to go, never used fastboot before.
After using kindlefire recovery tool, doing a wipe then option 2 my kindle booted up into TWRP.
I tried rebooting from here and now I get a flashing kindlefire logo.
occasionally i manage to get it into fastboot with the factory cable, but it doesnt stay there long enough to do anything. I hoping this is maybe a power issue so I'm leaving it plugged in overnight to attempt to charge it.
hope this info helps you, I feel like I was at a point to simply re flash a rom but messed up by rebooting from twrp.
I did it!!!!
Managed to get it to stay in fastboot mode and ran kindlerecover tool again. now have a working kindle running APEX launcher. Have to read up tomorrow and get cyanogenmod back.

kpugh162 said:
OK I may have cracked it here. I am no expert ( I wouldnt be in this mess if I was) i was playing with the adb commands with the factory cable connected.
Typed:
ADB devices
showed a device called D025A0A024540SF0 recovery
Typed:
ADB Reboot-Bootloader
Kindle fire boots into FASTBOOT screen. YEY ME!!!
Now i'm not really sure where to go, never used fastboot before.
After using kindlefire recovery tool, doing a wipe then option 2 my kindle booted up into TWRP.
I tried rebooting from here and now I get a flashing kindlefire logo.
occasionally i manage to get it into fastboot with the factory cable, but it doesnt stay there long enough to do anything. I hoping this is maybe a power issue so I'm leaving it plugged in overnight to attempt to charge it.
hope this info helps you, I feel like I was at a point to simply re flash a rom but messed up by rebooting from twrp.
I did it!!!!
Managed to get it to stay in fastboot mode and ran kindlerecover tool again. now have a working kindle running APEX launcher. Have to read up tomorrow and get cyanogenmod back.
Click to expand...
Click to collapse
Grats i'm glad it worked out for you man, i'll try out the same when i get my cable lol i ended up buying a new tablet thinking no one would solve this problem and now i just may have two if i get mine working also if you try loli pop again make sure you install gapps for it, that was my first mistake that led to me messing up my kindle the second being the factory reset, the devs should either disable or warn people not to try it since your screwed once you do anyways i'll give an update once i try to recover my kindle, cheers.

Stuck on bootloop - unrooted, S-ON, Unlocked, Tampered

Hi all... My device just went on bootloop. Last evening battery was drowned so I reached home and plugged it to charger and its on bootloop since then.. now fastboot screen is coming automatically on power on.
Screen is showing this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Don't know what to do as this device is not rooted or unlocked.

sumit77seo said:
Hi all... My device just went on bootloop. Last evening battery was drowned so I reached home and plugged it to charger and its on bootloop since then.. now fastboot screen is coming automatically on power on.
Screen is showing this:
Don't know what to do as this device is not rooted or unlocked.
Click to expand...
Click to collapse
You can try
Code:
fastboot erase cache
then a factory reset
otherwise you'll have to flash the 7.21.707.21 RUU to reset your phone back to stock. The ruu will wipe everything from your phone.
File and instructions here: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944

alray said:
You can try
Code:
fastboot erase cache
then a factory reset
otherwise you'll have to flash the 7.21.707.21 RUU to reset your phone back to stock. The ruu will wipe everything from your phone.
File and instructions here: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
Click to expand...
Click to collapse
Thanks I did all that... and I recovered successfully.. but after setting up... I just ran the older backup of my phone... and now its completely dead... No charging... no flashboot screen... nothing... completely dead.... But when plugged into system... After pressing power+vol down for 10 sec will make ding sound like its booting.... but nothing on phone... not even LED... Is my phone completely dead...

sumit77seo said:
Thanks I did all that... and I recovered successfully.. but after setting up... I just ran the older backup of my phone... and now its completely dead... No charging... no flashboot screen... nothing... completely dead.... But when plugged into system... After pressing power+vol down for 10 sec will make ding sound like its booting.... but nothing on phone... not even LED... Is my phone completely dead...
Click to expand...
Click to collapse
Sounds like your backup was corrupted or a mod inside the backup was no good for the device. Leave phone on the charger for a while and hopefully the juice will awaken it from it's sleep. Otherwise consider it bricked.
Sent from my C525c using Tapatalk

SHM said:
Sounds like your backup was corrupted or a mod inside the backup was no good for the device. Leave phone on the charger for a while and hopefully the juice will awaken it from it's sleep. Otherwise consider it bricked.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
Ok I will plug into the wall charger for 2-3 hours. What do you mean by bricked. So can't we unbrick it?? As I have heard somewhere no device can be bricked fully. As my device is not in warranty, the HTC guys will charge me much more... Can't we do anything?

sumit77seo said:
Ok I will plug into the wall charger for 2-3 hours. What do you mean by bricked. So can't we unbrick it?? As I have heard somewhere no device can be bricked fully. As my device is not in warranty, the HTC guys will charge me much more... Can't we do anything?
Click to expand...
Click to collapse
There are two types of bricks. Soft and Hard. Soft brick typically means you have access to your device in some way to some degree that which would allow you to recover the device promptly. An example of a soft brick would be to corrupt your partitions and neither the recovery or system works. Even if by installing a custom recovery. But access to rebootRUU still makes it plausible to restore everything assuming one has access to that RUU (this example is HTC specific).
A hard brick would be a scenario where nothing is accessible. System, recovery, bootloader, etc. Meaning there is no feasible way to gain the needed access to restore your device in some fashion so that it will work again.
Both types of bricks exist and both types of bricks are easily possible. Although, a hard brick is very unlikely to be seen by most since most typically have some sort of knowledge as to what they are doing prior to doing it. An example for a Hard Brick would be to attempt to reverse engineer the bootloader, make an error that goes unnoticed, and apply the mod with this fatal error to the device thus resulting in the device failing to boot at all.
Sent from my C525c using Tapatalk

SHM said:
There are two types of bricks. Soft and Hard.
Click to expand...
Click to collapse
though i tend to agree with you, but there are more than two types... i can think of at least four (not sure atm if i can think of more),
from mild, soft, hard, or just not-bricked-but-not-bootable either bricks
but when it goes from "Last evening battery was drowned so I reached home and plugged it to charger and its on bootloop since then" ... i wasnt flashing my phone or anything else, it just happened, then 99% of the time it's a hardware problem, and wont be fixed without changing the motherboard.

nkk71 said:
though i tend to agree with you, but there are more than two types... i can think of at least four (not sure atm if i can think of more),
from mild, soft, hard, or just not-bricked-but-not-bootable either bricks
but when it goes from "Last evening battery was drowned so I reached home and plugged it to charger and its on bootloop since then" ... i wasnt flashing my phone or anything else, it just happened, then 99% of the time it's a hardware problem, and wont be fixed without changing the motherboard.
Click to expand...
Click to collapse
A hardware issue could definitely be the cause. Thanks for bringing that up. As of there being four types... I believe there is really only two. Soft (still have access to some degree whether it be the recovery or just fastboot for example), hard (absolutely no access), and boot loops (Everything is operable but something as small as a file not having proper permissions), but could honestly be debatable so lets just agree just to agree lol.
With that said, I experienced a soft brick last weekend. I was converting my device to f2fs and borked my partitions after twrp abruptly crashed on me. Had no access to the recovery, system, and so on - it all failed to boot or respond in any way. I did however still have access to fastboot which allowed me to use my decrypted RUU. If not for that, my phone would be nothing more than a paperweight.
Sent from my C525c using Tapatalk

I believe I have bricked my HTC One Mini 2?

Was at work using both my company phone (iPhone 5) and my personal phone (HTC One Mini 2) just fine. Put my personal phone away to get on with actual work and came home at around 5:30'ish. Played a bit ("a bit") until about 9/10pm (I think?) whereby I looked for my phone to just check things like WhatsApp and Snapchat and the phone wasn't turning on when I was holding the power button. I just thought to myself "huh, the battery must be dead" and put it to charge and the charging LED (as well as the charging screen with the "do not distribute outside htc blabla" dev screen) displayed so I just assume it's charging as per usual. Fast forward to about 1am, I have finished using my computer and decide to hop into bed. I go to turn on my phone by first powering down with power, vol up and vol down (as usual) and then try to boot the phone up. It boots as normal up until the O/S loading screen with a pac-man boot animation (I have PAC ROM installed) whereby it will freeze on the "game over" image of the boot animation and then proceed to go to a black screen. I thought to myself "hm, must be a mistake or something" and try it again to no avail. So I then go into recovery to do a fresh install and I try to wipe the phone and I do a factory reset in twrp, but upon trying to format data, the progress bar doesn't move (and so I left it overnight as I couldn't be bothered to wait). Upon leaving it overnight (1am to 7am) to format the data, I wake up to see that the progress bar hadn't moved at all from 0%. I then just thought "maybe the phone has actually formatted it but hasn't updated the image on screen so me being the dumbo I am, decided to force shut down the phone (with power, volup and voldown) and upon trying to boot the phone up again, it displays the HTC logo with the red writing, tries to boot into the O/S, fails, and then tries to boot into recovery and gets stuck in a boot loop (it will show the twrp logo and then a black screen, twrp logo and then black screen etc.). I have tried to flash twrp again (without first removing the twrp currently on it) but I was wondering what I could do in this situation. I am able to access the bootmenu (for hboot and fastboot) but nothing else.
TL;DR: I think I bricked my HTC One Mini 2. Came home, charged phone and phone got stuck at boot animation. Wiped phone in recovery, it got stuck on formatting data and now It can't boot into the O/S since it's wiped and it can't boot into Recovery for whatever reason.

DistincTHD said:
blah blah
Click to expand...
Click to collapse
This is not Facebook, go straight to the point.
Did you install a different kernel?

kativiti said:
This is not Facebook, go straight to the point.
Did you install a different kernel?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sorry for the confusion, I wasn't doing that because I couldn't/didn't want to explain, it's just a common message people get after dev unlocking their HTC phones. And no, It was working up until when I tried to use it last night randomly. I flashed PAC-ROM ages ago (like maybe 2-3 weeks ago or maybe even a month) with the HTC One M9 Camera Kernel and that's it. I then tried to use it last night and what I explained in the original post occurred.

DistincTHD said:
[IMG="HTC Dev Message"]
Sorry for the confusion, I wasn't doing that because I couldn't/didn't want to explain, it's just a common message people get after dev unlocking their HTC phones. And no, It was working up until when I tried to use it last night randomly. I flashed PAC-ROM ages ago (like maybe 2-3 weeks ago or maybe even a month) with the HTC One M9 Camera Kernel and that's it. I then tried to use it last night and what I explained in the original post occurred.
Click to expand...
Click to collapse
Oops, Just realised you meant the whole post, not just the blah blah bit within the post. But yeah what I did, I explained above and in the original post. I basically just told a story to give a better idea of what generally happened before the phone just pooped out on me.

DistincTHD said:
Sorry for the confusion, I wasn't doing that because I couldn't/didn't want to explain, it's just a common message people get after dev unlocking their HTC phones. And no, It was working up until when I tried to use it last night randomly. I flashed PAC-ROM ages ago (like maybe 2-3 weeks ago or maybe even a month) with the HTC One M9 Camera Kernel and that's it. I then tried to use it last night and what I explained in the original post occurred.
Click to expand...
Click to collapse
Something its corrupted so try to reinstall everything using the files from this post plus your choosen ROM.
When rebooting phone unplug USB cable.

kativiti said:
Something its corrupted so try to reinstall everything using the files from this post plus your choosen ROM.
When rebooting phone unplug USB cable.
Click to expand...
Click to collapse
I can't access twrp recovery but I do have fastboot enabled and working and I can access the boot menu so how would I go about wiping everything before re-flashing the recovery and then re-installing the o/s and everything else?

Just tried to first erase everything before installing and it's locking me out of the phone? It's telling me that an administrator console is unable to erase the system or its data so I'm quite stumped at the moment

DistincTHD said:
Just tried to first erase everything before installing and it's locking me out of the phone? It's telling me that an administrator console is unable to erase the system or its data so I'm quite stumped at the moment
Click to expand...
Click to collapse
you don't need to do all that.
try to flash twrp. (if OK use it to wipe everything)
If NOT ok flash stock recovery and unlock bootloader( yes again, this will wipe your phone and fix permissions)
Then you can do all you want.
Good luck.
let me know...

kativiti said:
you don't need to do all that.
try to flash twrp. (if OK use it to wipe everything)
If NOT ok flash stock recovery and unlock bootloader( yes again, this will wipe your phone and fix permissions)
Then you can do all you want.
Good luck.
let me know...
Click to expand...
Click to collapse
Right, so before I read that message, I flashed stock recovery and tried to reformat data and now It won't let be get into the boot menu and the HTC dev writing is gone (so I think it's locked again). On top of this, it just keeps booting into the reformatting data screen and just ends up hanging so I think I will let the battery drain or something (no idea how long it would take, probably days) and then try again from there. Pretty sure it is bricked now though lol welp. Is there any way to cancel a format?

Getting "Your device is corrupt" message and I want to start completely fresh.

Getting "Your device is corrupt" message and I want to start completely fresh.
I had setup a Nexus 6 a couple years back for someone who was mostly blind and I used tasker to let them do most things they needed by voice only.
It was working fine until a couple days ago when somehow the device upgraded from Lollipop to Android 7.0. The way I initially unlocked the phone and obtained root, I didn't think it would ever be able to upgrade unless I intervened but it finally happened seemingly on its own.
Anyway, it lost root and many of the tasker commands stopped working because of it so I tried to get it back by:
1) Using fastboot to flashe twrp-3.1.1-0-shamu.img to recovery
2) Booting into recovery and installing SuperSU with TWRP after I made a backup
After that, the phone booted back up normally but still didn't have root access so I restarted again but when I tried to get into recovery I got a "no command" message. I was finally able to get passed that by pressing volume down (I think) and it gave me the standard android factory reset, wipe cache, etc. options. I tried wiping the cache and then after reboot I got this message:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And then it just disappears after a few seconds and the phone will not boot up.
Now though I can still get back into the bootloader menu with Power and Volume Down and even get back to the TWRP recovery where I tried restoring the backup I made before installing SuperSU but the same problem occurs.
I don't know what I've done wrong but I just want to start over. What do I need to do to wipe the phone completely and start over like it was brand new out of the box?

LaTropa64 said:
I had setup a Nexus 6 a couple years back for someone who was mostly blind and I used tasker to let them do most things they needed by voice only.
It was working fine until a couple days ago when somehow the device upgraded from Lollipop to Android 7.0. The way I initially unlocked the phone and obtained root, I didn't think it would ever be able to upgrade unless I intervened but it finally happened seemingly on its own.
Anyway, it lost root and many of the tasker commands stopped working because of it so I tried to get it back by:
1) Using fastboot to flashe twrp-3.1.1-0-shamu.img to recovery
2) Booting into recovery and installing SuperSU with TWRP after I made a backup
After that, the phone booted back up normally but still didn't have root access so I restarted again but when I tried to get into recovery I got a "no command" message. I was finally able to get passed that by pressing volume down (I think) and it gave me the standard android factory reset, wipe cache, etc. options. I tried wiping the cache and then after reboot I got this message:
And then it just disappears after a few seconds and the phone will not boot up.
Now though I can still get back into the bootloader menu with Power and Volume Down and even get back to the TWRP recovery where I tried restoring the backup I made before installing SuperSU but the same problem occurs.
I don't know what I've done wrong but I just want to start over. What do I need to do to wipe the phone completely and start over like it was brand new out of the box?
Click to expand...
Click to collapse
I'm not sure what to tell you, there's a lot of complication between these things but mostly seems like it'd include Re-flashing stock os 7.0 and obtaining root thru Android 7 without flashing any rom
Sent from my Z988 using Tapatalk
---------- Post added at 08:09 AM ---------- Previous post was at 08:08 AM ----------
And by complication I mean the whole concept of just starting over fresh
Sent from my Z988 using Tapatalk
---------- Post added at 08:09 AM ---------- Previous post was at 08:09 AM ----------
Good luck tho
Sent from my Z988 using Tapatalk

LaTropa64 said:
I don't know what I've done wrong but I just want to start over. What do I need to do to wipe the phone completely and start over like it was brand new out of the box?
Click to expand...
Click to collapse
Download a factory image from Google developer site. That site gives instructions to set-up your PC for fastboot (if you need it) and there is a flash all script in the download to handle the flash through fastboot. This thread will give you an overview. Using the flash all script will wipe the entire phone!
You can also fastboot flash each partition manually. If you use the -w flag, it will wipe all user data from the phone.
Be warned, the probability is you'll wipe the internal (user data) and if you want to try to back up first, you should be able to boot into TWRP and use ADB to do an a back up of user data to your PC using:
adb pull /path/to/files /home/[your username]/
E.G.
Windows:
adb pull /sdcard C:\Users\[your username]\Desktop
Linux:
adb pull /sdcard /home/[your username]/
You'll need administrator privileges on the PC to specify the output path.
---Edit---
You might look into the tasker beta to work with the newer nougat releases. I will say, all of my tasker profiles continued to work regardless of OS version with the exception of those relying on secure settings. Those I updated to use auto tools. There are other work around as well.

Follow what @ktmom says to get the device all straightened out firmware wise. As the device totally skipped Android 6 in doing its upgrade there could be undesired leftovers from the original install. Once you've installed the latest stock firmware from Google you can start over with your customizations, but be aware that installing TWRP, rooting the device, or both will cause the "device is corrupt" message you're seeing. That message will remain on every boot until a custom kernel which ignores dm-verity is installed.

In a few months, Galaxy S8 will get Bixby Voice so you could get one of them.
Sent from my Z988 using Tapatalk

Who in the hell would want to use Bixby?