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
Was trying to revert my phone to stock. I pick up my phone today after where I left it and now after holding down the volume down button and connecting USB it wont even go into download mode. Tried plugging it into the wall nothing happened. Phone wont turn on either. Help!
Mod edited
Battery dead?
The battery shouldn't have anything to do with not being able to enter download mode.
roboman342 said:
The battery shouldn't have anything to do with not being able to enter download mode.
Click to expand...
Click to collapse
Correct, but if the phone doesn't turn on at all, there's probably some other problem. You may not be accessing download mode because of a bad cable, bad usb port on phone, bad usb port on computer, etc.
If your phone is dead even when you try to charge it, you may have a bad usb port that is preventing it from charging or getting into download mode. So if you've been charging it but your battery is still dead, you can probably narrow down the issue to either cable or phone's usb port...
I'm going to guess that you weren't flashing the device with the battery in the phone, causing all of the failed flashes. Since it seems like you tried to flash several times, I'm also guessing that you never paid attention to where it stopped, or bothered to see what was going on until now, and it is very possible that you do have a brick if it failed during the flash of boot.bin and/or sbl.bin. If it did, then your only options are to try a jig to get into download mode, the unbrickable mod, insurance, or buy a new phone.
Cleaned up thread and edited op. Prob a good idea not to bash ur phone and the devs when asking for help
Papa Smurf151 said:
Cleaned up thread and edited op. Prob a good idea not to bash ur phone and the devs when asking for help
Click to expand...
Click to collapse
THANK YOU! Was wondering about the logic(or lack there of) behind that.
---------- Post added at 10:17 PM ---------- Previous post was at 10:13 PM ----------
imnuts said:
...If it did, then your only options are to try a jig to get into download mode, the unbrickable mod, insurance, or buy a new phone.
Click to expand...
Click to collapse
I've only successfully completed the jig once... Not easy stuff.
Hi all,
I got my AT&T HTC One X today. 1.85. I rooted it successfully and went about unlocking the bootloader following these instructions:
http://forum.xda-developers.com/showthread.php?t=1671396
I got to the point where you exchange the original boot file for the original. When I used the command "adb reboot bootloader" to boot into the bootloader screen my phone went black and has not worked since. No combination of button holding over any amount of time has caused any sort of reaction. Although, oddly enough, holding down the power button makes my computer alternate between the "device connected" and "device disconnected" sounds, so I guess it's not completely dead? ADB doesn't detect the phone at any time.
I think that I screwed up with the hex editing, which explains why it's not starting up - I might have destroyed one of the files it uses to boot. Is there any way to put the original file back, or do I have a brick? Thanks in advance.
KR_Badonkadonk said:
Hi all,
I got my AT&T HTC One X today. 1.85. I rooted it successfully and went about unlocking the bootloader following these instructions:
http://forum.xda-developers.com/showthread.php?t=1671396
I got to the point where you exchange the original boot file for the original. When I used the command "adb reboot bootloader" to boot into the bootloader screen my phone went black and has not worked since. No combination of button holding over any amount of time has caused any sort of reaction. Although, oddly enough, holding down the power button makes my computer alternate between the "device connected" and "device disconnected" sounds, so I guess it's not completely dead? ADB doesn't detect the phone at any time.
I think that I screwed up with the hex editing, which explains why it's not starting up - I might have destroyed one of the files it uses to boot. Is there any way to put the original file back, or do I have a brick? Thanks in advance.
Click to expand...
Click to collapse
I bricked mine the same way. Does it show a light when plugged into a charger? If not it's a bricked up bricky brick. Sorry
gunnyman said:
I bricked mine the same way. Does it show a light when plugged into a charger? If not it's a bricked up bricky brick. Sorry
Click to expand...
Click to collapse
Nope, no light.
Well...crap.
KR_Badonkadonk said:
Nope, no light.
Well...crap.
Click to expand...
Click to collapse
again I'm sorry. I feel your pain. The exact thing happened to me.
If by boot replacing boot thing you are referring to mmcblk0p4, that means you did not edit it correctly and sent it to the phone or sent it to the wrong partition(unlikely). Hex editing should always be done with EXTREME care, and if your not 100% sure u did it right you can always find someone here that can check it or do the edit for you uf needed. Sorry about the brick, that really sucks!
---------- Post added at 05:08 PM ---------- Previous post was at 05:03 PM ----------
Btw, if you just bought it, bring it back and tell them after charging it last night you woke up to THIS.
(Then listen to a couple posts accusing you of making phones too expensive, and being responsible for your actions)
You learned a important lesson here, and I''ll chip in my $0.0001 to getcha back up and running again:beer:
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
The problem is:
No download mode
No recovery
no fastboot mode
When connecting to the current does not turn on the screen and sometimes it turns on but the load does not rise from 0% and the red LED blinks after a moment stops blinking and no longer turns on the screen, when connecting it to the pc it is detected but with battery it does not light the screen, when removed the battery lights up with a non-battery alert and up comes out fastboot mode started. I have tried with other batteries and still nothing happens.
JhonMtz said:
The problem is:
No download mode
No recovery
no fastboot mode
When connecting to the current does not turn on the screen and sometimes it turns on but the load does not rise from 0% and the red LED blinks after a moment stops blinking and no longer turns on the screen, when connecting it to the pc it is detected but with battery it does not light the screen, when removed the battery lights up with a non-battery alert and up comes out fastboot mode started. I have tried with other batteries and still nothing happens.
Click to expand...
Click to collapse
Sounds like it's dead/hardware failure since youve tried different batteries.
Did you do anything to it like root , rom, etc before this happened? Or was it all stock?
Sent from my iPhone using Tapatalk
hyelton said:
Sounds like it's dead/hardware failure since youve tried different batteries.
Did you do anything to it like root , rom, etc before this happened? Or was it all stock?
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
I got a successful root but when I try to downgrade lollipop to kitkat my pc is shut down and the process is not complete.
Something like that happens: www . youtube.com/watch?v=6DVHQvcAVwQ
JhonMtz said:
I got a successful root but when I try to downgrade lollipop to kitkat my pc is shut down and the process is not complete.
Something like that happens: www . youtube.com/watch?v=6DVHQvcAVwQ
Click to expand...
Click to collapse
You would have to replace the motherboard.
Sent from my iPhone using Tapatalk
hyelton said:
Sounds like it's dead/hardware failure since youve tried different batteries.
Did you do anything to it like root , rom, etc before this happened? Or was it all stock?
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
hyelton said:
You would have to replace the motherboard.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Another possibility is not there?
JhonMtz said:
Another possibility is not there?
Click to expand...
Click to collapse
There may be an unbrick guide in the general section to do a Pinout which will still require taking apart the phone and it would bring back download mode.
Sent from my iPhone using Tapatalk
hyelton said:
There may be an unbrick guide in the general section to do a Pinout which will still require taking apart the phone and it would bring back download mode.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Could you give me the link? I find it difficult to find some terms in English and it would be difficult to find the right one.
JhonMtz said:
Could you give me the link? I find it difficult to find some terms in English and it would be difficult to find the right one.
Click to expand...
Click to collapse
Theres a thread somewhere here but couldnt find it, But this is the same - http://forum.gsmhosting.com/vbb/f49...ts-fix-qhsusb-bulk-_-qualcomm-9008-a-2029025/
hyelton said:
Theres a thread somewhere here but couldnt find it, But this is the same - http://forum.gsmhosting.com/vbb/f49...ts-fix-qhsusb-bulk-_-qualcomm-9008-a-2029025/
Click to expand...
Click to collapse
Thank you very much, I'll try.
JhonMtz said:
The problem is:
No download mode
No recovery
no fastboot mode
When connecting to the current does not turn on the screen and sometimes it turns on but the load does not rise from 0% and the red LED blinks after a moment stops blinking and no longer turns on the screen, when connecting it to the pc it is detected but with battery it does not light the screen, when removed the battery lights up with a non-battery alert and up comes out fastboot mode started. I have tried with other batteries and still nothing happens.
Click to expand...
Click to collapse
There is another possibility. Try another cord. The original cords after a while can be very finicky. Mine was. Make sure the next cord you try is definitely a fast charging data sync cable. Your best best is another of v10 cord. If that doesn't work, then you do indeed have a catastrophic hardware failure. And there is currently no fix 100% fix. There are the methods that the other posters mentioned but if those dont work, then your board is shot. Also, after trying the new cord. Reinstall the lg drivers on your pc.