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.
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 everyone im after some help please.
Just tried to install CM 13 nightly wiped everything userdata factory reset dalvik. When i try and install from usb stick I got a error "This package supports bootloader (s) 0x4118, Ox4119 this device has bootloader 0x4113.
I was previously on Lollipop 5.0.2 , so I thought CM 13 was compatible with the bootloader before? Ive done something wrong could anyone help me please.
thanks alot
Bootloader 41.13 is the KitKat bootloader. You haven't installed a stock Lollipop ROM before so your bootloader doesn't get upgraded. You was on CM12, right?
If you want to upgrade, check this thread: http://forum.xda-developers.com/moto-g/general/falcon-bootloader-upgrader-tool-t3093793
Or you can modify the update zip to install with bootloader 41.13 (it's a simple check at update-script)
My son's XT1031, which has an unlocked bootloader and TWRP recovery, has been continuously requesting to install an OTA update (221.31.4). I tried to install the update zip file I found in the /cache directory but it fails to install. Does anybody know how to install the OTA with a custom recovery? The phone is stock Android 5.1 (221.21.56) otherwise.
Thanks in advance.
gm2racer said:
My son's XT1031, which has an unlocked bootloader and TWRP recovery, has been continuously requesting to install an OTA update (221.31.4). I tried to install the update zip file I found in the /cache directory but it fails to install. Does anybody know how to install the OTA with a custom recovery? The phone is stock Android 5.1 (221.21.56) otherwise.
Thanks in advance.
Click to expand...
Click to collapse
Have you tried flashfire? It has an option for OTA update
This Process Will Update Or Downgrade Your VZW EMMC Chipset DEV Aboot Bootloader Unlocked S5 To Marshmallow 6.0 Lollipop 5.0 Or Kitkat 4.2 or 4.4
​Root And Unlock Instructions Can Be Found Here
EMMC 15 Rooting And Bootloader Unlocking
EMMC 11 Rooting And Bootloader Updating Or Downgrading
Explanation On This Process
To update bootloaders to a newer or older bootloaders all moddified system firmware must be put back to stock in order for the bootloader to update. There is some kind of check and a flag is thrown if there is a modded boot or recovery image present. This is why it is a 2 step process and why it cannot simply be a one zip process. You are on unlocked bootloader and have TWRP probably install and maybe a custom boot.img. To upgrade bootloaders the stock recovery and boot images must be put back to stock and when you do this you obviously do not have a way to flash the zip to update rom and bootloaders. because there is no more custom recovery installed. So too do this the first zip removes TWRP and puts back Stock recovery and boot images and also adds safestrap recovery which is a system based recovery. Then when booted to safestrap recovery you can flash the rom zip with bootloader update and it will flash properly because there is no modified boot or recovery image then once the zip is flashed it removes safestrap and puts back TWRP recovery. Now the reason there is a 2 different Files To Prepair To Upgrade Or Downgrade one for kitkat and one for Lollipop/Marshmallow is the safestrap needs to be different for the kitkat system vs the lollipop/marshmallow system which can use the same safestrap. This is the reason on zip does not work for all 3 systems
Download Files To Prepair To Upgrade Or Downgrade From Unlocked KitKat 4.2 or 4.4 Bootloader Rev1-Use To Update To Rev2
EMMC_15_TWRP_KK_Prepare_Dev_BL_Update.zip
This File Is Only For People Still On Rev1 Bootloaders
Download Files To Prepair To Upgrade Or Downgrade From Unlocked KK LL MM All Bootloader Rev2
EMMC_15_TWRP_Prepare_Dev_BL_UP_Dwngrd.zip
This File Is Only For People On Rev2 Bootloaders
Download Rom Files
EMMC_15_SS_Install_QL1_6_0_1_MM_Bootloader_Unlock_AIO_Rom.zip
Stock QL1 Deodexed Rom Prerooted With EFTSU with root hide Debloated And DeKnoxed
EMMC_15_SS_Install_PB1_5_0_1_LL_Bootloader_Unlock_AIO_Rom.zip
Stock PB1 Deodexed Rom Prerooted with SuperSU 2.82 Debloated And Deknoxed
If you wish to use magisk on this rom you can download the View attachment Magisk-v13.3.zip and flash when this entire process is done. If you wish to use newer magisk zips you will need to manually patch your boot.img but the View attachment Magisk-v13.3.zip will do it for you when you flash it
EMMC_15_SS_Install_NK2_4_4_4_KK_Bootloader_Unlock_AIO_Rom.zip
Stock NK2 Deodexed Rom Prerooted with SuperSU 2.82 Debloated And Deknoxed
Instructions
You Must Be On VZW EMMC Chipset 15 With DEV Aboot Unlocked Bootloader With TWRP Recovery
1. Choose the file from the Download Files To Prepair To Upgrade Or Downgrade above that matches your current firmware and place on phone
2. Choose rom from Download Rom Files that you wish to upgrade or downgrade too and copy to phone
3. Reboot too TWRP recovery and choose install and choose EMMC_15_TWRP_**_Prepare_Dev_BL_UP_Dwngrd.zip and install. Do not wipe anything at this point just flash. This zip will remove TWRP recovery and replace any it and your boot image with stock boot images and install safestrap to your system which is needed to upgrade or downgrade bootloaders. When down flashing phone will reboot phone to Safestrap Recovery which looks just like TWRP recovery.
4. In Safestrap recovery choose install and choose the EMMC_15_SS_Install_***_*_*_*_**_Bootloader_Unlock_AIO_Rom.zip you copied to your phone. This zip will install proper bootloaders and firmware and rom and TWRP again. Do Not wipe anything at this point just flash the zip. Once zip is finished flashing phone will power off.
5. Now reboot phone to TWRP recovery which will now be back on your phone and goto wipe and choose advanced wipe and wipe data only. Then reboot phone and you are done
Bugs Problems And Tips
All roms are deodexed so they will take a long time to boot up to 20 minutes or maybe longer the first time or if you wipe dalvik cache or data
When Rom is booting up if your key lights come on and stay on why the rom is on bootanimation the entire time and waiting for rom to boot then this means your bootloader is not matched to firmware. I suggest trying above process
Fingerprint will not work on kitkat roms and may not work on others
All above roms use the QL1 baseband you are free to use any baseband you want however the Non-Hlos file must match firmware so only flash modem file
If you flash modded boot images it may break root
If you loose bootloader unlock or wish too start fresh go here first https://forum.xda-developers.com/ve...-emmc-15-chipset-onlyroot-bootloader-t4009089
If simply wanting to reflash an above rom zip over same rom and firmware it is ok too just flash it in TWRP you can skip the EMMC_15_TWRP_**_Prepare_Dev_BL_UP_Dwngrd.zip
All above methods are for Samsung Stock roms I do not offer support or answer questions about flashing Lineage or AOSP based roms
Tools And Extras
View attachment G900V_TWRP_RECOVERY_AROMA_FIX.tar This is an older TWRP that supports Aroma Installer zips
View attachment Odin_Files_3_13_Patched.zip Patched Odin
Thank you my friend.
Updated root scripts added