Database Info

[q] nexus 5 bricked in first 4 days sos

Alright i got 6 hours before tmbobile store opens and i can HOPEFULLY get an exchange, but not banking on it. btw im new to rooting so i wasnt familiar with the process, but regardless i have hard bricked my NEXUS 5. Title says the problem. I followed wwjoshdew's guide to rooting on youtube, and rooted successfully. But i could'nt for the life of me figure out how to create nandroid. I ended up realizing i didnt download cmw recovery mode and downloaded it from the play store. the app took me to a button that said flash recovery and i hit it and my phone asked for permission from unknown source, i hit ok and it shut down, on 70% battery life. Not turning on please help

Try to boot the phone into bootloader mode. Just hold volume down and the power button. From there try to cycle to recovery. You use your volume down to cycle through the options and power but as select. If you can boot into recovery and have that successfully installed then you can erase your phone and try to power it on from there. If you didn't successful install the custom recovery then you'll have the standard Android recovery. You can erase everything from that too.
These phones are hard to brick and not be able to fix it.
Sent from my Nexus 5 using XDA Premium 4 mobile app

ruben8448 said:
Try to boot the phone into bootloader mode. Just hold volume down and the power button. From there try to cycle to recovery. You use your volume down to cycle through the options and power but as select. If you can boot into recovery and have that successfully installed then you can erase your phone and try to power it on from there. If you didn't successful install the custom recovery then you'll have the standard Android recovery. You can erase everything from that too.
These phones are hard to brick and not be able to fix it.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Doesn't turn on dude. No matter what. I am new to roms but i know what a hard brick is.

You should really read the guides and stickied threads at the top of these forums. The guides are very noob friendly and you wouldn't have bricked your phone. There's one to reset your device to stock as well. There's really no need for this thread and on top of that there is a sticky that says no questions in the General forums.
Sent from my Nexus 5 using Tapatalk

Determine your phone is actually off. Plug your phone into charge, if a battery sign appears in the middle of the screen then your phone is off.
If your phone is off, hold down the volume down button with the power button to start the bootloader, press volume down twice and press the power button to enter recovery.
If your screen remains black and doesn't show a battery logo, hold the volume up, volume down and power buttons at the same time for a minute, then let go and hold down the power button. Which should hopefully start your phone.

FuMMoD said:
You should really read the guides and stickied threads at the top of these forums. The guides are very noob friendly and you wouldn't have bricked your phone. There's one to reset your device to stock as well. There's really no need for this thread and on top of that there is a sticky that says no questions in the General forums.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
You should have been around long enough to know that when newbies break their new toys they go nuclear and dismiss all the information around them.

BNNEBULA said:
Alright i got 6 hours before tmbobile store opens and i can HOPEFULLY get an exchange, but not banking on it. btw im new to rooting so i wasnt familiar with the process, but regardless i have hard bricked my NEXUS 5. Title says the problem. I followed wwjoshdew's guide to rooting on youtube, and rooted successfully. But i could'nt for the life of me figure out how to create nandroid. I ended up realizing i didnt download cmw recovery mode and downloaded it from the play store. the app took me to a button that said flash recovery and i hit it and my phone asked for permission from unknown source, i hit ok and it shut down, on 70% battery life. Not turning on please help
Click to expand...
Click to collapse
You bricked a Nexus?
Hold down Volume Down, Up, and Power to get into fastboot mode. Restore from Factory Image.
Normally, to root a nexus, I fastboot Team Win Recovery Project.
Anyways what you did simply could not HARD BRICK the phone.

zeekiz said:
You should have been around long enough to know that when newbies break their new toys they go nuclear and dismiss all the information around them.
Click to expand...
Click to collapse
Seriously lol. Even though the guides are right there in their faces.
Sent from my Nexus 5 using Tapatalk

HELP SOS
FuMMoD said:
You should really read the guides and stickied threads at the top of these forums. The guides are very noob friendly and you wouldn't have bricked your phone. There's one to reset your device to stock as well. There's really no need for this thread and on top of that there is a sticky that says no questions in the General forums.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
My Nexus5 doesn't flash the Led light or enter bootloader and software . I was flashing the based CM kernel and i followed the instructions nicely, while using TWRP Recovery i pressed reboot system after the flash and the phone suddenly died. I connected it to the PC and the installing drivers popup appeared and it didn't install them, problem(QHSUSB_BULK) it only appeared once. And since that, phone is dead. PLEASE HELP!!!!

