Database Info

Root: Stuck at "Your device is booting now"

Hello! I tried to root my Honor 6x (BLN-L21, EMUI 5.0) following the instructions there:
cyberkey.in/how-to-root-honor-6x-100-working/
The bootloader was successfully unlocked.
But when I tried to flash TWRP the process failed and now my phone is stuck on boot :
"Your device has been unlocked and can't be trusted [...] Your device is booting now."
I can get access to recovery and fastboot. I wiped the cache and tried a factory reset but nothing changed, my system won't start and I don't know what to do.
Please help!

if you have the boot backup then restore it.

venugopalu007 said:
if you have the boot backup then restore it.
Click to expand...
Click to collapse
I don't have any backup. Is there a way to just reset everything? Also I don't know how to connect to the phone anymore since adb won't find the device.

if you cannot find the boot.img
just do a rollback bro
here is the link
first dload this
http://download-c.huawei.com/download/downloadCenter?downloadId=94070&version=376169&siteCode=de-h
and this now
if your device is BLN-L21C432B151 http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1277/g104/v84712/f1/full/update.zip
or BLN-L21C185B131 http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1277/g104/v75593/f1/full/update.zip

I think that I flashed the wrong files in "boot" and "recovery". Please tell me which files I should flash there.
I used the commands:
.\fastboot flash boot twrp.img
.\fastboot flash recovery twrp.img

Stinks said:
I think that I flashed the wrong files in "boot" and "recovery". Please tell me which files I should flash there.
I used the commands:
.\fastboot flash boot twrp.img
.\fastboot flash recovery twrp.img
Click to expand...
Click to collapse
The guide from "cyberkey.in/how-to-root-honor-6x-100-working/" is simply wrong when it comes to flashing the twrp recovery. If you really followed this guide completely then you flashed the recovery to the boot partition.
Use "fastboot flash recovery twrp.img" to flash the recovery.
You will still have to flash the boot image to your boot partition then (fastboot flash boot boot.img).

Stinks said:
I don't have any backup. Is there a way to just reset everything? Also I don't know how to connect to the phone anymore since adb won't find the device.
Click to expand...
Click to collapse
Use fastboot flash recovery twrpname.img to flash the recovery

Ok so basically I need to flash the boot image. However I don't know where to find the stock boot image. I downloaded the so-called "full version" of the stock firmware that I found here: boycracked.com/2017/07/20/official-huawei-honor-6x-bln-l21-berlin-l21-stock-rom-firmware/
However there was no boot.img file inside.
If you could direct me to the proper stock boot.img or send me one, that would greatly help. I had EMUI 5.0 with Nougat 7.0 I believe, phone version BLN-L21.

V
Stinks said:
Ok so basically I need to flash the boot image. However I don't know where to find the stock boot image. I downloaded the so-called "full version" of the stock firmware that I found here: boycracked.com/2017/07/20/official-huawei-honor-6x-bln-l21-berlin-l21-stock-rom-firmware/
However there was no boot.img file inside.
If you could direct me to the proper stock boot.img or send me one, that would greatly help. I had EMUI 5.0 with Nougat 7.0 I believe, phone version BLN-L21.
Click to expand...
Click to collapse
Bro there is update.app open it with huawei update extractor then you will see the the boot image.but remember the emui 4.1 boot wont help you in emui 5 .the boot.img must be emui 5 once.

