hi guys i'm brasilian and my english is pretty poor but lets try. i was flash 4.4.4 rom br retail. and i update via ota for lollipop.. and brick .. i search in forums here ... and i go it to put in boot loader without robot.. already try many ways to recovery my boot loader but always get error remote failure.. and already used 6.0.1 stock .. maybe i need to files atualy for this? i'm very sad my maxx is dead .. someone give me light .. help me fix this ... thank you guys
Is your bootloader locked or unlocked?
ChazzMatt said:
Is your bootloader locked or unlocked?
Click to expand...
Click to collapse
unlocked
kenedi jr said:
unlocked
Click to expand...
Click to collapse
Good.
What version Android was your phone on before the problem?
Were you on stock (factory) or on custom ROM?
Surely you weren't on Kitkat for almost 3 years?
ChazzMatt said:
Good.
What version Android was your phone on before the problem?
Were you on stock (factory) or on custom ROM?
Surely you weren't on Kitkat for almost 3 years?
Click to expand...
Click to collapse
I was in a custom rom and went to 4.4.4 and tried to upgrade via ota .. and brinck so I was able to make boot loader appear more without the robot
kenedi jr said:
I was in a custom rom and went to 4.4.4 and tried to upgrade via ota .. and brinck so I was able to make boot loader appear more without the robot
Click to expand...
Click to collapse
When you downgrade back to lower stock, you have to omit gpt.bin command. Because you have a newer bootloader.
This is also why you can't take OTA. Because it tries to install a different bootloader (which is probably still older than what you had with custom ROM). If you wanted stock 5.0.2 again, you have to flash full stock image and omit the gpt.bin command.
Are you able to use volume and power button to the bootloader screen?
ChazzMatt said:
When you downgrade back to lower stock, you have to omit gpt.bin command. Because you have a newer bootloader.
This is also why you can't take OTA. Because it tries to install a different bootloader (which is probably still older than what you had with custom ROM). If you wanted stock 5.0.2 again, you have to flash full stock image and omit the gpt.bin command.
Are you able to use volume and power button to the bootloader screen?
Click to expand...
Click to collapse
So I'm stuck on the bootloader. If I connect charger or pc it will already pro boot loader without the robot. I have already tried to pass stock 4.4.4 and 6.0 and more etc always from the failure remote failure in bootloader appears in the log something with gt bin downgrade
ChazzMatt said:
When you downgrade back to lower stock, you have to omit gpt.bin command. Because you have a newer bootloader.
This is also why you can't take OTA. Because it tries to install a different bootloader (which is probably still older than what you had with custom ROM). If you wanted stock 5.0.2 again, you have to flash full stock image and omit the gpt.bin command.
Are you able to use volume and power button to the bootloader screen?
Click to expand...
Click to collapse
My question is if I crashed from 4.4.4 trying to upgrade to 5.1 which version files do I need to adapt to my bootloader that seems to be corrupted?
kenedi jr said:
My question is if I crashed from 4.4.4 trying to upgrade to 5.1 which version files do I need to adapt to my bootloader that seems to be corrupted?
Click to expand...
Click to collapse
Before this trouble, were you ever on stock Marshmallow 6.0.1? If so, you can flash back to full firmware of that, but needs to be the very latest. I'll find a link for you.
Also, do you have TWRP installed and did you have a backup you can restore?
ChazzMatt said:
Before this trouble, were you ever on stock Marshmallow 6.0.1? If so, you can flash back to full firmware of that, but needs to be the very latest. I'll find a link for you.
Also, do you have TWRP installed and did you have a backup you can restore?
Click to expand...
Click to collapse
Yes before this problem I was in the latest 6.0.1 and the stock I have here when I installed had a security update
ChazzMatt said:
Before this trouble, were you ever on stock Marshmallow 6.0.1? If so, you can flash back to full firmware of that, but needs to be the very latest. I'll find a link for you.
Also, do you have TWRP installed and did you have a backup you can restore?
Click to expand...
Click to collapse
I do not have twrp backup and I can not even install the recovery stock
kenedi jr said:
Yes before this problem I was in the latest 6.0.1 and the stock I have here when I installed had a security update
Click to expand...
Click to collapse
OK, then that's the bootloader you were on and will always be on. You need to reflash that latest version (with the security update) to repair. Just reflash the entire full firmware.
There's a link to it here in this forum. I'll find it when I get home, if you don't have it.
Then in the future, if you try to downgrade, you always have to flash full stock version EXCEPT you omit the gpt.bin file. Whether 4.4.4 Kitkat or 5.0.2 Lollipop.
And you can never take OTA.
Because you really have 6.0.1 bootloader.
ChazzMatt said:
OK, then that's the bootloader you were on and will always be on. You need to reflash that version to repair. Just reflash the entire full firmware.
Click to expand...
Click to collapse
This is the most likely because all the methods say so old and not one was and when I try to pass any old stock also will not always get that error in the bootloader in the gptbin downgrade logs
ChazzMatt said:
OK, then that's the bootloader you were on and will always be on. You need to reflash that latest version (with the security update) to repair. Just reflash the entire full firmware.
There's a link to it here in this forum. I'll find it when I get home, if you don't have it.
Then in the future, if you try to downgrade, you always have to flash full stock version EXCEPT you omit the gpt.bin file. Whether 4.4.4 Kitkat or 5.0.2 Lollipop.
And you can never take OTA.
Because you really have 6.0.1 bootloader.
Click to expand...
Click to collapse
thanks bro you saved me
kenedi jr said:
This is the most likely because all the methods say so old and not one was and when I try to pass any old stock also will not always get that error in the bootloader in the gptbin downgrade logs
Click to expand...
Click to collapse
You can not flash any older gpt.bin files. You have to omit (leave out) that flash command.
Your gpt.bin file is 6.0.1, and you cannot downgrade. Even on 4.4.4, trying to accept the 5.0.2 OTA update is still older gpt.bin file in that OTA than your 6.0.1.
ChazzMatt said:
OK, then that's the bootloader you were on and will always be on. You need to reflash that latest version (with the security update) to repair. Just reflash the entire full firmware.
There's a link to it here in this forum. I'll find it when I get home, if you don't have it.
Then in the future, if you try to downgrade, you always have to flash full stock version EXCEPT you omit the gpt.bin file. Whether 4.4.4 Kitkat or 5.0.2 Lollipop.
And you can never take OTA.
Because you really have 6.0.1 bootloader.
Click to expand...
Click to collapse
i don't have link .. i will wanting you so
kenedi jr said:
i don't have link .. i will wanting you so
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?p=72846593
ChazzMatt said:
https://forum.xda-developers.com/showthread.php?p=72846593
Click to expand...
Click to collapse
I was a bit confused with this link which is the last one? I discovered because I am Brazilian and my English was developed only by playing
http://ftpeil.eil.com.br/vip/motoro...S24.107-70.2-7_cid12_subsidy-DEFAULT_CFC.xml/
ChazzMatt said:
http://ftpeil.eil.com.br/vip/motoro...S24.107-70.2-7_cid12_subsidy-DEFAULT_CFC.xml/
Click to expand...
Click to collapse
Face first you're a myth. I just passed gpt.bin and got the bootloader ... I'm very happy. Do I need to pass the entire rom ??
:good::laugh:
Related
Could someone help me restore 4.4.2 stock firmware?
MY BOOT LOADER IS LOCKED
When I turn on my phone I get this:
version downgraded for boot
failed to validate boot image
Fastboot reason: fall-through from normal boot mode
ImAustin366624 said:
Could someone help me restore 4.4.2 stock firmware?
When I turn on my phone I get this:
version downgraded for boot
failed to validate boot image
Fastboot reason: fall-through from normal boot mode
Click to expand...
Click to collapse
Flash the 4.4.4 image.
pfufle said:
Flash the 4.4.4 image.
Click to expand...
Click to collapse
My moto g never received the 4.4.4 update so do you think it will still work? Where could I find the 4.4.4 firmware?
It will work irrespective of whether you received the update or not.
Firmware image: http://forum.xda-developers.com/showthread.php?p=54872143#post54872143
Guide to Flash: http://forum.xda-developers.com/showthread.php?t=2542219
pfufle said:
It will work irrespective of whether you received the update or not.
Firmware image: http://forum.xda-developers.com/showthread.php?p=54872143#post54872143
Guide to Flash: http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
It's downloading now, will report back when i'm done Thanks for helping!
pfufle said:
It will work irrespective of whether you received the update or not.
Firmware image: http://forum.xda-developers.com/showthread.php?p=54872143#post54872143
Guide to Flash: http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
I will have to do this later in the day, my crappy satellite internet is acting up right now
I had this problem and sadly, after trying countless times with different firmwares the only solution I could find is to unlock the bootloader.
Then it stops giving you an error when you try to flash boot.img.
Your mileage may vary, but that is a potential fix, so keep that in mind.
ianxblog said:
I had this problem and sadly, after trying countless times with different firmwares the only solution I could find is to unlock the bootloader.
Then it stops giving you an error when you try to flash boot.img.
Your mileage may vary, but that is a potential fix, so keep that in mind.
Click to expand...
Click to collapse
The only way to unlock the bootloader with AIO moto g's is to use Jcases sunshine app and you have to be in the operating system for that
pfufle said:
It will work irrespective of whether you received the update or not.
Firmware image: http://forum.xda-developers.com/showthread.php?p=54872143#post54872143
Guide to Flash: http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
My parents use the same exact phone as me on the same carrier, could I dump the firmware from their phones and then flash it onto mine?
You can take a system image via a nandroid backup and the flash it on your device
Hi.. I hav a question... Can i flash 5.0.1 0n 4.4.4 with unlocked bootloader (even no root)
I tried this method but it said failed as bootloader was locked
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
I wanted to try this method (scenario 1) but it only tells about sideloading OTA zip.. I don't no for sure if i can use same method to flash the whole package..
http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
Help will be much appreciated
vikram66778 said:
Hi.. I hav a question... Can i flash 5.0.1 0n 4.4.4 with unlocked bootloader (even no root)
I tried this method but it said failed as bootloader was locked
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
I wanted to try this method (scenario 1) but it only tells about sideloading OTA zip.. I don't no for sure if i can use same method to flash the whole package..
http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
Help will be much appreciated
Click to expand...
Click to collapse
The bootloader needs to be unlocked when flashing images. In cmd type: fastboot oem unlock.
gee2012 said:
The bootloader needs to be unlocked when flashing images. In cmd type: fastboot oem unlock.
Click to expand...
Click to collapse
But y am i unable to get an OTA on my device. Am from India n some of others already got there update...
vikram66778 said:
But y am i unable to get an OTA on my device. Am from India n some of others already got there update...
Click to expand...
Click to collapse
OTA`s roll out in batches, it may take days or even weeks till everyone received the OTA. Just flash the 5.0.1 image in fastboot if you want it now .
gee2012 said:
OTA`s roll out in batches, it may take days or even weeks till everyone received the OTA. Just flash the 5.0.1 image in fastboot if you want it now .
Click to expand...
Click to collapse
:good::good:
Can i flash latest bootloader(hhz12d) & latest radio(m8974a-2.0.50.2.22) from 5.0.1 to 4.4.4....?
I am using rooted N5 running stock 4.4.4....
I am on stock lollipop 5.0 but flashed 4.4.2 radio on it using fastboot few weeks ago and locked the boot loader back.
I got 5.0.1 update and it downloads ,reboots and starts to install and hangs with a red icon halfway through the install.
Anybody know what I will need to do to update without losing any data or unlocking boot loader?
stivelio said:
I am on stock lollipop 5.0 but flashed 4.4.2 radio on it using fastboot few weeks ago and locked the boot loader back.
I got 5.0.1 update and it downloads ,reboots and starts to install and hangs with a red icon halfway through the install.
Anybody know what I will need to do to update without losing any data or unlocking boot loader?
Click to expand...
Click to collapse
You can`t do anything if you don`t unlock the bootloader and flash the 5.0 radio or flash the 5.0.1 factory image, you can backup your apps and data with Helium.
gee2012 said:
You can`t do anything if you don`t unlock the bootloader and flash the 5.0 radio or flash the 5.0.1 factory image, you can backup your apps and data with Helium.
Click to expand...
Click to collapse
That will be last resort but I was just trying to find out why the update doesn't work for me even though I'm on stock 5.0
stivelio said:
That will be last resort but I was just trying to find out why the update doesn't work for me even though I'm on stock 5.0
Click to expand...
Click to collapse
Your radio is not 5.0 compatible (stock), everythinhg has to be 100% stock and not rooted to be able to install the OTA
And if I unlock bootloader I will lose my data. Right?
stivelio said:
And if I unlock bootloader I will lose my data. Right?
Click to expand...
Click to collapse
Yup, there is no other way though. Backup everything you can before you unlock.
-Edit- You could try to root the device with CF Auto Root, install Bootunlocker from PLay and unlock the Bootloader without loosing data. Then unroot from the superSU app and flash the 5.0. radio, wipe caches in recovery or fastboot erase cache and see if the OTA can be installed
by sideloading it in stock recovery, link to the OTA http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
gee2012 said:
Yup, there is no other way though. Backup everything you can before you unlock.
Click to expand...
Click to collapse
Ah ok. I guess I will wait until 5.1 or something to do this when there are major updates
I was running cm12 on my nexus 5 and I had unlocked the boot loader and was asking xposed framework aplha version .
But then I decided to go back to stock android and I flashed the flashed the factory image of android 5.1 build number lmy47I . I wiped the data and even relocked the boot loader and now my phone is running smoothly and is on stock android.
But is there a way by which I can check if I flashed it correctly or not?
I mean nothing is broken but I heard android 5.1.1 update is around the corner so I was worried will I be able to apply the ota
Huh what? If it booted and is running smoothly its fine. If you didnt mod anything you'll get the ota
Sent from my Nexus 5 using Tapatalk
If you've flashed the factory image and everything is stock you should be fine for the OTA!
Thanks for the help
Lol....
You didn't need to relock the bootloader though. I tend to not ever want to relock it after unlocking it since that's about he only way you could potentially brick the device I think (Like if you relocked the bootloader and then for some reason the phone would not boot or something I am not sure how you'd unlock the bootloader again but whatever)
Evo_Shift said:
... I am not sure how you'd unlock the bootloader again but whatever)
Click to expand...
Click to collapse
Good to know. Btw, can you tell me, I'm on stock 5.1 unlocked bl, twrp, rooted. Will I be able to apply 5.1.1 over OTA when it comes out ?
jazzh said:
Good to know. Btw, can you tell me, I'm on stock 5.1 unlocked bl, twrp, rooted. Will I be able to apply 5.1.1 over OTA when it comes out ?
Click to expand...
Click to collapse
No, you're rooted.
Will I be able to flash the 5.1.1 image ?
jazzh said:
Will I be able to flash the 5.1.1 image ?
Click to expand...
Click to collapse
Yes
Someone will make a zip file of the update
SENT BY ENTANGLEMENT
Hello there,
About year ago I've done an update to 6.0 android. Battery was charged near full and everything seemed okey. But, after update I faced a bootloop. So I tried to flash stock firmware and... failed. Many times. I'm unable to boot into recovery mode. Factory mode also isnt working. So, I tried to unlock my bootloader and flash another image, but when I try to unlock, I get a: "Check allow oem unlock in developer options". Sadly, I cant boot to check this option Is there any way to unlock oem without running android? What can I do? :crying:
Jaszka said:
Hello there,
About year ago I've done an update to 6.0 android. Battery was charged near full and everything seemed okey. But, after update I faced a bootloop. So I tried to flash stock firmware and... failed. Many times. I'm unable to boot into recovery mode. Factory mode also isnt working. So, I tried to unlock my bootloader and flash another image, but when I try to unlock, I get a: "Check allow oem unlock in developer options". Sadly, I cant boot to check this option Is there any way to unlock oem without running android? What can I do? :crying:
Click to expand...
Click to collapse
You can flash the /persist partition from a device which has had OEM Unlock previously enabled in Developer Options.
MotoJunkie01 said:
You can flash the /persist partition from a device which has had OEM Unlock previously enabled in Developer Options.
Click to expand...
Click to collapse
How can you flash the /persist partition in a device with a locked bootloader? Doesn't this contain other information as well?
I think the real problem here is either the OP is not using the correct factory firmware image, or incorrect user procedure.
acejavelin said:
How can you flash the /persist partition in a device with a locked bootloader? Doesn't this contain other information as well?
I think the real problem here is either the OP is not using the correct factory firmware image, or incorrect user procedure.
Click to expand...
Click to collapse
You are probably correct. Even with a locked bootloader, certain partitions can be flashed as long as downgrading is not detected. Example, if I have an xt1548 Moto G3 running on stock 5.1.1 firmware, and I have a locked bootloader, I can flash either an updated 6.0.1 stock firmware package or I can reflash the 5.1.1 firmware with the same build as the one already installed. The bootloader will, however, prevent downgrading. In flashing the /persist partition, the .img being flashed would need to be from an equal or newer build as well.
But again, your statement regarding the correct firmware procedure and/or correct firmware package is likely correct.
MotoJunkie01 said:
You are probably correct. Even with a locked bootloader, certain partitions can be flashed as long as downgrading is not detected. Example, if I have an xt1548 Moto G3 running on stock 5.1.1 firmware, and I have a locked bootloader, I can flash either an updated 6.0.1 stock firmware package or I can reflash the 5.1.1 firmware with the same build as the one already installed. The bootloader will, however, prevent downgrading. In flashing the /persist partition, the .img being flashed would need to be from an equal or newer build as well.
But again, your statement regarding the correct firmware procedure and/or correct firmware package is likely correct.
Click to expand...
Click to collapse
You can't flash anything except a bootloader. I was in this situation as MotoJunkie knows and nothing works. I did have a full backup of every partition on the phone and none flashed. Today I bricked it so badly that it doesn't even turn on anymore. My tip is to not mess with the bootloader and stuff and just use the phone normally as many things are encrypted on this phone.
purplefruity said:
You can't flash anything except a bootloader. I was in this situation as MotoJunkie knows and nothing works. I did have a full backup of every partition on the phone and none flashed. Today I bricked it so badly that it doesn't even turn on anymore. My tip is to not mess with the bootloader and stuff and just use the phone normally as many things are encrypted on this phone.
Click to expand...
Click to collapse
Yes I recall your situation and your hard brick. I'm saying that under normal circumstances you can flash full firmware packages with a locked bootloader, as long as downgrading is not attempted.
MotoJunkie01 said:
Yes I recall your situation and your hard brick. I'm saying that under normal circumstances you can flash full firmware packages with a locked bootloader, as long as downgrading is not attempted.
Click to expand...
Click to collapse
You can't flash regular ones too. It has to be a newer firmware for the locked bootloader to let it pass
purplefruity said:
You can't flash regular ones too. It has to be a newer firmware for the locked bootloader to let it pass
Click to expand...
Click to collapse
That's what I was saying. An equal or newer one. Downgrading isn't permitted.
MotoJunkie01 said:
That's what I was saying. An equal or newer one. Downgrading isn't permitted.
Click to expand...
Click to collapse
Mine was on marshmallow and it wouldn't want to flash marshmallow stock so what I was saying is that you can't go anywhere unless stock nougat is released for this device.
purplefruity said:
Mine was on marshmallow and it wouldn't want to flash marshmallow stock so what I was saying is that you can't go anywhere unless stock nougat is released for this device.
Click to expand...
Click to collapse
You obviously developed corrupt partitions some way or another. I flash stock firmware packages with a locked bootloader on a regular basis. You should always be able to flash the same firmware build that is currently installed on your device.
MotoJunkie01 said:
You obviously developed corrupt partitions some way or another. I flash stock firmware packages with a locked bootloader on a regular basis. You should always be able to flash the same firmware build that is currently installed on your device.
Click to expand...
Click to collapse
O well I guess my device was different then. Won't turn on at all now . Gonna sell it for parts so at least I get some money back.