[Q] Flashing TWRP failing! - One (M9) Q&A, Help & Troubleshooting

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!

Related

[Q] TWRP Recovery Will Not Flash or Restore

I really hate to start a new thread but I really can't find a reason/solution to this issue. It's just as the title says. I tried flashing the MIUI ROM just as any ROM and got a failed error. Then went to do my nandroid restore and it just hangs on the splash screen (boot screen). Anyway I thought there could be a bad download so I took out the SD and redownloaded synergy on my laptop, then put it back in the phone and nothing but the nandroid should let me restore. I even tried moving the files to the internal SD and nothing. The only thing I can think of is to Odin back to stock? Is it the same method as rooting? I'm sure I can find that out, but I'm just confused why it seems TWRP doesn't want to work. Thanks for any help, it's 4 a.m. here and I'm dog tired.
Are you on the latest TWRP?
If all else fails you could go back to stock and root again.
DarkManX4lf said:
Are you on the latest TWRP?
If all else fails you could go back to stock and root again.
Click to expand...
Click to collapse
I think so. Yeah, just didn't want to go throught it all, and didn't know why.
jtadak said:
I think so. Yeah, just didn't want to go throught it all, and didn't know why.
Click to expand...
Click to collapse
Can I just reflash recovery from the state I'm in, or do I still need to unroot? I've moved some of my files to the ext SD within recovery but some things won't move and I really don't want to wipe it.
jd14771 said:
Try wiping everything 3X, then go to the reboot menu, and reboot system, wipe both the cache and dalvik cache and try to restore.
Click to expand...
Click to collapse
Do you mean reboot recovery? I can't reboot system. Sorry, not trying to split hairs, just trying to be specific.
Odin back to stock seems like the best option.
Sent from a galaxy note 2 far far away...
are you able to flash a different rom, say a stock rom? It's possible you got a corrupted TWRP download.
Since they just released another update 2.4.3, you might want to try and download the zip file, wipe cashe and davick (may want to do it three times). Reboot back into TWRP 2.4.3 and see if it gives you some better luck.
I've had Nandroid backup that didn't work for whatever reason. I didn't test it prior to needing it, and got burned. It just wouldn't show up in the restore menu.
On a side note, what error did you get when you tried flashing MIUI?
Try rebooting recovery when you are in recovery already once before flashing/restoring anything anything.
mexiking713 said:
Odin back to stock seems like the best option.
Sent from a galaxy note 2 far far away...
Click to expand...
Click to collapse
Yes, that's what I did. I'm just bummed I had to wipe storage. Oh well, it's inevedible... I dig that sig though, with phone line up.
lovekeiiy said:
are you able to flash a different rom, say a stock rom? It's possible you got a corrupted TWRP download.
Since they just released another update 2.4.3, you might want to try and download the zip file, wipe cashe and davick (may want to do it three times). Reboot back into TWRP 2.4.3 and see if it gives you some better luck.
I've had Nandroid backup that didn't work for whatever reason. I didn't test it prior to needing it, and got burned. It just wouldn't show up in the restore menu.
On a side note, what error did you get when you tried flashing MIUI?
Click to expand...
Click to collapse
I tried multiple ROMs, but not a stock one. Hmm, I was on 2.3.2.3. I did'nt get a special error, just said a red message saying failed.
Evo_Shift said:
Try rebooting recovery when you are in recovery already once before flashing/restoring anything anything.
Click to expand...
Click to collapse
Tried that. Did'nt work.
jd14771 said:
no, i meant reboot system, the recovery will warm you that there is no os installed but go fourth with it, it will turn off and reboot back to recovery. at that point in time, wipe cashe/dalvik cache and try to install.
Click to expand...
Click to collapse
Ok, I was'nt sure. I just went back to stock. I just wanted to know what exactly was going on and why.
The only thing different on my phone is I got a 32 gig SD card. I transfed some of my files a couple days before doing anything of this. That's the only thing I can think of. Even after root/unroot it STILL won't do my nandroid restore. I had so much time and work into the apps I set up, games, ect. Really freakin sucks. I even went into the the TWRP backup folder and made sure the backup files were there before doing anything. I never even got to flash many ROMs, I kinda just stayed on Jellybomb.
I had the uTorrent app installed and I noticed that it changed a lot of files with the "u" in front that the uTorrent app has. Anyone know why that is?
Sent from my SPH-L900 using xda app-developers app
This is what it did to a lot of my files. But not the ones I tried to flash.
Sent from my SPH-L900 using xda app-developers app

