Database Info

Stuck at fastboot mode after trying downgrade xt1028

So i found some firmwares of my moto g xt1028 and tried to flash downgrade it to 4.4.2 but not successfully. After that, i tried to back to 4.4.4 and now stuck at this message:
- "failed to validate system image"
- Fastboot reason: "Fall-through from normal boot mode"
Any idea how to let me back as it is? :crying: Please help
P/s: I tried to flash 4.4.4 firmware again and many times, seem like all commands are proceeded properly but still cant boot , i wonder if 4.4.2 version do anything with it :crying:
Update1: Fixed! <-- I found there's 1 more file named "system.img_sparsechunk4" and decided to flash it ---> Fixed the device. Thanks god :highfive:

Downgrading via fastboot is very dangerous as you are also flashing the Bootloader. Is your Bootloader unlocked? I haven't followed if that's possible with XT1028.

lost101 said:
Downgrading via fastboot is very dangerous as you are also flashing the Bootloader. Is your Bootloader unlocked? I haven't followed if that's possible with XT1028.
Click to expand...
Click to collapse
As this moment, no. Still locked. Im glad that i fixed this problems after 4 hours finding and trying

[Completed] how ot unlock bootloader of yu5510a with lollipop

Hi people,
I have tried to unlock bootlaoder of yu5510a to install twrp and flash with cyanogen but unfortunately it's not happening. And i previously tried to do this with ygdp tool and resulted in softbrick of device later i got new replacement . And now i have used latest adb drivers, now fastboot is detecting my device but when i am using fastboot oem unlock command its throwing unknown command error. Kindly some one here try to give me a tutorial i have googled a lot from past 1mnth. Now i am fed up. My device came with stock lollipop now i hate this stupid OS.

bajjirulz said:
Hi people,
I have tried to unlock bootlaoder of yu5510a to install twrp and flash with cyanogen but unfortunately it's not happening. And i previously tried to do this with ygdp tool and resulted in softbrick of device later i got new replacement . And now i have used latest adb drivers, now fastboot is detecting my device but when i am using fastboot oem unlock command its throwing unknown command error. Kindly some one here try to give me a tutorial i have googled a lot from past 1mnth. Now i am fed up. My device came with stock lollipop now i hate this stupid OS.
Click to expand...
Click to collapse
Greetings and welcome to assist. If you ask your question here
http://forum.xda-developers.com/yureka/general
the experts there will be able to help you
Good Luck
Sawdoctor

Bricked device

