Anyone experience a phone getting really hot after reboot 110 degrees shut itself off and now i cant get it back on. I tried booting into bootloader with power volume button but no go. I'm rooted running stock. when i connect to computer it shows as a usb device but if I try to open it it says please insert disk into removable disk. any fix or do I need to get a new one
FIXED
AFTER a couple of days battery went completely dead was able to charge and boot into boot loader now every Rom tried to install would load up after a a complete wipe but would only last about an hour before phone would freeze up. finally RUU with 651.18 and all seems to be working eight hours later.
Related
So after an unsuccessful ROM flash my phone was stuck at bootloader for quite sometime...i had a micro SD card reader and inserted it into multiple computers running XP, vista and ubuntu...they all registered that i had plugged something in but wouldn't show it as a disk drive...now i've already figured out how to access it but i put a new ROM image on it and tried to reflash but after the flash when my phone booted up it simply switched itself off... when i switched it back on it went back to the bootloader and tried to reflash the ROM. mid flash it just switches itself off... I realize that this is probably due to the charge level of the phone so i plugged it it but it will be off and charging then it will suddenly decide its got enough battery power and boot up to the bootloader screen until it dies again...how do i stop this vicious loop
tlglegacy said:
So after an unsuccessful ROM flash my phone was stuck at bootloader for quite sometime...i had a micro SD card reader and inserted it into multiple computers running XP, vista and ubuntu...they all registered that i had plugged something in but wouldn't show it as a disk drive...now i've already figured out how to access it but i put a new ROM image on it and tried to reflash but after the flash when my phone booted up it simply switched itself off... when i switched it back on it went back to the bootloader and tried to reflash the ROM. mid flash it just switches itself off... I realize that this is probably due to the charge level of the phone so i plugged it it but it will be off and charging then it will suddenly decide its got enough battery power and boot up to the bootloader screen until it dies again...how do i stop this vicious loop
Click to expand...
Click to collapse
can you put your phone into bootloader mode (power and vol down together whilst powering on)? be a good idea to remove your sd card first.
cr1960 said:
can you put your phone into bootloader mode (power and vol down together whilst powering on)? be a good idea to remove your sd card first.
Click to expand...
Click to collapse
I can't really manually put it into bootloader mode, but when the phone thinks its charged enough it will start up itself and go into bootloader mode
Does your phone say "RUUNBH" in the top right corner? Have you yanked out your battery then put it back in before charging? Those are the two things I would try. And BTW, in the future you shouldn't create two threads in different parts of the forum.
DaveTheTytnIIGuy said:
Does your phone say "RUUNBH" in the top right corner? Have you yanked out your battery then put it back in before charging? Those are the two things I would try. And BTW, in the future you shouldn't create two threads in different parts of the forum.
Click to expand...
Click to collapse
yea im sorry its just my phones been down for days and its really bugging me and i just want to get this fixed and my phone does say RUUNBH in the top right corner and i have yanked out the battery waited a few seconds for good measure and put it back in before charging...it still just loops into bootloader before dieing and charging again
Phone started up again this is what it says in bootloader
RHOD300 32 M SS-BC RUUNBH in top right
SPL-0.85.Olinex
MicroP(LED) 0x0A
MircroP(KEY) 0x04
TURBO HW/TURBO SW
TP MFG DATA
then it has some numbers and code error under it with try again
then it says 218,842 calibrated
Okay, the problem is that the RUU flag is set, and the device won't do anything until that is cleared. What you need to do is establish a connection via MTTY. Follow the instructions here about how to connect to your device via MTTY. Once you get an MTTY connection established with your device (it may take awhile, MTTY is quirky like that), simply type
Code:
set 16 0
You may need to manually soft reset the device. Then, I highly recommend flashing to a stock ROM using the microSD card method, before flashing another cooked ROM.
DaveTheTytnIIGuy said:
Okay, the problem is that the RUU flag is set, and the device won't do anything until that is cleared. What you need to do is establish a connection via MTTY. Follow the instructions here about how to connect to your device via MTTY. Once you get an MTTY connection established with your device (it may take awhile, MTTY is quirky like that), simply type
Code:
set 16 0
You may need to manually soft reset the device. Then, I highly recommend flashing to a stock ROM using the microSD card method, before flashing another cooked ROM.
Click to expand...
Click to collapse
hey thanks Dave i plugged in the usb then i waited until my phone was charged enough to switch on and go to bootloader then i opened MTTY the USB port showed up i selected it and it connected no problem i typed in set 16 0 then the device reset and showed the touch pro 2 boot screen then my phone died and started charging...i left it charging overnight and this morning it booted up and started loading the ROM...after it was finished i hard reset it just to be sure and now it's working perfectly thanks very much i appreciate the help
Duplicate thread??
Dude!! you already opened this same thread here, and HERE. Why another??
Closing thread.
Don't do this again.
I have 1.0.1 and used the correct autonooter and successfully rooted it. Although, after turning on and off the phone, I run into big problems. One time it got stuck in the boot screen and I had to do the 8x reflash thing. Now I'm getting the error "Battery too low to power ON. Please wait 15 minuets and try again" after charging for many hours! *EDIT* Now the reset method ("n" button, power, and +) isn't working. What am I doing wrong? I'm confused about what I'm supposed to do with the sd card. After rooting, do I leave it in for ever or do I take it out? I didn't even get adb working correctly.
Any help? Thanks
Hi,
Today I found a problem with my phone. Firstly it hang and then after reset after a start screen it enters the data transfer/recovery mode witch looks like that
telephone -> usb cable -> laptop.
I cannot enter boot loader and also hard reset is not working.
Does anyone has any idea how to fix it?
Additional information:
week ago I have installed Deepshinging mango 7.5 with HSPL.
After connecting with zune it enters recovery mode, and if I try to proceed the arrow on the phone screen above changes direction to the opposite and it is crossed. After that there is an automatic reset of phone (it enters the same data transfer/recovery mode) and zune writes error 801812E0.
Try removing the USB cord and battery, then waiting a while (like 30 seconds). Put the batty back in, cross your fingers, and power on the phone.
My phone (retail ROM, OSPL) got stuck on that screen after I used the backup-at-any-time tool. Normal reboots just kept going back to that screen. The steps above fixed it. Hope that helps!
Nope, I have tried to:
- remove battery
- completely discharge battery
and still the same.
Hello,
If your phone is in mango you have to downgrade to nodo using the gold card.
Cheers.
A day ago the battery got kinda low and I put it on charge. It started rebooting on its own while charging, I put it down to being low on battery and went along with my day. A few hours later I took it off charge and i was still rebooting itself after around 30 seconds being in the OS.
I thought it may be the ROM and did a wipe, after a wipe everything worked for 12 hours, it was even used outside and got real warm with no problems. Then I started uninstalling the apps that my old HTC Backup put back on and it did the same thing.
I did another wipe and just installed swiftkey (was NOT installed before) and then it started doing the exact same thing. I decided to try a different ROM in-case that would solve the problem, once I flashed a new ROM i restarted and it just took me into the bootloader and no further.
Recovery doesn't work, it just reboots. I tried plugging it in but all I get is it working for 10 seconds and then "USB Device not recognized". During the 10 seconds I still cant send ADB/Fastboot commands to it. I tried different PC's with and without USB 3.0 and 3 different cables. Before this ADB worked fine
All the drivers are correct, and I tried using HTC Sync drivers. (Even with the drivers uninstalled I get the error about it not being recognized)
Does anyone have any ideas? Or should I just sell it and move on?
Here is the screen with all the info on - https://dl.dropboxusercontent.com/u/6017469/P1010831.JPG
SeanBond said:
A day ago the battery got kinda low and I put it on charge. It started rebooting on its own while charging, I put it down to being low on battery and went along with my day. A few hours later I took it off charge and i was still rebooting itself after around 30 seconds being in the OS.
I thought it may be the ROM and did a wipe, after a wipe everything worked for 12 hours, it was even used outside and got real warm with no problems. Then I started uninstalling the apps that my old HTC Backup put back on and it did the same thing.
I did another wipe and just installed swiftkey (was NOT installed before) and then it started doing the exact same thing. I decided to try a different ROM in-case that would solve the problem, once I flashed a new ROM i restarted and it just took me into the bootloader and no further.
Recovery doesn't work, it just reboots. I tried plugging it in but all I get is it working for 10 seconds and then "USB Device not recognized". During the 10 seconds I still cant send ADB/Fastboot commands to it. I tried different PC's with and without USB 3.0 and 3 different cables. Before this ADB worked fine
All the drivers are correct, and I tried using HTC Sync drivers. (Even with the drivers uninstalled I get the error about it not being recognized)
Does anyone have any ideas? Or should I just sell it and move on?
Here is the screen with all the info on - https://dl.dropboxusercontent.com/u/6017469/P1010831.JPG
Click to expand...
Click to collapse
Damn, sorry. Pretty sure you're out of luck if you can't connect to PC and you can't get into recovery. I'd give it straight into support now and give an excuse like update failed, randomly started restarting etc.
What OS Are you running? 8.1? I would suggest using a Linux Live Disc or Windows 7. its much more reliable.
I am pretty sure you need hboot 1.56+ for windows 8 to work correctly in Fastboot
SeanBond said:
A day ago the battery got kinda low and I put it on charge. It started rebooting on its own while charging, I put it down to being low on battery and went along with my day. A few hours later I took it off charge and i was still rebooting itself after around 30 seconds being in the OS.
I thought it may be the ROM and did a wipe, after a wipe everything worked for 12 hours, it was even used outside and got real warm with no problems. Then I started uninstalling the apps that my old HTC Backup put back on and it did the same thing.
I did another wipe and just installed swiftkey (was NOT installed before) and then it started doing the exact same thing. I decided to try a different ROM in-case that would solve the problem, once I flashed a new ROM i restarted and it just took me into the bootloader and no further.
Recovery doesn't work, it just reboots. I tried plugging it in but all I get is it working for 10 seconds and then "USB Device not recognized". During the 10 seconds I still cant send ADB/Fastboot commands to it. I tried different PC's with and without USB 3.0 and 3 different cables. Before this ADB worked fine
All the drivers are correct, and I tried using HTC Sync drivers. (Even with the drivers uninstalled I get the error about it not being recognized)
Does anyone have any ideas? Or should I just sell it and move on?
Here is the screen with all the info on - https://dl.dropboxusercontent.com/u/6017469/P1010831.JPG
Click to expand...
Click to collapse
usually when it boots into the os, then reboots after 30sec or so, the radio is borked. the radio is the last thing to load in the os
if you can get into the bootloader as it shows in your pic, you need to select FASTBOOT. what you see in the pic is youre in HBOOT mode, and that will not connect to a pc that way. ADB will not work in the bootloader in any case, so dont even try that. You should have your recovery.img file ready, get into the bootloader as you show, and select FASTBOOT. then flash your recovery with command-- fastboot flash recovery recovery.img
however, if your radio is hosed, flashing a rom wont help you. You should probably do a RUU. Many RUU's work off fastboot mode, so get into that and start the RUU.exe
Today I left my phone in a cab and got it back in the evening. But after I got my phone it was stuck in a boot loop (after force restart - power button press and hold - it will go to battery icon and automatically restart after a few minutes and again goes to battery icon). Please see the video to understand the boot loop. Unfortunately, Developer options of the phone were not enabled.
Can boot to recovery but can boot to fastboot.
Can you please help me to boot my phone back to normal or sideload a ROM via adb.
tia
Was able to fix the issue. Followed below steps,
1. Kept phone until the battery fully drains
2. Plugged into the charger and charged the phone up to around 65% while the phone is switched off.
3. Switched on the phone when the cable is disconnected.
4. This time the phone was booted to recovery. No battery logo anymore
5. From recovery, rebooted the phone. But again it was booted to recovery.
6. Wiped all data and rebooted.
7. Phone was booted to MIUI os but had to set up the phone again from the beginning.
jayanath said:
Today I left my phone in a cab and got it back in the evening. But after I got my phone it was stuck in a boot loop (after force restart - power button press and hold - it will go to battery icon and automatically restart after a few minutes and again goes to battery icon). Please see the video to understand the boot loop. Unfortunately, Developer options of the phone were not enabled.
Can boot to recovery but can boot to fastboot.
Can you please help me to boot my phone back to normal or sideload a ROM via adb.
tia
Click to expand...
Click to collapse
Same problem bro, did u resolve it???
I think your battery is empty. Leave it on power for a while and check if its charging. Maybe the charginglevel is too low for booting up.
opg2000 said:
I think your battery is empty. Leave it on power for a while and check if its charging. Maybe the charginglevel is too low for booting up.
Click to expand...
Click to collapse
I hope it was that simple ..it seems probably like a bad update. My gfs phone did the similar today
The digitizer stopped working, I force reset the phone and boom ..recovery mode - Trying everything but it doesn't work. Wipe surely would work but she has pictures and videos so I'm trying to avoid that. Plug it to charging but she remembers it had like 75% of battery ...geez (hoping for a miracle)
EDIT: Probably this happen from the bad xiaomi update, anyway I did wipe the data and as expected it work without an issue, I'll unlock this phone and ditch MIUI (I mean I did it to my phone Xiaomi Mi Mix 2S from day 1 - I hate miui) ..now my gf has a reason to hate it too
A factory reset could be painful, since you would lose everything on the device. I saw a guy tap all over the back of the phone with two fingers, and boom! The Redmi Note 10 Pro boot normally! I tried it on a friend's phone, and it worked.
Hello,I had a kind of a similar thing.
I left my phone to charge and when I was back it seems to be stuck in a boot loop(MIUI14)
Well,I tried to force restart but the same.
Before I go to recovery mode,accidently,I putted the phone in fastboot mode.I restarted it in the try to go to recovery mode but the phone started normally.After boot,it's shows an update compete message,so te problem was from an android security path update whatever.
AlexfxDru said:
Hello,I had a kind of a similar thing.
I left my phone to charge and when I was back it seems to be stuck in a boot loop(MIUI14)
Well,I tried to force restart but the same.
Before I go to recovery mode,accidently,I putted the phone in fastboot mode.I restarted it in the try to go to recovery mode but the phone started normally.After boot,it's shows an update compete message,so te problem was from an android security path update whatever.
Click to expand...
Click to collapse
I have important apps on the phone and I wasnt thinking about a factory reset anyway but hopefully it worked in that way