I flashed boot loader of umts Moto G on my umtsds Moto G when I converted it to GPE rom, and after that phone's boot loader got updated when I flashed 4.4.4 OTA.
Since then my phone is recognized as XT1032
Now, for some warranty reasons, I want my phone to be seen as XT1033, but I can't flash any umtsds boot.img on my phone because you can't downgrade bootloader on Moto G.
So... I was just wondering if it is possible to skip the stupid version check by flashing boot.img via custom recovery?
I don´t get it. Are you trying to flash the kernel or bootloader? Boot.img is the kernel and can be flashed through fastboot (given you have the correct kernel modules in /system).
Motoboot.img is the bootloader as far as i know...
knizmi said:
I don´t get it. Are you trying to flash the kernel or bootloader? Boot.img is the kernel and can be flashed through fastboot (given you have the correct kernel modules in /system).
Motoboot.img is the bootloader as far as i know...
Click to expand...
Click to collapse
I am not able to flash both actually. But I thought that boot.img is the bootloader.
Related
I tried to downgrade my moto g from GPE (converted it) to stock rom like it was before, and now it is stuck on bootloader screen with the "warning bootloader unlocked..." sign. Every rom I try to install has now the same problem, even the GPE rom. What should i do now?
GiorgosCyprus said:
I tried to downgrade my moto g from GPE (converted it) to stock rom like it was before, and now it is stuck on bootloader screen with the "warning bootloader unlocked..." sign. Every rom I try to install has now the same problem, even the GPE rom. What should i do now?
Click to expand...
Click to collapse
Are you on the 41.18 bootloader? If you are, don't flash the motoboot.img file as you can't downgrade the Lollipop bootloader (41.18).
Did you flash all img files including gpt?
audit13 said:
Are you on the 41.18 bootloader? If you are, don't flash the motoboot.img file as you can't downgrade the Lollipop bootloader (41.18).
Did you flash all img files including gpt?
Click to expand...
Click to collapse
yes i flashed all img files including gpt
GiorgosCyprus said:
yes i flashed all img files including gpt
Click to expand...
Click to collapse
Try flashing the 5.0.2 fastboot firmware image for your model:
http://forum.xda-developers.com/showpost.php?p=58534609&postcount=519
Try re-installing GPE 4.4.4 using fastboot and then install stock 4.4.4 using fastboot.
Hi, I've successfully installed Brazilian Stock ROM/Identity Crysis ROM (both Lollipop) on my XT1032 without any error using PhilzTouch 6.55 recovery, but everytime i try to install CM12/CM12-based ROM it will fail. Apparently because my bootloader is older than it should be. I've tried TWRP and it will fail too. Is there any recovery compatible with 41.05 BL? Or should i update it? I'd rather be able to downgrade to KK, so 41.13 will be ok, right? Also, how to update BL?
Regards
I believe the bootloader file is named motoboot.img and could be flashed using fastboot commands.
The motoboot file are included with stock firmware xml.zip files.
I just downgraded my XT1032 (falcon) from stock 5.0 to stock 4.4 and it won't boot anymore. I did it using the fastboot method (flashing several .img or .bin files using fastboot), as I had done it many times before in order to revert the phone to stock.
But this time it won't boot no matter what I do. It may be related to the fact that I accidentally tried to flash 4.4 partition table and bootloader (now I see the downgrading tutorials recommend against that) but I don't know what to do.
I tried pushing another ROM (in the ZIP format) via ADB, but when I try to install that ZIP in TWRP recovery, it says "unable to mount data" or "unable to mount storage". It also used to say "unable to mount system" but I think I fixed that with "fastboot format system" (which you can't do for /data).
I think I'd need Android 5 .img and .bin files in orden to fix this via fastboot, but Android 5 doesn't seem to exist in that format.
Can anyone think of a solution? Thanks in advance.
Does your phone still have the 41.18 bootloader on it?
I'm surprised that it bricked because I flash every partition except motoboot when downgrading my xt1032 8 GB from LP to KK.
U did it with unlocked bootloader or locked one..?? I am looking for a tutorial on downgrading to 4.4.4. from 5.0.2 for locked bootloader..
Unlocked bootloader. If possible, unlock the bootloader as you may not be able to downgrade without unlocking.
i am also faced this problem......after reflashing the kitkat os my moto g is booted(dont flash motoboot and gpt)
seshuganesh2011 said:
i am also faced this problem......after reflashing the kitkat os my moto g is booted(dont flash motoboot and gpt)
Click to expand...
Click to collapse
How did u reflashed..?? Can u tell me the xact procedure..?? And on Locked bootloader..??
kaymaddy said:
How did u reflashed..?? Can u tell me the xact procedure..?? And on Locked bootloader..??
Click to expand...
Click to collapse
i flashed on unlocked boot loader
Guys help me Ibricked my moto g .Here is what i did
I have a XT1033 on stock lollipop with unlocked bootloader. So i first flashed cwm using fastboot, booted fine in recovery and back to system.
Then i again entered fastboot mode and flashed TWRP 2.8.5 for XT1032(There was no specific for xt1033). Booted fine into recovery , took a backup of entire rom .It was fine till now. Then when i booted into system the phone was stuck at boot logo. It kept on restarting again and again and when i entered fastboot mode to enter into recovery the recovery partition was also corrupted and it was stuck at teamwin logo.
but the bad things didnt end here.When i flashed stock firmware using fastboot the system sparsechunk files falshed with an error "FILE IS TOO LARGE". I tried both 4.4.4 and 5.0.2 but its still stuck at bootlogo.
PLEASE HELP ME DEVS
here u go
Happened with me once
Follow this:
1.Flash gpe 4.4.2 firmware( u may have xt1033 but still flash it)
2.Don't update the gpe to 4.4.4 or ur device will hardbrick(don't cry afterwards)
3.flash asian 5.0.2 firmware from fastboot
4.enjoy!
is it safe to flash gpe 4.4.2 over over 5.0.2
And if i flash it am i supposed to flash it with or without gpt.bin and motoboot.img
and also while flashing asian 5.0.2 are these two commands needed to be flashed.
srisurya95 said:
Happened with me once
Follow this:
1.Flash gpe 4.4.2 firmware( u may have xt1033 but still flash it)
2.Don't update the gpe to 4.4.4 or ur device will hardbrick(don't cry afterwards)
3.flash asian 5.0.2 firmware from fastboot
4.enjoy!
Click to expand...
Click to collapse
is it safe to flash gpe 4.4.2 over asian 5.0.2(because flashing a gpe rom changes partitions on the device)
And if i flash it am i supposed to flash it with or without gpt.bin and motoboot.img and after flashing gpe 4.4.2 do i need to boot into OS or i need to directly flash 5.0.2 over it
and also while flashing asian 5.0.2 are these two commands needed to be flashed.
please reply
thanks
PS: Can you provide me the link to gpe 4.4.2 firmware and the fastboot commands i am not able to find them
sjandroiddeveloper said:
is it safe to flash gpe 4.4.2 over asian 5.0.2(because flashing a gpe rom changes partitions on the device)
And if i flash it am i supposed to flash it with or without gpt.bin and motoboot.img and after flashing gpe 4.4.2 do i need to boot into OS or i need to directly flash 5.0.2 over it
and also while flashing asian 5.0.2 are these two commands needed to be flashed.
EDIT:- after flashing,boot into OS
please reply
thanks
Click to expand...
Click to collapse
Flashing fastboot files will never hard brick the device...just don't play with OTA's
and yes while flashing 4.4.2 skip gpt and motoboot and while flashing asian 5.0.2 no need of skipping
srisurya95 said:
Flashing fastboot files will never hard brick the device...just don't play with OTA's
and yes while flashing 4.4.2 skip gpt and motoboot and while flashing asian 5.0.2 no need of skipping
Click to expand...
Click to collapse
sorry but you didnt answer all my questions-
1 will flashing gpe 4.4.2 change partitions on device which will result in errors while flashing asian 5.0.2 over it
2 do i need to boot after flashing 4.4.2 gpe
and please provide the link for gpe 4.4.2 with fastboot commands because they are different from stock motoroms
sjandroiddeveloper said:
sorry but you didnt answer all my questions-
1 will flashing gpe 4.4.2 change partitions on device which will result in errors while flashing asian 5.0.2 over it
2 do i need to boot after flashing 4.4.2 gpe
and please provide the link for gpe 4.4.2 with fastboot commands because they are different from stock motoroms
Click to expand...
Click to collapse
yes u have to boot
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