Database Info

[Q] Stuck in a boot loop after using ASUS unlock tool

Hi guys,
I had a stock tf700, running ICS (4.1.1) and I followed the really good guide by sdbags on how to unlock/root.
I rooted it with no problems, and used the ASUS unlock tool which seemed to work (it says that my device in unlocked), but now I am stuck in a boot loop
It fully boots up and can stay working for about 30 seconds to a minute and then it just reboots.
I can get access to the bootloader but I have no idea what I'm doing. I haven't installed TWRP yet either.
I'm sceptical of just hitting "wipe data" as I hear I could brick it for good.
Any help would be greatly appreciated....I'm really at a loss!!

I've seen this behavior when the kernel was newer than the bootloader and incompatible - but if you haven't installed anything yet this is unlikely to be the reason for your problems. You can try to enable USB debugging, run "adb pull /proc/last_kmsg" and see if that file contains any interesting information about the reboot.
If you want to wipe data, you can choose RCK from the bootloader menu - if it loads the stock recovery (Android mascot with red triangle), you know that the recovery is good and you should be safe to run "wipe data". I have only seen the stock recovery once and that was almost 2 years ago, but if you press the Power button in the recovery, you may even get a menu from which you can wipe directly from the recovery (use power and volume keys to navigate).

Discard this post
HTC maxx

_that said:
I've seen this behavior when the kernel was newer than the bootloader and incompatible - but if you haven't installed anything yet this is unlikely to be the reason for your problems. You can try to enable USB debugging, run "adb pull /proc/last_kmsg" and see if that file contains any interesting information about the reboot.
If you want to wipe data, you can choose RCK from the bootloader menu - if it loads the stock recovery (Android mascot with red triangle), you know that the recovery is good and you should be safe to run "wipe data". I have only seen the stock recovery once and that was almost 2 years ago, but if you press the Power button in the recovery, you may even get a menu from which you can wipe directly from the recovery (use power and volume keys to navigate).
Click to expand...
Click to collapse
Thanks for the advice. I chose RCK from the bootloader menu but it just boots normally....no Android mascot. Am I doing something wrong there?excuse my complete newbness)
Is there a big risk in running "wipe data"? If I haven't installed any custom ROMs or flashed anything yet, is the risk of a brick slightly reduced?

bnscow said:
Thanks for the advice. I chose RCK from the bootloader menu but it just boots normally....no Android mascot. Am I doing something wrong there?excuse my complete newbness)
Click to expand...
Click to collapse
There's not much one can do wrong here - turn on tablet and hold volume-down until the bootloader menu appears, then hit volume-up to confirm "RCK", that should boot the recovery. If it starts the regular OS instead, something is wrong.
bnscow said:
Is there a big risk in running "wipe data"? If I haven't installed any custom ROMs or flashed anything yet, is the risk of a brick slightly reduced?
Click to expand...
Click to collapse
I wouldn't risk it if you can't even get to recovery manually ("wipe data" uses the recovery to wipe - if the recovery doesn't work, it's a hard brick).
Try installing TWRP via fastboot.

_that said:
There's not much one can do wrong here - turn on tablet and hold volume-down until the bootloader menu appears, then hit volume-up to confirm "RCK", that should boot the recovery. If it starts the regular OS instead, something is wrong.
Click to expand...
Click to collapse
Thanks for the advice. I took a couple of days break but I'm back trying to fix it.
I tried RCK and it just boots to a dead android man with the triangle error.
_that said:
Try installing TWRP via fastboot.
Click to expand...
Click to collapse
Also, I tried flashing TWRP via fastboot but after entering the flash recovery command, I keep getting an error message after entering saying "Too many links". Do you have any idea why that may be? I'm flashing TWRP 2.6.3.2
Thanks in advance!

