Hi guys, I'm very sorry if this has been solved already but I've been searching a lot now and none of the methods seemed to help me. I'm running a One X International. Until yesterday, I was running one of the older Cyanogenmod 10 Nightly builds but due to some performance issues and whatnot (nothing major), I decided to finally put in some work to update my phone to 10.1. My HBOOT was still on one of the older versions so after searching around, it seemed reinstalling the stock ICS and then doing some OTA updates would be the easiest way (for a n00b like me).
After doing so, I unlocked my bootloader again, re-rooted my phone, installed a newer version of CWM Recovery and finally flashed the latest stable build of CM 10.1. My first problem came after rebooting, where it would just hang at the Cyanogenmod ring loop and nothing else. I booted back to recovery and wiped everything (cache, data, dalvik etc.) and did a factory reset then reflashed the rom. This time it booted up but then, the "Unfortunately, the process com.android.phone has stopped." kept popping up. I literally can't do anything (there's a microsecond of space after I click OK before it would pop up again). I have read some people suggesting to others that they need to do a factory reset but I've tried doing that and it still didn't work. I've even tried installing the latest Nightly build of CM10.1 but it still didn't seem to make any difference.
Could someone please offer some advice? Thanks a lot in advance.
I had this problem and it was an hardware fault, so the only thing i could to was to send back the phone to HTC and get a new one...
MarcusJKX said:
Could someone please offer some advice? Thanks a lot in advance.
Click to expand...
Click to collapse
Did you flash the boot image?, and if so, did you fastboot erase cache after flashing the boot image?
matt95 said:
I had this problem and it was an hardware fault, so the only thing i could to was to send back the phone to HTC and get a new one...
Click to expand...
Click to collapse
I'm hoping that it's not and somehow I doubt it since I didn't have any problems like this until what I described earlier.
Did you flash the boot image?, and if so, did you fastboot erase cache after flashing the boot image?
Click to expand...
Click to collapse
I'm sorry, I'm not quite sure what you mean. Do you mean Boot image as in the bootloader? I didn't touch the bootloader except that it got upgraded whilst I updated the official HTC rom and also when I unlocked it. But I did erase everything before flashing.
MarcusJKX said:
I'm sorry, I'm not quite sure what you mean. Do you mean Boot image as in the bootloader? I didn't touch the bootloader except that it got upgraded whilst I updated the official HTC rom and also when I unlocked it. But I did erase everything before flashing.
Click to expand...
Click to collapse
he means
Code:
fastboot flash boot boot.img
matt95 said:
I had this problem and it was an hardware fault, so the only thing i could to was to send back the phone to HTC and get a new one...
Click to expand...
Click to collapse
matt95 said:
he means
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
I don't think I did this. What is it for? I don't remember reading it in any guides although I read so many that I might've have forgotten.
MarcusJKX said:
I don't think I did this. What is it for? I don't remember reading it in any guides although I read so many that I might've have forgotten.
Click to expand...
Click to collapse
you have to flash the boot.img everytime u flash different rom
it is inside the zip file of the rom just extract it from there and take your phone to the bootloader and flash the boot.img...thn it will work perfectly
have a good read on how to flash a rom
http://forum.xda-developers.com/showthread.php?t=2069904
ll_r1d0_ll said:
you have to flash the boot.img everytime u flash different rom
it is inside the zip file of the rom just extract it from there and take your phone to the bootloader and flash the boot.img...thn it will work perfectly
Click to expand...
Click to collapse
Thanks a lot! I can't right now because like an idiot, I was in a rush before coz I had to leave for a few hours and really needed my phone so I thought maybe I'd try redoing the process. I got to the stage where I relocked the bootloader, factory reset, erased the rom, cache and pretty much everything but then I had to leave. Now that I'm back, the phone is out of battery coz I had it plugged in but it just wouldn't shut down for some reason so the screen remained on the bootloader wasting a ton of battery. This had happened yesterday when I was doing this and the battery would charge really slowly since the screen was constantly on. Do you know why this is? I don't think it's a hardware issue since after installing the stock rom yesterday, it could turn the phone off through the bootloader, recovery or just in the actual OS.
MarcusJKX said:
Thanks a lot! I can't right now because like an idiot, I was in a rush before coz I had to leave for a few hours and really needed my phone so I thought maybe I'd try redoing the process. I got to the stage where I relocked the bootloader, factory reset, erased the rom, cache and pretty much everything but then I had to leave. Now that I'm back, the phone is out of battery coz I had it plugged in but it just wouldn't shut down for some reason so the screen remained on the bootloader wasting a ton of battery. This had happened yesterday when I was doing this and the battery would charge really slowly since the screen was constantly on. Do you know why this is? I don't think it's a hardware issue since after installing the stock rom yesterday, it could turn the phone off through the bootloader, recovery or just in the actual OS.
Click to expand...
Click to collapse
the phone never charges in the bootloader ....as ur phone is off right now just plug it to a wall charger and leave it for around 2-3 hours and check if the Red LED turns on which will show that your phone is charging
ll_r1d0_ll said:
the phone never charges in the bootloader ....as ur phone is off right now just plug it to a wall charger and leave it for around 2-3 hours and check if the Red LED turns on which will show that your phone is charging
Click to expand...
Click to collapse
Aha didn't know that! Well I did leave it on the charger before i left although it was on the bootloader so like you said, it didn't charge. But when i came back (several hours later), the screen was black and the red LED was not on. Again like an idiot, I tried to turn it on and it went into the bootloader although it said that the battery is critically low. I then tried restarting it and now it's staying on the HTC Quietly Brilliant screen. Does it charge here? The red LED is on. If i press power+vol down then it would go into the bootloader so i guess it's not bricked right?
MarcusJKX said:
Aha didn't know that! Well I did leave it on the charger before i left although it was on the bootloader so like you said, it didn't charge. But when i came back (several hours later), the screen was black and the red LED was not on. Again like an idiot, I tried to turn it on and it went into the bootloader although it said that the battery is critically low. I then tried restarting it and now it's staying on the HTC Quietly Brilliant screen. Does it charge here? The red LED is on. If i press power+vol down then it would go into the bootloader so i guess it's not bricked right?
Click to expand...
Click to collapse
nop its not bricked and if your phone is now on just press the power button for few seconds until the 3 buttons flash and it wll turn off and when your phone will have enough battery charged it will automatically turn on (my htc one x do this) and dn you continue the steps dat i told you
ll_r1d0_ll said:
nop its not bricked and if your phone is now on just press the power button for few seconds until the 3 buttons flash and it wll turn off and when your phone will have enough battery charged it will automatically turn on (my htc one x do this) and dn you continue the steps dat i told you
Click to expand...
Click to collapse
Hmm i still can't turn it off. After holding the power button and waiting for the 3 buttons to flash, it would just reboot into the HTC screen. But it seems to be charging because when I booted into the bootloader just then, it doesn't say "power critically low" anymore.
By the way, whilst we're on the subject, do you know if it's possible to disable the ability to restart the phone by holding down the power button even when the phone is locked? I have quite a bulky case (from Ballistic) which makes the power button stick out a bit and sometimes when it's in my jeans and I kneel down to tie my shoelace, my leg would press into the button making the phone restart. This doesn't happen with the iPhone for example. on the iPhone, when the screen is locked, the power button doesn't give any response and even when the screen is unlocked, holding down the power button will only display the option to shut it off. This has always annoyed me on the One X (don't know if this is the case for other Android phones).
MarcusJKX said:
Hmm i still can't turn it off. After holding the power button and waiting for the 3 buttons to flash, it would just reboot into the HTC screen. But it seems to be charging because when I booted into the bootloader just then, it doesn't say "power critically low" anymore.
By the way, whilst we're on the subject, do you know if it's possible to disable the ability to restart the phone by holding down the power button even when the phone is locked? I have quite a bulky case (from Ballistic) which makes the power button stick out a bit and sometimes when it's in my jeans and I kneel down to tie my shoelace, my leg would press into the button making the phone restart. This doesn't happen with the iPhone for example. on the iPhone, when the screen is locked, the power button doesn't give any response and even when the screen is unlocked, holding down the power button will only display the option to shut it off. This has always annoyed me on the One X (don't know if this is the case for other Android phones).
Click to expand...
Click to collapse
very good now ur phone is charging and i hope u have flashed the boot.img too well i also have that issue with that button :/ but i keep the phone in the opposite direction like the headphone jack side goes inside pocket and the mic side is on the outside whn inside the pocket ....thats the only idea i use :/
ll_r1d0_ll said:
very good now ur phone is charging and i hope u have flashed the boot.img too well i also have that issue with that button :/ but i keep the phone in the opposite direction like the headphone jack side goes inside pocket and the mic side is on the outside whn inside the pocket ....thats the only idea i use :/
Click to expand...
Click to collapse
Yeah I guess that's the only solution then. Glad I'm not the only one!
I just got home and it looks like I was wrong. The phone's screen was off and no red LED lights were showing even though it's plugged into the wall. I disconnected it and waited a few seconds and then reconnected it and after a couple of minutes, the red LED came back but it also started up into the bootloader automatically...this thing just won't stay off!! I will see what happens after an hour or so but at the moment, I can't think of what else I can do to shut it off to charge it.
By the way, as I said earlier, I have now resetted everything, cleared everything and relocked my bootloader. Can I flash the unlock_code.bin I got previously from HTC or has my Token ID changed now and I need to obtain a new one? I did a Google search and it sounds like it will have now changed but I just wanna make sure.
EDIT: ok I need to go to bed now but I just realised that the reason why it won't switch off is BECAUSE it is plugged in. After unplugging it and selecting Power Down from the bootloader menu, it's now switched off. But as soon as i plug it in again, the screen lights up again. I guess i have to leave it like this and hope that it charges overnight but I'm a bit worried that it's not so good for the screen not to mention it seems to get a little warm after awhile. We'll see...
MarcusJKX said:
Yeah I guess that's the only solution then. Glad I'm not the only one!
I just got home and it looks like I was wrong. The phone's screen was off and no red LED lights were showing even though it's plugged into the wall. I disconnected it and waited a few seconds and then reconnected it and after a couple of minutes, the red LED came back but it also started up into the bootloader automatically...this thing just won't stay off!! I will see what happens after an hour or so but at the moment, I can't think of what else I can do to shut it off to charge it.
By the way, as I said earlier, I have now resetted everything, cleared everything and relocked my bootloader. Can I flash the unlock_code.bin I got previously from HTC or has my Token ID changed now and I need to obtain a new one? I did a Google search and it sounds like it will have now changed but I just wanna make sure.
EDIT: ok I need to go to bed now but I just realised that the reason why it won't switch off is BECAUSE it is plugged in. After unplugging it and selecting Power Down from the bootloader menu, it's now switched off. But as soon as i plug it in again, the screen lights up again. I guess i have to leave it like this and hope that it charges overnight but I'm a bit worried that it's not so good for the screen not to mention it seems to get a little warm after awhile. We'll see...
Click to expand...
Click to collapse
no u just have to use the old unlock unlock_code.bin ....just charge it for 1-2 hours only and flash the boot.img in the bootloader and your go to go
ll_r1d0_ll said:
no u just have to use the old unlock unlock_code.bin ....just charge it for 1-2 hours only and flash the boot.img in the bootloader and your go to go
Click to expand...
Click to collapse
Thanks a lot man. So turns out that once again, it wasn't actually charging and the phone was dead when I woke up. So then I found another thread where someone had a similar issue and this was suggested:
mevorach said:
Hi
I have a solution for you
make a batch file :
" @echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
"
put this file in the directory where you have fastboot.exe adb.exe and all other
files , also put the unlock.bin file that you have from htcdev
put your phone to bootfsatusb , and run the batch file , you will see the voltage
off the battry each time it loop , after an hour or two you will have enough power(~3.68mv) to unlock it , then charge it and do what ever you want
Click to expand...
Click to collapse
I did that and left it for a couple of hours and then the battery was at a high enough level for me to get to work again. I went through everything again remembering to flash the boot.img before flashing my new ROM and now everything is working perfectly! By the way, that guide written by hasoon2000 made a mistake I think. He said to flash the boot.img AFTER flashing the new rom which I did but then still got that com.android.phone problem. But then I flashed it again BEFORE flashing CM10.1 and now everything is smooth as butter.
Anyways, thanks all for your help. I really appreciate it!
MarcusJKX said:
Thanks a lot man. So turns out that once again, it wasn't actually charging and the phone was dead when I woke up. So then I found another thread where someone had a similar issue and this was suggested:
I did that and left it for a couple of hours and then the battery was at a high enough level for me to get to work again. I went through everything again remembering to flash the boot.img before flashing my new ROM and now everything is working perfectly! By the way, that guide written by hasoon2000 made a mistake I think. He said to flash the boot.img AFTER flashing the new rom which I did but then still got that com.android.phone problem. But then I flashed it again BEFORE flashing CM10.1 and now everything is smooth as butter.
Anyways, thanks all for your help. I really appreciate it!
Click to expand...
Click to collapse
glad to know that your htc one x is running like a fire well that method is just to show the current battery level nothing else ...and i had flashed the boot.img after the room but it worked for me cux i did fix permission wipe davlik cache and partition cache too...on some roms it works for me and on some roms it doesnt..well its better if you flash the boot.img before installing the room well um glad to help you and sort out your problem
Related
Woke up this morning and my N7 wouldn't turn on. Plugged it in and the charging indicator came up showing at nearly full charge. Holding the power button then turned it on. Went away for an hour or two, came back and it was off. When I turned it back on it was stuck on the X screen. Forcing a reboot with power+vol just led to the tablet turning off. And now I just plugged it into my computer and QHSUSB_DLOAD came up.
Just got the damn thing a couple days ago and it was 100% stock. Any ideas as to what may have caused this?
Just unplugged it and it turned on but is again stuck on the X. Is QHSUSB_DLOAD no longer indicative of a hard brick?
I'm a newbie here, but let's try.
If you can get to the X one, then I think it's not brick yet.
Maybe your should try to press pwer button and volume down to get to fastboot. You press this combination when your Nexus is turned off.
opticaldh said:
I'm a newbie here, but let's try.
If you can get to the X one, then I think it's not brick yet.
Maybe your should try to press pwer button and volume down to get to fastboot. You press this combination when your Nexus is turned off.
Click to expand...
Click to collapse
once I turn it off the whole cycle starts over again. It's sporadically deciding whether or not it wants to boot but I'll keep trying to get into fastboot
herculesgs said:
Woke up this morning and my N7 wouldn't turn on. Plugged it in and the charging indicator came up showing at nearly full charge. Holding the power button then turned it on. Went away for an hour or two, came back and it was off. When I turned it back on it was stuck on the X screen. Forcing a reboot with power+vol just led to the tablet turning off. And now I just plugged it into my computer and QHSUSB_DLOAD came up.
Just got the damn thing a couple days ago and it was 100% stock. Any ideas as to what may have caused this?
Click to expand...
Click to collapse
In doing a little googling it looks to be possibly caused by the update. If you look up the error, you will see a common problem where HTC bricked a bunch of different phones when they pushed an ota a while back. I would say just return it and get a new one . You could do some research and try it yourself. Are you able to get into your bootloader ( vol+ and Vol - when you trun it on)?
uprightbass360 said:
In doing a little googling it looks to be possibly caused by the update. If you look up the error, you will see a common problem where HTC bricked a bunch of different phones when they pushed an ota a while back. I would say just return it and get a new one . You could do some research and try it yourself. Are you able to get into your bootloader ( vol+ and Vol - when you trun it on)?
Click to expand...
Click to collapse
I was able to get into it this morning and I wiped my cache. The next time it decides to turn on/I can get it into the bootloader I'll try a factory reset
herculesgs said:
I was able to get into it this morning and I wiped my cache. The next time it decides to turn on/I can get it into the bootloader I'll try a factory reset
Click to expand...
Click to collapse
Well something got corrupted, but if its booting its not hard bricked (that's good news). Luckily for you as well the aosp images are up so if you want to do a restore you can snag your images, and just do a fastboot install. I hope this isn't indicative of another problem with the device itself, I still maintain that you should probably exchange your device for a new one if you did indeed do nothing to the device. It would be a shame if the same problem happened again because of a faulty component.
uprightbass360 said:
Well something got corrupted, but if its booting its not hard bricked (that's good news). Luckily for you as well the aosp images are up so if you want to do a restore you can snag your images, and just do a fastboot install. I hope this isn't indicative of another problem with the device itself, I still maintain that you should probably exchange your device for a new one if you did indeed do nothing to the device. It would be a shame if the same problem happened again because of a faulty component.
Click to expand...
Click to collapse
Yeah, I most likely will. It'll boot to the X probably once every 25 tries so there's something weird going on and it's probably safer just to return it then find a fix and have it happen again.
herculesgs said:
Yeah, I most likely will. It'll boot to the X probably once every 25 tries so there's something weird going on and it's probably safer just to return it then find a fix and have it happen again.
Click to expand...
Click to collapse
Just out of curiosity, where did you purchase it from? Does the seller recognize a lemon as returnable, would you possibly have to tell them you just didn't like it?
uprightbass360 said:
Just out of curiosity, where did you purchase it from? Does the seller recognize a lemon as returnable, would you possibly have to tell them you just didn't like it?
Click to expand...
Click to collapse
Wally world. afaik they're pretty lax on returns
update
Got into the bootloader and did a factory reset. Everything seems to be working again now
herculesgs said:
Got into the bootloader and did a factory reset. Everything seems to be working again now
Click to expand...
Click to collapse
Awesome! Love a happy ending.
Mine was like that all day. I am unlocked and rooted but stock ROM. Damn thing was on an x all day. I was finally able to get to TWRP and flashed my latest backup. No ideas what happened or why.
Sent from my Nexus 7 using xda app-developers app
AnarchoXen said:
Mine was like that all day. I am unlocked and rooted but stock ROM. Damn thing was on an x all day. I was finally able to get to TWRP and flashed my latest backup. No ideas what happened or why.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Mine is just stuck on Google...... I got into fastboot and flashes stock image but it still will not get past google. I can not boot it to recovery or anything other than fastboot.
What happens when you do vol down and power to try and get into the bootloader? Nothing at all?
Sent from my Nexus 7 using xda app-developers app
kd5dmg said:
Mine is just stuck on Google...... I got into fastboot and flashes stock image but it still will not get past google. I can not boot it to recovery or anything other than fastboot.
Click to expand...
Click to collapse
Follow hercules advice. Vol Down + Power to get to bootloader. Then you should be able to get to recovery. Let us know.
Sent from my Nexus 7 using Tapatalk 4
kd5dmg said:
Mine is just stuck on Google...... I got into fastboot and flashes stock image but it still will not get past google. I can not boot it to recovery or anything other than fastboot.
Click to expand...
Click to collapse
Stuck at Google means /system is corrupted or erased (fastboot to restore system.img)
Stuck at X means something wrong with userdata/cache (factory restore from recovery)
Won't start at all with USB identifying as QHSUSB_DLOAD means either bootloader corrupted or raw partitions corrupted
I suggest you reflash again.
Hi everyone,fisrt of all happy new year tooo all the mates in this awesome forum.
Well, my problem is kind of weird, ive never faced such a problem with my hox, or any other smartphone.
My phone was running well, then it turned off,it was discharged (my phone always shuts down whet it hits 10% or below,i need to take out the sim card or airplane mode so it dosent shuts down),ive plugged it to charge, icould see it charging,but..after that....my phone JUSTE DIED.
It suddenly started bootlooping, always says battery is tooo low to flash from the bootloader, and it never goes below the htc quietly brilliant logo,but when i try like a loot of time, it goes trought it, loads my rom, but as soon as i can see the home screeen,it turns off.....always....its been 3 days im stuck ..... ive looked alll arond the forum but couldnt find any fix....
I am able to access bootloader,but no recovery, ive tried to flash several different recoveries, but it always shows black screen(turns off) when loading recovery....
I still havent tried to re-lock the bootlader and go trought it all again flashing a stock rom and all (even if im pessimistic about if it is oing to fix it)
cuz i do really have preecious data on my hox, i would like to save the content of the internal storage before re-locking it.
Is it a software issue? batterie issue? but, ive tried discharging my hox while letting it in the bootloader, and...it just didnt shut off randomly, it kept alive for about an hour..... then i plugged my phone to charge ,left it be for the whole night, got the greeen light, and still the same problem.....
also(when i get the phone to load, ive seen the last time that my battery was like 53%, and then it just shut down..
i have also tried cvharging it via fastboot reboot method...same issue....
Please, help me guys, I really, reaaally need your help,i was ssooo satisfied with this phone, i cannot afford myself another one right know, and i dont have any warranty....im confused :crying::crying:
Phone running on Viperx 4.0.6 with original kernel.
Thanks in advance.
Please Im really stuck out here, i would like, at least, be able to access CWM or the storage so i could backup everything end then Re-lock and stock.
Try 'fastboot erase cache' to attempt to fix recovery shutting down.
Sent from my C6903 using xda app-developers app
tomascus said:
Try 'fastboot erase cache' to attempt to fix recovery shutting down.
Sent from my C6903 using xda app-developers app
Click to expand...
Click to collapse
Thanks for answering, i already tried that,but it changed nothing.
Now it's WORST, i was rebooting the phone again and again to gain access to the rom, just pushing the buttons and all, and then it rebooted with no screen... its like the screen is dead, the phone vibrates when you power it, but the screen shows nothing.....
Is the screen dead? So i do need to replace it? now my problem has grown worst...
thekkiller said:
Thanks for answering, i already tried that,but it changed nothing.
Now it's WORST, i was rebooting the phone again and again to gain access to the rom, just pushing the buttons and all, and then it rebooted with no screen... its like the screen is dead, the phone vibrates when you power it, but the screen shows nothing.....
Is the screen dead? So i do need to replace it? now my problem has grown worst...
Click to expand...
Click to collapse
go to bootloader and flash Philz recovery 5.15 mount the sd card and backup the information. when you go in Philz and mount the recovery wait 3-4 min SD card to appear on the computer.
Thant said:
go to bootloader and flash Philz recovery 5.15 mount the sd card and backup the information. when you go in Philz and mount the recovery wait 3-4 min SD card to appear on the computer.
Click to expand...
Click to collapse
Well, as i already mentioned, i do not have any access to the recovery, didnt try to flash phillz but now my phone isnt showing anything, means it vibrates but no screen
thekkiller said:
Well, as i already mentioned, i do not have any access to the recovery, didnt try to flash phillz but now my phone isnt showing anything, means it vibrates but no screen
Click to expand...
Click to collapse
Try to charge the phone, maybe from so many restart you f**ck up the battery and for this you have only short vibrate no power for the screen or use battery extendet pack. Second try to go in bootloader not to start the phonejust the volume down +power button
Thant said:
Try to charge the phone, maybe from so many restart you f**ck up the battery and for this you have only short vibrate no power for the screen or use battery extendet pack. Second try to go in bootloader not to start the phonejust the volume down +power button
Click to expand...
Click to collapse
I tried that too,well, i finished opening the phone to check on the battery state and all, everything seemed to be fine, next step is buying another battery and test another set of screen+digitalizer to check for the origin of the problem.
Insane how from trying to access the recovery it became changing battery and screen.
Thanks for all your tips, im going to check on it and keep you informed about my issue
thekkiller said:
I tried that too,well, i finished opening the phone to check on the battery state and all, everything seemed to be fine, next step is buying another battery and test another set of screen+digitalizer to check for the origin of the problem.
Insane how from trying to access the recovery it became changing battery and screen.
Thanks for all your tips, im going to check on it and keep you informed about my issue
Click to expand...
Click to collapse
Good luck from me:good:
Hello, I am new to these forums. I mostly registered for this one specific problem.
I'm pretty sure the phone isn't hardbricked, but I tried rooting my T-Mobile Galaxy Note 3 (4G LTE version) with Klingo. After that, it said the root was successful and the phone immediately restarted itself. However, it was then stuck in a bootloop and it just kept restarting itself. The phone turns on, and then the "Samsung Galaxy Note 3" logo appears with "RECOVERY....." in blue in the top left corner, and directly under that it says "Set Warranty Bit: recovery" in yellow. Then after about 3-4 seconds it shuts off, then about 2 seconds later it restarts automatically and just keeps looping like that.
T-Mobile said they would replace the phone, and they'll be sending me a new one as soon as the old one reaches the return center. Obviously I didn't tell them what I actually tried to do. In case they're able to find out what I tried to do and end up sending my old one back, I just wanted to ask this question preemptively so I might have an idea of what to do.
I HAVE TRIED BOOTING INTO RECOVERY MODE AND DOWNLOAD MODE. No button combinations cause anything to happen. The only thing that stopped the auto-restarting and looping was taking the battery out. Upon putting the battery back in, it will stay off until I manually turn the phone on again, where it will then continue to auto-restart and loop itself.
I do not have the phone right now because I sent it to a return center after spending a few hours searching online for answers and talking to T-Mobile on the phone. But if any of you have any ideas it would certainly be a great help if the worst case scenario ends up happening. Thanks for any potential solutions!
JasePK said:
Hello, I am new to these forums. I mostly registered for this one specific problem.
I'm pretty sure the phone isn't hardbricked, but I tried rooting my T-Mobile Galaxy Note 3 (4G LTE version) with Klingo. After that, it said the root was successful and the phone immediately restarted itself. However, it was then stuck in a bootloop and it just kept restarting itself. The phone turns on, and then the "Samsung Galaxy Note 3" logo appears with "RECOVERY....." in blue in the top left corner, and directly under that it says "Set Warranty Bit: recovery" in yellow. Then after about 3-4 seconds it shuts off, then about 2 seconds later it restarts automatically and just keeps looping like that.
T-Mobile said they would replace the phone, and they'll be sending me a new one as soon as the old one reaches the return center. Obviously I didn't tell them what I actually tried to do. In case they're able to find out what I tried to do and end up sending my old one back, I just wanted to ask this question preemptively so I might have an idea of what to do.
I HAVE TRIED BOOTING INTO RECOVERY MODE AND DOWNLOAD MODE. No button combinations cause anything to happen. The only thing that stopped the auto-restarting and looping was taking the battery out. Upon putting the battery back in, it will stay off until I manually turn the phone on again, where it will then continue to auto-restart and loop itself.
I do not have the phone right now because I sent it to a return center after spending a few hours searching online for answers and talking to T-Mobile on the phone. But if any of you have any ideas it would certainly be a great help if the worst case scenario ends up happening. Thanks for any potential solutions!
Click to expand...
Click to collapse
I have no idea what the issue is, but it seems you might not have a recovery installed on the phone. Try this:
Hold power + volume to go into bootloader (I know you said you tried various combinations, but make sure you're doing it correctly.).
Go into fastboot
flash a new recovery image from (TWRP or CWM) (how to: https://sites.google.com/site/tomsgt123//adb-fastboot)
reboot and go into recovery, then use adb sideload to flash a new ROM.
Source: http://www.reddit.com/r/htcone/comments/1rkvy0/help_stuck_in_bootloop_without_access_to_recovery/
I have no idea whether this will work, but it's worth a try. Please don't blame me if your phone gets even more messed up than it already is.
Techngro said:
I have no idea what the issue is, but it seems you might not have a recovery installed on the phone. Try this:
Hold power + volume to go into bootloader (I know you said you tried various combinations, but make sure you're doing it correctly.).
Go into fastboot
flash a new recovery image from -snip-
reboot and go into recovery, then use adb sideload to flash a new ROM.
Source: -snip-
I have no idea whether this will work, but it's worth a try. Please don't blame me if your phone gets even more messed up than it already is.
Click to expand...
Click to collapse
Thank you so much. I will definitely try this. I was also getting replies elsewhere that if I can see the logo, I should be able to get into download mode where I could then flash the stock ROM. Honestly, it does seem like I somehow may not have a recovery installed.
If they send me my old phone back I will definitely give this a try. Thanks a bunch! And don't worry, I won't hold you accountable haha.
JasePK said:
Thank you so much. I will definitely try this. I was also getting replies elsewhere that if I can see the logo, I should be able to get into download mode where I could then flash the stock ROM. Honestly, it does seem like I somehow may not have a recovery installed.
If they send me my old phone back I will definitely give this a try. Thanks a bunch! And don't worry, I won't hold you accountable haha.
Click to expand...
Click to collapse
If the advice above didn´t work (nothing happened when pressing the usual VOL down - home - power etc; this did not work for me), this is how I managed:
I tried booting around 25 times with the power button released at different times. Did not work.
Tried to insert battery when pressing the 3 buttons. Did not work.
I let the battery run completely empty. Started charging the phone and pressing the 3 buttons. Did not work.
I charged the phone full (with booting the whole time....needed to put it somewhere quiet). After estimating it was full, I pulled out the battery, preparing to send it to mobiletechvideos.com (they saved me before). After a few hours I wanted to see the error message so I could inform them. When I inserted the battery, I got the regular download mode! Nowthen, would I dare to boot it since I am not really sure what to flash to my phone?
I rebooted, and now the phone is back to normal. OTOH, I will not try to flash CWM/TWRP again, so goodbye custom roms (Omega )
cdresor said:
If the advice above didn´t work (nothing happened when pressing the usual VOL down - home - power etc; this did not work for me), this is how I managed:
I tried booting around 25 times with the power button released at different times. Did not work.
Tried to insert battery when pressing the 3 buttons. Did not work.
I let the battery run completely empty. Started charging the phone and pressing the 3 buttons. Did not work.
I charged the phone full (with booting the whole time....needed to put it somewhere quiet). After estimating it was full, I pulled out the battery, preparing to send it to mobiletechvideos.com (they saved me before). After a few hours I wanted to see the error message so I could inform them. When I inserted the battery, I got the regular download mode! Nowthen, would I dare to boot it since I am not really sure what to flash to my phone?
I rebooted, and now the phone is back to normal. OTOH, I will not try to flash CWM/TWRP again, so goodbye custom roms (Omega )
Click to expand...
Click to collapse
So basically your problem was fixed by keeping the battery out for an extended period of time? Did you get the same problem as I did, with the phone trying to boot into recovery constantly and failing due to having no recovery image?
I never kept the battery out for more than 2-3 minutes, so that's another option for me to try if they send my old phone back and the first guy's suggestion doesn't work.
JasePK said:
So basically your problem was fixed by keeping the battery out for an extended period of time? Did you get the same problem as I did, with the phone trying to boot into recovery constantly and failing due to having no recovery image?
I never kept the battery out for more than 2-3 minutes, so that's another option for me to try if they send my old phone back and the first guy's suggestion doesn't work.
Click to expand...
Click to collapse
Yes, I had the exact problem. I tried to have the battery out for 10 minutes, and also ran out of battery during a nightly discharge. Still I could not get it to work. The only way was to leave the battery out for several hours. Beats me, but it worked.
Having bricked a device completely before, I am confident that your phone will be able to get fixed. This isn´t even semi-bricked
Good luck - let me know what happened!
cdresor said:
Yes, I had the exact problem. I tried to have the battery out for 10 minutes, and also ran out of battery during a nightly discharge. Still I could not get it to work. The only way was to leave the battery out for several hours. Beats me, but it worked.
Having bricked a device completely before, I am confident that your phone will be able to get fixed. This isn´t even semi-bricked
Good luck - let me know what happened!
Click to expand...
Click to collapse
Thanks so much to both of you. I feel relieved now no matter what happens. Will post the results when I've reached the end of this ordeal!
JasePK said:
Thanks so much to both of you. I feel relieved now no matter what happens. Will post the results when I've reached the end of this ordeal!
Click to expand...
Click to collapse
I tried to flash latest cwm again and got the same loop. I could narrow it down to 30 min without battery :laugh:
cdresor said:
I tried to flash latest cwm again and got the same loop. I could narrow it down to 30 min without battery :laugh:
Click to expand...
Click to collapse
When that happens and you go back to normal, are you able to access recovery mode afterwards if you want to? Or does trying to cause the same loop? Is it wise to re-flash the stock firmware just to be safe?
JasePK said:
When that happens and you go back to normal, are you able to access recovery mode afterwards if you want to? Or does trying to cause the same loop? Is it wise to re-flash the stock firmware just to be safe?
Click to expand...
Click to collapse
I never dared to try. But since I always used Windows under Mac (Parallells) or the fact that I used Windows 7 or 8, I tried to flash CWM on a native Windows XP PC today and it worked. So now I have a custom ROM working which I never thought would happen :laugh:
Sorry I did not try to access recovery before so you would know
Cheers,
cdresor said:
I never dared to try. But since I always used Windows under Mac (Parallells) or the fact that I used Windows 7 or 8, I tried to flash CWM on a native Windows XP PC today and it worked. So now I have a custom ROM working which I never thought would happen :laugh:
Sorry I did not try to access recovery before so you would know
Cheers,
Click to expand...
Click to collapse
No that's alright, I just wanted to know if it was something I should avoid. :laugh: I'll use Odin to flash the official firmware back on regardless.
I had this happen to me, what had occurred was that the efs was corrupt. Here's the fix:
http://forum.xda-developers.com/showthread.php?t=2507403
Now to implement this fix, you must first be able to get into download mode. To do so:
1. Pull the battery
2. Wait 10-20 secs
3. Reinsert battery WHILE holding power button and (volume down + home???, whatever the key combination is)
5. Phone will boot directly to download mode, no logo
6. Flash twrp via odin
7. Phone will reboot into bootloop again
8. Repeat steps 1-4 except this time use the key combination for recovery
9. You must now use adb and push the file I linked to earlier
10. Then without rebooting you must flash it
11. Reboot and problem solved
Fixed issue with continuous recovery boot
So, this issue was somewhat perplexing, and while the information shared was hopefully valuable to some, it took me about 2 minutes to
fix this and get back into download mode.
Take the battery out of the device, then plug the device into USB (If you're having same issue I was device will not show charging or turn on when plugged in.) Then with the device plugged in to usb and the battery out, hold down the Download mode combination Vulume +, Home and Power, then simultaneously slide in the batter, the phone will boot into download mode and you can get back to stock.
Hope this helped! If it did, leave a thanks.
twill1987 said:
So, this issue was somewhat perplexing, and while the information shared was hopefully valuable to some, it took me about 2 minutes to
fix this and get back into download mode.
Take the battery out of the device, then plug the device into USB (If you're having same issue I was device will not show charging or turn on when plugged in.) Then with the device plugged in to usb and the battery out, hold down the Download mode combination Vulume +, Home and Power, then simultaneously slide in the batter, the phone will boot into download mode and you can get back to stock.
Hope this helped! If it did, leave a thanks.
Click to expand...
Click to collapse
This is exactly what I posted above lol
LOL Sorry. When I flash the TWRP file it just rebooted the phone back into the Hyper Drive Rom I'm using, did it do the same for you?
Thanks to everyone who has provided information and tried to help me! Thankfully, T-Mobile simply sent me a new phone. However, I'm definitely going to keep this topic bookmarked for future reference. This seems to be a rather uncommon problem, considering I had to make a topic to find a solution since all of my searches didn't give me any results.
Thanks again to everyone!
twill1987 said:
So, this issue was somewhat perplexing, and while the information shared was hopefully valuable to some, it took me about 2 minutes to
fix this and get back into download mode.
Take the battery out of the device, then plug the device into USB (If you're having same issue I was device will not show charging or turn on when plugged in.) Then with the device plugged in to usb and the battery out, hold down the Download mode combination Vulume +, Home and Power, then simultaneously slide in the batter, the phone will boot into download mode and you can get back to stock.
Hope this helped! If it did, leave a thanks.
Click to expand...
Click to collapse
U r My neww Mirical worker I messed up a Mobile Odin Flash At work today trying to get the newish NE6
couldnt get it to boot into download after the screw up but read this this morning nd after trying everything else it worked perfect
thank you thank you
I'm having the same problem with my TMobile Note3 after using Kingo after upgrading via Kies to the latest Firmware. The only difference is my phone immediately starts rebooting as soon as I put the battery back in. It doesn't appear that any keys stop this and the USB isn't recognized by my computer in time before the reboot cycle starts.
Is there anything else to try other than sending the phone back for warranty replacement?
tim
Yeah Kingo has given me nothing but trouble, I'd steer clear of that software. I'm assuming you have no access to recovery mode? I have had that issue before on an S3 and was able to finally get it into download mode, but the battery being inserted immediately boots the phone up. So what you have to do is 1. Take battery out and unplug usb cable. 2. Plug USB cable in and Hold download mode buttons with BATTERY OUT (vol+, home and power) 3. insert battery simultaneously while holding buttons down, phone will boot up.. After holding down for about 10 seconds phone will manually reboot, 4. When screen shuts off (potentially vibrates) release download mode buttons, then IMMEDIATELY press and hold download mode buttons again (must perform this step FAST, the key is to do it right before the screen turns on if you can.) 5. The manual boot you've performed should allow you to trigger download mode. I was eventually able to get this to work (about 3 tries. ) I believe your download mode is still intact, you just have to use this method to access it. Remember that because your phone atuo boots with battery inserted download mode will only be available by manual reboot not battery insert.
Give thanks if I assisted you.. Your phone isn't a hard brick so Jtag service should be unnecessary at this juncture.
---------- Post added at 05:09 AM ---------- Previous post was at 05:01 AM ----------
Awesome!! Glad I could be of such assistance
---------- Post added at 05:13 AM ---------- Previous post was at 05:09 AM ----------
R187J said:
U r My neww Mirical worker I messed up a Mobile Odin Flash At work today trying to get the newish NE6
couldnt get it to boot into download after the screw up but read this this morning nd after trying everything else it worked perfect
thank you thank you
Click to expand...
Click to collapse
Awesome man!! Glad I could be of assistance!!
Give thanks/thumbs up!
I read on many posts and comments that everyone is able to boot in download mode. My Note 3 just stuck on recovery boot and I can't get it to boot in download mode. I tried all of the suggestions about pressing three buttons, removing battery etc.
Does anyone know solution for when you can't get into download mode?
Thanks
Firstly, yes, I am sure that the info that I need is on here somewhere, but I have spent the last hour reading threads and I am not a developer and I cannot tell the difference from a soft brick or a hard brick or a boot loop.
Also almost all of the tutorials to root / unbrick involve enabling USB debugging on the phone first, but I can't boot my phone to do this anyway....
So, I got 2.19 OTA update and installed it normally. Phone is not rooted, totally stock 550ML WW model.
But in the last update I got a few bugs so I wiped the cache from recovery mode by following a tutorial, no problems and the bugs went away. So I decided to do the same this time....
I got to the boot menu OK and selected Recovery Mode, then got the Error / sleeping droid screen, so I tried to hold power / vol up to get into the recovery mode and the phone turned off. It was at about 35% battery and plugged into the charger so I'm pretty sure it wasn't a battery issue.
Now I can't get it to turn on / boot at all. If I hold the power button down it just vibrates once and does nothing else, same for vol up and power.... Is this some kind of brick?
Problem is I am going travelling for a month tomorrow and I can't be without my phone so I have to fix it in less than 24 hrs.
Can anyone help me without using terms like "flash image" or "sideload" unless you explain exactly what they mean?
Thanks in advance. :silly:
Can you press vol down and power and see if it turns on?
Sent from my ASUS_Z008D using Tapatalk
Vol down and power has done something!!
The phone vibrated twice and the led has lit up showing that it is charging!! Also I have the battery graphic on the screen.
Should I just now turn it on normally?
Sorry to sound so dumb but I really don't want to screw this up...
Thanks for answering by the way.
You can try to boot like normal but my guess it would still be stuck with the android logo. Happened to me when I rebooted my phone while wiping cache.
Anyway go to the link and follow his instructions. Let me know if there's any problems. Cheers!
http://forum.xda-developers.com/showthread.php?t=3101556
Sent from my ASUS_Z008D using Tapatalk
i experienced shutting down during wipe cache.bad times then.i resolved with this : forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
remember for bootloader press power+volume up.when it vibrates release power and keep pushing volume up.you should be in booloader.scrolling with volume up volume down you can choose recovery..may will be wrote installing update and then an error message.just press power and immediately after volume up for a bit.you should be in recovery.if you reached recovery do a wipe cache.REMEMBER IT CAN TAKE 15-20 MIN TOO ! check if it power on.
if you still cat access bootloader...for me you have to use warranty.say to asus you just did an ota and then phone bricked.dont use the word brick say just it won't power on.approach is the key in this cases.approach to them like a total noob.call them,don't email them.if you are young,let someone older to talk,a relative or someone like this and give to him a text to follow.is difficult to think a noob thinks to do some difficult moves as root,unlocking bootloader....they think "this is a noob.he never thinked to root or modify phone" .so they can think your seller sold to you a rooted device (updating with root takes to brick,bootloop etc.) and so they will give to you a new phone.if it not power on they cant see if it is rooted or not
good luck bro
Many thanks to all of you that contributed, it seems that I was pretty lucky.
After the "reanimation" as per Aceazzay's suggestion, I left it charging for about an hour or so (just in case it was battery related) then booted it normally and it worked (upon booting the battery was over 90%, so it was certainly not a shutdown due to battery).
I have now been able to do a Cache partition wipe correctly and all is good.
I don't know why it shut down in my first attempt, perhaps clumsy fingers, or something more sinister? I guess I'll never know, but this site has certainly saved me some grief!!
Overandout said:
Many thanks to all of you that contributed, it seems that I was pretty lucky.
After the "reanimation" as per Aceazzay's suggestion, I left it charging for about an hour or so (just in case it was battery related) then booted it normally and it worked (upon booting the battery was over 90%, so it was certainly not a shutdown due to battery).
I have now been able to do a Cache partition wipe correctly and all is good.
I don't know why it shut down in my first attempt, perhaps clumsy fingers, or something more sinister? I guess I'll never know, but this site has certainly saved me some grief!!
Click to expand...
Click to collapse
happy for you :good:
Okay so for some context:
My phone had water spill on it, it then immediately started vibrating uncontrollably. I turned it off, it kept vibrating. I had no choice but to let it die of battery exhaustion.
I let it dry in a bag of rice for a week and now I trying to turn it on. It got stuck in a bootloop, booted up the main screen once, rebooted again. Kept vibrating uncontrollably which led to quicker battery exhaustion.
Eventually after like 30 reboots, it said, "this phone ass flashed with an unauthorized image and has been locked" and it told me to contact the manufacturer.
See, from the beginning, I don't give a damn about the phone itself, I just want to get the data off.
How do I achieve this? It's very important.
Thank you, any help is appreciated.
Power it up holding the volume up and power button down. Will boot into boot loader. Select hboot, then recovery. Wipe everything using your recovery. Is that what you are trying to do?
eskimosound said:
Power it up holding the volume up and power button down. Will boot into boot loader. Select hboot, then recovery. Wipe everything using your recovery. Is that what you are trying to do?
Click to expand...
Click to collapse
I want to get all data off correct. It's rooted and I have TWRP on here.
Also since that security message, my phone hasn't booted back up. It's a black screen.
Sent from my SM-A800F using XDA-Developers mobile app
mmmm, just try charging it and doing what I said but it does sound like you've fried it.
There was a program I used a few years back on my One X+ that switched the phone on and off for hours and that recharged the battery but I don't think the M8 works like that....may be worth a Google, recharging dead One battery.
eskimosound said:
mmmm, just try charging it and doing what I said but it does sound like you've fried it.
There was a program I used a few years back on my One X+ that switched the phone on and off for hours and that recharged the battery but I don't think the M8 works like that....may be worth a Google, recharging dead One battery.
Click to expand...
Click to collapse
Okay, here's an update.
The phone turns on but the screen will not work, I cannot unlock my devices but I can get INTO recovery and I can get into ADB Recovery. What can I do in this situation that will allow me to pull my files?
All I want to do is to pull my pictures off, that's it!
Thanks!
technocrat7 said:
Okay, here's an update.
The phone turns on but the screen will not work, I cannot unlock my devices but I can get INTO recovery and I can get into ADB Recovery. What can I do in this situation that will allow me to pull my files?
All I want to do is to pull my pictures off, that's it!
Thanks!
Click to expand...
Click to collapse
If you can get into recovery with adb access, just enter the following from a Windows CMD prompt...
For the entire contents of Internal Storage:
adb pull /data/media/0 C:\Users\(your username)\Desktop (or any location)
If you only want to recover your pictures:
adb pull /data/media/0/DCIM C:\Users\(your username)\Desktop (or any location)
Sent from my m8whl using Tapatalk