Develop Bugs

Bricked? Please help

Good evening,
before I start:
HTC Desire HD
Orange Branded
Clockwordmod Recovery
I was out and about today when I recieved a nice message telling me there was a system update to download and install. I got within WiFi signal and downloaded it. when I tried to run it, it kept hanging on the ClockwordMod (CWM) Recovery page. First it told me that it couldn't mount the SD card where the update was stored. So I mounted the SD card through CWM and tried again. This time it told me that it couldn't be verified. So I turned that off too. Then it told me something else didn't work so I disabled that (sorry, I can't remember but it begins with 'A'). I tried a final time to install the update but it wouldn't work still.
Then the phone wouldn't load. It just hung on the HTC white screen for about ten mins with no movement.
I removed the battery, reloaded by pressing Vol Down + On. I have tried every menu item but the loader tells me that an image (beginning with P****.zip) is missing. It lets me load the clockworkmod recovery page so I have tried to restore a backup that I made about a week ago. It restored it, (or so it said) but when I then told it to reload it still hangs on the HTC white screen.
It's now been hanging for ten mins and I'm just leaving it.
Does it just need to be left for a long time to reload from the HTC white screen?
If it does not reload, how can I get it to?
Many thanks for your impending help!

You havent bricked your phone, a bricked phone wont power on! For future reference, remember, you cannot flash an ota update with a custom recovery installed. As you have found out it messes your device up. Ok you have 2 options.
1. Try a full wipe from the mounts and storage menu. Then try to restore your backup.
2. Flash a custom rom from recovery.
Sent from my Desire HD using Tapatalk

AndroHero said:
You havent bricked your phone, a bricked phone wont power on! For future reference, remember, you cannot flash an ota update with a custom recovery installed. As you have found out it messes your device up. Ok you have 2 options.
1. Try a full wipe from the mounts and storage menu. Then try to restore your backup.
2. Flash a custom rom from recovery.
Click to expand...
Click to collapse
I really thought restoring my backup would have done it.
I now need to try a custom rom.

AndroHero said:
You havent bricked your phone, a bricked phone wont power on! For future reference, remember, you cannot flash an ota update with a custom recovery installed. As you have found out it messes your device up. Ok you have 2 options.
1. Try a full wipe from the mounts and storage menu. Then try to restore your backup.
2. Flash a custom rom from recovery.
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Would you happen to know where I can get the Orange ACE Rom from?

I've tried to install the Cyanogen Mod but that has got me no further.
I downloaded the most uptodate build of Cyanogen Mod (7) and copied it to my SD Card.
Through ClockworkMod Recovery I installed Cyanogen Mod and it told me that it had been successful. I restarted the phone and it got past the HTC white screen.....
I was very excited until it is not sat here on the Cyanogen Mod screen which just loads over and over again repeatedly.
Any other ideas please? I suspect I need the Orange ACE Stock Rom....is it available?

