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!
Related
I need advice on what you would do in my situation. I am on stock rom LF2, rooted, CWM recovery and bootloader unlocked and I want to upgrade to JB. What would you recommend be my upgrade path without wiping data? Just doing a dirty flash using CWM or upgrade via OTA and then rooting using the ODIN packages? As an added complication, I recently acquired the copy/paste bug. Thanks for your input.
Use the pre-rooted no-wipe version here:http://forum.xda-developers.com/showthread.php?t=1984436. Then you can just boot up the phone and flash CWM recovery using EZ-Recovery and unlock with EZ-Unlock version 1.2. There is another guide stickied at the top of the development section but I think it is a little more work to get the same result. Make sure to take a backup first of course. Then if you want the latest CWM recovery you can flash it with ROM Manager. I used this method to go from stock rooted and unlocked VRALG1 to the J1, K1 and then K3 leaks all without wiping data and everything has worked great. No media drain or anything else.
Thanks, I was confused about which method to use. I just finished flashing and everything seems to be working.
So, I think I have the right idea but I wanted to make sure before I do anything so I don't brick or cause headaches for myself.
Currently on:
Hellkat 4.2.2
Kernel: BMS 3.4.77
Basebad: I535VRBLK1
Download Mode shows the following:
ODIN MODE
Product name: SCH-I535
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Custom
Qualcomm Secureboot: Enable
My understanding is that I should get the MF1 firmware: http://forum.xda-developers.com/showthread.php?t=1788313
Flash that through recovery (do I need to wipe anything before/after this?)
Update baseband from that thread as well (do I flash this through recovery as well?)
And then I should be good?
Thanks in advance!
carngeX said:
So, I think I have the right idea but I wanted to make sure before I do anything so I don't brick or cause headaches for myself.
Currently on:
Hellkat 4.2.2
Kernel: BMS 3.4.77
Basebad: I535VRBLK1
Download Mode shows the following:
ODIN MODE
Product name: SCH-I535
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Custom
Qualcomm Secureboot: Enable
My understanding is that I should get the MF1 firmware: http://forum.xda-developers.com/showthread.php?t=1788313
Flash that through recovery (do I need to wipe anything before/after this?)
Update baseband from that thread as well (do I flash this through recovery as well?)
And then I should be good?
Thanks in advance!
Click to expand...
Click to collapse
All you need to do is what invisiblek says in this line:
"My recommendation: if you aren't already on MF1 firmware (below), flash that. Then update your baseband with this: http://invisiblek.org/sch-i535/modem..._ML1_modem.zip"
Both are flashed in recovery, you don't need to wipe first, or reboot or anything in between. Just flash this: http://invisiblek.org/sch-i535/firmware/d2vzw_VRBMF1_firmware.zip, and then flash this: http://invisiblek.org/sch-i535/modems/d2vzw_ML1_modem.zip. The first ZIP updates all the phone's firmware to the MF1 version, the second ZIP is just updating the radio portion of the firmware to ML1. If you're sticking with an AOSP ROM, there is no need to update the radio, but feel free to try the ML1 radio if you want, it may improve your reception. Sticking to MF1 won't cause any problems with your ROM though.
Jacquestrapp said:
All you need to do is what invisiblek says in this line:
"My recommendation: if you aren't already on MF1 firmware (below), flash that. Then update your baseband with this: http://invisiblek.org/sch-i535/modem..._ML1_modem.zip"
Both are flashed in recovery, you don't need to wipe first, or reboot or anything in between. Just flash this: http://invisiblek.org/sch-i535/firmware/d2vzw_VRBMF1_firmware.zip, and then flash this: http://invisiblek.org/sch-i535/modems/d2vzw_ML1_modem.zip. The first ZIP updates all the phone's firmware to the MF1 version, the second ZIP is just updating the radio portion of the firmware to ML1. If you're sticking with an AOSP ROM, there is no need to update the radio, but feel free to try the ML1 radio if you want, it may improve your reception. Sticking to MF1 won't cause any problems with your ROM though.
Click to expand...
Click to collapse
Awesome, that's what I figured I had to do, but I just wanted to confirm what I was thinking. Thanks!
I've never had issues barging into a development community and going out to the horizon of customization until this cellphone. It's been 12 hours of flashing and downloading and flushing and flashing...
I have S-off and unlocked through SunShine
I use the 0P6BIMG.zip to flash RUU back to the stock verizon rom android 4.4.2
I use 3.28.605.4-firmware.zip from the same RUU thread to update the firmware (???)
I want to install CM12 or liquidsmooth ROM, but I'm getting a hunch at this point I need to start with the stock verizon 5.0.1 installed before that because TWRP wants to patch the system file... But then why am I wiping my system before installing?
I also tried flashing FluentRom_v7.5.zip but I got stuck on the HTC initial screen, I don't even make it over to a boot animation.
What do?
Gevork Gevorkyan said:
I've never had issues barging into a development community and going out to the horizon of customization until this cellphone. It's been 12 hours of flashing and downloading and flushing and flashing...
I have S-off and unlocked through SunShine
I use the 0P6BIMG.zip to flash RUU back to the stock verizon rom android 4.4.2
I use 3.28.605.4-firmware.zip from the same RUU thread to update the firmware (???)
I want to install CM12 or liquidsmooth ROM, but I'm getting a hunch at this point I need to start with the stock verizon 5.0.1 installed before that because TWRP wants to patch the system file... But then why am I wiping my system before installing?
I also tried flashing FluentRom_v7.5.zip but I got stuck on the HTC initial screen, I don't even make it over to a boot animation.
What do?
Click to expand...
Click to collapse
I'm prettly sure you're on an older firmware. You need to be on 5.01 to flash the ROMs you have tried to flash. Use the pre-rooted RUU from this thread here: http://forum.xda-developers.com/ver...zw-m8-master-ruu-firmware-collection-t2946473
Also make sure you have the latest version of TWRP.
Edit: The firmware you flashed was 4.4.4
BladeRunner said:
I'm prettly sure you're on an older firmware. You need to be on 5.01 to flash the ROMs you have tried to flash. Use the pre-rooted RUU from this thread here: http://forum.xda-developers.com/ver...zw-m8-master-ruu-firmware-collection-t2946473
Also make sure you have the latest version of TWRP.
Edit: The firmware you flashed was 4.4.4
Click to expand...
Click to collapse
Thanks for the link that thread and your advice was exactly what I needed.
For whatever reason after using the app/exe to flash 5.0.1 stock-rooted, Liquid Rom failed to install in TWRP. I reflashed the stock-rooted rom and CM-12.1 worked flawlessly. So I'm on CM right now :good: but I'll take another look into Liquid rom. Thanks so much!
Since you like AOSP, I recommend visiting the main m8 thread some other Roms. They are unified builds.
Hi to All!: I'm new to this forum and you may consider me a newbie, willing to learn from you and share my experiences in the near future. Just recently I managed to root my Samsung Galaxy S5 SM-G900V running Lollipop latest release (OK3) following this tutorial (thanks a lot to jrkruse for that!!). Now I'm trying to install a Custom Recovery, I tried Safestrap (Safestrap-KLTEVZW-NCG-3.75-B03.apk), ClockworkMod (philz_touch_6.41.6-klte.tar) and TWRP (twrp-2.8.7.0-klte, tar & img versions) and this is what happened:
----Safestrap App installed successfully but failed to install Recovery.
----ClockworkMod (Philz Touch variant) failed to flash with Odin.
----TWRP succeeded to install via ADB shell, replaced Stock Recovery but gave this error:
''RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING''
I ended flashing Stock OK3 to have at least Stock Recovery again!, it's known OE1, OG5 and OK3 updates prevent downgrading, I want to downgrade to 4.4.4 to solve some wi-fi issues I've been having since Lollipop updates.
Some help about this subject will be very appreciated!!
Thanks a lot in advance to all members of this awesome forum!!
cd2xtac said:
Hi to All!: I'm new to this forum and you may consider me a newbie, willing to learn from you and share my experiences in the near future. Just recently I managed to root my Samsung Galaxy S5 SM-G900V running Lollipop latest release (OK3) following this tutorial (thanks a lot to jrkruse for that!!). Now I'm trying to install a Custom Recovery, I tried Safestrap (Safestrap-KLTEVZW-NCG-3.75-B03.apk), ClockworkMod (philz_touch_6.41.6-klte.tar) and TWRP (twrp-2.8.7.0-klte, tar & img versions) and this is what happened:
----Safestrap App installed successfully but failed to install Recovery.
----ClockworkMod (Philz Touch variant) failed to flash with Odin.
----TWRP succeeded to install via ADB shell, replaced Stock Recovery but gave this error:
''RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING''
I ended flashing Stock OK3 to have at least Stock Recovery again!, it's known OE1, OG5 and OK3 updates prevent downgrading, I want to downgrade to 4.4.4 to solve some wi-fi issues I've been having since Lollipop updates.
Some help about this subject will be very appreciated!!
Thanks a lot in advance to all members of this awesome forum!!
Click to expand...
Click to collapse
On OK3 the bootloader is locked. You cannot downgrade to 4.4.2 or 4.4.4 or any other previous version. You also cannot install custom recoveries like ClockworkMod or TWRP. You are relegated to Safestrap or FlashFire as discussed in jrkruse's threads.
You can ONLY use SafeStrap. TWRP and Clockworkmod cannot load because we have a locked bootloader.
You must flash a kitkat kernel to boot into safestrap, which I gather you didn't do. Then when you're done in Safestrap, flash a safestrap-flashable lollipop kernel BEFORE EXITING SAFESTRAP to boot back into your ROM.
@ landshark68
@painiac
Thank both for your replies!, let's see if I misunderstood something: flashing NI2 Stock Kernel with Odin will give the possibility to boot into Safestrap and flash zip of Stock NI2 ROM (4.4.4) or will I remain tied to OK3 even if I flash the KitKat Kernel?
cd2xtac said:
@ landshark68
@painiac
Thank both for your replies!, let's see if I misunderstood something: flashing NI2 Stock Kernel with Odin will give the possibility to boot into Safestrap and flash zip of Stock NI2 ROM (4.4.4) or will I remain tied to OK3 even if I flash the KitKat Kernel?
Click to expand...
Click to collapse
You will remain tied to OK3
@cd2xtac
I'm just curious about the whole flashing a custom recovery part you were talking about..
It let you flash one?
Normally I'd just shrug a thread like this off but when you said you tried to boot into recovery and saw
Code:
RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
that means it actually let you flash a custom recovery.
So my real questions here are, in download mode, does it say Knox 0x1?
And/or after you tried to boot into twrp, did it say "set warranty bit: recovery"?
This part makes me curious because on a locked bootloader, we shouldn't be able to flash a custom recovery.
Or maybe we can and just can't boot into it.
I haven't looked into this much because I've always just accepted that a locked bootloader means we need to use SS or FF and can't flash custom ROMs like CM.
Although I am curious what makes Samsung phones different than my old Droid Bionic. It has a locked bootloader and can only use Safestrap but it can still flash CM13 in a non-stock ROM slot. Why can'take we?
Perhaps I should call someone like @jrkruse in to see if he can clarify or if he knows why.
Dudash said:
@cd2xtac
I'm just curious about the whole flashing a custom recovery part you were talking about..
It let you flash one?
Normally I'd just shrug a thread like this off but when you said you tried to boot into recovery and saw
Code:
RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
that means it actually let you flash a custom recovery.
So my real questions here are, in download mode, does it say Knox 0x1?
And/or after you tried to boot into twrp, did it say "set warranty bit: recovery"?
This part makes me curious because on a locked bootloader, we shouldn't be able to flash a custom recovery.
Or maybe we can and just can't boot into it.
I haven't looked into this much because I've always just accepted that a locked bootloader means we need to use SS or FF and can't flash custom ROMs like CM.
Although I am curious what makes Samsung phones different than my old Droid Bionic. It has a locked bootloader and can only use Safestrap but it can still flash CM13 in a non-stock ROM slot. Why can'take we?
Perhaps I should call someone like @jrkruse in to see if he can clarify or if he knows why.
Click to expand...
Click to collapse
Because on other phones they had ways to trick the phone into letting a custom kernel be flashed. These ways dont work on S5. Also Rom slots dont work on our phone either unless you go back to kitkat, but you were still booting off of main kernel,so still no go
jrkruse said:
Because on other phones they had ways to trick the phone into letting a custom kernel be flashed. These ways dont work on S5. Also Rom slots dont work on our phone either unless you go back to kitkat, but you were still booting off of main kernel,so still no go
Click to expand...
Click to collapse
Thanks for clarifying
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