I'm a XT1032 user who updated to GPe 5.1 and I noticed it updated my bootloader to 41.19, given past experiences with the 41.18 bootloader it might no longer be safe to downgrade to KitKat 4.4.4 and OTA to 5.0.x as 5.0.x includes the the 41.18 bootloader.
We know from people who downgraded from official 5.0.x to 4.4.2 and OTA'd to 4.4.4 that the OTA procedure causes a hard brick due to flashing the old bootloader, therefore it might be wise to not downgrade to any KitKat version at all if you previously updated to GPe 5.1
yup going from 5.0.2 to KK (4.4.2 to 4.4.4) killed my moto g.
Flashed to 5.1 so if I need reflash I'd side flash to 5.1
Berties123 said:
yup going from 5.0.2 to KK (4.4.2 to 4.4.4) killed my moto g.
Flashed to 5.1 so if I need reflash I'd side flash to 5.1
Click to expand...
Click to collapse
I downgraded to 4.4.4 from GPE 5.1 without any problems, now updated to 5.0.2 from 4.4.4
AgentChaos said:
I downgraded to 4.4.4 from GPE 5.1 without any problems, now updated to 5.0.2 from 4.4.4
Click to expand...
Click to collapse
perhaps going to 4.4.2 then 4.4.4 did it? Wheras if you went straight to 4.4.4.
Either way won't risk going to KK
even i have downgraded to 4.4.4 from 5.1GPE and didnt face any problem.
It is 100% safe to downgrade ONLY if you do not flash the old bootloader. Kitkat, or lollipop 5.0.2 can run on 41.18 bootloader and even older bootloaders, just remember guys, if you try to flash the older bootloader it will hardbrick your phone. Avoid flashing anh bootloaders at all.
Just avoid flashing the bootloader, and you can go back and forth between Android versions. If you downgrade you'll have the flickering bug, but nothing more.
Flashing the 4.4.4 or 4.4.2 bootloader on a device with 41.18 or 41.19 will likely result in a hardbrick. AFAIK.
My point is that the OTA from stock/GPe KitKat to Lollipop 5.0.x includes the 41.18 bootloader, it will attempt to "upgrade" the 41.19 GPe 5.1 bootloader to 41.18 which might cause a brick the same way going from 4.4.2 with 41.18 to 4.4.4 with 41.13 by way of OTA was causing bricks
I made a mess of my attempt to upgrade to GPE 5.1 , so I downgraded to to 5.0.2 and it also downgraded the bootloader from 41.19 to 41.18. I wonder if that means that the 41.19 bootloader will allow us to downgrade further?
flyjazz said:
I made a mess of my attempt to upgrade to GPE 5.1 , so I downgraded to to 5.0.2 and it also downgraded the bootloader from 41.19 to 41.18. I wonder if that means that the 41.19 bootloader will allow us to downgrade further?
Click to expand...
Click to collapse
I'm not sure, I wouldn't try it unless you know you can get it repaired for free, IIRC the phone refuses to flash the bootloader if you downgrade it using mfastboot flash motoboot motoboot.img.
In any case, if you guys get sick of GPE 5.1, just flash the Brazilian 5.0.2 Firmware image without motoboot.img and gpt.bin... Then you will have back all Moto features (and will remain in 41.19 for now)... When the 5.1 moto firmware image comes available, just flash everything, including motoboot and gpt, to replace the ones from the GPE firmware...
Even if the 5.0.2 firmware image for your specific country comes available, you can flash it excluding bootloader and partition table safely... Then wou will be able to OTA to Moto 5.1 when it comes available, because you will already have the new bootloader, so there will be no problem.
Luckily, I flashed the GPE 5.1 flashable ZIP from lost101... :good:
4.4.2 WILL KILL YOUR PHONE
The death will happen after OTA from 4.4.2 to 4.4.4.
Speaking from experience :highfive:
So, I am kind of in a mess right now with my phone and I was wondering if it was because of the bootloader. Can anyone please tell me the bootloader versions for 4.4 kitkat, 5.0 lollipop and 5.1 lollipop?
hacorn96 said:
So, I am kind of in a mess right now with my phone and I was wondering if it was because of the bootloader. Can anyone please tell me the bootloader versions for 4.4 kitkat, 5.0 lollipop and 5.1 lollipop?
Click to expand...
Click to collapse
41.13, 41.18 and 41.19.
Hi,
I'm new to this rooting thing, but I'm trying to root so I can tether. How can I root a Moto X Pure already on stock 6.0 from OTA update without unlocking the bootloader. I'm trying to preserve my warranty. Thanks.
You won't lose your hardware warranty
Will the exploit "Working Root Method For 5.0 Lollipop Roms [OE1] [OG5] [OK3] [PB1] [3-3-16]" work on Marshmallow after getting the MM ota (flashed stock G900VBPB1 prior to downloading)
No. Attempting it will most likely softbrick your device, and possibly hardbrick.
diver47591 said:
Will the exploit "Working Root Method For 5.0 Lollipop Roms [OE1] [OG5] [OK3] [PB1] [3-3-16]" work on Marshmallow after getting the MM ota (flashed stock G900VBPB1 prior to downloading)
Click to expand...
Click to collapse
Nandr0idC0nsumer is correct, but you still can get root on MM even after having taken the OTA. However you will need to flash back to PB1, root PB1, then unlock the PB1 bootloader; after which you will need to do the MM bootloader Unlock and root method, http://forum.xda-developers.com/ver...t/rd-unlocking-galaxys-s5-bootloader-t3337909
Im currently on stock android marshmallow and I just got nougat update.Im currently rooted with bootloader and twrp installed.Do I have to relock the bootloader or just unroot?
Hey guys, I have a moto g4 (Xt 1622) 2 days ago I have reflashed a rom.... but When I do the update to Android 7.0.1 There were an hard brick...I followed this link : https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016 But i have relocked my bootloader....so I don't have OS and I didn't activate "oem unlock"
Sorry for my bad English thanks a lot
Just to clarify:
What stock ROM did you use to re-lock your bootloader? Normally, you can only re-lock your bootloader by flashing and locking with stock firmware as new or newer than your bootloader, so I'm not entirely clear how you managed to hard brick with a locked bootloader (locked bootloaders generally require your device to be on the same firmware patch level).
Have you tried the blankflash here: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 You may have to try flashing with the September 2017 stock firmware here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138