Phone issues after unlocking bootloader? - Honor 6X Questions & Answers

So I recently unlocked the bootloader on my Honor 6x and it is now stuck on the screen saying "Your device has been unlocked and can't be trusted" and the pesky "Your device is booting now message....". I am unable to get into fastboot mode, and so far no chances of booting into eRecovery. Any known fixes?

Do a clean flash of your ROM through dload method

in same situation.. any help pleasee ?
---------- Post added at 02:06 PM ---------- Previous post was at 02:05 PM ----------
but i have access to fastboot..

This also happened to me. I cant get to fastboot and the phone was stuck on "You're device is booting now...".
What I did is I let the phone drain its battery. After draining the battery, I tried to access fastboot mode. Holding down volume button and connecting the USB cable, the phone booted into the erecovery mode instead of fastboot mode. So I did a data wipe. After performing wipes, I tried to boot into fastboot mode again, and it worked. So I flashed the recovery, ramdisk, and kernel images. After which, I flashed the system again in TWRP and it was successful. ? Now my phone boots normally. ?

i have the same problem. i cant boot in fastboot or recovery...

player615 said:
i have the same problem. i cant boot in fastboot or recovery...
Click to expand...
Click to collapse
Try Dload or let it drain of battery. Next plug-in USB when it turns on hold Volume Up and boot into eRecovery.

Related

No FASTBOOT mode or RECOVERY mode

Today I tried to flash a new ROM and basically bricked my Z3. However, I was able to install a stock firmware and got the phone working perfectly again. Problem is, I want to install a new ROM (elsewhere in the forum) but I have lost my recovery mode and fastboot mode. Can anyone explain how I can get them back or install a new one? I tried flashing the TWRP recovery onto the phone but it keeps coming back with an error. My phone is not bootlocked and is rooted. I just want some kind of recovery options. Please help.
Thanks in advance :good:
To flash twrp you must have unlocked bootloader and if you want to flash on locked bootloder download nuts dual recovery.
For fastboot switch off the phone and hold vol up and plug in the usb voila if you see blue led.
---------- Post added at 04:03 PM ---------- Previous post was at 04:02 PM ----------
To flash twrp you must have unlocked bootloader and if you want to flash on locked bootloder download nuts dual recovery.
For fastboot switch off the phone and hold vol up and plug in the usb voila if you see blue led.
darkdevu said:
To flash twrp you must have unlocked bootloader and if you want to flash on locked bootloder download nuts dual recovery.
For fastboot switch off the phone and hold vol up and plug in the usb voila if you see blue led.
---------- Post added at 04:03 PM ---------- Previous post was at 04:02 PM ----------
To flash twrp you must have unlocked bootloader and if you want to flash on locked bootloder download nuts dual recovery.
For fastboot switch off the phone and hold vol up and plug in the usb voila if you see blue led.
Click to expand...
Click to collapse
My bootloader IS unlocked but still can't flash it. Fastboot not working either.
1974darrenh said:
My bootloader IS unlocked but still can't flash it. Fastboot not working either.
Click to expand...
Click to collapse
Try another PC or laptop to flash.
darkdevu said:
Try another PC or laptop to flash.
Click to expand...
Click to collapse
Is it possible to flash a new ROM without a working recovery? Any apps I can use?
I also downloaded TWRP manager and tried to install it but it comes back with an error.

[HONOR 6X BLN-L21] Honor 6X comletely bricked

