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.
Related
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
Guys, here's the problem:
I've clicked reboot to recovery in power menu in Pure Nexus ROM and now I'm stuck in recovery bootloop.
The phone tries to boot into recovery, shows the leeco recovery message and then flashes red triangle android robot and just shows black screen. If I connect to PC at that point, adb recognises a device in recovery mode. But I can't flash anything.
If I try long enough I can boot into fastboot, but then I get the "Android Bootloader Interface" in the device manager - but adb doesn't see the device.
Any suggestions? Can i somehow make ADB see the device so I can reflash TWRP?
ziembus said:
Guys, here's the problem:
I've clicked reboot to recovery in power menu in Pure Nexus ROM and now I'm stuck in recovery bootloop.
The phone tries to boot into recovery, shows the leeco recovery message and then flashes red triangle android robot and just shows black screen. If I connect to PC at that point, adb recognises a device in recovery mode. But I can't flash anything.
If I try long enough I can boot into fastboot, but then I get the "Android Bootloader Interface" in the device manager - but adb doesn't see the device.
Any suggestions? Can i somehow make ADB see the device so I can reflash TWRP?
Click to expand...
Click to collapse
Dear
Press and hold vol - and power button together, then your phone will boot into fastboot mode.
then simply you can use fastboot commond below to flash recovery.
fastboot flash recovery recovery.img
OK I've managed to get my PC to recognize the device. Now fastboot sees the phone.
The thing is that I can't flash anything. I had probably disabled "Allow Oem Unlock" in Developer options.
So I have fastboot but can't flash anything there. Any suggestions? If I reboot without holding Vol- the phone tries to boot into recovery and fails.
EDIT: At this point I can either boot into fastboot, where I can't do: "fastboot oem unlock-go"
Or boot into recovery, which doesn't load properly, all that's left is a blank screen - but ADB sees a device in recovery mode"
Is there anything I can do to get out of those two options?
ziembus said:
OK I've managed to get my PC to recognize the device. Now fastboot sees the phone.
The thing is that I can't flash anything. I had probably disabled "Allow Oem Unlock" in Developer options.
So I have fastboot but can't flash anything there. Any suggestions? If I reboot without holding Vol- the phone tries to boot into recovery and fails.
EDIT: At this point I can either boot into fastboot, where I can't do: "fastboot oem unlock-go"
Or boot into recovery, which doesn't load properly, all that's left is a blank screen - but ADB sees a device in recovery mode"
Is there anything I can do to get out of those two options?
Click to expand...
Click to collapse
I want to know which recovery you tried to flash through fastboot. It may not allow you flashing twrp ultill oem is locked. You can try flashing stocking recovery.
ziembus said:
OK I've managed to get my PC to recognize the device. Now fastboot sees the phone.
The thing is that I can't flash anything. I had probably disabled "Allow Oem Unlock" in Developer options.
So I have fastboot but can't flash anything there. Any suggestions? If I reboot without holding Vol- the phone tries to boot into recovery and fails.
EDIT: At this point I can either boot into fastboot, where I can't do: "fastboot oem unlock-go"
Or boot into recovery, which doesn't load properly, all that's left is a blank screen - but ADB sees a device in recovery mode"
Is there anything I can do to get out of those two options?
Click to expand...
Click to collapse
When in fastboot mode, you can try to boot twrp from the pc with
Code:
fastboot boot nameoftwrp.img
JamBax said:
When in fastboot mode, you can try to boot twrp from the pc with
Click to expand...
Click to collapse
Tried that, it tells me that I can't do this because the phone os locked. Now I'm looking for Stock recovery IMG for x522
EDIT: Trying to flash stock recovery gets me this message:
target reported max download size of 536870912 bytes
sending 'recovery' (13904 KB)...
OKAY [ 0.435s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.451s
Its the same whether its TWRP image or stock recovery image.
I was thinking of using this:
https://forum.xda-developers.com/le-2/development/tools-unbrick-thread-leeco-le-2-x52x-t3634609
But, unfortunately, there is no file for American x522.
It sucks to be able to get into fastboot and not be able to do anything.
Thanks for the suggestions so far
ziembus said:
Tried that, it tells me that I can't do this because the phone os locked. Now I'm looking for Stock recovery IMG for x522
EDIT: Trying to flash stock recovery gets me this message:
target reported max download size of 536870912 bytes
sending 'recovery' (13904 KB)...
OKAY [ 0.435s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.451s
Its the same whether its TWRP image or stock recovery image.
I was thinking of using this:
https://forum.xda-developers.com/le-2/development/tools-unbrick-thread-leeco-le-2-x52x-t3634609
But, unfortunately, there is no file for American x522.
It sucks to be able to get into fastboot and not be able to do anything.
Thanks for the suggestions so far
Click to expand...
Click to collapse
Try Leeco AIO tool kit to reboot your device into recovery . It's working for me
leco le 2 x520 recovery problem
I have a problem with recovery in le 2 x520. It installs via fastboot by unlocking the bootloader but stops at the Le recovery logo and nothing else happens. I installed from version 3.0.2.0 to 3.1.1.1 and nothing happens, I do not have recovery and writes everything okey went. what is going on ??
I have same problem. how to fix
I have a new one (acutally two, got them for U$D 108.99 each one)
Using ADB devices it recognize the UID like 0123456789ABCDEF, so I think the recovery is corrupted, intentional or not, it is blocking fastboot and recovery to load normally.
At this point I can't do anything.... any suggestions?
You solved it ?
I having the same issue maybe the issue is with stock rom since i flashed in normal twrp,chinese twrp and also that stock recovery.
****!
When I was trying to root my P10 I was trying to install SuperSU via TWRP but my file names were crypted, and I couldn't find the .zip file.
After some research I found out that it's a common problem, and can be solved by flashing a custom rom (no-verity-opt-encrypt.xxx.zip)... And that is supposed to decrypt the filenames.
After sideloading that file, I can't boot my phone as I get stuck on a screen saying: "your device is booting now..."
I can get to huawei eRecovery by pressing the volume up - I can't do a factory reset, it just says your device is not supported.
I can also get to fastboot & recovery mode screen, and by typing "fastboot devices" in console I can see my device's number so I can acces it.
If I type fastboot flash recovery twrp-3.1.0-0-P10.img it would successfully fiinish but it wont do anything.
Can I somehow fix this?
EDIT: saved the phone with
https://forum.xda-developers.com/p10/help/model-t3713886/post74719465#post74719465
Hello everyone, so recently i decided to update my mi a2 to android Q, since my OTA updates werent updating (i had root with magisk, and no twrp), so i decided to erase all my data, and i tried from 0, instaling twrp first so i can switch from custom roms and whatnot. when i tried to install twrp it started to give me some errors on my device when i typed commands on my computer, saying "press any key to shutdown", basically i think i bricked my phone, i cannot use a single fastboot command, im getting desperate, i can provide more information as we go on...
[EDIT] when i try a command, for example: "fastboot flashing unlock_critical" it gave me an error like "FAILED (command write failed (no such file or directory))" or "fastboot erase ddr
erasing 'ddr'... FAILED (remote: unknown command)" these were the last commands i had here
[EDIT 2] when i try to use MiFlash and flash the original rom, it still gives me the same error on my device like (press any key to shutdown), it goes all black with this small message....
I'm having the same problem.
basically when i am on slot b, I can't use any fastboot commands and ive also not installed twrp.
those same commands worked when i was on slot a.
now i am stuck in slot b. don't know any fix.
ZuNNN said:
Hello everyone, so recently i decided to update my mi a2 to android Q, since my OTA updates werent updating (i had root with magisk, and no twrp), so i decided to erase all my data, and i tried from 0, instaling twrp first so i can switch from custom roms and whatnot. when i tried to install twrp it started to give me some errors on my device when i typed commands on my computer, saying "press any key to shutdown", basically i think i bricked my phone, i cannot use a single fastboot command, im getting desperate, i can provide more information as we go on...
[EDIT] when i try a command, for example: "fastboot flashing unlock_critical" it gave me an error like "FAILED (command write failed (no such file or directory))" or "fastboot erase ddr
erasing 'ddr'... FAILED (remote: unknown command)" these were the last commands i had here
[EDIT 2] when i try to use MiFlash and flash the original rom, it still gives me the same error on my device like (press any key to shutdown), it goes all black with this small message....
Click to expand...
Click to collapse
Use Windows PC (preferably 7 with Intel and USB 2.0), latest platform tools and try again. I generally do not install TWRP, rather boot it (use the latest one) and carry out the tasks since I use Stock ROM.
I had that problem before.
Things that solved:
Use another usb-c cable
Run fastboot on linux
Use an usb 2.0 HUB (the ones that have 3 or 4 ports)
did u check usb debug box,and OEM as well?
and if you did all of that , did unlock bootloader?
hi guys, after the really buggy android 10 update from xiaomi i decided to install a custom rom on my device, i hadn't installed a custom rom in ages and never on an a/b device so it was new to me, i was kinda stumbling but managed to install twrp, install pixel experience rom and then switched to slot a and it booted
but now my device does not accept most fastboot commands! fastboot getvar all only works 1/3 of the time, most of the time it either fails with FAILED (remote: 'unknown command')) or FAILED (Write to device failed (Unknown error)) which boots me to the same black screen as OP. fastboot boot twrp.img always fails. the phone boots successfully but im unable to switch slots or boot to recovery when everything was working perfectly before switching slots. ive tried 2 cables with 3 usb ports on my laptop.
Hi,
today I tried to flash TWRP on my XZ1 Compact to later install LineageOS on it, as the provider-supplied Android version is stuck at version 9.
I managed to unlock the bootloader and I followed this guide on TWRP.me to install TWRP.
All steps were successful, except the actual flashing of the recovery.
Meaning, that I could successfully list my device with `adb devices`, successfully boot into the bootloader with `adb reboot bootloader` (blue LED indicator, black screen), as well as successfully list the device with `fastboot devices` afterwards.
The final step though fails as follows:
Code:
sudo ./fastboot flash recovery twrp-3.6.1_9-0-lilac.img
Sending 'recovery' (33816 KB) FAILED (Status read failed (No such device))
fastboot: error: Command failed
After the above command failed, the phone seems to end the bootloader mode and returns to just charging via USB.
I tried this several times, but nothing changed.
I'd appreciate any help to get TWRP installed to be hopefully able to install LineageOS.
If there's any further information/details missing, please let me know.
EDIT:
I tried the above steps with ADB/Fastboot versions 33.0.1-8253317 and 33.0.2-855794 on a Linux machine with the same outcome.
Thanks a lot in advance!
SOLVED: For some reason switching to another laptop (with the exact same adb/fastboot files and TWRP) solved the problem.
Had the same f--ing thing. Google brought me to this post where a user solved it by trying out different laptops and USB ports. Thought it was nonsense, but tried it out on another laptop and it worked. BTW, adb's fastboot never worked on Windows for me due to some driver issue which apparently only concerns Xperias and I tried two different Linux distros before finally having success booting up EndeavourOS from a USB.
I have a Redmi 7 and for some reason this is the top result for my search of this exact problem for the redmi, so I'm going to post this here in hops it can help keep someone from banging their head against the wall like I have. And hopefully this method helps us out with Sony as well.
I tried 4 different PCs and I couldn't get mine to work.
However I did get it to work by manually rebooting into recovery after flashing twrp by holding the power + volume up buttons right at the fastboot screen and releasing the buttons after seeing the Redmi name.
To clarify:
Run fastboot flash recovery twrpname.img
Do not run "fastboot boot twrpname.img"
From the fastboot screen on your phone hold the power & volume up buttons until you see the Redmi name display
You will be in TWRP