Hello All
I am the textbook Long-Time-Lurker First-Time-Poster. I apologise for some very clueless questions, but I am largely self-taught when it comes to ROM flashing etc on Android.
I have a Taiwan HTC 10 (currently with software version 1.55.709.5). I have flashed TWRP recovery and SuperSU Free 2.72. I have backed up the System and the Sytem Image (two separate backups) on to my external sdCard (I think I should have done that prior to flashing the SuperSU - my bad I guess).
I now want to revert back to stock recovery so I can recieve the new 1.80.709.1 update and so I know how to do this in the future. Because I have the Taiwan version there is no RUU for me to be able to easily flash back to stock, so I think I have to flash both the TWRP Backup and the Stock Recovery for 1.55.709.5 from the Stock Collection page. I assume that I would do it in this order:
1. Flash the TWRP Backup first using the standard method in TWRP and perform the standard TWRP wipes. I assume that I should also let the phone do a full system reboot before going to the next step.
2. Then I would flash the Stock Recovery - but I am not totally sure how to do this. Is there a method to do it using TWRP itself or should I do it from fastboot using the command "fastboot flash recovery 1.55.709.5_rec.img"? Is there something else I will have to do after that (e.g. wiping caches) and, if so, how do I do that?
Am I correct in my thinking?
To explain my cluelessness I have come from using Galaxy devices for the past few years where I just wanted to get away from TouchWiz as fast as possible - so I have never reverted a device back to stock. I also have used ClockworkMod as my recovery (because it was what I learnt with my Nexus One back in the day).
I thank you in advance for your help, and if you need me to post other information about my phone, please remember I may be tardy in replying due to timezones - I am in New Zealand.
Restore your stock system image and boot if you made one before modifying sytem. If not grab the one in the stock thread for your phone. Then boot to download mode and flash stock recovery with fastboot. Reboot to system and take ota
Sent from my HTC 10 using XDA-Developers mobile app
No need to wipe anything.
Just restore System img (already SU? Then Download one from the other Thread here on xda) and you can also restore recovery in TWRP simply Switch to img files instead of zip at the bottom of installing files.
All in one go, Reboot system take OTA and fastboot Flash twrp again.
If you Flash Systemless SU in the future you can still take OTAs
Thank you both for your help. I have been able to restore back to stock pretty much following your suggestions. For others who may be in the situation as I here are the steps I went through:
1. I "system image" backed up my setup - just in case.
2. using TWRP, I flashed the stock image for current software (1.55.709.15) from the [STOCK] Guides and Stock Backups/Recovery/OTA/RUU thread.
3. I had to do the standard three wipes in TWRP to get it back to stock as well - this was the only way that I could get rid of the SuperSU app and I had to go through the first-time-starting setup again. This made me confident that I was back to a pure stock installation.
4. I booted into download mode and used fastboot to flash the stock recovery for 1.55.709.15 (from the same thread as above).
5. Restarted the system and from there downloaded and installed the update - and after 10-15 minutes it successfully rebooted and gave me the message that it had worked.
Thanks again.
hi
are u htc cidnum HTC__621 ?
now can u OTA update ?
because my htc10 rom ver 1.55.709.1 .
now i cant ota update.
htcppadol said:
are u htc cidnum HTC__621 ?
now can u OTA update ?
because my htc10 rom ver 1.55.709.1 .
now i cant ota update.
Click to expand...
Click to collapse
Yes that is my CID, and yes I have updated. Did you change your recovery or system? Because that is what I did, and the process I describe above is how I got it back to stock so I could get the latest OTA update.
Hello,
I've a Taiwanese HTC 10 converted to USA (CID and MID) and flashed with official Nougat RUU. It's working quite good however I wanted to return it to default Taiwanese version and I couldn't.
What I had done:
1) Flashed latest version of TWRP
2) I changed CID and MID to default settings
3) I restored the backup of Taiwanese version downloaded from a thread here using TWRP.
4) I restored original recovery downloaded from a thread here
Following these steps my phone was unable to boot again and a boot loop occurred. To fix the phone I changed CID and MID to USA and thankfully the RUU restored my device to a working state.
I think I'm missing some procedure in TWRP. I only restored a backup using TWRP. It took about a minute or less to complete "successfully".
Do I need to do an extra procedure? Apparently the phone never recognized the Taiwanese version as in download mode the device shown the version of USA ROM even with the backup restored using TWRP.
I'm s-off (Sunshine) with bootloader locked. I think this shouldn't affect as TWRP installed properly and I'm s-off.
Thank you.
markthirteen said:
Thank you both for your help. I have been able to restore back to stock pretty much following your suggestions. For others who may be in the situation as I here are the steps I went through:
1. I "system image" backed up my setup - just in case.
2. using TWRP, I flashed the stock image for current software (1.55.709.15) from the [STOCK] Guides and Stock Backups/Recovery/OTA/RUU thread.
3. I had to do the standard three wipes in TWRP to get it back to stock as well - this was the only way that I could get rid of the SuperSU app and I had to go through the first-time-starting setup again. This made me confident that I was back to a pure stock installation.
4. I booted into download mode and used fastboot to flash the stock recovery for 1.55.709.15 (from the same thread as above).
5. Restarted the system and from there downloaded and installed the update - and after 10-15 minutes it successfully rebooted and gave me the message that it had worked.
Thanks again.
Click to expand...
Click to collapse
Related
Hello all,
I've got an unbranded international (taiwan) HOX.
Today I was notified that I got an update availabe for my device - finally JB!
So I let it download and install, but when it turns off to install (in CWM) it automatically I've got an error that says
PHP:
"E: unknown volume for path [file path]"
"E: Can't mount [file path]"
"Installation aborted."
So I tried to install the file from the zip manually (in CWM) but I got these errors:
PHP:
"E: failed to verify whole-file signature"
"E: signature verification failed"
"Installation aborted."
Also tried to put it in another folder and install manually, but no luck, and even re-download it. (Delete, let it download the update again and install).
Another friend who's got the same phone as mine (we bought it at the same store) did get to install the update successfully.
Any thoughts? I'll go ahead and say that my phone has CWM and is rooted. my friend's phone is clean in that matter, no modifications.
noodlez04 said:
Hello all,
I've got an unbranded international (taiwan) HOX.
Today I was notified that I got an update availabe for my device - finally JB!
So I let it download and install, but when it turns off to install (in CWM) it automatically I've got an error that says
PHP:
"E: unknown volume for path [file path]"
"E: Can't mount [file path]"
"Installation aborted."
So I tried to install the file from the zip manually (in CWM) but I got these errors:
PHP:
"E: failed to verify whole-file signature"
"E: signature verification failed"
"Installation aborted."
Also tried to put it in another folder and install manually, but no luck, and even re-download it. (Delete, let it download the update again and install).
Another friend who's got the same phone as mine (we bought it at the same store) did get to install the update successfully.
Any thoughts? I'll go ahead and say that my phone has CWM and is rooted. my friend's phone is clean in that matter, no modifications.
Click to expand...
Click to collapse
You need to go back to stock in everything to get that update ... It needs stock recovery and locked bootloader ...
chaun1308 said:
You need to go back to stock in everything to get that update ... It needs stock recovery and locked bootloader ...
Click to expand...
Click to collapse
Could you please refer me to a guide that will help me do that?
and from my understanding, If I'll go back to stock, and update, I'll have to unlock the bootloader again. Last time I did that I had to delete everything on my phone (I guess this will happen when I revert the root and bootloader unlocking too), so got any good way to backup all the app data and everything I need?
Thanks.
noodlez04 said:
Could you please refer me to a guide that will help me do that?
and from my understanding, If I'll go back to stock, and update, I'll have to unlock the bootloader again. Last time I did that I had to delete everything on my phone (I guess this will happen when I revert the root and bootloader unlocking too), so got any good way to backup all the app data and everything I need?
Thanks.
Click to expand...
Click to collapse
Correction . You will have to relock the bootloader again . And since you've rootedd your phone , use Titanium Backup or MyBackup .
This video will guide you to complete stock .
Relocking bootloader is not necessary for OTA updates, but you need stock recovery.
You have to find a stock recovery and then flash it via Fastboot.
Tutorials over here: http://forum.xda-developers.com/showthread.php?t=1832891
Agree with webpatrick
you only need stock recovery to install OTA updates, just find your original rom(or extract from ruu) and flash it in bootloader fastboot flash recovery path_to_recovery_signed.img
not sure if it requires locking the bootloader or not, after that you can reinstall CWM the way you did before and make a backup.
There are 2 options
1:
Flash the non-rooted stock rom with stock boot.img and stock recovery. Bootloader can stay UNLOCKED.
2:
Flash the right RUU, only LOCKING the bootloader is needed. The ruu will flash the stock recovery and boot.img.
Just to be clear
Verstuurd van mijn HTC One X
Need some clearing up here:
1. Can my phone stay rooted? if not - how do I remove SuperSU? tried to remove it from ES by removing the SU file and the app from system/app but that didn't work. - EDIT: Managed to remove root from my device using HTC Quick Root, though it says I need to install secure boot.img to entirely remove root.
2. I tried to flash a recovery file I found in a guide, but the recovery doesn't really work...when I try to access the recovery I got the error screen (the one with the red triangle and exclamation mark), so can someone refer me to a working recovery? attached my software information.
3. Do I need to relock my bootloader or not?
Thanks alot guys, I'm pretty much of a newbie in this whole business
Okay let me lay it down for you.. Pretty simple.. This process doesn't need you to relock the bootloader. (Even if you had to using the other process you would be adding a couple of minutes more in unlocking bootloader)
method1:
1- First things first get your RUU depending upon the version you are at. I haven't had a look at your picture. but just make sure that your region is correct and that the version you possess is either the same version or higher.
2- You need to flash the recovery as that is what will update the recovery and the ROM. so as mentioned above you can just go into fastboot and then flash recovery using the RUU.
method 2:
just relock te bootloader by going into fastboot and typing "fastboot oem lock".
Once that is done you can just run RUU and it will update everything for you. Once complete just unlock bootloader and then flash CWM.. thats it
zainalabididn.syed said:
Okay let me lay it down for you.. Pretty simple.. This process doesn't need you to relock the bootloader. (Even if you had to using the other process you would be adding a couple of minutes more in unlocking bootloader)
method1:
1- First things first get your RUU depending upon the version you are at. I haven't had a look at your picture. but just make sure that your region is correct and that the version you possess is either the same version or higher.
2- You need to flash the recovery as that is what will update the recovery and the ROM. so as mentioned above you can just go into fastboot and then flash recovery using the RUU.
method 2:
just relock te bootloader by going into fastboot and typing "fastboot oem lock".
Once that is done you can just run RUU and it will update everything for you. Once complete just unlock bootloader and then flash CWM.. thats it
Click to expand...
Click to collapse
now I've got a few problems with that:
first of all, my version is 2.18 and there is no RUU for that version for my HTC (which is TWM-TW) yet. and I don't wanna go back to stock ROM, it is the one I have. I just want to set my phone straight so it can get the OTA JB update.
The problem I think I've got now is that my recovery is malfunctioning. I think I don't have the right recovery, since when I try to go into recovery mode I get the red triangle and exclamation mark.
When I tried to install the update, it downloaded it, went into recovery, started doing the process (the green bar was progressing) and then out of the blue - error screen (red triangle and exclamation mark)...
Any ideas?
I always have this problem when i try to update even if i go back to the stock recovery.The problem is that you installed something that modified you'r system (in my case i've installed using CWM the Google Now and some other stuff on it) and now the phone can't update because something is "messed up" in the system.You now have to restore and old backup in CWM,preferably one that doesn't have any mods in it.The recovery is good,otherwise it wouldn't work at all.
jeyml said:
I always have this problem when i try to update even if i go back to the stock recovery.The problem is that you installed something that modified you'r system (in my case i've installed using CWM the Google Now and some other stuff on it) and now the phone can't update because something is "messed up" in the system.You now have to restore and old backup in CWM,preferably one that doesn't have any mods in it.The recovery is good,otherwise it wouldn't work at all.
Click to expand...
Click to collapse
Well, I rooted my phone and installed CWM. so I did the unroot (as far as I know) and got the stock recovery, so what else could it be? :S
No,you didn't understand,this is not about the stock recovery.This is about the fact that you probably installed something (using CWM) that rewrited some files in the /system or other folders that this update depend on.Because those folders are modified the update doesn't recognize those apps and can't continue.That is what i am saying.Install the CWM again,search for any nandroid backups that you have on it and install the oldest one.I usualy make a nandroid backup everytime i update my phone because until the next update i keep installing stuff that messes up my ROM and in cases like yours i just apply the backup i've taken and voila,the update works.Also there is one app that messes up you'r system,it is called BusyBox,and if you install that app and want to make an update,the update will fail (red triangle) because of that app.
If you don't have any nandroid backups the only solution is to install the RUU.
jeyml said:
No,you didn't understand,this is not about the stock recovery.This is about the fact that you probably installed something (using CWM) that rewrited some files in the /system or other folders that this update depend on.Because those folders are modified the update doesn't recognize those apps and can't continue.That is what i am saying.Install the CWM again,search for any nandroid backups that you have on it and install the oldest one.I usualy make a nandroid backup everytime i update my phone because until the next update i keep installing stuff that messes up my ROM and in cases like yours i just apply the backup i've taken and voila,the update works.Also there is one app that messes up you'r system,it is called BusyBox,and if you install that app and want to make an update,the update will fail (red triangle) because of that app.
If you don't have any nandroid backups the only solution is to install the RUU.
Click to expand...
Click to collapse
Thanks for making it all clear I'll check if I've got a backup from when I formatted my phone (does root affect this process?)
And from what I understand, I can only install RUU that is the same as my phone's version or higher. right now I got 2.18, the TWM-TW version of the phone. know by any chance if there is an RUU for it?
The root should not affect the backup/restore proces as far as i know.Yes,the RUU must be the same as phone version or higher.Honestly i don't know any RUU for that,try searching for the new JB RUU.
EDIT:
Check you'r CID and download one of the stock nandroid backups here:
http://forum.xda-developers.com/showthread.php?t=1975140
Thanks for the nandroid, It will be my last resort if restoring a clean image won't help
and about the root - I meant if it's supposed to interfere with the update.
Thanks.
So let me get this straight. You don't have the RUU for your version at all?? and what recovery is installed right now???
No problem,if there are any other problems just ask.
@zainalabididn - I made a recovery image when i first rooted the phone (not when I first got it), but it still won't let me update over it - maybe because of the root. the recovery I'm using right now is CWM 5.8.4
@jeyml - I tried to install the nandroid in the link you gave me, but it wouldn't let me flash the hboot on my device, so after flashing the boot and nandroid it just went into loops of trying to start up, getting stuck and rebooting. got any idea why that happens? (notice: I don't have S-off, if that's what causing the problem)
Hey All,
Model: HTC One M8 - 0p6b160
CID: TELUS0001
Got a HTC One M8 the other day, I have already dev unlocked it via HTC, but I'm looking to have root and if possible s-off but stay on the stock image.
I've been wanting to backup the recovery image (since there seems to be very little resources for the TELUS001 CID) but from everything I've read this can only be done once you have root using adb and dd. To get root I need to install TWRP or PHILZ.
What I'm not clear about:
Are TWRP or PHILZ replacing the recovery image? Is there actually a way to backup recovery image? or did I miss something.
When TWRP/PHILZ do a backup is it just the current installed state of the phone?
Reading a post on another forum (can't post link cause I'm new) they talk about doing a temporary flash, but I didn't seem to be able to make that work using: fastboot boot twrp-m8-recovery.img
In the future I want to go to Android L, will any of this prevent it?
Thanks
felix2000 said:
Are TWRP or PHILZ replacing the recovery image? Is there actually a way to backup recovery image? or did I miss something.
When TWRP/PHILZ do a backup is it just the current installed state of the phone?
Reading a post on another forum (can't post link cause I'm new) they talk about doing a temporary flash, but I didn't seem to be able to make that work using: fastboot boot twrp-m8-recovery.img
In the future I want to go to Android L, will any of this prevent it?
Click to expand...
Click to collapse
1 and 3. You can backup stock recovery by booting into custom recovery that is located on your computer, instead of flashing custom recovery to the phone. This is already what you have described in Item 3. Is your phone in fastboot mode? The TWRP file is located in the same folder as fastboot.exe? Are you sure you have fastboot connectivity? To check this, type "fastboot devices" (with no quotes) and see if your device ID comes up.
Also, a great many stock recoveries are already posted here: http://forum.xda-developers.com/showthread.php?t=2701376
This thread also describes the process of backing up stock recovery via fastboot.
2. Not sure what you are asking. But yes, recovery can't backup something that isn't there (just current installed state).
4. Having custom recovery will prevent install of OTA, if that is what you mean. But return to stock recovery and restore any system files altered by root allows install of OTA. Or you can just install a custom ROM based on Android L when it comes out, as custom ROMs are sure to come quickly after L is available. Maybe even sooner than your version's OTA.
I've got an HTC One M9 (Rogers) that I've rooted and installed CM13 (13.0-20160221-nightly-himaul). I'm reasonably experienced with custom ROMs and such having played with all of this stuff on several Samsung devices (Captivate, Galaxy Nexus, SGS3), but this is my first go on an HTC device and first time running TWRP as opposed to Clockworkmod. I attempted to update my TWRP from 2.8.4 to 3.0.0-2 by booting to recovery. Not sure how and where I went wrong in that process but I can no longer boot to recovery, the phone starts up just fine and is usable. I can still access download mode and the bootloader, device is S-on (and has never been s-off). I have since attempted to reinstall TWRP via ADB commands as per the below post. The flash seems to take, no errors but still I'm unable to access recovery. I'm at somewhat of a loss as to what if anything I can try next.
http://forum.xda-developers.com/one-m9/general/guide-root-install-twrp-htc-one-m9-t3061133
the0f said:
I've got an HTC One M9 (Rogers) that I've rooted and installed CM13 (13.0-20160221-nightly-himaul). I'm reasonably experienced with custom ROMs and such having played with all of this stuff on several Samsung devices (Captivate, Galaxy Nexus, SGS3), but this is my first go on an HTC device and first time running TWRP as opposed to Clockworkmod. I attempted to update my TWRP from 2.8.4 to 3.0.0-2 by booting to recovery. Not sure how and where I went wrong in that process but I can no longer boot to recovery, the phone starts up just fine and is usable. I can still access download mode and the bootloader, device is S-on (and has never been s-off). I have since attempted to reinstall TWRP via ADB commands as per the below post. The flash seems to take, no errors but still I'm unable to access recovery. I'm at somewhat of a loss as to what if anything I can try next.
http://forum.xda-developers.com/one-m9/general/guide-root-install-twrp-htc-one-m9-t3061133
Click to expand...
Click to collapse
Are you running 3.x firmware? TWRP 3.0+ only works on firmware 3.x (i.e., the firmware that comes with Marshmallow). Flash TWRP 2.8x using fastboot and it should work just fine.
efrant said:
Are you running 3.x firmware? TWRP 3.0+ only works on firmware 3.x (i.e., the firmware that comes with Marshmallow). Flash TWRP 2.8x using fastboot and it should work just fine.
Click to expand...
Click to collapse
You sir are my hero, that definitely worked. So now to update that firmware so that I can update everything else. By chance do you know of a guide on how to update to that newer firmware version?
the0f said:
You sir are my hero, that definitely worked. So now to update that firmware so that I can update everything else. By chance do you know of a guide on how to update to that newer firmware version?
Click to expand...
Click to collapse
The only way I know how to do it with S-ON is to restore your device to stock (i.e., the version of stock before you flashed CM), take the OTA update, then flash the ROM you want.
efrant said:
The only way I know how to do it with S-ON is to restore your device to stock (i.e., the version of stock before you flashed CM), take the OTA update, then flash the ROM you want.
Click to expand...
Click to collapse
Sorry to be a bother and ask for any form of hand holding, but any idea where I can source the files for the return to stock? Currently have 2.11.631.2 on there (checked in the bootloader). Either that or a way to go S-OFF, I've been unable to find a guide on how to accomplish this without sunshine, which won't work on Cyanogenmod. If that required flashing even to something more similar to stock (IE Android Revolution) that's not the end of the world. Just kind of at a loss as to how to go about that process from where I am now.
the0f said:
Sorry to be a bother and ask for any form of hand holding, but any idea where I can source the files for the return to stock? Currently have 2.11.631.2 on there (checked in the bootloader). Either that or a way to go S-OFF, I've been unable to find a guide on how to accomplish this without sunshine, which won't work on Cyanogenmod. If that required flashing even to something more similar to stock (IE Android Revolution) that's not the end of the world. Just kind of at a loss as to how to go about that process from where I am now.
Click to expand...
Click to collapse
1) Make sure you have an sdcard formatted exfat in your device.
2) Boot into TWRP and back up your boot image to the sdcard. (You are doing this to get TWRP to create the proper directory structure.)
3) Find your back up that you just created and delete the files in the folder, i.e., the boot image and the md5 file.
4) Make sure TWRP has the option to keep system read-only checked (in the mounts menu).
5) Go here and download the three files (boot, recovery, system_image) for 2.11.631.2 and place them in the folder on your sdcard mentioned in point #3 above.
6) Restore the files using TWRP and reboot your device into Android.
7) You'll get an OTA notification. Accept it and update your device. (It'll take a while and reboot multiple times.)
8) Once updated, you'll get a second OTA notification to update you to Marshmallow. Accept it and update your device. (It'll take a while and reboot multiple times.)
9) Once updated, you can go ahead and flash TWRP 3.0+ and do what you want.
http://forum.xda-developers.com/one-m9/general/guide-return-to-stock-canadian-htc-one-t3108236
efrant said:
1) Make sure you have an sdcard formatted exfat in your device.
2) Boot into TWRP and back up your boot image to the sdcard. (You are doing this to get TWRP to create the proper directory structure.)
3) Find your back up that you just created and delete the files in the folder, i.e., the boot image and the md5 file.
4) Make sure TWRP has the option to keep system read-only checked (in the mounts menu).
5) Go here and download the three files (boot, recovery, system_image) for 2.11.631.2 and place them in the folder on your sdcard mentioned in point #3 above.
6) Restore the files using TWRP and reboot your device into Android.
7) You'll get an OTA notification. Accept it and update your device. (It'll take a while and reboot multiple times.)
8) Once updated, you'll get a second OTA notification to update you to Marshmallow. Accept it and update your device. (It'll take a while and reboot multiple times.)
9) Once updated, you can go ahead and flash TWRP 3.0+ and do what you want.
http://forum.xda-developers.com/one-m9/general/guide-return-to-stock-canadian-htc-one-t3108236
Click to expand...
Click to collapse
Thank you again sir, I'll give that a try this evening when I get back home. The help and the hand holding is very much appreciated. I thought that I knew a fair bit about android phones and custom ROMs from my time with my old Samsung devices, and have had to do a lot of learning when it's come to the One M9. Never had a device with the S-ON feature before and have had a lot of trouble trying to find info on what I need to do. I did find that forum post you linked, but wasn't sure if that applied to my device or not. Again VERY much appreciated.
Yup, 6.0 stock is installed and working, TWRP 3.0.0-2 installed and working as well. This time took a system backup and stored it in a safe place (as I expect much the same trouble when Android N or any other major update happens). Thank you again for all of your assistance in getting my phone fixed and updated.
Hi All;
I've been a lurker for a while, now need further help. My mate has patiently drilled into my head to read XDA to the death, but I'm still stuck. In the last 4 days I've learnt;
-Bootloaders, fastboots, recoverys, TWRP's, stock's, OTAs, custom ROMs, md5's, MID's CID's, and all of that juicy stuff.
Currently my network unlocked M8 is stuck on Lollipop and has an error when attempting to activate the OTA for MM;
(stock recovery screen; )
Code:
"Installing update...
M60QCT.01.002.018
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: Device or resource busy
E:unknown command [set_err_msg]
Package expects build fingerprint of htc/telstra_wwe/htc_m8:5.0.01/LRX22C/457188.[B]9[/B]:user/release-keys or htc/telstra_wwe/tc_m8:6.0/MRA58K/663331.4:user/release-keys; this device has htc/telstra_wwe/htc_m8:5.0.1/LRX22C/457188.[B]5[/B]:user/release-keys.
E:Error in /data/data/com.android.providers.downloads/app_fota/OTA_M8_UL_M60_SENSE70_MR_Telstra_WWE_6.12.841.4-4.19.841.9_release_464352013pnx3icht129py.zip
(Status 7)
Installation aborted."
[note the single number difference in bold]
Here's what gets me confused. Orignally this phone was rooted with Lollipop and I lived with it for some time. I decided I wanted MM so my friend showed this XDA post; and it worked perfectly fine the first time (last friday). I then attempted to add TWRP to the phone which worked, and then when I hit the button in TWRP recovery "your phone is not rooted, do you want to root and install SuperSU" it all went to hell after that.
The OS froze at the HTC boot screen and since then I have tried;
--the above procedure exactly to each step and it gets the above typed error at the OTA MM install.
--Restoring MM from the above post links and its stock recovery, but during TWRP restoring of MM, it has a different error.
--Installing Original Lollipop 4.19.841.9 and stock recovery repeatedly, after clearing caches, wiping this and that...
--Attempting to change the "updater-script" file by deleting the assert / getprop line that does the check, has md5 error when installing with TWRP and stock recovery/OS says it's modified, do you want to re-download etc
Currently I'm out of ideas. I honestly don't know what to do. Any suggestions would be much appreciated, I understand you are going to ask for build details etc, so I'll type them below and hope it's enough information.
I'd like to save the current internal storage data but if not, so be it. I'm not actually sure what the "system" and "data" backup from TWRP actually saves. Every time I "wipe" the Boot, System and Data in TWRP, the phone data is still there (such as downloaded images/files). Is it the same data?
Any help or support would greatly be appreciated. Ideally I would like to have the phone on HTC MM rooted, and would like to keep up with OTA's but that's Ron's problem (later on).
Thanks for your help!
--matticas
android
5.0.1
software number
4.19.841.5
kernel version
3.4.0-g3c7a5c1
[email protected] #1
baseband version
1.26.214500021.24G_20.69.4196t.01_F
build number
4.19.841.5 CL457188 release-keys
teamwin recovery project
2.7.0.2
(also using TWRP-2.8.7.0)
CID = TELST001
MID = 0P6B11000
1. Never use TWRP 2.7.0.2 - use 2.8.7.0 or later, never accept root offered by TWRP.
2. The error clearly stated OTA expects 4.19.841.9 stock recovery (457188.9) or 6.12.841.4 stock recovery (663331.4) but you installed 4.19.841.5 stock recovery (457188.5).
Try again with correct stock recovery 4.19.841.9
3.Tips:
If you restore 4.19.841.5 backup must install 4.19.841.5 or 4.19.841.9 stock recovery
If you restore 4.19.841.9 backup must install 4.19.841.9 or 6.12.841.4 stock recovery
(always same or one version higher)
4. What's the OS- no. on the bootloader. Maybe you already on MM firmware. If you want to root it, download and install SuperSU-2.76 (don't accept the one offered by TWRP)
5. If your current firmware is MM, restore MM backup with TWRP 2.8.7.0 or later. It won't work with TWRP 2.7.0.2 (again don't accept root offered by TWRP)
ckpv5 said:
1. Never use TWRP 2.7.0.2 - use 2.8.7.0 or later, never accept root offered by TWRP.
2. The error clearly stated OTA expects 4.19.841.9 stock recovery (457188.9) or 6.12.841.4 stock recovery (663331.4) but you installed 4.19.841.5 stock recovery (457188.5).
Try again with correct stock recovery 4.19.841.9
3.Tips:
If you restore 4.19.841.5 backup must install 4.19.841.5 or 4.19.841.9 stock recovery
If you restore 4.19.841.9 backup must install 4.19.841.9 or 6.12.841.4 stock recovery
(always same or one version higher)
4. What's the OS- no. on the bootloader. Maybe you already on MM firmware. If you want to root it, download and install SuperSU-2.76 (don't accept the one offered by TWRP)
5. If your current firmware is MM, restore MM backup with TWRP 2.8.7.0 or later. It won't work with TWRP 2.7.0.2 (again don't accept root offered by TWRP)
Click to expand...
Click to collapse
Hi ckpv5;
1; roger that, 2.8.7.0, got it.
2; thanks for explaining what the other numbers meant. Does this mean (for my purpose of learning more) normal non-played with phones (aka general public) the OTA updates the recovery for them? Why didn't it work in this case or is it because in fastboot it knows it's "Modified"?? FYI tried to take the MM-OTA with 4.19.814.9 recovery, no luck, it didn't show an error, it just attempted to install the OTA, failed, and booted the OS back up. Tried with the 6.12.814.4 recovery, and now it appears to be working, I have a percentage number increasing which I haven't seen since it first worked.
3; Roger that, mine seems out of whack.
4; How do I find the OS number on the bootloader? Is that in the fastboot menu? from memory I saw a number 6.24.814.4 ??? I questioned that also but thought nothing of it - I'll reply in the morning once the phone finishes updating (need to sleep shortly).
So far I understand 3 components; OS = the main disto, lollipop, MM etc. Recovery = the other mini-OS that fixes things, TWRP, Cyanogenmod (sp?), stock etc. Bootloader is like the Grub. What's the firmware do? Is that the part that drivers the basic hardware?
5: will see how this one goes, restore every thing, then work on getting TWRP back on and root after that.
Thanks so much for your help, I was out of ideas and very over it, just wanted the phone back!
--matticas
Ok update, the percentage number increased, rebooted, percentage came back, rebooted quickly, then froze on the HTC splash screen.
I jumped into fastboot, OS=6.24.841.1
this is firmware i need to change?? What's the best order to do this in??
Thanks again...
matticas said:
I jumped into fastboot, OS=6.24.841.1
Click to expand...
Click to collapse
That's your current firmware. You should restore this version 6.24.841.1 if there is one (I don't have this one in my collection as I thought no one ever need it, I will upload the 6.24.841.1 backup this weekend when I'm home).
The best that you can do now is restore one version lower backup i.e 6.12.841.4 and install 6.12.841.4 stock recovery ( if you don't have 6.24.841.1 backup) then OTA to 6.24.841.1
Usually when restoring more than one version lower like 4.19.841.5 or 4.19.841.9, may not work due to firmware is too high version and it get stuck when it tries to install firmware (unless your device is S-Off, it can accept any firmware version)
ckpv5 said:
That's your current firmware. You should restore this version 6.24.841.1 if there is one (I don't have this one in my collection as I thought no one ever need it, I will upload the 6.24.841.1 backup this weekend when I'm home).
The best that you can do now is restore one version lower backup i.e 6.12.841.4 and install 6.12.841.4 stock recovery ( if you don't have 6.24.841.1 backup) then OTA to 6.24.841.1
Usually when restoring more than one version lower like 4.19.841.5 or 4.19.841.9, may not work due to firmware is too high version and it get stuck when it tries to install firmware (unless your device is S-Off, it can accept any firmware version)
Click to expand...
Click to collapse
Just realised I have firmware .1 not .4
Was worried last night when it didn't work following the instructions; failed the first time fine, but also failed the second time...
I'll wait for the .1 release if you have it. Thanks!!
Edit; mine is S-On
6.24.841.1 backup & recovery added to my thread : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
ckpv5 said:
6.24.841.1 backup & recovery added to my thread : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Click to expand...
Click to collapse
Downloading the stock recovery and stock OS now, ... I'll load them up and see what happens...!
Thanks very much... I'll update once something happens...
Annnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnd it's back!!
Thank you so much ckpv5!!!!
Downloaded your stock recovery and OS.
Launched TeamWin Recovery; mounted phone as USB, copied the OS over.
Wiped existing install.
Restore the new 6.24.814.1
Rebooted the bootloader, did NOT install the SuperSU
Bootloader then to fastboot
fastboot and flashed over the stock recovery.
reboot.
Phone working on Marshmallow again!!!
I'm happy to have it back.
Will let all the apps and software restore itself, then I'll remove the countless other backups and restores, make a latest fresh one.
Then TeamWin 2.8.7.0
Then use TeamWin to install SuperSU-2.76 (which should root as I understand?)
then I'm where I want to be! Marshmallow and rooted.
Thanks again, it's been a great learning curve!
--Matticas
matticas said:
then I'm where I want to be! Marshmallow and rooted.
Click to expand...
Click to collapse
If this is your target, you don't need to flash stock recovery after you restore the backup, so you don't have to reflash TWRP
I suggest to use TWRP 3.0.2-0 because using TWRP 2.8.7.0, you may accidently swipe to root with and outdated root offered by TWRP (unless you be careful then it's ok)
Installing SuperSU alone may not get you fully rooted (when on S-On) due to stock kernel is system write protection enabled. You need module to disable write protection to get full root.
You can install a custom kernel like ElementalX which is write protection disabled by default.
Personally I'm on this one - http://forum.xda-developers.com/showpost.php?p=66053720&postcount=778 when I'm running MM Sense ROM.
ckpv5 said:
If this is your target, you don't need to flash stock recovery after you restore the backup, so you don't have to reflash TWRP
I suggest to use TWRP 3.0.2-0 because using TWRP 2.8.7.0, you may accidently swipe to root with and outdated root offered by TWRP (unless you be careful then it's ok)
Installing SuperSU alone may not get you fully rooted (when on S-On) due to stock kernel is system write protection enabled. You need module to disable write protection to get full root.
You can install a custom kernel like ElementalX which is write protection disabled by default.
Personally I'm on this one - http://forum.xda-developers.com/showpost.php?p=66053720&postcount=778 when I'm running MM Sense ROM.
Click to expand...
Click to collapse
Ooooo more stuff to learn... Give me a few days to sort my phone out before backup then I'll start reading again.
Will go with that version of TeamWin.
What's the difference between the SuperSu-2.76.zip root and the custom kernel?? Further access to apps and system files or something else??
Is the custom kernel easy to roll back from? I'm thinking forward to more OTA's and easierly going stock to receive them...
matticas said:
Ooooo more stuff to learn... Give me a few days to sort my phone out before backup then I'll start reading again.
Will go with that version of TeamWin.
What's the difference between the SuperSu-2.76.zip root and the custom kernel?? Further access to apps and system files or something else??
Is the custom kernel easy to roll back from? I'm thinking forward to more OTA's and easierly going stock to receive them...
Click to expand...
Click to collapse
You need both custom kernel and SuperSu-2.76.zip.
If only SuperSu-2.76.zip, you make changes to system files, the system will revert the changes after reboot.
SuperSu-2.76.zip gives you root access to system files.
Custom kernel allow you to write/modified system files.
Make a nandroid backup (or use mine) before you modified it like installing SuperSu-2.76.zip and install custom kernel.
OTA will need a non-rooted ROM with all system file intact, if not, the OTA will fail. So when there is OTA, restore only boot & system part from the non-rooted backup and proceed for OTA after you install matching stock recovery
Anyway, I doubt there will be any further OTA as M8 is already more that 2 years old and HTC stop support after 2 years.
OK, I have a major problem/possibly problems.
I was running Stock on 1.80.something and flashed the latest LeeDroid ROM, not mentally registering that Lee is on 1.92. Naturally there were some quirks, so I wanted to restore the 1.80 untouched Stock so that I could download and install the 1.92 OTA and move to Lee and other custom ROMs. I understand to do that I have to flash back to Stock Recovery so that I can get the 1.92 OTA since otherwise it fails to install on my phone (I have an unlocked bootloader, root and TWRP). I have yet to successfully do that, though.
I booted into TWRP and wiped Lee since I didn't need it and since I had recoveries. I then flashed the 1.80.709.1 Stock Recovery image from topjohnwu's Stock Backups/Recovery/OTA/RUU repository and booted to it, however, it didn't like any of the 1.80 Untouched System Images I tried to flash from that repository. So, I reflashed TWRP with the adb console thinking I would restore a backup and deal with this another day when I'm not so tired.
For some reason the TWRP Restore menu now only lets me select one item ("DATE"_MMB29M_release-keys), even though I have two other backups. I'm missing the "Up a level" button that lets me pick a different folder, so I can't pick a different backup. Flashing this only available backup gives me the error "Cannot restore system -- mounted read only." Trying to install one of the 1.80 zips from the repository gives me errors saying that it "Could not find 'META-INF/com/google/android/update-binary' " in the zip file. I can only install LeeDroid on a firmware that's too high for my phone.
Any suggestions about what to do? I currently have no OS on my phone and download mode tells me the OS is 1.80.617.1. I apologize for my profuse stupidity on this. I used TWRP fairly frequently with my LG G3, but having to flash Stock Recovery for OTAs on the HTC 10 after a long day adds a whole new layer of complication.
Thanks in advance!
Are you S-off? if yes you can flash 1.9X firmware in DL mode to be able to boot LeeDroid.
macschwag14 said:
OK, I have a major problem/possibly problems.
I was running Stock on 1.80.something and flashed the latest LeeDroid ROM, not mentally registering that Lee is on 1.92. Naturally there were some quirks, so I wanted to restore the 1.80 untouched Stock so that I could download and install the 1.92 OTA and move to Lee and other custom ROMs. I understand to do that I have to flash back to Stock Recovery so that I can get the 1.92 OTA since otherwise it fails to install on my phone (I have an unlocked bootloader, root and TWRP). I have yet to successfully do that, though.
I booted into TWRP and wiped Lee since I didn't need it and since I had recoveries. I then flashed the 1.80.709.1 Stock Recovery image from topjohnwu's Stock Backups/Recovery/OTA/RUU repository and booted to it, however, it didn't like any of the 1.80 Untouched System Images I tried to flash from that repository. So, I reflashed TWRP with the adb console thinking I would restore a backup and deal with this another day when I'm not so tired.
For some reason the TWRP Restore menu now only lets me select one item ("DATE"_MMB29M_release-keys), even though I have two other backups. I'm missing the "Up a level" button that lets me pick a different folder, so I can't pick a different backup. Flashing this only available backup gives me the error "Cannot restore system -- mounted read only." Trying to install one of the 1.80 zips from the repository gives me errors saying that it "Could not find 'META-INF/com/google/android/update-binary' " in the zip file. I can only install LeeDroid on a firmware that's too high for my phone.
Any suggestions about what to do? I currently have no OS on my phone and download mode tells me the OS is 1.80.617.1. I apologize for my profuse stupidity on this. I used TWRP fairly frequently with my LG G3, but having to flash Stock Recovery for OTAs on the HTC 10 after a long day adds a whole new layer of complication.
Thanks in advance!
Click to expand...
Click to collapse
You are flashing wrong files for your phone. What is you cid and mid? It says your os is 1.80.617 but yoy are trying to flash 1.80.709 recover. The 3rd numbers are important that is a region code. Also Leedoid is based on. WWE 1.95.401. If i was you i would flash the RUU that is for your cid and mid and start over.
It seems that you are on US unlocked. If you search you will find an ruu zip for 1.91.617.1
Thanks for the replies. I'm unable to find my CID and MID. Download mode doesn't show either, and the using the adb console commands to show them only gives me the message "waiting for a device" in the console window.
I don't have S-OFF (yet). Should I install the 1.91.617.1 RUU via PC or should I first buy S-OFF and then install the RUU?
macschwag14 said:
Thanks for the replies. I'm unable to find my CID and MID. Download mode doesn't show either, and the using the adb console commands to show them only gives me the message "waiting for a device" in the console window.
I don't have S-OFF (yet). Should I install the 1.91.617.1 RUU via PC or should I first buy S-OFF and then install the RUU?
Click to expand...
Click to collapse
Install the RUU via pc or find the ruu zip and flash in download mode by renaming the zip to 2PS6IMG.zip you dont need SOFF to flash RUU.also remember it will erase your internal storage.
Thanks everyone! I installed RUU 1.91.617.1 and seem to be running smoothly now. I still can't see any other backups on in the TWRP Restore menu and don't have the Up a level button that lets me pick a different directory on my SD card. Any ideas about that?