venugopalu007 said:
V
Bro there is update.app open it with huawei update extractor then you will see the the boot image.but remember the emui 4.1 boot wont help you in emui 5 .the boot.img must be emui 5 once.
Click to expand...
Click to collapse
Thanks. I successfully updated boot.img and and recovery.img, but system won't load, so I might have imported from the wrong STOCK version.
I tried to reinstall a stock ROM using:
fastboot flash system system.img
But I got this error message:
target reported max download size of 471859200 bytes
sending sparse 'system' (444686 KB)...
OKAY [ 12.901s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 12.929s
Then I tried to erase the system file with "erase system" and got this error:
erasing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 0.013s
I guess that the only option now is to install the files on an external SD card?

Stinks said:
Thanks. I successfully updated boot.img and and recovery.img, but system won't load, so I might have imported from the wrong STOCK version.
I tried to reinstall a stock ROM using:
fastboot flash system system.img
But I got this error message:
target reported max download size of 471859200 bytes
sending sparse 'system' (444686 KB)...
OKAY [ 12.901s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 12.929s
Then I tried to erase the system file with "erase system" and got this error:
erasing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 0.013s
I guess that the only option now is to install the files on an external SD card?
Click to expand...
Click to collapse
Bro y this ,just do a rollback .

Stinks said:
Thanks. I successfully updated boot.img and and recovery.img, but system won't load, so I might have imported from the wrong STOCK version.
I tried to reinstall a stock ROM using:
fastboot flash system system.img
But I got this error message:
target reported max download size of 471859200 bytes
sending sparse 'system' (444686 KB)...
OKAY [ 12.901s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 12.929s
Then I tried to erase the system file with "erase system" and got this error:
erasing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 0.013s
I guess that the only option now is to install the files on an external SD card?
Click to expand...
Click to collapse
I recommend you to download firmware files only from the official honor website or by using the huawei firmware finder(https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146)
In this case try to use huawei firmware finder to get the right stock version for your phone. Download these two files: e.g. update.zip & update_full_BLN-L21_hw_eu.zip.
Export the following image files: recovery, system, boot and cust.
The try to flash them:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cust cust.img
fastboot flash recovery recovery.img
If flashing a partition via fastboot fails then it is usually because it's the wrong image or just not made for your phone.

Thank you guys, you saved my phone! I eventually managed to flash the files from Nougat update for European Honor 6X BLN-L21C432B360 that I found there: stechguide.com/honor-6x-b360-nougat-update/
Now the phone is working fine.

Stinks said:
Thank you guys, you saved my phone! I eventually managed to flash the files from Nougat update for European Honor 6X BLN-L21C432B360 that I found there: stechguide.com/honor-6x-b360-nougat-update/
Now the phone is working fine.
Click to expand...
Click to collapse
Glad you revived your phone

question
​
Stinks said:
Hello! I tried to root my Honor 6x (BLN-L21, EMUI 5.0) following the instructions there:
cyberkey.in/how-to-root-honor-6x-100-working/
The bootloader was successfully unlocked.
But when I tried to flash TWRP the process failed and now my phone is stuck on boot :
"Your device has been unlocked and can't be trusted [...] Your device is booting now."
I can get access to recovery and fastboot. I wiped the cache and tried a factory reset but nothing changed, my system won't start and I don't know what to do.
Please help!
Click to expand...
Click to collapse
my phone is stuck at your device is booting now i cant get to any of other functions such as fastboot or recovry i can only acces it after full charge is gone and after charging.how did you get to acces fastboot or recover.

[email protected] said:
question
my phone is stuck at your device is booting now i cant get to any of other functions such as fastboot or recovry i can only acces it after full charge is gone and after charging.how did you get to acces fastboot or recover.
Click to expand...
Click to collapse
did you solve your issue.....I have same problem now

nokiasatyam said:
did you solve your issue.....I have same problem now
Click to expand...
Click to collapse
Hello, could you be more specific about your problem? I'll be able to help you.
Brief Explanation:
From the screen on which you're stuck, press and hold power button for about 10 seconds to forcibly restart your device. when you see the same screen again, immediately press and hold volume up button(for about 3 seconds) to boot to eRecovery.
> Choose shut down option on eRecovery. press and hold vol down button and insert the charging cable to boot to fastboot.
> Press and hold power and volume up button to boot to recovery. (You could do this even from fastboot screen and the screen you're stuck at).

Htc bootloader unlocked but Not Allowed on Production Device

I am currently running android 9.0 on htc dual sim model. i have unlocked my bootloader but whenever i tried to flash twrp or any other fastboot command after sending it says not allowed on production device.
target reported max download size of 536870912 bytes
sending 'recovery' (46340 KB)...
OKAY [ 1.320s]
writing 'recovery'...
FAILED (remote: Not allowed on PRODUCTION device)
finished. total time: 1.355s
i have tried both commands
fastboot flash recovery
htc_fastboot flash recovery (through different folder heaving related files)
Help me Solve that issue.

hassanulhaq said:
I am currently running android 9.0 on htc dual sim model. i have unlocked my bootloader but whenever i tried to flash twrp or any other fastboot command after sending it says not allowed on production device.
target reported max download size of 536870912 bytes
sending 'recovery' (46340 KB)...
OKAY [ 1.320s]
writing 'recovery'...
FAILED (remote: Not allowed on PRODUCTION device)
finished. total time: 1.355s
i have tried both commands
fastboot flash recovery
htc_fastboot flash recovery (through different folder heaving related files)
Help me Solve that issue.
Click to expand...
Click to collapse
I recently unlocked bootloader to flash Magisk so I could have root access. I was getting the same error and found out that you must do the flashing in "download mode", not in fastboot or bootloader mode.
---------- Post added at 01:32 AM ---------- Previous post was at 01:31 AM ----------
hassanulhaq said:
I am currently running android 9.0 on htc dual sim model. i have unlocked my bootloader but whenever i tried to flash twrp or any other fastboot command after sending it says not allowed on production device.
target reported max download size of 536870912 bytes
sending 'recovery' (46340 KB)...
OKAY [ 1.320s]
writing 'recovery'...
FAILED (remote: Not allowed on PRODUCTION device)
finished. total time: 1.355s
i have tried both commands
fastboot flash recovery
htc_fastboot flash recovery (through different folder heaving related files)
Help me Solve that issue.
Click to expand...
Click to collapse
I recently unlocked bootloader on my HTC U11 to flash Magisk so I could have root access. I was getting the same error and found out that you must do the flashing in "download mode", not in fastboot or bootloader mode.

Download mode
CiroConsentino said:
I recently unlocked bootloader to flash Magisk so I could have root access. I was getting the same error and found out that you must do the flashing in "download mode", not in fastboot or bootloader mode.
---------- Post added at 01:32 AM ---------- Previous post was at 01:31 AM ----------
I recently unlocked bootloader on my HTC U11 to flash Magisk so I could have root access. I was getting the same error and found out that you must do the flashing in "download mode", not in fastboot or bootloader mode.
Click to expand...
Click to collapse
How to do that in download mode?

hassanulhaq said:
How to do that in download mode?
Click to expand...
Click to collapse
hi, sorry for the late reply, my brother "borrowed" my phone for a couple weeks and he did a factory reset. I don't have my phone yet, hopefully I won't have to unlock the phone again or flash Magisk into the bootloader again either...
To unlock the bootloader, I followed this nice and detailed tutorial here:
https://www.getdroidtips.com/unlock-bootloader-htc-u11/
Click to expand...
Click to collapse
.
Then I followed Magisk's official tutorial on how to flash it without a custom recovery... here
https://savegyd.com/magisk-root-tutorial/
Click to expand...
Click to collapse
... just go to the "How to install Magisk with ADB and Fastboot (without custom recovery)" section and read it carefully, but instead of rebooting the phone into fastboot mode, I had to do it all in download mode.
I I did not install TWRP custom recovery, I manually patched the stock "boot.img" file with Magisk and then flashed the patched boot with this command with the ADB tool in Windows (phone in download mode):
fastboot flash boot patched_boot.img. I wanted to keep HTC's stock recovery.
Then I rebooted the phone into Android, and opened "Magisk" app in Android to make sure the root was working...
I didn't have internet connection in my phone (data connection or wifi), I did it all offline.
If you don't have the locked "boot.img" you must check the exact version of your installed Android OS and download the correct RUU file. Then you can extract the boot.img from it, patch it with Magisk, then flash it into the phone.
I did it in download mode as it was failing in fastboot mode. Make sure to enter download mode when you restart your phone, not fastboot mode. I'm not responsible if you brick your phone. My phone is the "Global" version from India (6GB RAM, 128GB internal storage).

issue resolved
CiroConsentino said:
hi, sorry for the late reply, my brother "borrowed" my phone for a couple weeks and he did a factory reset. I don't have my phone yet, hopefully I won't have to unlock the phone again or flash Magisk into the bootloader again either...
To unlock the bootloader, I followed this nice and detailed tutorial here: .
Then I followed Magisk's official tutorial on how to flash it without a custom recovery... here
... just go to the "How to install Magisk with ADB and Fastboot (without custom recovery)" section and read it carefully, but instead of rebooting the phone into fastboot mode, I had to do it all in download mode.
I I did not install TWRP custom recovery, I manually patched the stock "boot.img" file with Magisk and then flashed the patched boot with this command with the ADB tool in Windows (phone in download mode):
fastboot flash boot patched_boot.img. I wanted to keep HTC's stock recovery.
Then I rebooted the phone into Android, and opened "Magisk" app in Android to make sure the root was working...
I didn't have internet connection in my phone (data connection or wifi), I did it all offline.
If you don't have the locked "boot.img" you must check the exact version of your installed Android OS and download the correct RUU file. Then you can extract the boot.img from it, patch it with Magisk, then flash it into the phone.
I did it in download mode as it was failing in fastboot mode. Make sure to enter download mode when you restart your phone, not fastboot mode. I'm not responsible if you brick your phone. My phone is the "Global" version from India (6GB RAM, 128GB internal storage).
Click to expand...
Click to collapse
Issue was resolved. My phone's bootloader was unlocked and and top of all it got pie update on unlocked bootloader with rooted phone and updated to android pie, then it started creating random issues like phone booting time was around 10 to 15 mins and i was getting above mentioned error. whenever i was booting to download mode my system was not detecting my phone but in fastboot mode it was detecting (kind of strange issue)... which turns out to be a cable issue. Once i changed my cable my phone was detected in download mode. So i re-locked the bootloader and then again flashed the firmware everything came to normal. Phone is up and working fine and thanks for help again.

How to backup stock recovery before flashing TWRP?

Hi. How can I backup the stock recovery on my Xiaomi Poco X3 NFC before flashing the TWRP?
I tried executing following code while the phone is in fastboot mode but it never actually boots the custom recovery. It get's stuck at the poco boot logo. Yes my phone has unlocked bootloader.
Code:
fastboot boot TWRP.img
In terminal I get this output:
Code:
[email protected]:/# fastboot boot twrp_3.4.0-15_mauronofrio.img
downloading 'boot.img'...
OKAY [ 3.080s]
booting...
OKAY [ 5.088s]
finished. total time: 8.168s
Does anybody know why this command is not working? Thanks.

lebigmac said:
Hi. How can I backup the stock recovery on my Xiaomi Poco X3 NFC before flashing the TWRP?
I tried executing following code while the phone is in fastboot mode but it never actually boots the custom recovery. It get's stuck at the poco boot logo. Yes my phone has unlocked bootloader.
Code:
fastboot boot TWRP.img
In terminal I get this output:
Code:
[email protected]:/# fastboot boot twrp_3.4.0-15_mauronofrio.img
downloading 'boot.img'...
OKAY [ 3.080s]
booting...
OKAY [ 5.088s]
finished. total time: 8.168s
Does anybody know why this command is not working? Thanks.
Click to expand...
Click to collapse
I have had the same issues with that TWRP from mauronofrio and our stock ramdisk image. However, using Orangefox or the latest 3.5.0 TWRP which can be found in the Index for our device (everything can be found there lol) solved that issue, also, you don't need to backup the recovery partition, because the stock can be easily found and flashed the same.

Thanks but that still doesn't explain why the command fastboot boot twrp.img doesn't work on the Xiaomi Poco X3 NFC with unlocked bootloader.
EDIT:
Ok good news. I've actually managed to boot into the TWRP before flashing it.
As soon as it's done uploading the recovery to the phone you must unplug the USB cable. The timing is very important.
Good luck!

lebigmac said:
This appears to be a more widespread issue than I had originally thought:
Fastboot boot <boot.img> doesn't work but flash does
Hi there ! I compiled a kernel for my DB410. I am trying to boot it using $ fastboot boot boot.img Following the instructions that can be found here: https://builds.96boards.org/releases/dragonboard410c/linaro/debian/17.06.1/ Unfortunately, the device doesn’t boot. It starts the booting...
discuss.96boards.org
fastboot boot TWRP.img Not working
I'm trying to just boot the TWRP image for my OnePlus 5t to then install a custom ROM. So I typed fastboot boot "C:\Users\Elias\Downloads\twrp-3.3.1-0-dumpling.img" and it seemed to work and I got ...
android.stackexchange.com
https://www.reddit.com/r/LineageOS/comments/arakiy
After Android Q upgrade fastboot boot doesn't work on guacamole · Issue #1530 · TeamWin/Team-Win-Recovery-Project
I am running an official build of TWRP, downloaded from https://twrp.me/Devices/ I am running the latest version of TWRP I have read the FAQ (https://twrp.me/FAQ/) I have searched for my issue and ...
github.com
Can't boot TWRP image using fastboot boot
I'm trying to root my Moto Z3 Play. I'm on Windows 10, I have already unlocked the bootloader, however, I can't boot the twrp.img. I got the twrp.img from here https://twrp.me/motorola/motorolamoto...
stackoverflow.com
Click to expand...
Click to collapse
try latest OFOX or TWRP (OFOX image needs to be extracted from zip file), I'm really interested if some of these will boot via "fastboot boot recovery.img", thanks

lebigmac said:
Hi. How can I backup the stock recovery on my Xiaomi Poco X3 NFC before flashing the TWRP?
I tried executing following code while the phone is in fastboot mode but it never actually boots the custom recovery. It get's stuck at the poco boot logo. Yes my phone has unlocked bootloader.
Code:
fastboot boot TWRP.img
In terminal I get this output:
Code:
[email protected]:/# fastboot boot twrp_3.4.0-15_mauronofrio.img
downloading 'boot.img'...
OKAY [ 3.080s]
booting...
OKAY [ 5.088s]
finished. total time: 8.168s
Does anybody know why this command is not working? Thanks.
Click to expand...
Click to collapse
You don't need to backup the sock recovery.
Everything you need to do is download the stock rom and extract recovery.

@jeryll thanks for chiming in. All of these TWRP images will boot via "fastboot boot recovery.img" on our device.
It's important to unplug the USB cable at the right moment as soon as it's done uploading. Good luck!

[SOLVED] Unable to flash boot image - Pixel 4a

I have been using this method to flash new stock update every month to my rooted pixel 4a.
Steps I follow:
- Download the factory image of the last month
- Extract the boot.img. And patch it using magisk canary build
- Move the boot.img to the computer and flash it in fastboot mode
- flash the complete image
- Reroot the phone using magisk
This time with January update, I am getting stuck on step 3. Everytime I try to flash the bootloader image using the command:
C:\platform-tools>fastboot flash bootloader "C:\platform-tools\magisk_boot.img.img"
I get the following error:
Sending 'bootloader' (65536 KB) OKAY [ 1.609s]
Writing 'bootloader' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
No, It isn't booted in fastbootd mode. I am using correct Fastboot mode using the hotkeys
Kindly assist. Thank you

Your fastboot may be old... Upgrading it might help.
Or you might be able to use fastboot boot patched.img to get temporary root and use Magisk manager to install (direct) to make it permanent. That's what I do, and it's always worked.

Absarock said:
I have been using this method to flash new stock update every month to my rooted pixel 4a.
Steps I follow:
- Download the factory image of the last month
- Extract the boot.img. And patch it using magisk canary build
- Move the boot.img to the computer and flash it in fastboot mode
- flash the complete image
- Reroot the phone using magisk
This time with January update, I am getting stuck on step 3. Everytime I try to flash the bootloader image using the command:
C:\platform-tools>fastboot flash bootloader "C:\platform-tools\magisk_boot.img.img"
I get the following error:
Sending 'bootloader' (65536 KB) OKAY [ 1.609s]
Writing 'bootloader' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
No, It isn't booted in fastbootd mode. I am using correct Fastboot mode using the hotkeys
Kindly assist. Thank you
Click to expand...
Click to collapse
fastboot flash boot
And not
fastboot flash bootloader
Cheers!

Typhus_ said:
fastboot flash boot
And not
fastboot flash bootloader
Cheers!
Click to expand...
Click to collapse
Thank you, sir. It helped

a1291762 said:
Your fastboot may be old... Upgrading it might help.
Or you might be able to use fastboot boot patched.img to get temporary root and use Magisk manager to install (direct) to make it permanent. That's what I do, and it's always worked.
Click to expand...
Click to collapse
I tried updating fastboot. Didn't work.
Either way I was able to solve by using the command boot_b instead of bootloader. B being the partition

Question stuck in fastboot mode

after unlocking my bootloader i tried to flash magisk.zip in fastboot mode by typing fastboot flash boot magisk.zip
now im stuck in fastboot mode. Enter reason: boot failure
with oneplus devices you can always go back to stock with msm tool. is there anything like that for pixel devices? or did i just turn my new phone into a shiny new paper weight?

barbosa212 said:
after unlocking my bootloader i tried to flash magisk.zip in fastboot mode by typing fastboot flash boot magisk.zip
now im stuck in fastboot mode. Enter reason: boot failure
with oneplus devices you can always go back to stock with msm tool. is there anything like that for pixel devices? or did i just turn my new phone into a shiny new paper weight?
Click to expand...
Click to collapse
To root you flash the patched boot image (the one you patched in Magisk), not magisk.zip.
Try flashing the stock boot image to get back to normal and then flash the patched boot image in fastboot.
See this guide.

Lughnasadh said:
To root you flash the patched boot image (the one you patched in Magisk), not magisk.zip.
Try flashing the stock boot image to get back to normal and then flash the patched boot image in fastboot.
See this guide.
Click to expand...
Click to collapse
Sending 'boot_a' (65536 KB) OKAY [ 1.715s]
Writing 'boot_a' (bootloader) unable to update boot image: use unmerged...
OKAY [ 0.144s]
Finished. Total time: 1.897s
now im at "waiting for rescue commands..." what do?

barbosa212 said:
Sending 'boot_a' (65536 KB) OKAY [ 1.715s]
Writing 'boot_a' (bootloader) unable to update boot image: use unmerged...
OKAY [ 0.144s]
Finished. Total time: 1.897s
now im at "waiting for rescue commands..." what do?
Click to expand...
Click to collapse
i held the power button until it rebooted successfully. Thank you so much

barbosa212 said:
i held the power button until it rebooted successfully. Thank you so much
Click to expand...
Click to collapse
If you want to root/flash, I recommend PixelFlasher. A simple and effective tool and saves you from trouble!