Asus TF700T Tablet fix
Try this, it worked for me....and the standard disclaimer: I am not responsible if you misunderstand instructions I give here, if my instructions are wrong, if you forget to charge the battery and the tablet dies halfway through a flash or if your house goes up in flames. YOU DO THIS AT YOUR OWN RISK
Ok, so I think that I may have lost power during an upgrade (can’t think of any other reason for it!!) and ended up soft bricking my Asus TF700T tablet and recovery attempts would just lead to the dead Android with a red triangle with an exclamation point in the middle. My warranty having expired with Asus and any attempt for their assistance proved fruitless.
Well I researched and tried absolutely everything out there – (Hard Reset, installing TWRP, used a tool called Motochopper and flashing a custom ROM, downloaded and renaming .zip files, putting it onto a Micro SDcard is formatted Fat32, Scotts Tf700t Recovery etc.etc. etc.)
I even took it to the local shops and paid to have one of the Mobile Technician pop-up stores take a look at it, then a friendly techno geek………all with the same suggestions most likely a motherboard/hard drive problem.
My Asus TF700T tablet eventually ended up with just the plain white ASUS logo in the middle of the screen, some small print in the top left corner followed by the dreaded words “Unrecoverable Bootloader Error (0x00000000)”.
During all of my research I was led to believe that if you can still get to the recovery screen, where you see the 4 icons, all is not lost so I persisted.
Here is the instructions that I followed that restored my TF700T:
Download and install ADB, Fastboot and the required drivers - Download and run this cool little tool which has it all packed into one: [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.1 - xda-developers (don't forget to hit the Thanks button)
NOTE: at the moment Fastboot seems to have issues with Windows 8
This awesome tool installs the ADB and Fastboot.exe to a folder on your C:\ drive (look for a file titled “adb”) as well as the corresponding drivers. This takes about 15 seconds to install following the prompts.
I installed the device drivers - if you have already tried to connect the tablet to your PC and it's recognised as a portable device you should be ok. If not, download the Asus Sync Utility from their support/downloads site and install it.
Download the latest firmware from Asus (Always make sure that you download the correct SKU version -WW, US etc.) and extract the zip twice so you access the blob file (a blob is a collection of binary data stored as a single entity) – copy and paste this blob file into the previously mentioned “adb” folder on your C:\ drive.
Reset the device with a paperclip/needle (about 2 cm down of the SDcard slot)
Power down the tablet and disconnect it from the keyboard dock.
Connect it to your computer via the original USB cable.
Push and hold the Volume Down key (left side of the rocker) and the Power key until you feel the tablet vibrate twice. Let go when you see the tiny script. Read it and it tells you that your tablet is now in Fastboot mode and you will see three or 4 icons (depending on the bootloader version). Select the USB icon to get into the Fastboot mode.
Your PC should acknowledge that a USB device has been connected (an audible indication) Don’t panic if the device does not appear under “My Computer” (as mine did not either – Fastboot will still communicate with it), you can go into Control Panel/Hardware and Sound/ Device Manager and you may see “Fastboot” icon, expand this and the device will be represented again by the “Fastboot” icon. Right click, select “Properties”, Driver tab and then select “Update Driver” and allow it to search automatically and update from the internet. This should then update and change to Asus icons. You now can be certain that you have the current device drivers.
In Windows Explorer navigate to the folder that contains your adb.exe and fastboot.exe
Win 7 press Shift + right click and select "Open command window here".
In the resulting command prompt screen type the following codes (those in bold):
C:\adb\ (or whatever the path to your fastboot folder is..)
fastboot devices (If that command returns a string of numbers and letters, you are good as gold. If it returns: "No devices found", fastboot is not working - yet - and you have to troubleshoot)
Followed by each in turn of the below, selecting Yes as required and allowing each to complete the process:
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
The resulting screen should look something like this below – NOTE, I did make a couple of typos while I was attempting this which returned some multiple choice garble if this happens recheck you input instructions:
E:\asus>fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 1.979s]
finished. total time: 1.980s
E:\asus>fastboot erase recovery
erasing 'recovery'...
OKAY [ 1.023s]
finished. total time: 1.025s
E:\asus>fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 39.623s]
finished. total time: 39.624s
E:\asus>fastboot erase boot
erasing 'boot'...
OKAY [ 0.303s]
finished. total time: 0.304s
E:\asus>fastboot erase misc
erasing 'misc'...
OKAY [ 0.602s]
finished. total time: 0.603s
E:\asus>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 1.459s]
finished. total time: 1.460s
fastboot -i 0x0B05 flash system c:\adb\TF700T\blob - depending where you stored your blob, also this was the first time that I saw the loading bar appear on my tablet.
It will now go through the process of reinstalling your Android stock ROM and you should see the something similar to the following:
E:\asus>fastboot -i 0x0B05 flash system e:\asus\blob
erasing 'system'...
OKAY [ 1.731s]
sending 'system' (800935 KB)...
OKAY [134.276s]
writing 'system'...
OKAY [131.640s]
finished. total time: 267.649s
fastboot -i 0x0B05 reboot
E:\asus>fastboot -i 0x0B05 reboot
rebooting...
finished. total time: 0.020s
E:\asus>
I disconnected and rebooted My Asus TF700T and I now have a fully functioning Tablet with a stock ROM.
It has been reported that after completing this you may have some issues getting back get into recovery, hitting RCK and getting the dreaded dead Android (with a red triangle with an exclamation point in the middle). I have not attempted this but have been led to believe that flashing TWRP 2.7.0.1 via Fastboot works.
All acknowledgement and appreciation for this method should go to Buster99, a Senior Member of XDA Developers
http://forum.xda-developers.com/showthread.php?t=2179759&page=2
And to Snoop05, also a Senior Member of XDA Developers for the awesome ADB/Fastboot/Driver tool.
http://forum.xda- developers.com/showthread.php?t=2588979
To whom I am most grateful for the return of my tablet to a working state, I hope this works for you. Good Luck.

