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).

Pixel Bootloop (Bootloader unlocked)

So I have been trying to flash the Pixel Factory Image, I have used the most recent SDK Platform Tools and I still can't get past the boot loop. I also have tried to flash the TWRP recovery but I am getting this:
Code:
C:\Users\MyName\Documents\Pixel\minimal_adb_fastboot_1.4.3_portable>fastboot flash recovery twrp-3.3.0-0-sailfish.img
target reported max download size of 536870912 bytes
sending 'recovery' (31000 KB)...
OKAY [ 0.828s]
writing 'recovery'...
(bootloader) Flashing active slot "_b"
FAILED (remote: partition [recovery] doesn't exist)
finished. total time: 0.938s
I have even tried but the bootloop is still there:
Code:
PS C:\Users\MyName\Documents\Pixel\minimal_adb_fastboot_1.4.3_portable> ./fastboot boot twrp-3.3.0-0-sailfish.img
downloading 'boot.img'...
OKAY [ 0.727s]
booting...
OKAY [ 1.010s]
finished. total time: 1.740s

There are a couple things wrong here:
Pixels don't have a recovery partition, everything happens in the boot one (root, twrp, custom kernel)
The first command in the first code block you wrote is wrong because the recovery partition is not there. In case you wanna flash a stock boot image, maybe for recover your device faulty kernel/twrp etc, without have to reflash the whole rom, the command should be "fastboot flash boot boot.img"
The command you sent in the second code block (./fastboot boot twrp-3.3.0-0-sailfish.img) in fact is correct because you just boot the twrp image (= no errors).
But when you wanna flash the recovery, you have to boot the twrp img and when it booted you have to flash the twrp.zip that you can download from the official site from the twrp screen, not the .img
Hope this helps

I'll add that you should also use the official platform-tools downloaded from Google. The minimal (and other alternatives) can give you problems when trying to flash.
The latest platform-tools is here. Note that Google hasn't updated the changelog, and the latest version is actually 28.0.3, not 28.0.2.
For TWRP, you need both the latest .img and .zip files from here, and transfer the .zip file to the Pixel. Use the boot command to boot from the .img, then from within the temporarily-booted TWRP install the .zip file.

Magisk working at motorola one vision?

hey guys, any magisk working for this awesome smartphone? i really want this !!!! :fingers-crossed:

i found this tuti but its too vague what letter A or B to place patched magisk img
https://www.getdroidtips.com/root-motorola-one-vision/
Click to expand...
Click to collapse

Amaterasus said:
i found this tuti but its too vague what letter A or B to place patched magisk img
Click to expand...
Click to collapse
Hi. I believe that tutorial is like a general one that's not actually been tested and verified working on one vision. It does work on many devices tho, including my motorola one.
You can use "fastboot getvar all" command to see which slot your on, plus a whole lot more info, or just use "fastboot flash boot" without specify slot to flash your current boot slot.
I unlocked my bootloader yesterday and tried to flash magisk patched boot.img, but it fails. Tried two different versions of fastboot.
Code:
fastboot r27.0.1
----------------
fastboot flash boot m_boot.img
target reported max download size of 535822336 bytes
sending 'boot_b' (33814 KB)...
OKAY [ 0.816s]
writing 'boot_b'...
FAILED (status read failed (Too many links))
finished. total time: 0.971s
fastboot r29.0.0
----------------
fastboot flash boot boot.img
(bootloader) is-logical:boot_b: not found
Sending 'boot_b' (33814 KB) OKAY [ 1.386s]
Writing 'boot_b' FAILED (Status read failed (Too many links))
fastboot: error: Command failed
Flashing stock boot seem to work even tho it says "(bootloader) is-logical:boot_b: not found"
Code:
./fastboot flash boot boot.img
(bootloader) is-logical:boot_b: not found
Sending 'boot_b' (65536 KB) OKAY [ 2.133s]
Writing 'boot_b' OKAY [ 0.636s]
Finished. Total time: 2.882s
I'll see if I can come up with some answers as to why patched boot won't be written to device.

tys0n said:
Hi. I believe that tutorial is like a general one that's not actually been tested and verified working on one vision. It does work on many devices tho, including my motorola one.
You can use "fastboot getvar all" command to see which slot your on, plus a whole lot more info, or just use "fastboot flash boot" without specify slot to flash your current boot slot.
I unlocked my bootloader yesterday and tried to flash magisk patched boot.img, but it fails. Tried two different versions of fastboot.
Code:
fastboot r27.0.1
----------------
fastboot flash boot m_boot.img
target reported max download size of 535822336 bytes
sending 'boot_b' (33814 KB)...
OKAY [ 0.816s]
writing 'boot_b'...
FAILED (status read failed (Too many links))
finished. total time: 0.971s
fastboot r29.0.0
----------------
fastboot flash boot boot.img
(bootloader) is-logical:boot_b: not found
Sending 'boot_b' (33814 KB) OKAY [ 1.386s]
Writing 'boot_b' FAILED (Status read failed (Too many links))
fastboot: error: Command failed
Flashing stock boot seem to work even tho it says "(bootloader) is-logical:boot_b: not found"
Code:
./fastboot flash boot boot.img
(bootloader) is-logical:boot_b: not found
Sending 'boot_b' (65536 KB) OKAY [ 2.133s]
Writing 'boot_b' OKAY [ 0.636s]
Finished. Total time: 2.882s
I'll see if I can come up with some answers as to why patched boot won't be written to device.
Click to expand...
Click to collapse
I also owns a motorola one too, i menaged to install magisk by patching magisk into motorola one, extracted patched boot.img and installed full stock room with patched boot.img, magisk working perfect, tried the same with motorola one vision but no sucess, it isntall flawesly but magisk stay as before, not abble to install or so.
obs: tried installing magisk into motorola one with windows 10 and no sucess, changed computer and tried with windows 7, worked.
commands used at motorola one
fastboot flash oem oem.img
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot reboot

Amaterasus said:
I also owns a motorola one too, i menaged to install magisk by patching magisk into motorola one, extracted patched boot.img and installed full stock room with patched boot.img, magisk working perfect, tried the same with motorola one vision but no sucess, it isntall flawesly but magisk stay as before, not abble to install or so.
obs: tried installing magisk into motorola one with windows 10 and no sucess, changed computer and tried with windows 7, worked.
commands used at motorola one
fastboot flash oem oem.img
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot reboot
Click to expand...
Click to collapse
Yes, Magisk works fine on "deen". So you're saying you got a patched boot.img to flash on Moto one vision (kane), but no root after open magisk manager to complete the process?

tys0n said:
Yes, Magisk works fine on "deen". So you're saying you got a patched boot.img to flash on Moto one vision (kane), but no root after open magisk manager to complete the process?
Click to expand...
Click to collapse
Exactly!
the whole process i made at motorola one i did with vision, but magisk does not install.

Amaterasus said:
Exactly!
the whole process i made at motorola one i did with vision, but magisk does not install.
Click to expand...
Click to collapse
I'll be damned. I always get some kind of error trying to flash it.
Flashing full stock worked fine tho, so it's not related to drivers, fastboot version or anything like that.

tys0n said:
I'll be damned. I always get some kind of error trying to flash it.
Flashing full stock worked fine tho, so it's not related to drivers, fastboot version or anything like that.
Click to expand...
Click to collapse
odd, and we also cannot use temporary TWRP to install magisk too , remote failure. recovery.img does not pass to boot recovery =/

Amaterasus said:
odd, and we also cannot use temporary TWRP to install magisk too , remote failure. recovery.img does not pass to boot recovery =/
Click to expand...
Click to collapse
There's TWRP for One Vision?
Sent from my Xperia XZ3.

tys0n said:
There's TWRP for One Vision?
Sent from my Xperia XZ3.
Click to expand...
Click to collapse
nope, just for motorola one power. But worked at moto one

Amaterasus said:
nope, just for motorola one power. But worked at moto one
Click to expand...
Click to collapse
Hmm, you're sure you didn't use twrp for deen? There's no way that moto one power recovery would work on moto one.
Even less on one vision since power is built on qualcomm soc, and vision is exynos soc.

hmm what could we do to improve development for magisk/twrp?

tys0n said:
Hmm, you're sure you didn't use twrp for deen? There's no way that moto one power recovery would work on moto one.
Even less on one vision since power is built on qualcomm soc, and vision is exynos soc.
Click to expand...
Click to collapse
you're right, its deen version... chef

TheMellowOne said:
hmm what could we do to improve development for magisk/twrp?
Click to expand...
Click to collapse
i wanna know the same

I guess we'll have to wait and hope that someone who knows developing buys this device. Afaik it's not even released in all regions yet.
Let's see what happens when it gets released in India 20/6.
At least kernel sources is out.
https://github.com/MotorolaMobilityLLC/kernel-slsi/releases/tag/MMI-PSA29.97-13-9
Skickat från min motorola one vision

tys0n said:
I guess we'll have to wait and hope that someone who knows developing buys this device. Afaik it's not even released in all regions yet.
Let's see what happens when it gets released in India 20/6.
At least kernel sources is out.
https://github.com/MotorolaMobilityLLC/kernel-slsi/releases/tag/MMI-PSA29.97-13-9
Skickat från min motorola one vision
Click to expand...
Click to collapse
Yeah there sure are some great devs from India lets hope they join us.

no succes
Interesting, Slot A for me is empty, and i cant flash anything to it even stock boot.img
so i tried B but it ended almost the same..
But bit different error code : Failed (status read(No such device))
So i try to boot it only- for modified boot -
PC: FAILED(remote failure)
Mobile console: (something like) not verified
when i tried boot stock img error code:
Failed (status read(No such device))
But device started booting and lagged on Android one screen.
the modified .img is also 2x smaller than normal boot .img
I guess better compression, but.. Im not sure

Bricked One plus 6 [no software workd] [Help post]

My one plus 6 device suddenly bricked without any sign. Shows only boot loader screen. I can reach recovery mood. I wiped all data (I select "erase everything(Music, pics, etc). Then I tried MSM tool (Run as administrator). After complete download it reboot again and wait for 1/2 min. It gose again to boot loop. Then I tried fastboot method. It said "failed to load 'images.zip': Not enough space". I try to wipe data by command "fastboot erase userdata". It said "FAILED (remote: Erase is not allowed in Lock State)". Also run "flash-all.bat" and it said "FAILED (remote: Flashing is not allowed in Lock State)". Nothing happen on my phone screen. Typed "fastboot continue" and it goes to boot loop. Now I stacked in boot loop screen. What should i do now??

you can go into recovery mod that means your phone is not brick.should you try to use fastboot rom?

soihuvuontrang said:
you can go into recovery mod that means your phone is not brick.should you try to use fastboot rom?
Click to expand...
Click to collapse
of course i tried that method. Download latest OOS and adb - platform tools v28.0.0. pest all into OSS file after unzip. I went to fastboot recovery mood. Run "flash-all.bat" and it said "FAILED (remote: Flashing is not allowed in Lock State)". Nothing happen on mobile screen. (NB: when I type command "fastboot devices" it can recognize my device).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

zobayer.a.m said:
of course i tried that method. Download latest OOS and adb - platform tools v28.0.0. pest all into OSS file after unzip. I went to fastboot recovery mood. Run "flash-all.bat" and it said "FAILED (remote: Flashing is not allowed in Lock State)". Nothing happen on mobile screen. (NB: when I type command "fastboot devices" it can recognize my device).
Click to expand...
Click to collapse
Of course You can't flash anything in fastboot nor in recovery...when you fleshed with msm download tool first time you've LOCKED YOUR BOOTLOADER...SO NO MORE FASTBOOT AND RECOVERY FLASHES...TRY WITH MSM TOOL AGAIN...AND DON'T CHANGE ANYTHING...OR UNLOCK YOUR BOOTLOADER AGAIN...YOU CAN READ HOW BASED ON WHAT OOS VERSION IS YOU ON. READ ABOUT IT. AND REMEMBER WHEN IT SAYS LOCKED STATE AND CAN'T FLASH IN FASTBOOT IT MEANS YOUR BOOTLOADER IS LOCKED...

James Blode said:
Of course You can't flash anything in fastboot nor in recovery...when you fleshed with msm download tool first time you've LOCKED YOUR BOOTLOADER...SO NO MORE FASTBOOT AND RECOVERY FLASHES...TRY WITH MSM TOOL AGAIN...AND DON'T CHANGE ANYTHING...OR UNLOCK YOUR BOOTLOADER AGAIN...YOU CAN READ HOW BASED ON WHAT OOS VERSION IS YOU ON. READ ABOUT IT. AND REMEMBER WHEN IT SAYS LOCKED STATE AND CAN'T FLASH IN FASTBOOT IT MEANS YOUR BOOTLOADER IS LOCKED...
Click to expand...
Click to collapse
distinguish beetwen Msm tool and fastboot rom(https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665)
your phone isnot brick,it boot into fastboot mood,you can you fastboot rom (link above). goodluck!

soihuvuontrang said:
distinguish beetwen Msm tool and fastboot rom(https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665)
your phone isnot brick,it boot into fastboot mood,you can you fastboot rom (link above). goodluck!
Click to expand...
Click to collapse
Unfortunately my boot loader is locked. This will not work. I tried it also

James Blode said:
Of course You can't flash anything in fastboot nor in recovery...when you fleshed with msm download tool first time you've LOCKED YOUR BOOTLOADER...SO NO MORE FASTBOOT AND RECOVERY FLASHES...TRY WITH MSM TOOL AGAIN...AND DON'T CHANGE ANYTHING...OR UNLOCK YOUR BOOTLOADER AGAIN...YOU CAN READ HOW BASED ON WHAT OOS VERSION IS YOU ON. READ ABOUT IT. AND REMEMBER WHEN IT SAYS LOCKED STATE AND CAN'T FLASH IN FASTBOOT IT MEANS YOUR BOOTLOADER IS LOCKED...
Click to expand...
Click to collapse
Ok i understand. I tried MSM tool also. After connect my phone with PC this software show connected status. After hit start it start to update. All process work perfectly fine and goes to completed status (text in MSM tool become green). My phone boot up and 1 or 2 min later it shows welcome screen without any touch response. Touch do not work (though touch was ok). After a few second my phone reboot again and stuck into bool loop again. I tried "enchilada_22_O.09_180517", "ANDROID+9+OOS+9.0.8+enchilada_22_O.33_190801_repack", "ANDROID+10+OOS+10.3.2+enchilada_22_J.44_200222". All MSM tools ended up with same result

Are you not able to unlock bootloader via fastboot and then flash a fastboot ROM?

zobayer.a.m said:
Ok i understand. I tried MSM tool also. After connect my phone with PC this software show connected status. After hit start it start to update. All process work perfectly fine and goes to completed status (text in MSM tool become green). My phone boot up and 1 or 2 min later it shows welcome screen without any touch response. Touch do not work (though touch was ok). After a few second my phone reboot again and stuck into bool loop again. I tried "enchilada_22_O.09_180517", "ANDROID+9+OOS+9.0.8+enchilada_22_O.33_190801_repack", "ANDROID+10+OOS+10.3.2+enchilada_22_J.44_200222". All MSM tools ended up with same result
Click to expand...
Click to collapse
Ok...i think you haven't tried full stock firmware which is msmdonwload tool but with 5.1.6 firmware...or you tried it?that might change everything...
Plus if that didn't worked as well...you should search for oneplus 6 fastboot roms here in xda...mauronofrio has a dedicated thread for it...search oneplus 6 fastboot rom on google and you should see an xda thread...go there download latest 10.3.3 and read all the instructions CAREFULLY...it might help you...try it and give us a feedback...

°Washy said:
Are you not able to unlock bootloader via fastboot and then flash a fastboot ROM?
Click to expand...
Click to collapse
Yes i tried it also. Download fastboot rom and copy all file to adb - platform tools v28.0.0. After clicking all-flash.bat it continuing some work and at last says "FAILED (remote: Flashing is not allowed in Lock State)"

James Blode said:
Ok...i think you haven't tried full stock firmware which is msmdonwload tool but with 5.1.6 firmware...or you tried it?that might change everything...
Plus if that didn't worked as well...you should search for oneplus 6 fastboot roms here in xda...mauronofrio has a dedicated thread for it...search oneplus 6 fastboot rom on google and you should see an xda thread...go there download latest 10.3.3 and read all the instructions CAREFULLY...it might help you...try it and give us a feedback...
Click to expand...
Click to collapse
Yes i tried it also. Download fastboot rom (9.0.9-OnePlus6Oxygen_22_OTA_034_all_1909112343_dd26-FASTBOOT) and copy all file to adb - platform tools v28.0.0. After clicking all-flash.bat it continuing some work and at last says "FAILED (remote: Flashing is not allowed in Lock State)"
I also do some nonseance work. I tried "MsmDownloadToolV4.0InternationalVersionOxygenOS5.1.5" and then enchilada_22_O.09_180517 2 times, later on "ANDROID+10+OOS+10.3.0+enchilada_22_J.42_191214". It worked!! My phone showing welcome screen. Every things seems ok. But i a few min latter realize that none of phone sensor working. So i decided switch other OOS. but 1st i unlock boot loaded. Use "fulldowngrade_wipe_MSM_17819_181025_2315_user_MP1_release.zip" role back pack via local OTA update. But its not working. stack in boot loop. Use fastboot rom "9.0.9-OnePlus6Oxygen_22_OTA_034_all_1909112343_dd26-FASTBOOT.zip". Same this goes there. stuck in boot loop. how can i get my phone sensor worked or Is there any way to role back?

zobayer.a.m said:
Yes i tried it also. Download fastboot rom (9.0.9-OnePlus6Oxygen_22_OTA_034_all_1909112343_dd26-FASTBOOT) and copy all file to adb - platform tools v28.0.0. After clicking all-flash.bat it continuing some work and at last says "FAILED (remote: Flashing is not allowed in Lock State)"
I also do some nonseance work. I tried "MsmDownloadToolV4.0InternationalVersionOxygenOS5.1.5" and then enchilada_22_O.09_180517 2 times, later on "ANDROID+10+OOS+10.3.0+enchilada_22_J.42_191214". It worked!! My phone showing welcome screen. Every things seems ok. But i a few min latter realize that none of phone sensor working. So i decided switch other OOS. but 1st i unlock boot loaded. Use "fulldowngrade_wipe_MSM_17819_181025_2315_user_MP1_release.zip" role back pack via local OTA update. But its not working. stack in boot loop. Use fastboot rom "9.0.9-OnePlus6Oxygen_22_OTA_034_all_1909112343_dd26-FASTBOOT.zip". Same this goes there. stuck in boot loop. how can i get my phone sensor worked or Is there any way to role back?
Click to expand...
Click to collapse
Did you switch on "unlock bootloader" under developer options? It could be the reason for bootloop after MSm flash.

James Blode said:
Ok...i think you haven't tried full stock firmware which is msmdonwload tool but with 5.1.6 firmware...or you tried it?that might change everything...
Plus if that didn't worked as well...you should search for oneplus 6 fastboot roms here in xda...mauronofrio has a dedicated thread for it...search oneplus 6 fastboot rom on google and you should see an xda thread...go there download latest 10.3.3 and read all the instructions CAREFULLY...it might help you...try it and give us a feedback...
Click to expand...
Click to collapse
Yes i tried it also. Download fastboot rom and copy all file to adb - platform tools v28.0.0. After clicking all-flash.bat it continuing some work and at last says "FAILED (remote: Flashing is not allowed in Lock State)"
I also do some nonsense work. I flash "MsmDownloadToolV4.0InternationalVersionOxygenOS5.1.5" and flash "enchilada_22_O.09_180517" 2 times and then flash "ANDROID+10+OOS+10.3.0+enchilada_22_J.42_191214.zip". Surprisingly it worked!! I dont know why and how it worked.
But after e few min i realize that none of my phone sensor working. I decided to role back to android 9. I unlock boot loader. Flash "fulldowngrade_wipe_MSM_17819_181025_2315_user_MP1_release" role back pack via local OTA update. But it again goes to boot loop. After that i try fastboot rom "9.0.9-OnePlus6Oxygen_22_OTA_034_all_1909112343_dd26-FASTBOOT". but again goes to boot loop. [N.B all rom i maintained in above were flash successfully]. Is there any way to get back my phone sensor worked or goes to previous version??

zobayer.a.m said:
Yes i tried it also. Download fastboot rom and copy all file to adb - platform tools v28.0.0. After clicking all-flash.bat it continuing some work and at last says "FAILED (remote: Flashing is not allowed in Lock State)"
Click to expand...
Click to collapse
you did not unlock bootbloader.and fastboot rom was completely failed.you should read on forum how to unblock bootloader,root oneplus 6.wish you success!

°Washy said:
Did you switch on "unlock bootloader" under developer options? It could be the reason for bootloop after MSm flash.
Click to expand...
Click to collapse
Negative. When I laslt flas MSM tool oos 10.3.0 boot loader was locked. I unlocked it as normal procedure (under developer opetion
turn on oem, usb debugging and other then go to fastboot mood any type command "fastboot oem unlock").

zobayer.a.m said:
Yes i tried it also. Download fastboot rom and copy all file to adb - platform tools v28.0.0. After clicking all-flash.bat it continuing some work and at last says "FAILED (remote: Flashing is not allowed in Lock State)"
I also do some nonsense work. I flash "MsmDownloadToolV4.0InternationalVersionOxygenOS5.1.5" and flash "enchilada_22_O.09_180517" 2 times and then flash "ANDROID+10+OOS+10.3.0+enchilada_22_J.42_191214.zip". Surprisingly it worked!! I dont know why and how it worked.
But after e few min i realize that none of my phone sensor working. I decided to role back to android 9. I unlock boot loader. Flash "fulldowngrade_wipe_MSM_17819_181025_2315_user_MP1_release" role back pack via local OTA update. But it again goes to boot loop. After that i try fastboot rom "9.0.9-OnePlus6Oxygen_22_OTA_034_all_1909112343_dd26-FASTBOOT". but again goes to boot loop. [N.B all rom i maintained in above were flash successfully]. Is there any way to get back my phone sensor worked or goes to previous version??
Click to expand...
Click to collapse
Flash whatever build you want...and then go to mauronofrios xda page where it has fastboot roms for op6...download the oos version that you have...and there will be one option FLASH ONLY PERSIST(FLASH PERSIST)...flash it via fastboot with oos installed and sensors should work...but for that you have to unlock your bootloader first...
Feels like you've damaged your phones critical partitions....I SAID READ MAURONOFRIOS THREAD CAREFULLY... ESPECIALLY FLASHING INSTRUCTIONS...
Wait here for a minute...

Read this carefully...i said you damaged all your phones CRITICALS...SO WHAT YOU NEED TO DO?
ALSO READ FOR THE SENSOR FLASH THAT I'VE SAID...AND TRY IT...i also had a sensor problem back in the days(touch worked...but no other sensor like proximity or gyro working)...and tried msmtool several times... didn't helped me...but this guys thread helped a lot with that...
Here is the thread also if You can't find it
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665/amp/

zobayer.a.m said:
Yes i tried it also. Download fastboot rom and copy all file to adb - platform tools v28.0.0. After clicking all-flash.bat it continuing some work and at last says "FAILED (remote: Flashing is not allowed in Lock State)"
Click to expand...
Click to collapse
you should use miniADB and fastboot tool to unlock bootbloader using instruction in forum.
fastboot rom,you only run all-flash.bat by clicking on it (not copy all files to adb-platform tool)before run the line" flash-all.bat" you should unzip file images.zip in fastboot rom.

soihuvuontrang said:
you should use miniADB and fastboot tool to unlock bootbloader using instruction in forum.
fastboot rom,you only run all-flash.bat by clicking on it (not copy all files to adb-platform tool)before run the line" flash-all.bat" you should unzip file images.zip in fastboot rom.
Click to expand...
Click to collapse
I do that and click all-flash.bat. All work perfectly on PC CMD command prompt. Successfully finish and it seems like bellow
-----
sending sparse 'vendor' 1/2 (504897 KB)...
OKAY [ 12.021s]
writing 'vendor' 1/2...
OKAY [ 0.003s]
sending sparse 'vendor' 2/2 (284097 KB)...
OKAY [ 9.762s]
writing 'vendor' 2/2...
OKAY [ 0.003s]
Setting current slot to 'b'...
OKAY [ 18.228s]
erasing 'userdata'...
OKAY [ 0.714s]
sending 'userdata' (5273 KB)...
OKAY [ 0.134s]
writing 'userdata'...
OKAY [ 0.003s]
rebooting...
finished. total time: 129.194s
Press any key to exit...
----
My phone reboot again and nothing actually happen. I stuck in boot loader as like before.

zobayer.a.m said:
I do that and click all-flash.bat. All work perfectly on PC CMD command prompt. Successfully finish and it seems like bellow
-----
sending sparse 'vendor' 1/2 (504897 KB)...
OKAY [ 12.021s]
writing 'vendor' 1/2...
OKAY [ 0.003s]
sending sparse 'vendor' 2/2 (284097 KB)...
OKAY [ 9.762s]
writing 'vendor' 2/2...
OKAY [ 0.003s]
Setting current slot to 'b'...
OKAY [ 18.228s]
erasing 'userdata'...
OKAY [ 0.714s]
sending 'userdata' (5273 KB)...
OKAY [ 0.134s]
writing 'userdata'...
OKAY [ 0.003s]
rebooting...
finished. total time: 129.194s
Press any key to exit...
----
My phone reboot again and nothing actually happen. I stuck in boot loader as like before.
Click to expand...
Click to collapse
it's quite strange.Did you unzipped the file"IMAGES.ZIP"?
---------- Post added at 10:31 AM ---------- Previous post was at 10:27 AM ----------
zobayer.a.m said:
My one plus 6 device suddenly bricked without any sign. Shows only boot loader screen. I can reach recovery mood. I wiped all data (I select "erase everything(Music, pics, etc). Then I tried MSM tool (Run as administrator). After complete download it reboot again and wait for 1/2 min. It gose again to boot loop. Then I tried fastboot method. It said "failed to load 'images.zip': Not enough space". I try to wipe data by command "fastboot erase userdata". It said "FAILED (remote: Erase is not allowed in Lock State)". Also run "flash-all.bat" and it said "FAILED (remote: Flashing is not allowed in Lock State)". Nothing happen on my phone screen. Typed "fastboot continue" and it goes to boot loop. Now I stacked in boot loop screen. What should i do now??
Click to expand...
Click to collapse
error at"images.zip" it means that you have to unzip the file images.zip.

Fastboot boot TWRP doesn't do anything

I'm trying to flash a custom ROM to my Xiaomi Redmi Note 7 Pro (Unlocked Bootloader)
Here's what i've done so far:
1) Entered Fastboot successfully
2) Typed: C...\platform-tools>fastboot flash recovery twrp-3.5.2_9-0-violet.img
And gotten the respone:
Sending 'recovery' (65536 KB) OKAY [ 1.878s]
Writing 'recovery' OKAY [ 0.462s]
Finished. Total time: 2.357s
3) Typed: C...\platform-tools>fastboot boot twrp-3.5.2_9-0-violet.img
And gotten the response:
Sending 'boot.img' (65536 KB) OKAY [ 1.968s]
Booting OKAY [ 0.143s]
Finished. Total time: 2.172s
This is the part where the phone is supposed to be booted into TWRP Custom Recovery, but instead, nothing happens. The phone is still in fastboot. If I try to reboot it and then reboot into recovery, it boots in the default xiaomi recovery. I've tried older versions of twrp.img files, and nothing works. What am I doing wrong?
Thanks in Advance

