Thank you guys in advance for your help but I just had a few questions. I am running 4.4.2 currently with the stock rom rooted and unlocked bootloader. I have however issued a few Mods such as extreme power saving and built in tether. Can I just load the 4.4.4 firmware and radios, switch back to stock recovery and take the OTA to 4.4.4 without having to wipe anything or since I have used some mods do I now have to wipe my device and put everything back after getting the 4.4.4 update. The reason I ask is I like having the stock features while just using google now launcher on top of sense. Also would any of you have a recommendation on a ROM to achieve this same thing so I dont have to go through this everytime I want to take the newest OTA if it is not possible to take without wiping.
jpgetter said:
Thank you guys in advance for your help but I just had a few questions. I am running 4.4.2 currently with the stock rom rooted and unlocked bootloader. I have however issued a few Mods such as extreme power saving and built in tether. Can I just load the 4.4.4 firmware and radios, switch back to stock recovery and take the OTA to 4.4.4 without having to wipe anything or since I have used some mods do I now have to wipe my device and put everything back after getting the 4.4.4 update. The reason I ask is I like having the stock features while just using google now launcher on top of sense. Also would any of you have a recommendation on a ROM to achieve this same thing so I dont have to go through this everytime I want to take the newest OTA if it is not possible to take without wiping.
Click to expand...
Click to collapse
Flash the ruu here. That will get you to 4.4.3 the easy way and make you 100% stock so you can take the ruu. Then flash twrp and flash su or the rooted Rom of your choosing.
The RUU is one way to go, although I would never update via OTA...
Another would be to flash the firmware and radios from here:
http://forum.xda-developers.com/showthread.php?t=2723159
And then Scott's rooted stock rom from here:
http://forum.xda-developers.com/showthread.php?t=2914922
He usually has them up a few hours after a new OTA has been released. Even better - try his stock, debloated CleanROM once it's out.
This way you can keep your recovery. You can even try to just flash the 4.4.4 firmware and radios and see if it runs your current 4.2 ROM ok. But I would not update the rom from version to version without a wipe.
The setup is the price to pay for getting a new and hopefully better Android version.
Related
Hi am having a problem after going back to telstra stock after being on rohans JB build 3. It was really bad at connecting on LTE so I wanted to go back to stock where I have less problems. So now the 4.0.4 OTA update is available which fixes the one of the main reasons I found a ROM, that stupid settings bar.
However when I reboot to install the OTA it just boots into TWRP (v 2.2.2). I cant manually apply update from within recovery. It just gives an error. If I reboot from recovery nothing is applied.
Android v 4.0.3, software version 1.89.841.9
Do I have to get rid off TWRP or find a RUU and and apply that image? Was there some boot locking thing I need to do through abd to get the OTA to work?
piscario said:
Hi am having a problem after going back to telstra stock after being on rohans JB build 3. It was really bad at connecting on LTE so I wanted to go back to stock where I have less problems. So now the 4.0.4 OTA update is available which fixes the one of the main reasons I found a ROM, that stupid settings bar.
However when I reboot to install the OTA it just boots into TWRP (v 2.2.2). I cant manually apply update from within recovery. It just gives an error. If I reboot from recovery nothing is applied.
Android v 4.0.3, software version 1.89.841.9
Do I have to get rid off TWRP or find a RUU and and apply that image? Was there some boot locking thing I need to do through abd to get the OTA to work?
Click to expand...
Click to collapse
Pretty sure you have to relock your bootloader and run an RUU to get your phone to true stock. Then OTA. Although, if the RUU was based off 4.0.4 you wouldn't have to OTA. You can always re-ulock your phone after an RUU as long as you have your unlock token and/or super CID.
Did you just flash a stock ROM?
Also, pretty sure there are 4.0.4 stock ROMs out there that you could flash so you wouldn't have to relock your phone.
Butters619 said:
Pretty sure you have to relock your bootloader and run an RUU to get your phone to true stock. Then OTA. Although, if the RUU was based off 4.0.4 you wouldn't have to OTA. You can always re-ulock your phone after an RUU as long as you have your unlock token and/or super CID.
Did you just flash a stock ROM?
Also, pretty sure there are 4.0.4 stock ROMs out there that you could flash so you wouldn't have to relock your phone.
Click to expand...
Click to collapse
Thanks I restored a backup I made before flashing the ROM. Might try and find another ROM to see how 4G goes.
Fixing a connectivity issue on one custom ROM is not a good reason to go stock. I think the OTA needs stock recovery, so that is why you are getting stuck at recovery. Even if it works, you lose root. Its a step backwards, so why would you want to do that?
Just flash a ROM based on 4.0.4 from Development. You can pick a custom ROM, or a stock rooted one (safe to flash from TWRP), if you want stock.
If you are rooted, don't install a OTA or run RUU (unless you are trying to fix a soft brick). Good rule for any Android device.
A month ago I rooted the stock rom, S-OFF, and install TWRP. I tried another ROM, but it didn't really interest me. I realized, that I actually like the stock ROM.
However, now I want to install the 4.4.3 OTA update. Is that possible? If I follow the directions, the device reboots in to TWRP, but does not install the update.
How can I install the OTA update, if I have a custom recovery?
DBordello said:
A month ago I rooted the stock rom, S-OFF, and install TWRP. I tried another ROM, but it didn't really interest me. I realized, that I actually like the stock ROM.
However, now I want to install the 4.4.3 OTA update. Is that possible? If I follow the directions, the device reboots in to TWRP, but does not install the update.
How can I install the OTA update, if I have a custom recovery?
Click to expand...
Click to collapse
It appears it is impossible: http://teamw.in/officialota
I guess I will have to completely reflash.
First off, it's not impossible. There's a thread in here with firmware that you can use and update without the OTA. Second, this is the wrong sub-forum for questions.
Sent from my HTC6525LVW using Tapatalk
I'm also trying to get to 4.4.3 but after trying to re install the old recovery, it tells me I can't do the OTA.
Jeez...if you guys have soff and twrp and whatnot just flash the stock rooted rom scott gave us. Simple as that. You'll find it here in the vzw one m8 android development section.
Or alternately, if you no longer require control of you device at the lowest levels then just flash dottats RUU and magically your phone will be 100% stock.
But yeah, wrong forum.
silver04v said:
Jeez...if you guys have soff and twrp and whatnot just flash the stock rooted rom scott gave us. Simple as that. You'll find it here in the vzw one m8 android development section.
Click to expand...
Click to collapse
The reason to do the OTA, is because I am lazy. I don't feel like reinstalling all of my apps, etc. The OTA is a nice incremental upgrade.
Where can I find the stock recovery, and directions to flash back to it? It is my understanding, that if I do that, I can apply the OTA.
Hey everyone,
So for the past couple of days I've been getting the notification that 5.1.1 has been downloaded and is ready to install, but I'm running a rooted stock ROM with CWM and ElementalX kernel, so I wasn't sure what would happen if I accepted the update. So my question to you all is just that; what will happen if I OTA update? I would imagine I'll lose root access and have to re-root, but would the OTA also flash a stock kernel and get rid of CWM? Or will the update create a load of problems since I'm not completely stock?
Thanks in advance for your help.
The OTA update will fail.
As of Lollipop, you have to have everything completely stock (including the recovery) to take an OTA update. You're better off just flashing another pre-rooted ROM or custom ROM which has been updated to 5.1.1.
Elluel said:
The OTA update will fail.
As of Lollipop, you have to have everything completely stock (including the recovery) to take an OTA update. You're better off just flashing another pre-rooted ROM or custom ROM which has been updated to 5.1.1.
Click to expand...
Click to collapse
Thanks for the help!
Hello,
I have a rooted Verizon HTC One M8 running on Android 4.4.2. I do not have the stock recovery and for some reason I am unable to flash CWM, so I am stuck with TWRP. I keep receiving notifications that Lollipop is available to install, but it fails each time I try to install it because I am rooted. How can I unroot and get back to my stock ROM so that I can install the update?
No need to update via OTA. Just follow the instructions here and you'll be on rooted 5.0.1 stock
http://forum.xda-developers.com/ver...u-m8vzw-5-0-1-s-off-onlynewest-t3047103/page3
Questions
Thank you for the reply. Are you 100% sure this is compatible/will work with my phone? If I flash the ROM and it doesn't work, can I simply flash a backup image I made to recover? And when I flash the ROM, will I lose all the data on my phone? Also, where may I download my stock recovery? I searched all over the internet and couldn't find one for the Verizon version of the HTC One M8.
Thank you
That RUU is a complete stock firmware package, including the recovery. Read the OP.
But if you're just looking for the stock recovery you can find it here: http://forum.xda-developers.com/showthread.php?p=52017763
That alone won't let you take the OTA though. If you modified your stock rom the OTA will fail.
You can find a complete stock rom elsewhere here on XDA, but why the trouble if you have it all in one neat package with the RUU?
Thank you very much for the help and useful information.
Sorry to bother you with all the questions but I have one more. How do I make a backup of my stock recovery? Say I went out and bought a new phone, how would I backup that stock recovery?
Image Update Error
Error fixed now
What is the most stable stock android version? Kitkat or Lollipop?
My phone is currently on NE9 and want to optimize my phone to be the best with what's out now, especially since development will be dwindling. It seems that Lollipop does not run too well (high battery usage?), according to what I see on the threads. Without any input, I would update to NK2 and then towelroot. However, would anyone recommend me updating to BOK3 or BPB1?
GoodLooks550 said:
What is the most stable stock android version? Kitkat or Lollipop?
My phone is currently on NE9 and want to optimize my phone to be the best with what's out now, especially since development will be dwindling. It seems that Lollipop does not run too well (high battery usage?), according to what I see on the threads. Without any input, I would update to NK2 and then towelroot. However, would anyone recommend me updating to BOK3 or BPB1?
Click to expand...
Click to collapse
They're both stable, but we do see a lot of complaints about lollipop battery life.
Try it for yourself. Just stick with jrkruse's stock lollipop images that don't update the bootloader past BOD5, or any ROM that specifically does not update the bootloader. Then you can easily downgrade back to kitkat if you decide you don't like it.
painiac said:
They're both stable, but we do see a lot of complaints about lollipop battery life.
Try it for yourself. Just stick with jrkruse's stock lollipop images that don't update the bootloader past BOD5, or any ROM that specifically does not update the bootloader. Then you can easily downgrade back to kitkat if you decide you don't like it.
Click to expand...
Click to collapse
Thanks, painiac! I used your guide to get up to date with the S5, btw--things are very different from what I remember in the S4 world.
Anyway, after rooting and installing safestrap, if i were to flash jrkruse’s BPB1 Rom (http://forum.xda-developers.com/verizon-galaxy-s5/development/vzwstock-based-tw-rom-3-4-16-t3329029), I would install the rom, safestrap fix, patch (optional), and BPB1_Firmware_No_Bootloaders.zip. Anything else to add?
This set up would allow me to go back to kit kat by installing a jrkruse kit kat rom and related firmware w/o bootloader?
GoodLooks550 said:
Thanks, painiac! I used your guide to get up to date with the S5, btw--things are very different from what I remember in the S4 world.
Click to expand...
Click to collapse
Glad I could be of service. I came here just a few months ago from an S3. Imagine my disgust and shock... That was actually the impetus for writing that guide, because there's so much to have to learn and I'd just finished researching the crap out of it all for myself in a short amount of time.
GoodLooks550 said:
Anyway, after rooting and installing safestrap, if i were to flash jrkruse’s BPB1 Rom (http://forum.xda-developers.com/verizon-galaxy-s5/development/vzwstock-based-tw-rom-3-4-16-t3329029), I would install the rom, safestrap fix, patch (optional), and BPB1_Firmware_No_Bootloaders.zip. Anything else to add?
This set up would allow me to go back to kit kat by installing a jrkruse kit kat rom and related firmware w/o bootloader?
Click to expand...
Click to collapse
Nothing else to add, I think you got it. That no bootloaders firmware file you selected is the important one.
jrkruse says you can still run kitkat ROMs even if you're stuck with Lollipop, but I haven't tried it yet. Staying with the BOD5 or earlier bootloader actually allows you to flash KitKat stock image files with Odin, which you cannot do without bricking if you've updated your bootloader to BOE1 or later. I like this because the KitKat root process is a lot less problematic than the new Lollipop root method; but more importantly, you can freely upgrade to Lollipop with BOD5 bootloader (modified) stock Odin images, and then you can freely downgrade with stock KitKat Odin images.
painiac said:
Glad I could be of service. I came here just a few months ago from an S3. Imagine my disgust and shock... That was actually the impetus for writing that guide, because there's so much to have to learn and I'd just finished researching the crap out of it all for myself in a short amount of time.
Click to expand...
Click to collapse
I was lucky to have my an S4 MDK (unlocked bl), so things were much simpler back then--had an S3, as well. In the process of getting my S5 running the way I wanted, the use of safestrap was completely new to me. Thankfully, some heavy browsing of the forums got me through. I did not use flashfire, which would have been something else to learn!
painiac said:
Nothing else to add, I think you got it. That no bootloaders firmware file you selected is the important one.
jrkruse says you can still run kitkat ROMs even if you're stuck with Lollipop, but I haven't tried it yet. Staying with the BOD5 or earlier bootloader actually allows you to flash KitKat stock image files with Odin, which you cannot do without bricking if you've updated your bootloader to BOE1 or later. I like this because the KitKat root process is a lot less problematic than the new Lollipop root method; but more importantly, you can freely upgrade to Lollipop with BOD5 bootloader (modified) stock Odin images, and then you can freely downgrade with stock KitKat Odin images.
Click to expand...
Click to collapse
Thank you--your replies and guide were gold in terms of figuring it all out.
For onlookers of this thread, once you get to lollipop, it's hard to go back to kitkat. A lot of the small details really add up to an improved user experience. Also, having an s7 edge, the PB1 build on the S5 has 90% of the same functionality of the S7e--excluding edge-related features, of course.
To summarize my upgrade experience:
Root from any kitkat rom: Flash the NCG kernel in odin (AP/PDA), reboot and root with towelroot apk, and then install and update supersu; and lastly re-flash the NE9 kernel.
Install Hashcode's version of Safestrap: Install busybox apk. Install safestrap apk (version 3.75). Make sure to use a microsd card for installation, as recommended.
Install PB1 rom: (source: http://forum.xda-developers.com/verizon-galaxy-s5/development/vzwstock-based-tw-rom-3-4-16-t3329029). Reboot into SS. Flash G900V_Fix Safestrap.zip. Reboot into SS. Flash:
VZW_BPB1_ODEX_DEODEX_V9.zip,
Extra_toggles.zip (optional),
BPB1_Firmware_No_Bootloaders.zip , and
G900V_PB1_Stock_KERNEL_SafeStrap-Flashable.zip.
Flash all in a single queue. Reboot into download mode and flash G900V_OD5_Bootloader.tar.md5 in odin. Reboot. Wait. (NOTE: for more customization, before installing rom, unzip rom. Edit the options.prop in text editor to your likeing. Rezip original contents with updated options.prop. Flash this zip as the rom file)
To get back into safestrap/recovery: Make sure hashcode's version of safestrap is installed. A lollipop safestrap will be installed--don't use it. Also, install NI2Flasher.apk (this flashes a kitkat kernel, which will allow you to get back into the kitkat safestrap). Reboot into safestrap. IMPORTANT: When complete with whatever is being done in SS, flash G900V_PB1_Stock_KERNEL_SafeStrap-Flashable.zip to get back into lollipop rom.
Install xpose modules: This allows the essential greenify app (HIGHLY RECOMMENDED) to run to maximum potential. Gather following files:
1. APK: Xposed Installer 3.0 alpha4 (comes with some roms)
2. Flash in SS: Framework: xposed-v75-sdk21-arm-arter97-snapdragon.zip
3. Flash in SS: Uninstaller: xposed-uninstaller-arter97.zip
Since the rom I installed did not come with xposed installed. I flashed the framework in SS (look above to properly access and leave SS). Reboot. Install the APK. Reboot. Highly recommend installing Wanam's modules for lollipop--tons of modifications.
Unbrick: Get into download mode and flash: Full Wipe G900V_Downgrade_to_NCG.tar . (This helped me a ton until I realized that safestrap for the S5 does not work with rom-slots. Use the stock slot to do all flashing)
I gathered all this information from various threads, and hope this helps (highly recommend reviewing painiac's guide before starting anything - http://forum.xda-developers.com/verizon-galaxy-s5/general/guide-painiacs-essential-guide-to-t3319848). I am no expert, but this is what worked for me--please correct me if I'm wrong at any step. I believe the way I set this up, I should be able to get back to a kitkat rom, if I ever wanted to (easiest way to do this would be to flash the unbrick file). I hope this can help at least one person, since I know I'm not the only person to recently get an S5 due to someone else in the family upgrading to the S7.
Need some guidance in setting up root and Rom on my s5. Never done this before on a Verizon phone so if anyone can help I'd appreciate it