Im experiencing issues flashing my Honor 7S, the errors come in diff varieties. Ive unlocked USB Debugging and Bootloader but it doesnt seem to work, here are some errors ive gotten.
"Rebooting. . ." FAILED (error: Command not allowed)
"Erasing Recovery. . ." FAILED (error: phone not linked)
Could anyone help me out on this? Thanks a bunch
Related
Hi,
I have an AT&T Atrix 4G and I wanted to imstall CM7.2.
I had the latest Atrix Android version on it. Then I followed the instruction at the cyanogemod wiki for the atrix. So I flashed the sbf (cyanodenmod wiki -> Motorola_Atrix_4G:_Full_Update_Guide).
The rsd lite flashing didn't succeed because the atrix rebooted and the programm couldn't switch into BP passtrougth, or so.
At this point the device said something about 0x1000 no bootloader, but I could choose between rsd, fastboot and the other possibilities.
I booted into the fastboot mode and did an oem unlock. Now it says unlocked.
I booted again into the fastboot mode, and now it should be a simple
Code:
fastboot flash recovery recover.img
.
But:
Windows) it always says:
Code:
sending 'recovery' (4824 KB)... OKAY [ 0.453s]
writing 'recovery'... FAILED (status read failed (Too many links))
after that the device reboots and is in a boot loop
so i tried linux)
The first time i tried the command everythings worked fine, but after reboot i chose
Code:
android recovery mode
, but after a while (secs) the device rebooted.
so went to fastboot again, but now the device reboots after the sending command and then it says writing failed because of no device
Thats my story
I don't know what to do, because I am frightened to make something stupid; maybe I did it already.
I don't know if when I am using rsd lite to flash a complete image the phone reboots again and i have a hard brick.
It would be nice if someone has an idea to solve this problem.
BR,
rommon
You should post this in the Atrix forums.
Posted from my rooted Motorola Atrix.
sorry,
I reposted it in Atrix 4G Q&A.
so please close or delete this thread
Hello,
USB Debugging is on
Bootloader is unlocked
HiSuite is up to date
Correct ADB Drivers are installed
and my device is recognized in both "adb devices" and "fastboot devices"
The problem: I'm trying to flash a TWRP recovery, but I keep getting the error "Failed (remote: Command not allowed)".
I don't know what's wrong, and I don't see any other way how I'd be able to flash a custom recovery. I'm trying to get my phone rooted ASAP.
I also get the same error when I type "fastboot oem device-info" for example, it's so weird I get so frustrated by phones sometimes :silly:
Hope anyone can help me out
Oh and I own a Huawei Honor 7 (PLK-L01 aka plank)
*BUMP*
Anyone who can help me out, please?
Hi,
Long story short I was on Pie (30b) on a US988 (TWRP and Bootloader unlocked) device and it appeared that the MVNO I was on started doing stuff with HD Voice/Advanced calling aka making phone calls no longer worked. I followed the instructions to go back to Oreo 20h and was successfully able to do so (phone works fine, just no recovery/root). I am now trying to get TWRP/recovery back on my phone but failing to do so. My issues:
adb devices works fine
if I try any fastboot commands it always says waiting for device
If I put the phone into fastboot (volume down & usb) fastboot commands work.
in fastboot - fastboot devices list my device
if I run (in fastboot mode on my phone) - Fastboot flash recovery TWRP.img (for the renamed twrp.image file) I get:
Waiting for any device
Sending 'recovery' (33324 KB)
FAILED (Write to device failed (Invalid argument))
fastboot:error Command failed
my phone then says in very small letters at the top press any key to reboot
Sometimes when I try i just get a "FAILED (Write to device failed (Unknown error))
If i just put my phone back into fastboot mode it fails again, but this time with error "FAILED (Write to device failed in SendBuffer() (Too many links))
Any help would be greatly appreciated.
jjppott said:
I am now trying to get TWRP/recovery back on my phone but failing to do so. My issues:
adb devices works fine
if I try any fastboot commands it always says waiting for device
If I put the phone into fastboot (volume down & usb) fastboot commands work.
in fastboot - fastboot devices list my device
if I run (in fastboot mode on my phone) - Fastboot flash recovery TWRP.img (for the renamed twrp.image file) I get:
Waiting for any device
Sending 'recovery' (33324 KB)
FAILED (Write to device failed (Invalid argument))
fastboot:error Command failed
my phone then says in very small letters at the top press any key to reboot
Sometimes when I try i just get a "FAILED (Write to device failed (Unknown error))
If i just put my phone back into fastboot mode it fails again, but this time with error "FAILED (Write to device failed in SendBuffer() (Too many links))
Any help would be greatly appreciated.
Click to expand...
Click to collapse
See WTF Section 7 Troubleshooting Tips. Everything you are describing -- especially "too many links" is an ADB/fastboot communication issue. Don't care if ADB "sees" your device. It's still not talking to it.
There's a dozen Section 7 Troubleshooting Tips. Except for Tip #1, the remaining 11 are to solve this V3O ADB/fastboot communication issue. Go through them one by one.
ChazzMatt said:
See WTF Section 7 Troubleshooting Tips. Everything you are describing -- especially "too many links" is an ADB/fastboot communication issue. Don't care if ADB "sees" your device. It's still not talking to it.
There's a dozen Section 7 Troubleshooting Tips. Except for Tip #1, the remaining 11 are to solve this V3O ADB/fastboot communication issue. Go through them one by one.
Click to expand...
Click to collapse
Thanks Chazz. Ultimately it took trying it on another computer, but I was able to get it TWRP flashed.
jjppott said:
Thanks Chazz. Ultimately it took trying it on another computer, but I was able to get it TWRP flashed.
Click to expand...
Click to collapse
Glad you got it working. Yeah, different computer often does the trick.
After doing a flash for new pixel experience PixelExperience_Plus_beryllium-11.0-20210823-0645-OFFICIAL, phone restarted and then no other option for access. Boots into twrp logo and stuck.
adb devices in command prompt show device and recovery.
When I do bootloader into fast boot,
fastboot devices shows
??????? fast boot
then disconnects. (after this it doesnt progress any further and disconnects from pc).
cant fastboot any files as it has error, my boot loader is unlocked and was on pixel experience 10 prior.
what are my next steps?
the teamwin recovery is 3.2.3-0
kmkzboi said:
After doing a flash for new pixel experience PixelExperience_Plus_beryllium-11.0-20210823-0645-OFFICIAL, phone restarted and then no other option for access. Boots into twrp logo and stuck.
adb devices in command prompt show device and recovery.
When I do bootloader into fast boot,
fastboot devices shows
??????? fast boot
then disconnects. (after this it doesnt progress any further and disconnects from pc).
cant fastboot any files as it has error, my boot loader is unlocked and was on pixel experience 10 prior.
what are my next steps?
the teamwin recovery is 3.2.3-0
Click to expand...
Click to collapse
Use the latest Official TWRP since the one you have now is outdated and do clean install according the guide at POCO F1 Ultimate Collection & Guides. (You need to format data not just wipe) You can find everything you need there.
first time i turned on phone today, i was able to to do command fastboot devices and it actually showed the device id, then when i tried to flash it stopped and then everytime i connect it wont even show fastboot devices without showing ???????? and shutting down again.
ive tried installing uninstalling the drivers and boot loader drivers, i believe its something to do with that, otherwise it has unlock symbol when it gets stuck on twrp logo, then when i put into fastboot it doesnt have unlock symbol before fastboot splash, what could it be? (im unable to flash anything without getting
1. running fastboot flash/boot/ any command really
Sending 'recovery' (1551913 KB) FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
2. running command then connecting phone already in fastboot
< waiting for any device >
FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
kmkzboi said:
first time i turned on phone today, i was able to to do command fastboot devices and it actually showed the device id, then when i tried to flash it stopped and then everytime i connect it wont even show fastboot devices without showing ???????? and shutting down again.
ive tried installing uninstalling the drivers and boot loader drivers, i believe its something to do with that, otherwise it has unlock symbol when it gets stuck on twrp logo, then when i put into fastboot it doesnt have unlock symbol before fastboot splash, what could it be? (im unable to flash anything without getting
1. running fastboot flash/boot/ any command really
Sending 'recovery' (1551913 KB) FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
2. running command then connecting phone already in fastboot
< waiting for any device >
FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
Click to expand...
Click to collapse
Check AMD Ryzen Fastboot Fix at the thread I posted above. If you have Intel system just install the Fastboot Drivers which is there (at the thread) and check.
So I got a Lil c100 a couple days ago. It has a screen lock and the recovery mode don't work. Everyone says get it into fastbook amd use that to get to recovery. But the problem is after I get into fastboot the device isn't found. I've installed every USB driver known to man about fastboot or Nokia in general. And yet it still not popping up. Can sb help me?
swiftd3v said:
So I got a Lil c100 a couple days ago. It has a screen lock and the recovery mode don't work. Everyone says get it into fastbook amd use that to get to recovery. But the problem is after I get into fastboot the device isn't found. I've installed every USB driver known to man about fastboot or Nokia in general. And yet it still not popping up. Can sb help me?
Click to expand...
Click to collapse
anything yet?
swiftd3v said:
So I got a Lil c100 a couple days ago. It has a screen lock and the recovery mode don't work. Everyone says get it into fastbook amd use that to get to recovery. But the problem is after I get into fastboot the device isn't found. I've installed every USB driver known to man about fastboot or Nokia in general. And yet it still not popping up. Can sb help me?
Click to expand...
Click to collapse
What do you mean by "the device isn't found"?
wenyendev said:
What do you mean by "the device isn't found"?
Click to expand...
Click to collapse
The error I’m getting is “fastboot: usage: unknown device target recovery”
I am experiencing the EXACT same thing. No matter what box program Im using , nothing works! crazy. Please help. Id be happy with a factory reset. Atleast then I could get past the FRP.
Wow, I have not encountered that error yet.
I could only guess that it might be a problem of recovery.
How did you install your current recovery if not from fastboot?
diamant3 said:
The error I’m getting is “fastboot: usage: unknown device target recovery”
Click to expand...
Click to collapse
you're using fastboot reboot recovery?
Hey any update on this? I can say I've come across the same issue where their seems to either be no recovery or a corrupt one.
One thing I want to point out is (at least with the TracFone) that when I put the device in fastboot, and have wondershare tune go running, it displays the device as a Sony Xperia. The program still isn't able to connect to the device for me to attempt a reboot into recovery. It also reads the device as two other devices.
I'm hoping someone has encountered these findings and may also have a dump of the stock rom.if so I may be able to begin rooting for at least fix the recovery issue.
TaigaDaReck said:
Hey any update on this? I can say I've come across the same issue where their seems to either be no recovery or a corrupt one.
One thing I want to point out is (at least with the TracFone) that when I put the device in fastboot, and have wondershare tune go running, it displays the device as a Sony Xperia. The program still isn't able to connect to the device for me to attempt a reboot into recovery. It also reads the device as two other devices.
I'm hoping someone has encountered these findings and may also have a dump of the stock rom.if so I may be able to begin rooting for at least fix the recovery issue.
Click to expand...
Click to collapse
Also I'm going to use my Linux system to see if I get any results. Let me know if you've tried it as well.
fastboot oem unlock/fastboot flashing unlock has been blocked in the boot loader, only hope for root is another brom exploit like mtkclient or a temp root privilege escalation exploit
luridphantom said:
fastboot oem unlock/fastboot flashing unlock has been blocked in the boot loader, only hope for root is another brom exploit like mtkclient or a temp root privilege escalation exploit
Click to expand...
Click to collapse
Were you able to get fastboot to recognize the device?
Which OS are you testing on if you are?
TaigaDaReck said:
Were you able to get fastboot to recognize the device?
Which OS are you testing on if you are?
Click to expand...
Click to collapse
you need to use a special mtk boot mode script you can download here #101
Code:
computer:~ user$ python3 ~/Downloads/mtk-bootseq.py FASTBOOT /dev/tty.usbmodem14100
b'READYTOO'
Boot sequence sent
computer:~ user$ ~/Downloads/platform-tools/fastboot oem unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
computer:~ user$ ~/Downloads/platform-tools/fastboot flashing unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
computer:~ user$ ~/Downloads/platform-tools/fastboot oem unlock-go
FAILED (remote: 'unknown command')
fastboot: error: Command failed
testing on android 12, jan5 2022 update build 02US_1_030
luridphantom said:
you need to use a special mtk boot mode script you can download here #101
Code:
computer:~ user$ python3 ~/Downloads/mtk-bootseq.py FASTBOOT /dev/tty.usbmodem14100
b'READYTOO'
Boot sequence sent
computer:~ user$ ~/Downloads/platform-tools/fastboot oem unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
computer:~ user$ ~/Downloads/platform-tools/fastboot flashing unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
computer:~ user$ ~/Downloads/platform-tools/fastboot oem unlock-go
FAILED (remote: 'unknown command')
fastboot: error: Command failed
testing on android 12, jan5 2022 update build 02US_1_030
Click to expand...
Click to collapse
Hey thanks for the response.
So far I've been able to get the device to read in fastboot but I'm still unable to unlock the bootloader since as your saying it's definitely..."gimped" haha. I'll checkout the script and do some tests to see what I get.
TaigaDaReck said:
Hey thanks for the response.
So far I've been able to get the device to read in fastboot but I'm still unable to unlock the bootloader since as your saying it's definitely..."gimped" haha. I'll checkout the script and do some tests to see what I get.
Click to expand...
Click to collapse
if you're curious you can always reach out to this guy, he's able to get prototype boot loaders and stuff: https://twitter.com/Hikari_Calyx
might even know how to get test points to force it into brom for mtkclient