Related
Strangest "Bricked" Oneplus One: No recovery, locked OS, can't unlock bootloader
Hi there, I've come in to the possession of the most stubbornly bricked phone that I've ever seen . Bought a OPO off Craigslist, someone cracked the screen and sold it for cheap instead of fixing it. It had been remote wiped but still has some strange difficult software. Posted this problem to the Oneplus Forum but have had no response, thought XDA would be more qualified!
From what I can tell it's a Oneplus One that was sold through a re-seller that replaced all the software on the phone with a high-security version of Android. It's called EncroChat and from their website (encrochat.network or encrochatsure.com) it looks like it removes the recovery from the phone and replaces it with an EncroChat OS (some kind of Cyanogen) that you can boot to in addition to the Android OS.
Well I assume during the remote wipe something went wrong with the software and the phone no longer really functions. It boots up fine but can't connect to Wifi, cellular, not detected when connected to my PC, and has no real apps to speak of. I think most of the device's drivers are missing. Trying to boot to recovery instead boots to their EncroChat OS which is locked behind a password that neither I nor the person I bought it from knows.
I can get to fastboot and my PC will detect the phone then but running the bootloader unlock command doesn't work, the phone just reboots into the locked EncroChat OS. My idea now is to try and hardbrick the phone and then re-do everything on the phone over again, but I can't figure out how to do that. Does anyone else have any ideas?
Contacting EncroChat
Tried contacting EncroChat via email form, twitter, and reddit. No luck! Still stuck with this. I want to try this unbrick guide: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 for hardbricks but I can't get my phone to show as QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008. Any idea how I can do that? This guy seems to have done it:
evronetwork said:
Had one GOOD soft brick in the past, I've used coloros rom(from the Chinese OnePlus One) and fix my phone ...it deleted all media of course but manage to unbrick the phone. Don't ask me how to, it's been a while, google it
It would fix even the most stubborn soft bricks you'll see. Before that I tried everything that was available at the time, no boot as well only fastboot(not even recovery)
Click to expand...
Click to collapse
broccolicakes said:
Tried contacting EncroChat via email form, twitter, and reddit. No luck! Still stuck with this. I want to try this unbrick guide: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 for hardbricks but I can't get my phone to show as QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008. Any idea how I can do that? This guy seems to have done it:
Click to expand...
Click to collapse
For your phone to be recognized in your PC as QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008, you need to install proper drivers. follow this guide
http://www.androidbrick.com/ultimat...agons-are-unbrickable-qhsusb_dload_qpst_qfil/
let me know, if I can help you furthermore.
broccolicakes said:
Tried contacting EncroChat via email form, twitter, and reddit. No luck! Still stuck with this. I want to try this unbrick guide: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 for hardbricks but I can't get my phone to show as QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008. Any idea how I can do that? This guy seems to have done it:
Click to expand...
Click to collapse
Hello dude,
While it was quite some time when I did this unbrick, it was successful ...expect ALL data to be deleted from phone. Google is your friend and I did get all the files from somewhere
You use a special software from the phone, it's coloros software and with provided files it recognise the phone and flash it(2-3 seperate flashes through the software if I remember correctly) - don't worry as long as the phone turns on(mine was turning on but did nothing ...blank, only way to turn it off was to hold power button and hold it(forced turn off))
P.S. The phone wasn't recognised by the OS ...only from this app(cool? ..weird if you ask me - I'm a computer repair tech guy and find this hard to believe if it didn't happen and see it with my own eyes - on the other hand it could be somewhere hidden in the system and recognised like something else so I won't put my hand in fire to verify this )
Thanks!
evronetwork said:
Hello dude,
While it was quite some time when I did this unbrick, it was successful ...expect ALL data to be deleted from phone. Google is your friend and I did get all the files from somewhere
You use a special software from the phone, it's coloros software and with provided files it recognise the phone and flash it(2-3 seperate flashes through the software if I remember correctly) - don't worry as long as the phone turns on(mine was turning on but did nothing ...blank, only way to turn it off was to hold power button and hold it(forced turn off))
P.S. The phone wasn't recognised by the OS ...only from this app(cool? ..weird if you ask me - I'm a computer repair tech guy and find this hard to believe if it didn't happen and see it with my own eyes - on the other hand it could be somewhere hidden in the system and recognised like something else so I won't put my hand in fire to verify this )
Click to expand...
Click to collapse
I figured it out, thanks ! Now I'm stuck with a more minor problem of only having 16gb visible on my 64gb phone. Can't write the userdata_64G image to my phone. Still trying some stuff out and I'll probably just make a new post if I can't get it to work. Thanks again!
broccolicakes said:
I figured it out, thanks ! Now I'm stuck with a more minor problem of only having 16gb visible on my 64gb phone. Can't write the userdata_64G image to my phone. Still trying some stuff out and I'll probably just make a new post if I can't get it to work. Thanks again!
Click to expand...
Click to collapse
I read just the other day that someone needs the 64gb image instead of the 16gb image. You did so well so far, I'm sure you'll figure this one out. Congrats! "Encrochat Beware!"
The mention of the 64gb vs 16gb image is here:
https://forums.oneplus.net/threads/solution-recover-from-hard-bricked-oneplus-one.104943/
He links to the images here:
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
help
broccolicakes said:
I figured it out, thanks ! Now I'm stuck with a more minor problem of only having 16gb visible on my 64gb phone. Can't write the userdata_64G image to my phone. Still trying some stuff out and I'll probably just make a new post if I can't get it to work. Thanks again!
Click to expand...
Click to collapse
Hi broccolicakes, cane you please tell me how you figured it out. Because Am at your same position with an Oneplus x ??
please tell me how you did it????
redi.c said:
Hi broccolicakes, cane you please tell me how you figured it out. Because Am at your same position with an Oneplus x ??
please tell me how you did it????
Click to expand...
Click to collapse
Hi there, sorry in advance this might not be very helpful in your situation. I ended up using the ColorOS repair tool for Oneplus One that I mentioned earlier in the post. It turned out I just didn't have the correct drivers so once I sorted those out the tool was able to bypass all the software and replace everything on the phone so that I could then install my own OS.
I guess the trick would be to find a version of this tool for OneplusX. I'm not sure if there is one available, I haven't looked. Maybe make a separate post about that? The ColorOS tool I'm talking about is from here: http://forum.xda-developers.com/showpost.php?p=55024864&postcount=136 and it just looks directly for the Qualcomm chip and writes to that. I'm not sure where that tool came from, if it made its way out of Oneplus directly or if someone created it afterwards...
LG OPTIMUS ZONE 3 - UNBRICKING GUIDE AND 5.1.1 FACTORY FIRMWARE
This guide has two main objectives: (1) for those with a bricked device who want to restore to the latest factory firmware image; and (2) those who need .kdz Stock 5.1.1 Factory Firmware files.
1. UNBRICKING THE LGVS425PP:
The Verizon LGVS425PP comes, pre-installed on the device, a Windows compatible LG Software Upgrade and Repair utility. When connected via micro USB cable, your device will connect to your PC as an installer and, if you look in your PC directory, you will see an installation directory for the Verizon LG utility. Inside that directory is an .exe file that will install the upgrade/repair utility on your PC. When launched, the utility will auto detect your device, determine if a firmware update is available, and give you an option to repair your device. The repair option will backup your existing userdata (depending on the level of damage to the firmware), download the most recent firmware build for your device, and flash your device to complete stock condition.
Of course, there are those who bricked their devices before being able to install the Verizon LG Upgrade/Repair utility on their PCs. And this utility appears difficult to locate for download on the internet. So, below is a download link for the utility:
DOWNLOAD LINK
https://drive.google.com/drive/folders/0B1Sfod4HWfk2elpGQ3JEbzF4Q0E?usp=sharing
The Verizon LG utility should install the correct USB mobile drivers on your PC. But just in case any driver issues arise, download and install the following LG United Mobile Driver package:
DOWNLOAD LINK
https://drive.google.com/file/d/0B1Sfod4HWfk2RHY2c29mTWg1Rkk/view?usp=sharing
Once the utility is launched, make sure your PC is connected to the internet, put your device in download mode by holding +Volume while connecting your micro USB cable for your PC connection. The utility will then detect your device. Select the REPAIR option and follow the on-screen instructions.
2. STOCK 5.1.1 FACTORY FIRMWARE
The following link is for four software versions of stock 5.1.1 Factory Firmware .kdz files for the Optimus Zone 3: VS425PP2, VS425PP4, VS425PP7 & VS425PP8. Also in the link is the LG United Mobile Driver, the LG-UP flashing tool, and the LG-UP .DLL for the VS425PP. Use these tools at your own risk. I am not responsible for bricked or inoperable devices. I want to thank each and every member in this thread who has tested and reported their findings and issues. That narrows it down greatly. And thanks guys for your patience.
As to rooting the Zone 3, several recent advancements have been achieved and full root access is now possible. Thanks to @Astr4y4L, a comprehensive root package is available for download. http://astrayalslanding.dynu.net:88/Android_Development/ Click on this link and scroll down the the bottom and click the projects link. His package includes precise instructions and alI the files you will need to root this phone. I am currently drafting a concise tutorial for downgrading this phone. Instructions for downgrading can be found within this thread, albeit somewhat scattered. I will update the OP accordingly as further progress is made. Guys, please be sure to thank @Astr4y4L for his unceasing hard work and development on this device. If you like his work and benefit from it, donations are always nice, even if just a couple bucks.
DOWNLOAD LINK
https://drive.google.com/drive/folders/0B1Sfod4HWfk2MUwxNk1oeXJCZEE?usp=sharing
I was attempting to test this on a phone i purchased just yesterday. The about phone section identifies this phone as a vs425pp but under the battery it's identified as a VS425LPP.
The drivers install successfully. The LGUP and LGUP .dll install fine. But when i start LGUP i get an error saying that it can't load the model. looks like i can't attach a picture probably because i'm new but i do have screencaps. I've tried it on my laptop where i do most of my android stuff and on my desktop, same problem on both. According to the LG Mobile Support Tool this one has VS245PP5 installed.
LGUP will start without the phone connected telling me there is no compatible handset attached and then show me a com window. But when i connect the phone it throws the same error and exits.
I must be the biggest idiot, because I cannot figure out how to get into download mode - I power off the device, then while holding the power and volume up key I plug in the usb cord from the Computer. I get the buzzing on the phone, the Verizon logo comes up, and i'm on the home screen. What am I doing wrong?
---------- Post added at 12:55 AM ---------- Previous post was at 12:51 AM ----------
never mind, I got it - it's the volume down and power, not volume up -
---------- Post added at 01:00 AM ---------- Previous post was at 12:55 AM ----------
ok, apparently, that's the restore function, not the download mode - I can't seem to figure out the combo of buttons for the download mode - as above, I go volume up and power then when it vibrates I plug it in?? any suggestions??
wperdigon said:
I must be the biggest idiot, because I cannot figure out how to get into download mode - I power off the device, then while holding the power and volume up key I plug in the usb cord from the Computer. I get the buzzing on the phone, the Verizon logo comes up, and i'm on the home screen. What am I doing wrong?
---------- Post added at 12:55 AM ---------- Previous post was at 12:51 AM ----------
never mind, I got it - it's the volume down and power, not volume up -
---------- Post added at 01:00 AM ---------- Previous post was at 12:55 AM ----------
ok, apparently, that's the restore function, not the download mode - I can't seem to figure out the combo of buttons for the download mode - as above, I go volume up and power then when it vibrates I plug it in?? any suggestions??
Click to expand...
Click to collapse
I just hold volume up and keep it help while connecting the micro USB
Metalchic said:
I was attempting to test this on a phone i purchased just yesterday. The about phone section identifies this phone as a vs425pp but under the battery it's identified as a VS425LPP.
The drivers install successfully. The LGUP and LGUP .dll install fine. But when i start LGUP i get an error saying that it can't load the model. looks like i can't attach a picture probably because i'm new but i do have screencaps. I've tried it on my laptop where i do most of my android stuff and on my desktop, same problem on both. According to the LG Mobile Support Tool this one has VS245PP5 installed.
LGUP will start without the phone connected telling me there is no compatible handset attached and then show me a com window. But when i connect the phone it throws the same error and exits.
Click to expand...
Click to collapse
With your device connected go to Device Manager. Look under Portable Devices, Ports and Com's, etc and look for LGE notations of your device. If you see a yellow question mark by any of the LGE notations, your issue is drivers.
MotoJunkie01 said:
With your device connected go to Device Manager. Look under Portable Devices, Ports and Com's, etc and look for LGE notations of your device. If you see a yellow question mark by any of the LGE notations, your issue is drivers.
Click to expand...
Click to collapse
i have a
Modems > LGE Mobile for VZW USB Modem - Operational
Ports (COM & LPT )> LGE Mobile for VZW USB Serial Port (COM4) - Operational
Portable Devices > LGE Android MTP Device - Code 10 device cannot start
I initially had the 4.1.1 drivers installed from the LG Mobile Support Tool. After uninstalling those and installing the 4.0.4 version from this thread i still have Code 10 error on LGE Android MTP Device.
Metalchic said:
i have a
Modems > LGE Mobile for VZW USB Modem - Operational
Ports (COM & LPT )> LGE Mobile for VZW USB Serial Port (COM4) - Operational
Portable Devices > LGE Android MTP Device - Code 10 device cannot start
I initially had the 4.1.1 drivers installed from the LG Mobile Support Tool. After uninstalling those and installing the 4.0.4 version from this thread i still have Code 10 error on LGE Android MTP Device.
Click to expand...
Click to collapse
Ok I have seen that MTP Device error before. It is not uncommon. Search the forums for a driver resolution. Off top of my head I cannot recall, but I do know there are threads on it.
MotoJunkie01 said:
Ok I have seen that MTP Device error before. It is not uncommon. Search the forums for a driver resolution. Off top of my head I cannot recall, but I do know there are threads on it.
Click to expand...
Click to collapse
The initial solution was to reinstall the drivers, did not work.
Second solution discovered in reference to samsung devices was to delete a registry key called UpperFilters from the WPD section. Did not work.
The third solution i've found involves downloading the Android SDK and installing it.
This last one seems sort of like a nuclear option. But i'm running out of ideas. the MTP and PTP transfer modes install and start correctly when the device is booted normally but when booted into download mode it just goes code 10. I'm working on the third option now but it will take a while to download.
Metalchic said:
The initial solution was to reinstall the drivers, did not work.
Second solution discovered in reference to samsung devices was to delete a registry key called UpperFilters from the WPD section. Did not work.
The third solution i've found involves downloading the Android SDK and installing it.
This last one seems sort of like a nuclear option. But i'm running out of ideas. the MTP and PTP transfer modes install and start correctly when the device is booted normally but when booted into download mode it just goes code 10. I'm working on the third option now but it will take a while to download.
Click to expand...
Click to collapse
Yes that SDK is a bulk of a download and installation. But may be your fix. Very odd I agree
MotoJunkie01 said:
Yes that SDK is a bulk of a download and installation. But may be your fix. Very odd I agree
Click to expand...
Click to collapse
It didn't work. Still code 10. I tried on a third computer, an old Dell laptop running Windows XP. It gave a strange error Code 28 saying something about an invalid service section of the INF. But i think this may be a red herring and actually be caused by Windows Media Player 11 not being installed. I'll have to setup an installation of Windows 7 to try that.
Edit: looks like i'm going to have to give up trying to fix the code 10 error because NONE of the information from google is relevant to this. All the information is for the phone being started normally and being unable to access the MTP file transfer through normal working operation. None of it relates to this "download mode" that LG has implemented. I wish this were easy like my Galaxy Nexus was back in the day.
Metalchic said:
It didn't work. Still code 10. I tried on a third computer, an old Dell laptop running Windows XP. It gave a strange error Code 28 saying something about an invalid service section of the INF. But i think this may be a red herring and actually be caused by Windows Media Player 11 not being installed. I'll have to setup an installation of Windows 7 to try that.
Click to expand...
Click to collapse
OK. Let me know..
Metalchic said:
It didn't work. Still code 10. I tried on a third computer, an old Dell laptop running Windows XP. It gave a strange error Code 28 saying something about an invalid service section of the INF. But i think this may be a red herring and actually be caused by Windows Media Player 11 not being installed. I'll have to setup an installation of Windows 7 to try that.
Edit: looks like i'm going to have to give up trying to fix the code 10 error because NONE of the information from google is relevant to this. All the information is for the phone being started normally and being unable to access the MTP file transfer through normal working operation. None of it relates to this "download mode" that LG has implemented. I wish this were easy like my Galaxy Nexus was back in the day.
Click to expand...
Click to collapse
Yeah tell me about it. The good ol' Nexus days were much simpler. I'm like you....I think its a Red Herring of some sort you are dealing with. Something so obvious and so simple that it is hiding behind a thin wall.
I'm searching right now trying to help too.
Hi MotoJunkie01,
I appreciate you putting together this guide but I have to say that I no further along than everyone else here. Similar to Metalchic I received the "can't load model" error from LGUP. Googling around i found that I was missing the LGUP_common.dll file. Found that and LGUP opened fine and found my device. Tried to flash VS425PP2 kdz got to about 9% and received "Secure device, But Unsecure image" error. And that's as far as i got.
As far as the LG Android MTP driver goes i also receive the code 10 cannot start error but only when the phone is in download mode. Otherwise the driver loads fine when the phone is "booted". I dont know jack about rooting phones and have never done it before. I had this one lying around and thought I'd try it. Hopefully all this helps to narrow down the issue.
roscoemctavish said:
Hi MotoJunkie01,
I appreciate you putting together this guide but I have to say that I no further along than everyone else here. Similar to Metalchic I received the "can't load model" error from LGUP. Googling around i found that I was missing the LGUP_common.dll file. Found that and LGUP opened fine and found my device. Tried to flash VS425PP2 kdz got to about 9% and received "Secure device, But Unsecure image" error. And that's as far as i got.
As far as the LG Android MTP driver goes i also receive the code 10 cannot start error but only when the phone is in download mode. Otherwise the driver loads fine when the phone is "booted". I dont know jack about rooting phones and have never done it before. I had this one lying around and thought I'd try it. Hopefully all this helps to narrow down the issue.
Click to expand...
Click to collapse
Thanks for pointing out the common .dll file. I will edit that in my thread for download. I am not sure on the MTP error. I have two of these Zone 3s lying around and neither gives any type of error on MTP. Almost certainly sounds like a driver related issue though. Im going to uninstall drivers and everything on my end, do factory resets, and reinstall everything and walk back through the process from scratch. See if I can pinpoint the issue.
MotoJunkie01 said:
Thanks for pointing out the common .dll file. I will edit that in my thread for download. I am not sure on the MTP error. I have two of these Zone 3s lying around and neither gives any type of error on MTP. Almost certainly sounds like a driver related issue though. Im going to uninstall drivers and everything on my end, do factory resets, and reinstall everything and walk back through the process from scratch. See if I can pinpoint the issue.
Click to expand...
Click to collapse
like roscoemctavish i was able to grab the LGUP_common.dll file and put it into ..\LG Electronics\LGUP\model\common and then LGUP started detecting my phone. It only takes the kdz file type under the Upgrade selection. But like roscoemctavish i ran into the 'unsecured image secured device' error. Still code 10 on the MTP driver but i don't think it's related to this. Maybe though.
Metalchic said:
like roscoemctavish i was able to grab the LGUP_common.dll file and put it into ..\LG Electronics\LGUP\model\common and then LGUP started detecting my phone. It only takes the kdz file type under the Upgrade selection. But like roscoemctavish i ran into the 'unsecured image secured device' error. Still code 10 on the MTP driver but i don't think it's related to this. Maybe though.
Click to expand...
Click to collapse
So in your instance, did the .kdz file flash for you with no issue or did it stop at some point?
MotoJunkie01 said:
So in your instance, did the .kdz file flash for you with no issue or did it stop at some point?
Click to expand...
Click to collapse
stopped at 9% with the "Secure device, But Unsecure image" error the other guy was having.
Metalchic said:
stopped at 9% with the "Secure device, But Unsecure image" error the other guy was having.
Click to expand...
Click to collapse
OK. So both you guys having the stop at 9% please try this. Rename the VS425PP2 file to the filename VS425PP6. Then flash the .kdz.
For now I'm editing the thread down to unbricking via the Verizon LG utility and I'll give links to the .kdz files. It's back to the drawing board guys. I'm very sorry. Please know that I am working hard on it.
MotoJunkie01 said:
For now I'm editing the thread down to unbricking via the Verizon LG utility and I'll give links to the .kdz files. It's back to the drawing board guys. I'm very sorry. Please know that I am working hard on it.
Click to expand...
Click to collapse
No worries man and I appreciate just having this as a potential option. If it matters I have tried to root my phone with Kingoroot. Of course it fails but the software status has changed to "modified". Current software version is VS425PP5.
I did try changing the filename "VS425PP2_02_ARB00.kdz" to "VS425PP6.kdz" and flashing with the same result (Stops at 9% with unsecure image error). There is a log file in the "\LGUP\model\common\LOG" folder which when opened in notepad produces unreadable text. Let me know if I can provide anything else.
Thanks!
Hi everyone!
Well guys, sorry to bring this subject on thread again (because this forum has a lot of guides to solve this problem).
But I'm without hope with my phone at this moment.
Let me tell you guys my sad story...
I have an Oneplus 6 since december 2018, and never, NEVER, tried to use any modification on my phone.
I am from Brazil (so sorry for my bad english =] ), and here we CANNOT use Oneplus Support services (I've tried but only received the response "sorry I cannot help you on your country"), so because of this, I've decided to never apply any modification to avoid problems.
This week after a simple reboot my OP6 started with "Qualcomm CrashDump" error and my despair begins.
I'm not able to enter on Fastboot Mode. When I try, the systems attempt to boot (the fastboot mode logo appears) and fall down into crash again.
I'm not able to enter on Recovery Mode either. This method shows nothing, only black screen and after some time the crash screen comes again.
I do not have Bootloader unlocked too.
Any suggestion to use TWRP via fastboot.exe or ADB are useless, because I cant make the connection. At least I think that is impossible because the 'adb devices' command does not find the device.
I followed a lot of guides from XDA to solve my problem, including the Mega Unbrick Thread.
I already downloaded at least 8 different versions of msmdownloadtool in consecutive attempts of unbrick my phone. Nothing really helps.
The most weird situation is that msmDownlodTool can finish the proccess with success. The driver installation is working... everything seens OK using the tool but my phone does not revive
Someone have a suggestion for me?
Any suggestion, tool or alternative method is welcome in my actual situation.
Sorry if I posted at wrong local, just tell me and I can fix if necessary.
Thanks in advance to all of you guys.
Did you try msm download tool? If not, nead that thread and good luck
whizeguy said:
Did you try msm download tool? If not, nead that thread and good luck
Click to expand...
Click to collapse
Hi!
Thanks for your reply, but I think you do not read my entire post
As I said, i've already tried at least 8 different versions of msmDownloadTool.
If you have any other suggestion, I'll appreciate.
so you can't boot into fastbootmode anymore?
Had the same problem once before and solved it by flashing the correct twrp by fastboot
EarthquakeXS said:
so you can't boot into fastbootmode anymore?
Had the same problem once before and solved it by flashing the correct twrp by fastboot
Click to expand...
Click to collapse
Yes, I am unable to enter into Fastboot Mode.
When I try, the logo saying "fastboot" appears, but after 4 seconds, the systems stucks on CrashDump error screen again.
That way my PC cannot find my phone with ADB or FASTBOOT commands.
The only tool that works is msmDownloadTool, but even with a success run with that tool, my system does not start and stills under CrashDump error.
I was thinking if exists some version of msmDownloadTool that justs restore the fastboot and unlock bootloader with brute force.
Thats my last hope
hello. heres what u need to do. download miracle kraked version. hold volume+ and - key simultaneously.
go to device manager in pc. look for port expand it and u should see qualcomm Qloader.
now use miracle under qualcomm tab select patch and flash!!
sanaulla jauhar said:
hello. heres what u need to do. download miracle kraked version. hold volume+ and - key simultaneously.
go to device manager in pc. look for port expand it and u should see qualcomm Qloader.
now use miracle under qualcomm tab select patch and flash!!
Click to expand...
Click to collapse
Hi!
Can you please provide some link to this tool?
Thanks for your help!
mikesmarcos said:
Hi everyone!
Well guys, sorry to bring this subject on thread again (because this forum has a lot of guides to solve this problem).
But I'm without hope with my phone at this moment.
Let me tell you guys my sad story...
I have an Oneplus 6 since december 2018, and never, NEVER, tried to use any modification on my phone.
I am from Brazil (so sorry for my bad english =] ), and here we CANNOT use Oneplus Support services (I've tried but only received the response "sorry I cannot help you on your country"), so because of this, I've decided to never apply any modification to avoid problems.
This week after a simple reboot my OP6 started with "Qualcomm CrashDump" error and my despair begins.
I'm not able to enter on Fastboot Mode. When I try, the systems attempt to boot (the fastboot mode logo appears) and fall down into crash again.
I'm not able to enter on Recovery Mode either. This method shows nothing, only black screen and after some time the crash screen comes again.
I do not have Bootloader unlocked too.
Any suggestion to use TWRP via fastboot.exe or ADB are useless, because I cant make the connection. At least I think that is impossible because the 'adb devices' command does not find the device.
I followed a lot of guides from XDA to solve my problem, including the Mega Unbrick Thread.
I already downloaded at least 8 different versions of msmdownloadtool in consecutive attempts of unbrick my phone. Nothing really helps.
The most weird situation is that msmDownlodTool can finish the proccess with success. The driver installation is working... everything seens OK using the tool but my phone does not revive
Someone have a suggestion for me?
Any suggestion, tool or alternative method is welcome in my actual situation.
Sorry if I posted at wrong local, just tell me and I can fix if necessary.
Thanks in advance to all of you guys.
Click to expand...
Click to collapse
Hi there ! I am experiencing a similar issue on the same device. Did you manage to fix it ?
Hi dude are u here ? i will help u
Try this
Rhach1d237 said:
Hi there ! I am experiencing a similar issue on the same device. Did you manage to fix it ?
Click to expand...
Click to collapse
Source is a videotutorial. google oneplus 6 hardbrick and click the video of Max Lee
(it worked for me)
the download takes an awful lot of time
first get your phone into qualcomm download mode by holding down volume up + power button and plug your device in your PC.
(first unzip the hardbrick zip folder) then the oneplus 6 folder and than the .exe file and click 'start' if it detects your phone.
That is flashing every chip and Hydrogen OS 5.whatever.3 but that is not important. Your phone should boot and than you can install Oxygen OS with android 10(thats the other zip folder) using the local upgrade feature.
(make sure to enable google play services after upgrade from hydrogen OS)
Hope it will work for you too if you haven't tried it already.
Sorry for lack of details, but I'm not sure it will help anyway. Feeling pretty bad right now.
T-Mobile Oneplus 7 Pro. 256GB version.
I wanted to go to stock OxygenOS after buying the branded version two weeks ago.
I successfully got T-Mobile to unlock my SIM, and got OnePlus to send me unlock code for my bootloader after a week.
Successfully unlocked via fastboot. Tried several times to flash TWRP and no success using fastboot.
Tried MSM-Downloader from guacamole_21_O.07_190512_repack and successfully held volume both buttons to connect to the PC. MSM-Downloader said it was successfully connected.
I cannot find the exact error message I got from MSM-Downloader, but it said it didn't match plus another error message. At that point, my heart sank.
USB Device Not Recognized keeps popping up on windows again and again, while the connect sound plays. Doesn't matter if I hold down the volume buttons or not.
Can't get into qualcomm EDL mode. My guess is I hosed my boot and now it restarts endlessly when connected to anything at all.
Is this the end of my journey? I did tons of research on the best phone and the best deals available to save money, but looks like I played myself here with lack of caution.
I would suggest following this guide to attempt reflashing of the international firmware (use the androidfilehost download).
If that also fails, you could always just reflash the TMO firmware with this guide.
bmg1001 said:
I would suggest following this guide to attempt reflashing of the international firmware (use the androidfilehost download).
If that also fails, you could always just reflash the TMO firmware with this guide.
Click to expand...
Click to collapse
I cannot get into EDL. Regardless of what buttons I press (I am holding both volume buttons down in excess of 5 seconds) when connecting USB to the phone, Windows makes the "connect" sound endlessly and the driver isn't recognized.
If I can get into EDL, I will definitely try the above.
Do you have the proper drivers installed to use EDL mode?
Also, if you go into the Device Manager, do you see the phone in there? Should pop up as something like "Qualcomm HS-USB 9008" or some variant of that.
bmg1001 said:
Do you have the proper URL installed to use EDL mode?
Also, if you go into the Device Manager, do you see the phone in there? Should pop up as something like "Qualcomm HS-USB 9008" or some variant of that.
Click to expand...
Click to collapse
Ok. I may be making progress thanks to your help but do have some hurdles I can see.
I do see the device when I hook it up to another computer. It shows up as Unknown USB Device (Device Descriptor Request Failed).
When I go to device manager to manually update the driver, and browse to the location I extracted the CAB file into, I see lots of devices to choose from, but the Qualcomm driver cab file list does not show "Qualcomm HS-USB QDLoader 9008" as an option. I see many Qualcomm USB Composite Devices in the list but none I have chosen seem to work (install fails).
Hmm. I know it may be an obvious question, but just to be sure, you're using the cable that came with the device correct?
bmg1001 said:
Hmm. I know it may be an obvious question, but just to be sure, you're using the cable that came with the device correct?
Click to expand...
Click to collapse
Yes, that is correct. Same cable i used to get into fastboot, etc... The original PC I caused the problems with recognized the device differently (showed up as a Qualcomm device) when I got into EDL with it before.
Edit: First event when plugging it into this second PC under device properties:
Device USB\VID_0000&PID_0002\5&3c8d678&0&2 was not migrated due to partial or ambiguous match.
Last Device Instance Id: USB\VID_0000&PID_0000\5&1AE39384&0&2
Class Guid: {36fc9e60-c465-11cf-8056-444553540000}
Location Path:
Migration Rank: 0xF000FFFFFFFFF000
Present: false
Status: 0xC0000719
I just did some googling and found this article. Perhaps you can try the drivers in this guide? They are .exe files so they should be easy to install, but I'm not sure if the other drivers I provided have any OnePlus specific stuff in it, but it's worth a shot.
bmg1001 said:
I just did some googling and found this article. Perhaps you can try the drivers in this guide? They are .exe files so they should be easy to install, but I'm not sure if the other drivers I provided have any OnePlus specific stuff in it, but it's worth a shot.
Click to expand...
Click to collapse
I've already tried the .zip version with no success. I am loath to install an .exe file (don't want to make the problem worse by infecting my PC) but may as well. I will restart and report back. Thank you again for your attention.
If this doesn't bear fruit, I may be SOL, correct?
unluckyoneplus7pro said:
I've already tried the .zip version with no success. I am loath to install an .exe file (don't want to make the problem worse by infecting my PC) but may as well. I will restart and report back. Thank you again for your attention.
If this doesn't bear fruit, I may be SOL, correct?
Click to expand...
Click to collapse
Mmm. The link I gave seems to have been blocked by XDA when I tried to access it from my post. Never had a problem myself with that site, but who knows.
You should be able to ultimately recover the phone though. Perhaps asking in one of the unbrick threads? OnePlus phones are theoretically unbrickable because we have good access to our EDL mode.
bmg1001 said:
Mmm. The link I gave seems to have been blocked by XDA when I tried to access it from my post. Never had a problem myself with that site, but who knows.
You should be able to ultimately recover the phone though. Perhaps asking in one of the unbrick threads? OnePlus phones are theoretically unbrickable because we have good access to our EDL mode.
Click to expand...
Click to collapse
I'll try there next. Can't seem to get any of my windows machines to recognize the thing.
bmg1001 said:
Mmm. The link I gave seems to have been blocked by XDA when I tried to access it from my post. Never had a problem myself with that site, but who knows.
You should be able to ultimately recover the phone though. Perhaps asking in one of the unbrick threads? OnePlus phones are theoretically unbrickable because we have good access to our EDL mode.
Click to expand...
Click to collapse
OK! I found on reddit that if you hold your vol up + down + power for 30 seconds, it will boot back into fastboot, which it did! Holy **** I'm so happy. Haven't even seen if the PC recognizes it but will check now. If it does, I just need to not screw up the conversion to international.
Thank you for your "unbrickable" comment. That gave me hope to not give up.
unluckyoneplus7pro said:
OK! I found on reddit that if you hold your vol up + down + power for 30 seconds, it will boot back into fastboot, which it did! Holy **** I'm so happy. Haven't even seen if the PC recognizes it but will check now. If it does, I just need to not screw up the conversion to international.
Thank you for your "unbrickable" comment. That gave me hope to not give up.
Click to expand...
Click to collapse
I just wanted to share a tip. After you load the msmtool and before you connect your phone with the cable, click the start button, the message will read "waiting for device". Then, as soon as you plug in the cable while holding the p-up and p-down, the msmtool will automatically start. No more rushing to hit the start button before EDL mode times out.
razorshiv said:
I just wanted to share a tip. After you load the msmtool and before you connect your phone with the cable, click the start button, the message will read "waiting for device". Then, as soon as you plug in the cable while holding the p-up and p-down, the msmtool will automatically start. No more rushing to hit the start button before EDL mode times out.
Click to expand...
Click to collapse
That's pretty cool. Makes the whole process much less stressful.
Got it up and running with international version. Now to see if I can get LOS installed. My sincere thanks to all and apologies for crapping up the board with my panic. I thought I had really screwed up, but it appears it was just stuck in EDL mode and needed a hard (HARD) reset.
Hey man, thanks for the donation. Glad you were able to get your phone up and running!
Holy Sh*t man. I know 5 bucks ain't much but I wanted to thank you so much. I thought I was fukd
Hey guys. I need some help. this is my wrong doing !!
I got a network unlocked T mobile which I started using with AT&T. Today I received the unlock code from T mobile to unlock bootloader which I did. then I I installed TWRP and Magisk without any issues. then I tried to fix the persis.img coz fingerpritn is not working. it didnt work so I left it alone. But I dont know why I wiped cache, data and then phone got stuck at boot loop. (no backup). I tried to install using MSM tool but it didnt work. MSM tool was not detecting the phone. then in TWRP I clicked on EDL and now the phone screen is blank. tried every possible combination of keys but no luck. was doing all this on windows 10. any help would be greatly appreciated. thanks
kool_am said:
Hey guys. I need some help. this is my wrong doing !!
I got a network unlocked T mobile which I started using with AT&T. Today I received the unlock code from T mobile to unlock bootloader which I did. then I I installed TWRP and Magisk without any issues. then I tried to fix the persis.img coz fingerpritn is not working. it didnt work so I left it alone. But I dont know why I wiped cache, data and then phone got stuck at boot loop. (no backup). I tried to install using MSM tool but it didnt work. MSM tool was not detecting the phone. then in TWRP I clicked on EDL and now the phone screen is blank. tried every possible combination of keys but no luck. was doing all this on windows 10. any help would be greatly appreciated. thanks
Click to expand...
Click to collapse
So it turns out its not a hard brick. I'm stuck on TWRP. I'm able to get to fastboot. I tried to install Oxygen OS thru fastboot but the PC is not detecting the phone in fastboot. Mac detects it but I believe all the stock Roms are for PC use. I did try it on my MAc and was able to open a terminal window inside the Oxygen OS folder but then the fastboot device command is not found. any help would be greatly appreciated. I installed SDK and ADB drivers on PC but in device manager the device still only shows as Android device with no drivers. !! thanks
kool_am said:
So it turns out its not a hard brick. I'm stuck on TWRP. I'm able to get to fastboot. I tried to install Oxygen OS thru fastboot but the PC is not detecting the phone in fastboot. Mac detects it but I believe all the stock Roms are for PC use. I did try it on my MAc and was able to open a terminal window inside the Oxygen OS folder but then the fastboot device command is not found. any help would be greatly appreciated. I installed SDK and ADB drivers on PC but in device manager the device still only shows as Android device with no drivers. !! thanks
Click to expand...
Click to collapse
Solved !
solved how? i greatly would like to know how to flash from fastboot, i know that isnt what this thread was about but im having the exact same problems you are with msm. i can see the phone in fastboot but i have no idea how to flash or what to flash from there. I can get into recovery but i cant copy anything over to the phone and the drivers dont show up for adb. so i pretty much ONLY have fastboot and dont know what to do! 2 days since the phone been down and im lost AF
JCroffut said:
solved how? i greatly would like to know how to flash from fastboot, i know that isnt what this thread was about but im having the exact same problems you are with msm. i can see the phone in fastboot but i have no idea how to flash or what to flash from there. I can get into recovery but i cant copy anything over to the phone and the drivers dont show up for adb. so i pretty much ONLY have fastboot and dont know what to do! 2 days since the phone been down and im lost AF
Click to expand...
Click to collapse
Can msm detect the phone when connected in fastboot. Also check device manager in pc to make sure it detects the phone as qualcomm device. Otherwise msm will not work.
Download msm. Turn phone off. Connect phone to pc. Open msm. Press start. Press volume down and power button on phone. It should be detected by msm and should start flashing the software.
Standby....
When plugged in the phone in EDL it shows
QUSB_BULK_CID0412 with an exclamation mark inside a yellow triangle
When i plugged in the phone and open fastboot it shows
Android with an exclamation point inside a yellow triangle
I booted up msm, clicked other, clicked start, pressed volume down and volume up and plugged it in. still says waiting for device to connect. ive also tried this with a number of keys being help, ive tried to boot from twrp straight into edl mode, none of which works
which all says to me its a driver issue of some kind, but for 3 days ive been slaving away on xda and cannot for the life of me figure out where to get the drivers.
JCroffut said:
Standby....
When plugged in the phone in EDL it shows
QUSB_BULK_CID0412 with an exclamation mark inside a yellow triangle
When i plugged in the phone and open fastboot it shows
Android with an exclamation point inside a yellow triangle
I booted up msm, clicked other, clicked start, pressed volume down and volume up and plugged it in. still says waiting for device to connect. ive also tried this with a number of keys being help, ive tried to boot from twrp straight into edl mode, none of which works
which all says to me its a driver issue of some kind, but for 3 days ive been slaving away on xda and cannot for the life of me figure out where to get the drivers.
Click to expand...
Click to collapse
It is a driver issue for sure. When connected device manager should detect as qualcomm hd9008.......
kool_am said:
It is a driver issue for sure. When connected device manager should detect as qualcomm hd9008.......
Click to expand...
Click to collapse
i figured that, i am at a complete loss as to where to find the drivers. i actually might need you to hold my hand on this one a tiny bit because im about to smash the phone on the ground and say someone stole it. thats where i am with this phone haha
JCroffut said:
i figured that, i am at a complete loss as to where to find the drivers. i actually might need you to hold my hand on this one a tiny bit because im about to smash the phone on the ground and say someone stole it. thats where i am with this phone haha
Click to expand...
Click to collapse
qualcomm hs-usb qdloader 9008 - this is the exact name of the driver.
Try this link: https://forum.xda-developers.com/t/guide-fixing-hard-bricks-qualcomm-hs-usb-qdloader-9008.3403868/
kool_am said:
qualcomm hs-usb qdloader 9008 - this is the exact name of the driver.
Try this link: https://forum.xda-developers.com/t/guide-fixing-hard-bricks-qualcomm-hs-usb-qdloader-9008.3403868/
Click to expand...
Click to collapse
standby ill read through it now. we also have 2 different threads going so i can combine them if thats easier for you
kool_am said:
qualcomm hs-usb qdloader 9008 - this is the exact name of the driver.
Try this link: https://forum.xda-developers.com/t/guide-fixing-hard-bricks-qualcomm-hs-usb-qdloader-9008.3403868/
Click to expand...
Click to collapse
Only download the qualcomm driver from this link. Or search for it online.
I have spent much more time than you trying to figure this out. I have a pc and Mac both. Mac is not compatible with a lot of the software and my pc usb ports are all bad. Point being, leave it alone for a day or so. Come back at it with a fresh start and fresh mind.
kool_am said:
Only download the qualcomm driver from this link. Or search for it online.
I have spent much more time than you trying to figure this out. I have a pc and Mac both. Mac is not compatible with a lot of the software and my pc usb ports are all bad. Point being, leave it alone for a day or so. Come back at it with a fresh start and fresh mind.
Click to expand...
Click to collapse
i hear that. after 3 days of non stop working at it im pretty sure im just not smarter than the phone today lol. looks like this phone is now stolen and going into a trash can lol
JCroffut said:
i hear that. after 3 days of non stop working at it im pretty sure im just not smarter than the phone today lol. looks like this phone is now stolen and going into a trash can lol
Click to expand...
Click to collapse
If I were you, I wouldn't throw the phone away. Like I said it's a simple issue of driver. Install the correct driver and make sure you see it as qualcomm device in device manager. Trust me, from then on, it's just a matter of a few clicks.
I unbricked my phone to t mobile and then converted to global rom without any issues.
kool_am said:
If I were you, I wouldn't throw the phone away. Like I said it's a simple issue of driver. Install the correct driver and make sure you see it as qualcomm device in device manager. Trust me, from then on, it's just a matter of a few clicks.
I unbricked my phone to t mobile and then converted to global rom without any issues.
Click to expand...
Click to collapse
i sent you a private convo on here if thats ok so i dont spam the forum! You may be able to help me out if i could borrow a few minutes of your time!
JCroffut said:
i hear that. after 3 days of non stop working at it im pretty sure im just not smarter than the phone today lol. looks like this phone is now stolen and going into a trash can lol
Click to expand...
Click to collapse
i was definatly kidding tho this is my only phone and i have to solve this problem lol
I'm not sure if you have read this thread already. I messed up my phone a couple days ago as well and follow the steps there and was able to MSM my phone back to stock.
[OP8][OOS TMO 55CB] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com