After flashing the recovery, try typing fastboot reboot recovery instead. That works without fail for me.

camperbh said:
After flashing the recovery, try typing fastboot reboot recovery instead. That works without fail for me.
Click to expand...
Click to collapse
didn't work, it just rebooted my phone

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Well this is what happens when I type it. You could also try booting to system after flashing and type "adb reboot recovery" instead. Or you could just turn off the phone and go into recovery with power+vol up.

camperbh said:
View attachment 5313135
Well this is what happens when I type it. You could also try booting to system after flashing and type "adb reboot recovery" instead. Or you could just turn off the phone and go into recovery with power+vol up.
Click to expand...
Click to collapse
the same message gets displayed to me, but it doesnt work. Even when I do power+vol up, it just reboots and doesnt go to recovery at all

What about the adb method? Does that work?

camperbh said:
What about the adb method? Does that work?
Click to expand...
Click to collapse
nope

That's all the methods I know of. As a last resort, maybe try flashing your stock rom using miflash and repeat the process to see if it works I guess. This is all the help I can offer, sorry.

camperbh said:
That's all the methods I know of. As a last resort, maybe try flashing your stock rom using miflash and repeat the process to see if it works I guess. This is all the help I can offer, sorry.
Click to expand...
Click to collapse
considering that it doesnt go to twrp neither when typing fastboot boot twrp.img nor when i type fastboot reboot recovery nor when rebooting and typing adb reboot recovery, i feel like the issue is that for some reason it cannot flash the twrp.img file. What's weird though is that it says it successfully flashes it. Anyway, thank you for your time, have a good one