cannot flash in updater and in fastboot MI-4c

HI experts
at first, i want to get a german rom/language on my Mi4c
UID: 1599425240
MI-4c
MIUI 7.2 | Stable
7.2.4.0(LXKCNDA)
5.1.1 LMY47V
Baseband version: 2.6.c1.2-0322_1437_9b018c9
Kernel version: 3.10.49-perf-gbf282a2f
how i will get this?
i read a lot of threads and try the following, but always i get some errors
Mi PC Suite
Recovery Flash R Flash: Reading device information failed
with Flash i get "Couldn´t flash device"
see Fastboot below: Mi PC Suite -> Window appear with two checkboxes - first Stable version 7.2.4.0 and second checkbox is Beta 6.4.7 -> i chose Beta -> following Error window write me: "Couldn´t flash device"
Updater on Mi4c:
Miui 7.2.4.0 | Stable
Choose update package -> downloaded_rom -> see testet Roms below
getting Info -> Can´t verify update | Couldn´t verify update package
miui_MI4c_6.3.3_2147a654b3_5.1.zip
miui_MI4c_V7.1.6.0.LXKCNCK_1debc127a9_5.1.zip
miui_MI4c_V7.0.16.0.LXKCNCI_cba5b6c4a8_5.1.zip
cm-13.0-20160406-UNOFFICIAL-libra.zip
sMiUI_v7_libra_6.3.24_SPU8SV.zip
no files found in:
libra_images_V7.0.6.0.LXKCNCI_20150917.0000.1_5.1_cn
libra_images_6.4.7_20160322.0000.17_5.1_cn
other method -> fastboot with PC Suite (i always take test it with command line - also error):
shutdown the MI-4c -> hold Power and Volumne down button -> come to rabbit Fastboot -> connect to PC (Win 7, 64 bit) running Mi PC Suite -> Window appear with to checkboxes - first Stable version 7.2.4.0 and second checkbox is Beta 6.4.7 -> i chose Beta -> following Error window write me: "Couldn´t flash device"
then i try to flash the stable version - the same error - what happend?????
What can i do?
thanks a lot
bye Peter

now i flash a global rom from the seller, but the error sy the same - also locked device
testet fastboot rom: Xiaomi_Mi4C_libra_images_V7.0.4.0.LXKCNCI_20150826.0000.7_5.1_Lang_K_151001
with this guide:
Steps:
1. download the phone driver from this link:
2.install the driver to your PC.
3.turn off your phone,press volume download and power button at the same time until you enter fastboot mode.
4.double click "MI4c_Flash_click_me.bat" to run the flashing tool.
5.connect your phone to PC,the flashing will be processing automatic.
6.after flashing success,reboot your phone.
come to the error, see attached

