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
Related
Hello,
If this is not the right place for this please fell free to move it.
Now that more unofficial roms like Cyanogenmod are getting closer to a stable/bug free release I am wondering about a few things.
According to Cyanogenmod's install guide a OLDER Kernel and Bootloader must be flashed in order to get recovery installed and Cyanogenmod running, one would also assume that most other custom roms would require this as well.
3. Flash the aboot.mbn file from VRALEC.bootloader.tar.md5 with Heimdall:
heimdall flash --ABOOT aboot.mbn
4. Flash the older kernel from VRALF2.boot.tar.md5 with Heimdall:
heimdall flash --boot boot.img
5. You should now be able to download and flash recovery:
koush's ClockworkMod Recovery: download
md5sum:3b13219e967fc622c035540107ee5553
heimdall flash --recovery your_recovery_image.img
6. Flash bootloader zipfile via recovery:
Flash the VRALE6.bootloader.zip in recovery
Install zip from sdcard
Choose VRALE6.bootloader.zip
Confirm installation
Reboot
Click to expand...
Click to collapse
Using this tutorial by invisiblek I obtained Root and Clockworkmod recovery some time ago and have not updated or touched the FW since. I even disabled OTA updates to avoid loosing my root.
In About Device I have:
Android Version 4.0.4
Baseband Version I535VRLF2
Kernel Version 3.0.8
Build number is I535VRALF2
CWM recovery version: 6.0.1.2
Would using the above methods to flash a new bootloader and kernel even be necessary on my phone to get Cyanogenmod running? Besides flashing the phone originally I have done nothing to change or update this stock rom.
The reason I ask is I would rather avoid any potentially phone bricking steps for installation of custom roms if they are unnecessary.
Thanks for the help in advance.
You can easily update your CWM version and bootchain (unlocked), which makes flashing custom kernels and ROMs possible, by via Odin. If that's what you wanted to know? Haha.
Well I was more wondering if I needed to even bother flashing my kernel/bootloader in order to get custom roms to run?
nuke235 said:
Well I was more wondering if I needed to even bother flashing my kernel/bootloader in order to get custom roms to run?
Click to expand...
Click to collapse
In order to load a custom ROM you'll need to be rooted, have an unlocked boot loader, and a custom recovery such as CWM or TWRP installed.
Most custom ROMS are based on a certain firmware. For instance Scott's ROM is based off of the I535VRBMB1 firmware but works with some older firmwares, however, it will not work with the newest firmware I535VRBMF1 (camera doesn't work).
Check this thread for newer firmwares (flashable through recovery) if you want to update yours!
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..
Is it possible to update bootloader and/or radio on kitkat & not ruin the rom or wipe device to update?
To still run kitkat rom w/ newer bootloader?
Yes just flash them manually in fastboot, or flash a zip file in custom recovery.
Hello, I am new to custom rom flashing, I understand that I can relock the bootloader if I want to and also can restore the stock rom but every tutorial I have seen shows me to lock the bootloader after flashing the stock rom, so my questions are,
1. Can I keep the bootloader unlocked and still install the stock rom using fastboot and use it?
2. If it is okay then will I loose twrp after flashing the stock rom?
3. If the twrp stays even after flashing the stock rom then how to uninstall twrp?
4. If I decide to relock the bootloader can I unlock it again with the same unique code by motorola?
Thank you soo much.
1. Yes, just refer to the fastboot factory firmware flashing guide by lost101.
2. Yes. Specifically this command replaces existing recovery-
Code:
fastboot flash recovery recovery.img
3. Make sure you include the above command when flashing stock firmware. Recoveries can't be uninstalled, they are overwritten (replaced) directly by flashing a new one from fastboot.
Just FYI, to temporarily boot a recovery without flashing it permanently, use-
Code:
fastboot boot recovery.img
where recovery.img is the file name. It is useful to load up TWRP without disturbing existing stock recovery, for example.
Broadcasted from Zeta Reticuli
Can I unlock and relock bootloader however many times as I wish? and also
I am running on marshmallow so will I get prevalidation error when I install a custom rom 7.0 and try to flash the 6.0 stock firmware because I got this message when I updated to marshmallow and wanted to downgrade to lollipop using fastboot.?
Thanks for your answers and also for the temporary recovery tip.
1. You shouldn't be locking and unlocking it repeatedly, it is a risky procedure involving full firmware flash. Some have got unlock errors while re-unlocking right after their 1st lock, some had their unlocked successfully.
2. You can use 7.x custom ROMs and still flash STOCK 6.0/6.0.1 firmware without errors. Preflash Validation occurs only when the target firmware is newer than the one to be flashed. It occurs mostly in partition table file (gpt.bin) and bootloader (bootloader.img). AFAIK Custom ROMs do not modify these and are immune to this error.
But if you accept an OTA for the stock ROM, you'll most likely get this error. Note that STOCK OTA will most likely update the bootloader and other important partitions too which the custom ROMs do not touch.
So even if you are on 7.x, the phone has an underlying 6.0.1 firmware (almost, except for the ROM itself, obviously). Hence, you'll get preflash validation error only when fastboot flashing an earlier 6.0.1/6.0/5.x STOCK build. You can use older custom ROMs without any problems though.
Broadcasted from Zeta Reticuli
thanks a lot
Hello/Hi/Good evening
Can i go back to older stock rom by flashing older boot.img and recovery.img through flashfire and then flashing my Older OTA.zip file through apply update from sd card via older stock recovery.
My device is asus x003, android 4.4.4. note that both of these stock firmware are of the same android version 4.4.4.
The older stock rom depicted here is of global version and newer one which I am currently on is of chinese sku.
Thanks
Guys, the method worked, if anyone want the flashfire flashable zip for the boot and recovery zip give a reply.