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.
Related
a bit similer with this case
my friend bought it 20 days ago and he unlock it
but he cant flash twrp as like guides
he had no expirience before this
so i get tablet and tried to solve the problem but
fastboot doesnt work properly
fastboot devices/reboot/device-info works
but
fastboot flash recovery twrp.img/ flash boot boot.img(guide on carbon rom)/boot twrp.img/and etc that for flashing or change any system
does not work
massage like failed(long link/bigger than max allowed)
changing everytime i try
i though there might some issues when my friend unlock the bootloader
so i 'fastboot oem lock' and try to unlock again
but from then fastboot not work properly
can be boot or 'adb reboot fastboot' to fastboot
but it become unknown device on windows device manager
fastboot command not work
when mi flash try to detect device, fastboot mode end and 'press any key to power off' screen came out
some times it working for few seconds so i try unlock with official xiaomi tool but tool said 'already unlocked'
right after i locked bootloader i used 'fastboot oem device-info' and checked bootloader is locked
i can switch oem unlock on/off in developer option but it doesnt change anything
i searched as i can and edl mode looks last
but few things to consider
1. its official chinese rom and working now
2. i dont know broken fastboot can be restored with flashing rom with edl (i flash rom with update app in settings but not solved)
3. adb reboot edl doesnt work it just rebooted(should teardown it but i dont know what pin to short)
the reason why i trying to install custom rom(or eu rom) is my friend and i not live in native english country
hope i get some help
thx
Ryzen CPU?
thE_29 said:
Ryzen CPU?
Click to expand...
Click to collapse
ryzen 1, 2, intel sandy etc
tried all i got
Im almost sure flashing stock rom with MiFlashTool should solve this problem as it does flash partritions as recovery and fastboot too. Have you tried this one?
KrakmanCz said:
Im almost sure flashing stock rom with MiFlashTool should solve this problem as it does flash partritions as recovery and fastboot too. Have you tried this one?
Click to expand...
Click to collapse
nope
cant go into edl mode until i teardown it
miflash 2018 doesnt connect with pad on fastboot mode
miflash should connect to mi devices when in fastboot mode. I would consider checking drivers for the device, try to install MiSuite, it should install all drivers needed for those actions. Also, in the fastboot mode you are trying some commands, are you using Windows 10 Powershell or basic cmd?
chocodesk said:
ryzen 1, 2, intel sandy etc
tried all i got
Click to expand...
Click to collapse
Ok, when you also tried Intel.. But Ryzen CPUs have major problems with the flash tool and the tablet. Would not do anything on Ryzen PCs.
KrakmanCz said:
miflash should connect to mi devices when in fastboot mode. I would consider checking drivers for the device, try to install MiSuite, it should install all drivers needed for those actions. Also, in the fastboot mode you are trying some commands, are you using Windows 10 Powershell or basic cmd?
Click to expand...
Click to collapse
on basic
with was detected as fastboot before
but know its unknown on device manager
update driver doesnt work
Try using a usb 2.0 port? If you ever need to, hard reset is holding all buttons at once for 30 seconds.
Dannyboy3210 said:
Try using a usb 2.0 port? If you ever need to, hard reset is holding all buttons at once for 30 seconds.
Click to expand...
Click to collapse
i tried 2.0 and 3.0
not work
tablet owner decide to use it on stock chinese rom
not in my hand now
$ adb reboot bootloader
List devices on fastboot :
$ fastboot devices
XXXXXX fastboot
Check if bootloader is unlocked :
$ fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
OKAY [ 0.001s]
Finished. Total time: 0.003s
Flash TWRP recovery :
$ fastboot flash recovery recovery.img
Sending 'recovery' (54400 KB) OKAY [ 1.540s]
Writing 'recovery' OKAY [ 0.410s]
Finished. Total time: 1.952s
Reboot your device
$ fastboot reboot
Rebooting
Finished. Total time: 0.000s
I installed TWRP on MIUI 10 using this description. On the end , after TWRP installed - I rebooted again to TWRP and installed stock rom at once . I not tested , but theory says , MIUI will reflash recovery if it will be booted in this situation .
Sorry to piggy-back off this post, but I'm having a similar issue with my Mi Pad I just received:
I can boot it into Fastboot mode no problem, even see it listed when I use the "Fastboot devices" command. When I run the OEM info everything comes back true for unlocked.
However, when I try to flash anything I get the max size error or just a "FAILED" and it kicks the Mi Pad to a black screen with the white text "Press any key to shut down".
Any ideas?
*edit*
I've continued testing, and I'm really at a loss here. See the response I'm getting using fastboot:
\minimal_adb_fastboot_1.4.3_portable>fastboot flash boot kernel.img
target didn't report max-download-size
sending 'boot' (15060 KB)...
FAILED (command write failed (No error))
finished. total time: 0.003s
I can transfer files in windows no problem... I can use adb commands no problem... fastboot just doesnt seem to work.
I figured out my issue. You cannot use USB 3 ports to connect and run fastboot commands. I bought a cheap USB 2 hub, ran the cable from that and had no problems at all.
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.
Hi, just got a brand new Armour x5, bought unlocked. It has Android 10 on it. First, I would like to back up entire phone without installing any apps at all, adb or fastboot commands to do so would be appreciated.
I tapped developer options 7 times, enabled adb, and OEM unlocking. I then adb reboot fastboot after allowing pc to connect, and in fastboot I try:
fastboot oem unlock
and
fastboot flashing unlock
C:\adb>adb devices
List of devices attached
3082SH1001004262 device
C:\adb>adb reboot recovery
C:\adb>fastboot devices
3082SH1001004262 fastboot
C:\adb>fastboot oem unlock
...
FAILED (remote: Command not supported in default implementation)
finished. total time: 0.010s
C:\adb>fastboot flashing unlock
...
FAILED (remote: Unrecognized command flashing unlock)
finished. total time: 0.010s
to no avail, fastboot just looks blackscreen and the tiniest of fonts lol... yes drivers are installed.
So I reboot, and try the Armour 6 tut, but Magisk manager has no option to patch the boot.img I extracted from stock firmware, it also has a distinct lack of advanced settings, most likely due to my not yet having flashed a twrp or magisk-20.4 due to still unable to find out about dm-verity, (is dm-verity different between android 9 + 10?) meaning I wont flash anything that will brick the fone before i even put a sim into it.
Any help appreciated. Google sux.
Edit: Well after 12 or so hours I can honestly say that rooting is all gone downhill, does anyone actually know what they are doing nowadays?
I read all 5 copies of the rooting procedure for this phone, none of which is anywhere near complete, and so very wrong. What might have worked years ago does not work now.
In the Armour x5, when rebooting into fastboot using adb reboot fastboot, we are taken to a black screen with the smallest of txt saying fastboot. This fastboot does not ****in work ('scuse the swearing) so dont tell people to do this, it wont work. Nothing works in this fastboot mode. What you have to do is go into ANOTHER fastboot, by going into what we call recovery, by pressing power and volume up button, then choosing fastboot, ONLY then will fastboot commands kind of work. I say kind of, because most of the fastboot commands do nothing anyway, but at least show some output proving that booting into fastboot from adb is useless now.
For instance, in the pure black screen fastboot, nothing is found in adb or fastboot shell, no 'null' (needing activation), no waiting, just black nothingness. But in the recovery version of fastboot, we see fastbootd at the top of the screen, this is the fastboot that recognises at least partial commands. But none I have actually tried re finding bootloader lock status etc, nada.
I also noticed, I do have shell access when in adb, but not recovery, so if anyone knows how to flash a twrp for android 10 using shell with no root, I'll try it on my not so shiney brand spankin blank fastbootin fone
Hello I am trying to boot my phone to recovery mode to do a factory reset since it keeps restarting and it does not passes the Logo screen, it is stuck on a looping state. I tried to access the recovery mode usign the volume buttons but is not working, it keeps restarting. I did not enable debugging usb since I never knew I was going to need it. Any help will be greatly appreciated.
lol easy.
if your has problem, can you boot your phone into fastboot, don't request usb debbuging.
install this file and unzip it on your pc. https://dl.google.com/android/repository/platform-tools-latest-windows.zip
now open this folder and open cmd window inside it.
and run this command "fastboot continue" for continue normal booting.
if you need to reset your phone, can you use this command "fastboot -w"
Thanks,
I've tried that but is says command not allow.
C:\adb\platform-tools>fastboot continue
Resuming boot FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
Then I tried fastboot reboot to fastboot and it gave me this
C:\Users\Aiven>fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.001s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
it goes back to the looping stage again.
First time poster.... please go gentle on me. Not entirely new to custom roms and TWRP, but really stuck here. I am trying to install a CrDroid ROM. Phone is not networked locked and brand new. What I managed to do so far:
1. Reset the phone
2. reboot into Recovery (Mi Recovery)
3. Wipe data
4. Unlocked the phone (using offical Mi Unlock)
I then proceeded to boot into Fastboot and flashed the TWRP (twrp-3.7.0_12-0-onclite), renamed to recovery. But after flashing and rebooting I can only get into Fastboot, or boot it normally. Holding down the Volume+Up and Power button doesn't get me anywhere but Fastboot. (Same for Volume-Down and Power Up). I tried both un-pluggin the phone from the PC immediately after flashing is finished, and using Fastboot Reboot command, but all to no avail. Its Fastboot or normal boot only.
I also tried whats suggested here upto the vbmeta image, but didn't make a difference. When sending the 'fastboot boot recovery.img' command, I get the following error:
C:\adb>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.939s]
booting...
FAILED (remote: unknown reason)
finished. total time: 1.502s
Trying this guide for a 'custom' boot image from this page also didnt help
Really hoping there is a way to get this resolved. But totally stuck here. Have access to both Mac OS and Windows 10. If anyone can point me in the right direction it would be wonderful!
Ok, small update - in hope to help others...
I went ahead and used 'XiaoMiTool V2'to see if it might help to load a different ROM. When starting the app, I choose the 'Bricked' device option, even it wasnt bricked. I choose the Global ROM 12. (The phone showed up as unknown and I didnt sign in with the Mi Account).
After the new ROM was on it, phone started normally and went through the setup. Had to re-enable Developer Options, USB Debugging, but even so it still didnt work - installing the TWRP just kept bringing me back to Fastboot.
However, the TWRP from this page did work: https://twrp.me/xiaomi/xiaomi-mi439.html
I also took no chances and held the Volume up button pressed and with the Command window open and 'fastboot reboot'typed out, hit the Enter key at the same time as pressing the Power button on the phone.
Worked for me!
Try to install PitchBlack Recovery it's very compable PBRP-pine-3.1.0 _OFFICIAL
Timesnaps said:
First time poster.... please go gentle on me. Not entirely new to custom roms and TWRP, but really stuck here. I am trying to install a CrDroid ROM. Phone is not networked locked and brand new. What I managed to do so far:
1. Reset the phone
2. reboot into Recovery (Mi Recovery)
3. Wipe data
4. Unlocked the phone (using offical Mi Unlock)
I then proceeded to boot into Fastboot and flashed the TWRP (twrp-3.7.0_12-0-onclite), renamed to recovery. But after flashing and rebooting I can only get into Fastboot, or boot it normally. Holding down the Volume+Up and Power button doesn't get me anywhere but Fastboot. (Same for Volume-Down and Power Up). I tried both un-pluggin the phone from the PC immediately after flashing is finished, and using Fastboot Reboot command, but all to no avail. Its Fastboot or normal boot only.
I also tried whats suggested here upto the vbmeta image, but didn't make a difference. When sending the 'fastboot boot recovery.img' command, I get the following error:
C:\adb>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.939s]
booting...
FAILED (remote: unknown reason)
finished. total time: 1.502s
Trying this guide for a 'custom' boot image from this page also didnt help
Really hoping there is a way to get this resolved. But totally stuck here. Have access to both Mac OS and Windows 10. If anyone can point me in the right direction it would be wonderful!
Click to expand...
Click to collapse
You are trying to install onclite (Redmi 7) recovery on pine (Redmi 7A) ???
mi439 TWRP works for me as well & even successfully flash the rom/gapps. but when it comes to rooting with Magisk, i failed to flash nor install it properly. hope someone/somebody would make a tutorial for flashing/installing Magisk.