zahlner said:
now i flash a global rom from the seller, but the error sy the same - also locked device
testet fastboot rom: Xiaomi_Mi4C_libra_images_V7.0.4.0.LXKCNCI_20150826.0000.7_5.1_Lang_K_151001
with this guide:
Steps:
1. download the phone driver from this link:
2.install the driver to your PC.
3.turn off your phone,press volume download and power button at the same time until you enter fastboot mode.
4.double click "MI4c_Flash_click_me.bat" to run the flashing tool.
5.connect your phone to PC,the flashing will be processing automatic.
6.after flashing success,reboot your phone.
come to the error, see attached
Click to expand...
Click to collapse
I don't understand what do you want to do? Install a custom ROM?? If you want this first you need to unlock the bootloader for procedure.. Let me know
Enviado desde mi Mi-4c mediante Tapatalk

Yes i want. How i unlock bootloader?

i try this methode https://youtu.be/ZkBLrn0Dzt4 methode to unlock the bootloader, but i get following error:
Quote:
C:\fastboot>fastboot devices
8c718fed fastboot
C:\fastboot>fastboot oem edl
...
OKAY [ 0.001s]
finished. total time: 0.004s
C:\fastboot>fastboot oem unlock bootloader
...
FAILED (remote: Token verification failed, reboot the device)
finished. total time: 0.011s
C:\fastboot>fastboot oem unlock bootloader
...
FAILED (remote: Token verification failed, reboot the device)
finished. total time: 0.014s
C:\fastboot>fastboot oem unlock bootloader
...
FAILED (remote: Token verification failed, reboot the device)
finished. total time: 0.017s

[Guide] Unlock Bootloader, Get Root and Flash TWRP Recovery

Warning: This guide is a WiP and is NOT complete. DO NOT FOLLOW THIS GUIDE UNTIL THIS MESSAGE IS REMOVED.
You will require ADB and Fastboot installed on your computer.
First you will need to send a private message to the_lazer with your IMEI and Serial Number and they will give you a key to unlock the bootloader.
Wherever you see KEY in this guide replace that with the key you got given.
Second you will need to download Magisk from here, rename that file to
Code:
magisk.zip
Then download the TWRP.img from here.
If the touch screen doesn't work on TWRP then press the power button so the screen sleeps and then press it again so it wakes up and it should work.
Make sure your device has "Enable OEM Bootloader Unlocking" enabled in settings.
Plug your device into your computer and turn the device off.
Hold the power and volume up buttons, if it has a menu where reboot to bootloader or fastboot is a option then do that.
Once in fastboot mode on your computer run:
Code:
fastboot oem key KEY
fastboot oem unlock
Press the volume up button on the phone and it should unlock successfuly.
Once that is done you will need to run:
Code:
fastboot boot TWRP.img
Note that you should NOT flash twrp yet as it will give "red state" error and prevent your device from booting.
Then once in TWRP if it asks for a password then click cancel. If that doesn't work then press the power button and then press it again so the screen sleeps and wakes up then swipe to unlock and click cancel again.
Swipe to allow modifications then click Advanced and then ADB Sideload and swipe.
Next run
Code:
adb sideload magisk.zip
and it will flash magisk.
Magisk will provide root and patch the bootloader so it will still boot past the "orange state" screen.
Next go back twice and click Reboot and then Bootloader.
Then on your computer run
Code:
fastboot flash recovery TWRP.img
That will now flash TWRP.
The reason you need to flash TWRP after you have flashed magisk is because magisk is required to patch the bootloader so that it will actualy boot.
Then run
Code:
fastboot reboot
and you should eventualy reboot to android, give it about 30mins to boot just to be safe.
Then install Magisk Manager from
Code:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
.
You should now have a working rooted Nokia 3 which uses Magisk.
TODO: Add troubleshooting section and steps to follow if something goes wrong.

Any feedback? Does anyone want to pm me and try it safely?

JakesDen said:
Any feedback? Does anyone want to pm me and try it safely?
Click to expand...
Click to collapse
Don't worry, then next time someone asks about rooting their Nokia 3 I will be sure to point them to this thread, and I like how you described the process. It's very easy to understand. I already have my phone rooted and i'm sticking with my stock recovery because of updates

