Few months ago I flashed some stuff on my phone which I shouldn't have, I guess. In the meantime I got a new one but now I'm trying to recover my OP3. I tried all sorts of MSM tools, (from Marshmallow to latest Pie that OP support provided me with) and in best case I could get it to bootloop and then throw me a dm verity warning screen after that (screenshot below) After that it only can throw me in a generic chinese OP recovery which fails to do anything. MSM runs fine, loads up as HS 9008 Qualcomm device and gets it's job done in 5-6 mins. I can't do anything in fastboot since bootloader is locked after MSM. Is there any help because it seems to not be completely dead?
Thanks
Screen after bootloop:
https://imgur.com/a/R1lJTjX
AnnoyingZlatan said:
Few months ago I flashed some stuff on my phone which I shouldn't have, I guess. In the meantime I got a new one but now I'm trying to recover my OP3. I tried all sorts of MSM tools, (from Marshmallow to latest Pie that OP support provided me with) and in best case I could get it to bootloop and then throw me a dm verity warning screen after that (screenshot below) After that it only can throw me in a generic chinese OP recovery which fails to do anything. MSM runs fine, loads up as HS 9008 Qualcomm device and gets it's job done in 5-6 mins. I can't do anything in fastboot since bootloader is locked after MSM. Is there any help because it seems to not be completely dead?
Thanks
Screen after bootloop:
https://imgur.com/a/R1lJTjX
Click to expand...
Click to collapse
If you can get to bootloader, download and flash OOS 5.0.6. If not, try one of the MSM Tools on XDA. There are quite a few of them, search. Please also note that the Tool is different for 3 and 3T.
I had used one of the oldest Tools here on XDA a couple of times without any hiccups.
Did you get a solution to this? I am struggling with the same issue.
Another OP3 user here with the same problem as you guys.
I tried all of the MSM tools posted here, with no success and varying responses from the phone.
One of them does let me actually boot to recovery, but it's the generic one that only has install from adb (and sideloading always fails at 47% - haven't found a solution around that yet either). From inside recovery, attempting to wipe cache or wipe system gets about 3/4 of the way then the device reboots on its own.
I was also on occasion able to boot to the decrypt password entry screen, but no password is valid and attempting to issue a reset from there (from Forgot password) doesn't seem to do anything.
No issues getting to fastboot or qs9008 serial mode, but bootloader is locked also so kind of stuck.
In my case, phone was working fine, but the OTA update caused a brick so I've been trying to recover it since then.
Maybe somebody else has an idea here..
myserver57 said:
Another OP3 user here with the same problem as you guys.
I tried all of the MSM tools posted here, with no success and varying responses from the phone.
One of them does let me actually boot to recovery, but it's the generic one that only has install from adb (and sideloading always fails at 47% - haven't found a solution around that yet either). From inside recovery, attempting to wipe cache or wipe system gets about 3/4 of the way then the device reboots on its own.
I was also on occasion able to boot to the decrypt password entry screen, but no password is valid and attempting to issue a reset from there (from Forgot password) doesn't seem to do anything.
No issues getting to fastboot or qs9008 serial mode, but bootloader is locked also so kind of stuck.
In my case, phone was working fine, but the OTA update caused a brick so I've been trying to recover it since then.
Maybe somebody else has an idea here..
Click to expand...
Click to collapse
Did you try to sideload OOS using adb? Try the various versions of OOS.
TNSMANI said:
Did you try to sideload OOS using adb? Try the various versions of OOS.
Click to expand...
Click to collapse
Thanks, yes I did. Stalls at 47%.
Also tried every version of OOS that I could find (5.04, 5.05, 5.06, etc from https://forum.xda-developers.com/oneplus-3/how-to/op3-collection-unbrick-tools-t3896722)
Also tried the versions from https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
(this one is the one that sometimes lets me get to recovery, the others don't).
myserver57 said:
Thanks, yes I did. Stalls at 47%.
Also tried every version of OOS that I could find (5.04, 5.05, 5.06, etc from https://forum.xda-developers.com/oneplus-3/how-to/op3-collection-unbrick-tools-t3896722)
Also tried the versions from https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
(this one is the one that sometimes lets me get to recovery, the others don't).
Click to expand...
Click to collapse
If you are able to use fastboot, try flashing TWRP or atleast boot TWRP and then from TWRP flash OOS or one of the custom ROMs.
If this also fails, I am at a loss for ideas. May be you have a hardware fault.
TNSMANI said:
If you are able to use fastboot, try flashing TWRP or atleast boot TWRP and then from TWRP flash OOS or one of the custom ROMs.
If this also fails, I am at a loss for ideas. May be you have a hardware fault.
Click to expand...
Click to collapse
Thanks again for trying to help.
Sadly, bootloader is locked so flashing TWRP or even booting to TWRP is a no-go.
I don't think it's a hardware fault since it was working fine before the OTA update, but I guess you never know. Damn, if only sideloading would work, darn thing...
Related
Dear XDA Community,
in past 2 months i've been using CM13, constantly having some trouble with apps involving the camera, such as the camera app(surprise) and e.g. snapchat.
So yesterday I decided to update my CM Build, not knowing it would be to CM14 and with this Android 7.
So resulting from this I experienced a lot of issues with different apps, especially the google ones and for example Instagram. I DID NOT Upgrade my twrp, which was pretty stupid as I found out.
So this morning I checked again for CM Updates and Updated to Version Nightly...25 I think... but because I did not update my TWRP it did absolutely nothing except bricking my phone.
I already followed through the Guide for Hard Bricked OP3s (both steps) "http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700"
Though it sadly did not work for me. The Recovery tool and all works but when I want to boot my Phone the md5checksum pops up after the OP3 Logo and it tells me that everythings fine except "boot: failed".
I tried the procedure of the Hard Brick fix over and over again but nothing seems to work. I am fairly new to this whole Custom Rom stuff so I have absolutely no clue what do to.
Does anyone have any idea that could help?
Best Regards
Aliasalex
Try fastboot flashing the whole rom.
how? i dont have a factory img.
i tried flashing CM14 again and OxygenOs OTA. Currently i am getting Cache, Boot and System Failed.
In the meanwhile I managed to get twrp installed, but trying to install OS or CM via twrp didnt work either
//edit: ran the msm download tool again. Now only Boot is failing. tried flashing a boot.img via fastboot but didnt work
//edit2: when flashing the boot.img via fastboot my phone boots and works. When restarting without PC it still has cache and boot failure in md5checksum
try the 1st method you mentioned in the OP but flash https://www.androidfilehost.com/?fid=24591020540821926 . from what I understand, you need to full write all your partitions since they seems corrupted.
aliasalex said:
how? i dont have a factory img.
i tried flashing CM14 again and OxygenOs OTA. Currently i am getting Cache, Boot and System Failed.
In the meanwhile I managed to get twrp installed, but trying to install OS or CM via twrp didnt work either
//edit: ran the msm download tool again. Now only Boot is failing. tried flashing a boot.img via fastboot but didnt work
//edit2: when flashing the boot.img via fastboot my phone boots and works. When restarting without PC it still has cache and boot failure in md5checksum
Click to expand...
Click to collapse
I'll help you when I'm home
Connect your phone to Fastboot. Go to device manager on Windows. Do you see something with OnePlus or kedacomm. I had this issue as well managed to solve it after 2 days.
Demian3112 said:
I'll help you when I'm home
Connect your phone to Fastboot. Go to device manager on Windows. Do you see something with OnePlus or kedacomm. I had this issue as well managed to solve it after 2 days.
Click to expand...
Click to collapse
Yes a Kedacom USB Device "Android ADB Interface" is listed.
aliasalex said:
Yes a Kedacom USB Device "Android ADB Interface" is listed.
Click to expand...
Click to collapse
I'm not home atm. But can you change it by any chance to Oneplus? Your almost there! Maybe the video can explain something, I don't have a pc close.
https://youtu.be/maLWScgXflk
Demian3112 said:
I'm not home atm. But can you change it by any chance to Oneplus? Your almost there! Maybe the video can explain something, I don't have a pc close.
https://youtu.be/maLWScgXflk
Click to expand...
Click to collapse
I installed the adb setup, still shows my OP3 as Kedacom -> android adb device..
my phone has been working for the past few days flawlessly, but it still doesnt boot on its own
aliasalex said:
I installed the adb setup, still shows my OP3 as Kedacom -> android adb device..
my phone has been working for the past few days flawlessly, but it still doesnt boot on its own
Click to expand...
Click to collapse
You can't access Fastboot because of that Kedacom driver, if you right click it you should be able to change the driver.
https://support.hidemyass.com/hc/en...ow-to-disable-Driver-Signing-check-on-Windows try to boot into this. Also try to install Oneplus drivers. It's in the unbrick post.
Demian3112 said:
You can't access Fastboot because of that Kedacom driver, if you right click it you should be able to change the driver.
https://support.hidemyass.com/hc/en...ow-to-disable-Driver-Signing-check-on-Windows try to boot into this. Also try to install Oneplus drivers. It's in the unbrick post.
Click to expand...
Click to collapse
But I can access fastboot!?
Also I disabled Driver Signing Check when first trying to unbrick my phone.
I installed the drivers given in the Unbrick Test, it showed something like Qualcomm [something] 9003. There was something in between.
aliasalex said:
But I can access fastboot!?
Also I disabled Driver Signing Check when first trying to unbrick my phone.
I installed the drivers given in the Unbrick Test, it showed something like Qualcomm [something] 9003. There was something in between.
Click to expand...
Click to collapse
Nice, whdn you boot you still get those errors in red letter something with "failed boot". Then manually flash the boot. Img provided in the folder where you ran the Unbrick tool from. Command for Fastboot "fastboot devices", then "fastboot flash boot boot.img". Make sure that Kedacom is not in device manager when you are accessing Fastboot.
Where to begin...
Okay, so I ended up flashing an incorrect .zip which caused my Nexus 5X to go into a boot loop. Usually, the fix is to go into TWRP and fix what I broke. Unfortunately, TWRP or Custom Recovery does not exist. The endless boot isn't booting far enough for ADB or Fastboot commands. Additionally, my volume down button my device is also broken so therefore I can not manually go into Custom Recovery. Also, I know I have the right drivers needed in my windows 10 machine to read the device. The device is not able to be seen by the computer currently either.
My question is, I am currently at the Firmware Update screen. This is the only screen I can currently go into manually. What is it that I can do from the Firmware Update screen ( Download Mode ) to restore my device?
There is a temporary fix or two so you can get back your data, but not permanent fix. The chipset will keep falling and the phone gonna die.
KarimKh said:
There is a temporary fix or two so you can get back your data, but not permanent fix. The chipset will keep falling and the phone gonna die.
Click to expand...
Click to collapse
That explains a lot...Lol!
Luckily, there is hope for you!
should work
Can't test it since my device is in a deeper bootloop that requires Qualcomm files that nobody wants to build.
I've had Google phones for years now, including previous Pixel, but I just got an XL 2 yesterday and I'm regretting it.
It's Google unlocked and running June's latest image. I've experienced various app crashing on stock, and random reboots.
Then there's the rooting and flashing. I unlocked the bootloader and installed the most recent, twrp (the one verified to work on xda for roms) but can't flash anything.
My twrp either hangs on the twrp start screen, or when it does load, the touch screen doesn't work. When I can get it going, every rom I flash gives me an error on the second step. I'm flashing on slot B by the way, that's what boots up when I boot to twrp.
Lastly, I am unlocked both for flashing and flashing_critical thru adb, so I'm at a loss and seriously confused.
When I FIRST unlocked everything, I was able to flash Nitrogen rom but I got stuck at the rom splash screen.
Tldr:
-What is the Correct install method/sequence for roms?
-do the slots matter?
-is random reboots and app crashing on stock a sign of a hardware issue?
I haven't installed a custom ROM on my P2XL, so I'm running rooted stock. Anyway, for rooted stock, this is what I did.
Entered bootloader mode.
Booted into recovery using the command "fastboot boot recovery.img", where "recovery.img" is the TWRP recovery iteslf. In my case, I renamed it "taimen.img".
Flashed the TWRP installer zip needed for the P2XL (Required if intending to replace the stock recovery).
Rebooted into recovery.
Flashed a custom kernel (Recommended - resolves touch issues in TWRP).
Flashed Magisk.
6. Rebooted.
If installing a custom ROM, flash it prior to the custom kernel. Slots only matter if running stock. Random reboots and app crashes are not signs of a hardware issue.
stevew84 said:
I've had Google phones for years now, including previous Pixel, but I just got an XL 2 yesterday and I'm regretting it.
It's Google unlocked and running June's latest image. I've experienced various app crashing on stock, and random reboots.
Then there's the rooting and flashing. I unlocked the bootloader and installed the most recent, twrp (the one verified to work on xda for roms) but can't flash anything.
My twrp either hangs on the twrp start screen, or when it does load, the touch screen doesn't work. When I can get it going, every rom I flash gives me an error on the second step. I'm flashing on slot B by the way, that's what boots up when I boot to twrp.
Lastly, I am unlocked both for flashing and flashing_critical thru adb, so I'm at a loss and seriously confused.
When I FIRST unlocked everything, I was able to flash Nitrogen rom but I got stuck at the rom splash screen.
Tldr:
-What is the Correct install method/sequence for roms?
-do the slots matter?
-is random reboots and app crashing on stock a sign of a hardware issue?
Click to expand...
Click to collapse
Ya know my friend, after our conversation yesterday, and your questions in the nitrogen thread, and now random reboots and app crashes, I think it's time to consider a factory reset. You shouldn't be having those problems on a stock setup. If that's not successful, then I would definitely consider an RMA. Just my 2 cents worth :good:
I agree. I got it used tho which is an issue.
Badger50 said:
Ya know my friend, after our conversation yesterday, and your questions in the nitrogen thread, and now random reboots and app crashes, I think it's time to consider a factory reset. You shouldn't be having those problems on a stock setup. If that's not successful, then I would definitely consider an RMA. Just my 2 cents worth :good:
Click to expand...
Click to collapse
Just so you know, I got the rom to flash finally, but it's stuck at the rom splash screen during first boot. I'm going to leave it and hope it eventually boots up.
stevew84 said:
Just so you know, I got the rom to flash finally, but it's stuck at the rom splash screen during first boot. I'm going to leave it and hope it eventually boots up.
Click to expand...
Click to collapse
If it doesn't after 5 minutes, do a hard restart with the power button. If that doesn't work, then reboot to twrp and flash the rom and twrp installer zip again.
Ok cool thanks. I relocked bootloader last night and went back to stock. Unlocked it all this morning from my work computer and different unlock app. So here's hoping.
Badger50 said:
If it doesn't after 5 minutes, do a hard restart with the power button. If that doesn't work, then reboot to twrp and flash the rom and twrp installer zip again.
Click to expand...
Click to collapse
I finally got everything to work. My vendor image is a mismatch but I could just flash junes and be done with it, right?
stevew84 said:
I finally got everything to work. My vendor image is a mismatch but I could just flash junes and be done with it, right?
Click to expand...
Click to collapse
What did you do to get it to work? You could just flash the June vendor.img to both slots. If you keep getting a vendor mismatch, probably nothing to worry about according to the Dev of nitrogen.
Different machine, cable and unlocking tool.
But I went to bone stock with locked bootloader, then flashed the newest twrp with the newest all in one tool. Was on slot A so wiped everything and flashed rom plus twrp again. I rebooted system to slot B, but then it just hung at the rom splash screen.
So I did it all over on slot A, ignored the "no os installed" message and booted anyway. Then it fired up. Rebooting into twrp from there took me to B, which is where I need to be for an image file or root.
So yea, thanks for the help.
I'm having this issue also. I tried flashing nitrogen, it hung. I tried to go back with factory reset Img and nothing happens in adb. Flashed the may img and it wouldn't boot all the way up. Now I'm stuck in bootloader trying to figure this all out. Seems like nothing in doing is working. I can get recovery to boot, but no files inside so idk. Tried to sideloadb nitrogen, but it said adb out of date for device when sdk is fully updated.
MatthewRobinson said:
I'm having this issue also. I tried flashing nitrogen, it hung. I tried to go back with factory reset Img and nothing happens in adb. Flashed the may img and it wouldn't boot all the way up. Now I'm stuck in bootloader trying to figure this all out. Seems like nothing in doing is working. I can get recovery to boot, but no files inside so idk. Tried to sideloadb nitrogen, but it said adb out of date for device when sdk is fully updated.
Click to expand...
Click to collapse
You didn't mention the out of date message in your other post, but uninstall SDK and then download the stand-alone adb/fastboot binaries from May of this year. Dump that in a folder (eg. c:\adb) and put that folder in your path statement. Manually flash the full factory image without modifying flash-all.bat. Post your screeen if you have any errors. :good:
stevew84 said:
I agree. I got it used tho which is an issue.
Click to expand...
Click to collapse
Google knows the date the phone was purchased based on imei number and honors their warranty by date, not owner. Unless it was blacklisted.
smartymcfly said:
Google knows the date the phone was purchased based on imei number and honors their warranty based on that.
Click to expand...
Click to collapse
Thanks. I might try to take advantage.
Not 100% sure of best place to post this, but I'm getting desperate now...
I'm pretty worried I've killed my device. After following the guide on how to root with Magisk, my phone is stuck on the white "loading" screen with a G logo. I've since tried to restart, but I can either go into fastboot mode or get the white screen when attempting to boot into android.
Tried to flash the latest factory image to fix it, but that couldn't get that to work. Now the phone isn't showing up on adb devices either. panicking a little bit here.
Does anyone know what to do?
ADB won't work unless the phone is booted into Android or in stock recovery for a sideload.
Does your computer recognize the device when you are in Fastboot mode and type "fastboot devices"? Try flashing the factory image again but make sure you have the most up to date platform tools from Google. Old versions are a common cause of issues.
Did you flash TWRP recovery or just boot to it to root? If you still have stock recovery you can try a factory reset from there but any modified images you installed might be the issue.
like Fury said, your platform tools need to be updated, same thing happened to me.
What didn't work when you flashed the factory image? Do you have the latest sdk tools version of fastboot and adb?
Sent from my [device_name] using XDA-Developers Legacy app
fury683 said:
ADB won't work unless the phone is booted into Android or in stock recovery for a sideload.
Does your computer recognize the device when you are in Fastboot mode and type "fastboot devices"? Try flashing the factory image again but make sure you have the most up to date platform tools from Google. Old versions are a common cause of issues.
Did you flash TWRP recovery or just boot to it to root? If you still have stock recovery you can try a factory reset from there but any modified images you installed might be the issue.
Click to expand...
Click to collapse
Thanks so much, this is where I was going wrong. Have gone into recovery and rescued it.
Tried the process again to get Magisk working, but ended up the same although this time the white screen only went on for a while before I got an error saying my data was corrupted. Tbh, after all the stress I'm just going to give up on this and live with the phone in stock. All my drivers and adb were installed and setup today, so everything is up to date.
edit...
Not out of the woods yet. After restarting the phone and going through the setup, it's not detecting the SIM card or any wifi networks. I've installed the OTA and wiped data once more after having this problem, still not resolved.
Nick676 said:
Thanks so much, this is where I was going wrong. Have gone into recovery and rescued it.
Tried the process again to get Magisk working, but ended up the same although this time the white screen only went on for a while before I got an error saying my data was corrupted. Tbh, after all the stress I'm just going to give up on this and live with the phone in stock. All my drivers and adb were installed and setup today, so everything is up to date.
Thanks again for helping.
Click to expand...
Click to collapse
It sounds like you are trying to install Magisk v17.1 like I tried. If so you need to use v17.3 beta. If you follow this thread you should be fine. It even tells you what to do for your original problem, just takes some reading and patience.
Misterxtc said:
It sounds like you are trying to install Magisk v17.1 like I tried. If so you need to use v17.3 beta. If you follow this thread you should be fine. It even tells you what to do for your original problem, just takes some reading and patience.
Click to expand...
Click to collapse
I tried it with both 17.1 and 17.3, so not sure what the issue is. Seem to have finally booted up properly with wifi and signal working, so hopefully it's all good now. Gonna give up on rooting.
Nick676 said:
Not 100% sure of best place to post this, but I'm getting desperate now...
I'm pretty worried I've killed my device. After following the guide on how to root with Magisk, my phone is stuck on the white "loading" screen with a G logo. I've since tried to restart, but I can either go into fastboot mode or get the white screen when attempting to boot into android.
Tried to flash the latest factory image to fix it, but that couldn't get that to work. Now the phone isn't showing up on adb devices either. panicking a little bit here.
Does anyone know what to do?
Click to expand...
Click to collapse
you may want to try to totally uninstalling Magisk frist with the official latest Magisk uninstaller and reboot and then do a complete factory reset. this has helped me in the past.
my new pixel 3XL will be the first Android phone that I owned that will not be rooted.
Hello everyone, Merry Christmas!
Although I say that, I bring not so merry news. My OnePlus 7T is bricked and after trying everything I don't know where to go from here. Currently I am stuck at the:
The current image (boot/recovery) has been destroyed​phase of things and all I can do is boot into fastboot, that is it.
How did this all start? All I did was just update the phone to Android 12 with the official OTA update from OnePlus, big mistake. Worst update ever; my adaptive brightness went haywire, the brightness gets stuck at max, I couldn't receive calls, data was completely unresponsive, and the list goes on. So before the obvious downgrade method, I try a few things first:
Cycle airplane mode on/off
Reset network settings
Reset ANR
These worked for a minute on my data then right back to the same issue.
Wipe cache partition... Oh wait I had to find out the hard way Android 12 removed this option....
Wipe the phone
That fixed nothing.
Ok time to downgrade, but this is where things got tricky and I realized that maybe all my issues stemmed from me getting the wrong update from OnePlus? Although I found this out too late.
See my phone model is HD1907 which I already knew at the back of my head, but when it mattered to remember the most, I didn't catch what happened. After my update to A12, my model number changed to HD1901 which is the Indian version, and when I saw it didn't think anything of it at the time but then after all my problems it came back to me, my phone has always HD1907 so maybe this is a compatibility issue.
Anyway since I was going to downgrade anyway I thought to myself, 'since I already wiped everything, maybe I can use this opportunity to try out a ROM for A12 and see if it is just this ****ty OOS causing all these issues,' and so I did. First thing I did was unlock the bootloader, and try get TWRP on my phone. That all went fine, I booted into TWRP, flashed my zip for TWRP, then proceeded to try to boot into the OS... and the rest is history because that is as far as I got. Apparently my boot.img is destroyed and I can't boot back into TWRP anymore either, all I can do is get to fastboot.
So then I tried MSM, it won't detect my phone.... So then I tried flashing my Stock ROM through fastboot, apparently I'm missing a partition and it won't write to a critical partition either....
So where do I go from here...?
Hello I was in the exact same boat as you today same phone, same update issues, same no recovery mode, no os to boot into only greeted with fastboot mode. I have resolved it and I'm back on oos 11 good as new. I did use the msm tool it is tricky for sure at first. A critical step is installing the qualcomm drivers and then rebooting your pc. Get them here
https://androiddatahost.com/nbyn6. Be sure to reboot. It's late and I just got this thing back into working shape so I don't want to write a lot a right now. It's been a few days since this post so... If you are still stuck I will be glad to help out let me know. There is hope!
Canbeit said:
Hello I was in the exact same boat as you today same phone, same update issues, same no recovery mode, no os to boot into only greeted with fastboot mode. I have resolved it and I'm back on oos 11 good as new. I did use the msm tool it is tricky for sure at first. A critical step is installing the qualcomm drivers and then rebooting your pc. Get them here
https://androiddatahost.com/nbyn6. Be sure to reboot. It's late and I just got this thing back into working shape so I don't want to write a lot a right now. It's been a few days since this post so... If you are still stuck I will be glad to help out let me know. There is hope!
Click to expand...
Click to collapse
I too had all the symptoms after an update to OOS12, including progressively losing any semblance of booting. not even recovery and the drivers found elsewhere didn't work, and had a different name when installed and would never get detected in the MsmDownloadTool. After installing this one and rebooting, it finally detects it and installs the image of EDL mode.