Related
Ok, this is my first post so be gentle. I tried to root my sons phone and now it's useless. I went thru HTC's website to unlock bootloader due to having HBOOT 1.5. I'm unlocked and thinking life is good but, I loaded several different ROM's and get the same result. It starts to load the ROM and reboots, sometimes it goes into a safemode with the Viper Rom. I've been jacking with this for 2 days and need some help. I can't find a good link for the RUU or PG86...bla bla bla, I would take it back to stock and surrender but, can't even do that. I've installed TWRP and CWM, just to try different stuff, but get all the same reults.
I think you need to flash the boot.img separately. I'm not sure though. There's a thread for flashing with 1.50 somewhere in the development section
We're comin from a pure power source.
I am having the same issue here, I installed several ROMS, it works for a day, but then the reboot attack starts. Constant lockups and random restarts, sometimes 3 reboots in a row.
ROMs I tried to flash:
1. Xperia XE
2. Titan Trinity 3 HD
3. Nocturnal Adrenaline 1.0.2
Maybe it's the kernel, is there a list of kernels that I can flash?
This worked for me
My phone kept rebooting after root before, but I managed to fix it. This will only work if you can get into fastboot. Download the ruu file located here and run it while in fastboot. This will unroot your phone if you have S-On. After that is done, if it still loops, take out the battery and count to five, then put the battery in and hold the power button on the phone until the phone starts to turn on normally. That fixed my problem, hope it fixes yours. You may have to update after you get your phone started and you will lose all your data. Sorry about the link, I updated to one that has a working download.
armydude13090 said:
My phone kept rebooting after root before, but I managed to fix it. This will only work if you can get into fastboot. Download the ruu file located here and run it while in fastboot. This will unroot your phone if you have S-On. After that is done, if it still loops, take out the battery and count to five, then put the battery in and hold the power button on the phone until the phone starts to turn on normally. That fixed my problem, hope it fixes yours. You may have to update after you get your phone started and you will lose all your data. Sorry about the link, I updated to one that has a working download.
Click to expand...
Click to collapse
Unroot my phone?
Is it possible to re-root it?
Thanks all for the posts. I will give some of this a shot and see what happens. I can get to fastboot, and have loaded a couple of things thru the cmd prompt to try and help, but nothing so far. I'm not really sure if the kernel thing is what's stopping the roms for loading. I can't get the S-OFF, I'm unlocked. I can send anything I want thru the cmd prompt, and also flash zips thru twrp or cwm. Would like to start over but ca't even find a way to do that. Thanks again for the posts.
Cardmastr, we're on the same boat, pg86 takes forever to download, so as I'm waiting patiently, keep me in on the loop with what you're doing.
RUU didn't cut it, kept failing. have not found an image file to flash thru the cmd prompt. Still no luck. What can I throw into fast boot that might help me?????!!!!!!
When I started flashing after using HTC Unlock, I ran "fastboot boot recovery.img" - which booted TWRP with the necessary permissions. Then I wiped everything and flashed the ROM. Haven't had any issues with the ROMs I've tried.
Which recovery did you install? Twrp 1.1.1 is your best bet.
The 2.x version twrp or cwm do not okay nice with some phones.
S3nt from my 3D wond3rland
I used the TWRP 1.1.1. Might of messed up with some of the cmd prompt stuff I'm going back thru.
thefsfempire said:
When I started flashing after using HTC Unlock, I ran "fastboot boot recovery.img" - which booted TWRP with the necessary permissions. Then I wiped everything and flashed the ROM. Haven't had any issues with the ROMs I've tried.
Click to expand...
Click to collapse
Everyday is Halloween for u dude!! UR a Monster! This little tidbit hooked me up. Thanks to you we are back in game.
When installing a ROM, doesn't it wipe /data, /system, etc for us?
Excuse me if I missed an existing thread with this issue, I have looked and didn't find one with exact problem.
It seems everyone else has one of the two problems, not both.
As the title claims, when I turn on my phone it freezes on the white background-green htc screen and won't load the OS.
I tried removing the batter then turning back on with power-volume down but nothing happens. That hboot menu doesn't show up.
As soon as I let go of the buttons, it attempts to start up normally then freezes again at the same screen.
Last night I rooted my phone (first time I've ever rooted) and installed SolidRom Suite ICS Sense 3.6 and it worked perfectly.
I then removed battery, went into hboot menu, cleared the catches and did a factory reset. I then attempted to install the SolidRom Suite JB 4.1.1
This is when it loaded the white screen-green htc and froze. I thought it was loading the rom slowly (First time like I said, I didn't know what to expect)
It was 2am so I just fell asleep. I woke up to a dead phone. I plugged it in to a charger and have been attempting to get access to the phone all morning with no luck.
CDMA (Sprint)
s-on
hboot 1.58
2.87
4ext
Any other information you need? Any and all help would be appreciated. Thanks in advance.
I just hope I didn't kill my phone
While rooting last night, I was using a youtube video as a cross reference to the directions I was using from AFs.
I asked the creator of the video the same thing and this is what he replied with
DON ,T BE SCARED (are u?)
this thing is called BOOTLOOP
the rom has problems OR U DID NOT FLASH THE KERNAL!!!!
to flash the kernal u need a working software and install an program called flash image gui
restore your nandroid back u created before flashing
DID U MADE A NANDROID BACK UP
If no
then u need to download the ruu image of your phone GOOGLE TIME keep searching until u got one
Click to expand...
Click to collapse
1-I didn't know I needed to flash the kernel if I was going to stick with the one provided with the custom ROM (is that a gross conceptual error?)
2-If I do need to flash the kernel first... I have no idea how.
3-I looked up flash image gui and all the instructions assume your phone is working fine so I'm not sure what I'm suppose to do with that.
I was so excited when the first rom (ICS) worked... guess that's what I get for then trying to upgrade to JB.
Thanks a lot guys. That noob video I watched to register on this site is so spot on.
update: I finally figured out how to fastboot. I keep trying clear caches then factory reset. I install new rom and then it bootloops again. What am I doing wrong?
I recommend you follow ramjet's guide here: http://forum.xda-developers.com/showthread.php?t=1889438
It will reset your phone back to stock (hopefully stopping the bootloops) and then get you s-off using the wire trick. This will allow you to flash ROMs without worrying about flashing kernels. It will also allow you to change hboots, which I think was what caused the issue in the first place. I think all the jb ROMs don't boot on hboot 1.58.
I was able to return the phone to factory settings. I then retried and now I get past the splash screen and am frozen at the next Sprint screen.
I'm still at it. I'll get it eventually.
ackNalej said:
Excuse me if I missed an existing thread with this issue, I have looked and didn't find one with exact problem.
It seems everyone else has one of the two problems, not both.
As the title claims, when I turn on my phone it freezes on the white background-green htc screen and won't load the OS.
I tried removing the batter then turning back on with power-volume down but nothing happens. That hboot menu doesn't show up.
As soon as I let go of the buttons, it attempts to start up normally then freezes again at the same screen.
Last night I rooted my phone (first time I've ever rooted) and installed SolidRom Suite ICS Sense 3.6 and it worked perfectly.
I then removed battery, went into hboot menu, cleared the catches and did a factory reset. I then attempted to install the SolidRom Suite JB 4.1.1
This is when it loaded the white screen-green htc and froze. I thought it was loading the rom slowly (First time like I said, I didn't know what to expect)
It was 2am so I just fell asleep. I woke up to a dead phone. I plugged it in to a charger and have been attempting to get access to the phone all morning with no luck.
CDMA (Sprint)
s-on
hboot 1.58
2.87
4ext
Any other information you need? Any and all help would be appreciated. Thanks in advance.
I just hope I didn't kill my phone
Click to expand...
Click to collapse
You can't run JB on 1.58
http://forum.xda-developers.com/showthread.php?t=1808332
You need to flash 1.58, the new firmware to flash my Rom.
Click to expand...
Click to collapse
I'm amusing he's talking about hboot there. Am I wrong?
I'm about to try that wire trick. Regardless of everything else, it seems to make life easier down the road.
Please lock
Hi,
I'm a bit new here and running a good old-fashioned stock Inc 4G LTE, never rooted or flashed to new ROM. It DOES have the latest OTA update from Verizon a couple months ago.
This morning my phone suddenly went off after working OK. Then when trying to restart, I get an infinite boot loop and it won't get past the red Droid screen. I've searched various threads and tried what I think are the most obvious things, and nothing seems to help. But I want to make sure there are no other options before I throw it in the trash.
Here's what I tried:
- Tried entering Safe Mode by holding down volume key after HTC screen comes on. Makes no difference, does not enter Safe Mode.
- Get to HBOOT OK. Says 'LOCKED' and I am running HBOOT v.1.15.0000.
- - In HBOOT, I've tried running Recovery a couple times. Seems to go OK, but just starts looping when restarting.
- - In HBOOT, tried running Recovery > Wipe Cache Partition. Says cache is cleared.
- - In HBOOT, tried running Recovery > Wipe data/factory reset. Seem to go through OK.
- - In HBOOT, tried running Factory Reset.
- - In HBOOT, tried running Clear Storage.
- Pulled battery and tried spare.
- Removed SD card.
Some history - this phone has always been very sluggish. A few months ago started shutting down when doing camera intensive things (would jump to battery at critical level). So I did a factory reset a couple weeks ago and was slowly adding some of the essential apps back in. It crashed trying to upload photos to Facebook. Last night I had just moved some apps to the Phone storage and set my Sound Profile app to change profiles in the morning. This is about the time the phone crashed.
Anything else I should try before giving up?
Can I try to root and install a custom ROM to fix when in this state? Is this now possible with latest OTA update?
If custom ROM is last chance, is there a really solid one running 4.3 and Sense?
THANKS! May be time to get a HTC One or iPhoney, as I'm just not into huge phones that are coming out...
iRunNaked said:
If your on bootloader 1.15.0000 and now 1.16.0000, try using the stock Ruu and restoring the phone. If not, try rebooting in bootloader and factory reset.
If that doesn't work, gain root (if you haven't) and get s-off/unlock bootloader/CID set to 111111, and try a custom rom. If all else fails, take it back to stock and unroot/s-on/CID back to VZW/Relocked.
Call Verizon and tell them you need a replacement. The phone randomly gets real hot and reboots. They should send you a new one no problem.
I girlfriend had the random reboots, ending up getting it replaced. Now shes on her 4th or 5th incredible lte. (data Issues & random reboots)
Click to expand...
Click to collapse
I tried running a stock 2.17.. RUU, but got a "Failed" message because the software was too old. I'm guessing that is because I'm on the newer 2.19.. OTA update?!? Anyone know where to get a RUU file for the latest 2.19 version? I've been searching with no luck.
I'll have to research how to root/unlock the phone when it won't boot. Any specific threads that have fairly detailed instructions would be appreciated.
Thanks!
jethrodesign said:
I tried running a stock 2.17.. RUU, but got a "Failed" message because the software was too old. I'm guessing that is because I'm on the newer 2.19.. OTA update?!? Anyone know where to get a RUU file for the latest 2.19 version? I've been searching with no luck.
I'll have to research how to root/unlock the phone when it won't boot. Any specific threads that have fairly detailed instructions would be appreciated.
Thanks!
Click to expand...
Click to collapse
I looked at the thread about how to successfully root & flash the phone when it has the Verizon OTA update (2.19.xx) found here: http://forum.xda-developers.com/showthread.php?t=2664460.
But it appears at first glance that to do it the phone needs to be booted up and connected to the computer via USB. I can only get my phone to the HBOOT screen, nothing else.
- Can anyone confirm that to unlock and/or flash a new ROM on this phone that it has to be able to boot up? No way to do it on my phone with the 2.19 software and constant rebooting?
Thanks. It's cosmetically perfect, so I feel bad about throwing it away. If I can get it back up somehow I could at least sell it or give it to someone in need.
jethrodesign said:
I looked at the thread about how to successfully root & flash the phone when it has the Verizon OTA update (2.19.xx) found here: http://forum.xda-developers.com/showthread.php?t=2664460.
But it appears at first glance that to do it the phone needs to be booted up and connected to the computer via USB. I can only get my phone to the HBOOT screen, nothing else.
- Can anyone confirm that to unlock and/or flash a new ROM on this phone that it has to be able to boot up? No way to do it on my phone with the 2.19 software and constant rebooting?
Thanks. It's cosmetically perfect, so I feel bad about throwing it away. If I can get it back up somehow I could at least sell it or give it to someone in need.
Click to expand...
Click to collapse
If you want to use mdmower's "temp-root" trick, then you'll need to be able to access the device through Android Debug Bridge. Can you see the device if you type
Code:
adb devices
after booting up past the bootloader?
stringedonbass said:
If you want to use mdmower's "temp-root" trick, then you'll need to be able to access the device through Android Debug Bridge. Can you see the device if you type
Code:
adb devices
after booting up past the bootloader?
Click to expand...
Click to collapse
Hi. I've never tried running ADB. Not very familiar with it at all. But my phone will not boot past the HBOOT option. No matter what I've tried, it will just go into a rebooting loop. I'm assuming it needs to be fully booted up to work with ADB?!?
- Is there an RUU for the latest software update (2.19.xx) somewhere that I can try running to see if it will help it fully boot?
- Any other options?
Thanks!
jethrodesign said:
Hi. I've never tried running ADB. Not very familiar with it at all. But my phone will not boot past the HBOOT option. No matter what I've tried, it will just go into a rebooting loop. I'm assuming it needs to be fully booted up to work with ADB?!?
- Is there an RUU for the latest software update (2.19.xx) somewhere that I can try running to see if it will help it fully boot?
- Any other options?
Thanks!
Click to expand...
Click to collapse
Yes, my understanding is that to use adb, you need to be able to boot into the OS with usb debugging turned on. Hopefully someone will come along with a worthwhile response!
Is anyone aware of more current RUU's than are menteioned here?
http://forum.xda-developers.com/showthread.php?t=1770978
---------- Post added at 05:19 PM ---------- Previous post was at 05:07 PM ----------
If the phone failed as a completely stocked phone, why not try returning as opposed to figuring out how to root a broken phone?
Hello all, and thanks in advance for your help. I don't know if all of this is relevant to what happened, but I'm including it in case there's some small clue.
My phone was an S-OFF running HBOOT 2.09. I have been running Deck's CM builds for a while now with no issues. Last week, I decided to update to the new firmware which included the new partition layout.
HTC's RUU executable did not work, so I used the two zip method in this post. I first renamed rom_01 to PJ75IMG.zip, placed it on the SD card, rebooted and installed, then did the same with rom_02. Loaded everything up, seemed great with the stock image. After verifying everything was working fine, I flashed a new recovery (2.7.0.0b, via PJ75IMG.zip as well), and installed the latest OmniROM (3/31) via recovery. I had some issues with the PA 0-Day GAPPs that were recommended (force close errors with Google Keyboard) so after reflashing Omni switched back to the 12/09 GAPPs in Deck's thread. Everything seemed great.
A few days later, after having the phone in my pocket, my screen turned into a rainbow of pixels. Here is what it looks like: http://imgur.com/9ef6F8z It still seemed to work, just the screen was always that rainbow.
Thinking it was an issue with the firmware, I tried to RUU back to a somewhat earlier stock by using ViperRUU 3.16.651.3. However, after going through the RUU process, it had gone about 30-40 minutes with no updates, so I thought it had crashed. I checked to see if that was normal, and saw that it was not and they recommended restarting the process. I restarted both the ViperRUU (couldn't find phone anymore) and the phone, and now I think my phone might be totally bricked.
When I turn it on, there is nothing on the screen. It vibrates once, like it's trying to start, but nothing happens and the phone is otherwise unresponsive. I can try to boot into the bootloader (volume down + power) and that SEEMS to work, but the screen doesn't turn on then either. Occasionally, it will display the same rainbow pixels after "selecting" an option on the bootloader menu (I'm assuming). I've also pulled the SD card to insure it's not trying to read any PJ75IMG.zip.
I can't seem to get it to go into fastboot mode (single power button click after thinking I'm in the bootloader) and adb only shows the device as OFFLINE when I can get it to detect. It's hard to know what's going on without the screen.
Has anyone heard of this before? I probably ****ed something up but other than ending the ViperRUU early, not sure what. Thanks in advance, I very much appreciate it.
matt135353 said:
Hello all, and thanks in advance for your help. I don't know if all of this is relevant to what happened, but I'm including it in case there's some small clue.
My phone was an S-OFF running HBOOT 2.09. I have been running Deck's CM builds for a while now with no issues. Last week, I decided to update to the new firmware which included the new partition layout.
HTC's RUU executable did not work, so I used the two zip method in this post. I first renamed rom_01 to PJ75IMG.zip, placed it on the SD card, rebooted and installed, then did the same with rom_02. Loaded everything up, seemed great with the stock image. After verifying everything was working fine, I flashed a new recovery (2.7.0.0b, via PJ75IMG.zip as well), and installed the latest OmniROM (3/31) via recovery. I had some issues with the PA 0-Day GAPPs that were recommended (force close errors with Google Keyboard) so after reflashing Omni switched back to the 12/09 GAPPs in Deck's thread. Everything seemed great.
A few days later, after having the phone in my pocket, my screen turned into a rainbow of pixels. Here is what it looks like: http://imgur.com/9ef6F8z It still seemed to work, just the screen was always that rainbow.
Thinking it was an issue with the firmware, I tried to RUU back to a somewhat earlier stock by using ViperRUU 3.16.651.3. However, after going through the RUU process, it had gone about 30-40 minutes with no updates, so I thought it had crashed. I checked to see if that was normal, and saw that it was not and they recommended restarting the process. I restarted both the ViperRUU (couldn't find phone anymore) and the phone, and now I think my phone might be totally bricked.
When I turn it on, there is nothing on the screen. It vibrates once, like it's trying to start, but nothing happens and the phone is otherwise unresponsive. I can try to boot into the bootloader (volume down + power) and that SEEMS to work, but the screen doesn't turn on then either. Occasionally, it will display the same rainbow pixels after "selecting" an option on the bootloader menu (I'm assuming). I've also pulled the SD card to insure it's not trying to read any PJ75IMG.zip.
I can't seem to get it to go into fastboot mode (single power button click after thinking I'm in the bootloader) and adb only shows the device as OFFLINE when I can get it to detect. It's hard to know what's going on without the screen.
Has anyone heard of this before? I probably ****ed something up but other than ending the ViperRUU early, not sure what. Thanks in advance, I very much appreciate it.
Click to expand...
Click to collapse
This is a known hardware issue. Look here:
http://forum.xda-developers.com/showthread.php?t=2470296
It happened to me as well. I called Sprint and they replaced my phone for no charge.
Sent from my EVO using XDA Premium 4 mobile app
Ah, thanks for the link. I don't have TEP and it's out of warranty but I'll give Sprint repair a shot. Thanks!
Evolution_Freak said:
This is a known hardware issue. Look here:
http://forum.xda-developers.com/showthread.php?t=2470296
It happened to me as well. I called Sprint and they replaced my phone for no charge.
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hmm...I bought mine secondhand and am going to be running it on Ting, you think they would do that for me if it happens? :laugh:
matt135353 said:
Ah, thanks for the link. I don't have TEP and it's out of warranty but I'll give Sprint repair a shot. Thanks!
Click to expand...
Click to collapse
I have TEP but that never even came up. I never filed a claim. They originally wanted me to go to a Sprint store to have a tech look at it but I complained that the nearest store is an hour away. So they took my word, after explaining what was happening, and sent me a new (refurbished) EVO and then I sent them the old one in the package they provided with the new one. This was back in November of 2013 and I never heard anything else about it.
Sent from my Nexus 5 using XDA Premium 4 mobile app
A few weird things are happening on my phone and I'm quite concerned (even though it's actually working perfectly fine, which is the weirdest part of all!)
A little background: I recently wiped my phone and flashed the Sense 5 Android 4.3, stock rom. Now I'm trying to flash Viper 4.0.
First of all, as the title suggests, whenever I put a zip file on my phone it doesn't show in the TWRP recovery. I downloaded the correct one on the site (the newest one for the HTC EVO 4G LTE) so I don't think that's the problem. Also, I tried to push the file Viper zip onto my phone using this program called WinDroid Toolkit, and it claims it did but when I go into TWRP I cannot see the zip file at all, and if I try to use other folder names (such as the 'boot' folder I saw when I was in TWRP recovery) it says those folders don't exist!
Second of all, TWRP claims there is no OS installed on my phone but when I reboot my phone, it's fine! It just goes to the home screen as usual and it works perfectly fine... so I don't understand this warning but I couldn't shake the feeling that this was relevant to my issue.
I've been combing the forums looking for this type of problem, and I've tried multiple things but to no avail. I've read snippets about partition problems after formatting some phones but I'm not sure because there doesn't seem to be much information about it (at least from what I could find).
Altom85 said:
A few weird things are happening on my phone and I'm quite concerned (even though it's actually working perfectly fine, which is the weirdest part of all!)
A little background: I recently wiped my phone and flashed the Sense 5 Android 4.3, stock rom. Now I'm trying to flash Viper 4.0.
First of all, as the title suggests, whenever I put a zip file on my phone it doesn't show in the TWRP recovery. I downloaded the correct one on the site (the newest one for the HTC EVO 4G LTE) so I don't think that's the problem. Also, I tried to push the file Viper zip onto my phone using this program called WinDroid Toolkit, and it claims it did but when I go into TWRP I cannot see the zip file at all, and if I try to use other folder names (such as the 'boot' folder I saw when I was in TWRP recovery) it says those folders don't exist!
Second of all, TWRP claims there is no OS installed on my phone but when I reboot my phone, it's fine! It just goes to the home screen as usual and it works perfectly fine... so I don't understand this warning but I couldn't shake the feeling that this was relevant to my issue.
I've been combing the forums looking for this type of problem, and I've tried multiple things but to no avail. I've read snippets about partition problems after formatting some phones but I'm not sure because there doesn't seem to be much information about it (at least from what I could find).
Click to expand...
Click to collapse
Try using the TWRP found here:
http://forum.xda-developers.com/showthread.php?t=2639180
Sent from my Nexus 5 using XDA Premium 4 mobile app
download this twrp http://d-h.st/7Cr
name it properly and fastboot flash it. after that mount your device to you pc and transfer a rom zip to storage.
Okay, well I flashed that TWRP and now I'm stuck at the white HTC screen. I can't even get into the bootloader, it just continually boots to the white HTC screen. Thoughts?
Altom85 said:
Okay, well I flashed that TWRP and now I'm stuck at the white HTC screen. I can't even get into the bootloader, it just continually boots to the white HTC screen. Thoughts?
Click to expand...
Click to collapse
RUU or ViperRUU. TBH it sounds like the behavior of a dirty flash. ViperRUU is especially helpful in these situations.
Once done, use the TWRP recommended by Evolution_Freak. There were some major changes to the partitioning in the last few releases, make sure your recovery is appropriate for your ROM.
FesterCluck said:
RUU or ViperRUU. TBH it sounds like the behavior of a dirty flash. ViperRUU is especially helpful in these situations.
Once done, use the TWRP recommended by Evolution_Freak. There were some major changes to the partitioning in the last few releases, make sure your recovery is appropriate for your ROM.
Click to expand...
Click to collapse
Ok it's not stuck anymore, I can get into recovery and bootloader, so I'm not in a panic anymore at least However, my computer is not detecting my phone, nor is VipeRUU. If I try to mount to the computer via TWRP, nothing comes up. BTW my recovery is 2.7.8.0b now. Still no OS, still gets stuck on the HTC screen until I boot to recovery or bootloader
Edit: Now the computer tries to install drivers for my phone whenever I plug it in. It pops up as HTC MTP Device, always fails to install, then has a warning in the device manager. So I uninstalled the drivers, uninstalled HTC Sync, reinstalled HTC Sync. Didn't help. This is beyond frustrating...
Edit 2: After scouring the internet someone said to lock the bootloader and that'll allow my PC to see my phone. Well, now i have a RELOCKED (that's what it says on top) bootloader and I'm no closer to the solution methinks. I'm ready to just throw this phone out the window.
Edit 3: I actually discovered ViperRUU has a way to bypass the initial screen so I can use it in bootloader. Great, except now it's stuck on "Flashing..." and has been for half an hour. I really might throw this phone out the window.
5th and final edit: VipeRUU just would not work at all, so I had to go back to an older stock RUU, which sucks but at least my phone is working now Thanks for your help guys!