All the forums that I could find are talking about updating from a stock rom to the ODEX rom. I am wondering if i need to update my bootloader if i am upgrading to the asus rom.
I have TWRP 2.4.1.0 and i am on the ASUS stock ics update 30. I have downloaded the ASUS stock firmware V10.6.1.14.8 which stores the 4.2.1 rom. If i do a wipe on everything from TWRP then mount and install the rom from an external sd card, will I brick my device without doing the same bootloader update that is done for the ODEX rom. Correct me if I am wrong but I believe that the firmware package comes with the bootloader needed for the rom.
data90 said:
All the forums that I could find are talking about updating from a stock rom to the ODEX rom. I am wondering if i need to update my bootloader if i am upgrading to the asus rom.
I have TWRP 2.4.1.0 and i am on the ASUS stock ics update 26. I have downloaded the ASUS stock firmware V10.6.1.14.8 which stores the 4.2.1 rom. If i do a wipe on everything from TWRP then mount and install the rom from an external sd card, will I brick my device without doing the same bootloader update that is done for the ODEX rom. Correct me if I am wrong but I believe that the firmware package comes with the bootloader needed for the rom.
Click to expand...
Click to collapse
Before you update to the latest firmware, I would recommend that you use NVFlash as a backup for recovering if you brick your device. You can find the information here: http://forum.xda-developers.com/showthread.php?t=1901479
If you update the latest Asus firmware, V10.6.1.14.8, it will also update your bootloader with the latest version. Good luck.
Thank you for the idea of NVFlash but unfortunately I have one too many updates to utilize that wonderful software. If I was able to use it, then I would have dove in head first and then informed the populace of my findings. So lets see if I give my self a ~$450 paper weight.
data90 said:
All the forums that I could find are talking about updating from a stock rom to the ODEX rom. I am wondering if i need to update my bootloader if i am upgrading to the asus rom.
I have TWRP 2.4.1.0 and i am on the ASUS stock ics update 30. I have downloaded the ASUS stock firmware V10.6.1.14.8 which stores the 4.2.1 rom. If i do a wipe on everything from TWRP then mount and install the rom from an external sd card, will I brick my device without doing the same bootloader update that is done for the ODEX rom. Correct me if I am wrong but I believe that the firmware package comes with the bootloader needed for the rom.
Click to expand...
Click to collapse
You are correct. The Asus firmware has the correct bootloader, recovery and rom. If you flash it from TWRP it will install the stock recovery. So you loose TWRP and root too. You're basically back to a stock system, except you're unlocked.
berndblb said:
You are correct. The Asus firmware has the correct bootloader, recovery and rom. If you flash it from TWRP it will install the stock recovery. So you loose TWRP and root too. You're basically back to a stock system, except you're unlocked.
Click to expand...
Click to collapse
When I went to flash the firmware from twrp it kept failing. (and i accidentally wiped the os from the device) So I flashed ics back onto it and then tried upgrading again from the stock recovery, but i kept getting the dead android. I also got the device to recognize that there was an update zip on the device so that it would send it into an updating state by itself, but that also produced the android with the caution sign.
Any ideas?
data90 said:
When I went to flash the firmware from twrp it kept failing. (and i accidentally wiped the os from the device) So I flashed ics back onto it and then tried upgrading again from the stock recovery, but i kept getting the dead android. I also got the device to recognize that there was an update zip on the device so that it would send it into an updating state by itself, but that also produced the android with the caution sign.
Any ideas?
Click to expand...
Click to collapse
There are a lot things that could be wrong. However, most likely are: 1. A wrong signed firmware, for example you have a US bootloader but you try to update with WW firmware. 2. You have a currupted zip file. 3. You forgot to unzip it once because there is a zip inside the other zip file. If non of the above are applied to you, you could try this.
1. Copy a second zip file to your Root directory on your Internal SD
2. Reboot your device
3. After rebooted, you should see the notification on your lower right corner with the new update
4. Just click on the updated notification and follow the instructions as it walk you through the updated precesses.
Please report back. If it does not work, you need to rename your second zip file and use the stock recovery to update the firmware. There is a link some where on this website will walk you through the processes. Good luck.
LetMeKnow said:
There are a lot things that could be wrong. However, most likely are: 1. A wrong signed firmware, for example you have a US bootloader but you try to update with WW firmware. 2. You have a currupted zip file. 3. You forgot to unzip it once because there is a zip inside the other zip file. If non of the above are applied to you, you could try this.
1. Copy a second zip file to your Root directory on your Internal SD
2. Reboot your device
3. After rebooted, you should see the notification on your lower right corner with the new update
4. Just click on the updated notification and follow the instructions as it walk you through the updated precesses.
Please report back. If it does not work, you need to rename your second zip file and use the stock recovery to update the firmware. There is a link some where on this website will walk you through the processes. Good luck.
Click to expand...
Click to collapse
I second LetMeKnow.
Download the firmware again unzip it once and put it into the root of your microSD card. The card should be formatted as FAT32.
If the recovery does not automatically recognize it, rename the file to EP201_768_SDUPDATE.zip.
As far as I can see you are on the .30 ICS so nvflash won't work for you.
I see many noobs like me being confused about how their root and custom recovery status should be before installing or even receivingLollipop OTA.
So my understanding is to receive OTA update and to successfully install it one needs to be on,
1. STOCK firmware of their respective device.
2.Custom recovery ( No TWRP, CWM or any other custom recovery ).
3.Bootloader should be locked.
Am i right?
So, my questions are,
1. I can understand why the first two needs to be done but why should we lock the bootloader?.
2. When i restored to stock firmware( Mine's XT1033 ) KK 4.4.4 from TWRP Recovery with this http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688 TWRP was still installed on my mobile.But when i reverted to stock 4.4.2( not 4.4.4 ) from fastboot using this http://forum.xda-developers.com/showthread.php?t=2700502 it successfully deleted TWRP.
So when we flash Stock ROM with Zip file it only installs the stock ROM and won't delete TWRP? and when we flash with fastboot( and .xml.zip file ) it removes TWRP? So am i right with this assumption?
If i am right how do i get back to stock recovery( delete TWRP ) since currently i have Stock 4.4.4 from the above link.
Help me and provide some correct scenarios to get Lollipop OTA.
this mototool has a functionallity of retrieving stock recovery
http://forum.xda-developers.com/showthread.php?p=50029015
it's pretty straight forward.
and as of what I've read, no need to relock bootloader for OTA to take place.. but I have no experience whatsoever..
In an attempt to stop anyone else from making a "pls halp me" thread I decided to make one myself.
Before I go further let me reiterate the importance of regular backups. Before you do anything, make a full backup of your device in a usable state^. This serves as somewhere you can revert to if you accidentally tap something that screws everything up.
^ - If you're trying to recover from what appears to be a softbrick you should start by flashing and/or booting into recovery or fastboot at least.
Being overly excited about finally getting Lollipop (I don't check for updates often) I immediately went and installed the first update available OTA, forgetting that I had for some reason refused to update my E8 since unboxing it. I've since successfully updated from 1.09 to 2.33 (Kit Kat 4.4.2 to Lollipop 5.0) and installed the Xposed Framework, here's some issues I ran into and what I did to solve them.
PROBLEM: Update takes you to your custom recovery mode without doing anything else.
Having already rooted and installing TWRP the OTA update failed, only taking me to TWRP's recovery screen instead of performing the update.
SOLUTION: Flash the stock recovery.img extracted from the downloaded .zip update in the Downloads folder on the Internal Storage
You can probably find the OTA/RUU update .zip you need from this thread or let your E8 check and download the update .zip which you can then find in the Download folder on the Internal Storage. Transfer it to your PC and extract recovery.img from 'firmware.zip' in the update .zip file. Using fastboot, flash the extracted stock recovery image and reboot. You can now restart the update which will properly complete. Once your phone has booted back up into Lollipop and completed the update you should flash back your custom recovery of choice using fastboot.
PROBLEM: ROOT LOST AFTER UPDATE
This shouldn't be a surprise. OTA updates will unroot your device.
SOLUTION: Install SuperSU in recovery, NOT Play Store.
Download the latest SuperSU installable .zip and copy it to your phone. Boot into recovery and install.
My E8 is a single-sim M8sX but I believe these steps should work with any other variant.
Hi Guys.
I've reached a state of confusion reading about OTA-updates, TWRP and root. My question question is this:
I installed TWRP, flashed the verity opt encryption kernel and rooted my G930F. Everything works and all is good. But with the new Chainfire AUTO-ROOT (is it X.72?) OTA-updates has been disabled.
I'm confused about the reason for this. Does this mean that I risk bricking my phone if I at some point in timez deside to flash stock rom via ODIN? Or will this just replace TWRP with original recovery and overwrite root?
Sorry for my noob-mind. I'm new to Samsung devices.
Best regards.
If you flash stock rom via Odin TWRP will be deleted and stock recovery will be installed. You will also lose root privileges. Make sure you have a backup before flashing stock via Odin. Once restored stock rom via odin follow same steps you took the first time you rooted your phone.
Leeum said:
If you flash stock rom via Odin TWRP will be deleted and stock recovery will be installed. You will also lose root privileges. Make sure you have a backup before flashing stock via Odin. Once restored stock rom via odin follow same steps you took the first time you rooted your phone.
Click to expand...
Click to collapse
Thanks alot!
Not sure if this is the correct place to post this. But, I'm having some trouble flashing TWRP and rooting my G5 (H830). I did unlock the bootloader and flashed the H83020a stock firmware. When I try using LGUP to flash a pre-rooted rom, I get an error syaing that the TOT file doesn't support the upgrade function (also tried refurbish function), tried using recowvery, but that just freezes during the process soft bricking my phone (left recowvery alone overnight just to make sure) so I had to reflash the custom rom, and also tried flashing TWRP through the ADB shell. Any help would be appreciated.