Related
Hello!
Okay, so the weirdest thing has happened with me. My Nexus S (i9023) was working absolutely fine till last evening when it ran out of battery. After I came back home, I put it for charging and switched it on.
For the first few time, nothing would show except the USB connected/ disconnected screen which appears everytime you plug your phone in. I thought maybe it was just being weird, so I took out the battery and booted it up again. This time I am just stuck at the Google Logo! It is not going ahead.
I can enter CWM Recovery. However, I cannot mount sd card or usb storage or anything for that matter. If I try and install through .zip it says 'e can't mount sd card'. I can't format my sd card either, same problem of can't mount. I thought if I tried pushing a ROM in by ADB that might work.. It did transfer the file it showed that in the cmd window. However, CWM refuses to mount my sd card or my usb storage.
So basically, in essence, I'm locked out of my Nexus! Please please help. I'm really lost and confused now.
Thanks so much.
Alex
Similar problems below in this thread with solutions.
Let your phone sit for an hour with the battery out, Download Wug's Nexus Toolkit from the development section, download drivers from there and install stock boot img then re-root.
I have never seen it before but seems like this prob is coming up a lot lately. It can be fixed. Good luck.
Sent from my Galaxy Nexus using Tapatalk 2
Nexism said:
Similar problems below in this thread with solutions.
Let your phone sit for an hour with the battery out, Download Wug's Nexus Toolkit from the development section, download drivers from there and install stock boot img then re-root.
I have never seen it before but seems like this prob is coming up a lot lately. It can be fixed. Good luck.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thanks for your reply. I'm starting now. I have a doubt, how do I install stock? Since I can't seem to be able to mount anything..
"It can be fixed" - few words have given me this much hope in my life! Thanks a lot!
EDIT: I guess you mean flash through ADB right? Okay, let me try that. I really hope you are right. Some of those other problems lead to paying up! Ouch.
Hey! I just tried using WUGS.. for some reason it does not make the final boot and instead says: 'Fastboot Status - FAILWrite Fail' -- oh god.. I'm trying it again now..
Is there any other way out? :/
Okay, so now my recovery is also gone after using WUGS.. oh man. And the phone isn't starting up. Please please please help? I'm getting really desperate now.
EDIT: And it sucks that I can't post in the WUGS thread (http://forum.xda-developers.com/showthread.php?t=1766475) because I have less than 10 posts! fml.
can you boot into fastboot? If so then itnwasnthe same prob I had when I wiped my phone and SD in recovery. If you can boot into fastbootnthen makensurenyou leave the batt out format least an hour. If you installed Wug's drivers the bottom left corner ofnfastboot should give a message.
Sent from my Galaxy Nexus using Tapatalk 2
Nexism said:
can you boot into fastboot? If so then itnwasnthe same prob I had when I wiped my phone and SD in recovery. If you can boot into fastbootnthen makensurenyou leave the batt out format least an hour. If you installed Wug's drivers the bottom left corner ofnfastboot should give a message.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yes, I can get into fastboot - i'm leaving the battery out now - do you think i should try
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
and then flash everything again?
There is always a way to recover the nexus right? Even if it is hardbricked, right?
I really really appreciate your help.
I too have this problem but after a lot of battery pulls it does eventually start up. It just started happening all of a sudden. Ive heard that heating it up with a hair dryer or heatgun can help and also re-locking and un-locking the boot loader can help as it wipes the card. Could be worth a try.
Any luck Someone? I know it sux big time to feel like your phone is bricked. I am not a dev or expert but it sounds like the prob I had last week, when I posted no one replied so I ordered a GNex thinking all was lost. Before I activated my new phone I felt like I had to fix my nexus before getting started on my new phone and that's my situation. I don't want you to feel like the community has forgot you and thats why I'm trying to help. Were you able to get Wug's Toolkit to recognize your phone after leaving the batt out? I don't know why but I think that's the key. I had to leave mine overnight 'cause I don't have a PC and the next day at my friends house when I plugged the USB in I got that message at the bottom of fast boot "system normal" or something to that effect. Once recognized the stock boot IMG is what you need.
ANY ONE ELSE WHO HAS HAD THIS OR A SIMILAR ISSUE PLEASE GIVE SOME ADVICE. LET'S NOT LEAVE A COMMUNITY MEMBER WITH A LIFELESS PIECE IF PLASTIC. THANKS FORUM.
To set your mind at ease yes, I believe as long ad you have access to fastboot your nexus can be saved.
Sent from my Galaxy Nexus using Tapatalk 2
sounds to me like a hardware issue, since you haven't changed software and it seems like a brick. try flashing stock rom via fastboot, you should be able to google around how you can do that.
Blo0dyyy said:
sounds to me like a hardware issue, since you haven't changed software and it seems like a brick. try flashing stock rom via fastboot, you should be able to google around how you can do that.
Click to expand...
Click to collapse
Hi, if I'm not wrong essentially what WUG does automatically is what you do by fastboot (erase bootloader, cache, system.. and then flash all of them back) in both system fails to wipe and refuses to be flashed again (flashwrite error).
I don't want to lock it and then unlock it again because I read in other threads that it might lead to a permanent lock with an error for subsequent unlocking - that would leave me completely out.
Anyway, let's see - I've given it to someone to check it up. I'll keep you guys posted. He said he wanted to repartition the sd card.
My intuition says: hardware problem!
So I tried Odin today - and that also did not work it refused to flash the ROM. In the process I somehow managed to mess up the bootloader such that the phone would have some two lights on randomly when I switch on. It doesn't go into download mode either. I next plan to use JTAG to get the bootloader back and then reflash everything. Hopefully, that should sort things out. The Resurrection tool is amazing! I'll keep you guys posted.
Get it going someone?
Sent from my Galaxy Nexus using Tapatalk 2
I have the same problem as you, with the added difficulty of my phone not being recognized by anything other than fastboot. No ADB commands will function. It was charging, rebooted itself into a bootloop, and I have been struggling with it ever since. It is currently a worthless piece of plastic, my favorite phone ever, gone.
I can wipe and re-write recovery all that I want, but it seems as if the sdcard partition that /system and some other stuff writes too is either corrupted or physically damaged. Every time I flash it all via fastboot it all goes as stated, but gives me a fail message on the last two partitions and never allows me to actually write a new ROM or boot image. I wanted to try ODIN but can't seem to get it to recognize my phone in download mode...
Let me know if you have any success or progress!
someone. said:
So I tried Odin today - and that also did not work it refused to flash the ROM. In the process I somehow managed to mess up the bootloader such that the phone would have some two lights on randomly when I switch on. It doesn't go into download mode either. I next plan to use JTAG to get the bootloader back and then reflash everything. Hopefully, that should sort things out. The Resurrection tool is amazing! I'll keep you guys posted.
Click to expand...
Click to collapse
I myself am experiencing the same problem.... Did your cell got fixed.....?? Did JTAG worked kindly keep us posted em really concerned about it... coz your solution might get me some where or else i hav completely lost my phone ;(
Get it going someone?
Click to expand...
Click to collapse
Hey Nexism! Sorry for the late reply - things've been busy.
The JTAG is giving an internal voltage for some reason - so I've sent it for repair. It'll be repaired by tomorrow or so.. I'm then going to set it back up. It's all already soldered and all, just waiting for the JTAG. I think I've understood how this thing works now. So yeah, I'm hoping it's all sorted. Thanks a lot for your concern man.
I have the same problem as you, with the added difficulty of my phone not being recognized by anything other than fastboot.
Click to expand...
Click to collapse
Well my phone went blank - no fastboot mode - no download mode - no nothing - when i'd put the battery in randomly two of the four front lights would come on.. JTAG is going to solve the problem hopefully.
someone. said:
Hey Nexism! Sorry for the late reply - things've been busy.
The JTAG is giving an internal voltage for some reason - so I've sent it for repair. It'll be repaired by tomorrow or so.. I'm then going to set it back up. It's all already soldered and all, just waiting for the JTAG. I think I've understood how this thing works now. So yeah, I'm hoping it's all sorted. Thanks a lot for your concern man.
Well my phone went blank - no fastboot mode - no download mode - no nothing - when i'd put the battery in randomly two of the four front lights would come on.. JTAG is going to solve the problem hopefully.
Click to expand...
Click to collapse
So ladies and gentleman, JTAG also failed - apparently something was wrong with the sd card only. I got my motherboard replaced - luckily the guy I went to knew someone and Samsung and charged me Rs. 4,000 as opposed to the Rs. 8500 quoted by the Samsung Service Centre. Oh well.
Back on my Nexus now. XD
someone. said:
So ladies and gentleman, JTAG also failed - apparently something was wrong with the sd card only. I got my motherboard replaced - luckily the guy I went to knew someone and Samsung and charged me Rs. 4,000 as opposed to the Rs. 8500 quoted by the Samsung Service Centre. Oh well.
Back on my Nexus now. XD
Click to expand...
Click to collapse
I am with the same problem here... I cant turn off my phone or it get stuck in pre-boot phase. Acess recovery and cant mout sd card. Using last stable cm 10.
I think my sdcar is dead.
Same problem here. Around 8 out of 10 times I get stuck on the Google logo, 8 out of 10 times in recovery I can't mount SD card as well. And if I successfully boot, Media wakelocks and my battery drains in sleep as fast as if the screen were on. Please help.
For me I first noticed that my apps weren't using the SD partition. Tried to mount normally (fully loaded ROM) (ROM is SlimBean Beta2), but it would not mount. Went into CWM and tried to mount in there, but it would not work. tried to "Format /sdcard" but "Error mounting /sdcard". My phone still boots and runs fine, but I just don't have access to the SD partition. I don't want to do anything because I need my phone for business. Is there any PROVEN way to fix this yet?
Hi there,
Today I tried to get back from cm12 to stock rom. I flashed, then tried to reboot ... nothing.
The phone is absolutely dead. No light when connected to power, no vibration when pressing the power button, no fast boot, no recovery mode. I tried to press power button over one minute, I tried to press for 20 seconds five times... nothing.
The device is absolutely dead. "adb devices" / "fastboot devices" show nothing, my Mac does not even see anything on the usb-port.
I cannot imagine how this is even possible. Is it really possible to destroy a device with flashing?
Has anybody have a hint for me?
S.
It's entirely possible to brick a device with flashing, in fact it's the most likely way to brick a device. Exactly what did you flash? And using what method?
Transmitted via Bacon
I used the method described here (xda-dev forum) with the stock rom from cygn.com : cm-11.0-XNPH44S-bacon-signed-fastboot.zip
all the flashes went fine, then I gave : "fastboot reboot" and got back " rebooting... finished. total time 0.005s". (And a black screen)...
What a pitty
McSvenster said:
I used the method described here (xda-dev forum) with the stock rom from cygn.com : cm-11.0-XNPH44S-bacon-signed-fastboot.zip
all the flashes went fine, then I gave : "fastboot reboot" and got back " rebooting... finished. total time 0.005s". (And a black screen)...
What a pitty
Click to expand...
Click to collapse
Did you use a toolkit or did you do it manually?
//edit
Wow somehow I got threads mixed up while switching back and forth from Tapatalk and chrome. Sorry ignore what I wrote lol.
From what I've read, the colorOS stuff is the way to recover from a bricked phone. I don't have any experience in it though so I can't help much there. I would seek advice from that colorOS thread and hopefully you're able to recover
Sent From Lollipopified Bacon Goodness!
ek69 said:
If going back from cm12 to cm11s then the cm11s firmware files need to be flashed also.
Are you able to get back into fast boot mode still?
Sent From Lollipopified Bacon Goodness!
Click to expand...
Click to collapse
The stock images contain the firmware so that isn't the issue.
The phone is practically dead, so colorOS seems to be no solution as I don't know how to flash it without usb connection. But thanks for the hint.
What I do not understand: What could have gone so wrong that the whole power circuit is damaged? I thought, that flashing only affects the internal "hard disk".
Does anyone know what exactly happens on powering on a working phone?
McSvenster said:
The phone is practically dead, so colorOS seems to be no solution as I don't know how to flash it without usb connection. But thanks for the hint.
What I do not understand: What could have gone so wrong that the whole power circuit is damaged? I thought, that flashing only affects the internal "hard disk".
Does anyone know what exactly happens on powering on a working phone?
Click to expand...
Click to collapse
Nobody said anything about the power circuit being damaged, and it almost definitely isn't. That isn't the cause of a brick, what's most likely wrong is the partitions are corrupted, so it has no information telling it how to boot, what to boot into, or even to boot at all.
You didn't answer my question earlier though, diff you flash manually or via a toolkit?
I'd suggest you try this out:
http://forum.xda-developers.com/showthread.php?t=2991851
Transmitted via Bacon
McSvenster said:
The phone is practically dead, so colorOS seems to be no solution as I don't know how to flash it without usb connection. But thanks for the hint.
What I do not understand: What could have gone so wrong that the whole power circuit is damaged? I thought, that flashing only affects the internal "hard disk".
Does anyone know what exactly happens on powering on a working phone?
Click to expand...
Click to collapse
Well, I'm not entirely sure but I think that when you press the power button, you connect two ends, one end has a signal and the other end doesnt, when those two connect, the one without the signal gets a signal which will result in a battery going on maybe? Of this last battery part I'm not sure but that's how I guess it works...
I did the same as you - This fixed it for me.
http://forum.xda-developers.com/showpost.php?p=55024864&postcount=136
Basically you have to use a Windows computer and the original ColorOS firmware to fix your partitions. Follow this guide and it will flash your One with ColorOS, then you can flash TWRP and go on to flash CM11S.
It worked for me but it was a bit of a pain.
timmaaa said:
Nobody said anything about the power circuit being damaged, and it almost definitely isn't. That isn't the cause of a brick, what's most likely wrong is the partitions are corrupted, so it has no information telling it how to boot, what to boot into, or even to boot at all.
You didn't answer my question earlier though, diff you flash manually or via a toolkit?
I'd suggest you try this out:
http://forum.xda-developers.com/showthread.php?t=2991851
Transmitted via Bacon
Click to expand...
Click to collapse
Sorry, I mixed up two answers... I did it all with the fastboot commands (e.g. fastboot flash userdata cm11s\userdata_64G.img)
Thank you all a lot for your hints - I will try to fix it with a windows computer and keep you informed.
I'd suggest you try this out:
http://forum.xda-developers.com/show....php?t=2991851
Click to expand...
Click to collapse
Well, that did the trick, thank you very much! Using Windows the phone was detected as a Qualcom mass storage. I could then use the tool that directly flashed the stock cm11.
Again, thanks a lot!
All the best,
Sven
McSvenster said:
Well, that did the trick, thank you very much! Using Windows the phone was detected as a Qualcom mass storage. I could then use the tool that directly flashed the stock cm11.
Again, thanks a lot!
All the best,
Sven
Click to expand...
Click to collapse
Awesome news.
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
Hello, guys. I'm new here, so please dont hate me.
I think I've bricked my Sensation.
So, here's the deal. My Sensation was unlocked and S-OFF, I was using Ivanich's CM 12 and my phone started to work real slow. Then I read somewhere on XDA that changing data partition to f2fs can speed it up a bit. So I tried to change partition in TWRP and it stucked saying formating or something like that, I waited for 30-40 minutes but no result. And I removed the battery. Since then Twrp says "cant mount \data,\system,\cache" and so on. I tried to format it back to ext4, but no luck. I think my internal sd corrupted.
The next thing I tried was to install RUU, but it also stucked on 37%. (I checked that it stucks on <bootloader> [RUU]WP,dzdata,0).
So now I've got my Sensation stucked in RUU mode, with silver HTC logo and 4 triangles in the corners. I can't go to recovery and anything, but fastboot works.
And here's the main question: can I make it back to work or is it completely dead and i can throw it away?
P.S. I've read lots of threads with simillar problems and as far as I see this is the end for my phone. Just needed one last confirmation from someone more experiensed than myself.
I realy liked my Senny, but maybe it's time for upgrade?
fallen_apple said:
Hello, guys. I'm new here, so please dont hate me.
I think I've bricked my Sensation.
So, here's the deal. My Sensation was unlocked and S-OFF, I was using Ivanich's CM 12 and my phone started to work real slow. Then I read somewhere on XDA that changing data partition to f2fs can speed it up a bit. So I tried to change partition in TWRP and it stucked saying formating or something like that, I waited for 30-40 minutes but no result. And I removed the battery. Since then Twrp says "cant mount \data,\system,\cache" and so on. I tried to format it back to ext4, but no luck. I think my internal sd corrupted.
The next thing I tried was to install RUU, but it also stucked on 37%. (I checked that it stucks on <bootloader> [RUU]WP,dzdata,0).
So now I've got my Sensation stucked in RUU mode, with silver HTC logo and 4 triangles in the corners. I can't go to recovery and anything, but fastboot works.
And here's the main question: can I make it back to work or is it completely dead and i can throw it away?
P.S. I've read lots of threads with simillar problems and as far as I see this is the end for my phone. Just needed one last confirmation from someone more experiensed than myself.
I realy liked my Senny, but maybe it's time for upgrade?
Click to expand...
Click to collapse
see here
http://forum.xda-developers.com/htc-sensation/help/recovering-data-mount-issues-t2859588
check also post #35 from that thread
rzr86 said:
see here
http://forum.xda-developers.com/htc-sensation/help/recovering-data-mount-issues-t2859588
check also post #35 from that thread
Click to expand...
Click to collapse
Thanks for your reply
Yes, I've read this thread and it seems to work, but the thing is that I'm stuck in RUU mode and can't boot to the recovery. The only thing I see on the screen of my phone is silver htc logo and 4 warning logos in the corners.
fallen_apple said:
Thanks for your reply
Yes, I've read this thread and it seems to work, but the thing is that I'm stuck in RUU mode and can't boot to the recovery. The only thing I see on the screen of my phone is silver htc logo and 4 warning logos in the corners.
Click to expand...
Click to collapse
did you try to use the command fastboot reboot bootloader from ruu mode?
Meh, it seems to be a lost cause.
I had an exact same issue. /system, /data and /cache partitions got completely messed up, with no hope of restoring them.
The only possibilities for fixing that seem to be changing the emmc chip... or somehow plugging it under Linux disto and completely rewriting the partition table. In theory it should work, but I have completely zero clue how to get to it.
Darn, if only Android/ARM would be as simple to fix as x86 systems.
Oh well, At least I have a nice paperweight. A shame
Screw TWRP. Someone failed to test their software and we are paying the price.
rzr86 said:
did you try to use the command fastboot reboot bootloader from ruu mode?
Click to expand...
Click to collapse
Yes, I tried, phone reboots but nothing changes. Just same RUU mode htc logo on the screen
XTacDK said:
Meh, it seems to be a lost cause.
I had an exact same issue. /system, /data and /cache partitions got completely messed up, with no hope of restoring them.
The only possibilities for fixing that seem to be changing the emmc chip... or somehow plugging it under Linux disto and completely rewriting the partition table. In theory it should work, but I have completely zero clue how to get to it.
Darn, if only Android/ARM would be as simple to fix as x86 systems.
Oh well, At least I have a nice paperweight. A shame
Screw TWRP. Someone failed to test their software and we are paying the price.
Click to expand...
Click to collapse
God damn TWRP!
So for now I think my Senny is a useless peace of gear. Maybe someday people find out how to fix this issue, I hope:fingers-crossed:
fallen_apple said:
Yes, I tried, phone reboots but nothing changes. Just same RUU mode htc logo on the screen
God damn TWRP!
So for now I think my Senny is a useless peace of gear. Maybe someday people find out how to fix this issue, I hope:fingers-crossed:
Click to expand...
Click to collapse
Same with my Senny, tried to change the rom and got stuck on bootloader ((((p
All sympthoms are the same, half a day looking for solution but, no way ((((((((((
XTacDK said:
Meh, it seems to be a lost cause.
I had an exact same issue. /system, /data and /cache partitions got completely messed up, with no hope of restoring them.
The only possibilities for fixing that seem to be changing the emmc chip... or somehow plugging it under Linux disto and completely rewriting the partition table. In theory it should work, but I have completely zero clue how to get to it.
Darn, if only Android/ARM would be as simple to fix as x86 systems.
Oh well, At least I have a nice paperweight. A shame
Screw TWRP. Someone failed to test their software and we are paying the price.
Click to expand...
Click to collapse
Same here my friend, BRICKED WITH TWRP, stuck with 4 triangles and only ruu which also gets stuck at 42%
---------- Post added at 10:10 PM ---------- Previous post was at 10:07 PM ----------
fallen_apple said:
Thanks for your reply
Yes, I've read this thread and it seems to work, but the thing is that I'm stuck in RUU mode and can't boot to the recovery. The only thing I see on the screen of my phone is silver htc logo and 4 warning logos in the corners.
Click to expand...
Click to collapse
if you find a fix update this post...
I have the exact same problem. Bootloader is unlocked and fastboot is working, and I even succeeded in flashing recovery (at least no error showed up when doing so), but when I try to get into recovery mode or simply boot the phone, HTC splash screen shows up and lasts indefinitely. Is there a solution for this?
Ranching said:
I have the exact same problem. Bootloader is unlocked and fastboot is working, and I even succeeded in flashing recovery (at least no error showed up when doing so), but when I try to get into recovery mode or simply boot the phone, HTC splash screen shows up and lasts indefinitely. Is there a solution for this?
Click to expand...
Click to collapse
Try redownloading the recovery (download 4EXT, avoid TWRP at all costs!), and reflashing it.
It might be a CRC error.
Any help appreciated. I accidentally put the pixel elemental x kernal on my pixel xl and no I am stuck at the google screen with an unlocked bootloader. Can these batteries get pulled at all? Im just stuck here, and very nervous.
Solved
having the same problem, im interested in how you solved it
dablitzkrieg said:
Solved
Click to expand...
Click to collapse
hiw did you fix this i seem to be in same problem
Did you start in recovery and flash the files manually through usb on a computer?
Sent from my Nexus 7 using XDA-Developers mobile app
chrisinsocalif said:
Did you start in recovery and flash the files manually through usb on a computer?
Click to expand...
Click to collapse
i cant get into recovery i got red corrupt screen i did fastboot continue got it booted back up but had a emergancy and had to run out and forgot to plug back in battery died now i cant seem to get to get it booted back up again just seems to bootloop or get stuck with white screen with the dots when i do the fastboot continue
chrisinsocalif said:
Did you start in recovery and flash the files manually through usb on a computer?
Click to expand...
Click to collapse
thank you so much for your help.somehow i got it back up and running
Had the same happen to me. It didn't want to go into recovery gave a message it failed. With some patience I manged to get the button combo to work for fastboot then did a flash-all of the factory image. I think the trick was it had to be plugged in to get to download mode and I think you may hit the power button slightly before the volume down. It was a bit tedious. I tried to recover the boot.img and that trashed things up worse, got no google loading logo or something odd. Anyhow flashing the full factory image fixed things!
Glad you got it resolved, maybe this helps someone else in the same spot.