Oneplus One keeps rebooting - ONE Q&A, Help & Troubleshooting

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.

Related

[Q] Random rebooting does not stop

Hi
This is a well known issue with the nexus 5. My device permanently starts rebooting. The google Logo occurs and then it rebotos again. There is no start animation. If I press the power and volume down bottom I just see the bootloader screen and after half a second it reboots. I can't do anything.
My phone is rooted (no custom ROM) and before I go back to the shop I want to unroot it. However, with this behaviour I'm not able to do it, or is there any chance? Does someone know at least, how I can boot normaly to unroot it.
thanks for your help
crampas
majorcrampas said:
Hi
This is a well known issue with the nexus 5. My device permanently starts rebooting. The google Logo occurs and then it rebotos again. There is no start animation. If I press the power and volume down bottom I just see the bootloader screen and after half a second it reboots. I can't do anything.
My phone is rooted (no custom ROM) and before I go back to the shop I want to unroot it. However, with this behaviour I'm not able to do it, or is there any chance? Does someone know at least, how I can boot normaly to unroot it.
thanks for your help
crampas
Click to expand...
Click to collapse
Hello, take a look at this thread http://forum.xda-developers.com/showthread.php?t=2513701
Is this really a well known issue? What were you doing directly beforehand? What have you tried to do to fix it? Have you tried using fastboot commands to reload factory images? Are you a toolkit only user? Have you tried a factory image through that?
Sent from my Nexus 5 using xda app-developers app
sorry, i overlooked that you cant enter fastboot.take a look here instead http://forum.xda-developers.com/showthread.php?t=2521691&page=3
kboya said:
Is this really a well known issue? What were you doing directly beforehand? What have you tried to do to fix it? Have you tried using fastboot commands to reload factory images? Are you a toolkit only user? Have you tried a factory image through that?
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Well IMHO it is a well known issue (see for example the wikipedia page or just have a look in tech forums). Directly before, I was writing an SMS and put it in my pocket (everything seems fine at that moment). 10 minutes later I just want to check my SMS and then it was already rebooting all the time. This was not the first time, I had this issue 2 todays before, but after approximatley 20 reboots it started correctly.
So far I was not able to use fastboot commands, since I can't enter fastboot. I didn't use a toolkit.
32299564
Madpiercing said:
sorry, i overlooked that you cant enter fastboot.take a look here instead http://forum.xda-developers.com/showthread.php?t=2521691&page=3
Click to expand...
Click to collapse
Thanks for the link. I will check it later, 'cause I have to leave. I will write again and let you know if I'm able to enter fastboot.
majorcrampas said:
Thanks for the link. I will check it later, 'cause I have to leave. I will write again and let you know if I'm able to enter fastboot.
Click to expand...
Click to collapse
no problemi, i hope you can unbrick it!
Use this thread:
http://forum.xda-developers.com/showthread.php?t=2513701
Or you can use this toolkit (some people are not fans of these but I am):
http://forum.xda-developers.com/showthread.php?t=2525026
I have never heard of the issue where it was only rooted and it just randomly decides to reboot and keeps doing it for no reason at all without the user flashing something that it did not like. So are you saying that you cannot even turn the phone off it just keeps going into a bootloop and trying to enter fastboot does nothing?
I don't think this is a really well known issue.. Have not seen to many support threads about this.
mistahseller said:
Use this thread:
http://forum.xda-developers.com/showthread.php?t=2513701
Or you can use this toolkit (some people are not fans of these but I am):
http://forum.xda-developers.com/showthread.php?t=2525026
I have never heard of the issue where it was only rooted and it just randomly decides to reboot and keeps doing it for no reason at all without the user flashing something that it did not like. So are you saying that you cannot even turn the phone off it just keeps going into a bootloop and trying to enter fastboot does nothing?
I don't think this is a really well known issue.. Have not seen to many support threads about this.
Click to expand...
Click to collapse
If the wall charger is plugged into the phone, the nexus just starts rebooting. I see the white Google logo and after one or two seconds it reboots. Sometimes you see the boot animation (4 circles) but after a short time it restarts the phone not able get to the point where you unlock the SIM. Trying to get into fastboot mode is also not possible. The fastboot mode appears but after half a second the phone reboots again. If the nexus is not connected to a charger it repeats rebooting for about four times after that just a black screen appears. If I'm not able to get into fastboot mode I can't unroot the phone, right? So the links you shared are not useful in my case
I have the nexus now over a week and the phone worked perfectly fine the first week.
I have uploaded two films of the problem to youtube, see this link. One film is with the nexus plugged into the chrager and one where it isn't.
That is very strange.
I would definitely use Madpiercing's post and link to http://forum.xda-developers.com/showthread.php?t=2521691&page=3 to try and fix it.
Madpiercing said:
no problemi, i hope you can unbrick it!
Click to expand...
Click to collapse
I tried the method described in your link without success. Still the same behavior. See my last post, there I add a youtube-link where you can see what exactly happens.
Saw your video that is very strange
mistahseller said:
Saw your video that is very strange
Click to expand...
Click to collapse
The very strange thing is, that it worked well over a week. the random rebooting starts two days ago, first time it starts again correctly after 5 min. Now it seems to hang in a loop.
mistahseller said:
Saw your video that is very strange
Click to expand...
Click to collapse
After a while I was able to get into the fastboot mode: I plugged my nexus into the wall charger for about 1 hour. Then it booted correctly. I had plugged my nexus into the charger before (over night) without leading to the same result. It seems that it just starts working correctly as random as it crashes
Do you think it is a bug in the bootloader or that something happened while to rooting the phone?
majorcrampas said:
After a while I was able to get into the fastboot mode: I plugged my nexus into the wall charger for about 1 hour. Then it booted correctly. I had plugged my nexus into the charger before (over night) without leading to the same result. It seems that it just startes working correctly as random as it crashes
Do you think it is a bug in the bootloader or that something happend due to rooting the phone?
Click to expand...
Click to collapse
It's most likely a hardware issue, bad cache memory on the cpu. I'd rma it.
jd1639 said:
It's most likely a hardware issue, bad cache memory on the cpu. I'd rma it.
Click to expand...
Click to collapse
I set it up again and give it another try. If something similar should happen again, I will rma it.
majorcrampas said:
I set it up again and give it another try. If something similar should happen again, I will rma it.
Click to expand...
Click to collapse
make sure you unroot and relock the bootloader and do this now while it is working.
mistahseller said:
make sure you unroot and relock the bootloader and do this now while it is working.
Click to expand...
Click to collapse
And triangle away or reset the flag or whatever.
Sent from my Nexus 5

[q] opo qhsusb_bulk

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.

[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?

Is my Sensation bricked or not?

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.

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.

Categories

Resources