I've just unlocked the phone, via minimal ADB
tried fastboot getvar current-slot and got the output that my slot was a
then I've tried flashing TWRP at a utilizing
fastboot flash recovery twrp.img
then got the following output:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 803868672 bytes
sending 'recovery' (39780 KB)...
OKAY [ 1.663s]
writing 'recovery'...
FAILED (remote: (recovery_a) No such partition)
finished. total time: 1.695s
so, I've tried fastboot flash boot twrp.img
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot recovery.img
target reported max download size of 803868672 bytes
sending 'boot_a' (35452 KB)...
OKAY [ 1.063s]
writing 'boot_a'...
OKAY [ 0.183s]
finished. total time: 1.254s
then I've manually pressed the power button + volume up and successfully entered TWRP
there, I've gone to advanced wipe and wiped
Dalvik / ART Cache, system, Data and Internal Storage
I didn't know Internal Storage would give me problems... After that, I couldn't access my internal storage from the PC to copy the .zip of the custom rom.
Tried going to mount into TWRP to mount different partitions, no succes.
Then I thought that maybe if I restarted the phone it would be ok. So I've restarted and TWRP told me "no system installed, do you wish to continue?" I said yes.
Now, I'm stuck at fastboot and can't boot into twrp anymore...
I've tried repeating the same commands above and got the same outputs.
fastboot flash boot twrp.img got me the "OKAY" messages. But now, even if I hold the power + vol up button, I won't get to recovery.
I've tried
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 1.291s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.298s
because my frient told me to do so, but this command does not exist.
How can I proceed?
Try using mi flash tool
I was also stuck in fastboot mode I then tried installing twrp again with no success.
So I then went and flashed stock rom again into my phone using mi flash tool.
(Having a new account, I can't post link to these files. So download the files from official mi website, it is available there)
Steps to flash
1- Place the Flash File on Desktop.
2- open flash tool application.
3- Assign the Folder path.
4-Go to slot a using adb
5- Click on refresh & then tap Flash button
Related
Hello guys,
I've flashed TWRP for Nexus 9 2.8.6:
Code:
#adb devices
List of devices attached
HT4C3WV01363 device
#adb reboot bootloader
#fastboot devices
HT4C3WV01363 fastboot
#fastboot flash recovery twrp-2.8.6.0-flounder.img
target reported max download size of 518205818 bytes
sending 'recovery' (13208 KB)...
OKAY [ 0.744s]
writing 'recovery'...
(bootloader) Device State : Unlocked
OKAY [ 0.867s]
finished. total time: 1.612s
There's no way to continue into recovery without rebooting:
Code:
#fastboot reboot
rebooting...
finished. total time: 0.099s
#adb reboot recovery
... leads to a fallen Android! (see attached screenshot)
Any suggestion?
Fastboot flash TWRP recovery again.
After doing above, don't touch your PC again. Pick up your device and use volume button to navigate to hboot, then navigate to recovery and use power button to select.
Done.
Yes, thanks!
actionmystique said:
Yes, thanks!
Click to expand...
Click to collapse
Welcome. And FWIW: there's a button for that...
Hello,
I ‘ve tried to flash ma XIAOMI REDMI 3 PRO with twrp_ido, and now my phone cannot start, it is blocked on MI logo.
My phone is unlocked.
Fastboot is available.
Flash is Ok, but the recovery fastboot boot command is on error :
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (15502 KB)...
OKAY [ 0.531s]
writing 'recovery'...
OKAY [ 0.204s]
finished. total time: 0.744s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.531s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 0.626s
I’ve tried to flash manually all IMG from a stable fastboot ROM. Everythings rules but I’m staying blocked on the MI logo after rebooting
I’ve tried many cable, many computers, many MIFLASH, many TWRP sources many forums but still on same error after rebooting :
I’ve tried also to install several rom Stable /DEV fastboot with fastboot option, it doesn’t work, a readrobust js encountered
I’m blocked since several weeks and I don’t know what to do.
Could you help me your assistance will be very (very very) appreciated.
Thanks in advance
Philippe
Hi,
My LG5 850 is rooted and wiped, after testing another custom ROM. However, this time I can't reboot into recovery using the Vol-dwn/Power key-combination. Always ending-up in fastboot
Is there a command to take it from there?
Thanks a lot!
Bash:
fastboot reboot recovery
Should generally do the trick.
Unfortunately not:
LG5# fastboot reboot recovery
fastboot: usage: unknown reboot target recovery
Also tried:
LG5# fastboot flash recovery twrp-3.4.0-0-h850.img
target reported max download size of 536870912 bytes
sending 'recovery' (21124 KB)...
OKAY [ 0.681s]
writing 'recovery'...
OKAY [ 0.226s]
finished. total time: 0.907s
LG5# fastboot reboot twrp-3.4.0-0-h850.img
fastboot: usage: unknown reboot target twrp-3.4.0-0-h850.img
I tried to install TWRP
fastboot flash a twrp.img
Sending 'a' (39892 KB) OKAY [ 0.929s]
Writing 'a' FAILED (remote: '(a_a) No such partition')
fastboot: error: Command failed
astboot -w
Erase successful, but not automatically formatting.
File system type f2fs not supported.
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
erasing 'userdata'...
OKAY [ 1.057s]
erasing 'cache'...
FAILED (remote: Check device console.)
finished. total time: 1.063s
The phone is stuck in fastboot.
I tried this:
c:\TWRP>fastboot flash boot_b twrp.img
target reported max download size of 804261888 bytes
sending 'boot_b' (39892 KB)...
OKAY [ 0.931s]
writing 'boot_b'...
OKAY [ 0.215s]
finished. total time: 1.148s
fastboot boot recovery twrp.img
cannot load 'recovery': No such file or directory
fastboot erase userdata
fastboot getvar all
fastboot erase boot
fastboot set_active b
fastboot erase boot
fastboot flash boot twrp.img
fastboot reboot
I press power Volume Up but the phone boot in Fastboot
you have flashed a bad boot image. if you are on a11 stock i dont think twrp work 100% safe. los recovery is recommended and work without problems
Adroid One 10
Unlock solved and installed the lineage OS a several times in twrp with success according to the given instruction here:
https://raw.githubusercontent.com/RaghuVarma331/changelogs/master/crossdevelopment/abcrins.txt
but the phone didnt boot the OS after restarting neither in slot A nor B. In twrp u could read that there was "no OS installed" (??).
In the last try i changed the slot before installing and now the phone hangs in a restart loop with download mode and i connot turn down the phone or get back to twrp. Trying to connect it by adb to restart twrp is not working....
=========================
My errors while trying to get out:
=========================
fastboot boot twrp.img
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot B:\Various\Nokia\TWRP\twrp.img
downloading 'boot.img'...
OKAY [ 0.969s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.011s
fastboot flash recovery twrp.img
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery B:\Various\Nokia\TWRP\twrp.img
target reported max download size of 402653184 bytes
sending 'recovery' (42412 KB)...
OKAY [ 0.953s]
writing 'recovery'...
FAILED (remote: (recovery_a) No such partition)
finished. total time: 0.968s
So right now I'm at the end with my rudementary skills here.
Any idea how to get back to the point with twrp and installing an OS?
Thanks.
In case that no one else answers but someone else have the same problems , I write my solutions here.
.......
I got back to twrp by changing the slot in ADB
fastboot --set-active=a
unfortunately the restart loop doesn't end and no OS starts wether in slot a or b.