i have a Boost mobile moto G and was wondering if roms are compatible with it because every one i have tried thats lollipop has spit out the status 7 error because the bootloader is not in the updater-script so i want to make sure that adding my bootloader to that list, or removing the line completely wont screw up the device, i have read on a few threads that 41.18 and a few others redid the partition table.
long story short, im just wanting to know if flashing a rom with no bootloader support will mess up the device.
Thanks for your time and input.
You will get screen flickers, but that goes away just minutes after each time you power on the phone. Aside from that I haven't heard about anything.
Nevertheless, upgrading isn't hard (although it is a bit risky), so if you aren't going to return to 4.x ROMs, maybe consider doing the upgrade?
Sent from Google Nexus 4 @ CM12.1
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
What upgrade are you talking about? The soak test?
Sent from my Nexus 7 using Tapatalk
crazymonkey05 said:
What upgrade are you talking about? The soak test?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I mean upgrading the bootloader of course. The development section has tools for that, or I have a flashable zip for that, although fiddling with bootloader always involves some risks. Proceed with caution.
Sent from Google Nexus 4 @ CM12.1
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
OK thanks for the info I guess I'll just use 41.13 till the ota hits me
Sent from my Nexus 7 using Tapatalk
AndyYan said:
I mean upgrading the bootloader of course. The development section has tools for that, or I have a flashable zip for that, although fiddling with bootloader always involves some risks. Proceed with caution.
Sent from Google Nexus 4 @ CM12.1
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
Click to expand...
Click to collapse
I'll take that flashable zip if you still have it. I'll be able to flash it with TWRP 2.8, right? Will I be unable to install 4.X roms if I update the bootloader?
Ryan11271 said:
I'll take that flashable zip if you still have it. I'll be able to flash it with TWRP 2.8, right? Will I be unable to install 4.X roms if I update the bootloader?
Click to expand...
Click to collapse
You will be able to install 4.4, but they will be haunted with screen flickering on startup. Also, standard risks of fiddling with the bootloader apply. PM me if you want to take the risk.
Sent from Google Nexus 4 @ CM12.1
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
Related
I have tried to put cm12 on my phone and it says that recovery is not compatible.
Does it matter that i have 4.4 bootloader on my phone? Is there a way to update the bootloader easily? Thanks!
Please update your recovery to CWM 6.0 4.8+ or TWRP 2.8.0.0+. Also, if you're flashing the latest nightlies, yes you have to upgrade your bootloader. And no, you don't need to flash to stock to do that - simply flash the bootloader partitions via fastboot.
Sent from Google Nexus 4 @ CM12
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
AndyYan said:
Please update your recovery to CWM 6.0 4.8+ or TWRP 2.8.0.0+. Also, if you're flashing the latest nightlies, yes you have to upgrade your bootloader. And no, you don't need to flash to stock to do that - simply flash the bootloader partitions via fastboot.
Sent from Google Nexus 4 @ CM12
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
Click to expand...
Click to collapse
Where do you find the bootloader to update? I've been looking all over XDA and Google for a while and still haven't found anything.
Edit: Never mind, I found it on youtube
I think you should install recent ROM for that
.
Sent from my Moto G using XDA Free mobile app
It would be great if some established developer help me.
And i am planning to upgrade to cm12. Now on stock kitkat, rooted, unlocked BT. So the process should be- flash LP bootloader, flash latest recovery, format everything and then flash the cm 12 zip.
Right?
This should do: http://d-h.st/rI1n - flash it in any custom recovery. Made for XT1033 but should work for 1032 also.
Keep in mind: the original creator of the package is not me - I only modified it to put in files specific to XT1033 and prevent flashing a few suspicious partitions. Because I manually updated mine using fastboot, I can't test out the package personally, but responses from my Chinese community and other XDA fellows are fairly positive.
Also, remember that 1) 5.0 BL will cause screen flicker on non 5.0 ROMs and 2) you can't downgrade BL after you've upgraded, so decide if you really want it before you proceed.
Sent from Google Nexus 4 @ CM12
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
AndyYan said:
This should do: http://d-h.st/rI1n - flash it in any custom recovery. Made for XT1033 but should work for 1032 also.
Keep in mind: the original creator of the package is not me - I only modified it to put in files specific to XT1033 and prevent flashing a few suspicious partitions. Because I manually updated mine using fastboot, I can't test out the package personally, but responses from my Chinese community and other XDA fellows are fairly positive.
Also, remember that 1) 5.0 BL will cause screen flicker on non 5.0 ROMs and 2) you can't downgrade BL after you've upgraded, so decide if you really want it before you proceed.
Sent from Google Nexus 4 @ CM12
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
Click to expand...
Click to collapse
So this is not original bootloader? And why you modified it. How many people have tested it on indian xt1033..... and last question- can i flash this bootloader using flashify app...
I am asking these questions because one wrong move and the phone will be permanently bricked.
Guru.Eclairs said:
So this is not original bootloader? And why you modified it. How many people have tested it on indian xt1033..... and last question- can i flash this bootloader using flashify app...
I am asking these questions because one wrong move and the phone will be permanently bricked.
Click to expand...
Click to collapse
It is the original bootloader. The people who provided me this also had 2 extra partitions packaged inside: fsg and gpt, and all I did was to remove them.
As of now, tens of Chinese fellows have tested out the original package, while 2 XDA members tested out my package, with full success.
And please, instead of using helper apps like Flashify, just learn to use a proper custom recovery.
Sent from Google Nexus 4 @ CM12
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
AndyYan said:
It is the original bootloader. The people who provided me this also had 2 extra partitions packaged inside: fsg and gpt, and all I did was to remove them.
As of now, tens of Chinese fellows have tested out the original package, while 2 XDA members tested out my package, with full success.
And please, instead of using helper apps like Flashify, just learn to use a proper custom recovery.
Sent from Google Nexus 4 @ CM12
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update][/QUOT
I know how to flash files using recovery. Actually you are right.. using flashing apps for sensitive things like bootloader is not fully safe. Thanks for the information.
Last question- What are fsg and gpt files.??
I think you should start a new thread on this bootloader topic in either moto g Q&A section or General section. I found no such particular thread. It will be helpful for those on KitKat or JB bootloaders.
Click to expand...
Click to collapse
Guru.Eclairs said:
I know how to flash files using recovery. Actually you are right.. using flashing apps for sensitive things like bootloader is not fully safe. Thanks for the information.
Last question- What are fsg and gpt files.??
I think you should start a new thread on this bootloader topic in either moto g Q&A section or General section. I found no such particular thread. It will be helpful for those on KitKat or JB bootloaders.
Click to expand...
Click to collapse
The bootloader for some variants of Moto G is still not made public yet and is (said to be) covered by an NDA, so I'm hesitant to make a dedicated thread for this - but if request is high then I surely will.
fsg goes for the baseband and gpt for the partition table. The baseband is different for each variant and each region, and flashing a new partition table when having an existing ROM might put a threat to your data, so I removed them for safety.
Sent from Google Nexus 4 @ CM12
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
So today I decided to install CM12.1 after finally unlocking the bootloader and installing root but when I installed it normally it wont boot. In fact any custom ROM I installed it wont work. I was originally on Stock 4.4.3 and even tried the guides here for solving the problem but it wont work! Help please?
Restore to the stock Android 4.4.3 and then OTA to 4.4.4 and then OTA 5.0.2 to get the new bootloader and now you can flash costum ROMs.
Eurofighter_ty said:
Restore to the stock Android 4.4.3 and then OTA to 4.4.4 and then OTA 5.0.2 to get the new bootloader and now you can flash costum ROMs.
Click to expand...
Click to collapse
Cant OTA to 4.4.4. as my phone will get hard bricked. Already flashed Lollipop bootloader and still on 4.4.3.
Flash and boot CM11 first. CM11 builds are deleted by the official server, but can be found by searching around the web.
Sent from Google Nexus 4 @ CM12
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
AndyYan said:
Flash and boot CM11 first. CM11 builds are deleted by the official server, but can be found by searching around the web.
Sent from Google Nexus 4 @ CM12
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
Click to expand...
Click to collapse
Thanks a lot man! I don't know what was wrong but it quite solved the problem!
I got hotspot tethering problem on cm12.1 masterawesome build.
Hotspot tethering unable to start and displaying error.
Is this cm bug? Or devices specifically? There is no problem with hotspot tethering with stock 5.0 rom.
Another problem is about horizontal line flickering on recovery. I read that screen flickering because of bootloader. But i have 41.18, so bootloader must not be the problem.
The flickering only occur on recovery and no problem on rom.
Thanks.
riyosakura said:
Another problem is about horizontal line flickering on recovery. I read that screen flickering because of bootloader. But i have 41.18, so bootloader must not be the problem.
The flickering only occur on recovery and no problem on rom.
Thanks.
Click to expand...
Click to collapse
Oops, mistakenly clicked Thanks...
Recovery is built using 4.4 blobs and is not affected by the ROM's version. Just upgrade it to TWRP 2.8.6.x (Development section has it) and the flicker should be gone.
Sent from Google Nexus 4 @ CM12
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
AndyYan said:
Oops, mistakenly clicked Thanks...
Recovery is built using 4.4 blobs and is not affected by the ROM's version. Just upgrade it to TWRP 2.8.6.x (Development section has it) and the flicker should be gone.
Sent from Google Nexus 4 @ CM12
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
Click to expand...
Click to collapse
What about the hotspot tethering?
i've attached logcat on the post.
is there anyway to fix this?
Hi
Stock 5.1.1 LMY48B
rooted with TWRP installed.
Can I flash to CM12.1 just by flashing the zip from TWRP ?
will I lose any data ? Do I need to worry about bootloader or radio versions ?
If I want to go back is it as simple as flashing my nandroid backup ?
Thanks
Sent from my Nexus 7 using XDA Free mobile app
Anyone?
Thanks
Sent from my Nexus 7 using XDA Free mobile app
albert_htc said:
Hi
Stock 5.1.1 LMY48B
rooted with TWRP installed.
Can I flash to CM12.1 just by flashing the zip from TWRP ?
will I lose any data ? Do I need to worry about bootloader or radio versions ?
If I want to go back is it as simple as flashing my nandroid backup ?
Thanks
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
As I know going from rom to rom you need to make a factory reset.
That will remove all what is stored on /data
All apps, cache and dalvik cache.
All other data insidr /storage/sdcard will be on safe
As I know stock rom cannot be restored, but I just take this device before 1 day. I don't know for that, because on mine previous phone that was impossible
Sent from my Nexus 5 using Tapatalk
albert_htc said:
will I lose any data ? Do I need to worry about bootloader or radio versions ?
Click to expand...
Click to collapse
CM nightlies include a radio and bootloader so you don't have to worry about that.
albert_htc said:
If I want to go back is it as simple as flashing my nandroid backup ?
Click to expand...
Click to collapse
Even if I never tried you should be able to restore a stock nandroid backup thru TWRP (you don't flash anything).
Thanks I'll try this at the weekend ?
Sent from my Nexus 7 using XDA Free mobile app
Primokorn said:
CM nightlies include a radio and bootloader so you don't have to worry about that.
Click to expand...
Click to collapse
No they don't.
But since he's upgraded to stock 5.1.x already, everything is up to date and there's nothing to worry about. Besides, Google's bootloaders usually have good forward- and backward-compatibility.
Sent from Google Nexus 4 @ CM12.1
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
AndyYan said:
No they don't.
Click to expand...
Click to collapse
From Jira:
Me => CM (AOSP) is the only rom which has a bootloader and a radio into its zip. Why? Could you remove them?
I was on the newest bootloader HHz12f and a radio from KRT16M. Every time I flash CM nightlies I have to update my bootloader and flash an older radio. Very annoying.
Thank you.
CM Team => Sorry, we will continue to ship both. It saves us more headaches in the long run. Thanks for your understanding.
It's as simple as that.
AndyYan said:
But since he's upgraded to stock 5.1.x already, everything is up to date and there's nothing to worry about. Besides, Google's bootloaders usually have good forward- and backward-compatibility.
Click to expand...
Click to collapse
Custom ROMs have a check into their update-script for the bootloader version. If you don't have the good one then you can't flash it.