Thinking about it, it could also be a driver issue. Try reainstalling your drivers and see if it works.

camperbh said:
Thinking about it, it could also be a driver issue. Try reainstalling your drivers and see if it works.
Click to expand...
Click to collapse
if you're referring to adb drivers, i tried that. It's updated to the latest version

maxccbvoe said:
I'm trying to flash a custom ROM to my Xiaomi Redmi Note 7 Pro (Unlocked Bootloader)
Here's what i've done so far:
1) Entered Fastboot successfully
2) Typed: C...\platform-tools>fastboot flash recovery twrp-3.5.2_9-0-violet.img
And gotten the respone:
Sending 'recovery' (65536 KB) OKAY [ 1.878s]
Writing 'recovery' OKAY [ 0.462s]
Finished. Total time: 2.357s
3) Typed: C...\platform-tools>fastboot boot twrp-3.5.2_9-0-violet.img
And gotten the response:
Sending 'boot.img' (65536 KB) OKAY [ 1.968s]
Booting OKAY [ 0.143s]
Finished. Total time: 2.172s
This is the part where the phone is supposed to be booted into TWRP Custom Recovery, but instead, nothing happens. The phone is still in fastboot. If I try to reboot it and then reboot into recovery, it boots in the default xiaomi recovery. I've tried older versions of twrp.img files, and nothing works. What am I doing wrong?
Thanks in A
Click to expand...
Click to collapse
maxccbvoe said:
I'm trying to flash a custom ROM to my Xiaomi Redmi Note 7 Pro (Unlocked Bootloader)
Here's what i've done so far:
1) Entered Fastboot successfully
2) Typed: C...\platform-tools>fastboot flash recovery twrp-3.5.2_9-0-violet.img
And gotten the respone:
Sending 'recovery' (65536 KB) OKAY [ 1.878s]
Writing 'recovery' OKAY [ 0.462s]
Finished. Total time: 2.357s
3) Typed: C...\platform-tools>fastboot boot twrp-3.5.2_9-0-violet.img
And gotten the response:
Sending 'boot.img' (65536 KB) OKAY [ 1.968s]
Booting OKAY [ 0.143s]
Finished. Total time: 2.172s
This is the part where the phone is supposed to be booted into TWRP Custom Recovery, but instead, nothing happens. The phone is still in fastboot. If I try to reboot it and then reboot into recovery, it boots in the default xiaomi recovery. I've tried older versions of twrp.img files, and nothing works. What am I doing wrong?
Thanks in Advance
Click to expand...
Click to collapse
The first method. I also had a problem after flashing "fastboot flash recovery twrp.img it says successfully but when I try to go to recovery by holding button + volume it cannot proceed it shows black screen but the phone did not get bootloop.
2nd method : I've also tried by using a command " fastboot boot recovery twrp.img " it shows the the command I use is invalid argument . For those who already root their phone Redmi 9t plsss reply about this issue plsss plssss