redweaver said:
Don't worry, then next time someone asks about rooting their Nokia 3 I will be sure to point them to this thread, and I like how you described the process. It's very easy to understand. I already have my phone rooted and i'm sticking with my stock recovery because of updates
Click to expand...
Click to collapse
Thanks :3

nice guide, did you encounter any crashes like SuperSU or it runs normal without errors?

SkaboXD said:
nice guide, did you encounter any crashes like SuperSU or it runs normal without errors?
Click to expand...
Click to collapse
Runs flawlessly and doesn't crash or bootloop.
However if you enable a magisk module which causes a bootloop then you would have to factory reset the device unless /data is decrypted in which case you can just delete the folder the magisk module is located in. I will add to the guide instructions on how to have a decrypted /data partitionlater.

SkaboXD said:
nice guide, did you encounter any crashes like SuperSU or it runs normal without errors?
Click to expand...
Click to collapse
QUOTE=virenhp;75052054]I have Unlocked bootloader in Nokia 3 TA 1032
I flashed Trwp Successfully but Still Getting Stock Recovery when entered to Recovery Mode. Please Help Me .. How Can I get Twrp Recovery. Thank Yo

virenhp said:
QUOTE=virenhp;75052054]I have Unlocked bootloader in Nokia 3 TA 1032
I flashed Trwp Successfully but Still Getting Stock Recovery when entered to Recovery Mode. Please Help Me .. How Can I get Twrp Recovery. Thank Yo
Click to expand...
Click to collapse
if flashing doesn't work, use this command: fastboot boot recovery.img
You will boot to twrp successfully but you need to do this every time when you want twrp.

I followed your guide step by step but when rebooting after TWRP flash, the phone does not boot into system. No matter how i try to reboot the android logo pop up with orange state and the next thing is TWRP loading. I can boot into bootloader, so i tried flashing magisk and TWRP again, but no success. Any help would be appreciated

I will try this method the next time I get an ota update. Wasn't sure if it was the superSU or the xposed that was causing the errors. After this update i've confirmed it's the SU.
I've never used magisk before. Hope it won't conflict with xposed

I recommend not using SuperSu.
You can however install magisk and then use magisk manager to install a systemless xposed.
Just don't use the official regular xposed or your device won't boot.

redweaver said:
I will try this method the next time I get an ota update. Wasn't sure if it was the superSU or the xposed that was causing the errors. After this update i've confirmed it's the SU.
I've never used magisk before. Hope it won't conflict with xposed
Click to expand...
Click to collapse
I recommend not using SuperSu.
You can however install magisk and then use magisk manager to install a systemless xposed.
Just don't use the official regular xposed or your device won't boot.

Please make sure to quote me so I get notified if you respond.

it's good and easy guide, i got my nokia 3 rooted in 30mins

Send me the adress where i'm sending private messege

Tayyabmadina said:
Send me the adress where i'm sending private messege
Click to expand...
Click to collapse
Just click "New Private Message" and enter "the_lazer" in the "Recipient Username" field.
Or message them from https://forum.xda-developers.com/member.php?u=3665957

Thank you

i did everything like on tutorial but when i finish it. it boot to TWRP

redweaver said:
I will try this method the next time I get an ota update. Wasn't sure if it was the superSU or the xposed that was causing the errors. After this update i've confirmed it's the SU.
I've never used magisk before. Hope it won't conflict with xposed
Click to expand...
Click to collapse
My Nokia3 roadacts:
- Developper mode OK
- Unlocked OK
- Install magisk & TWRP
fastboot boot TWRP.img
downloading 'boot.img'...
OKAY [ 0.406s]
booting...
OKAY [ 0.047s]
finished. total time: 0.484s
adb sideload magisk.zip
Total xfer: 1.59x
fastboot flash recovery TWRP.img
target reported max download size of 134217728 bytes
sending 'recovery' (13916 KB)...
OKAY [ 0.437s]
writing 'recovery'...
OKAY [ 0.734s]
finished. total time: 1.188s
- Install SuperSU
fastboot reboot
rebooting...
finished. total time: 0.016s
fastboot reboot
adb sideload SuperSU-v2.82-201705271822.zip
That's the only way I found to install SuperSU, cause I don't succed to put the zip in my phone: All mounts in TWRP failed : USB (a R1 warning PC appears), internal... I had transfert the zip in the Nokia before doing all but I don't know where it's located when I browse in TWRP.
According to the trace I saw on the phone when I did the adb sideload, SuperSU install and config seems to be OK, but I'm no sure.
When I open a term on the phone, navigate in the filesystem, I can't do su but see a SuperSU path with an install shell that failed...
My 2 problems:
1/ is SuperSU OK ?
2/ I'm block : how to go back to Andoid to execute root checker or SuperSU, always boot on TWRP ?
Need Help.