[Q] Google play store not working

Important info in the story:
Device: Nexus 7 (Rooted)
OS: Cyanogenmod 10.2.0
Overall problem: Google play not working or getting apps on working Google play system.
So let me start from the beginning. I was trying to get an app to work but the app kept saying i need root permission, so i went on SuperSU and i accidentally clicked a button that supposedly gets rid of supersu (no warning whatsoever). so to fix this problem i reboot my device that doesn't work. So i went in twrp and installed supersu. so now another problem arose. When i open Google play it says no connection, even though i can get on chrome and other things. so at this point i'm just concerned. i go home and tried uninstalling Google play and reinstall it. doesn't work. Then i try clearing cache, doesn't work, then data, still doesn't work. after that i try to delete my gmail account to see if that works, does not. so then i try on backing up my device with twrp, then making a whole new restore to get a fresh copy of cyanogenmod. everything works but i have no apps and data. so backup this new cyanogenmod and tried to go back on my old not working save and it wont restore, it says it failed. so i wipe all data so now i don't have an OS and then i solved that and got back rooted and installed cyanogenmod. the i try to just restore data from my old cyanogenmod and it goes through but this time on boot it optimizes apps, done with that, now is stuck in a infinite bootloader. so i restore to my old cyanogenmod and this is where i am now.
The overall question is how to i either fix google play store, or how do i port my apps and data to the working cyanogenmod Google play store?
If you can't follow with my terrible typing skills tell me and ill try to clarify. I just thought starting from the beginning of the problem would help.
--resolved--
Lionex1 said:
Question: Why are you using cyanogenmod 3.2? Or was that a typo? Currently, you should be on either 10 or 11.
Click to expand...
Click to collapse
typo
HVC FOG3Y34 said:
typo
Click to expand...
Click to collapse
Thanks.
My suggestion:
-----BACKUP EVERYTHING-----
Flash the stock factory image and the stock kernel, and go from there. You can easily reinstall a new CM, and reroot if you lost it in the process. WugFresh's N7 toolkit is great for this.
Also - I had problems with TWRP on my nexus. CWM touch works much better, I find.
EDIT: The N7 toolkit will restore everything to factory defaults, and can do backups as well.
Lionex1 said:
Thanks.
My suggestion:
-----BACKUP EVERYTHING-----
Flash the stock factory image and the stock kernel, and go from there. You can easily reinstall a new CM, and reroot if you lost it in the process. WugFresh's N7 toolkit is great for this.
Also - I had problems with TWRP on my nexus. CWM touch works much better, I find.
Click to expand...
Click to collapse
how do i flash the sock factory image and the stock kernel?
HVC FOG3Y34 said:
how do i flash the sock factory image and the stock kernel?
Click to expand...
Click to collapse
http://www.wugfresh.com/nrt/
^that's the toolkit. Pretty self-explanatory GUI.
So doing this i won't lose any apps and data and ill have to reroot? cause all i care about is not losing apps and data and getting google play to work again with a root.
^that's the toolkit. Pretty self-explanatory GUI.
Click to expand...
Click to collapse
ok so when i'm selecting my android build what "CUSTOM ROM (Wi-Fi Tablet) - ?" do i use JB or KK?
HVC FOG3Y34 said:
ok so when i'm selecting my android build what "CUSTOM ROM (Wi-Fi Tablet) - ?" do i use JB or KK?
Click to expand...
Click to collapse
Android 4.4+ is kitkat, 4.1-4.3 is JB. Select what it's running currently.
Lionex1 said:
Android 4.4+ is kitkat, 4.1-4.3 is JB. Select what it's running currently.
Click to expand...
Click to collapse
I seem to be having trouble, can you take me step by step on what to click to do this?
HVC FOG3Y34 said:
I seem to be having trouble, can you take me step by step on what to click to do this?
Click to expand...
Click to collapse
Sure, what exactly are you having trouble with?
When you first start the app, it will ask for the version and device model. After that, it will ask for your recovery that you're currently running (maybe not in that order), select TWRP in your case. It will then download things, and the program will start up.
Lionex1 said:
Sure, what exactly are you having trouble with?
When you first start the app, it will ask for the version and device model. After that, it will ask for your recovery that you're currently running (maybe not in that order), select TWRP in your case. It will then download things, and the program will start up.
Click to expand...
Click to collapse
I got that part selecting the model type, i'm now in advanced utilities do i select flash zip?
HVC FOG3Y34 said:
I got that part selecting the model type, i'm now in advanced utilities do i select flash zip?
Click to expand...
Click to collapse
You don't have to go to advanced utilities. On the first screen, "backup", then "back to stock"
After that's done and everything works, you can root and flash custom recovery if you lost it.
Lionex1 said:
You don't have to go to advanced utilities. On the first screen, "backup", then "back to stock"
After that's done and everything works, you can root and flash custom recovery if you lost it.
Click to expand...
Click to collapse
Ok now what do i do in "Which factory image?" remember i have cyanogenmod 10.2.0 or do i just get default android then reroot and get cyanogen mod again.
HVC FOG3Y34 said:
Ok now what do i do in "Which factory image?" remember i have cyanogenmod 10.2.0 or do i just get default android then reroot and get cyanogen mod again.
Click to expand...
Click to collapse
Default, then reroot and cyanogen.
Confirm it's working on stock before flashing cyanogen.
Lionex1 said:
Default, then reroot and cyanogen.
Confirm it's working on stock before flashing cyanogen.
Click to expand...
Click to collapse
ok that part fixed it, i think i lost my root, but am i still unlocked? because isn't the unlocking part that loses your data.
HVC FOG3Y34 said:
ok that part fixed it, i think i lost my root, but am i still unlocked? because isn't the unlocking part that loses your data.
Click to expand...
Click to collapse
You backed everything up, right? I'm pretty sure it doesn't relock it if you reflash factory image (what you just did)
If it did, just unlock it.
Lionex1 said:
You backed everything up, right? I'm pretty sure it doesn't relock it if you reflash factory image (what you just did)
If it did, just unlock it.
Click to expand...
Click to collapse
Ok i have now got everything working except i now need to install cyanogenmod. but when i go to install it i click the thing that says "click here to install" it goes to twrp then stops. what can i do to fix this, im in twrp now.
HVC FOG3Y34 said:
Ok i have now got everything working except i now need to install cyanogenmod. but when i go to install it i click the thing that says "click here to install" it goes to twrp then stops. what can i do to fix this, im in twrp now.
Click to expand...
Click to collapse
Grab the flashable zip from somewhere, go into twrp, and select "install" then flash the zip.
where would the .zip be if installed it from Rom toolbox pro