Hi guys, my moto one hyper is bricked. Somehow trying to downgrade the phone I manage to brick it. It's not booting up, it keeps rebooting to fastboot. I can't flash stock ROM through commands. Every command I send fails because the bootloader is locked. I've tried this Motorola software rescue and smart assistant and it didn't find match to the phone. RSD Lite doesn't show the device. So I'm running out of solutions... Does anyone know another method? Something like EDL with QFIL IDK...(I've used that method with Lenovo phones)

Do you have locked the bootloader after upgrading and do you have upgraded to 11?
Do you have tried 'fastboot oem get_unlock_data' or 'fastboot oem unlock ...'?

How to relock bootloader?

I factory reset my phone through TWRP after unlocking bootloader, rooting and bricking trying to get read write access.
But my bootloader is still unlocked and now preventing me from updating OTA update to Android 11.

As long as you remain unlocked you will not get updates. Just download the 11 stock ROM and fastboot it. You will be updated.

boltjuice said:
I factory reset my phone through TWRP after unlocking bootloader, rooting and bricking trying to get read write access.
But my bootloader is still unlocked and now preventing me from updating OTA update to Android 11.
Click to expand...
Click to collapse
You can get the firmware with LSMA
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com

I just downloaded it and ran the rescue but it just flashed the rom and is still unlocked.
Is there an option to re-lock bootloader with that tool?

What is your carrier and where did you get your phone? Not every bootloader can be unlocked.

Carrier is metro PCS. Model # XT2113-2
I did a factory reset. But I still get the message bootloader is unlocked when it boots.
I just want to re-lock it and revert it back to stock.
ADB code: fastboot oem lock
didnt work. Just made my phone not boot with error "no valid operating system could be found."
ADB code: fastboot oem unlock
restored it to booting again with same bootloader is unlocked message.
Any way to re-lock this?

boltjuice said:
Carrier is metro PCS. Model # XT2113-2
I did a factory reset. But I still get the message bootloader is unlocked when it boots.
I just want to re-lock it and revert it back to stock.
ADB code: fastboot oem lock
didnt work. Just made my phone not boot with error "no valid operating system could be found."
ADB code: fastboot oem unlock
restored it to booting again with same bootloader is unlocked message.
Any way to re-lock this?
Click to expand...
Click to collapse
Re locking is not advisable, can be tricky with Moto devices

Re-Locking see Post #4

I'm a little unclear what state your device is in atm.
I just downloaded it and ran the rescue but it just flashed the rom
Click to expand...
Click to collapse
but then you write
I just want to re-lock it and revert it back to stock.
Click to expand...
Click to collapse
"it just flashed the rom" implies to me that the moto rescue software flashed a stock image so you now should be back to stock (I'm not sure what was downloaded tho). Regardless of how you flash (moto's rescue tool or by using fastboot with the device booted into the bootloader), I'd recomend using an image specific to MetroPCS (assuming the device was originally a metroPCS device and not something else like retus) and not one older than the last stock version flashed to your device.
It might help to boot your device into the bootloader, and then record the output of
Code:
fastboot getvar all
the lines with `ro.build.fingerprint` (perhaps also ro.carrier) in them will tell you what bootloader is currently running on your device and should help you figure out what the last stock version was flashed to your device.
HTH

notmyrealhandle said:
I'm a little unclear what state your device is in atm.
but then you write
"it just flashed the rom" implies to me that the moto rescue software flashed a stock image so you now should be back to stock (I'm not sure what was downloaded tho). Regardless of how you flash (moto's rescue tool or by using fastboot with the device booted into the bootloader), I'd recomend using an image specific to MetroPCS (assuming the device was originally a metroPCS device and not something else like retus) and not one older than the last stock version flashed to your device.
It might help to boot your device into the bootloader, and then record the output of
Code:
fastboot getvar all
the lines with `ro.build.fingerprint` (perhaps also ro.carrier) in them will tell you what bootloader is currently running on your device and should help you figure out what the last stock version was flashed to your device.
HTH
Click to expand...
Click to collapse
I factory reset the phone. Everything gets reset except for the unlocked bootloader does not re-lock... which prevents me from OTA update to Android 11.

Ok. If I understand correctly, your post with "it just flashed the rom" means a factory reset (and no flashing an image via moto's rescue tool or fastboot) - my misunderstanding.
As I mentioned to you in my reply to your PM, I don't use stock other than to initially get the bootloader unlocked, test a few things, and occasionally verify that my device still works on stock.
Others posting in this thread have offered helpful and safe suggestions - consider following these. I do a fair amount of "risky" tweaking with custom roms so please be cautious about the following suggestions/observations. (Apologies if my comments below seem basic - it looks like you've tried some fairly sophisticated tweaking of your own but it's hard to judge others skill level in a forum.)
Based on your comment:
made my phone not boot with error "no valid operating system could be found."
Click to expand...
Click to collapse
I suspect your phone wont boot after re-locking due to prior modifications to it's OS, the evidence of which can survive a factory reset. Re-locking enables android to verify that certain parts of the OS have not been modified and if it detects a difference, the device won't boot.
If you insist on re-locking your device now, I think the only way to accomplish that is to re-flash your device with the correct factory (aka stock) image some of which are available on lolinet. This is much more than a "factory reset." The instructions linked by sd_shawdow above should help with this:
Re-Locking see Post #4
Click to expand...
Click to collapse
Choosing the correct factory image is important. For example, I have a XT2113-2 RETUS. At one point early on when I was playing with this device, I tried flashing the TMO variant which is also a XT2113-2 model. My device did not boot until I re-flashed a RETUS variant. It's possible I just made a mistake while trying to flash the TMO variant I can't be certain at this point. If your phone was originaly (meaning new out of the box) a MetroPCS variant, make sure you flash a MetroPCS image.
Android also has roll back protection to prevent reverting to an older image that might have security flaws. The roll back "index" can be written to persistent storage on your phone that not only will survive factory resets but likely also survives flashing factory images. Motorola's implementation of roll back protection does not seem consistent with what I've read online from android/google. I'm pretty sure I had the most recent Android 10 RETUS bootloader on my device but I was able to flash an older factory image and then relock the device while on stock. (As I mentioned in my PM, I have not tried re-locking stock android 11). This observation may be the result of a motorola bug specific to RETUS so don't count on this working for you. Flash an image that is the same as or newer than the newest factory image you've ever had on the device.
Moto's rescue tool apparently can select and download an image for you making the process of image selection easier. I have not used this tool so I don't know how smart it is. Trust your knowledge about what you've done with the device since you owned it.
Lastly, it looks like the OEM unlocking toggle issue I and others have observed upon upgrading to Android 11 is resolved by connecting the device to your carrier and waiting several days. If you don't mind the wait, it's probably safe to flash android 11 (by using an image form lolinet and fastboot or by using the moto rescue tool - not via ota) while the device is unlocked and then re-locking the device.
Sorry about the long post.
HTH.
EDIT: I prefer not to be PM'd. Please just communicate (with me) in the open.

I was on Lineage 19.1 on my 5g ace. When I heard about the version 11 software for Retail US, I went to the lolinet mirrors to download the firmware for my phone.
Make sure oem unlocking in the developer options menu is off. If you can't turn it off you will need to root your phone.
Make sure USB debugging is on and you allow access for the pc your using.
Start adb and verify it sees your phone. If so, type...
reboot bootloader
Verify fastboot is authorized
Use Motoflash Pro to flash the version 11 firmware to my phone. Motoflash can be downloaded from the one 5g ace telegram channel. When it is done close Motoflash Pro and then from your pc use adb to run:
fastboot oem lock
Your phone will ask you if you want to relock bootloader. Choose Yes
Now reboot to the stock recovery and then use power + Volume up to access the recovery menu.
Navigate down to factory reset and select. It will warn you ... Blah blah blah. Now choose reboot system.
Moto boot logo should appear and then setup should begin.
Hopefully this helps someone.

Question Allow oem unlocking option missing in developer options

So, i recently flashed arrow os 12.1 on my poco x4 pro (veux) using twrp. Flashing the rom removed twrp and now i cant flash it back because fastboot says that my bootloader is locked...
Of course, it isn't and the problem is that allow oem unlocking isn't on... I really would appreciate some help because i've been stuck on this rom for a day.
Gonna wait for some answers, thank you.

In the first place, flashing the rom shouldn't relock your bootloader. Can you please reboot to fastboot mode and use mi unlock tool with the same account you used to unlock bootloader first time.

Soma Das said:
In the first place, flashing the rom shouldn't relock your bootloader. Can you please reboot to fastboot mode and use mi unlock tool with the same account you used to unlock bootloader first time.
Click to expand...
Click to collapse
Thank you for your response. Sadly i already tried that and the tool says that the phone is unlocked.
I'm trying to reflash stock rom via EDL mode, but i always get some error.
By the way, when using fastboot getvar command, it says that my bootloader is locked.
So, i recently bought a poco x4 pro (veux) and flashed a custom rom using twrp. Sadly, the rom's recovery managed to overwrite twrp and when i tried to flash twrp back, i could not flash it because fastboot said my bootloader wasn't unlocked. When i tried to unlock the phone again the xiaomi tool said that the bootloader was already unlocked. So, i used the getvar command which said that my bootloader was locked. So, i remembered that i didnt turn on allow oem unlocking in developer options. Sadly, when i looked for it the setting wasn't there. I tried using Edl mode to go back to stock but with no success. I always get some failed to read hello packet error. Can someone give me any help? Im kinda getting desperate...

WhyisAethertaken said:
So, i recently bought a poco x4 pro (veux) and flashed a custom rom using twrp. Sadly, the rom's recovery managed to overwrite twrp and when i tried to flash twrp back, i could not flash it because fastboot said my bootloader wasn't unlocked. When i tried to unlock the phone again the xiaomi tool said that the bootloader was already unlocked. So, i used the getvar command which said that my bootloader was locked. So, i remembered that i didnt turn on allow oem unlocking in developer options. Sadly, when i looked for it the setting wasn't there. I tried using Edl mode to go back to stock but with no success. I always get some failed to read hello packet error. Can someone give me any help? Im kinda getting desperate...
Click to expand...
Click to collapse
Go to service centre if it is critical. I have never seen such case so i couldn't help. I am afraid that you would have to pay the service centre people money for reflashing your device.
Also have you tried flashing fastboot ROM (MIUI) through fastboot? Also try to flash stock recovery rom via the recovery you have now currently.
Another thing you could try is using the Xiaomi official flashing utility (which is not unlock tool) to flash stock rom which does not require OEM unlock.

Soma Das said:
Go to service centre if it is critical. I have never seen such case so i couldn't help. I am afraid that you would have to pay the service centre people money for reflashing your device.
Also have you tried flashing fastboot ROM (MIUI) through fastboot? Also try to flash stock recovery rom via the recovery you have now currently.
Another thing you could try is using the Xiaomi official flashing utility (which is not unlock tool) to flash stock rom which does not require OEM unlock.
Click to expand...
Click to collapse
Thanks for the reply, i will try what you said.