JBData said:
My Nokia3 roadacts:
- Developper mode OK
- Unlocked OK
- Install magisk & TWRP
fastboot boot TWRP.img
downloading 'boot.img'...
OKAY [ 0.406s]
booting...
OKAY [ 0.047s]
finished. total time: 0.484s
adb sideload magisk.zip
Total xfer: 1.59x
fastboot flash recovery TWRP.img
target reported max download size of 134217728 bytes
sending 'recovery' (13916 KB)...
OKAY [ 0.437s]
writing 'recovery'...
OKAY [ 0.734s]
finished. total time: 1.188s
- Install SuperSU
fastboot reboot
rebooting...
finished. total time: 0.016s
fastboot reboot
adb sideload SuperSU-v2.82-201705271822.zip
That's the only way I found to install SuperSU, cause I don't succed to put the zip in my phone: All mounts in TWRP failed : USB (a R1 warning PC appears), internal... I had transfert the zip in the Nokia before doing all but I don't know where it's located when I browse in TWRP.
According to the trace I saw on the phone when I did the adb sideload, SuperSU install and config seems to be OK, but I'm no sure.
When I open a term on the phone, navigate in the filesystem, I can't do su but see a SuperSU path with an install shell that failed...
My 2 problems:
1/ is SuperSU OK ?
2/ I'm block : how to go back to Andoid to execute root checker or SuperSU, always boot on TWRP ?
Need Help.
Click to expand...
Click to collapse
I haven't used magisk before, but I was under the opinion that you didn't need to sideload or flash supersu once you've sideloaded magisk. Maybe you need to read up on activating root with magisk

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.

Oneplus 6 TWRP boot img return QUALCOMM CrashDump Mode