Yazan Abzakh171 said:
My Nexus5 doesn't flash the Led light or enter bootloader and software . I was flashing the based CM kernel and i followed the instructions nicely, while using TWRP Recovery i pressed reboot system after the flash and the phone suddenly died. I connected it to the PC and the installing drivers popup appeared and it didn't install them, problem(QHSUSB_BULK) it only appeared once. And since that, phone is dead. PLEASE HELP!!!!
Click to expand...
Click to collapse
Do you have a link to the kernel you flashed? I think you done bricked it good.

Were you using this method?
http://www.youtube.com/watch?v=w3beFx-3Ic4
If yes,I think then all Nexus 5 users should be warned about CF's autoroot issues,because I see more and more topics related to this issue.

Simonna said:
Were you using this method?
http://www.youtube.com/watch?v=w3beFx-3Ic4
If yes,I think then all Nexus 5 users should be warned about CF's autoroot issues,because I see more and more topics related to this issue.
Click to expand...
Click to collapse
I don't believe the issues you're seeing, appears to be failed emmc, is related to chain fire's auto root. Cf is probably the most popular method to root and it's a coincidence. I've seen these failures with other root methods too.
I think the op flashed a kernel not for his device.

jd1639 said:
I don't believe the issues you're seeing, appears to be failed emmc, is related to chain fire's auto root. Cf is probably the most popular method to root and it's a coincidence. I've seen these failures with other root methods too.
I think the op flashed a kernel not for his device.
Click to expand...
Click to collapse
I am not a developer so bear with me. I'm just a guy in mpls with a completely stock N5 from Google Play that encountered similar issue as the original post. There was no damage or water issue, or other problem prior to going dead. It had about 50% battery and maybe 15 minutes after reading an email it was dead when I looked at it again. It just simply turned off while in my pocket. I could not get it to power on or enter bootloader or a recovery screen. After a week of trying to charge via USB and the original wall charger and countless attempts to hold power and volume buttons without success, I decided to pop the back off and disconnected the battery. I put it back together, but that made no difference either. Google play will send me a new phone, but I'd like to get it fired up and extract the last week or so of pics. Any ideas? Again, I am a complete noob and this 3 month old phone has not been modified in any way, other than auto updates from Google play. Thanks for any assistance or guidance.

elf1967 said:
I am not a developer so bear with me. I'm just a guy in mpls with a completely stock N5 from Google Play that encountered similar issue as the original post. There was no damage or water issue, or other problem prior to going dead. It had about 50% battery and maybe 15 minutes after reading an email it was dead when I looked at it again. It just simply turned off while in my pocket. I could not get it to power on or enter bootloader or a recovery screen. After a week of trying to charge via USB and the original wall charger and countless attempts to hold power and volume buttons without success, I decided to pop the back off and disconnected the battery. I put it back together, but that made no difference either. Google play will send me a new phone, but I'd like to get it fired up and extract the last week or so of pics. Any ideas? Again, I am a complete noob and this 3 month old phone has not been modified in any way, other than auto updates from Google play. Thanks for any assistance or guidance.
Click to expand...
Click to collapse
So, your phone doesn't turn on at all?

jd1639 said:
I don't believe the issues you're seeing, appears to be failed emmc, is related to chain fire's auto root. Cf is probably the most popular method to root and it's a coincidence. I've seen these failures with other root methods too.
I think the op flashed a kernel not for his device.
Click to expand...
Click to collapse
Correct. No symbols, no battery icon, no vibrate, etc.

elf1967 said:
Correct. No symbols, no battery icon, no vibrate, etc.
Click to expand...
Click to collapse
I'm afraid there's nothing you can do. It would have to at least get into recovery or bootloader to have a prayer.

jd1639 said:
I'm afraid there's nothing you can do. It would have to at least get into recovery or bootloader to have a prayer.
Click to expand...
Click to collapse
Thanks - was just hoping it was not a hardware failure given the posts about difficulty bricking N5. Any chance if I bought a new battery that came charged it would fire up or replacing the motherboard an option?
p.s. I am not the original poster so not sure if I ticked someone off or not, sorry if I did. Just looking for assistance

