Related
Hi everyone,
I'm using a HTC Wildfire and am considering changing from stock (HTC non-branded) to CyanogenMod for a number of minor reasons. Could anyone just confirm that I got a few points right before I get started:
- Recovery is totally independent from the ROM itself, right? So I can flash ClockWorkMod Recovery only, continue to use the stock ROM, but have the additional features of ClockWorkMod available, such as backup, with which I can create a complete backup of the stock ROM. In case I don't like CyanogenMod, I can restore the stock image and be exactly where I left it, Apps, Settings and everything (of course the new Recovery will still be installed.) Is this correct?
- I'm planning to do the following steps (I read about the details, just want to confirm the basics):
x use the Revolutionary way to S-OFF and install new Recovery
x create full image backup of the stock ROM using the new Recovery
x install new ROM (ClockWorkMod)
x if I don't like CM: restore image created before to return to stock
-> This should work, shouldn't it?
- One more: What will happen if the the phone is S-OFF, an alternative Recovery is installed, and a HTC Firmware-Update is attempted? Will this work at all, will it update just the ROM, or will it update the Recovery, too? S-OFF will not be changed back to S-ON, right?
Thanks for your help.
Regards
1. Yes, the recovery is in it's own partition and is independent from the ROM
2. The recovery creates a "snapshot" of your current ROM. So when you restore, it'll be just the way you left it.
3. There's no need to do any HTC Firmware updates after installing a custom ROM (infact, I'm almost 100% sure that it won't work)
As a basic answer yes you go ahead with what you posted.just make sure your hboot version is compatible with revolutionary 1st etc etc.
As for HTC firmware update question,if your talking about the over the air updates I'm not sure but I think it would update your hboot thus reverting back to s-on status again so best not accept it if you do get one (turn off in settings)
Edit : ninja'd lol
Sent from my HTC Wildfire using XDA App
slymobi said:
As a basic answer yes you go ahead with what you posted.just make sure your hboot version is compatible with revolutionary 1st etc etc.
Click to expand...
Click to collapse
Yes, of course.
As for HTC firmware update question,if your talking about the over the air updates [...]
Click to expand...
Click to collapse
No, the manual ones you can download directly from HTC and install via USB. My understanding was that this would kill everything flashable, including radio and recovery. It would be reassuring to have a worst-case way to go back to stock in case the image-restore fails for whatever reason.
150d said:
Yes, of course.
No, the manual ones you can download directly from HTC and install via USB. My understanding was that this would kill everything flashable, including radio and recovery. It would be reassuring to have a worst-case way to go back to stock in case the image-restore fails for whatever reason.
Click to expand...
Click to collapse
Ah sorry never dealt with any firmware updates. There are ruu.exe to help get back to stock if something goes wrong I think.
Sent from my HTC Wildfire using XDA App
You can go completely back to stock, s-on and all but believe me once you have cwm installed there really is no point unless its for warranty reasons, backup fails are rare with the latest recoveries + if it does fail with your first backup you can always post here and we will explain how to extract a stock Rom from an ruu to put things back to how they where before or you can flash a custom sense Rom and modify it to your liking.
Sent from my HTC Wildfire using xda premium
Scratch0805 said:
You can go completely back to stock, s-on and all
Click to expand...
Click to collapse
That's great.
[...] but believe me once you have cwm installed there really is no point unless its for warranty reasons[...]
Click to expand...
Click to collapse
Yea, exactly. I'm a little on the paranoid side, I know... ;-)
Ok, I'm on my way now. I've performed the "Revolutionary" S-OFF and am now running "Revolutionary CWM v4.0.1.4". Is this an out-of-date version?
I've read about ROM-Manager being able to auto-check for and flash a new Clockworks Recovery, but I've also read that ROM-Manager needs root. I have not yet flashed a new ROM, so I assume that I'm not yet rooted, am I? Can I find a ZIP of CWM that I can directly flash from the SD-card?
Does the CWM-version I'm running have any effect on the "quality" of the image backup? In other words, if I create a backup now, will I be able to restore it later running a different version of CWM?
The "different version backup restore" is a bit wonky and won't always work.
To flash a different recovery from the SD card do this:
1. Place this file on your SD card (Not in any folders!): http://www.multiupload.com/74EW2VPNHL
2. Boot into the bootloader
3. Wait a bit and then it should prompt you to update
4. Click the volume+ key to update
5. Remove SD card
6. Boot into the new recovery and insert the SD card
7. Go under mounts and select Mount USB storage
8. Delete the PCIMG file from your computer
nejc121 said:
1. Place this file on your SD card (Not in any folders!): http://www.multiupload.com/74EW2VPNHL
Click to expand...
Click to collapse
I tried to, but I couldn't use the link. The whole domain seems to be down - maybe another holy crusade of Big Content, who knows. They sure leave fans in their wake, don't they.
Since you indicated that updating would be ok for the wildfire I went to http://www.clockworkmod.com/rommanager and downloaded the file recovery-clockwork-5.0.2.0-buzz.zip.
However, I'm not sure how to handle it: If I put it on the card under this name, nothing happens on bootloader-start. In recovery, I can select the file and install it, and then I immidiatly get a newly colored menu with the new CWM version 5.something. However, once I restart, the old CWM (v4.x) is there again.
I assume I need to use a magic filename so that the bootloader performs the update, not the (already running) recovery. Right?
**EDIT: Ah, disregard. I believe I found the answer myself.
Do you have fastboot?
If you do I can give you the recovery.img I'm using, which you can flash via fastboot.
Yes, fastboot is available.
Thank you.
Okay, here's how you flash a recovery via fastboot.
1. Extract the .zip I attached to the location where you fastboot is
2. Reboot phone in the bootloader
3. Select fastboot and attach USB cable
4. Open up the command prompt and type in "cd [location of fastboot]
5. Type in "fastboot flash recovery recovery.img"
6. You're done
Oh and by [location of fastboot] I mean that you type in the location of fastboot.
Wow - this was fun. There was something really curious going on with my device: Whatever I tried, no "official" way worked to modify CWM v4 to v5. In every case, the menu of the new version showed up and was usable, but was gone again after restart. After the file-on-card method got me nowhere (file was not recognized), I tried the high road and installed ROM-Manager. This complained about missing su. So I installed su. After that ROM-Manager downloaded CWM v5 and put it onto the card (into a file named update.zip - ahh... ) On restart, the CWM-install-screen came up, then the v5 menu.
And after restart, it was gone again. Even ROM-Manager was confused: He showed v5 as "installed", when in fact it was still v4. ;-)
So finally I downloaded the Android SDK (to get fastboot.exe) and performed the flash as you suggested in the first place. And it worked. First try, without hitch, permanently.
Thank you very much for your help!
Regards
The problem with ROM Manager's version is that it's only temporary and can only be accessed from the ROM Manager itself
I want to be able to flash my stock recovery when I no longer want TWRP or CWM. How would I go about doing this?
tcmoffitt said:
I want to be able to flash my stock recovery when I no longer want TWRP or CWM. How would I go about doing this?
Click to expand...
Click to collapse
Hello,
Thanks for using XDA Assist.
What device do you have?
___
v7
XDA Assist
v7 said:
Hello,
Thanks for using XDA Assist.
What device do you have?
___
v7
XDA Assist
Click to expand...
Click to collapse
HTC One m8 Tmobile
Thanks for the help guys I really appreciate it. This forum is just so helpful............. ---____---
Which T-Mobile ?
If it is T-Mob US .. there's a dedicated section for T-Mob US and you can find any info there.
tcmoffitt said:
Thanks for the help guys I really appreciate it. This forum is just so helpful............. ---____---
Click to expand...
Click to collapse
This is not possible to backup your stock recovery. When you need that you can download it simply (base on your phone's build number). Also you can extract stock recovery frome your ota zip update(the file with img format inside of firmware folder)
Arsinn said:
This is not possible to backup your stock recovery.
Click to expand...
Click to collapse
Actually, the following usually works:
This has to be done before flashing custom recovery. Unlock bootloader, then fastboot boot recovery.img
With "recovery.img" being a TWRP file located in your fasboot folder. This will boot into TWRP without actually flashing it. From there, you can pick recovery in the backup options, to backup stock recovery.
But yes, I agree that stock recovery images are pretty easy to obtain from these forums, or extracting from a OTA or ROM.zip.
redpoint73 said:
Actually, the following usually works:
This has to be done before flashing custom recovery. Unlock bootloader, then fastboot boot recovery.img
With "recovery.img" being a TWRP file located in your fasboot folder. This will boot into TWRP without actually flashing it. From there, you can pick recovery in the backup options, to backup stock recovery.
But yes, I agree that stock recovery images are pretty easy to obtain from these forums, or extracting from a OTA or ROM.zip.
Click to expand...
Click to collapse
Hi, redpoint73...
Maybe I'm missing something here, but I'm not seeing an option to backup the Recovery in TWRP 2.8.7.0... Just Boot, Cache, System, Data and Android Secure are available (see attached screenshot). I remote booted TWRP from my laptop, as I did when I rooted Marshmallow around a fortnight ago, in order to keep the stock recovery intact.
It would certainly be useful to be able to backup the stock recovery via TWRP... I just haven't found a way of accomplishing it .
-----
But a possible option to backup the stock recovery would be to use the Flashify app...
Remote boot TWRP from your PC, acquire root, and then run Flashify...
Flashify PlayStore link...
https://play.google.com/store/apps/details?id=com.cgollner.flashify
XDA discussion thread...
http://forum.xda-developers.com/showthread.php?t=2349847
This app uses <dd=if/of> commands to backup and potentially restore the boot and/or recovery images.
Although it does require root to work.
I've used Flashify on my Nexus 7 and Nexus 9 in the past, but never on my M8, except to backup... never to restore, so I cannot personally vouch for it's safety on the M8.
-----
What I'm unsure of about Flashify...
@redpoint73, @ckpv5, maybe you guys could shed some light on this...
Would such a <dd=if/of> created backup of stock recovery be flashable via fastboot?
And would it be safe to do so?
I know that TWRP uses <dd=if/of> commands, having looked through TWRPs logs... but I'm not quite sure how fastboot works when it comes to flashing stuff, and I'm very wary about doing it myself or recommending it for others.
Normally, you'd just use the Flashify app to restore any recovery/boot.img backups you've previously made...
But Flashify requires root to work, and with an unrooted system, this is isn't viable. So could one use fastboot in the normal way to flash such a previously made backup of the stock recovery?
-----
Anyhow, it's not critical at the moment for me, because I've not flashed TWRP to my M8, my stock recovery remains intact.
-----
I would recommend anybody reading this seeking to root their Marshmallow M8 to just remote boot TWRP from their PC with fastboot boot twrp.img (ie., don't actually flash it), perform an unrooted Nandroid backup first...
...and then flash Chainfire in the usual way.
This leaves the stock recovery intact, which will be required for future OTAs.
And there still might be some...
My Nexus 9 receives monthly security patches from Google (probably after the StageFright debacle of last year), and it may well be that the M8 will also continue to receive security patches, despite it being nearly two years old.
So you need to be ready... with an unrooted/untouched Nandroid of your own creation and the stock recovery.
I know that Chainfires systemless root method is supposed to address this issue, but if you're going to mess with system, you should have a Nandroid backup anyway...
...just in case.
Rgrds,
Ged.
Funny, I use the fastboot boot option to boot into TWRP saving my original recovery.
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.
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
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?