Hi Guys,
I am pretty good with IT, but a beginner in rooting... so thought following a guide would be good.
I have a Oneplus 6 which has original software, and I followed this guide:
https://oneplus.gadgethacks.com/how-to/root-your-oneplus-6-with-magisk-beginners-guide-0185541/
I used Command prompt as Administrator and the above happend after the below commands:
C:\ADB>fastboot devices
195ce6aa fastboot
C:\ADB>fastboot boot twrp-3.2.1-0-enchilada.img
Sending 'boot.img' (26748 KB) OKAY [ 0.577s]
Booting OKAY [ 0.082s]
Finished. Total time: 0.710s
Result: Step 1 went fine, but in step 2 regarding TWRP it failed after point 8 - the phone rebooted with: 1+ LOGO - Fastboot Mode - and then showed a black screen with "QUALCOMM CrashDump Mode" but no error details.
*****************************
I then looked around and tried this:
https://www.xda-developers.com/how-to-install-twrp/
C:\ADB>fastboot devices
195ce6aa fastboot
C:\ADB>adb reboot bootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: no devices/emulators found
*****************************
I then looked around and tried this:
https://www.xda-developers.com/how-to-install-twrp/
C:\ADB>fastboot devices
195ce6aa fastboot
C:\ADB>fastboot flash recovery twrp-3.2.1-0-enchilada.img
Sending 'recovery' (26748 KB) OKAY [ 0.610s]
Writing 'recovery' FAILED (remote: '(recovery_b) No such partition')
fastboot: error: Command failed
*****************************
I then looked around and tried this:
https://oneplus.gadgethacks.com/how-to/install-twrp-custom-recovery-your-oneplus-6-0185477/
Boot after step 8 into error screen: "QUALCOMM CrashDump Mode"
*****************************
I then looked around and tried this and switched to PowerShell instead:
https://www.the***********.com/install-twrp-recovery-root-oneplus-6/
https://forum.xda-developers.com/oneplus-6/help/oneplus-6-stuck-qualcomm-crashdump-mode-t3863067
https://www.xda-developers.com/official-twrp-oneplus-6-huawei-p20-pro/
PS C:\ADB> fastboot devices
195ce6aa fastboot
PS C:\ADB> fastboot boot twrp-3.3.1-2-enchilada.img
Sending 'boot.img' (28980 KB) OKAY [ 0.625s]
Booting OKAY [ 0.078s]
Finished. Total time: 0.750s
Result: 1+ LOGO - Fastboot Mode screen - nothing happens, screen stay in this 1+ LOGO - Fastboot Mode screen forever without showing the ordinary fastboot menu
*****************************
I then looked around and tried this:
https://forum.xda-developers.com/oneplus-6/help/version-twrp-bluespark-t3865130
PS C:\ADB> fastboot devices
195ce6aa fastboot
PS C:\ADB> fastboot boot twrp-3.2.3-x_blu_spark_v9.91_op6.img
Sending 'boot.img' (28664 KB) OKAY [ 0.617s]
Booting OKAY [ 0.081s]
Finished. Total time: 0.751s
Result: 1+ LOGO - Fastboot Mode screen - nothing happens, screen stay in this 1+ LOGO - Fastboot Mode screen forever without showing the ordinary fastboot menu
*****************************
Seems like TWRP and BLU SPARK does not work properly, but it could be me who are a complete novice... so hope some of you guys have some good advice please?`
Many thanks in advance!

By the way, no "QUALCOMM CrashDump Mode" error shown in BLU SPARK and also not TWRP newer than version twrp-3.2.1-0-enchilada.img - just a black fastboot mode booting screen.

What oos you're running by that time?....
And pls...use latest 109 blu spark twrp...wich is working with Android 10...feels like you are using wrong twrp with wrong android version...
Also 3.2.1 is verrrry old version...

Thank you James,
You are absolutely correct in version 10, because I am using the original OOS for Oneplus 6 which is currently version 10.3.1
I found the latest TWRP 3.3.1-x blu_spark v9.109 using this link: https://github.com/engstk/android_device_oneplus_enchilada/releases
1)
I noticed that there is only a ZIP file available, not any img files to boot on, so can you please advice how I can get this ZIP installed, direct flash or boot via an img?
2)
https://oneplus.gadgethacks.com/how-to/root-your-oneplus-6-with-magisk-beginners-guide-0185541/
According to the guide on the above link, then I read that it is recommended to use Magisk app to hide root status from Google's SafetyNet.
Sorry for the noob question, but does that mean that I can continue to follow the guide and to run on the newest original software ROM currently on my Oneplus 6... so is the bootloader, TWRP, Magisk app or does Magisk Framework ZIP in step 4 to 6 mean it is an actual ROM?
Many thanks in advance!

No that's only a magisk zip file which will give you just root....
---------- Post added at 05:16 PM ---------- Previous post was at 05:15 PM ----------
So, blu spark don't provide img files anymore idk why...but you should try muronofrios latest twrp...it is + - the same twrp...
---------- Post added at 05:56 PM ---------- Previous post was at 05:16 PM ----------
Here is the link to the mauronofrios twrp
I can't upload img file here idk why
Just download Q one 3.3.17
Not the installer(its the same zip)
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3860815

Thank you James,
Besides that the download of the Q 3.3.1-17 img file got my security system to provide a warning of a malicious website with no valid certificate = qc5.androidfilehost.com - then I did get around that, and it worked perfectly with the mauronofrios twrp with both boot and installation!
Unfortunately I messed up afterwards, so I have created this new thread (but want to provide you with a "Thanks!" on this thread now, to keep things separated in 2 threads):
https://forum.xda-developers.com/oneplus-6/help/how-to-install-totally-formatted-t4050637
Thank you so much for your help!