elf1967 said:
Thanks - was just hoping it was not a hardware failure given the posts about difficulty bricking N5. Any chance if I bought a new battery that came charged it would fire up or replacing the motherboard an option?
p.s. I am not the original poster so not sure if I ticked someone off or not, sorry if I did. Just looking for assistance
Click to expand...
Click to collapse
It sure sounds like a hardware failure. Doubt a different battery would help. And don't worry about being the original op. This thread is old

jd1639 said:
It sure sounds like a hardware failure. Doubt a different battery would help. And don't worry about being the original op. This thread is old
Click to expand...
Click to collapse
I get the unknown device driver when hooked up USB to computer (QHSUSB_BULK). Think it is worth waiting a few weeks prior to returning it to see if there is a way to access the flash memory via a driver download? Searches for help showed similar unknown driver problem workable on samsung and HTC last year (QHSUSB_DLOAD)

elf1967 said:
I get the unknown device driver when hooked up USB to computer (QHSUSB_BULK). Think it is worth waiting a few weeks prior to returning it to see if there is a way to access the flash memory via a driver download? Searches for help showed similar unknown driver problem workable on samsung and HTC last year (QHSUSB_DLOAD)
Click to expand...
Click to collapse
No, you won't be able to. The memory doesn't mount like a sd card would. For the future use something like drop box or Google drive too backup your photos as you take them.

Nexus 5 Stuck at Google Loading Screen (Picture attached)

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.

[Q] OPO Boot Loop/Hang After Drop

I accidentally dropped my OPO face first from about chest height earlier today. The screen didn't break but now my phone is acting weird.
First, it was okay but after a few minutes, it hanged up and was on a boot loop. I tried a factory reset but now I'm unable to get wifi (wifi button is off with a orange square around it) and the boot loop and hanging still persists. The phone does heat up and seems to go out of the loop if its cool enough. Hangs up if it gets hot.
Any help on fixing this? I'm going to try a fresh install in a few minutes but I'm kinda feeling this is a hardware issue already.

The fact that it still does it even after doing a factory reset is concerning. Try doing a complete factory restore as per this thread and then also try this. If both fail to resolve the issue i suspect your hardware has been damaged and i don't see you fixing the issue one your own unfortunately.

Yeah, unfortunately I did both already. Installed stock build and the Audio FX fix. The Audio FX bug is still showing up though. Not sure if I have done anything wrong in replacing persist.img

brutalpanda said:
Yeah, unfortunately I did both already. Installed stock build and the Audio FX fix. The Audio FX bug is still showing up though. Not sure if I have done anything wrong in replacing persist.img
Click to expand...
Click to collapse
You could also try flashing this. Though i think its unlikely to fix the issue, you don't have anything to lose at this point...this also re-flashes the reserve4 partition.

S M G said:
You could also try flashing this. Though i think its unlikely to fix the issue, you don't have anything to lose at this point...this also re-flashes the reserve4 partition.
Click to expand...
Click to collapse
Just an update, my phone is now dead. After rebooting several times this morning, it suddenly lost power. Not even charging helps. No response from power button and can't even fastboot. I guess the main board got affected when it fell and fried itself up in the process.
Crap. I'm really sad about this..I'll probably try opening it up and see if anything got dislodged. You think that's a good idea?

brutalpanda said:
Just an update, my phone is now dead. After rebooting several times this morning, it suddenly lost power. Not even charging helps. No response from power button and can't even fastboot. I guess the main board got affected when it fell and fried itself up in the process.
Crap. I'm really sad about this..I'll probably try opening it up and see if anything got dislodged. You think that's a good idea?
Click to expand...
Click to collapse
I sorry to hear that bro, its a bummer. You might as well open it up yourself and see if you can find anything obvious wrong with it, or you could try and get in contact with OnePlus and find out if they can do a repair of sorts, but i wouldn't get my hopes up on that though.

aa

brutalpanda said:
aa
Click to expand...
Click to collapse
S M G said:
I sorry to hear that bro, its a bummer. You might as well open it up yourself and see if you can find anything obvious wrong with it, or you could try and get in contact with OnePlus and find out if they can do a repair of sorts, but i wouldn't get my hopes up on that though.
Click to expand...
Click to collapse
Well, it seems there's power. The phone is slightly hot when touching it. I tried plugging via PC and Windows recognizes there's a USB device although after trying to install drivers, it prompted me that the device was not recognized. Not sure what to do at this point though.