Hello there,
i had an camera issue on my Honor 6x (EMUI 5 B369), thats why I made a Rollback to EMUI 4(B130). After doing that properly with that files:
http://download-c.huawei.com/download/downloadCenter?downloadId=94070&version=376169&siteCode=de-h From Bxxx to B300 (only contains some .img (See Attachment))
and http://download-c.huawei.com/download/downloadCenter?downloadId=94087&version=376224&siteCode=de-h From B300 to B130 (full Update.app)
After being on EMUI 4, I wanted to dload back to B369, but then I accidentally flashed the B300, which only contained some .img.
Then it went into softbrick mode, so I only was able to boot into fastboot.
To flash anything I unlocked the bootloader. The Device turned off and back on, then wanted to boot to recovery for hard reset.
This is where I am now. I can not boot into any mode. It just turns on and then shows the "Your device has been unlocked and cant be trusted". I tried to go into dload mode, tried recovery, tried fastboot, none of them were working.
When force rebooting it just turns on, vibrates 2 times and shows that "Your device..." screen and "Your device is booting now"
To archieve that it forgets that process to boot into recovery i let the battery drain empty and try again, which partly worked. Now sometimes it doesnt show "Your device is booting now" on the "Your device..." screen, but it shows the three options that are normally shown when turning on with opened bootloader.
But still no success into fastboot etc.
Edit: My phone seems to be not charging anymore, because ist shows that booting stuff, but then turns on and shows the "Your device..."-screen
Is there any way to unbrick my Honor 6X BLN-L21C432?
Greetings, LRX
PS: plss help me
I didn't understood a thing; actually, you have access to fastboot mode or not? And if yes, what's the status of FRP and Phone in fastboot... Lock or unlocked?
Try to go in fastboot mode by pressing the volume down + power on buttons while your phone is connected to a PC USB port. If this shouldn't work, i had read something online that says that there is a chance to flash an image through HiSuite; never tested, so i can't ensure that it'll works... But we'll try to find out a way to unbrick your device
:crying: same problem shows on my mobile if you found any solution please share with me my device also in same state
same here ... my BLN-L21 is bricked. Can't access to recovery, no fastboot, no e-recovery. any connection with PC !
I have disassembled the phone and looking for schematic testpoint but no result for now
---------- Post added at 10:44 AM ---------- Previous post was at 10:41 AM ----------
LRX22G said:
Hello there,
i had an camera issue on my Honor 6x (EMUI 5 B369), thats why I made a Rollback to EMUI 4(B130). After doing that properly with that files:
http://download-c.huawei.com/download/downloadCenter?downloadId=94070&version=376169&siteCode=de-h From Bxxx to B300 (only contains some .img (See Attachment))
and http://download-c.huawei.com/download/downloadCenter?downloadId=94087&version=376224&siteCode=de-h From B300 to B130 (full Update.app)
After being on EMUI 4, I wanted to dload back to B369, but then I accidentally flashed the B300, which only contained some .img.
Then it went into softbrick mode, so I only was able to boot into fastboot.
To flash anything I unlocked the bootloader. The Device turned off and back on, then wanted to boot to recovery for hard reset.
This is where I am now. I can not boot into any mode. It just turns on and then shows the "Your device has been unlocked and cant be trusted". I tried to go into dload mode, tried recovery, tried fastboot, none of them were working.
When force rebooting it just turns on, vibrates 2 times and shows that "Your device..." screen and "Your device is booting now"
To archieve that it forgets that process to boot into recovery i let the battery drain empty and try again, which partly worked. Now sometimes it doesnt show "Your device is booting now" on the "Your device..." screen, but it shows the three options that are normally shown when turning on with opened bootloader.
But still no success into fastboot etc.
Edit: My phone seems to be not charging anymore, because ist shows that booting stuff, but then turns on and shows the "Your device..."-screen
Is there any way to unbrick my Honor 6X BLN-L21C432?
Greetings, LRX
PS: plss help me
Click to expand...
Click to collapse
Do yo have the red light ? and red charging logo before boot ? I have charge my battery yesterday out of phone (to see if out of battery change boot option). And try boot fastboot / recovery / erecovery with plug and replug battery but no success. Still same
Try to boot into fastboot mode. If you disconnected phone battery, connect it again. Unplug the phone from USB cable. When powered off, hold Vol down key (and only hold that key), then plug your phone to your computer (be sure to hold Vol down until you reach fastboot screen).
If you reached fastboot mode, then flash the RECOVERY.img image from B130 to the recovery partition.
If successful, unplug your device, then reboot.
When rebooting, hold Vol Up and Power button until you see the boot warning saying that you're booting to recovery mode or something like that (the screen won't show any other options to boot as a regular boot should, so that will be an important indicator).
If you reach the recovery screen, then try to dload full B130 firmware.
If this fail, try another flashing combinations. I mean:
1- Try dloading another firmware (e.g. the B369 firmware you downloaded) over B130 recovery.
2- If step 1 failed, flash B369 RECOVERY.img, then try to dload B130 package. If this don't work, now try to dload B369.
3- If previous steps failed, try to flash RECOVERY.img from THE DOWNGRADING PACKAGE (the one with few IMGs). After that, dload B130.
If this don't work, is because your soft brick is a real pain in the ass.
Cheers, and good luck.
PS: don't miss your hope. I achieved to recover my bricked phone with FRP locked (FRP doesn't let you flash anything at all), and a warning screen with RED letters, and a big exclamation mark, saying that the phone was not able to boot.
try dloading the correct firmware.dload works most of the time.
there is no way to enter in dload, recovery or fastboot. i try all methods but no luck. please is here any one know that can we access flash IC?
Ounly one possibility is using "testpoint" on motherboard mobile (Huawei USB COM 1.0 port in PC) with DC Phoenix and than HCU (19€). I had the same problem , I have repared it
1. Unbrick tutorial: you can find it on webside dc-unlocker ((ALL new users prevented from posting outside links in their messages)
2. Repair oeminfo and custom.bin tutorial: you can find it on webside hcu-client (ALL new users prevented from posting outside links in their messages)
I have the picture Testpoint Honor 6x BLN-L21.jpg
Send mi private message.
Good luck...

			
				
power off the device hold the vol down connect data cable to pc it will show fastboot then flash twrp then reboot to twrp flash custom rom.
Impossible to reboot to TWRP from fastboot...
- Install russian MultiTool 8
- download rollback package (Android 6, EMUI 4.1, 1.76GB ) then extract dload folder into SD Card and put sd-card in phone
- Connect USB cable to PC, power off phone, keep pressed Vol- then plug USB cable, phone start in Fastboot Mode
- From MultiTool flash Recovery and eRecovery 1.x version
- Power off phone
- Reboot pressing Vol+,Vol-, Power and wait...

Google Pixel Flasher Using QPST

Hello
I have a Google pixel 128 GB device but recently it got bricked after an ota update. Unfortunately my phone is not rooted or unlocked. So I could not do anything under fastboot, also adb is crashed.
So the phone is bricked. But it can be rectified using QPST is edl mode I suppose. But as of now there is no such development for qpst for Google pixel.
But there are many users they face the same issue recently.
Is there any chance of development for it?
you said bootloader ! you mean the phone can boot into bootloader mode ! after that you said edl mode ? i dont understand. please explain. i may help !
*The Phone Goes into Fastboot with no problems.
*In Fastboot Mode if i try to go to Recovery, The Phone Reboots and does not go to the Recovery But it Keeps on Rebooting.
So the Recovery Partition of the Phone might be Corrupted.
So im looking for ways to Flash the Recovery partition with QPST or any other methods.
Fastboot Doesn't Help Because the Bootloader is locked.
senthil19 said:
*The Phone Goes into Fastboot with no problems.
*In Fastboot Mode if i try to go to Recovery, The Phone Reboots and does not go to the Recovery But it Keeps on Rebooting.
So the Recovery Partition of the Phone might be Corrupted.
So im looking for ways to Flash the Recovery partition with QPST or any other methods.
Fastboot Doesn't Help Because the Bootloader is locked.
Click to expand...
Click to collapse
Download factory image, open up the .sh script as text, copy the fastboot commands about wiping and clearing userdata, cache , etc into a terminal using fastboot
Xdevillived666 said:
Download factory image, open up the .sh script as text, copy the fastboot commands about wiping and clearing userdata, cache , etc into a terminal using fastboot
Click to expand...
Click to collapse
I do believe I've tried this to no avail on a Verizon g-2pw4100-022-b (the "b" probably stands for "brickable").
I'm stuck in the same situation:
Power+vol down - bootloader
Bootloader to recovery - boot loop
Bootloader to barcodes - barcodes show
Edit: power on only leads to constant screen flashing unless you hold volume down for bootloader, at which point you can vol up once and power down.
Can't flash a recovery, can't flash an OTA since that requires adb sideload, which is part of recovery, and can't flash a factory image with the bootloader locked, which is only unlocked under development tools.
One thing to note is that in the bootloader screen, both "b/l" and the one below it (radio?) both say "n/a", which leads me to believe the December update from Verizon could be the cause.
Suggestions as to how to proceed are greatly appreciated.
senthil19 said:
Hello
I have a Google pixel 128 GB device but recently it got bricked after an ota update. Unfortunately my phone is not rooted or unlocked. So I could not do anything under fastboot, also adb is crashed.
So the phone is bricked. But it can be rectified using QPST is edl mode I suppose. But as of now there is no such development for qpst for Google pixel.
But there are many users they face the same issue recently.
Is there any chance of development for it?
Click to expand...
Click to collapse
I have a Reddit thread how to activate qpst .
You can also "adb reboot edl" if your PC can recognize your phone at least.
If not, power button and volume up(or down, I don't remember) for at least forty seconds sometimes brings it up
But then you'd need firmware to flash with qpst and I'm not sure how to go about doing that
---------- Post added at 07:44 AM ---------- Previous post was at 07:42 AM ----------
PoXFreak said:
I do believe I've tried this to no avail on a Verizon g-2pw4100-022-b (the "b" probably stands for "brickable").
I'm stuck in the same situation:
Power+vol down - bootloader
Bootloader to recovery - boot loop
Bootloader to barcodes - barcodes show
Edit: power on only leads to constant screen flashing unless you hold volume down for bootloader, at which point you can vol up once and power down.
Can't flash a recovery, can't flash an OTA since that requires adb sideload, which is part of recovery, and can't flash a factory image with the bootloader locked, which is only unlocked under development tools.
One thing to note is that in the bootloader screen, both "b/l" and the one below it (radio?) both say "n/a", which leads me to believe the December update from Verizon could be the cause.
Suggestions as to how to proceed are greatly appreciated.
Click to expand...
Click to collapse
Can you fastboot boot twrp ?
Are there any solutions to enter EDL Mode in google pixel without adb?

Unlocked bootloader, no recov, no system, fastboot not being detected

EDIT: Still open to suggestions, but am going to try the method posted Here and see if this works. (I have been searching forums, but I didn't find this link until after I posted, sorry admins)
So I was screwing around and booting TWRP through fastboot earlier(fastboot boot twrp-etc.etc), and ran the zip to install it in a stupid way(adb sideload, which I wasn't thinking and should have just flashed in fastboot first).
Now my bootloader comes up, but I have no recovery, and for some reason fastboot is not detected by my Windows PC or my Fedora Linux system.
If I turn the phone off and back on, it gives me ERROR: Slot Unbootable: Load Error.
Am I mega-screwed with a hard-brick since Windows and Linux can't even detect the phone in fastboot/bootloader anymore?
I've been researching was to get into the Qualcomm EDL, but can't find many resources in regards to the Pixel 2
Bought this device from a reputable dealer on Swappa, and it turns out the phone is still in warranty with Google, but not sure if it will cover something
that is obviously my own ****-up
Here's a short list of details that I'm going assume anyone who could help will need to know:
Bootloader: Unlocked
Bootloader: Shows up and gives me standard options [Start->Restart Bootloader->Download Mode->Recovery->Barcodes->Power-Off]
Spitting out ERROR: Slot Unbootable: Load Error
System partition: None
Recovery partition: Corrupted/none
Fastboot: Not working at all(was previously working, and still detects my Verizon Pixel if I go into bootloader menu)
Same exact problem Here...
---------- Post added at 04:41 PM ---------- Previous post was at 03:46 PM ----------
FIXED
I fixed it by completely draining the battery by maintaining the power button held with a rubberband. Then when the little red light was flashing I plugged the phone in the pc and after a few seconds the bootloader showed up and my phone was detected.
Optional: When flashing stock with flash-all.bat I was always betting ''archive does not contain xxxx'' and then my phone wouldn't boot. Ultimately I extracted the 20+ files in the zip image file and manually flashed all img files with fastboot, then I relocked the bootloader and now everything is working fine !
emile567 said:
Same exact problem Here...
---------- Post added at 04:41 PM ---------- Previous post was at 03:46 PM ----------
FIXED
I fixed it by completely draining the battery by maintaining the power button held with a rubberband. Then when the little red light was flashing I plugged the phone in the pc and after a few seconds the bootloader showed up and my phone was detected.
Optional: When flashing stock with flash-all.bat I was always betting ''archive does not contain xxxx'' and then my phone wouldn't boot. Ultimately I extracted the 20+ files in the zip image file and manually flashed all img files with fastboot, then I relocked the bootloader and now everything is working fine !
Click to expand...
Click to collapse
You didn't need to drain the battery completely. Just holding the power button for 10seconds is sufficient for the phone to be detected.

No OS Installed!!! Help Please!

I tried to get magisk to work after installing the latest OTA and I did something wrong and had to wipe all the data from the Oneplus recovery menu. Towards the end in TWRP while wiping, I wiped off the OS by mistake. After clicking reboot, it just rebooted to the fastboot menu and when I click 'Go to recovery' on the fastboot menu it just boots back to the fastboot menu. My device is not being detected in powershell when I type in adb devices and it might be because after the first wipe that happened I didnt turn on adb debugging. I do not have twrp and my device is not being detected by my pc in powershell for me to adb push the whole os and twrp and flash them. I am literally freaking my skin off at this moment. Please help me. If I didnt mention any important detail please ask, Im super frightened so I might have missed something.
tl dr: No OS, no TWRP and locked in fastboot. (thanks to null0seven)
prathk said:
I tried to get magisk to work after installing the latest OTA and I did something wrong and had to wipe all the data from the Oneplus recovery menu. Towards the end in TWRP while wiping, I wiped off the OS by mistake. After clicking reboot, it just rebooted to the fastboot menu and when I click 'Go to recovery' on the fastboot menu it just boots back to the fastboot menu. My device is not being detected in powershell when I type in adb devices and it might be because after the first wipe that happened I didnt turn on adb debugging. I do not have twrp and my device is not being detected by my pc in powershell for me to adb push the whole os and twrp and flash them. I am literally freaking my skin off at this moment. Please help me. If I didnt mention any important detail please ask, Im super frightened so I might have missed something.
Click to expand...
Click to collapse
You should be able to use TWRP to reflash the OS. Personally, I would put the device in EDL mode and use the MSM Tool to put the device back to factory stock. Once back to stock, you can get your OTA and then reflash TWRP and root your device once again.
jcsww said:
You should be able to use TWRP to reflash the OS. Personally, I would put the device in EDL mode and use the MSM Tool to put the device back to factory stock. Once back to stock, you can get your OTA and then reflash TWRP and root your device once again.
Click to expand...
Click to collapse
I am not able to use TWRP. In the fastboot menu when I enter the 'Go to Recovery' option it just reboots back to the fastboot menu.
I'm relatively a noob in all this so if there's any other way please mention it.
UPDATE: I am currently downloading the stuffs required for the MSM tool, the download is extremely slow. Will check back once the download is done and I tried it. Thanks for atleast giving me some hope in the time being.
jcsww said:
You should be able to use TWRP to reflash the OS. Personally, I would put the device in EDL mode and use the MSM Tool to put the device back to factory stock. Once back to stock, you can get your OTA and then reflash TWRP and root your device once again.
Click to expand...
Click to collapse
While in the MSM tool after clicking 'Start', I got a 'Sahara Communication Failed' error. What do I do now?
UPDATE: Another problem right now is that after holding the volume up and down buttons simultaneously for a few seconds and inserting the cable to enter EDL mode (it shows as Qualcomm HS-USB QDLoader 9008 in device manager), within a few seconds the phone reboots into the fastboot again.
Sahara error it's not a real error. After that MSM does not finish installing OS?
But first try FastBoot rom :
https://forum.xda-developers.com/on...fastboot-roms-oneplus-7-pro-t3931424#poststop
Choose the one you need. For example i need GM31BA (european version)
null0seven said:
But first try FastBoot rom :
https://forum.xda-developers.com/on...fastboot-roms-oneplus-7-pro-t3931424#poststop
Click to expand...
Click to collapse
This.
---------- Post added at 02:02 PM ---------- Previous post was at 02:00 PM ----------
prathk said:
IAfter clicking reboot, it just rebooted to the fastboot menu and when I click 'Go to recovery' on the fastboot menu it just boots back to the fastboot menu. My device is not being detected in powershell when I type in adb devices and it might be because after the first wipe that happened I didnt turn on adb debugging.
Click to expand...
Click to collapse
adb won't work in fastboot, by definition (only works in OS and TWRP). Fastboot mode is for fastboot (and fastboot does not need debugging to be on). And fastboot is what you want, to flash the stock ROM.
null0seven said:
Sahara error it's not a real error. After that MSM does not finish installing OS?
But first try FastBoot rom :
https://forum.xda-developers.com/on...fastboot-roms-oneplus-7-pro-t3931424#poststop
Choose the one you need. For example i need GM31BA (european version)
Click to expand...
Click to collapse
No, its written waiting for communication with device and the app stops responding. I would attach a screenshot of the error but I myself am not able to try this method again (Check the update in my previous post).
UPDATE: I'm currently downloading the fastboot ROM. Hope it works.
He, prathk,
write that it's locked on Fastboot. NO twrp, no OS. That's why i suggest Fastboot rom, before MSM tool.
---------- Post added at 07:11 PM ---------- Previous post was at 07:06 PM ----------
(it shows as Qualcomm HS-USB QDLoader 9008 in device manager),
this is GOOD. youre phone drivers are corect. Remove the cable from phone.
Do this :
With phone off hold both volume buttons only and plug cable into computer .
Or power off the phone. Press vol. UP, 5to 10 seconds, plug the cable.
Youre problem with MSM tool it's that the phone it's not shut OFF !
null0seven said:
He, prathk,
write that it's locked on Fastboot. NO twrp, no OS. That's why i suggest Fastboot rom, before MSM tool.
---------- Post added at 07:11 PM ---------- Previous post was at 07:06 PM ----------
(it shows as Qualcomm HS-USB QDLoader 9008 in device manager),
this is GOOD. youre phone drivers are corect. Remove the cable from phone.
Do this :
With phone off hold both volume buttons only and plug cable into computer .
Or power off the phone. Press vol. UP, 5to 10 seconds, plug the cable.
Youre problem with MSM tool it's that the phone it's not shut OFF !
Click to expand...
Click to collapse
Thanks for the suggestion in your previous post, I added it.
I tried both the methods and both resulted in 'Sahara Communication Failed'.
And now even on trying both the methods it keeps restarting to the fastboot menu.
If the phone it's not off MSM not working.
Alternatively you can force your OnePlus 7 Pro to boot to EDL mode by the following steps:
Power off the phone.
Plug in the USB cable your computer but do not connect the other end to the phone.
Hold down Volume Up and Volume Down buttons for a few seconds, and plug in the cable while you are continuing to hold them.
You should see the anticipated EDL mode.
As advised before, you need to download the fastboot package made by @mauronofrio
Run the "flash-all-partitions.bat" while in fastboot.
You seemed mebbe confused before, adb and fastboot are different, adb is only to be used either within the rom or while in recovery. Fastboot is to be used while you're in Fastboot mode. It will still let you flash multiple partitions, hence why the fastboot fix should work.
For future reference, the best way to wipe data while leaving the rom intact is "fastboot -w", that will also remove encryption. (The flash-all-partitions batch file will do this too)
As long as you get a result after typing "fastboot devices" then you should be ok.
I flashed the Fastboot ROM as many of you suggested and it worked. Thanks to everyone who helped out and also thanks for correcting my knowledge. I just want to know if I'll still be getting OTA updates as usual or should I manually download it and flash it from now onwards.
prathk said:
I flashed the Fastboot ROM as many of you suggested and it worked. Thanks to everyone who helped out and also thanks for correcting my knowledge. I just want to know if I'll still be getting OTA updates as usual or should I manually download it and flash it from now onwards.
Click to expand...
Click to collapse
If you've flashed the default partitions you should get OTA, if you flash TWRP and root then you'll download the entire new rom, you don't get an OTA option.

Categories

Resources