Hi guys,
I have this phone that stucks on bootloader mode.
I have tried to flash it with many firms and with lenovo assist.
Bootloader says:
Start up failed, your device didn't start successfully. Use the software repair assistant on computer to repair your device.
AP fastboot flash mode (secure)
Error: failed to pass validation, backup to fastboot
Fastboot reason: fall-through from normal boot mode
Every firm i tried to flash fail in system image sparsechuk 4...
Enviado desde mi SM-A505G mediante Tapatalk
Do you remember what your model number and software channel version was (for example xt1922-9 retus)
Related
I have my MI MIX 2 with official global V10.3.5.0.ODEMIXM. I upgraded to this version via regular OTA update about 2 weeks ago.
After factory recovery I did last day I stuck in restart loop with error.
I picked up language, region, and after that on Just a sec screen I have error Find Device closed unexpectedly and going to restart loop.
Via Mi suite 3 beta I am able to flash same firmware, but this is causing same error and loop. Older firmwares are not possible to flash because of error. (flashing firmware older the nactual firmware on phone)
Via fastboot I am not able to flash anything as phone has locked bootloader and is not assigned to my Mi account so unlock tool is not able to unlock it.
So.. what can I do to fix it ?
hi , if you have access to fastboot look if arb is on , download this => https://androidfilehost.com/?fid=24686681827312411 and copy/paste that => fastboot getvar anti ,, if you get 4, arb is on ..... if you have under , you can flash older firmware
So if you have 4 , search '' Anti-rollback Protection and Fastboot Unlocker '' to download antirbpass dummy.img
So
fastboot getvar anti
anti: 1
fastboot flash antirbpass dummy.img
target reported max download size of 536870912 bytes
sending 'antirbpass' (8 KB)...
OKAY [ 0.002s]
writing 'antirbpass'...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: 0.006s
Mi suite 3.0 still says:
Sorry, I can't support the rollback to a non-newer previous version.
Push Man Brush Pack Version: V10.3.5.0.ODEMIXM
hi you have anti 1 , you can flash older rom without brick , you have unlock bootloader
rom 10.2.2.0 =>http://bigota.d.miui.com/V10.2.2.0....XM_20190109.0000.00_8.0_global_ffb701bb41.tgz ,, you can flash ,, after that make upgrade firmware via update
ps: un flash.bat it will ask for 0 to flash ............. i did mistake ....... you can try flash beta rom , it's under pie , i flashed it to and it's stable
=> https://bigota.d.miui.com/9.5.30/ch...30_20190530.0000.00_9.0_global_6c535734e7.tgz
after flash search update normaly get 9.6.13
I really appreciate your help, but I was not succesfull.
Bootloader is locked and unlocking via MI Unlock is not succesfull because no Mi account is bound to the device.
Flashing via Mi Suite 3 always ends like this:
V9.5.8 (pie) -> Unable to flash between different android versions. Please flash ROM via Fastboot Flashing
V9.6.13 -> Unable to flash between different android versions. Please flash ROM via Fastboot Flashing
V10.2.2.0.ODEMIXM - > ROM Package verification failed Unknown Error[2013]
V10.3.1.0.ODEMIXM -> Sorry, I can't support the rollback to a non-newer previous version.
V10.3.5.0.ODEMIXM -> Succesfull, but always get boot loop with error FIND DEVICE CLOSED UNEXPECTEDLY
I also tried to reboot to EDL with help of this srticle: https://www.xiaomigeek.com/edl-mode-xiaomi.html second option - 2. How to Boot into EDL From Fastboot Mode.
But it always restarts and goes to boot loop.
So is last try open the phone and test point method? http://en.miui.com/thread-1351514-1-1.html
Hello guys:
One month ago i bought a Redmi note 8 pro, when it comes after a long time (almost 3 weeks) it comes with bootloader opened so i couldn use for example NFC pay. I looked for information to lock the bootloader i followed steps and bootloader was closed but phone was bricked too, so only can put smarthphone in fastboot or in recovery mode. I tried flash some roms by Fastboot using CMD in pc but appears this message
C:\adb>fastboot flash system system.img
target reported max download size of 134217728 bytes
erasing 'system'...
FAILED (remote: not allowed in locked state)
finished. total time: 0.004s
that was expected because bootloader is closed, but now i dont know if its posible to unlock bootloader and flash a new rom or beeing bootloader closed, flash a new rom for unbrick the phone.
To solve this problem I heard something abou autoriced xiaomi accounts and something about waiting seven days for unlock but i dont know nothing about it.
Thank you guys.
Have you tried the stock firmware and flash tool?
Sent from my SM-A705FN using Tapatalk
Sythel4 said:
Have you tried the stock firmware and flash tool?
Sent from my SM-A705FN using Tapatalk
Click to expand...
Click to collapse
I have tried to flash with fastboot and with miflash pro, and it always fails, I imagine that the flash tool will do the same as miflash pro and it will also fail, I will try anyway.
Thank you.
Try and give me a feedback
Sent from my SM-A705FN using Tapatalk
Sythel4 said:
Try and give me a feedback
Sent from my SM-A705FN using Tapatalk
Click to expand...
Click to collapse
I'm sorry for answering late, but I'm very busy with the current health situation.
What I have done is focus on unlocking the bootloader, and later will flash a new rom.
To unlock the device i have download "mi flash unlock tool"
Software recognice my phone
Click on "unlock">"unlock anyway">"unlock anyway"
Verifying device-ok
Unlocking-Fail
Couldn´t unlock
Please add your account in MIUI´s Settings > Developers option > Mi Unlock status
This way doesnt work.
I try by fastboot and cmd commands
Fastboot devices
Ok is connected and recognized
fastboot oem device-info
...
time 0.002s
Failed (remote: Unknown command)
fastboot oem unlock
...
time 18.455s
FAILED (Remote: GetVar Variable Not Found)
(Smartphone disconect and rebboy on recovery mode)
And well...I dont know what to do now.
It won't unlock because your device is already unlocked. You need to flash stock rom from custom recovery. Install custom recovery via adb. when you go back to stock rom device will be oem locked again. Also original account that was used to oem unlock device may be required that is why it might be failing.
https://forum.xda-developers.com/re...de-unlock-bootloader-flash-twrp-root-t3995919 (useful software here)
After flashing stock rom In fastboot try
Linux: adb fastboot-linux oem lock
OSX: adb fastboot-mac oem lock
Windows: adb fastboot-windows.exe oem lock
Hi,
I tried to flash european version of firmware to my LG G7+ by LGUP. It got stuck at 91%. After that i am not able to go in to download mode, becouse phone automaticly goes to fastboot mode.
I tried to flash laf.img extracted from firmware but fastboot is showing error:
Code:
C:\platform-tools>fastboot boot laf.img
Sending 'boot.img' (36736 KB) FAILED (Write to device failed (Too many links))
fastboot: error: Command failed
And then I can see that phone is unplugging from computer and fastboot cant see it. (fastboot menu on phone is vanishing in that moment too, there left only charging icon)
Any solutions? If you have any contact to someone who could help, please advice me.
pozdrowiony said:
Hi,
I tried to flash european version of firmware to my LG G7+ by LGUP. It got stuck at 91%. After that i am not able to go in to download mode, becouse phone automaticly goes to fastboot mode.
I tried to flash laf.img extracted from firmware but fastboot is showing error:
And then I can see that phone is unplugging from computer and fastboot cant see it. (fastboot menu on phone is vanishing in that moment too, there left only charging icon)
Any solutions? If you have any contact to someone who could help, please advice me.
Click to expand...
Click to collapse
Try using qfil to flash the required partitions.
I did a very stupid thing.
I locked bootloader with fastboot, with LineageOS installed. Device was not binded to xiaomi account.
Now when I reboot, it shows "System destroyed" message.
Same message, when trying to boot to recovery. (Because I had TWRP installed)
When I do fastboot oem unlock I got FAILED (remote: Token Verify Failed, Reboot the device)
When I use MI unlock tool with newly created MI account, it says
Code:
Please, add your account in MIUI's settings
.
When I downloaded stock fastboot firmware, and tried to ./flash_all.sh, or ./flash_all_lock.sh I got
product: sagit
erasing 'boot'...
FAILED (remote: Erase is not allowed in Lock State)
finished. total time: 0.000s
Erase boot error
How do I recover?
0sm1um said:
I did a very stupid thing.
I locked bootloader with fastboot, with LineageOS installed. Device was not binded to xiaomi account.
Now when I reboot, it shows "System destroyed" message.
Same message, when trying to boot to recovery. (Because I had TWRP installed)
When I do fastboot oem unlock I got FAILED (remote: Token Verify Failed, Reboot the device)
When I use MI unlock tool with newly created MI account, it says
Code:
Please, add your account in MIUI's settings
.
When I downloaded stock fastboot firmware, and tried to ./flash_all.sh, or ./flash_all_lock.sh I got
product: sagit
erasing 'boot'...
FAILED (remote: Erase is not allowed in Lock State)
finished. total time: 0.000s
Erase boot error
How do I recover?
Click to expand...
Click to collapse
i think you can research about Mi 6 EDL / Test point. by open the back and connect the test point, you can flash in lock state. i have not use it for a long time so this hint is all i can give.
demonntlxda said:
i think you can research about Mi 6 EDL / Test point. by open the back and connect the test point, you can flash in lock state. i have not use it for a long time so this hint is all i can give.
Click to expand...
Click to collapse
Well sadly Xiaomi locked down EDL mode and that needs people working for Xiaomi to fix it.
Sadly a service center will not fix it because they will convince you to dump your phone in a rubbish bin and buy a new mi 11 because Xiaomi could earn more.
So that is a bummer but your phone needs a new motherboard.
I'm stuck in unbootable mode, can you help me step by step? I ran the "partition" command and got the following results:
PartitionNumber DriveLetter Offset Size Type
1 1048576 260 MB System
2 273678336 16 MB Reserved
3 C 290455552 212.23 GB Basic
4 D 228168040448 25 GB Basic
5 255011586048 1000 MB Recovery
So, I think no memory is burnt. I've been trying for two days, but I don't understand what I'm doing wrong. I tried "flash_allAFT" but it gives me a failure. Can you tell me which code I can post? Thank you all.
"FAILED, fastboot.exe flash all WW_ZS660KL_17.0240.2103.75_M3.23.44.19-ASUS_1.1.229_Phone-user.raw failure, EXIT!"
anto-chipset said:
"FAILED, fastboot.exe flash all WW_ZS660KL_17.0240.2103.75_M3.23.44.19-ASUS_1.1.229_Phone-user.raw failure, EXIT!"
Click to expand...
Click to collapse
Flash in edl mode with edl Firmware
"I have an EU version, but I can only find WW or CN. Can you translate this into English?"
anto-chipset said:
"I have an EU version, but I can only find WW or CN. Can you translate this into English?"
Click to expand...
Click to collapse
Tutorial to flash your phone in edl mode.
If you can access fastboot mode then connect it to pc and open cmd and enter following command to enter in edl mode fastboot oem enter-dload
Make sure you have fastboot and qualcomm drivers installed and driver signature verification is disabled on your windows machine.
if no access to fastboot mode then please use the edl cable to boot in edl mode.
Repair your ROG2 phone with EDL mode，Official firmware！
Success is disgusted by some people, and will not share any files for free in the future.
forum.xda-developers.com
And here are the files required
Asus ROG 2 Firmware by VIKRANT.zip
drive.google.com
MI flash tool link to flash the firmware
MiFlash2018-5-28-0.zip
drive.google.com
fastboot devices
JAAZGV200231FRL fastboot
PS C:\Users\wras\Documents\rog> fastboot oem enter-dload
...
FAILED (remote: unknown command)
finished. total time: 0.000s
miflash : can not found file flash _all bat.
thanks for your patience if you can get me to fix this dead cellphone i will give you a fee