Hello everyone!
I have been using the AOKP ROM for quite a while now, and yesterday I had quite an issue:
I was simply writing on Whatsapp and using Maps, when suddenly the device froze and rebooted. Then, it loaded up to the bootscreen, only to reboot once again and get stuck in a black screen.
Afterwards, a few times it managed to load up to the homescreen, but it rebooted again after a few seconds.
I got it to Recovery mode, but whenever I tried to make a backup, it died halfway the process. That's why I didn't try to flash anything, while being so unstable.
At the moment, it seems totally dead. No bootloader, no charging, and of course, no startup.
I'm thinking of hardware failure, but maybe one of you might have another solution, or something I can try. You'll have my gratitude if you can lend me a hand with this.
Thanks a lot for reading!
i hope it will help you but give them a try
charge the device without battery,sim and sdcard for 5-6 hours
then put them again and switch on the device
if that fails then do the unbricking project
http://forum.xda-developers.com/showthread.php?t=1522351
otherwise maybe it is a hardware issue
rzr86 said:
i hope it will help you but give them a try
charge the device without battery,sim and sdcard for 5-6 hours
then put them again and switch on the device
if that fails then do the unbricking project
http://forum.xda-developers.com/showthread.php?t=1522351
otherwise maybe it is a hardware issue
Click to expand...
Click to collapse
Thanks rzr!
Charge WITHOUT battery? That's... weird. But whatever, I have nothing to lose.
I tried the unbricking project, but the brickdetect.sh script didn't pick up anything. I guess that's because the guide is intended for S-ON...
I'll try the first option for now. Thanks a lot!
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.
This phone was working perfectly and I left it to go away to another country so it must have discharged it's battery.
When I got back it would not turn on. Even after charging for a day, it will not turn on.
When I have the charging cable connected, it goes to Google Logo Screen and it loops (restarts over and over again)
There is no error message.
Picture is attached so please let me know what to do. It was a gift so no receipt to claim warranty.
Thanks for any help in advance.
joongpark said:
Hi.
This phone was working perfectly and I left it to go away to another country so it must have discharged it's battery.
When I got back it would not turn on. Even after charging for a day, it will not turn on.
When I have the charging cable connected, it goes to Google Logo Screen and it loops (restarts over and over again)
There is no error message.
Picture is attached so please let me know what to do. It was a gift so no receipt to claim warranty.
Thanks for any help in advance.
Click to expand...
Click to collapse
Try booting into stock recovery and clearing cache, reboot.
If that doesn't work then you'll have to unlock the bootloader (which wipes data) and try flashing the factory images. A guide for that can be found in the first link of my signature.
Lethargy said:
Try booting into stock recovery and clearing cache, reboot.
If that doesn't work then you'll have to unlock the bootloader (which wipes data) and try flashing the factory images. A guide for that can be found in the first link of my signature.
Click to expand...
Click to collapse
Thanks for the help...I am not sure If I am able to get into recovery more. Last time I tried, I was not able to.
Let you know once I try it.
Thanks.
Lethargy said:
Try booting into stock recovery and clearing cache, reboot.
If that doesn't work then you'll have to unlock the bootloader (which wipes data) and try flashing the factory images. A guide for that can be found in the first link of my signature.
Click to expand...
Click to collapse
I just tested and I am not able to get into recovery more...I am not sure what that mean. Should I connect Nexus to computer and see if it's recognized by computer and try to reload stock ROM?
Phone was never unlocked or flashed...it was in the same state as it was bought.
Can this be hardware problem? I saw some reports of similar thing happening with power button problem or other hardware problems.
joongpark said:
I just tested and I am not able to get into recovery more...I am not sure what that mean. Should I connect Nexus to computer and see if it's recognized by computer and try to reload stock ROM?
Phone was never unlocked or flashed...it was in the same state as it was bought.
Can this be hardware problem? I saw some reports of similar thing happening with power button problem or other hardware problems.
Click to expand...
Click to collapse
did you go into the bootloader, choose recovery, and it went to an android laying on its back?
This is the weirdest things...Spent days and days trying to bring it back to life and it would just reboot after GOOGLE logo. There was no way to get into recovery more.
I was looking around and someone said that tapping hard behind the power button with finger might bring it back and it did...so crazy. No matter what, I am a happy camper.
If you have tried everything, just try it...it behind power button and it might wake up the android that's been sleeping.
joongpark said:
This is the weirdest things...Spent days and days trying to bring it back to life and it would just reboot after GOOGLE logo. There was no way to get into recovery more.
I was looking around and someone said that tapping hard behind the power button with finger might bring it back and it did...so crazy. No matter what, I am a happy camper.
If you have tried everything, just try it...it behind power button and it might wake up the android that's been sleeping.
Click to expand...
Click to collapse
Can u explain how did u do that .what do u mean by behind the power button
I have the option to buy this device from a guy who has this problem and i have said to him to try the tips but not working. Computer does not see the device yet and thats logic since it just goes for 2-3 sec in bootloader he told me. Is this the power buttion failure or can it be fixed with nexus toolkit?
Price is €50 because of that and little damaged glass but i doubt if i can let it boot normal again.
Hey guys
So a couple of days ago I was browsing on facebook when suddenly my One froze and rebooted. After that I suddenly didn't have any connectivity.
I figured I might be able to fix this by rebooting the phone, but after the reboot the phone worked for two seconds and then froze, restarted etc.. It keeps doing that.
Now I looked up if this was a common problem and it is, there is also a fix for it. The fix requires fastboot, but I can't get fastboot to work because I get the QHSUSB_BULK error on my PC.
This usually indicates a hardbrick but my phone still starts up, I can also boot into recovery, I just can't use the fastboot.
Is there anyone who can help me?
Thanks in advance.
Unlegit said:
Hey guys
So a couple of days ago I was browsing on facebook when suddenly my One froze and rebooted. After that I suddenly didn't have any connectivity.
I figured I might be able to fix this by rebooting the phone, but after the reboot the phone worked for two seconds and then froze, restarted etc.. It keeps doing that.
Now I looked up if this was a common problem and it is, there is also a fix for it. The fix requires fastboot, but I can't get fastboot to work because I get the QHSUSB_BULK error on my PC.
This usually indicates a hardbrick but my phone still starts up, I can also boot into recovery, I just can't use the fastboot.
Is there anyone who can help me?
Thanks in advance.
Click to expand...
Click to collapse
I believe there is a way to recover from hardbrick by installing colorOS and reinstalling CM.
Please check here: https://forums.oneplus.net/threads/solution-recover-from-hard-bricked-oneplus-one.104943/
CravingMender9 said:
I believe there is a way to recover from hardbrick by installing colorOS and reinstalling CM.
Please check here:
Click to expand...
Click to collapse
Yeah, thanks. Gonna try that one, but I still fear for the phone's inability to use fastboot.
Unlegit said:
Yeah, thanks. Gonna try that one, but I still fear for the phone's inability to use fastboot.
Click to expand...
Click to collapse
No problem. Do let us know how it goes.
Hello guys,
I apologize if this has been solved before but I wasn't able to find anything on it.
I have a oneplus one phone which I had running Ressurection Rom (I don't have the details as my father was using it for the last 2 years).
He dropped the phone and gave it to a shop for repairing of the screen. They repaired the screen but now they have somehow messed with the software where I am UNABLE TO BOOT TO FASTBOOT OR TRWP. The function of holding POWER + VOLUME DOWN or POWER + VOLUME UP doesn't work. When I attempt those two options, it still continues to boot as it normally would and then start optimizing apps. Does that for about 45 minutes and then just restarts and repeats the process.
I haven't messed around with android stuff for about a year now, so simplified instructions (rather step by step) would be extremely helpful.
Thank you so much for taking the time.
NSingh95 said:
Hello guys,
I apologize if this has been solved before but I wasn't able to find anything on it.
I have a oneplus one phone which I had running Ressurection Rom (I don't have the details as my father was using it for the last 2 years).
He dropped the phone and gave it to a shop for repairing of the screen. They repaired the screen but now they have somehow messed with the software where I am UNABLE TO BOOT TO FASTBOOT OR TRWP. The function of holding POWER + VOLUME DOWN or POWER + VOLUME UP doesn't work. When I attempt those two options, it still continues to boot as it normally would and then start optimizing apps. Does that for about 45 minutes and then just restarts and repeats the process.
I haven't messed around with android stuff for about a year now, so simplified instructions (rather step by step) would be extremely helpful.
Thank you so much for taking the time.
Click to expand...
Click to collapse
This condition is called hard brick.To fix this,
https://forums.oneplus.net/threads/...ol-restore-stock-cm11s-fix-bricks-etc.237827/
Use this tool on winXp or win7(don't use 8 or 10),run it as administrator.Make sure you install the drivers correctly,good luck!
Mr.Ak said:
This condition is called hard brick.To fix this,
https://forums.oneplus.net/threads/...ol-restore-stock-cm11s-fix-bricks-etc.237827/
Use this tool on winXp or win7(don't use 8 or 10),run it as administrator.Make sure you install the drivers correctly,good luck!
Click to expand...
Click to collapse
Hello, Thank you for your response.
I have tried the instructions that you provided and I am stuck in a place where the "Samsung" drivers for OPO are installed but the phone isn't detected by the computer when its plugged in. I assume that means the drivers aren't installed correctly. However, when I do open device manager and attempt to update or uninstall the drivers there isn't a device there that is representative of OPO.
How do I get to the point where the drivers can be installed without me having access to the phone. I can't really go into a bricked phone and turn on ADB etc.'
Thank you
NSingh95 said:
Hello, Thank you for your response.
I have tried the instructions that you provided and I am stuck in a place where the "Samsung" drivers for OPO are installed but the phone isn't detected by the computer when its plugged in. I assume that means the drivers aren't installed correctly. However, when I do open device manager and attempt to update or uninstall the drivers there isn't a device there that is representative of OPO.
How do I get to the point where the drivers can be installed without me having access to the phone. I can't really go into a bricked phone and turn on ADB etc.'
Thank you
Click to expand...
Click to collapse
Read the whole thread.
https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Use Xp or win7(must).
Okay so I have attempted this a tiring number of times; initially the phone at least was going on to loading apps, now it just flashes on the Resurrection load screen and doesn't change at all. Also when I try to boot into recovery/fastboot, nothing happens.
I have also tried installing different drivers from like a samsung phone, nexus but to no avail.
Is there anyone who can perhaps TEAMVIEW me and help out or live chat?
NSingh95 said:
Okay so I have attempted this a tiring number of times; initially the phone at least was going on to loading apps, now it just flashes on the Resurrection load screen and doesn't change at all. Also when I try to boot into recovery/fastboot, nothing happens.
I have also tried installing different drivers from like a samsung phone, nexus but to no avail.
Is there anyone who can perhaps TEAMVIEW me and help out or live chat?
Click to expand...
Click to collapse
Device on Twrp works fine?
Mr.Ak said:
Device on Twrp works fine?
Click to expand...
Click to collapse
I'm not able to boot into twrp.
NSingh95 said:
I'm not able to boot into twrp.
Click to expand...
Click to collapse
@psxda97 ,can this be a battery issue?
Mr.Ak said:
@psxda97 ,can this be a battery issue?
Click to expand...
Click to collapse
I don't think so. If it is a battery issue he could go to fastboot since fastboot only uses a small amount of charge.
NSingh95 said:
I'm not able to boot into twrp.
Click to expand...
Click to collapse
Try turning on your phone while connected to a charger.
psxda97 said:
I don't think so. If it is a battery issue he could go to fastboot since fastboot only uses a small amount of charge.
Try turning on your phone while connected to a charger.
Click to expand...
Click to collapse
I have, its definitely not a battery issue, because i have seen the phone stay on for an hour just on the bootscreen without being plugged in or anything.
NSingh95 said:
I have, its definitely not a battery issue, because i have seen the phone stay on for an hour just on the bootscreen without being plugged in or anything.
Click to expand...
Click to collapse
Most probably your volume buttons were messed up during the repair. That's the only reason I can think of. There are some videos on YouTube about fixing the volume buttons.
Edit :
I managed to have a Deep Flash cable and successfully bring the device to EDL anytime I need. Thanks for the help, guys!
-----------------------------------------
My OnePlus 8T seems hard-bricked, it can not boot anymore, when plugin ( had to disconnected the battery connector ) it's screen only flash the Logo and vibrate then auto reboot and keep looping. So I need the test point map of this device in order to force flash the firmware, hence, if anyone have it's test point map, please help to share. Or any other solutions may work with the situation.
Thanks in advance!
I had something similar happen: see https://forum.xda-developers.com/t/how-to-get-out-of-endless-oos-boot-animation-solved.4366923/
So I'd suggest that you let the battery drain which will turn the phone off. Then charge it for a bit and connect it took the MSM Tool to restore your phone.
BillGoss said:
I had something similar happen: see https://forum.xda-developers.com/t/how-to-get-out-of-endless-oos-boot-animation-solved.4366923/
So I'd suggest that you let the battery drain which will turn the phone off. Then charge it for a bit and connect it took the MSM Tool to restore your phone.
Click to expand...
Click to collapse
Thanks for your info. I've tried draining the battery but seems by bootloader ( somehow ) relocked without my act knowledge, therefore, everytime I try to boot in to fastboot mode, it only show the Fastboot logo for a second then reboot again, then..........keep looping @@
Can u pls check out the video and see if your device used to be like this or not? Thanks mate!
LinhBT said:
Can u pls check out the video and see if your device used to be like this or not? Thanks mate!
Click to expand...
Click to collapse
It looks similar to what happened to me. I think I got a bit of the red and white circle before it restarted.
Don't try to go into bootloader. From power off, go straight to MSM.
BillGoss said:
It looks similar to what happened to me. I think I got a bit of the red and white circle before it restarted.
Don't try to go into bootloader. From power off, go straight to MSM.
Click to expand...
Click to collapse
Thanks mate, I'll give it another try. Leaving it to drain now
I experienced your issue with my hiccup a week ago, required the use of MSM tool (full reinstall of OOS)...i kept getting an error on install as it would reboot back to recovery and never finish the process. What corrected it was that I had to change "slot" and upon reboot MSM tool worked.
I use TWRP which was flashed on both a & b
Just a quick FYI
racenrich said:
I experienced your issue with my hiccup a week ago, required the use of MSM tool (full reinstall of OOS)...i kept getting an error on install as it would reboot back to recovery and never finish the process. What corrected it was that I had to change "slot" and upon reboot MSM tool worked.
I use TWRP which was flashed on both a & b
Just a quick FYI
Click to expand...
Click to collapse
Thanks mate, really appreciate, but my problem here is : no recovery, no fastboot, at all ((((