[Q] restored a nandroid backup and now stuck on boot screen

help! lol
my dilemma, i updated to 4.4.3, rooted, created a nandroid backup.
then i installed viperone 2.5
all going well till phone stopped sending texts (ee update fault, common fault)
after checking solutions all say factory reset, did that, phone booted, but i couldnt log into google, kept saying could not connect to servers
thought ive had enough, restore my nand, and now its stuck on load screen, been left for 15 mins and no joy, i can still get into twrp but im at a loss at what i can do.
twrp wont let me mount internal storage so i can send another backup, only mounts sd card
s-on so limited options
houston33 said:
help! lol
my dilemma, i updated to 4.4.3, rooted, created a nandroid backup.
then i installed viperone 2.5
all going well till phone stopped sending texts (ee update fault, common fault)
after checking solutions all say factory reset, did that, phone booted, but i couldnt log into google, kept saying could not connect to servers
thought ive had enough, restore my nand, and now its stuck on load screen, been left for 15 mins and no joy, i can still get into twrp but im at a loss at what i can do.
twrp wont let me mount internal storage so i can send another backup, only mounts sd card
s-on so limited options
Click to expand...
Click to collapse
If you can get into recovery, you can get into your bootloader. Flash a new ROM using ADB.
Also, only factory reset as a last resort. There's usually a way to fix stuff without resorting to that.
xunholyx said:
If you can get into recovery, you can get into your bootloader. Flash a new ROM using ADB.
Also, only factory reset as a last resort. There's usually a way to fix stuff without resorting to that.
Click to expand...
Click to collapse
i thought flashing a new rom on the m8 required the firmware setup?
so i can just reinstall viperone 2.5 again?
408
so from where i am now i can just go to twrp and install android rev 21? or do i have to use adb sideload?
is 21 even compatible?
i swore i wasnt gonna mess on with this phone.........
houston33 said:
i thought flashing a new rom on the m8 required the firmware setup?
so i can just reinstall viperone 2.5 again?
Click to expand...
Click to collapse
You sure can. The newer firmware is needed for 4.4.4 ROMs. If you had 2.5, reflash it. It will work with the newest firmware as well. Just not the old stuff.
Here's a pointer: A dirty flash of the ROM you are currently running will reset your tweaks, and often fix problems you are having. When I start having glitches, I first reboot. If that didn't work; and I can't find a solution on XDA easily, I reflash my ROM; the dirty way. It really does help to clear up stuff, especially if you are using themes and tweaks.
Sadly didn't work.
Will have to use one of the stock na droid backups from the collection on here once the thread is up and running again
How do I access phone memory to copy the backup over? I only have boot loader and twrp
houston33 said:
Sadly didn't work.
Will have to use one of the stock na droid backups from the collection on here once the thread is up and running again
How do I access phone memory to copy the backup over? I only have boot loader and twrp
Click to expand...
Click to collapse
In TWRP, you can manage files easily.
Click advanced > file manager
There you can copy files, move them and change permissions. Plus deleting and renaming them.

