Hi all,
About a month ago or so I updated my Moto G 2013 from 4.4.4 GPE to 5.0.1 GPE.
Then I rooted it using Chainfire Autoroot.
What I didn't know back then was that CF auto root screws your stock recovery.. (with all due respect to this great developer)
Auto root also prevents my from installing custom recoveries. (They just won't work).
I faced the same problem on my Nexus 7 2013. That problem could easily be solved by flashing again stock ROM image.
But since there is no 5.0.1 GPE image available for the Moto G it seems impossible to fix this..
Unluckily, Motorola doesn't allow us to downgrade to KitKat or Jelly Bean. (Yes.. I know there are ways to downgrade by skipping some commands, but there are several reports that it will cause screen flickering because the new Lollipop bootloader doesn't work properly on stock Kitkat ROM.)
So I guess I'm pretty stuck right know.
I guess factory resetting my phone would already hard brick the phone (because of the bricked stock recovery by cf auto root)
I would like to have Lollipop 5.0.1 GPE with TWRP recovery, so I can install custom kernels etc.
Do I have to wait for the Lollipop image? Or are there other ways of reaching my goal?
Any idea when we can expect the image to be released?
Thanks in advance!
I installed stock KK on a my Telus moto g with the L bootloader and the flickering was still be there. Just don't flash the motoboot.img file in fastboot.
I always found that the easiest way to get root is to flash supersu from a custom recovery.
Related
Here's the scenario:
I converted Moto G XT1033 4.4.4 to GPE 4.4.2
Then upgraded to GPE 4.4.4 and GPE 5.0.1, both by OTA
GPE 5.0.1 OTA ended up in softbrick
So now I cannot repeat the process beacause of the new bootloader, GPE 5.0.1 OTA brought with itself. And that bootloader would cause a hardbrick if I tried GPE 4.4.4 OTA on the device now
Questions: (No question is related to the other)
Would I be able to install Stock Lollipop OTA when I get one on 'Stock rom'? (I can revert to Stock 4.4.4) Would Stock Lollipop OTA mess up with the current bootloader, GPE Lollipop OTA has installed?
Is there any way I could flash Lollipop Stock image later, when it's available?
What can I do to set things right with the 'bootloader messup' that's caused right now?
Thanks, in advance!
emarld2011 said:
Here's the scenario:
I converted Moto G XT1033 4.4.4 to GPE 4.4.2
Then upgraded to GPE 4.4.4 and GPE 5.0.1, both by OTA
GPE 5.0.1 OTA ended up in softbrick
So now I cannot repeat the process beacause of the new bootloader, GPE 5.0.1 OTA brought with itself. And that bootloader would cause a hardbrick if I tried GPE 4.4.4 OTA on the device now
Questions: (No question is related to the other)
Would I be able to install Stock Lollipop OTA when I get one on 'Stock rom'? (I can revert to Stock 4.4.4) Would Stock Lollipop OTA mess up with the current bootloader, GPE Lollipop OTA has installed?
Is there any way I could flash Lollipop Stock image later, when it's available?
What can I do to set things right with the 'bootloader messup' that's caused right now?
Thanks, in advance!
Click to expand...
Click to collapse
You are another who has made a stupid mistake, you should HAVE READ MY THREAD!
You need to wait untill the Lollipop Factory images are published, then we can get a blankflasher and restore your bootloader.
Once your bootloader is working again, you can flash Lollipop without problems.
You need to wait 1 or 2 months.
GI0\/\NNI said:
You are another who has made a stupid mistake, you should HAVE READ MY THREAD!
You need to wait untill the Lollipop Factory images are published, then we can get a blankflasher and restore your bootloader.
Once your bootloader is working again, you can flash Lollipop without problems.
You need to wait 1 or 2 months.
Click to expand...
Click to collapse
Nope. I did read your thread after softbrick. And that's why I didn't install any OTA's after v5's.
I flashed 4.4.4. It's not an OTA!
I'm currently running 4.4.4 on 5.x bootloader.
Now what I'm asking is,
Would I be able to install 5.x OTA when I get it?
Before the factory image and all that thing.
PS: 5.x hasn't arrived for general public in INDIA yet. What I was trying was Brazil OTA.
Hi all,
When I install a custom recovery, it(recovery) won't boot up because of CF auto root. I don't know why, it just doesn't work anymore. I've got the same problem on my Nexus 7 2013. But on the Moto G, this is harder to fix because the 5.0.1 GPE image for Moto G is not available yet. (You can only get 5.0.1 GPE using an OTA link)
I would like like to have 5.0.1 GPE with working TWRP recovery and root acces.
To achieve that goal, I'll need to do some tricky steps I guess.. Which I don't like to take.
The plan is to downgrade from 5.0.1 GPE to 4.4.4 GPE. There's no image of 5.0.1 yet, so this is the only way of getting a clean install (I guess.... please correct me if I'm wrong). Now there is this problem of Motorola phones which don't allow you to downgrade your bootloader.
4.4.4 GPE image does contain an older bootloader...
Now I found this tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
It says: '"Downgrading:
The 1st command "mfastboot flash partition gpt.bin" will fail on 4.4.2 to 4.3 downgrade. Skip this command if you are downgrading and continue with the other commands, which should work."
I need to know if it's going to work for 5.0.1 to 4.4.4 downgrade.
After I have a clean install of GPE 5.0.1 I'll flash TWRP recovery and ultimately I'll flash the newest supersu.zip via TWRP recovery.
Can anyone tell me if the way I want to downgrade is safe? Or do you have other suggestions?
Please let me know.
Thanks in advance!
Best regards,
Daniel
I installed the Android Lollipop 5.0.1 GB OTA after flashing the Stock GB 4.4.4 firmware last night then flashed TWRP 2.8.3 and Aero Kernel. Now I'm thinking of selling my phone to upgrade to the second generation Moto G thus requiring me to reset the phone entirely, how would I go about this without bricking my phone? (Phone is XT1032)
I would flash back to stock 4.4.4 and OTA to 5.0 so the biyer doesn't have the ripple effect on the phone.
I had a phone with stock Telus 5.02 and I was able to downgrade to stock 4.4.4. Just don't try to flash motoboot.img.
Don't forget to flash a new logo too so the buyer doesn't see the unlocked bootloader warning.
So how would I go about doing that? Do you have a thread I could follow the steps of?
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.
Please anybody tried to downgrade from MM to LP & phone still works
as before my xt1032 bricked from long time cuz of downgrade fro LP to KK
Any help will be appreciated
I've switched to LP from MM and again LP, sometimes on KK no problem faced. if there any problem we should clean flash through p.c.
usually I used flashable zip (stock/custom) file, via TWRP.
I believe one line, someone says "no word like brick/dead on today's phone".
so, why fear?
you can downgrade the ROM but NOT the bootloader.
most bricking of devices is due to risky bootloader swaps. the particular scenario that you are referring to is a result of KK OTA update trying to upgrade the bootloader to LP bootloader and failing to do so (if you have been using stock LP ROM before, the bootloader most probably were upgraded then).