I just flashed the latest AEX, Pico GApps & Gabriel Kernel. There were no error message in the TWRP. I then wiped cache and then rebooted it. Suddenly my phone stucks at Fastboot logo.
I tried press the power button & recovery combo multiple time but it will always comes back to Fastboot logo. I can't turn it off at all, I can't reboot it to the system, I can't boot it to TWRP either. Nothing works.
I tried booting it using fastboot on computer. Tried using
Code:
fastboot flash recovery twrp_name.img
command. It succesfully flashed the twrp. But when I try to boot to TWRP using the
Code:
fastboot boot twrp_name.img
] command, it always fails. The error messages are either
Code:
FAILED (Status read failed (Too many links))
or
Code:
FAILED (remote: 'dtb not found')
Tried some other commands like
Code:
fastboot reboot bootloader
but they always come back to the Fastboot logo screen. The Fastboot has also been unlocked.
What should I do? Anyone has an idea? It's been more than an hour and everyone I asked no one has a clue how to solve it.
flash miui stable rom through fastboot
Download stock miui fastboot image from official miui website.
Extract the zip. (7zip Preferred)
Extract the file inside it. (If any)
Select clean_all.bat
Wait till the process completes.
Reboot.
This will fix the issue.
Dont flash ROM + Gapps + Kernel all together.
Just flash ROM and Gapps let first device boot after setting device later flash kernel.
Related
I dirty flashed a new version of xiaomi.eu stable build, and it caused TWRP to uninstall itself.
Whenever I hold power on and volume up it just goes to fastboot.
Now I tried reinstalling TWRP like I've done many times before, but it keeps throwing an error. The error I get is when trying to boot without flashing the img. When I do this, I get the error:
Code:
fastboot boot TWRP.img"
downloading 'boot.img'...
OKAY [ 1.609s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.675s
Anyone gotten any ideas on what could be going on here? I'm scared to try anything as my phone currently works, but I need TWRP back to update my phone to a different versions and to install the clock mod again.
Thanks!
Got it to load once, but now back to square one. Throwing same error.
Now when running the command fastboot reboot recovery it's saying
Code:
fastboot: usage: unknown reboot target recovery
And writing 'fastboot boot twrp.img' turns the phone off / makes the screen go black. Fully bricked now as the OS wont load either.
Try on a computer with a USB 2.0 port, or a different usb cable, had the same issue once
Ended up having to reinstall dev rom. Device relocked, so have to wait 15 days again. @BusterBg_18 Thanks, will do when I unlock the device
EDIT: When using Mi Flash tool, make sure to check 'clean all' and not 'clean all and lock' in the bottom right. That's what set me back 2 weeks.
I have the same error. How can I fix this pls?
MrkoZino said:
I have the same error. How can I fix this pls?
Click to expand...
Click to collapse
Flash the latest official rom then start all over again. Follow the post above you about miflash.
Hello, I've had the same problem, then flashed latest dev rom via MiFlash and it booted, but now after I flash any custom ROM in TWRP i have this issue again and need to reflash chinese ROM. How can I flash any custom rom?
i'm stuck in the same issue. stuck in fastboot and it would not load recovery. any fix?
Hi, i fixed the "Failed to load/authenticate boot image: Load Error" by simply restarting the Device.
It seems to appear randomly when flashing partitions and then block all further Transfers.
If the Device loops in Fastboot, the only Solution to me was re flashing the Stock Firmware.
greendra8 said:
And writing 'fastboot boot twrp.img' turns the phone off / makes the screen go black. Fully bricked now as the OS wont load either.
Click to expand...
Click to collapse
I have the same Issue, but reflashing Stock Firmware or making OTA Updates dident helped for me. Ive already tried TWRP and OrangeFox without success. The Screen always turns black and Fastboot stays active in an limited Mode, any Ideas? My host Computer only has 3.0+ Ports only, but ive used an 2.0 Extender so it should be fine?
DJPlaya said:
Hi, i fixed the "Failed to load/authenticate boot image: Load Error" by simply restarting the Device.
It seems to appear randomly when flashing partitions and then block all further Transfers.
If the Device loops in Fastboot, the only Solution to me was re flashing the Stock Firmware.
I have the same Issue, but reflashing Stock Firmware or making OTA Updates dident helped for me. Ive already tried TWRP and OrangeFox without success. The Screen always turns black and Fastboot stays active in an limited Mode, any Ideas? My host Computer only has 3.0+ Ports only, but ive used an 2.0 Extender so it should be fine?
Click to expand...
Click to collapse
long time ago now. but i remember at one point having to flash the stock firmware using the mi unlock tool. i also remember trying every single version of twrp and rom until one finally worked. sorry i can't help much but i believe that's how i eventually fixed it.
hi, I've experienced with the same thing.
this methode help me out from it.
try to reflashing some file image from the rom where youre want to install in hh with adb.
copy this files below from rom image to adb folder
1. system.img (command in adb >> fastboot flash system system.img)
2. boot.img (command in adb like #1, change the name of img file) do till #6
3. vendor.img
4. dtbo.img
5. cust.img
6. misc.img
7. now flashing twrp/recovery.img (choose twrp compatible with rom you want to install) with adb
8. the "fastboot boot recovery.img" with adb
9. flashing the rom by twrp
Marihot said:
hi, I've experienced with the same thing.
this methode help me out from it.
try to reflashing some file image from the rom where youre want to install in hh with adb.
copy this files below from rom image to adb folder
1. system.img (command in adb >> fastboot flash system system.img)
2. boot.img (command in adb like #1, change the name of img file) do till #6
3. vendor.img
4. dtbo.img
5. cust.img
6. misc.img
7. now flashing twrp/recovery.img (choose twrp compatible with rom you want to install) with adb
8. the "fastboot boot recovery.img" with adb
9. flashing the rom by twrp
Click to expand...
Click to collapse
Where do you get these .img files?
iconoclasthero said:
Where do you get these .img files?
Click to expand...
Click to collapse
all img files come from the official rom china stable V12.0.2.0.QEBCNXM (.tgz), download and extract the tgz file then find img files from images folder
Marihot said:
all img files come from the official rom china stable V12.0.2.0.QEBCNXM (.tgz), download and extract the tgz file then find img files from images folder
Click to expand...
Click to collapse
Please tell the details for this method
greendra8 said:
Ended up having to reinstall dev rom. Device relocked, so have to wait 15 days again. @BusterBg_18 Thanks, will do when I unlock the device
EDIT: When using Mi Flash tool, make sure to check 'clean all' and not 'clean all and lock' in the bottom right. That's what set me back 2 weeks.
Click to expand...
Click to collapse
BROOOOOOOOOO HAHAHAHAHAHA I LITERALLY JUST READ YOUR COMMENT AND 10 SECONDS LATER I FLASH THE ROM WITH "CLEAN ALL AND LOCK" Im a f-king dumb bro
Marihot said:
你好，我也经历过同样的事情。
这个方法帮助我摆脱它。
尝试使用 adb 从要在 hh 中安装的 rom 中重新刷新一些文件映像。
将下面的文件从 rom 映像复制到 adb 文件夹
1.system.img（adb >> fastboot flash system system.img中的命令）
2. boot.img（adb 中的命令，如#1，更改 img 文件的名称）直到 #6
3. 供应商.img
4.dtbo.img
5. 自定义.img
6. 杂项.img
7. 现在用adb刷twrp/recovery.img（选择twrp与你要安装的rom兼容）
8. adb 的“fastboot boot recovery.img”
9. twrp刷入rom
Click to expand...
Click to collapse
Thank you, brother
try fastboot set_active a
or fastboot set_active b
Motorola One Power is not responding to fastboot commands.
*Screenshot attached*
Whenever I try to flash or boot anything through fastboot :-
1. It never returns the max_size
2. Stuck on the downloading <filename.img> it can be anyfile i.e boot.img, bootloader.img, system.img etc
3. Process a single command for forever
What I've done till now :-
1. Tried flashing stock rom :- Failed
2. Tried Blankflashing :- Failed
3. Tried all ports
4. Tried Various Base OS (win10,8,7) (CentOS,Kali)
5. Tried Different PCs
Even I've given it to service center and I've got Fresh OS installed i.e Pie with August Patch installed but still instead of having bootloader installed and debugging mode on I cannot flash anything through fastboot.
Please Help Me!!!
C:\adb> adb reboot bootloader
C:\adb> fastboot devices
ZF6223RGJK fastboot
C:\adb> fastboot flash recovery twrp.img
downloading 'boot.img'...
Hello,
I deciden to install Android 10 Beta 3 then install a custom rom. I succesfully installed Android 10 Beta 3, and tried to install Magisk as told in here. After the patched boot.img step, my device stopped booting.
When I press Power+Volume Up or Down, it always goes to fastboot mode. I can't boot into recovery from fastboot, I can't boot TWRP from fastboot. I tried:
fastboot oem reboot-recovery
fastboot boot twrp.img
fastboot flash recovery twrp.img
As shown in the image rebooting into recovery always failing. What can I do?
same problem here... were you able to fix it?
You might have to use the QFIL method to get your phone going again. Remember you MUST backup the EFS partition and anything associated with your phones imei and SN
Lirimaer said:
Hello,
I deciden to install Android 10 Beta 3 then install a custom rom. I succesfully installed Android 10 Beta 3, and tried to install Magisk as told in here. After the patched boot.img step, my device stopped booting.
When I press Power+Volume Up or Down, it always goes to fastboot mode. I can't boot into recovery from fastboot, I can't boot TWRP from fastboot. I tried:
fastboot oem reboot-recovery
fastboot boot twrp.img
fastboot flash recovery twrp.img
As shown in the image rebooting into recovery always failing. What can I do?
Click to expand...
Click to collapse
flash the boot partition then flash stock recovery then try to flash twrp then try to flash a custom or stock rom what you want.
Lirimaer said:
Hello,
I deciden to install Android 10 Beta 3 then install a custom rom. I succesfully installed Android 10 Beta 3, and tried to install Magisk as told in here. After the patched boot.img step, my device stopped booting.
When I press Power+Volume Up or Down, it always goes to fastboot mode. I can't boot into recovery from fastboot, I can't boot TWRP from fastboot. I tried:
fastboot oem reboot-recovery
fastboot boot twrp.img
fastboot flash recovery twrp.img
As shown in the image rebooting into recovery always failing. What can I do?
Click to expand...
Click to collapse
Anyone solve this problem?
Juninalilla said:
有人解决这个问题吗？
Click to expand...
Click to collapse
这两个可怕的重锁码吓了我一跳，以为手机没电了。幸运的是，我找到了解决方案。你可能需要找个老股rec，跟着视频操作，不用拆机，重点解压。进入adb文件夹，生效
Lirimaer said:
Hello,
I deciden to install Android 10 Beta 3 then install a custom rom. I succesfully installed Android 10 Beta 3, and tried to install Magisk as told in here. After the patched boot.img step, my device stopped booting.
When I press Power+Volume Up or Down, it always goes to fastboot mode. I can't boot into recovery from fastboot, I can't boot TWRP from fastboot. I tried:
fastboot oem reboot-recovery
fastboot boot twrp.img
fastboot flash recovery twrp.img
As shown in the image rebooting into recovery always failing. What can I do?
Click to expand...
Click to collapse
Hey guy,
My phone was running the rom "UL-ASUS_X00QD-ASUS-AOSP-17.0615.2005.25-1.1.1-user.zip" (downloaded from Asus Web). I tried to install the TWRP ver 3.3.1 unofficial and my phone was stuck on the fastboot mode only.
After a lot of searching on how to fix the issue, I didn't change anything and almost gave up, until I've read this thread.
My Asus Zenfone 8 flip is STUCK in CSC FASTBOOT MODE PLZ HELP!, RAW FIRMWARE ANYONE???
These are what I did to get the phone into the recovery mode:
1. Extract the rom zip file that my phone was running on.
2. Copy the file boot.img to adb folder.
3. On PC, at adb folder enter CMD, connect the phone then type
fastboot -w
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot reboot recovery
4. After that, my phone can be booted into the recovery mode.
Hope you can solve the same problem as me.
Bye bye ...
Hi,
I have Carbon ROM with Android 10,
I wanted to flash Bliss ROM, and it says that I need a rooted device,
So I've downloaded Magisk and follow the instruction, created a boot.img and flashed it in fastboot, then I did the same only with twrp recovery & Magisk, flashed it and now it is wiered and I'm not sure what is the problem,
I have fastboot BUT when I try to perform any command, it shutsdown and preety useless, I've tried from PC, if I try from MAC, I can boot into twrp but every operation is causing the tablet to reboot.. So I can't even flash a stock ROM,
In PC, the recognized Android device (When in fastboot mode) I update it's driver to Android bootloader device
Now, fastboot says: "fastboot: error: cannot get boot partition size"
tried:
fastboot flash:raw boot boot.img
fastboot flash:raw recovery twrp.img
How can I solve it?
Thanks !!!
Did you also try
Code:
fastboot flash boot boot.img
?
I can boot into twrp but every operation is causing the tablet to reboot
Click to expand...
Click to collapse
I didn't understand the problem, I think.
You flashed a patched boot.img and your twrp recovery isn't working? Like if you press a button, it just reboots?
I have fastboot BUT when I try to perform any command, it shutsdown and preety useless
Click to expand...
Click to collapse
If you do
Code:
fastboot devices
it also doesn't work?
Or only if you flash a img?
Hello,
I had LineageOS running for some time without any issues.
Then I tried to install a fresh copy of LineageOS by fastbooting the most recent recovery image like this:
fastboot flash vendor_boot <recovery_filename>.img
This command works and says "OKAY" and "Finished" but now I'm stuck in Fastboot Mode with "error boot prepare" and it won't launch into Recovery Mode.
How do I start over with a fresh recovery image?
Thank you
moniker5438 said:
Hello,
I had LineageOS running for some time without any issues.
Then I tried to install a fresh copy of LineageOS by fastbooting the most recent recovery image like this:
fastboot flash vendor_boot <recovery_filename>.img
This command works and says "OKAY" and "Finished" but now I'm stuck in Fastboot Mode with "error boot prepare" and it won't launch into Recovery Mode.
How do I start over with a fresh recovery image?
Thank you
Click to expand...
Click to collapse
Not sure if it will help but, sometimes you might need to...
- Flash the same version of the boot image.
- Flash both slots with the same version.
[ fastboot flash boot boot.img ]
[ fastboot --slot all flash vendor_boot vendor_boot.img ]
[ fastboot --slot all flash boot boot.img ]
Cheers.
Thanks for your response. This issue is resolved.
About a year ago, I originally installed MicroG LineageOS (lineage.microg.org) and used their recovery image and build with no issues.
Now, for some reason, that exact same recovery image doesn't work anymore and gives "error boot prepare". Similarly, the latest version of the MicroG LineageOS recovery image gives "error boot prepare".
The only recovery image that would work is vendor_boot.img from LineageOS (without MicroG):
https://mirror.math.princeton.edu/pub/lineageos/full/barbet/ (in my case 20220915)
Using that I could adb sideload the latest MicroG LineageOS (from 20220915)
Hello guys, did you able to use esim? on latest lineage os? When I click on + to add esim, nothing happens