brutalpanda said:
Just an update, my phone is now dead. After rebooting several times this morning, it suddenly lost power. Not even charging helps. No response from power button and can't even fastboot. I guess the main board got affected when it fell and fried itself up in the process.
Crap. I'm really sad about this..I'll probably try opening it up and see if anything got dislodged. You think that's a good idea?
Click to expand...
Click to collapse
brutalpanda said:
Well, it seems there's power. The phone is slightly hot when touching it. I tried plugging via PC and Windows recognizes there's a USB device although after trying to install drivers, it prompted me that the device was not recognized. Not sure what to do at this point though.
Click to expand...
Click to collapse
As what does Windows' Device Manager show/identify the device ?

S M G said:
As what does Windows' Device Manager show/identify the device ?
Click to expand...
Click to collapse
My phone is back but still boot looping. Would installing other ROMs solve the problem? I won't be able to RMA this so it's not an option.

brutalpanda said:
My phone is back but still boot looping. Would installing other ROMs solve the problem? I won't be able to RMA this so it's not an option.
Click to expand...
Click to collapse
It could perhaps, but lets start here: Can you boot into fastboot mode? If YES does it reboot itself while in fastboot or is it actually stable as in it stays in fastboot?

S M G said:
It could perhaps, but lets start here: Can you boot into fastboot mode? If YES does it reboot itself while in fastboot or is it actually stable as in it stays in fastboot?
Click to expand...
Click to collapse
It's actually quite stable. I had never seen it reboot when in Fastboot. It's also worth mentioning that if I'm in Recovery Mode (TWRP installed), the phone also doesn't reboot.
I also noticed that ever since the drop/boot loop/hangs, my phone reboots very long (around 2-3 minutes it it does boot into the system; which happens less frequently than the boot loop). Before it took probably a minute at most to reboot.

brutalpanda said:
It's actually quite stable. I had never seen it reboot when in Fastboot. It's also worth mentioning that if I'm in Recovery Mode (TWRP installed), the phone also doesn't reboot.
I also noticed that ever since the drop/boot loop/hangs, my phone reboots very long (around 2-3 minutes it it does boot into the system; which happens less frequently than the boot loop). Before it took probably a minute at most to reboot.
Click to expand...
Click to collapse
Another update. So here's what I found out. My phone needs to be super cooled for it to work. I tried putting it in front of the air conditioner. If it's really cool, WIFI works. When it gets slightly warm, my phone hangs up. When it reboots, I lose wifi. After that, if I still don't cool it down, boot loops happens.
I'm not sure what's happening but it seems that it's an overheating issue perhaps?

brutalpanda said:
Another update. So here's what I found out. My phone needs to be super cooled for it to work. I tried putting it in front of the air conditioner. If it's really cool, WIFI works. When it gets slightly warm, my phone hangs up. When it reboots, I lose wifi. After that, if I still don't cool it down, boot loops happens.
I'm not sure what's happening but it seems that it's an overheating issue perhaps?
Click to expand...
Click to collapse
Well that is possible, i suppose. Maybe the heat-spreader moved away ever so slightly of the CPU, or isn't making good enough contact with it anymore which would lead to it not properly dissipating the heat. Unfortunately that i wont be able to know.
Lets assume that this is a software issue for now. Have you tried this yet by any chance ?
If not it is definitely worth a shot. Before flashing it i recommend clearing cache partition & dalvik cache in TWRP first then reboot into bootloader mode and then run this as per the READ ME file which is included.
There are essentially 3 batch file you need to run and it will recreate all the partitions on your device etc.
PS: You need to register on the OnePlus forums to actually be able to view the thread.
PPS: If for some reason the download link is bad let me know and ill mirror it for you on my dropbox.

S M G said:
Well that is possible, i suppose. Maybe the heat-spreader moved away ever so slightly of the CPU, or isn't making good enough contact with it anymore which would lead to it not properly dissipating the heat. Unfortunately that i wont be able to know.
Lets assume that this is a software issue for now. Have you tried this yet by any chance ?
If not it is definitely worth a shot. Before flashing it i recommend clearing cache partition & dalvik cache in TWRP first then reboot into bootloader mode and then run this as per the READ ME file which is included.
There are essentially 3 batch file you need to run and it will recreate all the partitions on your device etc.
PS: You need to register on the OnePlus forums to actually be able to view the thread.
PPS: If for some reason the download link is bad let me know and ill mirror it for you on my dropbox.
Click to expand...
Click to collapse
Yeah, unfortunately I have the 16GB version. Any chance what's the difference? Is it just the userdata.img?