did you wipe your phone before trying to flash the new roms as AndroHero suggested?
if not try that first (you can do it via clockwork recovery or via easy full wipe from mero01 -> http://forum.xda-developers.com/showthread.php?t=868720)

-shadeless- said:
did you wipe your phone before trying to flash the new roms as AndroHero suggested?
if not try that first (you can do it via clockwork recovery or via easy full wipe from mero01 -> http://forum.xda-developers.com/showthread.php?t=868720)
Click to expand...
Click to collapse
yes, the only thing I didn't wipe was the SD card because that's where the rom / backup is stored. Do i need to completely wipe that then put the backup back on there?

as far as i know, it shouldn't be necessary. but i'm not really sure, sorry.
you could try formatting your sd card, wouldn't hurt, but maybe it would be better to wait for someone with more knowledge about android than me.

-shadeless- said:
as far as i know, it shouldn't be necessary. but i'm not really sure, sorry.
you could try formatting your sd card, wouldn't hurt, but maybe it would be better to wait for someone with more knowledge about android than me.
Click to expand...
Click to collapse
Thanks for your help so far. I am trying everything. If I could find the actual Orange Stock Rom (Ace) then I might get somewhere. I don't want to install a custom rom if not necessary.
EDIT: I have found an Orange Stock Rom (RUU). How do i install it?
I can only get to the bootloader screen so do I plug the USB cable in at this point and run the RUU from the PC once the drivers have installed? Do I put the RUU on the SD card and somehow run it from there?

i think this is the newest stock rom : http://forum.xda-developers.com/showthread.php?t=969374&highlight=orange+rom
but as AndroHero already mentioned, i think you can't flash stock RUUs with cwm recovery.
p.s. did you give easy wipe from the link from my previous post a try ?

-shadeless- said:
i think this is the newest stock rom : http://forum.xda-developers.com/showthread.php?t=969374&highlight=orange+rom
but as AndroHero already mentioned, i think you can't flash stock RUUs with cwm recovery.
p.s. did you give easy wipe from the link from my previous post a try ?
Click to expand...
Click to collapse
I must admit that i've not yet tried the Easy Wipe. At the moment I am downloading an older stock Rom (the one that was on there before this happened) and am following some other instructions to extract the PD98IMG.ZIP which appears to be missing.
I DID go through CWM to competely wipe everything with the exception of the SD card and i managed to almost get CyanogenMod working....it would work for about 20seconds before reloading again....very strange. It has given me hope though. I tried wiping everything before doing the restore of my original backup but still nothing.
the download is taking ages so I'll give easy wipe a go.....wait....

SOLVED
thank you for all who helped.
I solved this problem by downloading an older Orange Stock Rom from the link above. After that, I followed instructions in: http://forum.xda-developers.com/showthread.php?t=841890 and reinstalled the rom.zip that it mentions. Sure enough, I am back to where I started about 3 weeks ago but because everything was backed up to the cloud I really don't mind at all. Sure, I have to root it with VISIONary again to remove all the apps that Orange have stuffed in but I can cope with that.
In fact, the worst thing is that I completed Angry Birds and Angry Birds Seasons and now i have no proof!!
Thanks again all.

glad that you could finally solved it!
i, too just lost all my angry birds saves because i just downgraded so that i could root my dhd

[Q] 4.2 Upgrade Problems-- verizon gnex

My vzw nexus has been running mRom version x.x for sometime. I went to install the upgraded 4.2 rom via clockworkmod, (wipe cache and dalvik, flash over current rom) and it appeared to install successfully. However, when I rebooted I saw the lock screen for a split second and it just started to boot loop. I rebooted back into recovery and wiped all data and tried to reinstall the rom via through the new 0 partition, but I get the error symlink: some symlinks failed
E: Error in /sdcard/0/mRom_v3.0_JOP40C.zip (status 7)
I think that this may have something to do with the multiple users in 4.2, but don't quote me on it. I cannot get my computer to recognize my phone, when I go to mounts in cwm I can mount everything except the sdcard, although I think this problem was evident before I flashed. Any suggestions? I could try to restore to stock using galaxynexusrestore-- http://forum.xda-developers.com/showthread.php?t=1743939 but I have not tried it before so I cannot speak to weither it will work or not.
HELP!

Always always wipe data when changing an Android version. Unless it comes via OTA, which is specifically designed to fix all the little problems that will arise.
As to how to fix the problem, flashing a factory image
http://forum.xda-developers.com/showthread.php?t=1626895 will probably work. Just follow the rules for Toro. The toolkit you linked may work, but it's generally a better idea to not use them and actually familiarize yourself with how to fix things yourself, you'll be less likely to make mistakes in the future.

Same thing happened to me.
when i try to restore from backup Clockwork can't locate the backup file because the root file structure has changed to \0.
Is there an update to Recovery that fixes this?
Help!

Misread OP.

ironerd said:
Same thing happened to me.
when i try to restore from backup Clockwork can't locate the backup file because the root file structure has changed to \0.
Is there an update to Recovery that fixes this?
Help!
Click to expand...
Click to collapse
Clockwork dev said he knows about the issue and is working on a fix.
TWRP already has a patch out that solves the problem. If you decide to temporary move to TWRP it can be flashed through fastboot or Goomanager. CWM and TWRP backups are not compatible however.
http://teamw.in/androidmultiuser useful reading for how TWRP fixed it.

same problem, stuck at JB logo
Marisa said:
Clockwork dev said he knows about the issue and is working on a fix.
TWRP already has a patch out that solves the problem. If you decide to temporary move to TWRP it can be flashed through fastboot or Goomanager. CWM and TWRP backups are not compatible however.
http://teamw.in/androidmultiuser useful reading for how TWRP fixed it.
Click to expand...
Click to collapse
I was running stock JRO03O with Clockwork Recovery Mod and decided to flash the JB 4.2 ROM from Grouper (http://forum.xda-developers.com/showthread.php?t=1993545 - I can't post there since I'm too new).
The update must have succeeded, because I can see the new 0/ partition on my phone, but it won't boot past the "X" logo. I can boot into CWM and try various things, but of course because of the data structure changes, I can't actually recover to my last save. When I'm home, I'm hoping I can get the CWM backup off my phone to restore later, but without a terminal in CWM, I can't try to fix the path.
It's nice to hear that CW is working on a fix - I hope it's retroactive (I mean, helpful to those of use who already screwed up). Also, I've never flashed anything but OTA, so I didn't realize I needed to wipe data before flashing something that's supposed to be almost stock. I guess it matters how different from stock the ROM actually is.
What's next? I'll try to interface with my PC at home. If others have this problem, I'd be happy to hear your success (or fail) stories. I'll share mine once I've tried it.

The issue with non-OTA version updates is that the OTA is specifically designed to know what little bits and pieces need to be updated, removed, or left alone.
Flashing a ROM is usually intended as a fresh slate, as the dev cannot know exactly from where you started. Basically without the wipe, you could end up with old files loitering about the system and making it do things incorrectly at boot.
Koush
When trying to restore CWM backup move previous backups AND blobs folder to /data/media/clockworkmod if the folder does not exist simply create one or if unsure just go to recovery and make new backup, it will create necessary folders for you then move (or copy to be safe) files to location.... The blobs folder is what I was missing and why I kept getting error while trying to restore.
Click to expand...
Click to collapse
This should help your problem solving for the moment, if you're familiar enough with ADB to move the files that way it shouldn't take very long at all

thanks, and update of my status
Marisa said:
The issue with non-OTA version updates is that the OTA is specifically designed to know what little bits and pieces need to be updated, removed, or left alone.
Flashing a ROM is usually intended as a fresh slate, as the dev cannot know exactly from where you started. Basically without the wipe, you could end up with old files loitering about the system and making it do things incorrectly at boot.
Click to expand...
Click to collapse
Thanks for the extra insight. I wrestled with my phone all night and finally got it back to 4.1.1 (JRO030). Along the way I screwed up my adb or fastboot drivers, and for all my efforts I couldn't get any of my nexus toolkits to recognize the phone as in fastboot mode. Adb was fine, but fastboot was a no-go. I moved to a fresh computer after someone else had success with that, and read up on how to do a manual (adb command line) flash to factory image.
Now that that's done, I'm hoping I can restore from CWM to get back to where I was. If not, then yuck, but I'm optimistic.

[Q] Can't boot after SuperSU binary update

Hey hey,
Today I had a SuperSU update through the Play Store which I installed. When that was done it told me I needed to update my binary or something along those lines. Since I have an HTC it told me I should install it through a custom recovery like TWRP. I already had TWRP installed, so I went ahead and did that. After it did its thing, it rebooted. Or well, tried. I stared at the boot animation for about 10 minutes, and then I rebooted. I still didn't get past the boot animation. Then I shut it off, went into my bootloader and via there into the recovery. Downloaded the latest SuperSU zip and flashed it through TWRP. Rebooted, but no dice. A couple of reboots later and I'm unable to properly shut off my phone or get into the bootloader/recovery. When I try to shut it off with Power+Volume up it simply reboots. I also can't see my phone through ADB.
My M8 has been converted to Lollipop GPE and have had no issues at all before. I am sort of familiar with ADB, recovery's etc, but I would not call myself an expert. Right now I'm at a loss, and any help would be great.
Edit: Tried pressing Power + Volume down in the 3 seconds it's off before rebooting after doing Power + volume down. I can now access the bootloader and recovery, but I'm still not quite sure what to do next.

Phone needs to be booted into OS or in recovery for adb to work, so that is probably the cause of your adb issue right there.
Does fastboot work (phone needs to be in bootloader fastboot mode)? If so, try fastboot erase cache and install TWRP again by fastboot.
---------- Post added at 02:15 PM ---------- Previous post was at 02:14 PM ----------
jsmits447 said:
Edit: Tried pressing Power + Volume down in the 3 seconds it's off before rebooting after doing Power + volume down. I can now access the bootloader and recovery, but I'm still not quite sure what to do next.
Click to expand...
Click to collapse
Since you can now boot recovery, restore your nandroid that you made.

redpoint73 said:
Phone needs to be booted into OS or in recovery for adb to work, so that is probably the cause of your adb issue right there.
Does fastboot work (phone needs to be in bootloader fastboot mode)? If so, try fastboot erase cache and install TWRP again by fastboot.
---------- Post added at 02:15 PM ---------- Previous post was at 02:14 PM ----------
Since you can now boot recovery, restore your nandroid that you made.
Click to expand...
Click to collapse
Thanks for the reply. My last nandroid was quite a while ago. Got so many things changed I might as well do a reset. That would have the same effect, yes?
I suppose there is not a way for me to fix what is wrong? I prefer not to lose anything obviously, but if I would it wouldn't be that much of a big deal.

jsmits447 said:
Thanks for the reply. My last nandroid was quite a while ago. Got so many things changed I might as well do a reset. That would have the same effect, yes?
Click to expand...
Click to collapse
No, not the same at all. Folks constantly misunderstand what a factory reset does. All it does is wipe user data, it doesn't touch the ROM. This sounds like the opposite of what you want.
At least you have a nandroid! I was half expecting you to say you never made one (all too common on these forums lately, for some reason).
jsmits447 said:
I suppose there is not a way for me to fix what is wrong? I prefer not to lose anything obviously, but if I would it wouldn't be that much of a big deal.
Click to expand...
Click to collapse
I'm like 95% sure we can fix it. Couple options I can think of: restore your TWRP nandroid, and just select to restore SYSTEM and BOOT (and not DATA) and this will just restore the ROM without restoring your user data.
This is assuming your nandroid was taken with the current GPE ROM at least?
Other idea is to find the same stock GPE ROM (assuming that is what you have) as a flashable zip, and either adb push it to the phone, or put it on removeable SD using a card reader connected to your computer. Then boot into TWRP and flash the ROM.
I'm thinking all that has happened is that the SuperSU flash somehow damaged the ROM, and we just need to restore the ROM.

redpoint73 said:
No, not the same at all. Folks constantly misunderstand what a factory reset does. All it does is wipe user data, it doesn't touch the ROM. This sounds like the opposite of what you want.
At least you have a nandroid! I was half expecting you to say you never made one (all too common on these forums lately, for some reason).
I'm like 95% sure we can fix it. Couple options I can think of: restore your TWRP nandroid, and just select to restore SYSTEM and BOOT (and not DATA) and this will just restore the ROM without restoring your user data.
This is assuming your nandroid was taken with the current GPE ROM at least?
Other idea is to find the same stock GPE ROM (assuming that is what you have) as a flashable zip, and either adb push it to the phone, or put it on removeable SD using a card reader connected to your computer. Then boot into TWRP and flash the ROM.
I'm thinking all that has happened is that the SuperSU flash somehow damaged the ROM, and we just need to restore the ROM.
Click to expand...
Click to collapse
Yeah, for once I decided to create a backup when I'm told to. I'm actually not sure it's the Lollipop nandroid. I made it 10 februari 2014, but there's a chance it's the one from Kitkat before I upgraded to Lollipop. Any way I could figure out? Could I make my problem worse by flashing the Kitkat one on the Lollipop if I wanted to try and see which one it is by flashing?
Thanks for clearing up what a factory reset does! Great to know.

jsmits447 said:
Could I make my problem worse by flashing the Kitkat one on the Lollipop if I wanted to try and see which one it is by flashing?
Click to expand...
Click to collapse
It might lead to a firmware-ROM mismatch (the nandroid backs up and restores the ROM and user data, but not firmware), breaking WiFi or other things. But nothing that isn't reversible.
Just make a nandroid of your current setup. Then worst case if you just restore back to your present situation.

redpoint73 said:
It might lead to a firmware-ROM mismatch (the nandroid backs up and restores the ROM and user data, but not firmware), breaking WiFi or other things. But nothing that isn't reversible.
Just make a nandroid of your current setup. Then worst case if you just restore back to your present situation.
Click to expand...
Click to collapse
Alright, will do. Be right back.

Just restored the nandroid from the 10th of december in twrp. It now asks me if I want to install SuperSU. Should I?

I went ahead and also installed SuperSU when it asked me to. Didnt even get to the boot animation then. Only saw "Google" and the little open lock. I have now restored to my Lollipop nandroid I just made.

[Q] Flashing TWRP failing!

Right, so. Managed to unlock and root my M9 successfully, no problems, using a good guide, which included making a Nandroid backup prior to rooting.
So I decide to get rid of LeeDroid and restore my Nandroid backup. All went well. Then TWRP asks if I want to install SuperSU as my device isn't rooted. So swipe yes, and it goes through the usual list, and just as it gets to the last line my phone goes off, and reboots.
I've tried both the stable and beta and always get the same damn crash/reboot, tried the mounting methods, but NOTHING works!
Could anyone shed any light as to why? It's the GSM variant of the M9.

Vesten said:
Right, so. Managed to unlock and root my M9 successfully, no problems, using a good guide, which included making a Nandroid backup prior to rooting.
So I decide to get rid of LeeDroid and restore my Nandroid backup. All went well. Then TWRP asks if I want to install SuperSU as my device isn't rooted. So swipe yes, and it goes through the usual list, and just as it gets to the last line my phone goes off, and reboots.
I've tried both the stable and beta and always get the same damn crash/reboot, tried the mounting methods, but NOTHING works!
Could anyone shed any light as to why? It's the GSM variant of the M9.
Click to expand...
Click to collapse
what exact version of twrp?
Is the backup a system IMAGE backup?
are you entering TWRP in read-only mode?
When you try to restore now, what does the terminal output say?

TWRP version 2.8.7.0
The backup was made using TWRP after flashing it for the first time, which included the usual data, system, etc.
Not sure about TWRP entering read only mode. I read it only does this on unmodified software. Mine is still saying modified even after restoring my nandroid.
Also unsure of what the terminal says without copying the log. Can restore it as many times as I want.
Can't be much more help until I get to a PC.
I'm still S-On, etc. Have a feeling it's to do with the TWRP read only thing...

Vesten said:
TWRP version 2.8.7.0
The backup was made using TWRP after flashing it for the first time, which included the usual data, system, etc.
Not sure about TWRP entering read only mode. I read it only does this on unmodified software. Mine is still saying modified even after restoring my nandroid.
Also unsure of what the terminal says without copying the log. Can restore it as many times as I want.
Can't be much more help until I get to a PC.
I'm still S-On, etc. Have a feeling it's to do with the TWRP read only thing...
Click to expand...
Click to collapse
well, when you go to restore twrp, does it say unable to wipe system/cache, etc?
If so, go into the mount menu and put a check mark in the system read only box, then uncheck it and try to restore again.
If that doesn't work, try updating to the latest twrp, which is 2.8.7.1. http://forum.xda-developers.com/devdb/project/?id=8915#downloads

jollywhitefoot said:
well, when you go to restore twrp, does it say unable to wipe system/cache, etc?
If so, go into the mount menu and put a check mark in the system read only box, then uncheck it and try to restore again.
If that doesn't work, try updating to the latest twrp, which is 2.8.7.1. http://forum.xda-developers.com/devdb/project/?id=8915#downloads
Click to expand...
Click to collapse
I'll have to check, but don't think it does.
I'll try that new version of TWRP and report back.
Many thanks for the help, greatly appreciated.

jollywhitefoot said:
well, when you go to restore twrp, does it say unable to wipe system/cache, etc?
If so, go into the mount menu and put a check mark in the system read only box, then uncheck it and try to restore again.
If that doesn't work, try updating to the latest twrp, which is 2.8.7.1. http://forum.xda-developers.com/devdb/project/?id=8915#downloads
Click to expand...
Click to collapse
Flashed that latest TWRP. Then tried flashing SuperSU. Same thing. Just shuts off completely and reboots back to Android.
In the mount menu, system is unchecked. and the bottom "Only mount system read-only" is also unchecked.
The Terminal log gets to..
"Placing files..."
Restoring files..."
Then shuts off. I'm starting to think I'm going to have to flash a stock RUU and start from scratch.
BTW this is after checking system. It seems to do nothing at all.
EDIT: Would not having an external SD in it matter at all? I originally flashed SuperSU using the internal SD card.

Vesten said:
Flashed that latest TWRP. Then tried flashing SuperSU. Same thing. Just shuts off completely and reboots back to Android.
In the mount menu, system is unchecked. and the bottom "Only mount system read-only" is also unchecked.
The Terminal log gets to..
"Placing files..."
Restoring files..."
Then shuts off. I'm starting to think I'm going to have to flash a stock RUU and start from scratch.
BTW this is after checking system. It seems to do nothing at all.
EDIT: Would not having an external SD in it matter at all? I originally flashed SuperSU using the internal SD card.
Click to expand...
Click to collapse
What happens when you restore your backup and reboot without installing supersu?

jollywhitefoot said:
What happens when you restore your backup and reboot without installing supersu?
Click to expand...
Click to collapse
Will let you know soon. Just restoring again.
When I made the Nandroid backup, there's a new option to backup recovery too, which I did. Could this mean anything? I'm assuming it's backed up TWRP because stock obviously wasn't present when making the backup.
Will try and screenshot the log.

Vesten said:
Will let you know soon. Just restoring again.
When I made the Nandroid backup, there's a new option to backup recovery too, which I did. Could this mean anything? I'm assuming it's backed up TWRP because stock obviously wasn't present when making the backup.
Will try and screenshot the log.
Click to expand...
Click to collapse
Yeah backing up recovery doesn't matter....as you suspected it just backs up twrp, so if you backed up the older version, then updated it, don't restore the old version

jollywhitefoot said:
Yeah backing up recovery doesn't matter....as you suspected it just backs up twrp, so if you backed up the older version, then updated it, don't restore the old version
Click to expand...
Click to collapse
Interesting. There's nothing saying it couldn't write anything..
Just tried opening SuperSU from my restored backup, and hits me with "There is no SuperSU binary installed!" This is a problem, blah, blah, etc.
Then tried check-boxing the 'system' box in the Mount section. Then tried flashing UPDATESuperSu.VsXX and just gave me the usual as said above. Crashed and reboots.
https://www.dropbox.com/s/cvkclw8xuzua4u3/2015-07-20 21.56.37.png?dl=0
Losing the will to live! Ha

What about trying to push SuperSU via ADB?
EDIT: Think I'm getting ahead of myself. Not possible to flash SuperSU via ADB is it..?

Vesten said:
What about trying to push SuperSU via ADB?
EDIT: Think I'm getting ahead of myself. Not possible to flash SuperSU via ADB is it..?
Click to expand...
Click to collapse
The only way I ever do it is by swiping to install as I'm rebooting out of recovery.

jollywhitefoot said:
The only way I ever do it is by swiping to install as I'm rebooting out of recovery.
Click to expand...
Click to collapse
Would you say the nuclear option would be to sit and bide my time until a decent RUU becomes available and start from scratch?

Vesten said:
Would you say the nuclear option would be to sit and bide my time until a decent RUU becomes available and start from scratch?
Click to expand...
Click to collapse
What's your ultimate goal? Stock, rooted? What cid and firmware are you on?

jollywhitefoot said:
What's your ultimate goal? Stock, rooted? What cid and firmware are you on?
Click to expand...
Click to collapse
Well I was going to sell the phone, since it's only 2 weeks old, and obviously for warranty reasons. So back to 100% stock, which includes it saying Software Status: Official and it saying "Locked" instead of re-locked.
CID is HTC__001
Firmware is Lollipop 5.0.2 - Software version 1.40.401.8 (CL549783 release-keys)

Vesten said:
Well I was going to sell the phone, since it's only 2 weeks old, and obviously for warranty reasons. So back to 100% stock, which includes it saying Software Status: Official and it saying "Locked" instead of re-locked.
CID is HTC__001
Firmware is Lollipop 5.0.2 - Software version 1.40.401.8 (CL549783 release-keys)
Click to expand...
Click to collapse
Then yeah, just ruu back to stock and bobs your uncle. You don't have to wait, an ruu is available for 1.40.401

jollywhitefoot said:
Then yeah, just ruu back to stock and bobs your uncle. You don't have to wait, an ruu is available for 1.40.401
Click to expand...
Click to collapse
What about stock recovery? Is that included I take it...?
Still getting used to all this in-depth flashing Android stuff. Managed to convert my M8 to the GP Edition without any trouble.

Vesten said:
What about stock recovery? Is that included I take it...?
Still getting used to all this in-depth flashing Android stuff. Managed to convert my M8 to the GP Edition without any trouble.
Click to expand...
Click to collapse
Yeah. That's included. If you did that then you can get that thing back to stock.
Probably find the ruu here: http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698

jollywhitefoot said:
Yeah. That's included. If you did that then you can get that thing back to stock.
Probably find the ruu here: http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
Click to expand...
Click to collapse
Wow, thankyou! I've been Googling RUU's all night at work and found nothing like this. Think I'll do that and flash the RUU and start afresh!
Getting a killer 17.4 kbp/s though. 100mb connection wasted. Ha!

jollywhitefoot said:
Yeah. That's included. If you did that then you can get that thing back to stock.
Probably find the ruu here: http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
Click to expand...
Click to collapse
Yay it worked! Using a stock image from that link. Something must of been really screwed up. I'm now re-rooted! Many thanks for your help!

TWRP - Unable to mount storage (Moto Z Play on Nougat)

​I've been using the forums for a while but this is the first time I post on here, so I'm not so sure if I'm posting this in the right place. But I need any help I can get at this point.
​So a while ago I unlocked and rooted my Moto Z Play by flashing TWRP recovery with the fastboot ADB tools. Things were fine, but then I accidentally let the phone do an automatic OTA update. When the phone was going to boot, it went straight to TWRP recovery and after I input my unlock pattern, it gave me a couple lines of text. In these lines was a red line of text saying "Unable to mount storage" and then it would go to the recovery menu. It won't boot past the recovery anymore.
​I looked it up but I can't seem to find clear answers anywhere, as many that I have found have their storage indicating that they have "0mb" when they go to backup. I don't have that problem as all my storage is present and even MTP is enabled. Hopefully someone can help me out here anyway possible.

You can not install OTA updates on ROOTED phone with TWRP recovery.
For working OTA you must have stock recovery and NO ROOT.
If you have XT 1635-02 version, you can reflash your phone using this RSD LITE unbrick tool https://forum.xda-developers.com/ge...orola-usb-drivers-rsd-lite-firmware-t3042687- and you can try to use this firmware for Moto Z Play : https://androidfilehost.com/?fid=673791459329058517
Your phone data will be deteled.

Ax1qwer said:
Your phone data will be deteled.
Click to expand...
Click to collapse
This sounds a bit too hard for me. Usually it is sufficient to flash a firmware with a similar version like you currently have installed, omitting "erase userdata", meaning you do a dirty flash keeping the data.
Alternative, if you want to keep data but erase the phone installing a firmware, you may do backup in twrp and restore data after the phone runs. But keep in mind that a) there were some problems restoring Nandroid backups on Z Play and b) /data/media must be treated separately, which usually is the data you want to keep (mainly: photos and videos you made). You need to enter your phone pin to decrypt data to mount it, maybe that is the missing step.

If you cannot receive OTA updates on a phone with custom recovery, even after (say) restoring a full TWRP System Image backup. . . doesn't that imply, in practice, that you cannot ever return to a stock experience?
I have a stock Z Play with the latest 7.1.1 updates. If I decide to unlock and install LineageOS, there is no way to get back to stock? ever? I mean, I knew about the warranty, that safetynet won't pass, and that I can't re-lock the bootloader. I'm fine with all that. But I thought I could at least get back to the stock ROM, and continue to receive OTA updates. Instead, it sounds like running my backup would be hell: the phone would constantly nag me to install OTA updates, yet if I ever slipped up and said "yes" it would be bricked.
Is there no way to back up the original recovery partition too, so that you can make the OTA updater happy?

mark04 said:
Is there no way to back up the original recovery partition too, so that you can make the OTA updater happy?
Click to expand...
Click to collapse
The are several easy possibilities.
You can get some firmware which you install using fastboot flash. You may decide to only flash stock recovery. For a successful update you need to have system, boot, recovery, logo, oem (from memory, hope I got this right) in exactly the same version.
You can use fastboot boot to start recovery. Then you should be able to restore your recovery backup.
My usual way: if you have stock, never install twrp. Always boot it when needed using fastboot boot. Then you don't need to care about recovery when updating.
If an update does not work, your always can decide to install a full stock ROM, if you omit the command "erase userdata", your data usually survives fine. No guarantee of course, always do a backup. Don't forget data/media where personal things are stored and never covered by Nandroid backup of twrp.

tag68 said:
My usual way: if you have stock, never install twrp. Always boot it when needed using fastboot boot. Then you don't need to care about recovery when updating.
Click to expand...
Click to collapse
Aha---great suggestion, thanks! I would never have thought of that, even though I had to do it on another device once where the bootloader kept overwriting the recovery.
tag68 said:
If an update does not work, your always can decide to install a full stock ROM, if you omit the command "erase userdata", your data usually survives fine. No guarantee of course, always do a backup. Don't forget data/media where personal things are stored and never covered by Nandroid backup of twrp.
Click to expand...
Click to collapse
I was just reading up on how to wipe and install a full stock ROM (factory image). It seems reasonably straightforward, IF you can find the correct image. This worries me a little, because my device is RETUS and there aren't many of those images floating around. None on lolinet.com for example. Some people say to use a RETAIL image but does anyone actually understand how they are different, and what the repercussions might be?

mark04 said:
... and there aren't many of those images floating around. None on lolinet.com for example.
Click to expand...
Click to collapse
You may have a look at firmware.center. They have a lot, but I'm not sure if all are working fine. You may need to do a backup and try. But you nowhere get the safety it's right, because Lenorola does not release signed versions (which would also allow relocking).
Note: For me all the firmwares from there worked by now.
mark04 said:
Some people say to use a RETAIL image but does anyone actually understand how they are different, and what the repercussions might be?
Click to expand...
Click to collapse
Changing update channel is said to be possible, but I never tried it. If you really want it you may try searching a bit in xda forums of similar but older phones how experiences with this are.