I think I understand what's happening, but what I've read isn't clear. I have updated to KK in order to unlock the bootloader on my Motorola RAZR HD xt926. That all went fine. I've been using both CWM 6049 and TWRP 2710. I've tried flashing several ROM versions of Cyanogen and SlimKat and they all end up boot looping (hang at the red M). There are no errors during flashing. The only ROMs that will boot are Cyanogenmod nightlies after M8. Those nightlies, however, have issues (notably no GPS). Several others seem to have the same problems, but many are running these builds fine. If I (finally) understand correctly the stock KK update also updates the bootloader to a KK bootloader and there is no way to downgrade the bootloader. The post-M8 nightlies of CM can use the KK bootloader, but all else needs the earlier JB bootloader. Basically I'm wondering if I'm just stuck in a "too new" are and have to wait until KK bootloader compatible ROMs are available. Does this sound correct? Or can I just downgrade the bootloader to flash Cyanogenmod and Slimkat stable builds? Thanks in advance!
--Mike
duffme said:
I think I understand what's happening, but what I've read isn't clear. I have updated to KK in order to unlock the bootloader on my Motorola RAZR HD xt926. That all went fine. I've been using both CWM 6049 and TWRP 2710. I've tried flashing several ROM versions of Cyanogen and SlimKat and they all end up boot looping (hang at the red M). There are no errors during flashing. The only ROMs that will boot are Cyanogenmod nightlies after M8. Those nightlies, however, have issues (notably no GPS). Several others seem to have the same problems, but many are running these builds fine. If I (finally) understand correctly the stock KK update also updates the bootloader to a KK bootloader and there is no way to downgrade the bootloader. The post-M8 nightlies of CM can use the KK bootloader, but all else needs the earlier JB bootloader. Basically I'm wondering if I'm just stuck in a "too new" are and have to wait until KK bootloader compatible ROMs are available. Does this sound correct? Or can I just downgrade the bootloader to flash Cyanogenmod and Slimkat stable builds? Thanks in advance!
--Mike
Click to expand...
Click to collapse
you can flash back to JB and use the JB based roms.
there is a guide in my sig with instructions and files to use, just skip down to the relevant parts.
bweN diorD said:
you can flash back to JB and use the JB based roms.
there is a guide in my sig with instructions and files to use, just skip down to the relevant parts.
Click to expand...
Click to collapse
Thanks for the clarification @bweN diorD. I had actually done that to re-flash the KK images, thinking I might have missed something. Looks like I had given up one step too soon. I'm now happily unlocked and rooted and running a stable CM11 M8.
Related
So I recently got a SGS3 for verizon and I was looking to install CM10 on it. On the CM wiki it says that "CyanogenMod on the Verizon variant of the Galaxy S3 you need to load an older bootloader."
I'm not clear to whether this means I just need an unlocked bootloader (which I have now from EZ Unlock) or if I need an entirely different bootloader, because looking at some forum posts for the official CM10.1, it only mentions that I need updated CWM or TWRP.
Any help would be appreciated.
siriusgamer said:
So I recently got a SGS3 for verizon and I was looking to install CM10 on it. On the CM wiki it says that "CyanogenMod on the Verizon variant of the Galaxy S3 you need to load an older bootloader."
I'm not clear to whether this means I just need an unlocked bootloader (which I have now from EZ Unlock) or if I need an entirely different bootloader, because looking at some forum posts for the official CM10.1, it only mentions that I need updated CWM or TWRP.
Any help would be appreciated.
Click to expand...
Click to collapse
I installed it without modifying my bootloader, just rooted, unlocked and flashed CWM then flashed many CM ROMs (10 nightly's, 10 stable and 10.1 nightly's)
root. unlock bootloader. download rom manager from store. flash away in recovery.
do a search, theres guides EVERYWHERE.
ddurandSGS3 said:
root. unlock bootloader. download rom manager from store. flash away in recovery.
do a search, theres guides EVERYWHERE.
Click to expand...
Click to collapse
There are guides everywhere, but they don't mention the need to flash an older bootloader, yet the how-to guide on the cm wiki says to. A little odd don't you think. I just want to get my facts straight before I turn my 2 day old sgs3 into a brick.
siriusgamer said:
There are guides everywhere, but they don't mention the need to flash an older bootloader, yet the how-to guide on the cm wiki says to. A little odd don't you think. I just want to get my facts straight before I turn my 2 day old sgs3 into a brick.
Click to expand...
Click to collapse
What they mean by the older bootloader is to unlock it. The way we unlock the bootloader is with a leaked EC build that was never officially released for our phone. So just do what others are saying, backup your imei/custom recovery/root/unlock bootloader and flash away
Thanks, that cleared up things for me.
But one more question, I didn't accept the OTA to JB when I first got this phone and I'm still on ICS, can I go from ICS to JB or would I have to accept the OTA/ flash JB through odin first?
This also applies to if I wanted to go from jb to ics. Can I just flash an ics Rom over a jb Rom or is Odin required.
I'm currently on Android 4.1.2 using Baked 6 and I want to upgrade to Baked 8, or anything on 4.2 for that matter. If I update a ROM, does this also mean it updates my bootloader? If not how to I properly update my bootloader without bricking my tablet? I've been reading around but there's so much data on the forums that I feel like I'm going to accidentally make a mistake
lifewater said:
I'm currently on Android 4.1.2 using Baked 6 and I want to upgrade to Baked 8, or anything on 4.2 for that matter. If I update a ROM, does this also mean it updates my bootloader? If not how to I properly update my bootloader without bricking my tablet? I've been reading around but there's so much data on the forums that I feel like I'm going to accidentally make a mistake
Click to expand...
Click to collapse
No flashing a custom rom will not upgrade your bootloader, only the stock asus firmwares will do this or a custom made blob file.
There are several methods to upgrade your bootloader to a JB 4.2 bootloader which can be found here or here. I prefer using the fastboot method for upgrading but up to you. Just make sure that once you've upgraded your bootloader to a 4.2 bootloader that you flash a -4.2 version of twrp or you will brick. I would suggest upgrading to JB 4.2 - 10.6.1.15.3 & twrp 2.5.0.0-4.2 as I find this more stable than 10.6.1.8 & twrp 2.4.4.0-4.2
If using the fastboot method and you need any help with any step just let me know.
I was on the 9.30 OTA and installed the KK ota via @SamuriHL method.... I rooted and unlocked the bootloader.
Next I installed CWM for KK and tried installing Mokee @Ryuinferno. Now I am in a bootloop. What could have gone wrong?
kpaliyath said:
I was on the 9.30 OTA and installed the KK ota via @SamuriHL method.... I rooted and unlocked the bootloader.
Next I installed CWM for KK and tried installing Mokee @Ryuinferno. Now I am in a bootloop. What could have gone wrong?
Click to expand...
Click to collapse
You must factory reset
Ryuinferno said:
You must factory reset
Click to expand...
Click to collapse
Nope didnt work. Should I have downgraded to JB and done this? I am not sure about that though as the ROM is KK
kpaliyath said:
Nope didnt work. Should I have downgraded to JB and done this? I am not sure about that though as the ROM is KK
Click to expand...
Click to collapse
I am not sure as this is device specific... sorry...as long as recovery is compatible it should work
kpaliyath said:
Nope didnt work. Should I have downgraded to JB and done this? I am not sure about that though as the ROM is KK
Click to expand...
Click to collapse
The ROM is KK but it was not designed for the latest boot loader version, I think. The only custom rom that will work with the most recent OTA boot loader are dhacker's test builds
You have to either downgrade the boot loader, use one of the test builds or revert to stock system.
RCOO said:
The ROM is KK but it was not designed for the latest boot loader version, I think. The only custom rom that will work with the most recent OTA boot loader are dhacker's test builds
You have to either downgrade the boot loader, use one of the test builds or revert to stock system.
Click to expand...
Click to collapse
Thanks a lot @RCOO...... I have flashed back Samuri's Stock KK.... I was worried it had hard bricked....
Will try downgrading and then flash back n see what happens....:fingers-crossed:
whao there
kpaliyath said:
I was on the 9.30 OTA and installed the KK ota via @SamuriHL method.... I rooted and unlocked the bootloader.
Next I installed CWM for KK and tried installing Mokee @Ryuinferno. Now I am in a bootloop. What could have gone wrong?
Click to expand...
Click to collapse
i did something very similiar. from what i understand (which isnt muchLOL). but Dhacker29 told me that once you upgrade you have to use the new kitkat bootloader. and the new bootloader only works with roms that have upgraded kernels 3.5 or higher(i think) so right at this momoent there are next to no roms but you can either use stock and modify it yourself or you can give Dhackers test build which isnt bad it has a few bugs but all the hardware works so far and my RAZR HD is playing games it couldnt touch before at all. here give this a try( oh turn off touch sounds to get rid of that anoying popping/cracking sound) i started this thread after having the same issues LMAO in it u will find links to the test rom . hope this helps
http://forum.xda-developers.com/showthread.php?t=2789490
@JohnnyMcG... I did the downgrade and it worked.... Flashed mokee and it works like a charm.
Sent from my DROID RAZR HD using Tapatalk
Currently my phone is on 4.1.2 bonestock ROM with [VRBMF1] and I believe the bootloader is unlocked. I've been out of the loop for so long that I dont know what the best way to get to 4.3 is while keeping my root and bootloader unlocked. Any help is appreciated!
Wolfmother1257 said:
Currently my phone is on 4.1.2 bonestock ROM with [VRBMF1] and I believe the bootloader is unlocked. I've been out of the loop for so long that I dont know what the best way to get to 4.3 is while keeping my root and bootloader unlocked. Any help is appreciated!
Click to expand...
Click to collapse
First, a caveat: Android 4.4 was just released for our phones a couple days ago, so you may want to wait a little while and see if any ROMs based on it come out. As of right now, there isn't a rooted version available, so 4.3 is your only option.
If you're on Bonestock, your bootloader is in fact unlocked. You can flash any of the 4.3 ROMs you find in the Android Development section. You should update your recovery first, I use TWRP version 2.6.3.0, the newest version is 2.7.1.0.
You should also flash the newer modem for the phone, VRUCML1, first, you can find that here under the Modems folder: http://d-h.st/users/invisiblek/?fld_id=35604#files. Only do that if you are actually going to update to a 4.3 ROM. Then you can flash any ROM you like: CleanROM 8.2 would be my pick, there's also Alliance and MOAR.
Jacquestrapp said:
First, a caveat: Android 4.4 was just released for our phones a couple days ago, so you may want to wait a little while and see if any ROMs based on it come out. As of right now, there isn't a rooted version available, so 4.3 is your only option.
If you're on Bonestock, your bootloader is in fact unlocked. You can flash any of the 4.3 ROMs you find in the Android Development section. You should update your recovery first, I use TWRP version 2.6.3.0, the newest version is 2.7.1.0.
You should also flash the newer modem for the phone, VRUCML1, first, you can find that here under the Modems folder: . Only do that if you are actually going to update to a 4.3 ROM. Then you can flash any ROM you like: CleanROM 8.2 would be my pick, there's also Alliance and MOAR.
Click to expand...
Click to collapse
Thank bud, this is exactly what I needed!
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.