Related
I looked for this all over XDA and google and couldn't find an answer,
I have an unlocked and rooted HOX+ international that had CM 10.2, I flashed a backup of my stock sense 4 using TWRP to try the official sense 5 update.
Now I need to re-lock bootloader and reinstall stock recovery for the HTC update to install, I can't find a stock recovery image anywhere and I'm not sure if it is even possible to do it this way without flashing an RUU?
Any help? any one can point me to a stock recovery image?
RECAP:
What I have: HOX+ International, stock sense 4, unlocked, rooted, TWRP recovery, HTC software update downloaded and ready to install
What I need: Relock, Revert to stock recovery (stock recovery img)
Thanks in Advance!
Haerviu said:
I looked for this all over XDA and google and couldn't find an answer,
I have an unlocked and rooted HOX+ international that had CM 10.2, I flashed a backup of my stock sense 4 using TWRP to try the official sense 5 update.
Now I need to re-lock bootloader and reinstall stock recovery for the HTC update to install, I can't find a stock recovery image anywhere and I'm not sure if it is even possible to do it this way without flashing an RUU?
Any help? any one can point me to a stock recovery image?
RECAP:
What I have: HOX+ International, stock sense 4, unlocked, rooted, TWRP recovery, HTC software update downloaded and ready to install
What I need: Relock, Revert to stock recovery (stock recovery img)
Thanks in Advance!
Click to expand...
Click to collapse
The stock recovery is here
[email protected] said:
The stock recovery is here
Click to expand...
Click to collapse
Thanks alot!
is it possible to do it the way I'm attempting? flash this stock recovery, relock bootloader and let the software update install?
Haerviu said:
Thanks alot!
is it possible to do it the way I'm attempting? flash this stock recovery, relock bootloader and let the software update install?
Click to expand...
Click to collapse
U have to unroot first........must be ok if u still get the notification for the Update installation...
Use SuperSu from Playstore.....and in the setting do full unroot......
then flash the Stock recovery and relock the bootloader.....
The main thing is u have to still get that notification to install the update.......
[email protected] said:
U have to unroot first........must be ok if u still get the notification for the Update installation...
Use SuperSu from Playstore.....and in the setting do full unroot......
then flash the Stock recovery and relock the bootloader.....
The main thing is u have to still get that notification to install the update.......
Click to expand...
Click to collapse
Life savior! Updated successfully.
Full unroot with SuperSu
Flash stock recovery
Relock bootloader
Update wasn't in notification but worked from settings menu.
Now I'm on sense 5!
I'm using p768 and flashed CW recovery. I'm wondering if there's a way to flash a stock recovery again. I searched the forum but didn't find any stock recoveries.
UNForces said:
I'm using p768 and flashed CW recovery. I'm wondering if there's a way to flash a stock recovery again. I searched the forum but didn't find any stock recoveries.
Click to expand...
Click to collapse
I don't think there is one... You'd have to either extract it from a stock kdz or flash one. The stock recovery really has no functions.
xdrc45 said:
I don't think there is one... You'd have to either extract it from a stock kdz or flash one. The stock recovery really has no functions.
Click to expand...
Click to collapse
I figured out that flashing a KDZ automatically restores the stock recovery.
And for those who want their unlocked boot loader to look as if it's locked, usually when using your warranty, you can follow these steps.
You can extract stock recovery.img from KDZ and then flash it via fastboot.
[Guide] EXTRACT BIN (from kdz) TO IMAGES FOR L9
So, never had a Sony-Device, the guides and instructions here are a bit unclear to me.
As far as i understood before going custom:
Downgrade to .532 with flashtool -> run BackupTA -> upgrade to latest again (rly neccessary?) -> then unlock Bootloader
Pretty straight forward up until here.
From there on i can use [NUTS]s XZDualRecovery if i want to stay on stock-kernel and flash custom roms frem there without any problem as far as i understood.
Is this correct?
But what if i want to use a custom kernel at some point?
DooMKernel for example is flahsed via Fastboot, but only compatible with Stock-Sony-Roms
PimpedKernel for example on the other hand is CM-based only and only uses a recovery flashable zip
I'm a little bit confused because of that.
Is a Kernel and / or recovery included in every ROM? (Edit: Yep Kernel is..)
Can i just use [NUTS] recovery and then flash any ROM / Kernel trough it? And afterwards a custom Kernel if the one included in ROM (if any?) lacks any features i want?
competent devs who maintain roms for this phone would include a recovery in their package
slimrom does this and i don't have to worry about losing trwp recovery
alia5 said:
So, never had a Sony-Device, the guides and instructions here are a bit unclear to me.
As far as i understood before going custom:
Downgrade to .532 with flashtool -> run BackupTA -> upgrade to latest again (rly neccessary?) -> then unlock Bootloader
Pretty straight forward up until here.
From there on i can use [NUTS]s XZDualRecovery if i want to stay on stock-kernel and flash custom roms frem there without any problem as far as i understood.
Is this correct?
But what if i want to use a custom kernel at some point?
DooMKernel for example is flahsed via Fastboot, but only compatible with Stock-Sony-Roms
PimpedKernel for example on the other hand is CM-based only and only uses a recovery flashable zip
I'm a little bit confused because of that.
Is a Kernel and / or recovery included in every ROM? (Edit: Yep Kernel is..)
Can i just use [NUTS] recovery and then flash any ROM / Kernel trough it? And afterwards a custom Kernel if the one included in ROM (if any?) lacks any features i want?
Click to expand...
Click to collapse
The downgrading is no longer necessary, use the easyroot tool. Or use the dualrecovery installer for locked bootloaders then flash superuser zip from recovery. Once you have it rooted then back up TA and unlock bootloader. You should be able to flash boot.img from flashtool, if you wanted to download a rom and pull it from zip. I mention that because most roms only have one recovery, so if you flash the img from the rom you want to install first with flashtool you could make a backup that could be restored with new recovery. One other thing that I learned the hard way is a backup made before unlocking bootloader will relock it if restored.
No downgrading, just root and back up TA, great
So i need to flash boot.img from the ROM every time i want to install a new ROM? Or just the first time going from stock to custom? Or just if i have twrp n current rom and the rom i wanna flash is only compatible with CWM?
alia5 said:
No downgrading, just root and back up TA, great
So i need to flash boot.img from the ROM every time i want to install a new ROM? Or just the first time going from stock to custom? Or just if i have twrp n current rom and the rom i wanna flash is only compatible with CWM?
Click to expand...
Click to collapse
Here is a brand spanking new guide to check out that is up to date.
http://forum.xda-developers.com/xperia-z-ultra/general/guide-everything-root-4-4-4-t2938098
I will try to put forth an example to try and demonstrate what I trying to convey in regards to flashing boot.img.
Example.... You are on a rom that contains CWM and you are going to flash a rom that contains TWRP and you wish to have a backup of first rom that could be restored you would flash the img. with TWRP then make backup. Another option would be to just go ahead and use CWM to make backup but you would need to flash that img. in order to be able to restore. I think most roms can be flashed from either recovery at the moment, the concern is your backup being compatible with whichever one is in your current rom.
So, in the boot.img is Kernel+Recovery, alright, and i only need to worry about flashing boot.img für backup reasons.
Pretty much answers what i was wondering, thanks guys
Hello,
I am not new to the process of rooting, unlock bootloader or flashing ROM. But, this is the first time that I need to root a HTC phone, the HTC One M8. I don't usually care much for stock ROM, but this is my girlfriend's phone and I think stock ROM works best for her. It is more stable, even though it will be a bit slow and has a lot of bloatware. I plan to root it then manually go in and disable most of the bloated apps. Then, I will install Xposed Module and add some useful modules. However, the release of Lollipop is around the corner. I want to know if rooting it will affect the ability of doing OTA upgrade.
Base on what I have read, in order to root, you have to unlock the bootloader, then replace the stock recovery with custom recovery like CWM/TWRP, then you flash the supersu.zip file to grant root permission. I am familiar with the process, but I am a bit confused at this part. Since we use a custom recovery to flash the supersu.zip file, it is more likely that OTA upgrade will fail since most OTA upgrade rely on stock recovery.
1/ Then, how do I upgrade to Lollipop 5.0 once I have rooted the phone?
The current ROM is Kitkat I think.
2/ I mean, is there a stock recovery file that I can flash back to replace the custom recovery once the phone has been rooted? or the OTA process will work with the custom recovery, which is very unlikely in my opinion.
3/ Also, once I have upgraded to Lollipop, I can do the same process to gain root again, (flash custom recovery, then flash supersu.zip to gain root). Is that correct?
4/ Is there any other method of gaining root without losing OTA update? As long as I don't have to wipe everything and restore it for every OTA update. I am fine with it.
Please let me know. Thank you all for your help.
After you root, flash back your stock recovery. As long as you are running stock the ota will attempt to download. Even when running non-stock recovery - what will happen is the ota will download and when you accept the update the phone will reboot into your custom recovery and the update won't be applied because the ota relies on the stock recovery being there.
So anyway, you can root, replace custom recovery back with stock and allow the update. You will most likely loose root once the update is applied, but then as long as there are custom recoveries available for the new android version you can flash back to custom recovery, reroot and you should be set.
I did this for a while, but the downside is that if SuperSU updates (or whichever root method you use) and requires a bin update, you won't be able to apply the root bin update unless you are running the custom recovery.
Hope that makes sense, typing from my phone while on a train.
What I do is this
Unlock Bootloader via HTC DEV website.
Dl a custom recovery I prefer TWRP Recovery flash that via Fastboot.
Then boot into custom recovery on your phone and create a New backup of the stock rom b4 you install SuperSU for root, name it something like (Stock untouched) .
Then flash superSU update zip in recovery.
Once superuser is working do what you want.
Note: I'd go ahead and find and Dl the stock recovery and keep it on hand for when you ready to go back Stock for the OTA update.
Go back to stock
Boot into custom recovery wipe system /data/cache. Then restore the Stock (untouched) backup you made.
Fastboot flash the stock recovery back.
Then relock Bootloader and now you back to Stock and ready to do the OTA update.
Note : this is what I do, everybody got their own way of doing things
Sent from my HTC One_M8 using Tapatalk
tommy_riley said:
After you root, flash back your stock recovery. As long as you are running stock the ota will attempt to download. Even when running non-stock recovery - what will happen is the ota will download and when you accept the update the phone will reboot into your custom recovery and the update won't be applied because the ota relies on the stock recovery being there.
So anyway, you can root, replace custom recovery back with stock and allow the update. You will most likely loose root once the update is applied, but then as long as there are custom recoveries available for the new android version you can flash back to custom recovery, reroot and you should be set.
I did this for a while, but the downside is that if SuperSU updates (or whichever root method you use) and requires a bin update, you won't be able to apply the root bin update unless you are running the custom recovery.
Hope that makes sense, typing from my phone while on a train.
Click to expand...
Click to collapse
Ok, thank you for the reply. That clears up a little. I can just flash stock recovery every time I want to update. I was able to find a thread that has all the stock recovery file. I have a quick question. Does any version of stock recovery will work? or you want the one that match your current stock recovery. Also, what is Non-WWE-Recoveries?
Here is the thread with all the stock recoveries:
http://forum.xda-developers.com/showthread.php?t=2701376
Let me know. Thank you
scoot0073 said:
What I do is this
Unlock Bootloader via HTC DEV website.
Dl a custom recovery I prefer TWRP Recovery flash that via Fastboot.
Then boot into custom recovery on your phone and create a New backup of the stock rom b4 you install SuperSU for root, name it something like (Stock untouched) .
Then flash superSU update zip in recovery.
Once superuser is working do what you want.
Note: I'd go ahead and find and Dl the stock recovery and keep it on hand for when you ready to go back Stock for the OTA update.
Go back to stock
Boot into custom recovery wipe system /data/cache. Then restore the Stock (untouched) backup you made.
Fastboot flash the stock recovery back.
Then relock Bootloader and now you back to Stock and ready to do the OTA update.
Note : this is what I do, everybody got their own way of doing things
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Hello,
I understand your concept for going back to stock. But, I don't get why I have to relock the bootloader. What I mean is, is that necessary for the OTA to work? I thought you only need the stock recovery for the OTA to work. Also, once you have done OTA update, and you want to root the phone again. The downsize is you have to unlock the bootloader again, which will wipe the phone completely and you will have to restore everything, which wastes times.
I like the idea of just restoring the stock recovery, do the OTA upgrade, then flash custom recovery to gain root again. I don't mind repeating that process for each update. But to relock/unlock the bootloader, having to wipe everything is a hassle. Please clarify. Thank you for your help.
I don't believe you need to relock boot loader for OTA. You do need locked bootloader for RUU full install, but only if S-ON (s-off you can do RUU w/boot loader locked or unlocked) - but that's not what were talking about here - OTA w/ unlocked boot loader = All good.
I believe WWE recovery refers to Europe versions of the recovery, so if in US go for the non-WWE.
I'd stick with trying to lineup stick recovery versions with version of OS software you have installed - so if you are running stock 4.4.2 or 4.4.3 grab the latest stocl recovery available.
vi6s said:
Hello,
I understand your concept for going back to stock. But, I don't get why I have to relock the bootloader. What I mean is, is that necessary for the OTA to work? I thought you only need the stock recovery for the OTA to work. Also, once you have done OTA update, and you want to root the phone again. The downsize is you have to unlock the bootloader again, which will wipe the phone completely and you will have to restore everything, which wastes times.
I like the idea of just restoring the stock recovery, do the OTA upgrade, then flash custom recovery to gain root again. I don't mind repeating that process for each update. But to relock/unlock the bootloader, having to wipe everything is a hassle. Please clarify. Thank you for your help.
Click to expand...
Click to collapse
Lol.. Yea if S-On relock Bootloader for RUU.
But no you don't need to relock the Bootloader for OTA updates S-On or s-off Sorry for the confusion I was going back n forth with another user and got you mixed up.
Sent from my HTC One_M8 using Tapatalk
vi6s said:
Ok, thank you for the reply. That clears up a little. I can just flash stock recovery every time I want to update. I was able to find a thread that has all the stock recovery file. I have a quick question. Does any version of stock recovery will work? or you want the one that match your current stock recovery.
Click to expand...
Click to collapse
You need the stock recovery that correspond to your stock software. AT&T software is x.xx.502, and I don't see any corresponding recoveries in exocet's stock nandroid collection, but 1.12.502 and 1.58.502 stock recoveries are posted here: http://forum.xda-developers.com/att-htc-one-m8/development/att-stock-backups-recoveries-otas-t2855966
Also, while eluded to above, it should be clearly stated, no /system files may be modified, in order for OTA to install. So depending on what you intend to change with root, you will either need to put it back to stock (if you modded any system files), restore the stock ROM with a nandroid you made, or a stock ROM posted on XDA.
Alternately, you can quickly return to stock by RUU. Although you either need to relock the bootloader or have s-off to run the RUU. And RUU will also wipe the phone.
So to sum it up, in order to OTA you need:
/system to be returned to stock (stock ROM)
stock recovery
Unlocked bootloader is OK
Root is okay (you will lose root after the OTA)
Hi All
I have a nexus 9 with an unlocked bootloader, root (from CF auto-root), and TWRP installed, currently on 5.0.1 LRX22C. I have read this means that I will not be able to complete an OTA due to lack of stock recovery and changes within the system files that the OTA will check.
So my question is how much of stock do I have to return to be able to do the OTA to 5.0.2 and 5.1 later today. I am hoping that I won't have to do a factory reset and wipe all the files and apps, but if so nevermind.
Do I have to relock the bootloader?
Do I have to flash back to stock completely or can I just flash a stock recovery?
If I wait will a flashable zip be created by someone, that would allow me to keep unlocked and rooted?
If this has been asked before, I am sorry, I have searched but couldn't find any clear answers that were related to lollypop.
I am used to samsung phones and the nexus ADB sideloading ect. is taking me a while to get used to, so any link to a guide would be very appreciated.
Thanks for any help,
OTA appears to checksum the entire partitions, so even remount RW could have an effect (with no intentional accesses, depending how the filesystem works). However, this doesn't make a lot of sense since any update is going to struggle to replicate the same raw filesystem data reliable - maybe this is why we are seeing 5.0.2 OTAs fail on 'stock' devices.
fallen2004 said:
Hi All
I have a nexus 9 with an unlocked bootloader, root (from CF auto-root), and TWRP installed, currently on 5.0.1 LRX22C. I have read this means that I will not be able to complete an OTA due to lack of stock recovery and changes within the system files that the OTA will check.
So my question is how much of stock do I have to return to be able to do the OTA to 5.0.2 and 5.1 later today. I am hoping that I won't have to do a factory reset and wipe all the files and apps, but if so nevermind.
Do I have to relock the bootloader?
Do I have to flash back to stock completely or can I just flash a stock recovery?
If I wait will a flashable zip be created by someone, that would allow me to keep unlocked and rooted?
If this has been asked before, I am sorry, I have searched but couldn't find any clear answers that were related to lollypop.
I am used to samsung phones and the nexus ADB sideloading ect. is taking me a while to get used to, so any link to a guide would be very appreciated.
Thanks for any help,
Click to expand...
Click to collapse
Do not relock your bootloader. It is not necessary.
Since you are rooted with a custom recovery, if you want to take the OTA, you will have to fastboot flash the stock 5.0.1 system.img, recovery.img, boot.img, and vendor.img.
IMHO, it's just as easy to fastboot flash the 5.0.2 factory images and forget about the OTA.
cam30era said:
Do not relock your bootloader. It is not necessary.
Since you are rooted with a custom recovery, if you want to take the OTA, you will have to fastboot flash the stock 5.0.1 system.img, recovery.img, boot.img, and vendor.img.
IMHO, it's just as easy to fastboot flash the 5.0.2 factory images and forget about the OTA.
Click to expand...
Click to collapse
Okay well I think I will wait until the 5.1 factory image is released, backup my phone, then fastboot flash it.
I guess I will then have to reroot and add TWRP again?
fallen2004 said:
Okay well I think I will wait until the 5.1 factory image is released, backup my phone, then fastboot flash it.
I guess I will then have to reroot and add TWRP again?
Click to expand...
Click to collapse
Do it in the other order. Fastboot flash TWRP, then flash SuperSU from inside TWRP. Very easy.