Related
Greeting,
My nexus 6P, suddenly while having a phone call, got freeze, then rebooted,
Then it keeps rebooting, showing Google “in white” while booting, then off, restart again “by itself”, and same in loop
Started the device into fastboot mode, selected recovery mode
Again same issue, restart, shows Google “in white” then restart again
Tried to follow the instructions, at [GUIDE] Unlock/Root/Flash for Nexus 6P
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Commands and results are here
C:\nexus6p\angler-n4f26o>adb version
Android Debug Bridge version 1.0.36
Revision 0e9850346394-android
C:\nexus6p\angler-n4f26o>adb devices
List of devices attached
<Notice no result returned>
C:\nexus6p\angler-n4f26o>fastboot devices
8XV7N16126000082 fastboot
Please note, I checked those points
ADB and fastboot, downloaded from the link provided in the guide, as well I downloaded it from Google directly
USB driver, updated with latest from google
Java, updated
And of course, I cannot run the device, to do any required configuration on it
And here is a copy of the device details
malibusa said:
Greeting,
My nexus 6P, suddenly while having a phone call, got freeze, then rebooted,
Then it keeps rebooting, showing Google “in white” while booting, then off, restart again “by itself”, and same in loop
Started the device into fastboot mode, selected recovery mode
Again same issue, restart, shows Google “in white” then restart again
Tried to follow the instructions, at [GUIDE] Unlock/Root/Flash for Nexus 6P
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Commands and results are here
C:\nexus6p\angler-n4f26o>adb version
Android Debug Bridge version 1.0.36
Revision 0e9850346394-android
C:\nexus6p\angler-n4f26o>adb devices
List of devices attached
<Notice no result returned>
C:\nexus6p\angler-n4f26o>fastboot devices
8XV7N16126000082 fastboot
Please note, I checked those points
ADB and fastboot, downloaded from the link provided in the guide, as well I downloaded it from Google directly
USB driver, updated with latest from google
Java, updated
And of course, I cannot run the device, to do any required configuration on it
And here is a copy of the device details
Click to expand...
Click to collapse
If you can get into bootloader mode then maybe try fastest flashing things like stock recovery. If you manage to get stock recovery then boot into it and adb sideload a stock OTA from Google Developer website. Other than that I'm not too sure, you might need to contact Google/Huawei if that or anything else doesn't work.
---------- Post added at 08:43 PM ---------- Previous post was at 08:35 PM ----------
Okay, in bootloader mode try flashing the stock bootloader image from their OTA by typing fastboot flash bootloader (drag bootloader image here) then type fastboot reboot-bootloader. After that type fastboot flash radio (drag radio image here). Then type fastboot reboot-bootloader again. After that you can try booting up. If you are somehow able to get into recovery mode whether you can boot up normally or not then you can simply adb sideloading the stock OTA. If nothing I have said gets you into recovery or to boot up the device then you are probably screwed to be honest. Good luck
Hi,
thanks for your reply,
let me make sure, that i understood you clearly,
when i boot into bootloader, and select the recovery mode,
it get rebooted, shows Google “in white” then restart again, and again in same loop exactly as if i booted normally, not into the bootloader
as i read in other posts, i should expect the device to show me a confirmation message, or something similar,
but in my case, nothing at all, restart, and keep restarting
The options i have with bootloader are
1- Start
2- Reboot bootloader
3- Recovery mode
4- Power off
5- Barcodes
malibusa said:
Hi,
thanks for your reply,
let me make sure, that i understood you clearly,
when i boot into bootloader, and select the recovery mode,
it get rebooted, shows Google “in white” then restart again, and again in same loop exactly as if i booted normally, not into the bootloader
as i read in other posts, i should expect the device to show me a confirmation message, or something similar,
but in my case, nothing at all, restart, and keep restarting
The options i have with bootloader are
1- Start
2- Reboot bootloader
3- Recovery mode
4- Power off
5- Barcodes
Click to expand...
Click to collapse
In bootloader mode, not recovery try flashing the bootloader and radio like I said.
Hi... RMA your phone... Contact google or Huawei depending where you bought your N6P.
Check this link. A lot of people seem to be in the same situation at the moment:
https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528
You're in the same boat as a few of us.
Phone is stuck in a bootloop, won't go to recovery. Only boots to fastboot, but your bootloader is locked so you cannot boot/flash any zips, even official ones. That means no recovery access, which means no adb commands. ADB commands *might* be useful to reboot into EDL mode for QFIL flashing, or for wiping partitions. Problem is - if that bootloader wasn't unlocked, it's not going to be. You need to check "Allow OEM unlocking" in settings BEFORE the phone dies, otherwise you will not be able to unlock the bootloader and thereby reflash the phone.
In a perfect world - we could use EDL mode (or something) to use QFIL/MiFlash to completely rewrite the partitions and MAYBE bring the phone back to life, but the stock bootloader does not allow access to EDL. (tried the custom fastboot.exe meant to send the reboot-edl command, didn't work). If someone can figure out the JTAG pins, we might be able to move forward by purposely bricking it to QHUSB_BULK mode.
The thing is - we don't know why the phones started bootlooping in the first place. For some people, a simple cache wipe/factory reset fixes the loop and away they go. HOWEVER, those of us stuck in fastboot mode with a locked bootloader have no way to erase/wipe/format/write partitions, and even if we could, there's no guarantee it was a software issue that caused the loop in the first place.
TL/DR - You have a locked bootloader and cannot access recovery mode, this means you won't be able to flash/wipe/format partitions or images. Best bet is to contact Huawei/Google, but you'll need the original receipt. If that's not an option for you, you're gonna have to wait until the XDA geniuses out there grant us some answers.
Here's a related thread with some deep info:
https://forum.xda-developers.com/nexus-6p/general/qpst-qfil-answer-to-issues-t3455779
singularoctopi said:
You're in the same boat as a few of us.
Phone is stuck in a bootloop, won't go to recovery. Only boots to fastboot, but your bootloader is locked so you cannot boot/flash any zips, even official ones. That means no recovery access, which means no adb commands. ADB commands *might* be useful to reboot into EDL mode for QFIL flashing, or for wiping partitions. Problem is - if that bootloader wasn't unlocked, it's not going to be. You need to check "Allow OEM unlocking" in settings BEFORE the phone dies, otherwise you will not be able to unlock the bootloader and thereby reflash the phone.
In a perfect world - we could use EDL mode (or something) to use QFIL/MiFlash to completely rewrite the partitions and MAYBE bring the phone back to life, but the stock bootloader does not allow access to EDL. (tried the custom fastboot.exe meant to send the reboot-edl command, didn't work). If someone can figure out the JTAG pins, we might be able to move forward by purposely bricking it to QHUSB_BULK mode.
The thing is - we don't know why the phones started bootlooping in the first place. For some people, a simple cache wipe/factory reset fixes the loop and away they go. HOWEVER, those of us stuck in fastboot mode with a locked bootloader have no way to erase/wipe/format/write partitions, and even if we could, there's no guarantee it was a software issue that caused the loop in the first place.
TL/DR - You have a locked bootloader and cannot access recovery mode, this means you won't be able to flash/wipe/format partitions or images. Best bet is to contact Huawei/Google, but you'll need the original receipt. If that's not an option for you, you're gonna have to wait until the XDA geniuses out there grant us some answers.
Here's a related thread with some deep info:
https://forum.xda-developers.com/nexus-6p/general/qpst-qfil-answer-to-issues-t3455779
Click to expand...
Click to collapse
I'm stuck with a black screen and QFIL and XiaoMiFlash won't work. My bootloader is unlocked but I can't get to fastboot. Screen is always black but Quallcomm HS-USB QDLoader 9008 appears in device manager. No red light or vibration when connecting the phone.
vcharette said:
I'm stuck with a black screen and QFIL and XiaoMiFlash won't work. My bootloader is unlocked but I can't get to fastboot. Screen is always black but Quallcomm HS-USB QDLoader 9008 appears in device manager. No red light or vibration when connecting the phone.
Click to expand...
Click to collapse
Have you read this thread: https://forum.xda-developers.com/nexus-6p/general/howtos-debrick-nexus-6p-stuck-edl-9008-t3552838
Maybe try asking here, explaining the things you tried.
Okay, to start with, I've read the other threads about this. I understand the process that *should* work:
1. Power off.
2. Then, press and hold both all Volume Down + Power buttons at the same time until the LG Logo is being displayed on your LG V20.
3. Now, release the keys and press the above combination again however, this time you should wait until recovery mode menu is displayed.
...and I've tried the version where you keep holding the Volume Down button the entire time.
So, yes, I've reached the white screen where it asks you if you want to do a factory reset. I've hit "Yes" to both questions. The problem is that it really does a factory reset then.
---
After unlocking the bootloader, I installed TWRP via fastboot:
adb reboot bootloader
fastboot flash recovery twrp.img
fastboot reboot
...everything went fine.
But I can't get into recovery. And since I'm waiting to have TWRP working so that I can flash root, I can't boot into recovery via an app.
What did I do wrong?
EDIT:
Okay, it looks like TWRP isn't working properly. I tried "adb reboot recovery" and that got me to a dead Android icon and a "No command" message. I have no idea why TWRP isn't working.
Haphim said:
Okay, to start with, I've read the other threads about this. I understand the process that *should* work:
1. Power off.
2. Then, press and hold both all Volume Down + Power buttons at the same time until the LG Logo is being displayed on your LG V20.
3. Now, release the keys and press the above combination again however, this time you should wait until recovery mode menu is displayed.
...and I've tried the version where you keep holding the Volume Down button the entire time.
So, yes, I've reached the white screen where it asks you if you want to do a factory reset. I've hit "Yes" to both questions. The problem is that it really does a factory reset then.
---
After unlocking the bootloader, I installed TWRP via fastboot:
adb reboot bootloader
fastboot flash recovery twrp.img
fastboot reboot
...everything went fine.
But I can't get into recovery. And since I'm waiting to have TWRP working so that I can flash root, I can't boot into recovery via an app.
What did I do wrong?
EDIT:
Okay, it looks like TWRP isn't working properly. I tried "adb reboot recovery" and that got me to a dead Android icon and a "No command" message. I have no idea why TWRP isn't working.
Click to expand...
Click to collapse
to confirm, have you verified you are using the correct TWRP version for your V20?
in this step "fastboot flash recovery twrp.img" is your twrp image that you saved, named twrp.img? If its not, that command won't work correctly.
usually after I flash recovery, when still in the recovery menu, i choose reboot recovery just to make sure it did stick. If it reboots back to itself, then try rebooting the device, and again confirm with manually entering recovery. Maybe overkill but it works for me LOL.
Good luck!
I am in need of big help! I made a critical error after days of trying to navigate the minefields of rooting my device. I have a LG V20 h910 and it is no one-click wonder root. It made me work for it and I finally got it. I loaded LineageOS 14.1 and all was good until the USB OTG cable from my PS4 controller did not register anymore. Damn, that was a let down, and probably led to my careless move of needing to downgrade my TWRP, saw the version I needed, forgot these are device specific, and now I'm stuck in a hard place.
Perhaps the fix is easy, but I have not found the answer after many, many searches...
I had TWRP 3.2.1-2 and needed to downgrade to 3.2.1-0 to try SuperRom (hoping it would have OTG ability). I hastily grabbed the first TWRP 3.2.1-0, threw it on the SD card, wiped everything except internal storage, and flashed the img, and did a reboot. Road block went up.
I tried getting back into recovery, did the PWR and DOWN pressing combo and got the Factory Reset screen, but after clicking "Yes" to both, instead of getting the TWRP screen, I got this error screen (attached).
I tried another idea - hooked it up USB to my PC and tried accessing it via adb/fastboot. I tried multiple drivers for my device, but no adb and no fastboot devices were ever found. The only thing that almost worked was booting phone into FASTBOOT mode by holding DOWN btn and plugging in a USB cable attached to PC. Once in FASTBOOT mode, My PC at least saw the ID for fastboot device. I tried to flash TWRP via fastboot, and it looked like it would happen, but in the end there was no phone screen response to my attempt, and the cmd window on my PC would get stuck and just hang.
Can someone please advise me on how I can fix this problem?
Alright, yesterday I decided to root my phone and install LineageOS through bkores' Axon 7 toolkit, starting from a A2017U on B19. Unlocked the bootloader, rooted, flashed TWRP with no problems. Then, I was a dumbass, and flashed LineageOS without first installing the Universal Bootloader or appropriate modem, which resulted in only being able to access the Fastboot and Recovery menus. Then, I panicked and decided to be an even bigger dumbass and locked the bootloader, which has lead me to this point.
For now, when I try to start the phone "normally," it just cycles through the screen with the blue ZTE logo a few times.
I can't get into EDL mode no matter what I try- I even hacked together a deep flash cable.
I can get into Fastboot mode if I hold down both volume buttons as soon as the ZTE screen pops up. From there, I can select "Start," which just takes me to the first boot loop, "Restart bootloader," which just takes me back into Fastboot, "Recovery mode," which doesn't take me to recovery mode and only puts me in the first boot loop, and "Power off," which does exactly what it says it does.
Device Manager recognizes it as "Android Sooner Single ADB Interface" when it's plugged in Fastboot mode. When not in Fastboot mode, it's recognized as "Handset Diagnostic Interface(DFU) (COM3)," with a model of "QUSB__BULK". Typing "adb devices" into the command line results in no connection in either mode.
Miflash recognizes it as a device when plugged in Fastboot, but any attempts to flash anything results in an error message saying "can not found file flash_all_except_storage.bat".
I've tried pretty much every method to restore it back to a usable state- Axon7Toolkit, MiFlash, axon7tool, all with no luck. All of the other threads on here with people in similar situations seem to be for those with AU2017G models, which hasn't helped. Is there anything I can do, or is it FUBAR?
Thank you in advance for the help.
Americ said:
Alright, yesterday I decided to root my phone and install LineageOS through bkores' Axon 7 toolkit, starting from a A2017U on B19. Unlocked the bootloader, rooted, flashed TWRP with no problems. Then, I was a dumbass, and flashed LineageOS without first installing the Universal Bootloader or appropriate modem, which resulted in only being able to access the Fastboot and Recovery menus. Then, I panicked and decided to be an even bigger dumbass and locked the bootloader, which has lead me to this point.
For now, when I try to start the phone "normally," it just cycles through the screen with the blue ZTE logo a few times.
I can't get into EDL mode no matter what I try- I even hacked together a deep flash cable.
I can get into Fastboot mode if I hold down both volume buttons as soon as the ZTE screen pops up. From there, I can select "Start," which just takes me to the first boot loop, "Restart bootloader," which just takes me back into Fastboot, "Recovery mode," which doesn't take me to recovery mode and only puts me in the first boot loop, and "Power off," which does exactly what it says it does.
Device Manager recognizes it as "Android Sooner Single ADB Interface" when it's plugged in Fastboot mode. When not in Fastboot mode, it's recognized as "Handset Diagnostic Interface(DFU) (COM3)," with a model of "QUSB__BULK". Typing "adb devices" into the command line results in no connection in either mode.
Miflash recognizes it as a device when plugged in Fastboot, but any attempts to flash anything results in an error message saying "can not found file flash_all_except_storage.bat".
I've tried pretty much every method to restore it back to a usable state- Axon7Toolkit, MiFlash, axon7tool, all with no luck. All of the other threads on here with people in similar situations seem to be for those with AU2017G models, which hasn't helped. Is there anything I can do, or is it FUBAR?
Thank you in advance for the help.
Click to expand...
Click to collapse
Ouch, DFU brick. I don't know if you can really do anything from fastboot, maybe unlock the bootloader again? fastboot oem unlock?
I'm wondering how you managed to lock the bootloader without having been warned tgat your phone would become a brick if ANYTHING was out of place (for example a custom recovery, or root) Every guide to relock has a big flashy warning. Did you use the toolkit to relock? If that's the case I'd say @bkores needs to add a warning to the option, maybe something like the "Type yes to continue" kind.
Okay, on to the other stuff. There are two ways to fix a DFU brick: send to ZTE, say it broke itself (Or be honest and pay $80, your choice) or take apart your device (I did this on my A2017G, with a lot of care and patience it works). There might be a solution that uses fastboot, but I'm unsure about flashing a system with fastboot, maybe it is possible though. You want EDL mode to use MiFlash and reinstall a working system on the phone. You are on DFU mode instead of EDL. google "4th category brick repair guide" for the actual guide that you need to use (it's here in XDA but it's faster to find via google). Just a small comment:
To download the stuff easily without having to translate the whole 4PDA page (the guys who made the method are Russians from 4pda), find the "MiFlash and Drivers" link. Open it, you'll find a bunch of spoilers. If you open them all you'll see that the actual files that you need to use have non-cyrillic titles, so download the A2017U_FULL_EDL (like 3 GB), and the MiFlash and drivers. Once you have everything you can simply follow the XDA guide and get it up and running again. Remember to keep the battery plugged to the motherboard though, it won't work otherwise
One of my costumer V20 is now stuck in fastboot.
Whatever I do, it's keep coming back to fastboot mode.
I can enter download mode, and try flash , even using the costum LG up, with upgrade option, partition DL option.
I use Box ( octopus, Z3x ).
I don't know what is wrong with this phone.
it's only going back to fastboot.
Any help is really apreciated.
Thank You.
sing2x said:
One of my costumer V20 is now stuck in fastboot.
Whatever I do, it's keep coming back to fastboot mode.
I can enter download mode, and try flash , even using the costum LG up, with upgrade option, partition DL option.
I use Box ( octopus, Z3x ).
I don't know what is wrong with this phone.
it's only going back to fastboot.
Any help is really apreciated.
Thank You.
Click to expand...
Click to collapse
What does using the "fastboot reboot" cmd do ?
Ak7J4 said:
What does using the "fastboot reboot" cmd do ?
Click to expand...
Click to collapse
It goes back straight to fastboot after LG logo
If you can get into download mode try the 'upgrade' option in lgup
It is stuck in fastboot because your customer tried to root it with lafsploit without unlocking the bootloader.
They have two choices:
1 - Send it to LG to have it repaired.
2 - Wait for me to finish lafsploit 2.0 which will unlock their bootloader, and their phone will just start working.
The partitions that hold the unlock information are not touched when you flash a KDZ, so no amount of flashing is going to fix it.
-- Brian
runningnak3d said:
It is stuck in fastboot because your customer tried to root it with lafsploit without unlocking the bootloader.
They have two choices:
1 - Send it to LG to have it repaired.
2 - Wait for me to finish lafsploit 2.0 which will unlock their bootloader, and their phone will just start working.
The partitions that hold the unlock information are not touched when you flash a KDZ, so no amount of flashing is going to fix it.
-- Brian
Click to expand...
Click to collapse
I think that's what happen, and I don't have any choice except to wait . Returning to LG is not an option.
Thank you very much sir.
did you get to solve this problem also have one stuck in fastboot mode but no download mode
boot loader seem to be lock
thee011 said:
did you get to solve this problem also have one stuck in fastboot mode but no download mode
boot loader seem to be lock
Click to expand...
Click to collapse
If you cant get into download mode by powering off, holding vol up and then plugging into a pc (no power button needed) then you dont have a phone anymore. Unless rooted via dirtysanta which replaces aboot (which provides fastboot), the stock fastboot mode of the h918 can't actually flash anything to the phone which means no unbricking with it; TWRP and download mode are only ways to restore firmware.
I know this is an old thread but my gf has the h918 which is unlocked with twrp Installed, she tried updating magisk from inside magisk and now she's stuck in fastboot mode .The fastboot reboot command does not reboot the phone I even booted into twrp and wiped cache any ideas?
wolf45801 said:
I know this is an old thread but my gf has the h918 which is unlocked with twrp Installed, she tried updating magisk from inside magisk and now she's stuck in fastboot mode .The fastboot reboot command does not reboot the phone I even booted into twrp and wiped cache any ideas?
Click to expand...
Click to collapse
This is a Magisk 20.2 issue there's at two threads in the LGV20 forum on how to recover
Sent from my LG-H910 using XDA Labs
I decided to update my old oneplus 2 to lineageos 15.1 with, but when I tried to flash the file with TWRP, it shows an error. Since the TWRP version I was using was old, I decided to update it first. Keep in mind at this point i had completely wiped my device. So, I downloaded the "twrp-3.2.1-0-kenzo.img" file, as per a youtube video where the dude managed to flash the update successfully, and gave it a go. It showed up as successful. Then i shut the whole device off, and tried to boot back in to recovery to flash the ROM again, but the thing won't boot. It's stuck on this boot screen (with the oneplus logo and 'powered by android' at the bottom), and refuses to go further. I'm stuck in a situation with the phone having no OS, no recovery and the thing won't show up when I connect it to the pc either. Well, the pc makes the 'device connected' notification sound when I plug it in, but nothing shows up on the file explorer or the device manager.
That's my dilemma, please i need help!
Thanks in advance.
inwarse said:
I decided to update my old oneplus 2 to lineageos 15.1 with, but when I tried to flash the file with TWRP, it shows an error. Since the TWRP version I was using was old, I decided to update it first. Keep in mind at this point i had completely wiped my device. So, I downloaded the "twrp-3.2.1-0-kenzo.img" file, as per a youtube video where the dude managed to flash the update successfully, and gave it a go. It showed up as successful. Then i shut the whole device off, and tried to boot back in to recovery to flash the ROM again, but the thing won't boot. It's stuck on this boot screen (with the oneplus logo and 'powered by android' at the bottom), and refuses to go further. I'm stuck in a situation with the phone having no OS, no recovery and the thing won't show up when I connect it to the pc either. Well, the pc makes the 'device connected' notification sound when I plug it in, but nothing shows up on the file explorer or the device manager.
That's my dilemma, please i need help!
Thanks in advance.
Click to expand...
Click to collapse
You downloaded the KENZO (this is not oneplus2! ) TWRP and flashed it on another phone (oneplus2), just normal that it doesn't work and your phone is messed up.
If you can enter fastboot (vol up and power button to boot) you can rescue your phone:
-enter fastboot (vol up + power, while phone is completely off, u can also hold it until you can see "fastboot" written on the screen)
-connect device to a computer with fastboot installed
-type "fastboot oem unlock" into a terminal/cmd window if there is no error, you are good to go, otherwise your bootloader relocked, use this thread to recover
-if your bootloader is still unlocked, download the ONEPLUS2 TWRP IMG, ALWAYS make sure to only flash the roms, kernels, recoveries or zips for YOUR phone otherwise you can really DESTROY your phone!
-now type into terminal/cmd: "fastboot flash recovery *drag the oneplus2 twrp image into terminal/cmd window* and hit enter
-use vol down + power to reboot phone into recovery and wipe all partitions
-Install a ONEPLUS2 ROM of your choice
If something is not clear, use google, because this is most likely basic stuff you have to know when flashing your phone
I can in fact go to fastboot mode by holding the power+volume up keys. When I the phone to my pc it does show a fastboot device (9597b869 fastboot). What do i do from here?
inwarse said:
I can in fact go to fastboot mode by holding the power+volume up keys. When I the phone to my pc it does show a fastboot device (9597b869 fastboot). What do i do from here?
Click to expand...
Click to collapse
As I wrote above (it's a step-by-step guide, u only have to READ )
-connect device to a computer with fastboot installed
-type "fastboot oem unlock" into a terminal/cmd window if there is no error, you are good to go, otherwise your bootloader relocked, use this thread to recover
-if your bootloader is still unlocked, download the ONEPLUS2 TWRP IMG, ALWAYS make sure to only flash the roms, kernels, recoveries or zips for YOUR phone otherwise you can really DESTROY your phone!
-now type into terminal/cmd: "fastboot flash recovery *drag the oneplus2 twrp image into terminal/cmd window* and hit enter
-use vol down + power to reboot phone into recovery and wipe all partitions
-Install a ONEPLUS2 ROM of your choice
wertus33333 said:
As I wrote above (it's a step-by-step guide, u only have to READ )
-connect device to a computer with fastboot installed
-type "fastboot oem unlock" into a terminal/cmd window if there is no error, you are good to go, otherwise your bootloader relocked, use this thread to recover
-if your bootloader is still unlocked, download the ONEPLUS2 TWRP IMG, ALWAYS make sure to only flash the roms, kernels, recoveries or zips for YOUR phone otherwise you can really DESTROY your phone!
-now type into terminal/cmd: "fastboot flash recovery *drag the oneplus2 twrp image into terminal/cmd window* and hit enter
-use vol down + power to reboot phone into recovery and wipe all partitions
-Install a ONEPLUS2 ROM of your choice
Click to expand...
Click to collapse
i tried to follow the guide. but the bootloader, as per you description is relocked. the download link for the driver you provided shows up as empty/no longer available. that's where i'm getting stuck.
P.S, i can enter fastboot mode on the phone via power+volume up.
thanks for the help so far, i can't seem to find much help other than from you so far
Oh, the link is dead, sry for that. try this one (GDrive links are up and working).
inwarse said:
i tried to follow the guide. but the bootloader, as per you description is relocked. the download link for the driver you provided shows up as empty/no longer available. that's where i'm getting stuck.
P.S, i can enter fastboot mode on the phone via power+volume up.
thanks for the help so far, i can't seem to find much help other than from you so far
Click to expand...
Click to collapse
so i managed to get into qualcomm mode, updated the drivers, and ran "MSM8994DownloadTool.exe" in administrator mode. it went as it's outlined in your guide. however, at the end of that process, the phone got stuck in a bootloop (the oneplus logo flashes for a moment and restarts). and can't get into qualcomm mode now, since when i connect the usb to the pc while the phone off, it lights the display (to show that it's charging, i think). any way back from this?
(i can still get into fastboot mode)
inwarse said:
so i managed to get into qualcomm mode, updated the drivers, and ran "MSM8994DownloadTool.exe" in administrator mode. it went as it's outlined in your guide. however, at the end of that process, the phone got stuck in a bootloop (the oneplus logo flashes for a moment and restarts). and can't get into qualcomm mode now, since when i connect the usb to the pc while the phone off, it lights the display (to show that it's charging, i think). any way back from this?
(i can still get into fastboot mode)
Click to expand...
Click to collapse
Do you still have TWRP? If yes go to TWRP and shut down the phone there, afterwards you should be able to enter qualcomm mode again.
otherwise you have to try (i think 10s power button will shut the device completely down). You should be able to enter qualcomm mode if the device is fully shut off (your scenario sounds as if the device is not fully shut off when u connect it to the pc).
Just to go sure: You are absolutely sure to have a oneplus2, are you?
inwarse said:
so i managed to get into qualcomm mode, updated the drivers, and ran "MSM8994DownloadTool.exe" in administrator mode. it went as it's outlined in your guide. however, at the end of that process, the phone got stuck in a bootloop (the oneplus logo flashes for a moment and restarts). and can't get into qualcomm mode now, since when i connect the usb to the pc while the phone off, it lights the display (to show that it's charging, i think). any way back from this?
(i can still get into fastboot mode)
Click to expand...
Click to collapse
Could you resolve the issue?
wertus33333 said:
Could you resolve the issue?
Click to expand...
Click to collapse
nope. kept running into issue after issue, so got dejected and gave up.