Oneplus One keeps rebooting

Recently my screen's digitizer broke, so I ordered a new screen and just got it today.
I replaced it and I tested it, it turned on and that, but when I try to boot it just come with the onplus logo and powered by android stuff in the bottom and that's the only thing it's showing with it just turns off and on basically rebooting
So I tested, can it go into fastboot it could so I tried flashing twrp on but didn't work keeps doing the same cannot even enter recovery just fastboot.
Anyone tried this before or, what can I do to fix it if there is a possible fix for it.

Have you tried flashing official images from fastboot? hopefully not a hardware issues

I'm having the same problem, also since today. My phone just got in a bootloop while powered on and running completely fine. Trying to boot into recovery also gets me a bootloop. Fastboot works, and when i try to flash anything it tells me it succeeds. Then when i try to power on again, still the same bootloop.
I've tried the Oneplus Recovery Tool, same thing. Everything succeeds, but I still end up with a bootloop. The logo on the fastboot page had changed, though, so I'm guessing the flash was successful, but something else is broken.
I'm actually really worried about my phone right now.

morreion said:
I'm having the same problem, also since today. My phone just got in a bootloop while powered on and running completely fine. Trying to boot into recovery also gets me a bootloop. Fastboot works, and when i try to flash anything it tells me it succeeds. Then when i try to power on again, still the same bootloop.
I've tried the Oneplus Recovery Tool, same thing. Everything succeeds, but I still end up with a bootloop. The logo on the fastboot page had changed, though, so I'm guessing the flash was successful, but something else is broken.
I'm actually really worried about my phone right now.
Click to expand...
Click to collapse
You tried one plus recovery tool cm11s?

Mr.Ak said:
You tried one plus recovery tool cm11s?
Click to expand...
Click to collapse
Yep, that's the one. Everything seems to work fine, all the bars are loading, and the device turns green. Unplugged the device, booted up, still a bootloop.
I tried the ColorOS guide (https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732) too, same thing. The boot logo did turn red though.

morreion said:
Yep, that's the one. Everything seems to work fine, all the bars are loading, and the device turns green. Unplugged the device, booted up, still a bootloop.
I tried the ColorOS guide (https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732) too, same thing. The boot logo did turn red though.
Click to expand...
Click to collapse
If even that tool couldn't solve it then it's definitely a hardware issue.

Mr.Ak said:
If even that tool couldn't solve it then it's definitely a hardware issue.
Click to expand...
Click to collapse
Damn. Well, too bad. I'm going to try to fix my phone for a bit more, not that I think it's still fixable. Thanks!

I also think it is a hardware issue but I don't want it to be :/
It's just funny but I think I found it, its the power button because apparently the button itself got off the wire so maybe I can sort it on again.
Or maybe it could be something else but cannot seem to find it.
I maybe u try to get my friend to sort a new storage chip on if I can get I contact with him wish me luck

morreion said:
Damn. Well, too bad. I'm going to try to fix my phone for a bit more, not that I think it's still fixable. Thanks!
Click to expand...
Click to collapse
Just get your device checked from a local source and then replace the decayed part yourself.
AFAIK,it can be either battery or Motherboard/Logic board.
---------- Post added at 09:07 PM ---------- Previous post was at 09:06 PM ----------
Melonendk said:
I also think it is a hardware issue but I don't want it to be :/
It's just funny but I think I found it, its the power button because apparently the button itself got off the wire so maybe I can sort it on again.
Or maybe it could be something else but cannot seem to find it.
I maybe u try to get my friend to sort a new storage chip on if I can get I contact with him wish me luck
Click to expand...
Click to collapse
Best of luck!

I am encountering the same problem. Out of nowhere my phone started rebooting. It reboots ok and after a minute it does it again...so it is working alright for a minute. However, my phone is completely stock Cyanogen OS...
I have tried this, but it did not work for me.

diosak said:
I am encountering the same problem. Out of nowhere my phone started rebooting. It reboots ok and after a minute it does it again...so it is working alright for a minute. However, my phone is completely stock Cyanogen OS...
I have tried this, but it did not work for me.
Click to expand...
Click to collapse
If it does work alright for a minute every time, I don't think you have the same problem as I have.

OnePlus One - stuck on Resurrection boot

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.