Help with system partition reinstall HTC M8

Helloes ^^
I was trying to root HTC One M8 following a guide. I managed to unlock the bootloader and install TWRP 2.7.0.2 but I accidentally deleted the system partition :SS I hope I left everything else intact..
I downloaded OTA_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_R-4.16.401.13 and tried flashing it but Im getting
mount failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata
Click to expand...
Click to collapse
Package expects build fingerprint of htc/htc_europe/htc_m8:5.0.1./LRX22C/448934. 13:user/release-keys...
Click to expand...
Click to collapse
I also downloaded RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4 and tried to update but it fails with error 155(I tried locking the bootloader and running it again but it still gives me the same error
My bootloader is unlocked atm and S-on...
Is it possible to recover the os in any way?
------
After trying to flash like 5 roms flashing InsertCoin worked somehow...
Qitsch said:
Helloes ^^
I was trying to root HTC One M8 following a guide. I managed to unlock the bootloader and install TWRP 2.7.0.2 but I accidentally deleted the system partition :SS
Click to expand...
Click to collapse
Why did you flash such an old version TWRP? That one is from about 3 years ago, and will cause lots of problems!
Couple simple rules to live by, when modding these phones:
1) Do not wipe things in TWRP willy-nilly, without knowing what they are, or what the result will be. The option to wipe "system" is in the Advance wipe section. It's called "Advanced" for a reason. That alone would have been a warning to be careful, and not mess with things, unless you know what you are doing. It also clearly says in TWRP wipe screen, that most of the time, the default wipe (cache, Dalvik/ART and data) is all you ever need. It says that for a reason.
2) Right after you install TWRP, and before messing around with anything, you should make a TWRP backup of your current stock ROM. Definitely do that, before trying to flash root, ROMs, or any other mods. That way, if anything goes wrong (or you simply screw up, and wipe system) you have a backup, that you can easily restore.
Qitsch said:
I downloaded OTA_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_R-4.16.401.13 and tried flashing it but Im getting
Click to expand...
Click to collapse
In general, you should never flash a file named "OTA" unless you know exactly what you are doing. The requirements for an OTA on this device are steep:
a) Must currently have the version number directly before the OTA number (you can't skip or flash the same number OTA)
b) Must have stock recovery installed (not TWRP)
c) Must match your version (CID, MID). Do you have the Euro version? You never stated this info.
Qitsch said:
I also downloaded RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4 and tried to update but it fails with error 155(I tried locking the bootloader and running it again but it still gives me the same error
Click to expand...
Click to collapse
This RUU is only for the US Developer's Edition version M8. Will not work on any other version.
Even if you had the US Dev Ed (which is unlikely) this RUU would require the firmware being flashed, before the RUU will install (thus, Error 155).
In short, it seems like you are just guessing at solutions. Not a good idea.

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.

Categories

Resources