On my amaze I attempted the s-off with the juopunutbear. Something happened and when I turn my phone on the juopunutbear with the phone and going down comes on. Every time I turn it on it happens. I went to bootloader and tried to factory reset it, it didn't work. So every time I cut my phone on that screen comes on and if I leave it on for like 5min itll restart and that screen will come up. Any help?
Have you tried running it with the program again? That might help
You can either keep attempting to get s-off, or you can just keep s-on for now and have a working phone. If you want to skip s-off for now and have a working phone, download the leak ICS stock rom and rename it to ph85img.zip. Put the file onto a microsd card, and put the card into your phone. Relock your bootloader and boot into bootloader (vol down + power). Your phone should automatically install the ROM. You should have a working phone after it's done.
Related
A few weeks ago, I decided to install Liberated Aria. I had a few problems with the installation, but eventually it ended up working fine. Last night, I turned my phone off and turned it back on this morning, but now it won't boot. When I turn the phone on, I get:
LIBERTY PVT SHIP S-ON
HBOOT-0.57.0000
MICROP-031b
TOUCH PANEL-STN 21_00
RADIO-7.08.35.06
MAY 8, 2010,03:56:58
FASTBOOT
and then the options:
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
When I try to boot into recovery, I eventually get:
SD Checking. . .
Loading . . .[LIBEDIAG.zip]
No image!
Loading. . . [LIBEDIAG.nbh]
No image or wrong image!
Loading. . . [LIBEIMG.zip]
No image!
Loading. . . [LIBEIMG.nbh]
No image or wrong image.
and the options change to:
HBOOT
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
The only problem is that I can't select any of the options. None of the buttons - volume, power, whatever - change or select anything. I can't get past either of these screens. I'm kind of a noob when it comes to this kind of thing, so any help would be appreciated.
The phone will automatically boot into FASTBOOT mode if you hold down the trackpad button while pressing the power button. Is it possible that your trackpad button is broken and is being registered as held down? Try messing with it to see if you can fix it. Otherwise you may have to get the phone replaced if it's under warranty.
This issue does not sound like it is related to installing Liberated Aria.
The trackpad button feels the same as it always has when I click it and I don't see anything visibly wrong with it, so I don't see why it would be registered it as clicked. I tried pushing it and all the other buttons a number of times with the same results. I even took off the screen protector thinking maybe that was causing a problem. Is there a way I can just put an image on my SD card and have it automatically boot that so I can fix it?
Doesn't installing a custom bootloader and/or ROM void the warranty?
Well, you probably will be able to simply run the 2.1 RUU on your phone since you can get to FASTBOOT. I'd probably recommend that over doing the SD card method because when you do the SD card method, you have to press a couple buttons to confirm actions which may not work if your phone isn't accepting button presses. The RUU method does not involve any button presses on the phone itself.
However if you want to try the SD card method I can point you in the right direction.
Edit: Link to 2.1 RUU here: http://www.mediafire.com/?cj56c2gfk86k8oe
Rohda said:
Doesn't installing a custom bootloader and/or ROM void the warranty?
Click to expand...
Click to collapse
Installing a custom bootloader would for sure, but you don't have a custom bootloader. Installing a custom ROM does, but you can reverse the process (via RUU) so they can't really tell.
I downloaded the 2.1 RUU, booted to recovery, connected my phone to my computer, and tried to run the RUU but it gave me a USB connection error. Windows also gave me a USB device not recognized error. My phone does say HBOOT USB PLUG, though. Aside from HTC Sync, do I need another driver?
Do you still have the HBOOT driver installed from when you used Unrevoked? If so you should uninstall that driver I believe. That might be interfering.
Also trying running the RUU when your phone is in FASTBOOT, not HBOOT, to see if that works.
I did have the HBOOT driver still installed. I uninstalled it from device manager and deleted the driver folders. Android Phone doesn't show up in device manager anymore. I retried running the RUU in HBOOT and tried running it in FASTBOOT and still get the USB connection error. Any other ideas?
Try reinstalling HTC sync
Sent from my Liberty using XDA App
Also try doing it on a different computer if you have access to one. Preferably one that never had any drivers on it before. Just install HTC Sync, then run the RUU, that's it.
I've always had trouble getting the RUU to run. It's bizarre.
If that doesn't work, and you still want to try the SD card method, you can download this file: http://www.mediafire.com/?ct1ay7t93d8g742
Rename the zip file to LIBEIMG.zip then place it on the SD card. Then it should automatically detect the file next time you're in HBOOT and ask you if you want to proceed with the install. It's pretty self explanatory. Be patient as some steps take a while and it may appear like nothing is happening. It takes about 5 minutes to finish installing everything and will reboot once during the process. After it's done (it will tell you when it's done), the phone will reboot and there will be a scary looking screen but JUST WAIT about 10 seconds and it will boot normally. Then you're good to go.
After you're done with this, make sure to DELETE the LIBEIMG.ZIP file from your SD card. Otherwise it will ask you every time you go into HBOOT if you want to apply the update.
I reinstalled HTC Sync and it wouldn't recognize the phone was connected.
It seems to have taken a turn for the worse. Now, it won't even turn on. The screen turns on (but stays black) and off and the notification light flashes red when connected to a computer but won't do anything at all when it's not connected. I'll try to plug it into a wall instead of a computer and let it charge for a while and try the SD card method.
I went in today to get it checked out and got a new SIM card and a new battery and it fixed the problem.
Thanks a ton for all the help.
Alright so I've been running UKB and Cubed kernel for the last 6 days without issue. I've had some random reboots and the phone locking up, but I was just going to deal with it until ViperDNA came out. So this morning comes and I unlock my phone and the phone reboots within 2 minutes. Comes to the lock screen and is completely stuck... Alright it happens. I hard reboot the phone (holding down power and volume down buttom) and reboot the phone. Still, it is frozen at the lock screen. Phone is coming up in ADB devices, but it cannot accept any commands. I reboot into recovery (CWM 6.0.2.1) and try to clear cache/dalvik. Reboot the phone and it's still stuck at the lock screen. I go into fastboot and push the stock kernel, phone boots gets to the lock screen, starts of fine and then locks again. I don't have any earlier restores to go to on the phone as I shifted them to my HDD to save a little space. I feel like an idiot now. Any help would be appreciated.
I also tried to sideload ViperDNA via CWM and it isn't showing up the device in ADB.
EDIT: Also while in Fastboot the computer shows the device as attached via Removable hardware as Android 1.0 it just wont let me sideload or push anything other than a kernel.
This happened to me at one point.. I had to re lock the phone in the all in one tool and reunlock and start fresh.. No problem since
With help from Dr_demento on the IRC channel I was able to get the phone booting again. For future reference of people running into this issue, formatting data helps. You'll unfortunately lose everything, but it's better than locking the phone and then unlocking it again.
Ok snoot sure if anyone has experienced this but randomly after using my phone this morning I noticed it was getting really warm in my pocket. I took it out only to realize I am stuck in a boot loop. I can hold volume down and power and get into hboot, but none of the options....even factory reset do anything, just sends the phone into another boot loop. The kicker is that I have never even attempted to REIT my phone yet. Any suggestions other than going to Verizon and taking my chances there?
Have you tried holding down the power button for 10 seconds to hard reboot the device?
If that doesn't work, try getting the phone into the bootloader, connect it to your computer and try to flash an RUU from there. There's a link to the download for it in the development section, along with guides on how to use it. If you can't flash the RUU, post back here and we can help with that, but if the RUU flashes successfully and it still boot loops, there's probably not much to do except take it back.
This is going to be a long story hopefully someone will find the trigger.
My phone has been succussfully been S-off and rooted using the DirtyRacun method for over a year. I have used the recovery and booted different ROMs with no problem. I have found a ROM that I like and have been using it and haven't changed anything recently. The following problem arose from a normal day of usage.
I had my phone turned off because I was not going to be using it and wanted to conserve battery. Upon turning it on it was fine and battery above 60%. Within an hour my phone screen was black and unresponsive although the bottom lights were on. I held the power button to do a soft reset. My phone is now stuck in a bootloop at the white htc screen. I rebooted to the bootloader where upon when it does the image checks NONE of them are found. I tried to boot into recovery. Again it goes to the white htc screen and enters a bootloop. I boot back into bootloader. If I go to the powerdown option my phone turns off. 20 seconds later it turns itself back on without any intervention and goes back to bootloop. I let the battery die and then plugged it in. It charged for a while and then proceeded to start turning itself back into bootloop without any intervention.
I did also try to fastboot flash recovery twp.image It was unsuccessful due to low remote battery. (phone has currently died again. I'm going to let it charge until it starts itself again and retry that step to see if I might have a large enough charge then). The following from the Don't Panic guide is most relevant I believe...
"Bad kernel and or system image and recovery Phone will boot to boot loader, will not boot to OS and selecting recovery will boot to boot loader. All is not lost, simply fastboot recovery and or boot image (for those on HBOOT 1.15 and higher) and then flash ROM from recovery. This happens but it is very unlikely it will happen to you."
HELP....
I am outside of my league on this one.
Any help will be much appreciated
I took it to Sprint. They thout it was the power button, after replacing it and the same I got a refurbashed phone through TEP insurance at no cost. WIN. Except does anyone have S-off suggestions for Hboot 2.09 and mainver 3.17.651.4 dirtyracun which I am familiar with does not apper to work.
m1gramme said:
This is going to be a long story hopefully someone will find the trigger.
My phone has been succussfully been S-off and rooted using the DirtyRacun method for over a year. I have used the recovery and booted different ROMs with no problem. I have found a ROM that I like and have been using it and haven't changed anything recently. The following problem arose from a normal day of usage.
I had my phone turned off because I was not going to be using it and wanted to conserve battery. Upon turning it on it was fine and battery above 60%. Within an hour my phone screen was black and unresponsive although the bottom lights were on. I held the power button to do a soft reset. My phone is now stuck in a bootloop at the white htc screen. I rebooted to the bootloader where upon when it does the image checks NONE of them are found. I tried to boot into recovery. Again it goes to the white htc screen and enters a bootloop. I boot back into bootloader. If I go to the powerdown option my phone turns off. 20 seconds later it turns itself back on without any intervention and goes back to bootloop. I let the battery die and then plugged it in. It charged for a while and then proceeded to start turning itself back into bootloop without any intervention.
I did also try to fastboot flash recovery twp.image It was unsuccessful due to low remote battery. (phone has currently died again. I'm going to let it charge until it starts itself again and retry that step to see if I might have a large enough charge then). The following from the Don't Panic guide is most relevant I believe...
"Bad kernel and or system image and recovery Phone will boot to boot loader, will not boot to OS and selecting recovery will boot to boot loader. All is not lost, simply fastboot recovery and or boot image (for those on HBOOT 1.15 and higher) and then flash ROM from recovery. This happens but it is very unlikely it will happen to you."
HELP....
I am outside of my league on this one.
Any help will be much appreciated
Click to expand...
Click to collapse
Did you upgrade to the new partitions? What ROM had you flashed? The only two S-off methods that I know that work without any problems are rumrunner and firewater.
What HBoot version? What exact version of TWRP are you trying to flash? If you've upgraded to new partitions, you'll need the modified TWRP.
Once you provide a bit more information, it will be easier to tell you what to do next.
fizbanrapper said:
Did you upgrade to the new partitions? What ROM had you flashed? The only two S-off methods that I know that work without any problems are rumrunner and firewater.
What HBoot version? What exact version of TWRP are you trying to flash? If you've upgraded to new partitions, you'll need the modified TWRP.
Once you provide a bit more information, it will be easier to tell you what to do next.
Click to expand...
Click to collapse
My HBOOT is 2.09.4444
I believe my ROM was eiter a rooted sense or BeanStalk 4.3. I honestly don't remember because I haven't changed anything in so long.
I had TWP openrecovery-twrp-2.6.3.0-jewel.img
Again this wasn't a problem that came from trying to change anything. My phone froze I soft-reset it and it was in an unstoppable bootloop. No images were found. Telling it to go to recovery still took it to bootloop. Even after power down from bootloader, after 20 seconds it boots back into bootloop.
The problem I feel most at hand is I can't charge the battery enough to do anything because it appears to not charge in bootloader.
I have had my phone rooted and s-off through Dirty Racun for almost a year now and have been using the same setup without changing for at least 6 months.
The "no image" error you're referring to isn't a error at all. It's normal-the bootloader is scanning for a file named PJ75IMG.zip on the external SD card. Unless you have one on it, you'll get that message. It's normal. Have you tried removing your SD card and seeing if the phone will boot? Also, have you had any luck powering the phone off and letting it charge?
If you're able to and have the proper equipment, I'd test the internal battery with a voltage meter to see if it is even able to hold a charge, will save a lot of frustration.
Magnum_Enforcer said:
The "no image" error you're referring to isn't a error at all. It's normal-the bootloader is scanning for a file named PJ75IMG.zip on the external SD card. Unless you have one on it, you'll get that message. It's normal. Have you tried removing your SD card and seeing if the phone will boot? Also, have you had any luck powering the phone off and letting it charge?
Click to expand...
Click to collapse
Again the hardest part about this is my phone refuses to turn off. I have gone into the bootloader and selected Power Down. The phone turns off and the charge light blinks. Then 20 seconds later without me touching it, it turns on and starts into the bootloop.
I am currently finding some luck by holding the down button so when it starts itself again I can be in bootloader mode and select power down. I have elevated my battery from 3530mv to 3649mv (as per fastboot getvar battery-voltage)
Any suggestion as to where a good number to reach would be helpful.
Magnum_Enforcer said:
The "no image" error you're referring to isn't a error at all. It's normal-the bootloader is scanning for a file named PJ75IMG.zip on the external SD card. Unless you have one on it, you'll get that message. It's normal. Have you tried removing your SD card and seeing if the phone will boot? Also, have you had any luck powering the phone off and letting it charge?
Click to expand...
Click to collapse
See above about "charging" after getting it up a little (and without SD card) I tried booting to recovery (getvar battery-status good) still went to htc bootloop screen. Tried to flash recovery and boot as per
"Bad kernel and or system image and recovery Phone will boot to boot loader, will not boot to OS and selecting recovery will boot to boot loader. All is not lost, simply fastboot recovery and or boot image (for those on HBOOT 1.15 and higher) and then flash ROM from recovery. This happens but it is very unlikely it will happen to you."
in troubleshooting guide. Still continues in bootloop
So a littel update after spending forever with my charging trick I was able to get a little more charge. I was able to run commands of flash recovery it stated it was complete. Still boots to bootloop. I was able to try to run RUU using RUU 3.15.651.16 - HBOOT 2.09
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip RUU.zip
The whole process worked (said it did)
Still in repeating bootloops at htc screen.
Phone still turns itself on into a bootloop even after selecting power down from bootloader.
I'm beginning to think it's the dreaded brick...
Interesting issue, indeed. There were some problems reported with the 3.15 RUU, but none that should cause the issue you're having. Check out the top link in my sig and go to the bottom of the first post. Hit up the link for VipeRUU. I suggest trying it and returning your phone to stock. If after returning your phone to stock the issue persists, then you most likely have a hardware issue (already sounds like that's likely the case). If you have TEP with Sprint you can take the phone to a Sprint service center and see about getting it replaced.
Sent from my HTC device
My wife had that issue as well but a factory reset fixed
Sent from my EVO LTE using Tapatalk
Hi all,
This is my sons phone which he doesn't use as phone - just for games.
Last night he dropped it and it froze, after removing battery it started powering and boot-looping on white htc logo screen.
I powered it with vol down and went on boot-loader and I thought I just restore it via recovery to a state I made him few months back, but failed to go to recovery, again on white screen loop.
I tried installing shipped ruu and after few fails I did it, but again restarts on white screen.
I can connect it to pc and all, running fastboot commands usualy comes with "remote not allowed"
I was sure that I did unlock bootloader for this phone but it says locked, so I am not sure ( having 4 htc phones in same house hard to know what I did to which )
This phone prior to drop had:
4EXT_Recovery_Touch_v1.0.0.5_RC7
S-OFF
not sure on unlocked bootloader
and
Cool-ICS-v17-EvoC
any ideas appreciated
Thank you
PS
I tried to go to htc page and unlock boot-loader, but numbers i paste are not recognized ( I did this many times so its not my error in copy paste)
I guess I cant edit my post.
I managed to unlock bootloader
I installed "Cool-ICS-v17-EvoC" rom via sd card as PG86IMG.zip as I can't load into recovery
and it reboots on white htc logo again
help
Wow... If the issue occurred after a drop, I'd worry it's a hardware issue.
As far as not being able to access recovery, either go into the power settings and uncheck fastboot, or do a battery pull and then access the bootloader with volume down +power and then select recovery.
Brian706 said:
Wow... If the issue occurred after a drop, I'd worry it's a hardware issue.
As far as not being able to access recovery, either go into the power settings and uncheck fastboot, or do a battery pull and then access the bootloader with volume down +power and then select recovery.
Click to expand...
Click to collapse
I can get to bootloader and try to switch to recovery, but phone never gets there as it has to reboot into it and once it gets to white screen it loops.
I thought rom got corrupted and tried to restore it, but you are right, it might be a hardware.
I found a motherboard for $18 on ebay but I am not sure will it fix the issue.
cipher101 said:
I can get to bootloader and try to switch to recovery, but phone never gets there as it has to reboot into it and once it gets to white screen it loops.
I thought rom got corrupted and tried to restore it, but you are right, it might be a hardware.
I found a motherboard for $18 on ebay but I am not sure will it fix the issue.
Click to expand...
Click to collapse
Apologies, I went and re-read the op and now I see that.
I think you are having trouble with the fastboot commands because of the locked bootloader like you said. You could also use the juopunutbear patched hboot since you are s-off, it will give you access to the extra fastboot commands regardless of locked/unlocked state. It can be flashed as a PG86IMG.zip via the bootloader.
If you use the patched hboot you could attempt to boot recovery into memory by using fastboot boot recovery.img
Because you are s-off, you can also flash a recovery via the bootloader as a PG86IMG.zip. If you want to try, here is 4ext recovery:
https://www.dropbox.com/s/t6q8wi58xzidgan/4ext_1.0.0.5.rc9_PG86IMG.zip
Obviously just Rename the file and remove everything prior to PG86IMG.zip.
I have a feeling though that since you successfully ran the ruu and it still won't boot, that no amount of software changes will fix the issue. I'm not sure if the motherboard will fix the issue or not buy that's a pretty cheap fix to try
Thanks for help and advice man,
I bought him a working used evo 3d from ebay, it was under $30 so I'll keep this one for parts I guess.
Thanks again