XT1563 bricked?? Forgot to unlock OEM in dev options - Moto X Q&A

long story short, my relative came to me for help after he decided to install a new ROM and made a simple error of forgetting about the OEM unlock option in the settings menu beforehand. an error occurred along the way and he tried to go back to stock. now when the phone boots it goes into the bootloader (which is locked) and gives a start up failed message saying to use Software Repair Assistant.
trying to go into recovery gives a
Code:
AP Fastboot Flash Mode [Secure]
Fastboot Reason: UTAG *bootmode* configured as fastboot
failed to validate system image
ERROR : Failed to pass validation. backup to fastboot
Boot up failed
i tried flashing TWRP but its giving errors too. are there any known workarounds to unlocking the bootloader or forcing a recovery/twrp to work?
thanks, all

Related

Got rooted then wanted back to stock - End up "failed to validate system image msg

Got rooted then wanted back to stock - End up "failed to validate system image msg
owner of a Motorola XT1072 UK model from Amazon
hi guys have made an absolute mess of this
heres what i did manged to install TWRP / Superu / unlock bootloader and root the phone with no issues
decided i wanted to go back to stock so via TWRP i flashed the stock image
that left me at stock - BUT bootloader still locked
so I went in and enabled USB debugging and FORGOT to tick the allow oem lock option
did an mfastboot oem lock - and it said success
then i did fastboot reboot - this where it failed
saying "boot up failed - failed to validate system image
but it was the corrrect image as of this thread
http://forum.xda-developers.com/mot...dows-tool-moto-g-2015-xt1072-restore-t3124915
Am stuck in that screen with options Normal Powerup/ REcovery / Factory / Barcodes / BP Tools
Currently it says "failed to validate system image"
and on next line
"Fastboot Reason: Fall-through from normal boot mode"
!00% my own fault for not being careful -
are there any utilities / batch files / tips or tricks
that can get me back on the road to stock firmware again ?
dmm1000 said:
owner of a Motorola XT1072 UK model from Amazon
hi guys have made an absolute mess of this
heres what i did manged to install TWRP / Superu / unlock bootloader and root the phone with no issues
decided i wanted to go back to stock so via TWRP i flashed the stock image
that left me at stock - BUT bootloader still locked
so I went in and enabled USB debugging and FORGOT to tick the allow oem lock option
did an mfastboot oem lock - and it said success
then i did fastboot reboot - this where it failed
saying "boot up failed - failed to validate system image
but it was the corrrect image as of this thread
http://forum.xda-developers.com/mot...dows-tool-moto-g-2015-xt1072-restore-t3124915
Am stuck in that screen with options Normal Powerup/ REcovery / Factory / Barcodes / BP Tools
Currently it says "failed to validate system image"
and on next line
"Fastboot Reason: Fall-through from normal boot mode"
!00% my own fault for not being careful -
are there any utilities / batch files / tips or tricks
that can get me back on the road to stock firmware again ?
Click to expand...
Click to collapse
Just unlock it... There's no point of locking it again.
LuK1337 said:
Just unlock it... There's no point of locking it again.
Click to expand...
Click to collapse
Hi Luk
the problem is that i DID NOT set the option for "Allow OEM UnLock"
and it will not unlock for me
its says (bootloader) - Check Allow OEM Unlock
it says FAILED (Remote failure)
Please help

XT1072 bootloop after replacing screen

Hi,
my friend has replaced the screen of his XT1072. Now the phone is stuck in a bootloop. He has never experimented with custom ROMs etc., so the developer options are disabled (no ADB, no unlock allowed). I can access the bootloader (locked, status 0) and connect via fastboot. Here is what I have tried so far:
select the "Recovery" option of the bootloader: immediately reboots into bootloop
fastboot oem unlock: not allowed (developer option not set)
flash CWM: Preflash validation failed
flash stock rom (as described here): Preflash validation failed
Are there typical hardware issues (forgotten connectors etc.) when replacing the screen of this phone? I don't know if it is a software problem, but what I find quite confusing is that the "Recovery" option of the bootloader does not do anything - not even before I tried the flashing stuff.
Any other ideas how I can get this thing running?
EDIT: I finally managed to flash the stock image. First I tried with fastboot on linux, then with mfastboot on windows. I also tried different images - probably the "Preflash validation failed" error was because of a wrong image. Still bootlooping and recovery option functionless.

[Help] message in fastboot "Boot up failed"

I try to put in on my Moto G 2014 recovery TWRP through an application called flashify, and agrochemical it no turn on nor load, have tried to make the rom procedure stock \ root \ hard reset (bootloader n no way do as n have access to the phone via USB, it n is found to provide the code where I would use it to make the bootloader)
None of the forward, from getting desperate to try to get my phone without spending a bundle
warnings in Fastboot:
hab check failed for boot
Failed to verify hab boot image
failed to validate boot image
Fastboot Reason: Fall-through from the normal boot mode
you mean the device only start on bootlader?

