Challenge for experts! - P8lite General

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

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

XT1563 bricked?? Forgot to unlock OEM in dev options

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

P9 rescue - only fastboot (Help please)

Hi,
I have a P9 here I'm was asked to repair. I think it is kind of bricked and I hope some one can help me to unbrick it.
According to the auto dc-unlocker identification:
Found Phone : EVA-L09
Firmware : EVA-L09C432B386
FB LockState: LOCKED
USER LockState: LOCKED
So, bootloader locked and FRP locked. I don't know if the Firmware version above is right. All I know is that some Update.app files were flashed to the state of the phone now and before there where bootloops while the start animation and stuck boot with black screen.
At the moment I can do:
- turn on to see only the first huawei log with "powered by android", then nothing happens
- I can not enter eRecovery or update for Update.app
- I can only enter fastboot
I have the unlock code for the bootloader. I can not commit any fastboot commands (oem unlock, flash, etc) all is blocked with:
FAILED (remote: Command not allowed)
The locked FRP should be the reason for this.
I think OEM-unlock and usb debug from developer section was not enabled as the phone was usable. adb commands like "adb reboot bootloader" fail with
error: device '(null)' not found
fastboot devices shows the device
I have tried to uncharge the battery and then try to enter other modes than fastboot. No luck with that.
Do I have any chance to unbrick it without paying for the dc-unlocker/phoenix?
Can I do something with SRKTool?
If I have to use unlocker,
- do I have to unlock the bootloader?
- should I flash the same firmware that is now on the phone (B386) and where can I find it? (found only 1000 other versions until now)
Hope for answers
I've gone through that before, but ended up using DC-Phoenix to unbrick it when it's FRP and bootloader locked. Cost me about $15. There is a post on how to do this but I'll have to search for it again.
Here is the post I used:
https://forum.xda-developers.com/showpost.php?p=71767614&postcount=7
I guess you enter fastboot by Vol- and Power?
Not sure if the following method could help you with, but you can analyze before you go for dc-phoenix:
https://forum.xda-developers.com/showpost.php?p=74169408&postcount=7
scammander said:
Hi,
I have a P9 here I'm was asked to repair. I think it is kind of bricked and I hope some one can help me to unbrick it.
According to the auto dc-unlocker identification:
Found Phone : EVA-L09
Firmware : EVA-L09C432B386
FB LockState: LOCKED
USER LockState: LOCKED
So, bootloader locked and FRP locked. I don't know if the Firmware version above is right. All I know is that some Update.app files were flashed to the state of the phone now and before there where bootloops while the start animation and stuck boot with black screen.
At the moment I can do:
- turn on to see only the first huawei log with "powered by android", then nothing happens
- I can not enter eRecovery or update for Update.app
- I can only enter fastboot
I have the unlock code for the bootloader. I can not commit any fastboot commands (oem unlock, flash, etc) all is blocked with:
FAILED (remote: Command not allowed)
The locked FRP should be the reason for this.
I think OEM-unlock and usb debug from developer section was not enabled as the phone was usable. adb commands like "adb reboot bootloader" fail with
error: device '(null)' not found
fastboot devices shows the device
I have tried to uncharge the battery and then try to enter other modes than fastboot. No luck with that.
Do I have any chance to unbrick it without paying for the dc-unlocker/phoenix?
Can I do something with SRKTool?
If I have to use unlocker,
- do I have to unlock the bootloader?
- should I flash the same firmware that is now on the phone (B386) and where can I find it? (found only 1000 other versions until now)
Hope for answers
Click to expand...
Click to collapse
So you can not update via dload method? Did you try booting into recovery (not Recovery)? And you can't update with Update.app, you need to flash update.zip and full_update.zip via TWRP or Recovery. What wanted the owner of this phone to do, that he bricked it ?
Thank you all for your answers. Like I tried to describe: I was not able to access any other mode than fastboot.
"was able": I used DC-Phoenix now and it worked just fine.
Little confusing is that in all tutorials, even the on on the DC site, the UI of the tool is different.
But that's now Problem. The current Version is lot easier. Just "Standard Mode", select Update.app (full), Click Update.
The Phone gets flashed with fastboot, DC will restart it to update mode and will flash again. All automatic.
Really easy.
so you paid 15 USD ?
DallasCZ said:
so you paid 15 USD ?
Click to expand...
Click to collapse
Yes I did, and it worked.

Can't get TWRP on my phone

Guys i've tried everything but my MI8 doesn't want to have TWRP to run on it.
I've unlocked the bootloader just yesterday and tried to boot to TWRP via
fastboot boot twrp.img
or fastboot flash recovery twrp.img and fastboot reboot recovery.
But every boot or flash command give me different errors.
I've latest fastboot files and my drivers are ok since my phone appears as Android bootloader devices.
Any suggestions?
Some of the errors are:
- "write to device failed in sendbuffer() (unknown error)"
- "write to device failed (invalid argument)"
- even just stuck at "downloading twrp.img.."
and sometimes after some commands the phone just goes black with "press any key to shutdown" in the top left corner.
I've tried to change cable, usb port and pc, yet it didn't work.

Unbrick or something

Hello I have a VTR-L09 (Australian) with stock Pie on it. I unlocked the bootloader with the code from Huawei. Then I installed the openkirin AOSP 10 Preview 2 on it which led me to not being to connect to the internet and only occasionally being able to make calls, so that was junk...
Then I tried to install TWRP and FutureROM, but something must have gone wrong (pos user error) and now I can't even use the erecovery as it, after getting the last firmware, throws a "can't verify" error. I since tried to install TWRP via fastboot, but even though it reports success, when I try to boot into TWRP recovery all I get is a screen similar to the fastboot screen only with the below message
ERROR MODE
Attention!
Please update system again
Error!
Func NO: 11 (recovery image)
Error NO: 2 (load failed!)
When I try to boot iut just gets me to the FASTBOOT&RESCUE MODE screen
Is the phone bricked? Where to from here to get it back on stock ROM?
Thank you kindly!!!
Perhaps the device cannot verify the recovery image.
If bootloader is still unlocked, try to flash stock recovery and see what happens.

Categories

Resources