Related
Hi guys.
After two weeks without wifi, yesterday, my phone decide to update about 20 apps from market. When Beautiful Widgets were downloading, phone suddenly froze and I had to remove my battery after 10 minutes. When it booted again, Angry Birds started to update and phone froze again. So I removed my battery once again and when it booted up, I turned my net connection offline to prevent downloading. As soon as I did so, I canceled all market downloads and turned connection online again. Market started updating on its own and phone froze during night.
So I decided to removed battery once again this morning and when I put it back in, put it back in, phone froze after "Quietly Brilliant" logo with black screen.
It was suitable for factory reset from bootloader. So I did factory reset and same story repeated, except for this, it was a loading loop, HTC Quietly Brilliant and sound which comes with it over and over again.
So in the end, I tried to do the "recovery" option which did no good and again factory reset, but this time, bootloader froze and nothing happened. This is final state of my phone.
So after boring story, there is a question. Is there any way I can do software flash / reset without phone (via USB etc?) before I send it back to HTC for repair?
Device is S ON and never been rooted. I also removed SIM and memory card with no effect.
Thanks a lot!
You should take hope from the fact that you are able to still enter bootloader and perform full reset
Also the fact that you are still s-on means that you should still be covered under warranty
I believe that you should be able to re flash your original rom via your pc using RUU, check to see if your original is in the rom sticky thread within the dev section and if so start downloading
Sent from my HTC Desire S using XDA Premium App
You may well have a hardware problem, in which case I would advise you send it for repair rather than trying to root and invalidating your warranty.
Hey, thx for reply.
I have no experiences in this but I guess I only need to know this things:
RUU - Stands for ROM Upgrade Utility. What soft should I use?
Also, all I can see in bootloader is following:
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0000
RADIO-38.03.02.11_M
eMMC-boot
Mar 10 2011,14:58:38 (<wtf?)
and then just classic boot menu with options like FASTBOOT etc.
Therefore I cant figure out, which ROM is mine in that thread. Also, is there any option to flash ROM from memory card? Does it have to be signed?
Only limitation is warranty which I dont wanna lose. Thx.
InfernalByte said:
You may well have a hardware problem, in which case I would advise you send it for repair rather than trying to root and invalidating your warranty.
Click to expand...
Click to collapse
See the statement above, I will not do anything to invalidate the warranty.
Yesterday, after attempting the "Update all" for the first time (well, not exactly) the phone froze just as yours did & started encountering the same issues. After coming here to seek assistance, this thread was the first I laid eyes upon.
My case in somewhat more detail, after freezing during the "Update all", I performed a soft reset by removing the battery as well, booted up fine, but as soon as everything was loaded the market tried to continue where it left off (which is updating Opera Mobile @ 98%) and the result was another freeze. I was quickly able to deduct that the update were to be the issue & turned off connectivity. Now, at the present state, Opera Mobile update is still under notifications (at 98% complete but "paused"), as soon as I re-enable either WiFi or 3G it continues & crashes. I cleared all caches & reset all Market applications & rebooted to no avail.
Hard reset was next on my list, but see-ing how the situation got worse for your device hereafter, I am holding it off for now. Is it possible to have market updates, that are ongoing, canceled? Bear in mind that I cant enter Market since it requires connectivity.
Weird stuff.
Yes, when your phone is turned on (connection on), open your Market app, press menu button and select "My apps". You should see all downloading apps now. Hold your finger on each and wait until menu pops up. Select cancel download. You have to be quick tho.
If I were you, I would not do any software reset, my phone is pretty much bricked now, as it freezes on nearly every bootloader option.
Numline1 said:
Yes, when your phone is turned on (connection on), open your Market app, press menu button and select "My apps". You should see all downloading apps now. Hold your finger on each and wait until menu pops up. Select cancel download. You have to be quick tho.
If I were you, I would not do any software reset, my phone is pretty much bricked now, as it freezes on nearly every bootloader option.
Click to expand...
Click to collapse
Thanks! That did the trick, was able to remove everything due to be updated.
Strangely, though, I wasn't able to finish loading the market before it resumed the Opera update. This time, however, instead of crashing it was able to complete it (contrary to the last 10+ attempts yesterday), thus there is a chance it wouldn't have crashed at all. In any case, keeping distance from the Market seems like a valid idea for now.
Reading your thread might've helped to avoid my device turning into a brick, I appreciate it.
Well, update to my current status:
Im still in hboot. Device was recognized as "Android 1.0" in my Windows, so I had to install ADB driver. It is now connected as Android Composite ADB Interface".
I can't get any further, since RUU says my phone is not connected to PC.
Any advices please?
PS: When I choose "Recovery" in hboot, it shows HTC logo for a while, then icon of mobile phone with green sign shows and after few secs, screen turns off and phone vibrate for a few times and disconnects from PC.
//When I connect it in Fastboot, it shows as "MyHTC" in Windows.
Numline1 said:
PS: When I choose "Recovery" in hboot, it shows HTC logo for a while, then icon of mobile phone with green sign shows and after few secs, screen turns off and phone vibrate for a few times and disconnects from PC.
Click to expand...
Click to collapse
Afraid, that I'm well out of my depth with all that, hopefully someone else with more knowledge will post...or else it's warranty return. best of luck
Np, thx for trying, maybe someone else will know
//Update: In Fastboot mode, my device is recognized by RUU!!! Trying to update right now!!!
As you've never been rooted or S-off, and the phone has developed its own fault. I'd return it!
Well, so far, no luck. RUU stuck at "Rebooting to bootloader" and phone is frozen.
InfernalByte said:
As you've never been rooted or S-off, and the phone has developed its own fault. I'd return it!
Click to expand...
Click to collapse
Im willing to do that first thing tommorow, but Im trying to fix it today, as it is sunday and I have day off.
Numline1 said:
Well, so far, no luck. RUU stuck at "Rebooting to bootloader" and phone is frozen.
Im willing to do that first thing tommorow, but Im trying to fix it today, as it is sunday and I have day off.
Click to expand...
Click to collapse
Good luck
(....10 Chars...)
Ok, update about my phone so far:
RUU was not sucessful, for some reason there's still freeze in certain HBOOT actions, like when I select "Factory reset" or when RUU is trying to get phone from fastboot to bootloader.
So I extracted rom.zip from my RUU and now I'm backing up my memory card using my old phone. I'm willing to rename it to update.zip and try to flash it.
Any advices about this?
Numline1 said:
Ok, update about my phone so far:
RUU was not sucessful, for some reason there's still freeze in certain HBOOT actions, like when I select "Factory reset" or when RUU is trying to get phone from fastboot to bootloader.
So I extracted rom.zip from my RUU and now I'm backing up my memory card using my old phone. I'm willing to rename it to update.zip and try to flash it.
Any advices about this?
Click to expand...
Click to collapse
Update.zip will not work, if your determined to try something push a new SPL via fastboot commander, even thought your not S-off if things aren't working maybe the CID check wont check either.
Below will only work if your phone is not branded or you have a goldcard.
Alternatively unzip your RUU on your PC in one of the files called {squigly brackets and a lot of numbers673652435364849483763} you'll find a .zip called rom.zip rename this PB99IMG and put the file into the root directory of your SD card, and boot into Hboot. Just answer yes to any questions. This is the way HTC Tech folk themselves serve an RUU.
Yea, I actually extracted it using advanced system monitor from microsoft, this file was in temp folder. That's where my rom.zip was. Anyway, isn't it PB88IMG.zip? I think DS is checking for this one. Thx.
//Edit: I mean PB88IMG.img
//Edit2: It's PG88IMG.zip It's now updating, don't know if it works yet, still at BOOTLOADER update with status "Updating".
Ok, I think this is my last post, since I no longer know what else to do. When Im trying to flash PG88IMG, it stops at [1]BOOTLOADER - Updating.
For more than one hour. There's something wrong with it and I will claim my warranty, which will be funny, since Im in Slovakia, phone was bought from Amazon with 3 year warranty from SquareTrade and they claim, they may just return money in some cases, which will result in buying a new phone = more than 2 weeks...
Numline1 said:
they may just return money in some cases, which will result in buying a new phone = more than 2 weeks...
Click to expand...
Click to collapse
O, bugger!
question is if they do give you the money, will you buy another DS? and if not what would you consider instead? Sensation?
Yea, can't say yet, since I don't know. I just discovered, there may be a chance they will cover my repair costs when I email them all the service documentation from service center.
But if they do, I'd like to stay with HTC, I paid something about 377L for the phone, so I may buy something better now.
Anyway, thanks a lot for help guys, if you come with some new ideas about how to fix it, do not hesitate to tell me I'll be sending it to them first thing tommorow.
Ok guys, new to the forums but this problem has had me fully occupied for the last 6 hours and I feel like I have tried everything. I had cm9 alpha 12, and went to flash TrickDroid v5.0, something happened and I'm currently stuck in some wierd bootloop/soft brick. I had access to CWM but my SD card wouldn't mount and my adb push attempts didn't do anything, for reasons I don't know why. My phone would start up into the wierd trickdroid bootup and last for like 30 minutes. I tried the solution of another thread on how to fix a bootloop/ softbrick, but now I dont have any CWM access and I can only access the bootloader or the endless bootup screen. I tried using the all in one tool to flash the CWM again but it just restarts it and puts it back into the bootup, and when i restart to go to bootloader to acess the recovery, it goes back to bootup. Every solution I try makes my problem worse, and to top it off I cant turn my phone off and keep it off because it will just start back up. Thanks.
Edit: Problem fixed. Downloaded the original all in 1 tool for htc one s, plugged phone into comp went to fastboot and with the tool flashed the phones stock recovery. I reset to factory defaults and cleared storage with it from the bootloader. After that, I flashed clockwork mod recovery again and my SD card was able to be mounted and accepted files from my adb push, and I reflashed cyanogenmod. Wuzzah!
milesmarrero said:
Ok guys, new to the forums but this problem has had me fully occupied for the last 6 hours and I feel like I have tried everything. I had cm9 alpha 12, and went to flash TrickDroid v5.0, something happened and I'm currently stuck in some wierd bootloop/soft brick. I had access to CWM but my SD card wouldn't mount and my adb push attempts didn't do anything, for reasons I don't know why. My phone would start up into the wierd trickdroid bootup and last for like 30 minutes. I tried the solution of another thread on how to fix a bootloop/ softbrick, but now I dont have any CWM access and I can only access the bootloader or the endless bootup screen. I tried using the all in one tool to flash the CWM again but it just restarts it and puts it back into the bootup, and when i restart to go to bootloader to acess the recovery, it goes back to bootup. Every solution I try makes my problem worse, and to top it off I cant turn my phone off and keep it off because it will just start back up. Thanks.
Click to expand...
Click to collapse
lol, meant to "quote" not "thanks".
Can you fastboot a new recovery?
Did you do a full wipe coming from CM9 to TrickDroid
Well I can't access the phone from usb on my computer (still takes charge though), so I don't think I can flash a recovery thru fastboot (I'm not too experienced though). From cm9, I wiped all and flashed trickdroid + tweak set, then it just stat their at home screen. CMW being lost occurred later.
Im in the same situation rght now. I have trickdroid and I went into my tweaks to set them back to their original setup...so removing all of the options I chose before when I used the tweaks for the first time. When I rebooted my phone it just hangs on the HTC screen. I can get into recovery and I tried reinstalling trickdroid but its still getting stuck. Not sure what to do at this point. I don't think I can put a recovery file on this since I can't connect it to my computer.
Hopefully someone can help us.
But the thing is I can't access recovery. I try to flash it again with the all in 1 tool and it won't work. It says it went through, but accessing it doesn't work.
If its recognised by USB when plugged in computer just run an ruu that's my solution all The time lol
Sent from my HTC One S using xda premium
Ok i somehow managed to get TWR on my phone, but still unable to mount the SD. How do I run the RUU? I downloaded it, but the instructions are flawed I think
Connect with USB to.computer go into faatboot USB then run ruu on pc
Sent from my HTC One S using xda premium
Well I thought the RUU was going to work, but it just stops at the HTC and gives me an error saying I can't. What now?
Ok currently, I relocked my bootloader in an attempt to do the RUU, but I get a 155 Unknown Error up doing such, using the TMOUS 1.53 ruu... other places I have seen say something about returning to the stock img etc, but I'm quite stuck. Any advice appreciated
htc one s stuck in bootloop almost unresponsive
hey guys, got a brain teaser for you.
i have a tmobile htc one s, unlocked, rooted using all in one htc tool, been at it for two days now. im stuck on the boot screen showing its unlocked, i used to be able to get into the boot loader screen but now it seems ive dead ended. ill hold any combination of power and vol up/down, the keys flash for 10 sec and the screen flashes once, i let go and it reboots, keeps that htc screen, after 20-30 sec goes black. my pc doings like it detects a device but i cant locate it. ive used adb and the htc all in one unlock tool trying to get any kind of os to launch.
Shortly before this i was able to go into the boot loader, clear and master reset the files and cache, and search for the rom zip, thus never allowing me to flash. on a journey to place this in the phone through various combinations of the all in one, adb push, and everything else i found on youtube, countless forum posts, i seem to be in a deeper hole now.
I ultimately want to end with a cm10 nightly on my tmo htc one s. I have never done this to a phone without a sd card. i come to this community humbly seeking any and all advice. thank you.
Hi all,
I've spent a good two hours trying to figure this out. Generally I'm pretty good at these things, but there just isn't that much action or information on the Blu Life Play when things go wrong (L100a)
http://forum.xda-developers.com/showthread.php?t=2370987
In reference to the above link, I followed all instructions to a T. My phone is rooted just fine, all that is working perfectly. However, once I tried installing CWM using the first method, mobileuncle, not only did it fail, but it also entirely broke my recovery mode! Whenever I try to boot into recovery (vol+/power) I get a black screen until the phone eventually reboots itself.
I then tried method two using the flashing tool, SPFT. I used something similar pretty often, ODIN, with my old Samsung Epic. Again I run into a problem: I can't keep the phone connected long enough to allow SPFT to finish flashing the recovery. As instructed, I plug in the USB cable with the battery out, my computer chimes to let me know it has recognised the device, but- Three seconds later, it chimes again to let me know it has disconnected.
SPFT follows suit, detecting and starting the flash then getting interrupted 2 seconds later.
My phone is still able to boot, it is not bricked. However, it is very distressing to have no access to a recovery mode.
Help?
I have the same issue. Got my phone replaced under warranty and the new one I got yesterday will not boot to recovery. Only black screen. Hopefully we can figure out the issues.
issact said:
Hi all,
I've spent a good two hours trying to figure this out. Generally I'm pretty good at these things, but there just isn't that much action or information on the Blu Life Play when things go wrong (L100a)
http://forum.xda-developers.com/showthread.php?t=2370987
In reference to the above link, I followed all instructions to a T. My phone is rooted just fine, all that is working perfectly. However, once I tried installing CWM using the first method, mobileuncle, not only did it fail, but it also entirely broke my recovery mode! Whenever I try to boot into recovery (vol+/power) I get a black screen until the phone eventually reboots itself.
I then tried method two using the flashing tool, SPFT. I used something similar pretty often, ODIN, with my old Samsung Epic. Again I run into a problem: I can't keep the phone connected long enough to allow SPFT to finish flashing the recovery. As instructed, I plug in the USB cable with the battery out, my computer chimes to let me know it has recognised the device, but- Three seconds later, it chimes again to let me know it has disconnected.
SPFT follows suit, detecting and starting the flash then getting interrupted 2 seconds later.
My phone is still able to boot, it is not bricked. However, it is very distressing to have no access to a recovery mode.
Help?
Click to expand...
Click to collapse
zironia said:
I have the same issue. Got my phone replaced under warranty and the new one I got yesterday will not boot to recovery. Only black screen. Hopefully we can figure out the issues.
Click to expand...
Click to collapse
Hey, it's good to hear I'm not alone in this. lopestom has been friendly enough to correspond with me about it and he suspects it's a new model of the same phone. I sent him a screen cap of the factory settings screen (VOL-/POW)
In the end we might be out of luck until more people get their hands on the new version of the phone.
Hey folks...I'm running into a problem I was hoping someone might be able to help with.
Earlier today I pulled my phone out of my pocket at work and saw that it was off...I thought that the battery must have died sooner than I thought. I started charging it in the car on the way home and it wouldn't boot up like normal. It would get to the google or "dots" screen and then reboot. I again thought that the battery might just be really low. After getting home and charging the phone all the way I still can't get it to boot up. As of now, one of 3 things will happen...
1-The phone will turn on, get to the google screen and bootloop (usually when plugged in).
2-The phone will turn on, get to the google screen and freeze.
3-Get to the "dots" screen and either swirl forever or eventually reboot and do one of the above again.
I've read some threads where people suggest this is a faulty power button, that doesn't seem to be the case for me though because I can get into fastboot and it won't select anything or turn off without me doing it.
I've used WugFresh NRT and wiped/reflashed android. I'm running out of ideas. Do you have any others?
I was running the stock 5.0.1, unlocked, not currently rooted.
Thanks!
kyle313 said:
Hey folks...I'm running into a problem I was hoping someone might be able to help with.
Earlier today I pulled my phone out of my pocket at work and saw that it was off...I thought that the battery must have died sooner than I thought. I started charging it in the car on the way home and it wouldn't boot up like normal. It would get to the google or "dots" screen and then reboot. I again thought that the battery might just be really low. After getting home and charging the phone all the way I still can't get it to boot up. As of now, one of 3 things will happen...
1-The phone will turn on, get to the google screen and bootloop (usually when plugged in).
2-The phone will turn on, get to the google screen and freeze.
3-Get to the "dots" screen and either swirl forever or eventually reboot and do one of the above again.
I've read some threads where people suggest this is a faulty power button, that doesn't seem to be the case for me though because I can get into fastboot and it won't select anything or turn off without me doing it.
I've used WugFresh NRT and wiped/reflashed android. I'm running out of ideas. Do you have any others?
I was running the stock 5.0.1, unlocked, not currently rooted.
Thanks!
Click to expand...
Click to collapse
Did you try flashing factory images?
ryukiri said:
Did you try flashing factory images?
Click to expand...
Click to collapse
Yeah, that was what I flashed :/
If you can get into fastboot you "should" be able to flash stock images... Obviously this will revert any root and you will need to flash TWRP/CWM recovery after.
I assume you have a Windows PC with fastboot/adb setup and all drivers etc..
- Download latest "stock" hammerhead images (I cannot post links due to XDA rules... so: "developers.google.com/android/nexus/images#hammerhead"
- Extract the .tgz archive contents on your PC into a folder
- Boot the N5 into fastboot and plug USB cable from phone into your PC
- Go to the folder with the extracted files and run the "flash-all.bat" script on Windows
**Hopefully at this point your device will start to respond.. I.e, on fastboot screen, at the bottom you will see "writing" or something, as the script runs on the command window on your PC.**
If this works, you should be able to reboot once complete and then wait to see if you can get back into your phone.. then you can fastboot again and flash custom recovery, and then whatever rom.
If however you have a hardware issue (i.e, even after the above process it fails) then I am not sure what you could do... I guess ensure it has a complete charge. If you can get into fastboot and the buttons are responsive then it should not be a faulty power button.
Hope this helps :good:
Have you tried a simple factory reset? Reason I ask is it was working fine so sounds like something needs "flushing out" clear cache etc.
kyle313 said:
Hey folks...I'm running into a problem I was hoping someone might be able to help with.
Earlier today I pulled my phone out of my pocket at work and saw that it was off...I thought that the battery must have died sooner than I thought. I started charging it in the car on the way home and it wouldn't boot up like normal. It would get to the google or "dots" screen and then reboot. I again thought that the battery might just be really low. After getting home and charging the phone all the way I still can't get it to boot up. As of now, one of 3 things will happen...
1-The phone will turn on, get to the google screen and bootloop (usually when plugged in).
2-The phone will turn on, get to the google screen and freeze.
3-Get to the "dots" screen and either swirl forever or eventually reboot and do one of the above again.
I've read some threads where people suggest this is a faulty power button, that doesn't seem to be the case for me though because I can get into fastboot and it won't select anything or turn off without me doing it.
I've used WugFresh NRT and wiped/reflashed android. I'm running out of ideas. Do you have any others?
I was running the stock 5.0.1, unlocked, not currently rooted.
Thanks!
Click to expand...
Click to collapse
Did you choose the right model and firmware before you flash in WugFresh NRT?
The above could be right, however when I've used it, it's pointed out if I made that mistake. Having used his software dozens of times I've found it will bring any Nexus 5 back to life.
howard bamber said:
The above could be right, however when I've used it, it's pointed out if I made that mistake. Having used his software dozens of times I've found it will bring any Nexus 5 back to life.
Click to expand...
Click to collapse
Hello! I am apologize for that I didn't read the OP carefully. This happened to me once in that particulary way, but it was immediately after flashing. OP says that it happened suddenly, without reason. So now I am the one, who doesn't read, right? Sorry for that.
Regards, Zagor
Thanks for the responses, but I'm still having trouble.
I have been able to successfully write the newest stock android 3 times (1 without full wipe, 2 with) and the phone still can't boot up and goes through one of the three issues above.
I've also been able to get to the system recovery from the bootloader and I've tried wiping the cache and doing a factory reset from there and the problem remains.
I'd contact google, but I bought it at launch so I don't think they'll do anything for me since it's been 1+ years.
kyle313 said:
Thanks for the responses, but I'm still having trouble.
I have been able to successfully write the newest stock android 3 times (1 without full wipe, 2 with) and the phone still can't boot up and goes through one of the three issues above.
I've also been able to get to the system recovery from the bootloader and I've tried wiping the cache and doing a factory reset from there and the problem remains.
I'd contact google, but I bought it at launch so I don't think they'll do anything for me since it's been 1+ years.
Click to expand...
Click to collapse
Sounds like you have a bad nand sector. From fastboot try:
Code:
fastboot oem lock
Then reboot into fastboot and check if it's locked or not. If the device isn't locked your emmc is corrupt and there is nothing you can do. If that is the case call Google and they will most likely help you out with a RMA.
theesotericone said:
Sounds like you have a bad nand sector. From fastboot try:
Code:
fastboot oem lock
Then reboot into fastboot and check if it's locked or not. If the device isn't locked your emmc is corrupt and there is nothing you can do. If that is the case call Google and they will most likely help you out with a RMA.
Click to expand...
Click to collapse
I was actually able to relock the phone.
Luckily I called google and they're going to send me a replacement.
If anyone else has any other ideas, I'll still take them...I'd rather not be without a phone for the next week!
You won't be without a phone - they are sending a refurbish unit to you , putting a block on your credit card and waiting for you phone to arive at them. Once that happens they will release the funds.
Hello guys,
so two days ago just when I was heading into work my phone randomly started restarting itself again and again. I had it in my pocket, mobile data and wifi off and nothing really going on when this happened. I was on stock Cyanogen OS with 6.0.1, rooted and with Xposed, but nothing too crazy or experimental.
The phone would boot with a small vibration to the Oneplus logo with the "Powered by Android" writing, stay on that for about 17-18 seconds, then reboot again. No way of going to the recovery with the hardware keys, it would just reboot the same again and again. Since I couldn't really do much, not turn it off and no way of disconnecting the battery, I just had to watch it reboot helplessly until the battery was dead. At home with some hassle I could get it charged again, which basically consisted of charging it while it kept rebooting and cooling it while doing that since it would get really, really hot.
The only option that really works is is getting it into fastboot via the volume up + power button. But in fastboot nothing I did so far changed even the smalles thing about it's behaviour. I tried flashing a new recovery image, letting it boot into the recovery via fastboot (both stock recovery and TWRP), reflashing the complete OS via fastboot again (CM 13 ZNH2KAS3P0), completely wiping it via fastboot and flashing an older ROM (CM11S XNPH44S) but so far nothing has even changed a thing. It keeps booting to the Oneplus logo for about 17-18 seconds before rebooting. The only thing that has changed is with the CM11S ROM the fastboot logo of the android head is now bigger.
I checked the bootloader via fastboot, but it's still unlocked.
So yeah, I'm at my wits end and desperate for any help. At this point I fear it might be a hardware issue and I can trash it, but I'm ready to grasp for straws as I don't really have the money for a new device yet.
Any help is appreciated! Thanks guys!
Atomschlumpf said:
Hello guys,
so two days ago just when I was heading into work my phone randomly started restarting itself again and again. I had it in my pocket, mobile data and wifi off and nothing really going on when this happened. I was on stock Cyanogen OS with 6.0.1, rooted and with Xposed, but nothing too crazy or experimental.
The phone would boot with a small vibration to the Oneplus logo with the "Powered by Android" writing, stay on that for about 17-18 seconds, then reboot again. No way of going to the recovery with the hardware keys, it would just reboot the same again and again. Since I couldn't really do much, not turn it off and no way of disconnecting the battery, I just had to watch it reboot helplessly until the battery was dead. At home with some hassle I could get it charged again, which basically consisted of charging it while it kept rebooting and cooling it while doing that since it would get really, really hot.
The only option that really works is is getting it into fastboot via the volume up + power button. But in fastboot nothing I did so far changed even the smalles thing about it's behaviour. I tried flashing a new recovery image, letting it boot into the recovery via fastboot (both stock recovery and TWRP), reflashing the complete OS via fastboot again (CM 13 ZNH2KAS3P0), completely wiping it via fastboot and flashing an older ROM (CM11S XNPH44S) but so far nothing has even changed a thing. It keeps booting to the Oneplus logo for about 17-18 seconds before rebooting. The only thing that has changed is with the CM11S ROM the fastboot logo of the android head is now bigger.
I checked the bootloader via fastboot, but it's still unlocked.
So yeah, I'm at my wits end and desperate for any help. At this point I fear it might be a hardware issue and I can trash it, but I'm ready to grasp for straws as I don't really have the money for a new device yet.
Any help is appreciated! Thanks guys!
Click to expand...
Click to collapse
how old is the device?
As far as I know my sister bought it around summer 2014 when it was released, I got it in late 2015
Atomschlumpf said:
As far as I know my sister bought it around summer 2014 when it was released, I got it in late 2015
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
AFAIK,If this toolkit can't fix your device then it's definitely hw issue.
Mr.Ak said:
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
AFAIK,If this toolkit can't fix your device then it's definitely hw issue.
Click to expand...
Click to collapse
Well, the tool won't even recognize my phone, so I guess I'm **** out of luck ¯\_(ツ)_/¯
****ing great....
Atomschlumpf said:
Well, the tool won't even recognize my phone, so I guess I'm **** out of luck ¯\_(ツ)_/¯
****ing great....
Click to expand...
Click to collapse
Lol,gave up that early?
It needs around 10 tries to get it correctly recognised.
Use XP system with the proper drivers given in the above thread.This tool doesn't work on adb/fastboot,it works on Usb Debugging Port,hence requires different drivers.
Mr.Ak said:
Lol,gave up that early?
It needs around 10 tries to get it correctly recognised.
Use XP system with the proper drivers given in the above thread.This tool doesn't work on adb/fastboot,it works on Usb Debugging Port,hence requires different drivers.
Click to expand...
Click to collapse
No, I didn't. I tried the USB Drivers I had already installed, the drivers that came in the package and the QPST Tool suggested in the thread on both my and my girlfriends laptop. But if it doesn't work on ADB/fastboot I probably can't use it anyway since my only two options are having the phone on the fastboot screen or having it constantly reboot....
At this point I'm just really, really frustrated and have sorta accepted it's very likely a hardware issue
I'm with the same problem. In my case, the tool does recognize and shows green after the end but when i try to boot, it only shows the boot logo.
I can enter in fastboot and trying the command "fastboot continue" the brightness goes up, but nothing else
already tried various tools, back to stock, qualcomm , and none worked, so can i throw it out of the window?
Edit: can't enter in recovery, and unlike the op, my phone doesn't reboot (at least i didn't notice it)