hi guys.. i am in android 9 PKQ1.190416.001.V10.3.16.0.PFQMIXM version.
i tried installing twrp as given in below link but it fails at step 7.. it cannot boot to recovery.
gizmochina.com/2020/01/27/install-twrp-on-xiaomi-mi-a3-root/
while running the fastboot boot twrp.img command, it gives following error and stops there only. what's wrong??
downloading 'boot.img'... OKAY [ 1.500s] booting... FAILED (remote: unknown command) finished. total time: 1.547s
You are using wrong guide.
Search XDA for the correct one, you might start reading here for example: https://forum.xda-developers.com/mi-a3/help/mi-a3-beginner-issues-twrp-t4076003
Related
Hi Everyone,
First I apologize if this isn't the right place to post this, please move it to the correct forum if it's not.
I have a Asus TF700 (running the latest Asus firmware) the, warranty just ran out so I figured it was time to unlock and play with some custom roms.
I got it unlocked using the Asus bootloader tool, I went to install CWM using fastboot and it seemed to go OK but then when I went to reboot the bootloader it failed giving me a write failure. Now when I try to boot up recovery it briefly shows the android guy in working mode then goes to the error with the android laying on his back.
Here is my commands with fastboot:
C:\adb>adb reboot bootloader
C:\adb>fastboot flash recovery recovery.img
sending 'recovery' (6688 KB)...
OKAY [ 2.483s]
writing 'recovery'...
OKAY [ 2.409s]
finished. total time: 4.893s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
C:\adb>adb reboot bootloader
error: device not found
And that's it, I'm a bit stumped not sure how to fix it so I can move onto installing the roms, any help would be greatly appreciated.
Anyone?
DId you install the Google USB driver?
If don't,please install the Android SDK and install all.
packyy said:
DId you install the Google USB driver?
If don't,please install the Android SDK and install all.
Click to expand...
Click to collapse
Yes, if I hadn't then I wouldnt have been able to use fastboot or install CWM.
No one? I thought this was the android super stars forum.
Can someone at lease suggest another forum with people willing to help?
Not a single person willing to help me out? Wow, thanks.
Long story short, I tried to flash new rom on my Mt2-L02 mate2 and failed and its bootlooping (at Huawei Ascend screen and keep rebooting) now. using the SDcard udload to load new rom don't work either. I cannot go into recovery, or boot into system.
My phone is bootloader unlocked, so I tried to flash (extract from a rom) boot.img, recovery.img and is ok but when flashing system.img, it stucked in writing 'system'... for long time.... so I tried fastboot erase system -w and get FAILED (remote: Command not allowed)... why is it so? my phone is already unlocked. I tried unlock again and flash the system.img, same problem.
So... I'm screwed?
You're not screwed. Impatient maybe. Try on a different computer if you have one. If not, update drivers and try a different port on the existing computer. Are you flashing an MT2-L02 ROM?
kimtyson said:
You're not screwed. Impatient maybe. Try on a different computer if you have one. If not, update drivers and try a different port on the existing computer. Are you flashing an MT2-L02 ROM?
Click to expand...
Click to collapse
Only have 1 pc, yes, I'm flashing MT2-L02 ROM, tried alot of version but discovered only these version rom (b408, b603, b606, b607) able to write the system.img, original out of box android version for my phone is 4.4.2. but still bootlooping after flashing boot.img, recovery.img and system.img. I think only custom recovery can save now, but there is none for this model... or maybe there is no hope for my phone? Maybe my phone got some system modified lock so that I'm not able to erase using flashboot?
C:\adb>fastboot erase cache
erasing 'cache'...
FAILED (remote: Command not allowed)
finished. total time: 0.001s
C:\adb>fastboot erase data
erasing 'data'...
FAILED (remote: Command not allowed)
finished. total time: 0.002s
C:\adb>fastboot erase system
erasing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 0.001s
If I'm able to erase those, I'm might solved the bootlooping problem..
Try using this thread as reference, http://forum.xda-developers.com/asc...to-fix-soft-bricked-phone-using-twrp-t2886630. It's for a different model so just use your stock ROM in place of the L03 ROM. I'm not sure how to help beyond that. There has to be a way to return to stock on the L02.
Maybe this message is late, pls try following
http://pan.baidu.com/s/1dDpc4eP
http://www.huaweirom.com/rom/mate2/2619.html
usb flash instructions:
http://www.huaweirom.com/guide/2621.html
You may need to use google translate since all the info is in Chinese
Basically they are saying you should use B117 if B4xx not working.
Hello. Today i tried to flash the phone to the stock ROM twice but it didnt work probably cause unlocked bootloader and custom recovery (TWRP).
So i brick the phone and now i cant access the rom or the recovery. All i can do is access the fastboot mode. I tried to install the new recovery through fastboot but it doesnt work.
I tried the twrp 3.0.2.0 and 3.0.1.0 for yuga.
Code:
C:\Users\Kubo\Downloads\platform-tools>fastboot flash recovery recovery.img
target didn't report max-download-size
sending 'recovery' (10704 KB)...
OKAY [ 0.342s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.347s
Tried various of commands that i found on google and this forum but nothing worked. I unlocked the bootloader before when i was installing various of custom roms. Could somehow stock rom affect the bootloader when i was flashing through flashtool ? I tried to only boot the recovery from the img, the command worked but the recovery did not boot.
Code:
C:\Users\Kubo\Downloads\platform-tools>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.341s]
booting...
OKAY [ 0.033s]
finished. total time: 0.378s
Tried to check the status of bootloader but the command is just showing ... and nothing happend. Tried to get the IMEI through fastboot getvar command but no output is given. Im desperate. Sorry for english not my native language. I'll appreciate all the help.
Hi all,
I have an LG G5 H850. I'm trying to install TWRP using ADB. I've had it previously and it worked fine. I'm pretty sure the bootloader is unlocked. Anyway, when I do "fastboot flash recovery twrp-3.1.1.1-0-h850.img" I get the following output:
target reported max download size of 536870912 bytes
sending 'recovery' (19076 KB)...
OKAY [ 0.431s]
writing 'recovery'...
OKAY [ 0.345s]
finished. total time: 0.781s
To me, that looks as though thats worked fine. Now when I try fastboot boot twrp-3.1.1.1-0-h850.img I get the following:
downloading 'boot.img'...
OKAY [ 0.432s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.456s
Has anyone got any ideas on this?
Same here
I am having the same problem, please help
Had this issue a while back. I resorted to doing complete flash with LGUP to the latest version and then it worked. I had been messing around with various ROMS on different android versions.
lywyn said:
Had this issue a while back. I resorted to doing complete flash with LGUP to the latest version and then it worked. I had been messing around with various ROMS on different android versions.
Click to expand...
Click to collapse
Don't happen to know where I could get a rom that it would work with do you?
Managed to solve this. Flashed the TWRP image using fastboot flash recovery <img> via adb. Then I unplugged from USB, and got into recovery mode by doing power + volume down buttons and quickly release and repress ont he LG logo. Answered yes to both questions and got into TWRP.
Barsbeh said:
Managed to solve this. Flashed the TWRP image using fastboot flash recovery <img> via adb. Then I unplugged from USB, and got into recovery mode by doing power + volume down buttons and quickly release and repress ont he LG logo. Answered yes to both questions and got into TWRP.
Click to expand...
Click to collapse
That is the required way of doing it. You have to boot into recovery after flashing the recovery or it gets reset.
Hi,
Having a similar problem since trying to update my ROM ... and the Magisk install failed. Now I can only get to fastboot, can't get to recovery. And, tried this,
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.1.1-0-h830.img
target reported max download size of 536870912 bytes
sending 'recovery' (18644 KB)...
OKAY [ 0.439s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.461s
Help!?! ... and thanks!
I've bean trying to go to twrp and every time it only says
downloading 'boot.img'...
OKAY [ 1.523s]
booting...
FAILED (remote: Error verifying the received boot.img: Invalid Parameter)
finished. total time: 3.874s
can anyone help and yes i did unlock the bootloader
Did you try
Bash:
fastboot boot twrp.img
i did
dizziboi said:
I've bean trying to go to twrp and every time it only says
downloading 'boot.img'...
OKAY [ 1.523s]
booting...
FAILED (remote: Error verifying the received boot.img: Invalid Parameter)
finished. total time: 3.874s
can anyone help and yes i did unlock the bootloader
Click to expand...
Click to collapse
TWRP recovery is not boot.img, but is recovery.img
i fixed it
dizziboi said:
i fixed it
Click to expand...
Click to collapse
So how did you go about fixing it? Thanks for sharing your method!
i found a way to get back into recovery mode then i sideloaded the android 12 dev preview