Related
Hello guys,
so two days ago just when I was heading into work my phone randomly started restarting itself again and again. I had it in my pocket, mobile data and wifi off and nothing really going on when this happened. I was on stock Cyanogen OS with 6.0.1, rooted and with Xposed, but nothing too crazy or experimental.
The phone would boot with a small vibration to the Oneplus logo with the "Powered by Android" writing, stay on that for about 17-18 seconds, then reboot again. No way of going to the recovery with the hardware keys, it would just reboot the same again and again. Since I couldn't really do much, not turn it off and no way of disconnecting the battery, I just had to watch it reboot helplessly until the battery was dead. At home with some hassle I could get it charged again, which basically consisted of charging it while it kept rebooting and cooling it while doing that since it would get really, really hot.
The only option that really works is is getting it into fastboot via the volume up + power button. But in fastboot nothing I did so far changed even the smalles thing about it's behaviour. I tried flashing a new recovery image, letting it boot into the recovery via fastboot (both stock recovery and TWRP), reflashing the complete OS via fastboot again (CM 13 ZNH2KAS3P0), completely wiping it via fastboot and flashing an older ROM (CM11S XNPH44S) but so far nothing has even changed a thing. It keeps booting to the Oneplus logo for about 17-18 seconds before rebooting. The only thing that has changed is with the CM11S ROM the fastboot logo of the android head is now bigger.
I checked the bootloader via fastboot, but it's still unlocked.
So yeah, I'm at my wits end and desperate for any help. At this point I fear it might be a hardware issue and I can trash it, but I'm ready to grasp for straws as I don't really have the money for a new device yet.
Any help is appreciated! Thanks guys!
Atomschlumpf said:
Hello guys,
so two days ago just when I was heading into work my phone randomly started restarting itself again and again. I had it in my pocket, mobile data and wifi off and nothing really going on when this happened. I was on stock Cyanogen OS with 6.0.1, rooted and with Xposed, but nothing too crazy or experimental.
The phone would boot with a small vibration to the Oneplus logo with the "Powered by Android" writing, stay on that for about 17-18 seconds, then reboot again. No way of going to the recovery with the hardware keys, it would just reboot the same again and again. Since I couldn't really do much, not turn it off and no way of disconnecting the battery, I just had to watch it reboot helplessly until the battery was dead. At home with some hassle I could get it charged again, which basically consisted of charging it while it kept rebooting and cooling it while doing that since it would get really, really hot.
The only option that really works is is getting it into fastboot via the volume up + power button. But in fastboot nothing I did so far changed even the smalles thing about it's behaviour. I tried flashing a new recovery image, letting it boot into the recovery via fastboot (both stock recovery and TWRP), reflashing the complete OS via fastboot again (CM 13 ZNH2KAS3P0), completely wiping it via fastboot and flashing an older ROM (CM11S XNPH44S) but so far nothing has even changed a thing. It keeps booting to the Oneplus logo for about 17-18 seconds before rebooting. The only thing that has changed is with the CM11S ROM the fastboot logo of the android head is now bigger.
I checked the bootloader via fastboot, but it's still unlocked.
So yeah, I'm at my wits end and desperate for any help. At this point I fear it might be a hardware issue and I can trash it, but I'm ready to grasp for straws as I don't really have the money for a new device yet.
Any help is appreciated! Thanks guys!
Click to expand...
Click to collapse
how old is the device?
As far as I know my sister bought it around summer 2014 when it was released, I got it in late 2015
Atomschlumpf said:
As far as I know my sister bought it around summer 2014 when it was released, I got it in late 2015
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
AFAIK,If this toolkit can't fix your device then it's definitely hw issue.
Mr.Ak said:
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
AFAIK,If this toolkit can't fix your device then it's definitely hw issue.
Click to expand...
Click to collapse
Well, the tool won't even recognize my phone, so I guess I'm **** out of luck ¯\_(ツ)_/¯
****ing great....
Atomschlumpf said:
Well, the tool won't even recognize my phone, so I guess I'm **** out of luck ¯\_(ツ)_/¯
****ing great....
Click to expand...
Click to collapse
Lol,gave up that early?
It needs around 10 tries to get it correctly recognised.
Use XP system with the proper drivers given in the above thread.This tool doesn't work on adb/fastboot,it works on Usb Debugging Port,hence requires different drivers.
Mr.Ak said:
Lol,gave up that early?
It needs around 10 tries to get it correctly recognised.
Use XP system with the proper drivers given in the above thread.This tool doesn't work on adb/fastboot,it works on Usb Debugging Port,hence requires different drivers.
Click to expand...
Click to collapse
No, I didn't. I tried the USB Drivers I had already installed, the drivers that came in the package and the QPST Tool suggested in the thread on both my and my girlfriends laptop. But if it doesn't work on ADB/fastboot I probably can't use it anyway since my only two options are having the phone on the fastboot screen or having it constantly reboot....
At this point I'm just really, really frustrated and have sorta accepted it's very likely a hardware issue
I'm with the same problem. In my case, the tool does recognize and shows green after the end but when i try to boot, it only shows the boot logo.
I can enter in fastboot and trying the command "fastboot continue" the brightness goes up, but nothing else
already tried various tools, back to stock, qualcomm , and none worked, so can i throw it out of the window?
Edit: can't enter in recovery, and unlike the op, my phone doesn't reboot (at least i didn't notice it)
Hey, i was trying to flash Lineage OS on my Moto g7 Power but after flashing it and trying to reboot it, it went completely dead. The buttons don't respond and the screen just stays black. And there's definitly enough battery (full night of charging) and i'm 99% sure that it's not a hardware issue (only just got the phone). Any ways to force it to boot? (Btw i can't go into recovery or bootloader). Or any other solutions?
Ballyeet said:
Hey, i was trying to flash Lineage OS on my Moto g7 Power but after flashing it and trying to reboot it, it went completely dead. The buttons don't respond and the screen just stays black. And there's definitly enough battery (full night of charging) and i'm 99% sure that it's not a hardware issue (only just got the phone). Any ways to force it to boot? (Btw i can't go into recovery or bootloader). Or any other solutions?
Click to expand...
Click to collapse
Connect to a PC
Open Device Manager
Look for
QHSUSB_Bulk or qloader
If you see that it's in emergency download mode
You will need to flash the Blank Flash
https://forum.xda-developers.com/g7-power/how-to/guide-recovering-hard-brick-t3989753
Sent from my mata using XDA Labs
Thanks for the reply!
Tried the guide, but so far no luck. It does recognise my device and starts the process, but gets stuck at the firehose part, even though i have the exact same model as the poster of the guide. Asked him for help, so we'll see i guess.
i installed the DSU package and now the phone is stuck on your device is corrupted and cannot be trusted. I can only get into fast boot mode
can someone guide me through resetting it, I dont care about anything on the phone i just want it to go back
[FASTBOOT] [ROM] [PC REQUIRED] [OP9] Stock OOS 11.2.2.2AA
Greetings, I've appreciated @Slikkster2k's terrific thread that explains and walks you through fastboot recovery of a OnePlus 9. To make it more convenient, I've taken his process and adapted @mauronofrio's OnePlus 8 fastboot ROM to post a...
forum.xda-developers.com
This is flashed through fastboot
mattie_49 said:
[FASTBOOT] [ROM] [PC REQUIRED] [OP9] Stock OOS 11.2.2.2AA
Greetings, I've appreciated @Slikkster2k's terrific thread that explains and walks you through fastboot recovery of a OnePlus 9. To make it more convenient, I've taken his process and adapted @mauronofrio's OnePlus 8 fastboot ROM to post a...
forum.xda-developers.com
This is flashed through fastboot
Click to expand...
Click to collapse
If you can reach fastboot this method should work
_MartyMan_ said:
If you can reach fastboot this method should work
Click to expand...
Click to collapse
dont i need unlocked bootloader?
mattie_49 said:
[FASTBOOT] [ROM] [PC REQUIRED] [OP9] Stock OOS 11.2.2.2AA
Greetings, I've appreciated @Slikkster2k's terrific thread that explains and walks you through fastboot recovery of a OnePlus 9. To make it more convenient, I've taken his process and adapted @mauronofrio's OnePlus 8 fastboot ROM to post a...
forum.xda-developers.com
This is flashed through fastboot
Click to expand...
Click to collapse
dont i need unlocked bootloader?
You don't have bootloader unlocked? You might need to find your correct msm tool for your device, depending on if you got your phone from OnePlus or T-Mobile, or send it in for repair? A few people on here, including me, also was able to send it to OnePlus via 1 day airmail and have it shipped back the same way and repaired all for free. That might not be an option for you though, I don't know how much you need your phone but if it's bricked either way it might be the best option. Try the msm tool first though instead of using fastboot to flash stock.
casualBricker said:
dont i need unlocked bootloader?
Click to expand...
Click to collapse
To flash critical partitions, yes
D3G0N said:
You don't have bootloader unlocked? You might need to find your correct msm tool for your device, depending on if you got your phone from OnePlus or T-Mobile, or send it in for repair? A few people on here, including me, also was able to send it to OnePlus via 1 day airmail and have it shipped back the same way and repaired all for free. That might not be an option for you though, I don't know how much you need your phone but if it's bricked either way it might be the best option. Try the msm tool first though instead of using fastboot to flash stock.
Click to expand...
Click to collapse
+1 get a remote session from OnePlus tech's. He had said earlier he tried msm already and couldn't connect and changed op
D3G0N said:
You don't have bootloader unlocked? You might need to find your correct msm tool for your device, depending on if you got your phone from OnePlus or T-Mobile, or send it in for repair? A few people on here, including me, also was able to send it to OnePlus via 1 day airmail and have it shipped back the same way and repaired all for free. That might not be an option for you though, I don't know how much you need your phone but if it's bricked either way it might be the best option. Try the msm tool first though instead of using fastboot to flash stock.
Click to expand...
Click to collapse
A phone wouldnt have an unlocked bootloader from the start right? I've never been this deep in **** with my android so this is all really out of my depth. Ill send a message to the oneplus support while the file from the other post downloads, maybe it'll work after all
mattie_49 said:
+1 get a remote session from OnePlus tech's. He had said earlier he tried msm already and couldn't connect and changed op
Click to expand...
Click to collapse
My bad, didn't see that he changed op. I mean if he could not connect through msm, there are a few options to try, including installing a driver manually for the qcom device. I had to fiddle with drivers and whatnot for about an hour or so before flashing was able to successfully commence. msm should help but scheduling a remote repair might take a day or so from oneplus so might as well try you know?
casualBricker said:
A phone wouldnt have an unlocked bootloader from the start right? I've never been this deep in **** with my android so this is all really out of my depth. Ill send a message to the oneplus support while the file from the other post downloads, maybe it'll work after all
Click to expand...
Click to collapse
No it would not, however msm tool does not use unlocked bootloader. I was informed that you tried it and it did not work and removed it from your op, but what would not work? was the device not seen on com port?
D3G0N said:
No it would not, however msm tool does not use unlocked bootloader. I was informed that you tried it and it did not work and removed it from your op, but what would not work? was the device not seen on com port?
Click to expand...
Click to collapse
i havent used an msm? i couldnt get the com port to show up, or It was like showing up for short periods while i was doing certain inputs, but not long enough to get anything done
casualBricker said:
i havent used an msm? i couldnt get the com port to show up, or It was like showing up for short periods while i was doing certain inputs, but not long enough to get anything done
Click to expand...
Click to collapse
So you tried it though it sounds like. It requires specific steps to work. You need drivers to be installed, go into EDL mode by having the device off and holding volume up while plugging the device into your computer, and then you have to start it when the device is enumerated. Are you willing to try msm again? The only other options really are to have a remote session with oneplus, which might take a day or so to get done, or send it for free for repair?
D3G0N said:
So you tried it though it sounds like. It requires specific steps to work. You need drivers to be installed, go into EDL mode by having the device off and holding volume up while plugging the device into your computer, and then you have to start it when the device is enumerated. Are you willing to try msm again? The only other options really are to have a remote session with oneplus, which might take a day or so to get done, or send it for free for repair?
Click to expand...
Click to collapse
its the holding buttons part thats a little weird but im definitely ready to try it again. The problem occurs with how my phone is powercycling by itself whatever I do while its not in fast boot mode. This makes the MSM stop detecting the phone and I have to start over.
casualBricker said:
its the holding buttons part thats a little weird but im definitely ready to try it again. The problem occurs with how my phone is powercycling by itself whatever I do while its not in fast boot mode. This makes the MSM stop detecting the phone and I have to start over.
Click to expand...
Click to collapse
Yeah, I have bricked my op9 so many times I know what you are talking about. With the power cycling thing I have no idea why that happens, but sometimes if I start the msm tool while it is detected, it will stay in EDL mode and stop cycling. Other times I realized that it was not really in EDL mode to begin with. Make sure that the device is completely off. Open up msmtool and get it ready. Hold volume down and up, without holding the power button, and then connect it to your pc. Once it shows up just click start. You might need to try different usb ports, and/or make sure that your drivers are installed for qcom device in edl mode.
D3G0N said:
Yeah, I have bricked my op9 so many times I know what you are talking about. With the power cycling thing I have no idea why that happens, but sometimes if I start the msm tool while it is detected, it will stay in EDL mode and stop cycling. Other times I realized that it was not really in EDL mode to begin with. Make sure that the device is completely off. Open up msmtool and get it ready. Hold volume down and up, without holding the power button, and then connect it to your pc. Once it shows up just click start. You might need to try different usb ports, and/or make sure that your drivers are installed for qcom device in edl mode.
Click to expand...
Click to collapse
Thank you! i think im ready to start this hell, the "qualcom something 8001ish" driver showing up(while the phone shows up in msmtool) would mean the drivers are correctly installed right?
casualBricker said:
Thank you! i think im ready to start this hell, the "qualcom something 8001ish" driver showing up(while the phone shows up in msmtool) would mean the drivers are correctly installed right?
Click to expand...
Click to collapse
I believe so? in device manager you should see the device and then COM... like COM4 or COM3 or something, as long as it is COM and then a number, and if it shows up in msmtool then the drivers are probably installed. The process won't work if you dont have drivers set right, so try it and if it fails make sure that it is the right msmtool and that you have drivers installed. Do not touch it while it is doing its thing, lay it down on a surface or something just to be safe. Also you might not have to do this but I have found success with msmtool by going offline like disconnecting ethernet and turning off wifi, and setting my date back to december of 2018 in windows before starting the tool, I do not know why but if it fails try that first above all else.
D3G0N said:
I believe so? in device manager you should see the device and then COM... like COM4 or COM3 or something, as long as it is COM and then a number, and if it shows up in msmtool then the drivers are probably installed. The process won't work if you dont have drivers set right, so try it and if it fails make sure that it is the right msmtool and that you have drivers installed. Do not touch it while it is doing its thing, lay it down on a surface or something just to be safe. Also you might not have to do this but I have found success with msmtool by going offline like disconnecting ethernet and turning off wifi, and setting my date back to december of 2018 in windows before starting the tool, I do not know why but if it fails try that first above all else.
Click to expand...
Click to collapse
how do i make sure the phone is turned off, just when it goes black? and when I hold the volume buttons it goes into fast boot, does this mean I was too slow?
casualBricker said:
how do i make sure the phone is turned off, just when it goes black? and when I hold the volume buttons it goes into fast boot, does this mean I was too slow?
Click to expand...
Click to collapse
Yeah it should just be black screen. It goes into fastboot? You sure you aren't hitting the power button as well? In fastboot select power off. When it's off, hold only the volume buttons, and then plug it in.
D3G0N said:
Yeah it should just be black screen. It goes into fastboot? You sure you aren't hitting the power button as well? In fastboot select power off. When it's off, hold only the volume buttons, and then plug it in.
Click to expand...
Click to collapse
im not touching the powerbutton, it confuses me as well. do I wait for it to vibrate before I plug in the phone?
Hey guys, I recently rooted my stylus 5g and went to install TWRP. I was able to get it to boot to TWRP, but I believe within TWRP I did the flash wrong as now my device is hard bricked. I cannot get it to show the initial logo, get to the bootloader or I think even EDL. I've tried the Lenovo recovery tool and the Moto all-in-one tool, but essentially all I get now is a black screen.
Any input on what I can do to either diagnose and possibly recover my device? I have the original firmware downloaded, but without being able to get to the bootloader, recovery, or even EDL, I'm at a loss as to how to proceed. I did grab a blankflash for the device, but I'm not clear on how to begin to use that to move forward.
Thanks for any advice you can provide.
-Ryan
Hello friend, honestly I am new to this. In fact I'm looking for how to unlock my moto g stylus 5g xt2131-1 from metropcs to use it with a mobile operator in Colombia. But given your problem, and everything I've researched recently, I would say you could check this video:
in which revive a moto g8+, although it is a different version, it should work if you do the steps as indicated.
Did you ever figure this out? Mine is also hard bricked at the moment. I've been trying to get it to the 9008 mode so I can blankflash but I've had no luck. I see on some phones there is a pair of pins on the board that need to be shorted but I'm not sure which ones. I just bought an edl cable on amazon which should be here tomorrow, hopefully that will get it in the correct mode.
duffman452001 said:
Did you ever figure this out? Mine is also hard bricked at the moment. I've been trying to get it to the 9008 mode so I can blankflash but I've had no luck. I see on some phones there is a pair of pins on the board that need to be shorted but I'm not sure which ones. I just bought an edl cable on amazon which should be here tomorrow, hopefully that will get it in the correct mode.
Click to expand...
Click to collapse
could you let me know if that works. im struggling with this as well
Absolut_Malarkey said:
could you let me know if that works. im struggling with this as well
Click to expand...
Click to collapse
No luck. Only change with the EDL cable is that if I plug the phone in via the cable with the battery unplugged it was a pretty rapid blink vs before it would blink every 10 seconds or so if I held the power button while plugged in to power. The button on the EDL cable had no effect. I then tried to short out every combination of pads on the board similar to the video above. No luck, it just seems to be completely toast. All I did from TWRP is format data and reboot to fastboot. Dead since then.
Is there any more information on this subject?
View attachment IMG_20220717_121138987~2_66348_SP-8988.jpg
Here is the pcb picture. Not sure if the number 2 has any significant meaning but someone told me it was one of those points with one by the battery connector. Anyone have any info on this it would be greatly appreciated.
EDL test points and blank-flash boost mobile
Here are the edl (emergency download mode) test points for Motorola Moto G Stylus 5G XT2131.
forum.xda-developers.com
duffman452001 said:
No luck. Only change with the EDL cable is that if I plug the phone in via the cable with the battery unplugged it was a pretty rapid blink vs before it would blink every 10 seconds or so if I held the power button while plugged in to power. The button on the EDL cable had no effect. I then tried to short out every combination of pads on the board similar to the video above. No luck, it just seems to be completely toast. All I did from TWRP is format data and reboot to fastboot. Dead since then.
Click to expand...
Click to collapse
thank god i saw this, i was getting ready to flash TWRP even just unlocked my bootloader and everything, not taking this chance! i honestly got so many phones to root, unlock the bootloader, flash new roms, but litterly all of them have at least one problem.. (my devices range from lg to motorola, zte, htc, samsung...) i had a moto g play, but i tried to flash TWRP from magisk, and looked like it was stuck in boot loop, then used motorola tool, and fried it.. litterly didnt show any sign of life after, (I dont thing it was motorlas tool, i think it had something to do with me trying to flash TWRP, anyway, the screen looks like an explosion! had more fun hitting it with a rubber mallet than getting frusterated, and maybe fixing it...
liammmmnnnn said:
thank god i saw this, i was getting ready to flash TWRP even just unlocked my bootloader and everything, not taking this chance! i honestly got so many phones to root, unlock the bootloader, flash new roms, but litterly all of them have at least one problem.. (my devices range from lg to motorola, zte, htc, samsung...) i had a moto g play, but i tried to flash TWRP from magisk, and looked like it was stuck in boot loop, then used motorola tool, and fried it.. litterly didnt show any sign of life after, (I dont thing it was motorlas tool, i think it had something to do with me trying to flash TWRP, anyway, the screen looks like an explosion! had more fun hitting it with a rubber mallet than getting frusterated, and maybe fixing it...
Click to expand...
Click to collapse
I did end up recovering mine via the test points https://forum.xda-developers.com/t/...ank-flash-boost-mobile.4469613/#post-87181339
duffman452001 said:
I did end up recovering mine via the test points https://forum.xda-developers.com/t/...ank-flash-boost-mobile.4469613/#post-87181339
Click to expand...
Click to collapse
my moto g stylus is thru T-Mobile, i heard that its different, lol i just honestly dont want to brick mine, im also kinda new to this stuff, so if something is gonna go wrong even with steps its me LOLL, also im not meaning to be mean if you take it that way
deleted.
liammmmnnnn said:
my moto g stylus is thru T-Mobile, i heard that its different, lol i just honestly dont want to brick mine, im also kinda new to this stuff, so if something is gonna go wrong even with steps its me LOLL, also im not meaning to be mean if you take it that way
Click to expand...
Click to collapse
That thread for the 2131 EDL is correct, ive used it.
wickedxjay said:
That thread for the 2131 EDL is correct, ive used it.
Click to expand...
Click to collapse
You used it it on the xt2215-4?
I have an OP 9 LE 2115 Global in USA
I was on LOS 19.
I had some issues and wanted to revert back to stock OOS 11.
First I tried via Recovery to flash Stock ROM OOS 11, but I had an error regarding the system version being too old and it didn't complete. The phone would no longer boot to OS.
I got the MSMDownloadTool from here: https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_9/Global_LE25AA/R/
I used the tool successfully and got my phone booting to OS again.
But now my power button IMMEDIATELY turns off the phone whenever pressed, and does this kind of CRT TV shutdown, where the screen phases out vertically with colors.
This happens in recovery/fastboot menus as well, most of the time, and makes booting into recovery/fastboot *almost* impossible, as when I let go of the power button it turns off, and when I select and option with the power button it shuts off.
Any information would be so helpful! Thank you fine knowledgeable people of XDA.
For anyone to help, we need to know which model you have and which version of msm tool did you use?
Updated my original post. My apologies for the lack of important details.
Also I got a TWRP recovery successfully installed, so I have a recovery again.
I found this article that explains how to install each part individually via fastboot
Do you think this would help with my errors of non-existent partitions?
How to Unbrick OnePlus 9/Pro via Fastboot Commands
In this comprehensive guide, we will show you the steps to unbrick the OnePlus 9 and 9 Pro devices via Fastboot Commands.
www.droidwin.com
I'm tempted to try, but if anyone could chime in first?
Still having this issue, has anyone ever even heard of this problem?
wakeeshi said:
Still having this issue, has anyone ever even heard of this problem?
Click to expand...
Click to collapse
This sounds like a hardware problem. If just after msm the phone does this, hardware it is then.
Thank you for the reply.
Do you have any more information or an idea on how to fix it? Or are you implying I may have caused permanent damage?
wakeeshi said:
Thank you for the reply.
Do you have any more information or an idea on how to fix it? Or are you implying I may have caused permanent damage?
Click to expand...
Click to collapse
Flash with msm again. If problem persist after first time setup, hardware problem.
MrSteelX said:
Flash with msm again. If problem persist after first time setup, hardware problem.
Click to expand...
Click to collapse
I have flashed with MSM a couple more times and same thing.
But for example, I got it to boot without the issue again, and everything works as normal, but as soon as I turn the phone off or it dies, I will struggle to get a boot that works properly.
I end up fiddling with the holding the volume buttons and power buttons in different combinations and eventually it works. I'm not sure if that's just random, or if I'm actually causing it.
If I can have a completely working boot, where the power/sleep button functions as normal, it seems like it's a firmware, data issue. Could you elaborate?
Thank you!
Hoping to bump this and try to get some help. My GPS also has failed to get a fix in this kerfuffle. (this is one of the reasons I was originally resetting to stock from LineageOS 19). Any advice?
Hardware problem and the fact it is 100% repeatable is a sign of hardware problem.