Xiaomi MI A2, is stuck in bootloop

Hi Guys,
My MI-A2 is stuck in bootloop ( When I turn on my phone it shows its Android One logo and then it shutdown itself ).
In my phone, I didn't turn on any USB Debugging or and OEM unlocking. and now it is possible as the phone is not starting.
I am able to access fastboot and recovery options
I tried to do factoryReset the device from the recovery option but it is just wiping the data.
here are the following things which I have tried with fastboot.
- I tried to unlock the fastboot with MiFlashUnlock but it stops at 99% and gives me the error of unable to verify the device,
- flashing the Stock ROM isn't working with MiFlashTool. giving random errors.
- tried changing the drive partition. it gives error to unlock the device first.
- tried tried to flash TWRP but it also gives me the error of unlocking the device first.
Almost every command of Fastboot is giving me some kind of error
But I am able to access the ADB Sideload from the recovery option.
- I tried to load the April OTA update from ADB Sidelode. The update is Successfully installed. But the device is still in bootloop.
Saving User data is not my priority. I just want the device to be working anyhow. As per my assumption, Fastboot is not an option for me unless it unlocked. I think something from the ADB sideload can be done.
Any help will be appreciated.
Is it a Guide?
Oh, now, its a Great News!
Please delete this post from this forum.
As I have already wrote to you, questions should go to "Questions and Answers" forum.
And as I have already wrote to you, Search works here, and if you've used it, you'd get answers (in mentioned above forum):
1. MiA2 having A/B slots architecture, - is supposed to recover to the other slot X when OTA corrupts ROM is slot Y, - after numerous boot attempts.
2. In case you have tampered phone with try-and-see operations without knowing what you were doing - the only way to recover phone is: TEST Point / EDL. Search these keywords in this forum for appropriate Guide.
try the "fastboot continue" command
dillu12 said:
Hi Guys,
My MI-A2 is stuck in bootloop ( When I turn on my phone it shows its Android One logo and then it shutdown itself ).
In my phone, I didn't turn on any USB Debugging or and OEM unlocking. and now it is possible as the phone is not starting.
I am able to access fastboot and recovery options
I tried to do factoryReset the device from the recovery option but it is just wiping the data.
here are the following things which I have tried with fastboot.
- I tried to unlock the fastboot with MiFlashUnlock but it stops at 99% and gives me the error of unable to verify the device,
- flashing the Stock ROM isn't working with MiFlashTool. giving random errors.
- tried changing the drive partition. it gives error to unlock the device first.
- tried tried to flash TWRP but it also gives me the error of unlocking the device first.
Almost every command of Fastboot is giving me some kind of error
But I am able to access the ADB Sideload from the recovery option.
- I tried to load the April OTA update from ADB Sidelode. The update is Successfully installed. But the device is still in bootloop.
Saving User data is not my priority. I just want the device to be working anyhow. As per my assumption, Fastboot is not an option for me unless it unlocked. I think something from the ADB sideload can be done.
Any help will be appreciated.
Click to expand...
Click to collapse
you need to flash the phone in edl mode
**just be careful there is a timeout ..when you put it into edl you need miflash and rom.loaded
*** download a stock fastboot stable pie for jasmine
**** unzip amd select revelant xml from within miflash
*****on phone manually boot to fastboot mode with buttons
****** run command "fastboot oem.edl"
*******device will boot to black screen ... immediately go to miflash and press the button to start flashing
___BE CAREFUL__ select clear all tick box at bottom of miflash screen
this should be enough to rescue your device regardless of what you've done or whether you unlocked bootloader or not

Challenge for experts!

OK so I have this PRA-LX1, long story short after a dload tonight to go back to stock ROM I ended up with softbricked phone, I can only enter Fastboot/Rescue mode.
Anything else ends up either in error 8 (ROM) or error 11 (Recovery) error.
- I have access to fastboot via adb/fastboot in a PC terminal
- I have FRP Lock, Phone Locked
- Nearly any fastboot command I send ends up in FAILED (remote: command not allowed!)
- I have my bootloader unlock code, but can't unlock because no botting ROM to check OEM unlock in developer options
- Can't flash any recovery (fastboot "not allowed" error)
- Can't seem to launch a new Dload with Vol+&Vol-&Power. Gives black screen "error mode: please update system again - Error Func NO 11 (recovery image)"
I'll try to let the blank screen drain the battery to get a new try to the Dload method... tomorrow

Categories

Resources