An official CM12 commit for tomorrow's nightly will ask for the bootloader to be updated.
One way would be to flash back to stock and take the LP OTA update.
Alternatively, you may be able to find an LP ROM that is compatible with your phone, extract the motoboot file, and flash it using fastboot, although the safest would be via an OTA update.
audit13 said:
One way would be to flash back to stock and take the LP OTA update.
Alternatively, you may be able to find an LP ROM that is compatible with your phone, extract the motoboot file, and flash it using fastboot, although the safest would be via an OTA update.
Click to expand...
Click to collapse
Strange, I've seen steps for flashing Lollipop on CDMA devices that makes you first flash the full GSM fastboot package then the radio files - doesn't this mean the bootloaders are actually interchangeable?
Also, I found a link for XT1031's lollipop OTA, but unpacking it reveals nothing related to the bootloader...
EDIT: Sh*t - I updated manually to the new bootloader, but the existing CM12 starts to exhibit screen flickering issues (shaking stripe moving vertically across the screen). It seems the new bootloader needs to be paired with the new CM build.
Sent from ARChon Runtime @ Chromium 42
Yeah, the flickering will also be fixed by flashing a stock LP ROM.
audit13 said:
Yeah, the flickering will also be fixed by flashing a stock LP ROM.
Click to expand...
Click to collapse
Stock ROM isn't necessary - the latest CM build has it fixed The recovery still flickers though (because it's built upon 4.4 blobs?).
Sent from Google Nexus 4 @ CM12
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
No flickering in stock lollipop recovery, only custom I think
The last cm12 deals with the flickering I believe, but earlier builds have it.
Related
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.
Hi all,
I just tried to upgrade my old CyanogenMod from January to a recent nightly and got hit by an error caused by my old KK bootloader (http://forum.xda-developers.com/mot...uently-questions-t2996087/page24#post59520890). The guy in that thread offers a supposedly official Brazilian Lollipop bootloader, but I'm a bit hesitant 1) downloading something like that from unknown origin on the net and 2) I have a UK XT1032 (I think it was unbranded, bought in Tesco), not Brazilian. So what are my options?
Can I get the official bootloader from Motorola, by downgrading to 4.4.4 and then get the OTA? Or is it not available yet for my phone?
If I were to do that, can I unlock/root the phone again and get a custom ROM or is there no unlock yet for the Moto stock LP stuff?
What are my options, besides staying on my January CM ROM?
Thank you very much for any input!
You could manually flash the GB 4.4.4 stock ROM for the xt1032, update apps, take the 5.02 OTA update, and be running a Lollipop bootloader.
I just flash manually stock 5.0.2
Mister Muscle said:
I just flash manually stock 5.0.2
Click to expand...
Click to collapse
Which version do you recommend for the xt1032?
Or, if you're skilled enough, just manually fastboot flash the tz, rpm, sdi, aboot and sbl1 partitions extracted from any 5.0.x OTA package for XT1032. I did the procedure on my 1031 (with corresponding files for the 1031, of course) and it worked nicely.
Sent from Google Nexus 4 @ CM12
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
here's one more option http://forum.xda-developers.com/moto-g/help/rc-faq-cm12-frequently-questions-t2996087/post59520890#post59520890 .
it doesn't need the ota-update-way
audit13 said:
You could manually flash the GB 4.4.4 stock ROM for the xt1032, update apps, take the 5.02 OTA update, and be running a Lollipop bootloader.
Click to expand...
Click to collapse
That sounds like a good plan. So
1) GB 5.02 OTA is already out for all XT1032 devices? I read somewhere else we're still waiting?
2) Is my phone still unlocked after this, i.e. can I install a custom recovery, root etc. and custom roms afterwards?
Thanks =)
The 5.02 OTA for GB ROM has been released from what I have read.
Once the phone is sim and bootloader unlocked, flashing ROMs, recoveries, etc. will not relock the bootloader or sim lock the phone.
audit13 said:
The 5.02 OTA for GB ROM has been released from what I have read.
Once the phone is sim and bootloader unlocked, flashing ROMs, recoveries, etc. will not relock the bootloader or sim lock the phone.
Click to expand...
Click to collapse
That's great to know! My worries was about that flashing the bootloader could result in a newly locked one. Thank you very much!
Hello forum, basically, when I got my moto G, it was on 4.3, so I did all the bits, and the step i did after all the rooting unlocking etc was upgraded my bootloader to the lollipop one (ending in 8 i believe) - which i wish i didnt do, and cant downgrade to 4.4.4 (or can I without bricking)......right back to the story.......the problem now is, whenever i try uninstalling apps, or wiping data in any app etc, my phone does a reboot, I installed the brazillian 5.0.2 flashable rom (the optimised one) which worked perfectly, did all the correct wipes etc, but it reboots when uninstalling apps......, and thought i would try dirty unicorns....works well except the rebooting problem...... help....what can I do????????
I read somewhere that maybe to solve it, you gotta change runtime from dalvik to ART, but there is no option to change this....
There are no 5.0.2 uk images available that i have read (so i cant completely get back to complete factory settings)
I really wished i kept the KK bootloader!!!! so who can help me????? I want to try some of the great CM11 builds!!!
Since your bootloader is unlocked and you have the lollipop bootloader, I suggest flashing the stock 4.4.4 (not 4.4.2) ROM for your xt1032 (you will not be able to flash the motoboot file so don't bother trying), upgrade the Motorola apps via Play store, and take the 5.02 OTA update.
FInd your stock ROM here: http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=filename&order=ASC&show=100&page=1
audit13 said:
Since your bootloader is unlocked and you have the lollipop bootloader, I suggest flashing the stock 4.4.4 (not 4.4.2) ROM for your xt1032 (you will not be able to flash the motoboot file so don't bother trying), upgrade the Motorola apps via Play store, and take the 5.02 OTA update.
FInd your stock ROM here: http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=filename&order=ASC&show=100&page=1
Click to expand...
Click to collapse
do i have to update to 5.0.2 again? as i want to try cm11 again
@audit13 is this a flashable zip, or do you need to do it via fastboot? as its got a bootloader included in the zip (4.4.4 kitkat bootloader)
The files from filefactory need to be unzipped and flashed via fastboot or mfastboot.
You do not need to do anything with the stock ROM if you want to install a custom ROM. All you need to do is install a compatible custom recovery and a custom ROM. I suggest flashing right to the latest CM12 rather than using CM11.
I suggested flashing back to the stock for your phone and upgrading to 5.02 via OTA to see if the uninstall problem goes away.
yep understood @audit13 read your other posts on this matter too, the reason I want to use a cm11 rom, is I had a moto g about 8-9 months ago, and there was a rom i loved, and it was cm11 based......will i brick if i do flash this cm11 rom? i know about flickering bug, and possible hard brick if i went back to versions below 4.4.4 ...... and i love cyanogenmod roms, as i dont get irritating moto updates etc
Flashing CM11 should not be a problem as CM11 ROMs do not touch the bootloader or modem.
so basically, downgrade to the 4.4.4 firmware file, and cm11 and im done? yeah?
You can try to flash cm11 directly over stock 5.02. If it doesn't work, you may have to flash back to stock 4.4.4, install recovery, and then flash cm11.
Hey guys, so I've unlocked the bootloader, flashed TWRP 2.8.6.0, got a rom, kernel and some minimal gapps.
I found out that flashing any CM12 rom directly will bootloop on the moto G. So I flashed a CM11 snapshot build (M6), but now the screen has a flicker, sort of an analog, old TV flicker that goes up and down, distorting the image.
I've also found out that in order to fix that you have to flash stock 5.0.2. Since it's a xt1032 that came with KITKAT 4.4.2, I thought that flashing this would fix it, but gives me an error.
Therefore, what is the adequate way to flash a stock 5.0.2 rom in order to upgrade the rom, bootloader and modem? Can they be done separately? I figure that's what's missing in order to fix the flickering.
Thank you.
Choristav said:
Hey guys, so I've unlocked the bootloader, flashed TWRP 2.8.6.0, got a rom, kernel and some minimal gapps.
I found out that flashing any CM12 rom directly will bootloop on the moto G. So I flashed a CM11 snapshot build (M6), but now the screen has a flicker, sort of an analog, old TV flicker that goes up and down, distorting the image.
I've also found out that in order to fix that you have to flash stock 5.0.2. Since it's a xt1032 that came with KITKAT 4.4.2, I thought that flashing this would fix it, but gives me an error.
Therefore, what is the adequate way to flash a stock 5.0.2 rom in order to upgrade the rom, bootloader and modem? Can they be done separately? I figure that's what's missing in order to fix the flickering.
Thank you.
Click to expand...
Click to collapse
First tell me your bootloader version
And you don't need to flash stock lollipop to correct the screen flicker issue you just need the updated bootloader
sjandroiddeveloper said:
First tell me your bootloader version
And you don't need to flash stock lollipop to correct the screen flicker issue you just need the updated bootloader
Click to expand...
Click to collapse
How can I find the bootloader version exactly? The device came with kitkat 4.4.2, so I guess it's that!
Choristav said:
How can I find the bootloader version exactly? The device came with kitkat 4.4.2, so I guess it's that!
Click to expand...
Click to collapse
Boot into bootloader and see there it should be like 41.xx
I wanna Downgrade back to Stock 5.1 but my question is, do I have any problems with bootloader, flickering or OTA's if I downgrade from 6.0.1 CM13 to 5.1 Pure Stock?
And should I think about something before I downgrade?
Push
You can do it through MFastboot method, and you won't have any problem at all. Just download right version for your region and you're done.
razor001_ said:
You can do it through MFastboot method, and you won't have any problem at all. Just download right version for your region and you're done.
Click to expand...
Click to collapse
I got a flashable zip?
can i flash it or do i need to use the mfastboot method?
It will be fine with that flashable ZIP... it's just like another ROM. I told you MFastboot method because that way you're making sure that everything is stock and not Modified.
razor001_ said:
It will be fine with that flashable ZIP... it's just like another ROM. I told you MFastboot method because that way you're making sure that everything is stock and not Modified.
Click to expand...
Click to collapse
Is a factory reset/ all wipe not enough to flash it normaly?
or why mfastboot?
Well, If you want everything Stock then you must do it through MFastboot method. with the ZIP that you have it will be a stock ROM; but your Recovery and Bootlogo still are modded (Recovery will be CWM or TWRP, and your bootlogo stays the same you have right now, not the warning you get when you unlock the Bootloader)
Edit: both ways to do it are fine... Just different results at the end.
razor001_ said:
Well, If you want everything Stock then you must do it through MFastboot method. with the ZIP that you have it will be a stock ROM; but your Recovery and Bootlogo still are modded (Recovery will be CWM or TWRP, and your bootlogo stays the same you have right now, not the warning you get when you unlock the Bootloader)
Edit: both ways to do it are fine... Just different results at the end.
Click to expand...
Click to collapse
So what are the results if I only flash it instead of mfastboot?
Flash Zip: Stock ROM, modified recovery, and if in the past you flashed a bootlogo it will stay the same. (If in the future you want to flash again CM or any other ROM this is the best)
Mfastboot: Stock ROM, stock recovery, and stock bootlogo (the one with the warning of unlocked bootloader) (if in the future you want to flash again CM or other ROM you'll have to flash the recovery first and then flash your ROM)
Sent from my Moto G using XDA Labs
razor001_ said:
Flash Zip: Stock ROM, modified recovery, and if in the past you flashed a bootlogo it will stay the same. (If in the future you want to flash again CM or any other ROM this is the best)
Mfastboot: Stock ROM, stock recovery, and stock bootlogo (the one with the warning of unlocked bootloader) (if in the future you want to flash again CM or other ROM you'll have to flash the recovery first and then flash your ROM)
Sent from my Moto G using XDA Labs
Click to expand...
Click to collapse
Okay thx for the Info
But my phone will not get bricked or flickering because of bootloader?
I know it gets bricked if I go from MM to KK.
It won't... Flicker happens because some kernel implementations changed from KitKat to Lollipop. And the bricked devices were because people tried to flash KitKat bootloader (motoboot.bin) and partition table (gpt.bin or something like that) on top of Lollipop.
But as our Moto G 1st gen didn't get past Official Lollipop there isn't a new bootloader version released. And CM13 is implemented over the same Lollipop bootloader. So don't worry about bricking your device if you wanna downgrade to Stock Lollipop.
Sent from my Moto G using XDA Labs
razor001_ said:
It won't... Flicker happens because some kernel implementations changed from KitKat to Lollipop. And the bricked devices were because people tried to flash KitKat bootloader (motoboot.bin) and partition table (gpt.bin or something like that) on top of Lollipop.
But as our Moto G 1st gen didn't get past Official Lollipop there isn't a new bootloader version released. And CM13 is implemented over the same Lollipop bootloader. So don't worry about bricking your device if you wanna downgrade to Stock Lollipop.
Sent from my Moto G using XDA Labs
Click to expand...
Click to collapse
Okay Thanks
I think not brick