Related
Guys, i wanted to get my phone repaired under warranty. I had rooted it and it was S-OFF. So i flashed the stock ROM and the radio, but while trying to make it back to S-ON, using rebranding, debranding and S-ON method given in the android development section, i think i bricked my phone. When i wrote the command "fastboot oem writesecureflag 3", the phone just turned off. Now it wont turn on, tried everything still no use. Plz help!!
Also, can i get it repaired under warranty still, as the phone does not turn on at all so i dont think there would be any way for htc to detect wether it was rooted or not.
Sounds like it ran out of battery when doing it, mine didn't turn off when I set back to S-ON
Actually after i wrote the command and pressed enter, the text on cmd said okay and then as the phone should have rebooted, the screen turned off but it did not reboot, so i tried by removing and re-inserting the battery but still it couldnt go in the bootloader mode. I still cannot figure out what i did wrong.
does your phone respond to the charger?? (does the orange lamp turn on when you plug it to the charger)
if it reacts, probably your battery ran out. try charging it, and when it's charged (or while it's charging) try to start the phone, or try to boot into fastboot (vol down + power)
If you can boot into fastboot, the phone is not bricked.
If it doesn't respond to charger or you can't boot into fastboot, then the phone is bricked, and you can send it to store to repair it...
(i had this last problem, and I sent my phone to the dealer to repair it.)
ico86 said:
does your phone respond to the charger?? (does the orange lamp turn on when you plug it to the charger)
if it reacts, probably your battery ran out. try charging it, and when it's charged (or while it's charging) try to start the phone, or try to boot into fastboot (vol down + power)
If you can boot into fastboot, the phone is not bricked.
If it doesn't respond to charger or you can't boot into fastboot, then the phone is bricked, and you can send it to store to repair it...
(i had this last problem, and I sent my phone to the dealer to repair it.)
Click to expand...
Click to collapse
No, the phone does not respond to the charger as well. Did your's get bricked as well? and can bricked devices be repaired by reflashing with special programmable cables or they have to be replaced?
Thnx in advance
As I said, it should NOT have rebooted after writing S-ON. Mine didn't and is working fine
[email protected] said:
Guys, i wanted to get my phone repaired under warranty. I had rooted it and it was S-OFF. So i flashed the stock ROM and the radio, but while trying to make it back to S-ON, using rebranding, debranding and S-ON method given in the android development section, i think i bricked my phone. When i wrote the command "fastboot oem writesecureflag 3", the phone just turned off. Now it wont turn on, tried everything still no use. Plz help!!
Also, can i get it repaired under warranty still, as the phone does not turn on at all so i dont think there would be any way for htc to detect wether it was rooted or not.
Click to expand...
Click to collapse
Did exactly the same some time ago and got it repaired within a week without a problem.
Motherboard was replaced. Hope this helps.
EddyOS said:
As I said, it should NOT have rebooted after writing S-ON. Mine didn't and is working fine
Click to expand...
Click to collapse
But the post says that we have to write the reboot bootloader command.That's exactly what i did. It also said that if it doesn't after writing the command, the battery is to be removed and re-inserted and then we have to power on in bootloader mode!
http://forum.xda-developers.com/showthread.php?t=1322080
http://forum.xda-developers.com/showthread.php?t=1214965
http://forum.xda-developers.com/showthread.php?t=1302180
Its a fully brick, un'repairable at home. JTAG reflash in service center may help you.
I hate to say this:
I bricked my fone once.
Not the method you thit.
But the same problem..
Wouldn't turn on and no charging response..
I think your emc is deleted..
Then your phone is death..
The only reaponse i had was: putting the usb cable and connect to the pc.
Then you see something.
What i thit was: go back to the store and say
I was changing my phone at night and in the morning i turn on the phone and nothing happens.
The vodafone store sent my phone back to htc factory.
And i got a factory garantie.
They changed a new motherboard in my fone for free!
DON'T SAY THAT YOUR PHONE WAS ROOTED!
AND REMOVE THE SDCARD maybe you have some root stuff on it
bobsie41 said:
Did exactly the same some time ago and got it repaired within a week without a problem.
Motherboard was replaced. Hope this helps.
Click to expand...
Click to collapse
Thanx bro. I got really scared when my phone got bricked. Just one question so that i don't end up saying the wrong thing to the htc guys, what story did you make up?
[email protected] said:
But the post says that we have to write the reboot bootloader command.That's exactly what i did. It also said that if it doesn't after writing the command, the battery is to be removed and re-inserted and then we have to power on in bootloader mode!
Click to expand...
Click to collapse
When i bricked mine i followed instructions to the letter and it wasn't the first time i had been through the procedure. Your situation appears identical to mine and i guess we have just been unfortunate, a power blip perhaps?
Unfortunately yes, you are bricked but fortunately, htc will repair it for you as it is so totally lifeless they won't have a clue what you have been doing to it!
I guess that htc repair would have ways of reviving the device but just write them off due to the time constraints that they work under.
---------- Post added at 12:23 PM ---------- Previous post was at 12:20 PM ----------
[email protected] said:
Thanx bro. I got really scared when my phone got bricked. Just one question so that i don't end up saying the wrong thing to the htc guys, what story did you make up?
Click to expand...
Click to collapse
I told them that it wouldn't reboot after an ota update.
bobsie41 said:
When i bricked mine i followed instructions to the letter and it wasn't the first time i had been through the procedure. Your situation appears identical to mine and i guess we have just been unfortunate, a power blip perhaps?
Unfortunately yes, you are bricked but fortunately, htc will repair it for you as it is so totally lifeless they won't have a clue what you have been doing to it!
I guess that htc repair would have ways of reviving the device but just write them off due to the time constraints that they work under.
---------- Post added at 12:23 PM ---------- Previous post was at 12:20 PM ----------
I told them that it wouldn't reboot after an ota update.
Click to expand...
Click to collapse
Thnx again. I hope i'll get mine repaired as well. Will tell them that an OTA update did this. Although, came across many posts saying they followed the exact guide and bricked their phones!
bobsie41 said:
I told them that it wouldn't reboot after an ota update.
Click to expand...
Click to collapse
I also told them the same thing when i bricked my Sensation.
And the warranty coverd it.
I went today to see what's up with my phone, and it's coming today (after 6 working days) to the dealer where I bought my phone.
bobsie41 said:
Did exactly the same some time ago and got it repaired within a week without a problem.
Motherboard was replaced. Hope this helps.
Click to expand...
Click to collapse
The service told me that motherboard replaced...
Don't worry, if you have valid warranty, you'l get the phone fixed for free...
ico86 said:
I also told them the same thing when i bricked my Sensation.
And the warranty coverd it.
I went today to see what's up with my phone, and it's coming today (after 6 working days) to the dealer where I bought my phone.
The service told me that motherboard replaced...
Don't worry, if you have valid warranty, you'l get the phone fixed for free...
Click to expand...
Click to collapse
Alright, will take mine to service centre and get back with details of what happened. Thnx guys
I was following Timmaaas 'How To' guide to a tee when I got to step #5 and and did the Reboot to find that my phone is now bricked. I was racking my brain trying to understand what I did wrong and I realize that I used the wrong Boot.img file when I flashed it!
I was having issues during the entire process and realized it was because I was using the CyanogenMod One X ROM instead of the XL. This was causing me to get an 'Error 7' until I switched to the XL and everything downloaded fine. However, I completely forgot to replace the Boot.img and ended up flashing my phone with the One X boot.img instead of the XL!
The phone is not responding at all. I did have it plugged into the computer and after it became bricked my computer downloaded the Qualcomm USB drivers for 9006 but its still not responding at all.
Is there anything I can do? It seems like all I need to do is change that one boot file and I would be golden. Please keep in mind this is my first Root so if you know of a way to fix I would really appreciate it if you can teach me in simple terms if possible.
Thanks so much! I really appreciate all you guys do at XDA you help an enormous amount of people. A donation from me is on the way! :good:
EDIT: I kept messing with the power button trying to boot it over and over and finally it launched to HTC one entry screen with the red text for a little less then 1 second but then shut back off. Maybe this gives some hope?
You're gonna need to get a jtag repair done. There's just no way for you to get the device to the bootloader in order to flash the right boot.img because it won't boot due to you borking the boot partition.
Transmitted via Bacon
BrickedAmbitions said:
EDIT: I kept messing with the power button trying to boot it over and over and finally it launched to HTC one entry screen with the red text for a little less then 1 second but then shut back off. Maybe this gives some hope?
Click to expand...
Click to collapse
Are you able to issue adb commands? If you're seeing the splash screen then you may not be completely bricked. If the device is still showing as qualcommUSB then you're likely out of luck though.
nem1yan said:
Are you able to issue adb commands? If you're seeing the splash screen then you may not be completely bricked. If the device is still showing as qualcommUSB then you're likely out of luck though.
Click to expand...
Click to collapse
No I can't issue any commands. I guess its toast, oh well. How do I get the jtag repairs done?
nem1yan said:
Are you able to issue adb commands? If you're seeing the splash screen then you may not be completely bricked. If the device is still showing as qualcommUSB then you're likely out of luck though.
Click to expand...
Click to collapse
There's no way the phone can get to the bootloader, it ain't gonna happen with a broken boot partition.
BrickedAmbitions said:
No I can't issue any commands. I guess its toast, oh well. How do I get the jtag repairs done?
Click to expand...
Click to collapse
You need to find a jtag repairer in your area.
Transmitted via Bacon
Okay, so I was flashing full stock + unroot using WugFresh Bacon Root Toolkit.
It got up to flashing the RPM, completed that and then rebooted into bootloader.. It never rebooted it just shut down and didn't come back on.
Dead screen, can't reboot into bootloader, fastboot, normal reboot, nothing on screen at all ever, the charging LED doesn't even come on.
Device is not recognised on my computer at all, under any device name.
Took the back casing off, unhooked the battery and rehooked it back on again.. Nothing.
Thinking the phone is well and truly f*cked.
What are my options guys? Contact Oneplus customer service and play roulette to see if I actually get a response from them within a 3 month period and then have to face the gigantic cost of posting the phone back to them from Australia on the hopes of getting a new one? Or just buy a new phone, the S6 just came out so that's an option.
Lesson: don't use toolkits.
Anyway, give this a try:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
If that doesn't revive your phone nothing will. There's no point in contacting OnePlus about this unless you're happy to pay for whatever repairs are needed, this doesn't fall under warranty.
Transmitted via Bacon
timmaaa said:
Lesson: don't use toolkits.
Anyway, give this a try:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
If that doesn't revive your phone nothing will. There's no point in contacting OnePlus about this unless you're happy to pay for whatever repairs are needed, this doesn't fall under warranty.
Transmitted via Bacon
Click to expand...
Click to collapse
Yeah like I said earlier.. It isn't recognised via USB at all. Thanks anyway.
It wasn't a fault of the toolkit, it was the fault of the phone itself. I use it because it saves me time, who can be arsed typing that manually when you have a .bat to do it for you?
Stevles said:
Yeah like I said earlier.. It isn't recognised via USB at all. Thanks anyway.
Click to expand...
Click to collapse
Yeah, and many of the people who have successfully revived their phones using that method weren't able to recognise their phone via usb to start with either. But hey, I guess it isn't worth trying.
Transmitted via Bacon
timmaaa said:
Yeah, and many of the people who have successfully revived their phones using that method weren't able to recognise their phone via usb to start with either. But hey, I guess it isn't worth trying.
Transmitted via Bacon
Click to expand...
Click to collapse
"A hardware bricked OPO has nothing but a black screen (nothing ever comes on the screen, not even a boot logo), it might vibrate when a power button is pressed and held for 20 seconds, has no Recovery partition, no adb mode, and no fastboot partition. The device might be detected in Linux and you might be able to even send commands to it. In Windows, the bricked OPO should be detected as QHSUSB_BULK USB"
AS I SAID the device is not showing up on the computer, AT ALL. Under any device name.
It does not vibrate when I hold the power button for 20 seconds, it has no ADB, no fastboot, no nothing.
But hey, thanks for being an arsehole about it. Really appreciate it.
Stevles said:
"A hardware bricked OPO has nothing but a black screen (nothing ever comes on the screen, not even a boot logo), it might vibrate when a power button is pressed and held for 20 seconds, has no Recovery partition, no adb mode, and no fastboot partition. The device might be detected in Linux and you might be able to even send commands to it. In Windows, the bricked OPO should be detected as QHSUSB_BULK USB"
AS I SAID the device is not showing up on the computer, AT ALL. Under any device name.
It does not vibrate when I hold the power button for 20 seconds, it has no ADB, no fastboot, no nothing.
But hey, thanks for being an arsehole about it. Really appreciate it.
Click to expand...
Click to collapse
I know what a hard brick is. And as I said, many people who thought they were hard-bricked have revived their phones with that method. It isn't your usual detect-by-fastboot fix. Isn't it worth a try? Others in your situation have had success with it.
Plus, if your phone is actually 100% hard-bricked, why are you posting here? If that's the case there's absolutely nothing that can be done. You came here looking for help, I'm giving you the link to the one thing that has a chance of saving your phone.
Transmitted via Bacon
---------- Post added at 12:40 ---------- Previous post was at 12:39 ----------
Jessooca said:
Wugfresh is the one of the most reputable and is the most downloaded developer on all of XDA look it up. So suggesting not to use toolkits is ridiculous.
Send me a PM of your issues and I'll see if I can't get you back up and running... Provide me all the details of what all your phone does and does not do, etc... I've read all that you've said above, so I suppose just tell me what it DOES so if anything, Thanks
- Jessooca
---------- Post added at 06:32 PM ---------- Previous post was at 06:31 PM ----------
+1
Click to expand...
Click to collapse
It doesn't matter how reputable a toolkit is, they cause problems, this thread is a testament to that. You can find many threads just like this one in this very q&a section that describe very similar issues after using a toolkit.
Transmitted via Bacon
timmaaa said:
I know what a hard brick is. And as I said, many people who thought they were hard-bricked have revived their phones with that method. It isn't your usual detect-by-fastboot fix. Isn't it worth a try? Others in your situation have had success with it.
Plus, if your phone is actually 100% hard-bricked, why are you posting here? If that's the case there's absolutely nothing that can be done. You came here looking for help, I'm giving you the link to the one thing that has a chance of saving your phone.
Transmitted via Bacon
---------- Post added at 12:40 ---------- Previous post was at 12:39 ----------
It doesn't matter how reputable a toolkit is, they cause problems, this thread is a testament to that. You can find many threads just like this one in this very q&a section that describe very similar issues after using a toolkit.
Transmitted via Bacon
Click to expand...
Click to collapse
Actually in this case I'm almost 100% sure it was due to the fact I had just installed Oxygen OS and was reverting back to stock from it. Had nothing to do with the toolkit. Not to mention, I have never had any problems with this toolkit in the past and I would still recommend it to people who want to save them self from hassle and wasting time. Thanks anyway.
By the way, anyone reading this: Stay the hell away from OxygenOS. Nothing but dramas from it, it seems. Not forgetting to mention the fact it is literally just a stock version of Lollipop anyway! Better off with CM12S or BlissPop or any of the CFW's out there.
Stevles said:
Actually in this case I'm almost 100% sure it was due to the fact I had just installed Oxygen OS and was reverting back to stock from it. Had nothing to do with the toolkit. Not to mention, I have never had any problems with this toolkit in the past and I would still recommend it to people who want to save them self from hassle and wasting time. Thanks anyway.
By the way, anyone reading this: Stay the hell away from OxygenOS. Nothing but dramas from it, it seems. Not forgetting to mention the fact it is literally just a stock version of Lollipop anyway! Better off with CM12S or BlissPop or any of the CFW's out there.
Click to expand...
Click to collapse
I agree that there are better ROMs available for this phone, but that's just our opinion, heaps of people have been looking for a stock aosp experience on this phone and I think Oxygen is as close as you could get. As for the ROM itself causing problems, I don't think that's it. I flashed it to test it out and went back to my previous ROM without a single issue (as have many others). I think it's a matter of taking the care to flash the right firmware/modem before reverting back to whatever ROM was running previously, otherwise it's kinda asking for trouble.
So have you tried the unbrick method I linked you to? I'm not saying it's definitely going to fix your problem. What I'm saying is there have been several cases of this phone showing all the signs of being hard bricked, without it actually being hard bricked, and that's the fix that saved those phones. You might be hard bricked, or your phone might fall into the category that I just mentioned, but at this point anything has to be worth a try.
Transmitted via Bacon
timmaaa said:
I agree that there are better ROMs available for this phone, but that's just our opinion, heaps of people have been looking for a stock aosp experience on this phone and I think Oxygen is as close as you could get. As for the ROM itself causing problems, I don't think that's it. I flashed it to test it out and went back to my previous ROM without a single issue (as have many others). I think it's a matter of taking the care to flash the right firmware/modem before reverting back to whatever ROM was running previously, otherwise it's kinda asking for trouble.
So have you tried the unbrick method I linked you to? I'm not saying it's definitely going to fix your problem. What I'm saying is there have been several cases of this phone showing all the signs of being hard bricked, without it actually being hard bricked, and that's the fix that saved those phones. You might be hard bricked, or your phone might fall into the category that I just mentioned, but at this point anything has to be worth a try.
Transmitted via Bacon
Click to expand...
Click to collapse
Read through it and the sole problem of why it won't work is that there is no communication with my phone via my computer at all. The point of that tutorial is to unbrick your device by manipulating what your computer see's as the device (Qualcomm generic hardware ID being reported) unfortunately I can't even see that. I think it's just a lost cause unfortunately. But thank you for taking an interest.
UPDATE: Wow what do you know? After trying for an hour of powering on/off and trying to fastboot and flashmode and all that jazz and no luck, tried it on my laptop and sure enough it popped up with the Qualcomm generic driver ID. Whole bunch of screwing around and now it is booting into ColosOS. Thanks guys for the links and offers of help!
Stevles said:
Read through it and the sole problem of why it won't work is that there is no communication with my phone via my computer at all. The point of that tutorial is to unbrick your device by manipulating what your computer see's as the device (Qualcomm generic hardware ID being reported) unfortunately I can't even see that. I think it's just a lost cause unfortunately. But thank you for taking an interest.
UPDATE: Wow what do you know? After trying for an hour of powering on/off and trying to fastboot and flashmode and all that jazz and no luck, tried it on my laptop and sure enough it popped up with the Qualcomm generic driver ID. Whole bunch of screwing around and now it is booting into ColosOS. Thanks guys for the links and offers of help!
Click to expand...
Click to collapse
Lol, I knew that was going to get your phone up and running again [emoji14]
Very glad to see that your phone has been revived from the dead
Transmitted via Bacon
timmaaa said:
Lol, I knew that was going to get your phone up and running again [emoji14]
Very glad to see that your phone has been revived from the dead
Transmitted via Bacon
Click to expand...
Click to collapse
You earn a medal!
You can even help people who don't want to get helped
Way to go, Tim
Same thing happen to me whike swithing back to stoc. After using oxygen but i m flashing the factory images flashall.bat but after this hard brick my device after changing or trying able to connect my like bulkusb kind of in device manager and use one plus one recovery toolkit 1.0 it will brink my complete dead one plus one to life try buddy
rakesh595160 said:
Same thing happen to me whike swithing back to stoc. After using oxygen but i m flashing the factory images flashall.bat but after this hard brick my device after changing or trying able to connect my like bulkusb kind of in device manager and use one plus one recovery toolkit 1.0 it will brink my complete dead one plus one to life try buddy
Click to expand...
Click to collapse
Yeah, I'm just gonna wait for the CM12S OTA. Tried most every other ROM and was not impressed. This being said, I'm still buying an S6 in two days. Will be keeping my OPO to satisfy my ROM flashing/android manipulating needs and using the S6 for everything else a smart phone offers
Stevles said:
UPDATE: Wow what do you know? After trying for an hour of powering on/off and trying to fastboot and flashmode and all that jazz and no luck, tried it on my laptop and sure enough it popped up with the Qualcomm generic driver ID. Whole bunch of screwing around and now it is booting into ColosOS. Thanks guys for the links and offers of help!
Click to expand...
Click to collapse
How did u get it unbricked / ur PC to recognize ur OPO? Im having the same hard brick issue... my OPO is completely dead, doesnt even charge at all too. :crying:
MatLiamSousa said:
How did u get it unbricked / ur PC to recognize ur OPO? Im having the same hard brick issue... my OPO is completely dead, doesnt even charge at all too. :crying:
Click to expand...
Click to collapse
Try plugging it into a different computer.. That was what worked for me.
Don't know if it was necessary (in fact I am almost certain it isn't) but In my haste I took off the back cover and unscrewed a thousand small screws with my jewellers kit and unplugged the battery and plugged it back in. Like I said, not necessary.
Even if it doesn't look like it's charging.. If you can't see it on a computer at all then keep it on charge for a few hours anyway.. It can't hurt.
Best of luck!
Stevles said:
Okay, so I was flashing full stock + unroot using WugFresh Bacon Root Toolkit.
It got up to flashing the RPM, completed that and then rebooted into bootloader.. It never rebooted it just shut down and didn't come back on.
Dead screen, can't reboot into bootloader, fastboot, normal reboot, nothing on screen at all ever, the charging LED doesn't even come on.
Device is not recognised on my computer at all, under any device name.
Took the back casing off, unhooked the battery and rehooked it back on again.. Nothing.
Thinking the phone is well and truly f*cked.
What are my options guys? Contact Oneplus customer service and play roulette to see if I actually get a response from them within a 3 month period and then have to face the gigantic cost of posting the phone back to them from Australia on the hopes of getting a new one? Or just buy a new phone, the S6 just came out so that's an option.
Click to expand...
Click to collapse
hello buddy,
i got same situation like yours. but the only different thing is when i connect my opo to my laptop and press the power button with vol up key it connects to my laptop showing QHUSB_BULK. I update it with ANDROID ADB INTERFACE and it does but thats it nothing else. i cant go fastboot or adb.
CAN YOU PLEASE tell me how you fixed your super hard bricked opo like mine...
thank you.
dewan555 said:
hello buddy,
i got same situation like yours. but the only different thing is when i connect my opo to my laptop and press the power button with vol up key it connects to my laptop showing QHUSB_BULK. I update it with ANDROID ADB INTERFACE and it does but thats it nothing else. i cant go fastboot or adb.
CAN YOU PLEASE tell me how you fixed your super hard bricked opo like mine...
thank you.
Click to expand...
Click to collapse
http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
From previous comment on thread.
dewan555 said:
hello buddy,
i got same situation like yours. but the only different thing is when i connect my opo to my laptop and press the power button with vol up key it connects to my laptop showing QHUSB_BULK. I update it with ANDROID ADB INTERFACE and it does but thats it nothing else. i cant go fastboot or adb.
CAN YOU PLEASE tell me how you fixed your super hard bricked opo like mine...
thank you.
Click to expand...
Click to collapse
No that is exactly like what happened to mine. Follow the guide to the letter and it'll fix it up if you did it right, it fixed mine.
Best of luck!
help plz
The step to install color fails every time. Suggestion plz....
Here is the log(both in windows 8.1 & xp) plz help...
8974_msimage.mbn: OK
dynamic_nvbk.bin: OK
emmc_appsboot.mbn: OK
gpt_backup0.bin: OK
gpt_backup0_64G.bin: OK
gpt_main0.bin: OK
gpt_main0_64G.bin: OK
userdata.img: FAILED
userdata_64G.img: FAILED
rawprogram0.xml: OK
rawprogram0_64G.xml: OK
NON-HLOS.bin: OK
MPRG8974.mbn: OK
rpm.mbn: OK
sbl1.mbn: OK
sdi.mbn: OK
static_nvbk.bin: OK
tz.mbn: OK
boot.img: FAILED
cache.img: OK
persist.img: FAILED
recovery.img: FAILED
mobasser said:
The step to install color fails every time. Suggestion plz....
Here is the log(both in windows 8.1 & xp) plz help...
8974_msimage.mbn: OK
dynamic_nvbk.bin: OK
emmc_appsboot.mbn: OK
gpt_backup0.bin: OK
gpt_backup0_64G.bin: OK
gpt_main0.bin: OK
gpt_main0_64G.bin: OK
userdata.img: FAILED
userdata_64G.img: FAILED
rawprogram0.xml: OK
rawprogram0_64G.xml: OK
NON-HLOS.bin: OK
MPRG8974.mbn: OK
rpm.mbn: OK
sbl1.mbn: OK
sdi.mbn: OK
static_nvbk.bin: OK
tz.mbn: OK
boot.img: FAILED
cache.img: OK
persist.img: FAILED
recovery.img: FAILED
Click to expand...
Click to collapse
Instead of posting this multiple times in various threads (double posting is against the rules) you should ask this question in the unbrick thread.
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
After getting update I was trying to flash TWRP and was having troubles. The first one was something to do with the partitions. After following a guide to change the slot I then went and flashed TWRP and now I'm stuck in a boot loop with the one plus animation going round slowly.
I'm currently looking in to the msm tool but I'm in a panic as I cant get into fastboot mode. Does anyone have any advice. Have I lost everything. Did I brick it.
Thank you
try to press volume up + volume down + power button
Just use the MSM tool, youre using the EDL mode there. Its going to be alright, I had it bricked like that the first day i bought the phone.
Limetak said:
Just use the MSM tool, youre using the EDL mode there. Its going to be alright, I had it bricked like that the first day i bought the phone.
Click to expand...
Click to collapse
Thanks. I did use it. But I had problems connecting to it. Turns it was the drivers needing updating. But still it was a bit of a panic. Thought I had completely ruined it.
I'm wondering though does this tool re lock the bootloader?
JohnsNotHome said:
Thanks. I did use it. But I had problems connecting to it. Turns it was the drivers needing updating. But still it was a bit of a panic. Thought I had completely ruined it.
I'm wondering though does this tool re lock the bootloader?
Click to expand...
Click to collapse
Yes, it does.
Fortunately this is OP not Xiaomi, so you don't have to wait 4 years to unlock it again if you want to.
loshabih said:
try to press volume up + volume down + power button
Click to expand...
Click to collapse
This is also what I would suggest. Hold that combo to get to bootloader. You may need to hold that for a few seconds to power down the phone, then hold them again to boot to bootloader.
---------- Post added at 09:11 AM ---------- Previous post was at 09:06 AM ----------
JohnsNotHome said:
After getting update I was trying to flash TWRP and was having troubles. The first one was something to do with the partitions. After following a guide to change the slot I then went and flashed TWRP and now I'm stuck in a boot loop with the one plus animation going round slowly.
I'm currently looking in to the msm tool but I'm in a panic as I cant get into fastboot mode. Does anyone have any advice. Have I lost everything. Did I brick it.
Click to expand...
Click to collapse
You haven't been specific about that guide, or what steps you took exactly. But you shouldn't have to mess with changing slots to install TWRP. There are a couple ways to retain TWRP after an update. But again, without more details, it is impossible to tell what you have done, or to what extent you need to do exactly to get it up and running. But this phone is pretty hard to permanently brick, since we have the unbrick tool.
Hi,
You do not need to have the fastboot mode. Turn off your phone, on black screen hold vol up for 6-10 sec and plug usb cabel. After that make sure that your pc can see the phone, then run as admin the msm tool. It always worked for me for OP3T, OP5T and now for OP7Pro.
Full instraction and the msm tool is here.
Hope you will bring back to life your phone.
Thank you so much. !
Limetak said:
I had it bricked like that the first day i bought the phone.
Click to expand...
Click to collapse
And me thinking, I was the only one Who bricked his Phone the first day :silly:
EDIT: I fixed it and will explain you how i did.
So, what was my issue ?
I was on rooted DP4. I was trying some things, to see what is possible and what wasn't. I uninstalled magisk using the manager and that was a terrible mistake lmao.
After that the phone rebooted and it never start again. I was all time stucked at the bootloader warning screen. I tried to start in fastboot, edl or recovery but it was stucked again and again...
I was really not able to boot anything.
How i fixed it ?
I thought the boot partition was ****ed, and i was right.
After arround 10 hours stucked on the bootloader warning the phone got shudown because battery was empty.
I charged it for 20 mins, the phone was power on but was stucked on the warning again. I tried to start the phone fastboot and wow it got damn worked !!!!
I flashed the stock boot.img file, start phone to recovery and did a hard reset and reboot.
yay the phone booted.
To resume, that was an idiot mistake, and i was not able to fix it until battery was empty. But i fixed it, so all good.
if someone do the same mistake, that's the solution
Have you tried the MSM tool: https://forum.xda-developers.com/oneplus-8/how-to/op8-unbrick-tool-to-restore-device-to-t4093043 ?
ycavan said:
Have you tried the MSM tool: https://forum.xda-developers.com/oneplus-8/how-to/op8-unbrick-tool-to-restore-device-to-t4093043 ?
Click to expand...
Click to collapse
Useless, can't go to fastboot, recovery or edl. I'm really stuck on the bootloader warning.
I will send the phone to OnePlus Repair Center
guys ? will oneplus accepts the phone for the repair center if the bootloader is unlocked ? i really hope, don't want to loose 600 euros
Try this hold power and volume as long as phone start to reboot
---------- Post added at 04:46 PM ---------- Previous post was at 04:45 PM ----------
volume up
dziello said:
Try this hold power and volume as long as phone start to reboot
---------- Post added at 04:46 PM ---------- Previous post was at 04:45 PM ----------
volume up
Click to expand...
Click to collapse
I already said it doesn't work, please read all messages next time.
It's stuck on the bootloader warning screen. Everytime i try to start the phone in fastboot or in recovery the phpone get stucked on the warning screen.
Matteo said:
I already said it doesn't work, please read all messages next time.
It's stuck on the bootloader warning screen. Everytime i try to start the phone in fastboot or in recovery the phpone get stucked on the warning screen.
Click to expand...
Click to collapse
This reboot is hard reboot and when I have problem to boot to edl this method help me. This is only a idea you can try but there is no reason to be nasty and sarcastic.
dziello said:
This reboot is hard reboot and when I have problem to boot to edl this method help me. This is only a idea you can try but there is no reason to be nasty and sarcastic.
Click to expand...
Click to collapse
Yes i was sarcastic and that's normal.
My phone is soft bricked, i can't boot anything at all.
Press buttons to boot to fastboot, edl, recovery or anything else don't work. I can't pass the warning screen. For exemple, i don't touch the phone since some hours, and i'm still on the warning screen. I can't do anything.
So, the real swner i want know is, will OnePlus accepts my phone at the repair center if the bootloader is unlocked ? I hope you will know for that dude
Have a nice day
Please help
I literally just had this problem 2 days ago, I was so scared. What I did to get my T-Mobile OnePlus 8 back to working state was MSM download Tool. At first, nothing works. Took me like 1 hour to figure it out. So went back to XDA to the "Convert to global WIP" THREAD and followed the MSM steps. I just hold on to volume up and down after 6 seconds then plug while still doing it and it finally connected. I really thought I was screwed. This happened when I was trying to convert to Global fastboot ROM. I have 3 OnePlus chargers, two from old OnePlus 7 Pro and one that came with my 8. I'm not going to flash anything again. I'll just stick with the T-Mobile software and wait for them to push out updates. I tried converting for 2 weeks straight and no luck no matter what ROM I used & fastboot drivers.
hold all three buttons for 15 seconds
will close the thread, sadly you are all saying the same thing. Your solutions don't work as i said like 3 or 4 times.
I can't boot to any mode, i'm all time stuck at the warning screen. Don't care if it's fastboot, edl or recovery, can't boot anything at all.
Matteo said:
will close the thread, sadly you are all saying the same thing. Your solutions don't work as i said like 3 or 4 times.
I can't boot to any mode, i'm all time stuck at the warning screen. Don't care if it's fastboot, edl or recovery, can't boot anything at all.
Click to expand...
Click to collapse
People are obviously just trying to help. [Closed] as per your request. Unlocking the bootloader with OnePlus does not void warranty so good luck with your RMA request.
THREAD RE-OPENED on request of OP @Matteo
Hello guys, sorry for yesterday, i was really sad that my phone died for an idiot mistake.
I fixed it some mins ago, and ask for mod to reopen the thread. i will edit the main post to explain with details what happened and how i fixed it.
have a nice day guys