Hi there,
I had a quick question on my issue.
I found my appropriate file to flash and loaded it in the twrp-backup folder and flashed. Then used the hassoon2000 program to close the bootloader. I was already S-on. Used the program to close the bootloader. Now the bootloader says relocked in red. Rebooted and started up. Everything works great. I'm with Rogers and emmidiately it says an update is available. After I download it asks if I want to flash. It unzips and reboots to the bootloader. What is the next step? I'm also wondering why I'm in the bootloader. Shouldn't it just reboot and finish the upgrade?
I'm convinced there's an issue.
Is there something I should change.
I'm lost. Any help would be appreciated.
Being a tester for Viper as stated in your signature, you shouldn't make this silly mistake.
Don't relock bootloader .. not needed at all and a hassle for you to fix problems.
You need non-rooted backup & stock recovery to update.
Read how-to and files needed in my thread linked in my signature.
You need to unlock bootloader again to fix it.
Its been a year and a half since I tweaked anything on my phone. Viper has been solid but wanted to upgrade to marshmellow then install newer vipper. Anyways, thats just the back ground reasons.
If I open the bootloader ( I'll have to search for this step as I'm sure using the "open bootloader" option in Hassoon's program would require many more steps) the update would take me to recovery. I spent hours searching through folders trying to find the OTA to install with no luck.
Don't use tools...
1. Unlock bootloader with unlock_code bin that you should already have. If no, request again from htcdev
2. Install TWRP
3. Restore non-rooted nandroid backup for your current firmware.
What's your current firmware ?
4. Install current firmware stock recovery
5. Do OTA checking, download & install
You won't find the OTA file after you already tried to install it .. it will be removed by the system after you tried to update (and failed)
ckpv5 said:
Don't use tools...
1. Unlock bootloader with unlock_code bin that you should already have. If no, request again from htcdev
2. Install TWRP
3. Restore non-rooted nandroid backup for your current firmware.
What's your current firmware ?
4. Install current firmware stock recovery
5. Do OTA checking, download & install
You won't find the OTA file after you already tried to install it .. it will be removed by the system after you tried to update (and failed)
Click to expand...
Click to collapse
Again I apprecoate the insight into this. I did some reading and it looks like the tool kit hasn't been updated in a few years. I followed your link/page and went through the unlock with htcdev. It said successful and they were emailing me the code and further instructions. That was originally 12hrs ago. I redid it about 3hrs ago but again still waiting on the email( I did check the spam folder but still nothing.
As for previous firmware, I have:
CID Rogers_001
Version main(OS) 4.20.631.2
HBoot 3.19.0.0000
I was just thinking, maybe its a different token number each attempt. So again I redid the process. Now I wait. I've also looked at my account in the htcdev and it is correct. This is strange.
Sometime it happens the delay.
If I remember correctly, I have RUU for your current version. If there is, while waiting for the unlock_code.bin, you can run RUU for a fresh system and do OTA up to Marshmallow.
Then you can unlock bootloader to install your favorite ROM.
I'm already in bed, I'll check my hdisk tomorrow and upload for you
I assume your device is S-On, if it is S-Off you don't need the unlock code to unlock bootloader.
Am I right about the device is S-On. I hope I am wrong then it's easier to fix it.
ckpv5 said:
Sometime it happens the delay.
If I remember correctly, I have RUU for your current version. If there is, while waiting for the unlock_code.bin, you can run RUU for a fresh system and do OTA up to Marshmallow.
Then you can unlock bootloader to install your favorite ROM.
I'm already in bed, I'll check my hdisk tomorrow and upload for you
I assume your device is S-On, if it is S-Off you don't need the unlock code to unlock bootloader.
Am I right about the device is S-On. I hope I am wrong then it's easier to fix it.
Click to expand...
Click to collapse
You are correct as its still S-On. I had to redo my registration as my old account didn't have all the Capitals, hexadecimal stuff the latest user name/passwords require. but after that the email came through and I'm back to being unlocked. If you stumble on the RUU I'd very very thankful for the copy. In the meantime I'll look up the RUU and the install. chances are this is what your thread is all about.
Splitshot said:
I'm back to being unlocked. If you stumble on the RUU I'd very very thankful for the copy. In the meantime I'll look up the RUU and the install. chances are this is what your thread is all about.
Click to expand...
Click to collapse
No .. my thread is not about RUU but nandroid backup. You don't need the RUU when your target is to have Marshmallow firmware and install custom ROM ..
Now the bootloader is unlocked and you have the unlock_code, the fastest method for you is:
Restore directly Marshmallow nandroid 6.13.631.7 (instead of going for OTA) then relock bootloader and install 6.13.631.7 signed firmware.zip .. reboot.
After all setup done .. you can unlock bootloader, reboot .. after setup is completed, install latest TWRP and install your favorite custom ROM.
The usual method :
Restore 4.20.631.3 backup (yes, not 4.20.631.2 backup), install 4.20.631.3 stock recovery - reboot - setup - check OTA - download and install 6.13.631.7 OTA. Once completed, install latest TWRP and install your favorite custom ROM.
The usual method is better, no hassle of relocking and unlocking bootloader.
followed your procedures but after downloading the marshmallow update it unzips and reboots to the install part after about 1 minute it reboots to factory recovery. is there a step here? because I wiped twrp before restoring the 4.20.631.3 file I have no twrp( That's what I'm familiar with not this factory recovery).
Make sure you install either 4.20.631.3 or 6.13.631.7 stock recovery.
When it stops in recovery, there's an error log on why it stops.
But it never stops in recovery, if there is error, it will boot to bootloader or reboot back to system without installing update.
ckpv5 said:
Make sure you install either 4.20.631.3 or 6.13.631.7 stock recovery.
When it stops in recovery, there's an error log on why it stops.
But it never stops in recovery, if there is error, it will boot to bootloader or reboot back to system without installing update.
Click to expand...
Click to collapse
So if I reDL your 4.20.631.3 and place it back into twrp/backups/phone serial/ and get back into the factory recovery would I be able to restore from here? I don't remember there being a restore option only install.
Or is my only option now to reinstall twrp and go through the paces a 2nd time?
I asked you to 4.20.631.3 or 6.13.631.7 stock recovery, what it got to do with redownload 4.20.631.3 (which I believe you refer to nandroid backup)
Nandroid & stock recovery are two different thing.
There is no need to redo the process of restoring 4.20.631.3 nandroid (if it was done correctly) .. just make sure 4.20.631.3 or 6.13.631.7 stock recovery is installed, not any other version.
Reboot, check OTA, download and select install now. The system will boot to RUU mode to install the update .. it won't go to recovery (that's why I don't understand your above post saying it stop in recovery - no manual installation too)
Read the How-To all the 14 steps and tick what you have done so you'll know that you don't skip any step
ckpv5 said:
I asked you to 4.20.631.3 or 6.13.631.7 stock recovery, what it got to do with redownload 4.20.631.3 (which I believe you refer to nandroid backup)
Nandroid & stock recovery are two different thing.
There is no need to redo the process of restoring 4.20.631.3 nandroid (if it was done correctly) .. just make sure 4.20.631.3 or 6.13.631.7 stock recovery is installed, not any other version.
Reboot, check OTA, download and select install now. The system will boot to RUU mode to install the update .. it won't go to recovery (that's why I don't understand your above post saying it stop in recovery - no manual installation too)
Read the How-To all the 14 steps and tick what you have done so you'll know that you don't skip any step
Click to expand...
Click to collapse
I apologize as if never seen this screen before. My assumption was it's a stock android recovery. But I must admit I do not know.
Attached is the pic of what I'm talking about.
https://drive.google.com/file/d/0B--VfMbsbBNCMEl6X3UyN3NIdGtXS29kRmE1R0tiaWdjVm9n/view?usp=sharing
Yeah ... that's stock recovery with error log ...
It says the system expect stock recovery 4.20.631.3 (463267.3) or 6.13.631.7 (667457.7) is installed for it to proceed the update, but the device has wrong stock recovery image 4.20.631.2 (463267.2) installed so it stops the installation (Status 7)
As I said above, no need to redo the nandroid restore process. Just install recovery image 4.20.631.3 or 6.13.631.7 then redo the OTA checking, download and install.
Note : I believe you followed the instruction written on post #9. There was a typo on recovery version that I edited an hour after posting it yesterday.
That's why you got this error ... sorry for that.
ckpv5 said:
Yeah ... that's stock recovery with error log ...
It says the system expect stock recovery 4.20.631.3 (463267.3) or 6.13.631.7 (667457.7) is installed for it to proceed the update, but the device has wrong stock recovery image 4.20.631.2 (463267.2) installed so it stops the installation (Status 7)
As I said above, no need to redo the nandroid restore process. Just install recovery image 4.20.631.3 or 6.13.631.7 then redo the OTA checking, download and install.
Note : I believe you followed the instruction written on post #9. There was a typo on recovery version that I edited an hour after posting it yesterday.
That's why you got this error ... sorry for that.
Click to expand...
Click to collapse
no worries. I have been feeling like a jerk for not following what your saying. I never wanted to frustrate you like this.
Last quick question before I stress over this. My next steps are:
DL your 6.13.631.7
Install in twrp/backups / 6.13.631.7
reboot
DL the OTA
install.
I'm just not sure about where to put the 6.13.631.7 file?
I think you still confused with nandroid & stock recovery.
There is no need to download 6.13.631.7 nandroid and no need to put it in twrp/backups
You just need to download the stock recovery image. Let's forget about 6.13.631.7 for now ...
1. download stock recovery image 4.20.631.3 - https://mega.nz/#!TdZg1aID!einylYid2QmN8OoxehNcnTrh6iijFqJ2-klrRsb-5MI
2. Put your device on bootloader/fastboot mode and install stock recovery image 4.20.631.3
fastboot flash recovery 4.20.631.3_recovery.img
3. reboot, check OTA, download OTA, select install now and let the system do it stuff.
4. Once completed, it will reboot and greet you with new Marshmallow 6.13.631.7 ROM.
5. Put your device on bootloader/fastboot mode and install latest TWRP
6. install your custom ROM .... done
ckpv5 said:
I think you still confused with nandroid & stock recovery.
There is no need to download 6.13.631.7 nandroid and no need to put it in twrp/backups
You just need to download the stock recovery image. Let's forget about 6.13.631.7 for now ...
1. download stock recovery image 4.20.631.3 - https://mega.nz/#!TdZg1aID!einylYid2QmN8OoxehNcnTrh6iijFqJ2-klrRsb-5MI
2. Put your device on bootloader/fastboot mode and install stock recovery image 4.20.631.3
fastboot flash recovery 4.20.631.3_recovery.img
3. reboot, check OTA, download OTA, select install now and let the system do it stuff.
4. Once completed, it will reboot and greet you with new Marshmallow 6.13.631.7 ROM.
5. Put your device on bootloader/fastboot mode and install latest TWRP
6. install your custom ROM .... done
Click to expand...
Click to collapse
I really don't know whats happened to all my knowledge and abilities. It's like my frustrations have literally taken over.
I was able to push the recovery image to the phone. rebooted and am now DL'ing the update.
for the last little while I've downloaded twrp but have yet to succeed on pushing it to the phone. I've downloaded the latest file, changed the name to twrp.img and used this while in bootloader/fastboot mode.
fastboot flash recovery twrp.img
error cannot load "twrp.img"
At the end of the day today I was able to install your nandroid file, upgrade to marshmallow, install the latest TWRP and about to flash a marshmallow ROM. I cannot thank you enough for all your insight, patience and help with this. You truly have an amazing talent. It is amazing the support you find on XDA and your name should be at the top of that list.
The official step http://www.htcdev.com/bootloader
Related
As there are many questions on how to do OTA update & to revert to stock after a device is rooted and bootloader unlocked; I made this simple guide which I hope will help the newbies especially.
NOTE : always do a backup and a nandroid backup before trying any of these.
OTA update:
A) ROM is stock, bootloader unlocked, stock recovery and not rooted.
- just run the OTA update, there is no need to relock the bootloader
B) ROM is stock, bootloader unlocked, CWM recovery and not rooted.
- flash the stock recovery that comes with your RUU, extract the RUU for the stock recovery.
* boot to bootloader
* fastboot flash recovery recovery_signed.img
* fastboot reboot-bootloader
* fastboot erase cache
* fastboot reboot
- run the OTA update
C) ROM is stock, bootloader unlocked, stock recovery and rooted
- download OTA Rootkeeper from Play Store
- run the OTA Rootkeeper and click protect root
- run the OTA update, there is no need to relock bootloader
- Once done, run OTA Rootkeeper and click restore root
D) ROM is stock, bootloader unlocked, CWM recovery and rooted
- download OTA Rootkeeper from Play Store
- run the OTA Rootkeeper and click protect root
- no need to relock bootloader
- boot to bootloader and fastboot flash the stock recovery
- run the OTA update
- Once done, run OTA Rootkeeper and click restore root
E) ROM is custom, bootloader unlocked, CWM recovery and rooted and you have a stock nandroid backup
- flash the stock boot.img if after nandroid restore, you have a bootloop
- flash the stock recovery.img
- relock the bootloader - fastboot oem lock
- boot your device and run the OTA update
F) ROM is custom, bootloader unlocked, CWM recovery and rooted and you don't have a stock nandroid backup
- if you dont have the stock nandroid backup, you need to run RUU
- before you can run the RUU you need to:
* flash the stock recovery.img
* flash the stock boot.img (maybe no need)
* relock the bootloader - fastboot oem lock
* run RUU
- run device setup
- run the OTA update
Flashing RUU to revert to stock or to update your One V after you have a custom ROM installed.
- you must have the correct RUU for your device.
- if you are not sure, download CID Getter from Play Store and run it, it will show your CID.
- with your CID, you may be able to find a correct RUU for your device
then
1- in fastboot mode - relock the bootloader : run command fastboot oem lock
2- in fastboot mode - flash/run/double click the RUU; follow the updater instruction - next,update,bla,bla,bla until it finish
Note :
Error 155 - usually wrong recovery.img /wrong boot.img or bootloader not relocked
Error 140 - wrong bootloader / bootloader unlocked
Error 131 - wrong RUU for your device
Credit to all XDA members that posted all the guides in various forum thread and some from own experience which I compiled here for easy reference.
If I have a nandroid backup from my stock (nandroid after it was rooted), how can I get rid of root? I need to lock bootloader also because I need to return my product. Also, I have the kernel img and recovery img (need to flash those also because I have flashed custom kernel and cwm).
So my guess is that:
nandroid restore
go to fastboot and flash boot.img
go to fastboot and flash recovery img
go to fastboot and relock bootloader.
but how do you get rid of root?
1ceb0x said:
If I have a nandroid backup from my stock (nandroid after it was rooted), how can I get rid of root? I need to lock bootloader also because I need to return my product. Also, I have the kernel img and recovery img (need to flash those also because I have flashed custom kernel and cwm).
So my guess is that:
nandroid restore
go to fastboot and flash boot.img
go to fastboot and flash recovery img
go to fastboot and relock bootloader.
but how do you get rid of root?
Click to expand...
Click to collapse
i think u have an option in super su
to completely get rid of root
dnt knw if tht wrks
try it
dont just say thanks hit thanks if i helped
sent from my awesome HTC One V using xda premium
1ceb0x said:
If I have a nandroid backup from my stock (nandroid after it was rooted), how can I get rid of root? I need to lock bootloader also because I need to return my product. Also, I have the kernel img and recovery img (need to flash those also because I have flashed custom kernel and cwm).
So my guess is that:
nandroid restore
go to fastboot and flash boot.img
go to fastboot and flash recovery img
go to fastboot and relock bootloader.
but how do you get rid of root?
Click to expand...
Click to collapse
Are you able to get the RUU for your phone/region?
1ceb0x said:
but how do you get rid of root?
Click to expand...
Click to collapse
Reflash system.img is the no-fail way.
CafeKampuchia said:
Reflash system.img is the no-fail way.
Click to expand...
Click to collapse
System.img is the rom itself right? If yes, by reflashing it, the root will still be there because the nandroid was AFTER it was rooted. And I didn't found my RUU. I have found one which is the same as mine but the last number .x differs from mine (I have .4 and the RUU has .3)...
your going to need the ruu buddy, i have to do the same, the kernel shows up as root blah blah blah. kernel recovery and rom itself need flashing.....
Would you be okay with just removing the superuser.apk or did you also want the binary gone?
One of the possible options is to modify your nandroid backup so that both files are deleted (and not restored), but I'm not sure if CWM complains if the backup has been modified.
1ceb0x said:
If I have a nandroid backup from my stock (nandroid after it was rooted), how can I get rid of root? I need to lock bootloader also because I need to return my product. Also, I have the kernel img and recovery img (need to flash those also because I have flashed custom kernel and cwm).
So my guess is that:
nandroid restore
go to fastboot and flash boot.img
go to fastboot and flash recovery img
go to fastboot and relock bootloader.
but how do you get rid of root?
Click to expand...
Click to collapse
Restore your nandroid backup
Reboot your device.
Open the SuperSU, and click Full unroot (it will remove the app, apk & su library)
Reboot to recovery
Make a new nandroid backup (this time there is no root for safekeeping)
Reboot to bootloader
fastboot flash boot stockboot.img
fastboot erase cache
fastboot flash recovery stockrecovery.img
fastboot erase cache
fastboot oem lock
now you are back to stock rom without root and relocked
Thank you so much, will try it tonight because tomorrow I need to get my unit to replacement. I didn't knew how the process worked since I never did it (I work with android for 3 years now).
But I have a question. If you open su and you click full unroot, why do you need to make a new nandroid and flash that?
1ceb0x said:
Thank you so much, will try it tonight because tomorrow I need to get my unit to replacement. I didn't knew how the process worked since I never did it (I work with android for 3 years now).
But I have a question. If you open su and you click full unroot, why do you need to make a new nandroid and flash that?
Click to expand...
Click to collapse
Because your old nandroid has SuperSU.apk and SU library in it.
New backup will not have those because you already remove them before new nandroid is made.
So you'll have a new stock nandroid without root.
ckpv5 said:
Because your old nandroid has SuperSU.apk and SU library in it.
New backup will not have those because you already remove them before new nandroid is made.
So you'll have a stock nandroid without root.
Click to expand...
Click to collapse
But if I restore the nandroid that has root and then unroot it, I don't see why you need to make a new one and restore that.
1ceb0x said:
But if I restore the nandroid that has root and then unroot it, I don't see why you need to make a new one and restore that.
Click to expand...
Click to collapse
I see your point... I thought that you do want to keep a stock nandroid without root for safekeeping as there is no RUU for .4 yet
The post now updated.
ckpv5 said:
I see your point... I thought that you do want to keep a stock nandroid without root for safekeeping as there is no RUU for .4 yet
Click to expand...
Click to collapse
Well, the point is that I will replace this unit with another one since this one is not working with Orange carriers. My shop was in talks with HTC service to get an unlock code but they failed to do so, so they said it is ok to change the unit. No need to keep a nandroid backup since I don't know what software version I will have on the new phone. Thank you for your help!
I fall under category D (ROM is stock, bootloader unlocked, CWM recovery and rooted)
Can someone tell me in detail how to
boot to bootloader and fastboot flash the stock recovery
Click to expand...
Click to collapse
Do I boot into CWM?
Thanks for your help.
RaskloP said:
I fall under category D (ROM is stock, bootloader unlocked, CWM recovery and rooted)
Can someone tell me in detail how to
Do I boot into CWM?
Thanks for your help.
Click to expand...
Click to collapse
No, not boot into CWM.
Remember how you go to bootloader when you first want to unlock your bootloader ? You press power + volume down, that is boot to bootloader.
1ceb0x said:
Thank you so much, will try it tonight because tomorrow I need to get my unit to replacement. I didn't knew how the process worked since I never did it (I work with android for 3 years now).
But I have a question. If you open su and you click full unroot, why do you need to make a new nandroid and flash that?
Click to expand...
Click to collapse
so that your new nandroid backup doesn't have SuperSU and you can still keep your datas
RaskloP said:
I fall under category D (ROM is stock, bootloader unlocked, CWM recovery and rooted)
Can someone tell me in detail how to
Do I boot into CWM?
Thanks for your help.
Click to expand...
Click to collapse
Please make sure you're flashing to recovery, not boot.
Connect your phone to your computer via USB. I'll assume you have the necessary bootloader/adb drivers installed.
Open up a command prompt to wherever your recovery.img is and type (this assumes you can easily access adb/fastboot from anywhere):
adb reboot bootloader
Phone should reboot into fastboot. From there type:
fastboot flash recovery recovery.img
It should then flash the stock recovery.
I would recommend taking a look at the HTC All-in-One ToolKit in the Development forums. It might simplify it for you.
To get back to you guys, I have followed these instructions and I am back to stock. The only thing that should worry me now is that the bootloader says "RELOCKED" instead of "LOCKED" but I don't think this is a reason why I should loose my warranty since we've done it using HTCDEV method.
It was easy enough because I had my nandroid backup. Such a joy to have one of these at hand!
Thank you all for the infos. Tomorrow I'll get my replacement :yuhuu:
1ceb0x said:
To get back to you guys, I have followed these instructions and I am back to stock. The only thing that should worry me now is that the bootloader says "RELOCKED" instead of "LOCKED" but I don't think this is a reason why I should loose my warranty since we've done it using HTCDEV method.
It was easy enough because I had my nandroid backup. Such a joy to have one of these at hand!
Thank you all for the infos. Tomorrow I'll get my replacement :yuhuu:
Click to expand...
Click to collapse
yea it should be ok buddy, my new handset arrives tomorrow, wish i could had gone to a store to pick it up so i could check it before i left the store :/ i do hate 3 customer services
Hi I have a htc one.m8 rooted with htc dev and.twrp and I have a over.the air.update and no way of installing it at the moment. How does one go about doing.this update when.rooted or do I have to unroot to do the update? Thanks
Sent from my HTC One_M8 using Tapatalk
MAhtc said:
Hi I have a htc one.m8 rooted with htc dev and.twrp and I have a over.the air.update and no way of installing it at the moment. How does one go about doing.this update when.rooted or do I have to unroot to do the update? Thanks
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
I assume, that a HTC-Stock ROM is installed on your htc one m8. NO Custom ROM and NO Custom HBoot! <- IMPORTANT
Root doesn't matter for an OTA Update.
But you have to flash the Stock Recovery that matches with your ROM Base and Relock the Bootloader.
First you must Backup your device including Internal Storage, because of the Factory Reset that happen when you Unlock the Bootloader again!
You can find here a collection of Stock Recovery
COLLECTION of Stock backup's by Mr Hofs
And you shut use this Toolkit to Relock the Bootloader and to Unlock it again after the OTA.
All-In-One Toolkit V2.0 by Hasoon2000
Menu -> Commands->Relock Bootloader. You have to be in fastboot USB Mode first, to do that.
After that you can receive and install a OTA for HTC.
READ EVERYTHING VERY CAREFULLY IN EVERY THREAD!
Since your device is Unlocked and S-OFF you can brick it with a wrong move!
You can find almost everything on this Forum, try to use Search next time.
Regards, Toni
---------- Post added at 08:03 AM ---------- Previous post was at 07:59 AM ----------
I've forgotten to mention that you must be on the right CID!
Or supercid 11111111
exad said:
Or supercid 11111111
Click to expand...
Click to collapse
As far as I know, you can't receive a OTA Update with Super CID 111111.
It won't flash, because of the "android-info" in the OTA Update File.
The "android-Info" contains the CID that can receive the OTA, otherwise it won't flash. to avoid that the device receives a wrong OTA.
You must set it to the original Provider CID that matches with your Stock ROM.
In your case, I think:
modelid: 0P6B16000
cidnum: TELUS001
just install a custom rom...
Toni10 said:
As far as I know, you can't receive a OTA Update with Super CID 111111.
It won't flash, because of the "android-info" in the OTA Update File.
The "android-Info" contains the CID that can receive the OTA, otherwise it won't flash. to avoid that the device receives a wrong OTA.
You must set it to the original Provider CID that matches with your Stock ROM.
In your case, I think:
modelid: 0P6B16000
cidnum: TELUS001
Click to expand...
Click to collapse
Incorrect, SuperCID bypasses all CID checks. I was pretty sure already as this was the case on my OneXL, but for the sake of giving the correct information, I just restored a Rogers TWRP backup, flashed rogers stock recovery extracted from the rogers OTA, changed my CID to 11111111 and ran the OTA from stock recovery. As per my sig, I am not even using a rogers phone.
Ran just fine.
Does rooting and s-off affect performance at all on the m8?
Sent from my HTC One_M8 using xda app-developers app
No. Just gives you the opportunity to tweak it more to your needs.
Toni10 said:
I assume, that a HTC-Stock ROM is installed on your htc one m8. NO Custom ROM and NO Custom HBoot! <- IMPORTANT
Root doesn't matter for an OTA Update.
But you have to flash the Stock Recovery that matches with your ROM Base and Relock the Bootloader.
First you must Backup your device including Internal Storage, because of the Factory Reset that happen when you Unlock the Bootloader again!
You can find here a collection of Stock Recovery
[url] COLLECTION of Stock backup's by Mr Hofs[/URL]
And you shut use this Toolkit to Relock the Bootloader and to Unlock it again after the OTA.
All-In-One Toolkit V2.0 by Hasoon2000
Menu -> Commands->Relock Bootloader. You have to be in fastboot USB Mode first, to do that.
After that you can receive and install a OTA for HTC.
READ EVERYTHING VERY CAREFULLY IN EVERY THREAD!
Since your device is Unlocked and S-OFF you can brick it with a wrong move!
You can find almost everything on this Forum, try to use Search next time.
Regards, Toni
---------- Post added at 08:03 AM ---------- Previous post was at 07:59 AM ----------
I've forgotten to mention that you must be on the right CID!
Click to expand...
Click to collapse
the link for stock recovery doesn't work
Toni10 said:
As far as I know, you can't receive a OTA Update with Super CID 111111.
It won't flash, because of the "android-info" in the OTA Update File.
The "android-Info" contains the CID that can receive the OTA, otherwise it won't flash. to avoid that the device receives a wrong OTA.
You must set it to the original Provider CID that matches with your Stock ROM.
In your case, I think:
modelid: 0P6B16000
cidnum: TELUS001
Click to expand...
Click to collapse
I have a SaskTel htc one m8
MAhtc said:
Hi I have a htc one.m8 rooted with htc dev and.twrp and I have a over.the air.update and no way of installing it at the moment. How does one go about doing.this update when.rooted or do I have to unroot to do the update? Thanks
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
on another note I am new to this whole root thing and was wondering about going back to stock or at least a step by step way to get the ota update on my rooted m8. I can't seem to find it on the forum, I very well could be blind lol so I apologize
thank you
What you need to do an OTA:
Stock Recovery
Stock Rom
Stock CID or SuperCID
Can I keep root!?!? Yes, you can!
As it stands there is no RUU (Rom Update Utility) to easily return to stock SO If one does not have the stock rom installed, one must restore a stock nandroid and manually flash stock recovery/
Stock Rom Nandroid backups and Recoveries courtesy of Mr Hofs
This collection assumes you know your CID. If you don't know it, check it! Boot to fastboot then use the command: fastboot oem readcid
What can you do if you don't have your nandroid and it isn't listed there? You can request someone from the same carrier with a stock nandroid upload theirs within that thread.
Once you have the nandroid, it's simply a matter of putting the nandroid in the appropriate folder for your custom recovery, booting to said recovery and restoring the nandroid.
Where nandroids should be placed:
TWRP: \sdcard\TWRP\backups\
Philz Touch: \sdcard\clockworkmod\backups\
Once you have the nandroid restored, you will need to flash stock recovery. If you know the stock recovery version you should be using, you can download them on that same thread. It is also possible to extract the recovery from the OTA zip file should you have access to it. (You can use the stock rom you restored to download the OTA then extract it and the firmware.zip file within and then flash the recovery.img)
fastboot flash recovery recovery.img
Then you can boot to stock recovery and flash the OTA.zip
Boot to bootloader
Select Recovery
You'll get a picture on your screen
Press and hold volume up and then press power
You will be presented with a menu
Select apply update from internal storage and then select the OTA Zip file in the downloads folder.
All done.
exad said:
Incorrect, SuperCID bypasses all CID checks. I was pretty sure already as this was the case on my OneXL, but for the sake of giving the correct information, I just restored a Rogers TWRP backup, flashed rogers stock recovery extracted from the rogers OTA, changed my CID to 11111111 and ran the OTA from stock recovery. As per my sig, I am not even using a rogers phone.
Ran just fine.
Click to expand...
Click to collapse
I never tried it with Super CID, to install an OTA.
In the most Tutorials that I've found it was recommended to set the original CID.
But good to Know that it works.
At least it's safer to set the original CID, in that case.
MAhtc said:
the link for stock recovery doesn't work
Click to expand...
Click to collapse
Sorry, the Link is working now.
That is a HTC CID List at xda.
http://forum.xda-developers.com/showthread.php?t=2445289
EDIT: Nevermind, I followed the guide here http://forum.xda-developers.com/showthread.php?t=2708581 to change my MID to the European one,
reflahed the OTA.zip in stock recovery and all good now!
******************************************************************************************************************
I am on SuperCID and flashed everything to 1.54.401.5.
Everything stock.
I tried flashing the OTA.zip from stock recovery but I get an error
"assert failed: check_mid("full", "0P6B100000" == "t".
I have the Asia 2.5GHZ version and the MID is "0P6B11000" but wanted to run full EU WWE and get the updates there.
Does the stock recovery check for ModelID as well?
Is there something I can do, like change my model ID? Can you please point me to a link on how to do it? Thanks.
exad said:
What you need to do an OTA:
Stock Recovery
Stock Rom
Stock CID or SuperCID
Can I keep root!?!? Yes, you can!
As it stands there is no RUU (Rom Update Utility) to easily return to stock SO If one does not have the stock rom installed, one must restore a stock nandroid and manually flash stock recovery/
Stock Rom Nandroid backups and Recoveries courtesy of Mr Hofs
This collection assumes you know your CID. If you don't know it, check it! Boot to fastboot then use the command: fastboot oem readcid
What can you do if you don't have your nandroid and it isn't listed there? You can request someone from the same carrier with a stock nandroid upload theirs within that thread.
Once you have the nandroid, it's simply a matter of putting the nandroid in the appropriate folder for your custom recovery, booting to said recovery and restoring the nandroid.
Where nandroids should be placed:
TWRP: \sdcard\TWRP\backups\
Philz Touch: \sdcard\clockworkmod\backups\
Once you have the nandroid restored, you will need to flash stock recovery. If you know the stock recovery version you should be using, you can download them on that same thread. It is also possible to extract the recovery from the OTA zip file should you have access to it. (You can use the stock rom you restored to download the OTA then extract it and the firmware.zip file within and then flash the recovery.img)
fastboot flash recovery recovery.img
Then you can boot to stock recovery and flash the OTA.zip
Boot to bootloader
Select Recovery
You'll get a picture on your screen
Press and hold volume up and then press power
You will be presented with a menu
Select apply update from internal storage and then select the OTA Zip file in the downloads folder.
All done.
Click to expand...
Click to collapse
Firstly you don't need to relock the bootloder to flash an ota.
From what I can see from looking at the updater script in the ota it checks CID and MID. The CID and MID for various models seem to be listed in the updater script. If yours isn't there then it it will fail.
From what I can see it doesnt seem like a particular CID or MID is required, just one listed in the updater script.
Not sure if you can modify an updater script in a signed ota and it still work or not.
Toni10 said:
As far as I know, you can't receive a OTA Update with Super CID 111111.
It won't flash, because of the "android-info" in the OTA Update File.
The "android-Info" contains the CID that can receive the OTA, otherwise it won't flash. to avoid that the device receives a wrong OTA.
You must set it to the original Provider CID that matches with your Stock ROM.
In your case, I think:
modelid: 0P6B16000
cidnum: TELUS001
Click to expand...
Click to collapse
I left mine on Super CID and was able to flash the OTA. I've also read reports of others who have been able to flash the OTA after only going back to the stock recovery, however I went through the process of relocking my bootloader and insuring all "bloat" apps were restored (this was on an AT&T variant though).
Well tired doing this again but it fails, umm says cid unknown in the recovery screen when try I to flash the ota, tired changing my cid to original and to supercid, still same.thing, don't know what I am doing wrong
I also tried going back to stock and running the update but says it Won't install since it thinks the phone is rooted
exad said:
What you need to do an OTA:
Stock Recovery
Stock Rom
Stock CID or SuperCID
Can I keep root!?!? Yes, you can!
As it stands there is no RUU (Rom Update Utility) to easily return to stock SO If one does not have the stock rom installed, one must restore a stock nandroid and manually flash stock recovery/
Stock Rom Nandroid backups and Recoveries courtesy of Mr Hofs
This collection assumes you know your CID. If you don't know it, check it! Boot to fastboot then use the command: fastboot oem readcid
What can you do if you don't have your nandroid and it isn't listed there? You can request someone from the same carrier with a stock nandroid upload theirs within that thread.
Once you have the nandroid, it's simply a matter of putting the nandroid in the appropriate folder for your custom recovery, booting to said recovery and restoring the nandroid.
Where nandroids should be placed:
TWRP: \sdcard\TWRP\backups\
Philz Touch: \sdcard\clockworkmod\backups\
Once you have the nandroid restored, you will need to flash stock recovery. If you know the stock recovery version you should be using, you can download them on that same thread. It is also possible to extract the recovery from the OTA zip file should you have access to it. (You can use the stock rom you restored to download the OTA then extract it and the firmware.zip file within and then flash the recovery.img)
fastboot flash recovery recovery.img
Then you can boot to stock recovery and flash the OTA.zip
Boot to bootloader
Select Recovery
You'll get a picture on your screen
Press and hold volume up and then press power
You will be presented with a menu
Select apply update from internal storage and then select the OTA Zip file in the downloads folder.
All done.
Click to expand...
Click to collapse
So I cannot flash ota, lost s-off and would like to go back to stock for now, and tried flashing several ways to get stock software back but nothing is working
exad said:
Incorrect, SuperCID bypasses all CID checks. I was pretty sure already as this was the case on my OneXL, but for the sake of giving the correct information, I just restored a Rogers TWRP backup, flashed rogers stock recovery extracted from the rogers OTA, changed my CID to 11111111 and ran the OTA from stock recovery. As per my sig, I am not even using a rogers phone.
Ran just fine.
Click to expand...
Click to collapse
Really? This is terrific info. Not that I care to do any type of OTA, (why bother? It'll be on XDA in a couple of minutes lol) but it is something to remember. I didn't realize the Super CID was that expansive. I did realize that it allowed you to use your phone on any carrier though, so I probably should have picked up on that.
Hi all,
I'm sending my phone back to HTC becuase since day one it's been presenting issues (loose screen, the volume button is saggy and ultimatly what made me send it back, the camera seems to be having issues, I get the "you are blocking the secondary camera" message, when I'm not, and the camera can't focus correctly making the pictures extreamly blurry.
anyways, I'm getting the phone ready to sent it back, I flashed 1.54.401.5 firmware and went back to my old nandroid backup which was in 4.4.2, I flashed the stock recovery 1.12.1540.17 and the CID to the original one BS_US002.
I did a factory reset in the stock recovery and set up the phone, however I'm not getting the OTA for 4.4.3 and I have no idea what I'm missing...
any help would be highly appreciated.
ps: I used this as reference.
http://forum.xda-developers.com/showthread.php?t=2710735
I think it's kinda strange to flash the 1.12.1540 stock recovery on a 1.54.401 firmware ?! Weird huh....because they don't match.....but......that has nothing to do wether you get update notifications ! You should get them wether they can be installed or not. But the combo recovery + nand will not work to official install of the ota
Mr Hofs said:
I think it's kinda strange to flash the 1.12.1540 stock recovery on a 1.54.401 firmware ?! Weird huh....because they don't match.....but......that has nothing to do wether you get update notifications ! You should get them wether they can be installed or not. But the combo recovery + nand will not work to official install of the ota
Click to expand...
Click to collapse
thank you so much for your reply, I flashed the matching recovery, but still the update is not showing up, do you have any suggestions?
I'm downloading the stock nandroid listed in your nandroid backup thread for BS_US002 just to double check...
I think you need a different firmware. If you have the dev edition model that is originally on .1540 you can't do it via a 401 firmware.
My dev edition doesn't get 4.4.3 update either. All stock except unlocked s-off
Here a workaround for the ones interested:
1- Make sure MID and CID match, for the developer edition you have it should be:
MID: 0P6B12000
CID: BS_US002
If they match then you can download a stock nandroid and the firmware here.
2- Wipe evertying using TWRP and then restore the nand you´ve downloaded from the link above
3- Reboot your phone into booloader and then flash the firmware
4- I would advise you to clean the cache once you install the firmware in bootloader
5- Do a full factory restore from the bootloader, your phone should reboot by itself afterwards
In case you need it:
In order to flash the firmware you have to type Fastboot oem rebootRUU in bootloader mode then you will see an HTC grey logo, there you will have to type: fastboot flash zip firmware.zip. Make sure firmware you've have downloaded is renamed as "firmware.zip" before you do all this. I would recomend to perform this last command twice. To reboot your phone into bootloader type: fastboot reboot-bootloader, once your phone reboots then type Fastboot erase cache, perform a full factory restore there and let your phone reboot. After your phone reboots, you should have the latest version installed.
As and advise: be carefull with all this!
Mr Hofs said:
I think it's kinda strange to flash the 1.12.1540 stock recovery on a 1.54.401 firmware ?! Weird huh....because they don't match.....but......that has nothing to do wether you get update notifications ! You should get them wether they can be installed or not. But the combo recovery + nand will not work to official install of the ota
Click to expand...
Click to collapse
I flash any recovery to get dev ota and they all work
Or even simpler, as I did, apply the OTA through stock recovery.
Hello All,
So I recently bought a M8 and I just need some help in getting the steps nailed down correctly. Be warned long post with lots of questions...
Code:
fastboot getvar version-main
version-main: 3.32.111.3
fastboot oem readcid
(bootloader) cid: T-MOB101
That is basically my device, now due to it being 4.4.4 from factory I am unable to use Sunshine & Weaksauce. I could wait until the new year but why
bother .
First step:
Get my factory firmware image after reading this thread: http://forum.xda-developers.com/showthread.php?t=2701376 due to it being a T-Mobile and
Germany and 4.4.4 I am unable to run the command listed there to get the stock recovery, so how do I get the stock recovery for my device? @BerndM14
Has provided me with a link to download the latest firmware for my device but it has the TWRP recovery inside it, link is this one: http://www.handy-
faq.de/forum/htc_one_m8_custom_roms/304821-htc_one_m8_firmwaresammlung_ruus_otas_backups.html#post2832636. I should point out that I do have a OTA
waiting to download and install, should I download and install it? The version listed on the screen is 3.32.111.9 and is only 183.73MB. Would it have a
viable stock recovery? Can I downgrade to a older version for the stock recovery?
Second step:
Once the above is done and dusted my next step is getting root & S-OFF & custom recovery. This is relatively simple because all I need to do is visit
HTCDev, unlock and then S-OFF with Sunshine and then a custom recovery. Correct? Sounds and looks simple enough.
Third step:
Download ROM of choice and flash away. So I am going with InsertCoin due to user loyalty from the Desire days . However I see people in the thread
mentioning that they flashed the latest firmware to sort out a couple of issues, I take it they mean the ROM file and not HTC firmware?
Fourth and probably not needed step:
Changing the phone to WWE and SuperCID? Do I really need to do this? Benefit of changing to WWE is changing the HBOOT to a more universal one? The
reason why I am thinking of converting is because I would want to get rid of the red text on the boot screen as listed here: http://forum.xda-
developers.com/showpost.php?p=51744965&postcount=1 however for T-Mobile Dutch the HBOOT CIDS are T-MOB003, if I flash that would it cause a problem?
I would also be looking at running the commands to change the flags showing tampered and unlocked but that looks simple to do. Am I missing anything? For warranty purposes I would use the instructions from this thread: http://forum.xda-developers.com/showthread.php?t=2710735 but download the recovery file for T-MOB Germany instead?
Thank you for reading the long post and I hope that I have made some sort of sense.
Yes it will have the firmware.zip with the recovery.img inside it. Even the small 47MB or so, OTA update for the WWE from 2.22.401.4 - 2.22.401.5 had the firmware.zip inside. So just download the OTA.zip copy to PC extract firmware.zip and grab the recovery.img.
Benefits to converting to WWE or even Developer edition also includes the fact that those devices will receive OTA updates before any carrier version, directly from HTC. It's a bonus if you're into the "latest & greatest" scene.
As for making a backup before flashing custom recovery, have you tried booting the custom recovery? Philz will probably be better if you want to use the booted custom recovery to make a backup of stock recovery. You could also try and boot either TWRP or Philz and see if you can root your device without flashing custom recovery, that way you can at least use the dd command to grab a copy of the recovery block. <My preferred method, though it's a terrible circle. Need to flash custom recovery to root, need root to make backup of stock recovery... So hopefully booting the custom recovery will work. That being said, easiest way still remains to grab it from the OTA.zip.
Perhaps you could even upload a copy of the OTA.zip and share it on here, I don't think the OP has a copy in the second post
ROM/Firmware. You need the latest firmware to run the latest ROM. For most it'll be firmware with 3.x. If you still run on 2.x(which you aren't) you'd have some problems with radio(bluetooth, gps, wifi, data etc)
Thank you for the reply .
To be honest I have not tried booting a custom recovery because I saw this in the first post of this thread: http://forum.xda-developers.com/showthread.php?t=2701376
fastboot boot recovery_filename.img (this does not work on the latest 3.xx firmwares !!! we need to get the stock recoveries from the OTA files)
Click to expand...
Click to collapse
So I am not sure what to try to be honest. This toolkit: http://forum.xda-developers.com/showthread.php?p=51383278&highlight=ota#post51383278 mentions getting root without S-OFF but with a unlocked bootloader. So I am thinking that if I follow those steps, maybe when I get to the reboot phase I can execute a nandroid instead which might get me the files I want?
I won't bother with WWE then. I will rely on the dev's to give me the latest & greatest .
Anakha56 said:
Thank you for the reply .
To be honest I have not tried booting a custom recovery because I saw this in the first post of this thread: http://forum.xda-developers.com/showthread.php?t=2701376
So I am not sure what to try to be honest. This toolkit: http://forum.xda-developers.com/showthread.php?p=51383278&highlight=ota#post51383278 mentions getting root without S-OFF but with a unlocked bootloader. So I am thinking that if I follow those steps, maybe when I get to the reboot phase I can execute a nandroid instead which might get me the files I want?
I won't bother with WWE then. I will rely on the dev's to give me the latest & greatest .
Click to expand...
Click to collapse
Hm, yeah I also had some problems booting a recovery, but I just tested it out again. I can at least boot TWRP version 2.8.3.0 so it still works for me. I'm on 3.28.1540.5 (Developer edition). Haven't tried Philz though, net a bit too slow to bother with even a small download
No problem. I am busy downloading the OTA.zip and once complete I will try the toolkit method and see what happens . Again, thank you for the reply.
I need some help... My phone seems to be stuck in fastboot mode and is not picked up in Device Manager of Windows. I can touch the fastboot screen and it vibrates but it does not nothing. I have held down the power button for 20 seconds with no result. I had just unlocked the bootloader and then tried pushing the Philz recovery image to the device with the command line:
Code:
C:\android\sdk\android\platform-tools>fastboot boot philz_touch_6.57.8-m8.img
downloading 'boot.img'...
OKAY [ 1.541s]
booting...
OKAY [ 0.002s]
finished. total time: 1.547s
*edit*
Holding volume up + power for 10 seconds helped *whew*...
Anakha56 said:
Thank you for the reply .
To be honest I have not tried booting a custom recovery because I saw this in the first post of this thread: http://forum.xda-developers.com/showthread.php?t=2701376
So I am not sure what to try to be honest. This toolkit: http://forum.xda-developers.com/showthread.php?p=51383278&highlight=ota#post51383278 mentions getting root without S-OFF but with a unlocked bootloader. So I am thinking that if I follow those steps, maybe when I get to the reboot phase I can execute a nandroid instead which might get me the files I want?
I won't bother with WWE then. I will rely on the dev's to give me the latest & greatest .
Click to expand...
Click to collapse
You don't need S-Off to root, just the unlocked bootloader, custom recovery, and superuser.
@xunholyx Thanks for the post . I am trying to get an image of my stock recovery file first, so I am trying to avoid flashing the custom recovery right now . BTW Does anyone know if TWRP makes a backup of the stock recovery before overwriting it like Philz does?
Anakha56 said:
@xunholyx Thanks for the post . I am trying to get an image of my stock recovery file first, so I am trying to avoid flashing the custom recovery right now . BTW Does anyone know if TWRP makes a backup of the stock recovery before overwriting it like Philz does?
Click to expand...
Click to collapse
http://www.handy-faq.de/forum/htc_o...resammlung_ruus_otas_backups.html#post2832635
oops sorry.. i see you already been their
your hboot 3.19 will prevent booting to recovery ... and no TWRP doesn't backup stock recovery
you just need to find the OTA.zip for your version it must be out their somewhere
@clsA I have the file
3.32.111.3 - TWRP
Click to expand...
Click to collapse
From that site but its recovery is TWRP. I am trying to grab the stock recovery currently on the device before going forward. When I unzip that file it has 6 items:
boot.emmc.win
boot.emmc.win.md5
system.ext4.win000
system.ext4.win000.md5
system.ext4.win001
system.ext4.win001.md5
Click to expand...
Click to collapse
I have downloaded the OTA that is ready for my phone but I had hit a snag. The file was corrupt, on redownload I have the small OTA but the recovery version number has incremented past mine, I don't know if it will be still useable with the ROM file from the link?
Anakha56 said:
@clsA I have the file
From that site but its recovery is TWRP. I am trying to grab the stock recovery currently on the device before going forward. When I unzip that file it has 6 items:
I have downloaded the OTA that is ready for my phone but I had hit a snag. The file was corrupt, on redownload I have the small OTA but the recovery version number has incremented past mine, I don't know if it will be still useable with the ROM file from the link?
Click to expand...
Click to collapse
it should work, recovery does not have to be exact just close
and the file you have doesn't include TWRP .. it was created with twrp ... big difference
Anakha56 said:
@clsA I have the file
From that site but its recovery is TWRP. I am trying to grab the stock recovery currently on the device before going forward. When I unzip that file it has 6 items:
I have downloaded the OTA that is ready for my phone but I had hit a snag. The file was corrupt, on redownload I have the small OTA but the recovery version number has incremented past mine, I don't know if it will be still useable with the ROM file from the link?
Click to expand...
Click to collapse
You can use any 3.32 based stock recovery for your phone. There are plenty of backups for that on this thread. No need to backup your own.
Thank you guys! That helps me a lot! Off I go to flash a custom recovery .
Hi Folks,
Well, I'm S-OFF and running ViperROM with 2.10.401.1 firmware (from sneakyghost thread) and TWRP Recovery on an international device with unlocked bootloader and SuperCID.
Now I want to play again with a full fresh and clean stock experience. How to accomplish this?
The easiest way would be to run a 2.10.401.1 RUU exe, but I couldn't find one. I guess it's not available and maybe never will be.
So, after reading threads I would assume the way I have to go is to run an 1.32 RUU exe and then I should get the 2.10 OTA
Is that right or do I have to relock the bootloader to get stock OTAs ? (Cos of S-OFF)
Hope you could help me out on that one and point me in the right direction.
Thx
You have to be 100% stock to get OTAs successfully. Since you're s-off, just running an earlier RUU exe should do it, but you may need to relock.
Under no circumstances should you go back to s-on.
DroidShift79 said:
Hi Folks,
Well, I'm S-OFF and running ViperROM with 2.10.401.1 firmware (from sneakyghost thread) and TWRP Recovery on an international device with unlocked bootloader and SuperCID.
Now I want to play again with a full fresh and clean stock experience. How to accomplish this?
The easiest way would be to run a 2.10.401.1 RUU exe, but I couldn't find one. I guess it's not available and maybe never will be.
So, after reading threads I would assume the way I have to go is to run an 1.32 RUU exe and then I should get the 2.10 OTA
Is that right or do I have to relock the bootloader to get stock OTAs ? (Cos of S-OFF)
Hope you could help me out on that one and point me in the right direction.
Thx
Click to expand...
Click to collapse
Hi
Did you check this thread...
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
MAX 404 said:
Hi
Did you check this thread...
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
Click to expand...
Click to collapse
Yes, did that. But the full ZIP that is there doesn't touch the /system partition, so it's not the clean way I want to go.
THX anyway.
DroidShift79 said:
Yes, did that. But the full ZIP that is there doesn't touch the /system partition, so it's not the clean way I want to go.
THX anyway.
Click to expand...
Click to collapse
Hi
I see....guess the only way for now is as you point out earlier RUU and upgrade from there.
good luck
MAX 404 said:
Hi
I see....guess the only way for now is as you point out earlier RUU and upgrade from there.
good luck
Click to expand...
Click to collapse
Thought of this,
just not sure if I need to relock bootloader to get official otas
DroidShift79 said:
Thought of this,
just not sure if I need to relock bootloader to get official otas
Click to expand...
Click to collapse
If you're S-OFF you don't need to relock to get OTAs. I converted my carrier handset to unbranded and received OTA updates after flashing a RUU without relocking.
Sent from my HTC One M9 using Tapatalk
THX kingvortex. I just do it and report back.
Thanks all of you.
DroidShift79 said:
Thought of this,
just not sure if I need to relock bootloader to get official otas
Click to expand...
Click to collapse
kingvortex said:
If you're S-OFF you don't need to relock to get OTAs. I converted my carrier handset to unbranded and received OTA updates after flashing a RUU without relocking.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
hi mates
I do not think S-OFF , S-ON or locked bootloaders are much of an issue to get OTA, check points 8, 9 and 10 from this thread
EDIT : kingvortex you are right oem locked is necessary with s-on
http://forum.xda-developers.com/one...ery-twrp-touch-recovery-t3066720/post59745198
8. How do I restore stock system so that I can accept an OTA?
Check the "Mount system as read-only" box in the Mount menu.
Restore stock "System Image" backup (This will only work if you've made a System Image backup prior to making any modifications to /system like root it). As of the official 2.8.6.1 version, it is no longer necessary to fastboot flash the stock system image.
NOTE: If you made a stock system backup with one of the Beta TWRP versions, you will have to rename the backup file in the backup folder manually from "system.emmc.win" to "system_image.emmc.win" for the new official TWRP to see it as a "System Image" backup rather than a "System" backup. Otherwise, you'll get an error that the backup can't be restored because system is read-only.
Fastboot flash stock recovery (fastboot flash recovery recovery_signed.img)
NOTE: It is also possible to restore stock recovery via the TWRP GUI. Rename the stock recovery file to "recovery.emmc.win" and place in the backup folder with the stock system image. Recovery will then show as a restore option. MAKE SURE YOU REALLY WANT TO DO THIS, AS TWRP WILL BE GONE WHEN YOU REBOOT OUT OF RECOVERY!!
Reboot to system, install OTA.
9. What if I have an RUU? Do I need to worry about all this OTA nonsense?
Not if you don't care about losing all your data. If you're S-ON and have an RUU available for your exact variant (model ID and CID must match) and software number (main version must be the same or newer), then you can get back to a fully stock state by relocking (fastboot oem lock) and flashing an RUU. However, if you'd prefer to take an OTA to keep your data intact, the method stated above is how to do so. Or, you can just run a custom ROM and wait for your ROM chef to update their ROM to the latest software (though you'll still have to find a way to update your firmware if you're not S-OFF)
10. After I go through all this and successfully apply an OTA, how do I make sure I have a clean starting point again?
After the OTA is applied and TWRP is flashed, it will once again detect an untouched system, which will mount system read-only and allow you to make a fully stock backup and start the process over again, this time with the new base.
Well, what I did so far, was to use the 1.32.401.17 ruu.exe
Flash went fine, but no OTA did show up.
So I wanted to flash the 1.32.401.8 ruu zip.
But putting it on sdcard or using fastboot flash zip failed.
Wonder why!?
Later on I'll try Max 404 find.
MAX 404 said:
hi mates
I do not think S-OFF , S-ON or locked bootloaders are much of an issue to get OTA, check points 8, 9 and 10 from this thread
EDIT : kingvortex you are right oem locked is necessary with s-on
http://forum.xda-developers.com/one...ery-twrp-touch-recovery-t3066720/post59745198
8. How do I restore stock system so that I can accept an OTA?
Check the "Mount system as read-only" box in the Mount menu.
Restore stock "System Image" backup (This will only work if you've made a System Image backup prior to making any modifications to /system like root it). As of the official 2.8.6.1 version, it is no longer necessary to fastboot flash the stock system image.
NOTE: If you made a stock system backup with one of the Beta TWRP versions, you will have to rename the backup file in the backup folder manually from "system.emmc.win" to "system_image.emmc.win" for the new official TWRP to see it as a "System Image" backup rather than a "System" backup. Otherwise, you'll get an error that the backup can't be restored because system is read-only.
Fastboot flash stock recovery (fastboot flash recovery recovery_signed.img)
NOTE: It is also possible to restore stock recovery via the TWRP GUI. Rename the stock recovery file to "recovery.emmc.win" and place in the backup folder with the stock system image. Recovery will then show as a restore option. MAKE SURE YOU REALLY WANT TO DO THIS, AS TWRP WILL BE GONE WHEN YOU REBOOT OUT OF RECOVERY!!
Reboot to system, install OTA.
9. What if I have an RUU? Do I need to worry about all this OTA nonsense?
Not if you don't care about losing all your data. If you're S-ON and have an RUU available for your exact variant (model ID and CID must match) and software number (main version must be the same or newer), then you can get back to a fully stock state by relocking (fastboot oem lock) and flashing an RUU. However, if you'd prefer to take an OTA to keep your data intact, the method stated above is how to do so. Or, you can just run a custom ROM and wait for your ROM chef to update their ROM to the latest software (though you'll still have to find a way to update your firmware if you're not S-OFF)
10. After I go through all this and successfully apply an OTA, how do I make sure I have a clean starting point again?
After the OTA is applied and TWRP is flashed, it will once again detect an untouched system, which will mount system read-only and allow you to make a fully stock backup and start the process over again, this time with the new base.
Click to expand...
Click to collapse