Related
Hi, I have an Unlocked 32GB HTC One (BS_US001) and I'm having a hard time trying to find info about stock recoveries.
My phone currently is on stock 4.1.2, bootloader unlocked, S-Off and rooted. I was using the TWRP recovery, used to root my phone. Since the 4.3 update came out, I was searching for the stock recovery to proceed with the update, but too many different files seems to exist. I just want to install the right recovery and apply the 4.3 update, no full ROM flash.
Yesterday I flashed this recovery file (9MB) and got icons similar of those on the right of this image.
Today, I flashed this one (7.9MB) and got something like this, the little android icon.
Later, I've found another one (9.8MB).
Edit: and another one, a few bytes shorter than the third.
But now I'm little afraid of flashing again, just for the sake of it.
So, first of all, which one is the right file for my phone (yet another one)?
Second, I flash recoveries through fastboot command line (fastboot flash recovery recovery.img). Can this method and command brick my phone?
Third, how the stock recovery behaves on your phone? Both times, when I flashed the files and entered in recovery mode, my phone would boot 2 or 3 times straight into recovery mode again, until it boot itself properly, into the system. Also, recovery mode goes from the green to the red icon and awaits until I reboot the phone again.
Thanks in advance.
Final edit: For the sake of others lost in the lack of good info, I'm editing this old post.
I found some crap advices here and there. One of them was the need to relock the bootloader to accept OTAs. It doesn't make any sense, but if you are seeking help, you will take **** as good advice. Don't do it.
Another bad advice was about the stock recovery. Just open the last update you got (Downloads folder on your phone or get the OTA from HTC website) and extract the recovery.img file. Flash it and you have the proper stock recovery for your phone.
All of this is about the stock HTC One - no custom roms, no xposed changes, nothing. The only thing I did prior to this was to flash TWRP and root. That's how I want my phone for now - stock with root.
I kind of went through this today. Ended up just wiping it, running a RUU and reapplying OTAs.
I'll tell you this… after I went through this I attempted to salvage the stock recovery before rerooting etc. I was stuck trying to get fastboot to boot a recovery instead of flash one. I did find an alternate way to harvest the recovery. I got it out of the ota. I'm not done testing it yet, but my phone was still showing tampered. Flashed cwr and called it a day at that point
Sent from my HTC One
Thank you for your answer. I'm trying to avoid the whole RUU thing, but I'll keep it as a last resource, for sure. Also, I'm trying to understand more about this piece of software called recovery.
The one I sent you is pulled directly from stock 1.29.1540.16 for Dev. edition, which comes with an unlocked bootloader as well. Also, it's signed, which will allow it to be flashed whether you're s-on or off. Assuming your MID is PN0712000, with CID BS_US001, this recovery is your stock and will work. Hope it helps.
kibmikey1 said:
The one I sent you is pulled directly from stock 1.29.1540.16 for Dev. edition, which comes with an unlocked bootloader as well. Also, it's signed, which will allow it to be flashed whether you're s-on or off. Assuming your MID is PN0712000, with CID BS_US001, this recovery is your stock and will work. Hope it helps.
Click to expand...
Click to collapse
I've been running into similar issues. For the previous 2 OTA's (1540.3 --> 1540.16 & 1540.16 --> 1540.17), simply reflashed stock recovery, ran the OTA, it updated, then I flashed TWRP again. For the most recent OTA (3.22.1540.1, I think), that seems to not be working, but I can't seem to find the right recovery. I've found 1540.3's recovery, but not 1540.16 (or .17 if there was a new recovery in that OTA). Where did you end up finding it?
Thanks!
bjg222 said:
I've been running into similar issues. For the previous 2 OTA's (1540.3 --> 1540.16 & 1540.16 --> 1540.17), simply reflashed stock recovery, ran the OTA, it updated, then I flashed TWRP again. For the most recent OTA (3.22.1540.1, I think), that seems to not be working, but I can't seem to find the right recovery. I've found 1540.3's recovery, but not 1540.16 (or .17 if there was a new recovery in that OTA). Where did you end up finding it?
Thanks!
Click to expand...
Click to collapse
I pulled it directly from my decrypted RUU zip of 1540.16.
Here, there are some of stock recovery.
Check if there is the right version for you.
You have to check the versionmain on your phone
kibmikey1 said:
I pulled it directly from my decrypted RUU zip of 1540.16.
Click to expand...
Click to collapse
Would you be willing to share it? I haven't found a decrypted version of the 1540.16 RUU since Bugsy's hosting server stopped hosting downloads (The new thread only has 1540.3 last I checked).
Guich said:
Here, there are some of stock recovery.
Check if there is the right version for you.
You have to check the versionmain on your phone
Click to expand...
Click to collapse
Thanks, looks like for the dev edition, those sites only have the new recovery from the Android 4.3 updated (3.22.1540.1), though
bjg222 said:
Thanks, looks like for the dev edition, those sites only have the new recovery from the Android 4.3 updated (3.22.1540.1), though
Click to expand...
Click to collapse
Is the 3.22 in the folder
Guich said:
Is the 3.22 in the folder
Click to expand...
Click to collapse
In the Dev Edition folder, 3.22 is all that's there. Have you had any luck finding the 1.29.1540.16 recovery? That's the one I need.
bjg222 said:
In the Dev Edition folder, 3.22 is all that's there. Have you had any luck finding the 1.29.1540.16 recovery? That's the one I need.
Click to expand...
Click to collapse
1.29.1540.16 Developer Edition signed stock recovery.
Has anyone else flashed stock recovery while on custom ROM? I was pleasantly surprised to discover my SD card was wiped Is this normal, and was there some way I could have figured out this was what was going to happen? I don't really understand what stock recovery does/is for. The only other time I'd flashed stock recovery was after restoring to stock ROM from nandroid.
kibmikey1 said:
1.29.1540.16 Developer Edition signed stock recovery.
Click to expand...
Click to collapse
Awesome, thanks!
bjg222 said:
Awesome, thanks!
Click to expand...
Click to collapse
Have you had any luck with this? I have a DE 64gb and I'm in the same situation you were/are, I'm on stock recovery but I can't accept the OTA unlike the other 4.1.2 ones. Always gets stuck on the red triangle !.
arikah said:
Have you had any luck with this? I have a DE 64gb and I'm in the same situation you were/are, I'm on stock recovery but I can't accept the OTA unlike the other 4.1.2 ones. Always gets stuck on the red triangle !.
Click to expand...
Click to collapse
If you're rooted, unroot through SU, then do a factory reset and try it again.
kibmikey1 said:
If you're rooted, unroot through SU, then do a factory reset and try it again.
Click to expand...
Click to collapse
I haven't been rooted since one of the last 4.1.2 updates, because that's when I went back to stock recovery. I was able to accept those OTA packs, why is this one different? I'm really trying to save factory resets or RUU's for the absolute last ditch effort, in fact I'm more likely to stick with 4.1.2 until I can find a way to do this.
help
I have att htc one dev edition, its in soft brick state and i cny get it to do anything, i have tried running the recovery kit, and that get to the end then error 131...
could somebody please suggest some help for me please, thanks in advance
I am relatively new to the HTC. I am running a Stock rooted image with TWRP 2.6.3.0 recovery.
The OTA for 4.3 came down and whenever I start the install the phone reboots and ends up in twrp recovery and I do not know where to go from there. I tried searching the forums but the search is down at the moment.
Here comes the Noob question : A little help please as I am not sure where to go next?
I just asked almost the same question. One thing everyone says is don't take the OTA update.
I found a few places with the pre-rooted stock ROM update, but it does not include the firmware update, that is a separate flashable zip, but I'm not sure how to update the "Full Firmware w/o hboot, boot, recovery" without S-off. I don't know if doing the "full firmware update" will mess up my recovery/root.
http://forum.xda-developers.com/showthread.php?t=2467607
http://forum.xda-developers.com/showthread.php?p=46110767
generosity21 said:
I just asked almost the same question. One thing everyone says is don't take the OTA update.
I found a few places with the pre-rooted stock ROM update, but it does not include the firmware update, that is a separate flashable zip, but I'm not sure how to update the "Full Firmware w/o hboot, boot, recovery" without S-off. I don't know if doing the "full firmware update" will mess up my recovery/root.
http://forum.xda-developers.com/showthread.php?t=2467607
http://forum.xda-developers.com/showthread.php?p=46110767
Click to expand...
Click to collapse
I have been all over the forums looking at this and came up with squat.
If I take the OTA will I loose root? Can't seem to find an answer to that.
I was running an earlier version of twrp and thought that might be the issue but after updating twrp I am still at the same place. The sprint update notifications are still coming.
If I find something I will post it here.
Must be on stock firmware and recovery to take the update guys.... It has been posted numerous times. You must also ahve the stock kernel.
Yes you will lose root if you take the OTA, you always do. Also TWRP appears to be broken with 4.3, no responsive, etc, etc
jziggy101 said:
I am relatively new to the HTC. I am running a Stock rooted image with TWRP 2.6.3.0 recovery.
The OTA for 4.3 came down and whenever I start the install the phone reboots and ends up in twrp recovery and I do not know where to go from there. I tried searching the forums but the search is down at the moment.
Here comes the Noob question : A little help please as I am not sure where to go next?
Click to expand...
Click to collapse
you can't flash the update with custom recovery installed, you need thev stock recovery image which is posted numerous times in this forum
jziggy101 said:
The OTA for 4.3 came down and whenever I start the install the phone reboots and ends up in twrp recovery and I do not know where to go from there.
Click to expand...
Click to collapse
You have to have stock recovery to take the OTA
generosity21 said:
I just asked almost the same question. One thing everyone says is don't take the OTA update.
Click to expand...
Click to collapse
You can take the OTA if you are prepared for, and know what to do - also, don't take it if you are currently S-ON and ever want S-OFF because it comes with a new hboot.
jziggy101 said:
If I take the OTA will I loose root? Can't seem to find an answer to that.
Click to expand...
Click to collapse
Yes, you will probably lose root unless you are using the OTA preservation function of SuperSU and it works for you, but either way, it is easy to get it back.
Bottom line, how you take the OTA depends on whether you are S-ON or S-OFF, the latter is much easier. Assuming you are S-ON and running the Sprint stock ROM, here is what you need to do.
1. Flash stock recovery.
2. Lock the bootloader
3. Take the OTA update
4. Unlock the bootloader
5. Flash custom recovery (TWRP)
6. Flash root (SuperSU)
If you are S-off you can skip numbers 2 and 4.
Aldo101t said:
you can't flash the update with custom recovery installed, you need thev stock recovery image which is posted numerous times in this forum
Click to expand...
Click to collapse
Thanks for the replies. It's very confusing whether people are referencing the OTA update, or the tweaked, rooted downloadable update (http://forum.xda-developers.com/showthread.php?p=46110767). This forum should be friendly to questions when things are confusing.
Even with the two replies on this thread, it's still not clear to me if the downloadable (NOT OTA) updates can be flashed with a custom recovery, or what the procedure is for an S-On device regarding firmware and ROM updates. Sorry to offend anyone if they feel this has been answered somewhere in the forums, but it's still unclear to some of us.
EDIT:
@PillowMetal Thanks for the very helpful reply. I guess the next question is, is it possible to get S-Off on 1.31.651.2 without losing everything?
Kraizk said:
Must be on stock firmware and recovery to take the update guys.... It has been posted numerous times. You must also ahve the stock kernel.
Yes you will lose root if you take the OTA, you always do. Also TWRP appears to be broken with 4.3, no responsive, etc, etc
Click to expand...
Click to collapse
If your not stock ota will mess you up big time. I just rooted my HTC one on sprint with the update that was on a swap out for bad speakers . Twrp isn't responsive if you use the one in toolkit. I downloaded 2.6.3 loaded it in the data folder of toolkit installed through the toolkit and bam... I got response out of Twrp. I'll find the link and post for you guys.
Sent from my SGH-M919 using Tapatalk 4
generosity21 said:
@PillowMetal Thanks for the very helpful reply. I guess the next question is, is it possible to get S-Off on 1.31.651.2 without losing everything?
Click to expand...
Click to collapse
Not without losing everything because it requires tricking your bootloader by writing to your misc partition, then running the 1.29 RUU - http://forum.xda-developers.com/showthread.php?t=2390821
http://techerrata.com/browse/twrp2/m7wls
This is the link for people who are stock and unlocking their phone. If you're using the toolkit put it in the data folder and rename to twrp. Be careful though the other files are the same name but in capital letters! Flash it and u will have responsive twrp and rooted 4.3 ota
Sent from my SGH-M919 using Tapatalk 4
---------- Post added at 02:10 PM ---------- Previous post was at 01:34 PM ----------
Anyone having poor reception?
Sent from my SGH-M919 using Tapatalk 4
PillowMetal said:
Not without losing everything because it requires tricking your bootloader by writing to your misc partition, then running the 1.29 RUU - http://forum.xda-developers.com/showthread.php?t=2390821
Click to expand...
Click to collapse
Tried this once more, and successfully got S-off without downgrading anything, as a few others have reported.
http://forum.xda-developers.com/showthread.php?t=2314582
Brand new device Stock 1.29 Rom Uninstalled SuperSU Unrooted for Updates
PillowMetal said:
You have to have stock recovery to take the OTA
You can take the OTA if you are prepared for, and know what to do - also, don't take it if you are currently S-ON and ever want S-OFF because it comes with a new hboot.
Yes, you will probably lose root unless you are using the OTA preservation function of SuperSU and it works for you, but either way, it is easy to get it back.
Bottom line, how you take the OTA depends on whether you are S-ON or S-OFF, the latter is much easier. Assuming you are S-ON and running the Sprint stock ROM, here is what you need to do.
1. Flash stock recovery.
2. Lock the bootloader
3. Take the OTA update
4. Unlock the bootloader
5. Flash custom recovery (TWRP)
6. Flash root (SuperSU)
If you are S-off you can skip numbers 2 and 4.
Click to expand...
Click to collapse
Think I messed up a step in my attempt to return to unroot to be ready to get the 4.3 jellybean update. I was stock rom 1.29, rooted, SuperSU, twerp 2.6.3. Unlocked sim. I unistalled SuperSU using the full unroot option and relocked the bootloader. When the phone attempts to update it reboots into the bootloader straight into fastboot. Will not reboot and stay in hboot. Recovery option does nothing. Do I even want the ota 1.31? Do I just skip the OTA 1.31 and get the 4.3 jellybean update. I'm new first Android phone. Sorry for the idiocy I have portrayed here. Hope someone can help with knowledge of OTA's and Jellybean update. My problem seems so simple compared to all the other posts I read but I can't seem to figure it out on my own. Thanks everyone
upowersystems said:
Think I messed up a step in my attempt to return to unroot to be ready to get the 4.3 jellybean update. I was stock rom 1.29, rooted, SuperSU, twerp 2.6.3. Unlocked sim. I unistalled SuperSU using the full unroot option and relocked the bootloader. When the phone attempts to update it reboots into the bootloader straight into fastboot. Will not reboot and stay in hboot. Recovery option does nothing. Do I even want the ota 1.31? Do I just skip the OTA 1.31 and get the 4.3 jellybean update. I'm new first Android phone. Sorry for the idiocy I have portrayed here. Hope someone can help with knowledge of OTA's and Jellybean update. My problem seems so simple compared to all the other posts I read but I can't seem to figure it out on my own. Thanks everyone
Click to expand...
Click to collapse
Did you flash stock recovery? The OTA needs that. You did not need to unroot though. Also not sure if having an unlocked SIM interferes with OTA, never performed that myself. Since we don't have RUUs for anything later than 1.29, then yes, you will need to take the 1.31 OTA update first, then the 3.04 update.
Twerp to Stock recovery
PillowMetal said:
Did you flash stock recovery? The OTA needs that. You did not need to unroot though. Also not sure if having an unlocked SIM interferes with OTA, never performed that myself. Since we don't have RUUs for anything later than 1.29, then yes, you will need to take the 1.31 OTA update first, then the 3.04 update.
Click to expand...
Click to collapse
Darn, no I did not flash the stock recovery. Also I read another thread said I needed to unroot!lol So I was back tracing my steps to unroot, so I thought.. I did save the original backup before installing Twerp 2.6.3 and rooting so its in there if I can get to it. I really dont know how to proceed from here. There are no options in the bootloader to proceed.
Twerp vs Stock recovery
PillowMetal said:
Did you flash stock recovery? The OTA needs that. You did not need to unroot though. Also not sure if having an unlocked SIM interferes with OTA, never performed that myself. Since we don't have RUUs for anything later than 1.29, then yes, you will need to take the 1.31 OTA update first, then the 3.04 update.
Click to expand...
Click to collapse
Do I need to figure out how to flash or return to stock recovery from Twerp or can I simploy flash the 1.29 ruu back in to the device for a return to stock?
Twerp 2.6.3
PillowMetal said:
Did you flash stock recovery? The OTA needs that. You did not need to unroot though. Also not sure if having an unlocked SIM interferes with OTA, never performed that myself. Since we don't have RUUs for anything later than 1.29, then yes, you will need to take the 1.31 OTA update first, then the 3.04 update.
Click to expand...
Click to collapse
Kraizk said:
Must be on stock firmware and recovery to take the update guys.... It has been posted numerous times. You must also ahve the stock kernel.
Yes you will lose root if you take the OTA, you always do. Also TWRP appears to be broken with 4.3, no responsive, etc, etc
Click to expand...
Click to collapse
Maybe you can help. Will a re-install of the stock ruu 1.29 without removing twerp 2.6.3 and reverting to stock recovery cause issues.. Will this just completely re-install everything including stock Recovery or will twerp remain. I am running stock 1.29 rom, did save an original backup when I loaded twerp. How would I get in it to load it. Then I would not need to load the complete ruu. When I try for the ota it used to reboot to twerp. Since I unrooted it reboots to bootloader and there are NO options for load, Recovery option doesnt work. I have asked this question on several threads no one seems to know or its too simple for them to reply since I'm a newb. Thanks
upowersystems said:
Maybe you can help. Will a re-install of the stock ruu 1.29 without removing twerp 2.6.3 and reverting to stock recovery cause issues.. Will this just completely re-install everything including stock Recovery or will twerp remain. I am running stock 1.29 rom, did save an original backup when I loaded twerp. How would I get in it to load it. Then I would not need to load the complete ruu. When I try for the ota it used to reboot to twerp. Since I unrooted it reboots to bootloader and there are NO options for load, Recovery option doesnt work. I have asked this question on several threads no one seems to know or its too simple for them to reply since I'm a newb. Thanks
Click to expand...
Click to collapse
Are you S-Off? Is so, the easiest way to to get up to date for you would be to RUU back to 1.29 which will restore everything on your phone back to stock including recovery. Make sure you copy anything you want to keep off your phone's internal memory (/sdcard) because it will wipe that too.
But from there, you can then easily take the OTA update for 1.31, then take the update for 3.04. Now you have the latest and greatest and can now flash TWRP, SuperSU, and any 4.3 ROM you want. With S-Off, you do not need the bootloader unlocked, but if you want to, you can flash an old hboot 1.29 from May or earlier and use revone -u, or go through htcdev to unlock. But like I said, totally unnecessary and more of a pain for me than it is worth.
Now, if you are S-ON, that is a totally different story, you cannot flash back to 1.29 RUU unless you still on 1.29 and have not updated to 1.31 yet. If you are currently on 1.31 you will have to try and restore the backup you said you had through TWRP, flash stock recovery from fastboot, re-lock your bootloader and all kinds of other crap to get to 3.04 and unlocked and rooted again.
You would have to tell me more about what condition your phone is currently in. hboot version? recovery custom or stock? ROM version installed? S-On or S-Off, etc.
Current State
PillowMetal said:
Are you S-Off? Is so, the easiest way to to get up to date for you would be to RUU back to 1.29 which will restore everything on your phone back to stock including recovery. Make sure you copy anything you want to keep off your phone's internal memory (/sdcard) because it will wipe that too.
But from there, you can then easily take the OTA update for 1.31, then take the update for 3.04. Now you have the latest and greatest and can now flash TWRP, SuperSU, and any 4.3 ROM you want. With S-Off, you do not need the bootloader unlocked, but if you want to, you can flash an old hboot 1.29 from May or earlier and use revone -u, or go through htcdev to unlock. But like I said, totally unnecessary and more of a pain for me than it is worth.
Now, if you are S-ON, that is a totally different story, you cannot flash back to 1.29 RUU unless you still on 1.29 and have not updated to 1.31 yet. If you are currently on 1.31 you will have to try and restore the backup you said you had through TWRP, flash stock recovery from fastboot, re-lock your bootloader and all kinds of other crap to get to 3.04 and unlocked and rooted again.
You would have to tell me more about what condition your phone is currently in. hboot version? recovery custom or stock? ROM version installed? S-On or S-Off, etc.
Click to expand...
Click to collapse
Was told if I un-rooted and relocked the bootloader I should be able to update. This is a brand new phone. No data to worry about losing.
Currently:
Stock ROM 1.29, S-On, (Was rooted) Now Unrooted
Hboot 1.44 (Bootloader relocked)
Twerp Recovery (although with attempt to update to 1.31 twerp did not open as it did in prior attempts to update before unroot)
Now You have opened an interesting subject. Do I need to S-off before any updates to defeat the new hboot? New stuff is being written for the new hboot as we speak right? Read a thread last night about it. Sounded like they could s-off a 1.31 and I wouldn't need to worry about s-off'ing before upgrading. It also seems like I should be able to re load the backup of the stock recovery somehow and skip the complete load of the ruu 1.29 since I am already running it. I am probably making somethong more difficult than it needs to be but I would like to learn the little details. My first Android here. Want to learn quickly here as I Also bought the New 4g LTE Nexus 7 tablet with jelly bean. I get 4g LTE from T-mobile and just hotspot my phone.
upowersystems said:
Was told if I un-rooted and relocked the bootloader I should be able to update. This is a brand new phone. No data to worry about losing.
Currently:
Stock ROM 1.29, S-On, (Was rooted) Now Unrooted
Hboot 1.44 (Bootloader relocked)
Twerp Recovery (although with attempt to update to 1.31 twerp did not open as it did in prior attempts to update before unroot)
Now You have opened an interesting subject. Do I need to S-off before any updates to defeat the new hboot? New stuff is being written for the new hboot as we speak right? Read a thread last night about it. Sounded like they could s-off a 1.31 and I wouldn't need to worry about s-off'ing before upgrading. It also seems like I should be able to re load the backup of the stock recovery somehow and skip the complete load of the ruu 1.29 since I am already running it. I am probably making somethong more difficult than it needs to be but I would like to learn the little details. My first Android here. Want to learn quickly here as I Also bought the New 4g LTE Nexus 7 tablet with jelly bean. I get 4g LTE from T-mobile and just hotspot my phone.
Click to expand...
Click to collapse
If you don't want to go the RUU route, then the condition your phone is currently in would only require you to flash stock recovery from 1.29.651.10 (which I got from the actual OTA file). The problem is that your bootloader is now locked and your are S-ON, so you will not be able to flash stock recovery unless you unlock again. If you still have the unlock.bin file from htcdev, that will still work if was done on your current hboot version, otherwise, you would have to visit the site again. Then flash stock recovery, and relock bootloader again. Then the 1.31 update will succeed followed by the 3.04 update.
As far as S-OFF, if you ever want it, you should get it now before updating to anything - even 1.31 (as long as the date on your hboot is May 2013 or earlier). Because, you WILL get the new hboots when you update to 1.31 and 3.04 and since you are S-ON, you will be stuck with it. There is no guarantee that you will ever be able to get S-OFF again with the new hboots. People on hboot 1.54 have been waiting and clamoring for months and there has been no progress and other phones have never even been able to get S-OFF.
Using revone to S-OFF will not wipe your phone or remove anything, it does not require root, and it you do not need to be unlocked. I have performed it from the computer 3 times on Sprint phones and even have made a post about how to make it succeed. There is also a video showing how it can be done on the phone too via terminal emulator, but that method requires root.
Having S-OFF just makes life so much easier, but with it carries great responsibility because security has been turned off and you need to know what you are flashing or you can run into trouble. But as long as you can get to the bootloader, you can recover.
PillowMetal said:
You have to have stock recovery to take the OTA
You can take the OTA if you are prepared for, and know what to do - also, don't take it if you are currently S-ON and ever want S-OFF because it comes with a new hboot.
Yes, you will probably lose root unless you are using the OTA preservation function of SuperSU and it works for you, but either way, it is easy to get it back.
Bottom line, how you take the OTA depends on whether you are S-ON or S-OFF, the latter is much easier. Assuming you are S-ON and running the Sprint stock ROM, here is what you need to do.
1. Flash stock recovery.
2. Lock the bootloader
3. Take the OTA update
4. Unlock the bootloader
5. Flash custom recovery (TWRP)
6. Flash root (SuperSU)
If you are S-off you can skip numbers 2 and 4.
Click to expand...
Click to collapse
On the att variant you don't need to relock the boot loader to ota.
Sent from my XT1058 using Tapatalk 2
Hi All,
I have an ATT m7 that I'm running on GPE 4.4 (build KTR16S) with TWRP and the bulletproof kernel.
I'm getting notifications for the 4.4.2 update, and I'd like to install it, but obviously with TWRP installed, it can't automate the update process. So, a few questions:
1) Is it okay for me to manually install the update after locating it from my own recovery?
2) Where is the update stored, so that I can track it down within TWRP to flash?
Thanks guys!
karankshah said:
Hi All,
I have an ATT m7 that I'm running on GPE 4.4 (build KTR16S) with TWRP and the bulletproof kernel.
I'm getting notifications for the 4.4.2 update, and I'd like to install it, but obviously with TWRP installed, it can't automate the update process. So, a few questions:
1) Is it okay for me to manually install the update after locating it from my own recovery?
2) Where is the update stored, so that I can track it down within TWRP to flash?
Thanks guys!
Click to expand...
Click to collapse
Mines in the downloads folder
karankshah said:
Hi All,
I have an ATT m7 that I'm running on GPE 4.4 (build KTR16S) with TWRP and the bulletproof kernel.
I'm getting notifications for the 4.4.2 update, and I'd like to install it, but obviously with TWRP installed, it can't automate the update process. So, a few questions:
1) Is it okay for me to manually install the update after locating it from my own recovery?
2) Where is the update stored, so that I can track it down within TWRP to flash?
Thanks guys!
Click to expand...
Click to collapse
you can't flash ota updates with twrp. only stock recovery. like mb_guy said, the ota are stored in the ''downloads'' folder. When you apply the ota, the file is deleted automatically.
You can manually flash ota updates from stock recovery. Move the ota.zip to android/obb. boot phone in stock recovery, select ''apply from phone storage'' ---> /obb --> your ota.zip
For some reason the update is in the /cache/ directory instead of in the downloads directory.
How do I switch to the standard recovery? Do I need to reflash the entire ROM or is there another flashable file?
karankshah said:
For some reason the update is in the /cache/ directory instead of in the downloads directory.
How do I switch to the standard recovery? Do I need to reflash the entire ROM or is there another flashable file?
Click to expand...
Click to collapse
you can flash stock recovery the same way you flashed custom recovery:
Code:
fastboot flash recovery name_of_recovery.img
you must flash the stock recovery that match your firmware version which you can find with a:
Code:
fastboot getvar all
karankshah said:
For some reason the update is in the /cache/ directory instead of in the downloads directory.
How do I switch to the standard recovery? Do I need to reflash the entire ROM or is there another flashable file?
Click to expand...
Click to collapse
Stock recovery from here
http://forum.xda-developers.com/showthread.php?t=2545227
bored_stupid said:
Stock recovery from here
http://forum.xda-developers.com/showthread.php?t=2545227
Click to expand...
Click to collapse
Thanks for the help guys. I spent way too long trying to figure out how to get my computer to recognize my phone while in fastboot so I could get the main version number.
I finally was able to figure that out, but I'm not seeing my version (1.26.502.10) on the page.
Are any of the other recoveries usable? Or does this mean that I would have to go back to stock ATT, take the OTA update ATT was pushing a loong time ago, and then re-root to then flash a GE rom?
karankshah said:
Thanks for the help guys. I spent way too long trying to figure out how to get my computer to recognize my phone while in fastboot so I could get the main version number.
I finally was able to figure that out, but I'm not seeing my version (1.26.502.10) on the page.
Are any of the other recoveries usable? Or does this mean that I would have to go back to stock ATT, take the OTA update ATT was pushing a loong time ago, and then re-root to then flash a GE rom?
Click to expand...
Click to collapse
There is a rom dump here. once downloaded, you should be able to extract the stock recovery from there.
http://forum.xda-developers.com/showthread.php?p=40764389&highlight=1+26+502+10#post40764389
bored_stupid said:
There is a rom dump here. once downloaded, you should be able to extract the stock recovery from there.
http://forum.xda-developers.com/showthread.php?p=40764389&highlight=1+26+502+10#post40764389
Click to expand...
Click to collapse
It looks like he's pulled the 1.26.502.10 rom - know of any other places it might be? Most of the 502.10 roms I'm seeing now are pre-rooted.
karankshah said:
It looks like he's pulled the 1.26.502.10 rom - know of any other places it might be? Most of the 502.10 roms I'm seeing now are pre-rooted.
Click to expand...
Click to collapse
I can only find pre-rooted roms two. however, if the rom has the SuperSU installed, you can do a full unroot from the SuperSU settings
bored_stupid said:
I can only find pre-rooted roms two. however, if the rom has the SuperSU installed, you can do a full unroot from the SuperSU settings
Click to expand...
Click to collapse
That might be a good idea. Do you know if that removes S-OFF?
bored_stupid said:
I can only find pre-rooted roms two. however, if the rom has the SuperSU installed, you can do a full unroot from the SuperSU settings
Click to expand...
Click to collapse
Ah - nevermind - just found out it won't reinstall the stock recovery, which means the OTA update won't stick anyway. Looks like the only way is the long way.
karankshah said:
Ah - nevermind - just found out it won't reinstall the stock recovery, which means the OTA update won't stick anyway. Looks like the only way is the long way.
Click to expand...
Click to collapse
If you unzip the OTA the stock recovery should be in there..
Sent from my GT-I9505 using XDA Premium 4 mobile app
karankshah said:
Thanks for the help guys. I spent way too long trying to figure out how to get my computer to recognize my phone while in fastboot so I could get the main version number.
I finally was able to figure that out, but I'm not seeing my version (1.26.502.10) on the page.
Are any of the other recoveries usable? Or does this mean that I would have to go back to stock ATT, take the OTA update ATT was pushing a loong time ago, and then re-root to then flash a GE rom?
Click to expand...
Click to collapse
Here is your stock recovery
http://www.androidfilehost.com/?fid=23501681358538645
I have a Verizon Nexus 6 that is rooted, unlocked, custom TWRP recovery and stock running 5.1 build LMY47E and I am getting the OTA notification for the 5.1.1 update. I have searched a good deal of places and haven't found the answer to how I might go about getting the update. I have been out of the rooting game for several years, so I am rusty and need a little help. I wasn't sure if there was a way to take the update and stay rooted or if I have to completely undo everything back to stock. Any info would be a great help and appreciated.
I could be mistaken, but I don't think that you can take an OTA amd remain rooted. I think it will break root, and you will have to re-root.
What I would suggest is to just flash a custom ROM that is build on 5.1.1 like Beans' PureNexus. That is what I am running, and it is great.
http://forum.xda-developers.com/nexus-6/development/rom-pure-nexus-project-t3148214
evolefty said:
I have a Verizon Nexus 6 that is rooted, unlocked, custom TWRP recovery and stock running 5.1 build LMY47E and I am getting the OTA notification for the 5.1.1 update. I have searched a good deal of places and haven't found the answer to how I might go about getting the update. I have been out of the rooting game for several years, so I am rusty and need a little help. I wasn't sure if there was a way to take the update and stay rooted or if I have to completely undo everything back to stock. Any info would be a great help and appreciated.
Click to expand...
Click to collapse
a.demarco said:
I could be mistaken, but I don't think that you can take an OTA amd remain rooted. I think it will break root, and you will have to re-root.
What I would suggest is to just flash a custom ROM that is build on 5.1.1 like Beans' PureNexus. That is what I am running, and it is great.
http://forum.xda-developers.com/nexus-6/development/rom-pure-nexus-project-t3148214
Click to expand...
Click to collapse
When installing a recovery, the updater script looks at system and boot. This means that you can not be rooted and and have the stock, encrypted kernel. You also need to have stock recovery to install the OTA.
You can download the 5.1.1 factory image from Google and flash the boot.img, system.img, bootloader.img, and radio.img. Then, while still in bootloader, select "recovery" and you will boot to TWRP where you can flash the SuperSU.zip.
a.demarco said:
I could be mistaken, but I don't think that you can take an OTA amd remain rooted. I think it will break root, and you will have to re-root.
What I would suggest is to just flash a custom ROM that is build on 5.1.1 like Beans' PureNexus. That is what I am running, and it is great.
http://forum.xda-developers.com/nexus-6/development/rom-pure-nexus-project-t3148214
Click to expand...
Click to collapse
The OTA will not install when the device is rooted
cam30era said:
When installing a recovery, the updater script looks at system and boot. This means that you can not be rooted and and have the stock, encrypted kernel. You also need to have stock recovery to install the OTA.
You can download the 5.1.1 factory image from Google and flash the boot.img, system.img, bootloader.img, and radio.img. Then, while still in bootloader, select "recovery" and you will boot to TWRP where you can flash the SuperSU.zip.
Click to expand...
Click to collapse
Just checked again and yes I am rooted, with TWRP and I also checked and the device is not encrypted, so maybe that is why I am getting the notification. I really appreciate your input on getting the update installed.
evolefty said:
Just checked again and yes I am rooted, with TWRP and I also checked and the device is not encrypted, so maybe that is why I am getting the notification. I really appreciate your input on getting the update installed.
Click to expand...
Click to collapse
You'll get the notification. You just can't flash it.
I'm not sure there's been a full, satisfactory answer to this thread (or a few others). Would using something like Nexus Root Toolkit to 1) unroot 2) restore stock recovery, 3) accept the OTA. Will this work?
- Does this relock the bootloader? (Would we then have to unlock, thus wiping the device?)
- Can we successfully re-root and flash recovery? (Or will new 5.1.1 versions be needed?)
At some point, to get 5.1.1 going, should I just backup and flash the whole bloody image from Google?
DogzOfWar said:
I'm not sure there's been a full, satisfactory answer to this thread (or a few others). Would using something like Nexus Root Toolkit to 1) unroot 2) restore stock recovery, 3) accept the OTA. Will this work?
- Does this relock the bootloader? (Would we then have to unlock, thus wiping the device?)
- Can we successfully re-root and flash recovery? (Or will new 5.1.1 versions be needed?)
At some point, to get 5.1.1 going, should I just backup and flash the whole bloody image from Google?
Click to expand...
Click to collapse
- OTA`s will not install if the sytem, boot and recovery are modified in any way.
- Reflashing the stock image will NOT lock the bootloader
- And yes you can flash a custom recovery and reroot after updating.
Or flash the latest stock rom with TWRP from here http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052.
gee2012 said:
- OTA`s will not install if the sytem, boot and recovery are modified in any way.
- Reflashing the stock image will NOT lock the bootloader
- And yes you can flash a custom recovery and reroot after updating.
Or flash the latest stock rom with TWRP from here http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052.
Click to expand...
Click to collapse
So the question that started this thread: My system is technically modified. Can I unroot and replace recovery, and now be in a sufficiently "unmodified" state? OR, do I have to lock the bootloader in order for the OTA to continue?
I think the OP and myself are trying to do the same thing: We're lazy, we don't want to wipe, we don't want to lose data, we just want the OTA without having to reflash the whole thing. Does anyone know if this is possible?
DogzOfWar said:
So the question that started this thread: My system is technically modified. Can I unroot and replace recovery, and now be in a sufficiently "unmodified" state? OR, do I have to lock the bootloader in order for the OTA to continue?
I think the OP and myself are trying to do the same thing: We're lazy, we don't want to wipe, we don't want to lose data, we just want the OTA without having to reflash the whole thing. Does anyone know if this is possible?
Click to expand...
Click to collapse
Best/easiest is to:
- fastboot erase system
- fastboot flash system system.img
- flash the stock boot and recovery.img if needed
- adb sideload the OTA in stock recovery
This will not wipe your device
And you don`t have to lock the bootloader ever unless you have too RMA it or send it in for service, OTA`s will even install with a unlocked bootloader.
DogzOfWar said:
So the question that started this thread: My system is technically modified. Can I unroot and replace recovery, and now be in a sufficiently "unmodified" state? OR, do I have to lock the bootloader in order for the OTA to continue?
I think the OP and myself are trying to do the same thing: We're lazy, we don't want to wipe, we don't want to lose data, we just want the OTA without having to reflash the whole thing. Does anyone know if this is possible?
Click to expand...
Click to collapse
Supplementing that: using the "unroot" function in SuperSU is not sufficient with Lollipop. It still leaves the vestiges of a few modified files that will cause an OTA to fail.
gee2012 said:
Best/easiest is to:
- fastboot erase system
- fastboot flash system system.img
- flash the stock boot and recovery.img if needed
- adb sideload the OTA in stock recovery
This will not wipe your device
And you don`t have to lock the bootloader ever unless you have too RMA it or send it in for service, OTA`s will even install with a unlocked bootloader.
Click to expand...
Click to collapse
gee2012 said:
Best/easiest is to:
- fastboot erase system
- fastboot flash system system.img
- flash the stock boot and recovery.img if needed
- adb sideload the OTA in stock recovery
This will not wipe your device
And you don`t have to lock the bootloader ever unless you have too RMA it or send it in for service, OTA`s will even install with a unlocked bootloader.
Click to expand...
Click to collapse
Thanks for the info and I really appreciate your input. What are your feelings on using Wug's toolkit to unroot and go back stock, take the update, then re-root and flash the custom recovery. I have never used a toolkit before, but that seems to be the popular method. Like I said at the beginning I am new to all of this, the last device I rooted and really messed around with was the droid x so bear with me as I am learning. I am currently reading about Wug's and will look at the method you just spoke of, but any info would be great.
evolefty said:
Thanks for the info and I really appreciate your input. What are your feelings on using Wug's toolkit to unroot and go back stock, take the update, then re-root and flash the custom recovery. I have never used a toolkit before, but that seems to be the popular method. Like I said at the beginning I am new to all of this, the last device I rooted and really messed around with was the droid x so bear with me as I am learning. I am currently reading about Wug's and will look at the method you just spoke of, but any info would be great.
Click to expand...
Click to collapse
I don`t like Toolkits tbh because like with all automated applications the unexperienced user has no idea whats going/has zero control over whats happening and if something goes wrong they can`t fix the issue. Imo its best to learn adb/fastboot/sideload.
gee2012 said:
I don`t like Toolkits tbh because like with all automated applications the unexperienced user has no idea whats going/has zero control over whats happening and if something goes wrong they can`t fix the issue. Imo its best to learn adb/fastboot/sideload.
Click to expand...
Click to collapse
Gotcha, and completely understand. I will do some reading on that method and again thanks for your help.
evolefty said:
Gotcha, and completely understand. I will do some reading on that method and again thanks for your help.
Click to expand...
Click to collapse
Read the sticky threads http://forum.xda-developers.com/nexus-6/general/nexus-6-sticky-roll-thread-t3061066, this is a good start. Adb and fastboot isn`t that hard but its very safe and effective
gee2012 said:
Read the sticky threads http://forum.xda-developers.com/nexus-6/general/nexus-6-sticky-roll-thread-t3061066, this is a good start. Adb and fastboot isn`t that hard but its very safe and effective
Click to expand...
Click to collapse
Will do, and that is the method I used to root for the simple fact to learn.
evolefty said:
Will do, and that is the method I used to root for the simple fact to learn.
Click to expand...
Click to collapse
Good luck
gee2012 said:
- OTA`s will not install if the sytem, boot and recovery are modified in any way.
- Reflashing the stock image will NOT lock the bootloader
- And yes you can flash a custom recovery and reroot after updating.
Or flash the latest stock rom with TWRP from here http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052.
Click to expand...
Click to collapse
In that link you sent I am not seeing the VZW version of 5.1.1. Can we use the "International" version?
Thank you.
needoZ said:
In that link you sent I am not seeing the VZW version of 5.1.1. Can we use the "International" version?
Thank you.
Click to expand...
Click to collapse
Yes, use the LMY47Z build.
DogzOfWar said:
So the question that started this thread: My system is technically modified. Can I unroot and replace recovery, and now be in a sufficiently "unmodified" state? OR, do I have to lock the bootloader in order for the OTA to continue?
I think the OP and myself are trying to do the same thing: We're lazy, we don't want to wipe, we don't want to lose data, we just want the OTA without having to reflash the whole thing. Does anyone know if this is possible?
Click to expand...
Click to collapse
Bootloader does not have to be locked to take an OTA. You can not be rooted or modified in any way however.
gee2012 said:
I don`t like Toolkits tbh because like with all automated applications the unexperienced user has no idea whats going/has zero control over whats happening and if something goes wrong they can`t fix the issue. Imo its best to learn adb/fastboot/sideload.
Click to expand...
Click to collapse
While I agree, once you have "paid your dues" and flashed without automation then the NRT is a great tool, so long as you have an understanding of what it is doing.
I had rooted my K3 note by replacing the stock recovery with TWRP with the help of SP Flash tools and installing SuperSU.
Recently the Marshmallow OTA update rolled out for the Indian K3 Note. However, when I try installing it, the phone simply reboots without updating. Going through the forums, I believe that this is due to the absence of the stock recovery which seems to be required for installing the update.
I also believe that if I try manually flashing the OTA update zip through TWRP, it'll probably fail, since this is what most people have attempted to do so have experienced.
So how do I go about installing the OTA update now? Do I have to reinstall the stock recovery or is there a workaround via TWRP? If I do have to unroot and install stock recovery, how do I go about it? I don't want to go through the hassles of unrooting my phone to install this update, neither do I want to apply any unofficial ROMs such as the cuoco92 one.
Suggest me some solutions guys..
Thanks in advance
tirtha2shredder said:
I had rooted my K3 note by replacing the stock recovery with TWRP with the help of SP Flash tools and installing SuperSU.
Recently the Marshmallow OTA update rolled out for the Indian K3 Note. However, when I try installing it, the phone simply reboots without updating. Going through the forums, I believe that this is due to the absence of the stock recovery which seems to be required for installing the update.
I also believe that if I try manually flashing the OTA update zip through TWRP, it'll probably fail, since this is what most people have attempted to do so have experienced.
So how do I go about installing the OTA update now? Do I have to reinstall the stock recovery or is there a workaround via TWRP? If I do have to unroot and install stock recovery, how do I go about it? I don't want to go through the hassles of unrooting my phone to install this update, neither do I want to apply any unofficial ROMs such as the cuoco92 one.
Suggest me some solutions guys..
Thanks in advance
Click to expand...
Click to collapse
Try to download official mm rom for indian k3 and flash via twrp or sp flash tool..
adikri said:
Try to download official mm rom for indian k3 and flash via twrp or sp flash tool..
Click to expand...
Click to collapse
Have you tried doing the same? Won't that require the phone to be unrooted?
tirtha2shredder said:
Have you tried doing the same? Won't that require the phone to be unrooted?
Click to expand...
Click to collapse
You will be downloading whole new mm official Indian lenovo rom..
Obviously there will be no root after new rom but you have re-root after finishing boot.. :laugh:
Its easy to download and install updated rom and re-root..
adikri said:
You will be downloading whole new mm official Indian lenovo rom..
Obviously there will be no root after new rom but you have re-root after finishing boot.. :laugh:
Its easy to download and install updated rom and re-root..
Click to expand...
Click to collapse
Stop spreading misinformation mate, if you don't know what you're talking about. I've spent the whole evening looking through the internet regarding my query where all of them say that the OTA update only works with stock recovery. Flashing the official OTA update with TWRP will most definitely not work.
There is no definitive article or post which explains how to do it with a rooted phone and custom recovery, which is what I'm looking for.
tirtha2shredder said:
Stop spreading misinformation mate, if you don't know what you're talking about. I've spent the whole evening looking through the internet regarding my query where all of them say that the OTA update only works with stock recovery. Flashing the official OTA update with TWRP will most definitely not work.
There is no definitive article or post which explains how to do it with a rooted phone and custom recovery, which is what I'm looking for.
Click to expand...
Click to collapse
Obviously there is nothing..
And you won't find anything so.. choose your side..