Was running jellybomb for a few months, nothing has changed recently. This morning I started to notice a static looking colorful screen for a few seconds before the locker showed up. Later in the day, the same static was taking over my status bar. Then static staying on the screen, would take several power cycles befpre I could get to my phone, the displays were completely out of whack, and while the phone seemed to operate and run just fine (according to the sounds & vibration feedback)... the screen would lag behind by about 5 seconds, and remain for the most part, jumbled and static everywhere, making it impossible to do anything.
I backed up my phone, was able to clear cache, dalvic cache, factory reset, etc, I'm s-on so I flashed the kernel (boot.img) via adb fastboot, the phone re-set (don't remember how), and am unable to get into bootloader in order to install the rom. I hit the power and it vibrates and is "on", just a black screen. I cannot get the timing right on doing a simulated battery pull and power + vol. down to get into the bootloader since the screen is not visible. Any other way I can get to boot loader/recovery? I have the SDK installed, can the phone be viewed on my computer? All I need to do is install the rom.
I have TWRP on it BTW.
Anyone suggestions would be greatly appreciated, this one's over my head.
Thanks,
-Mike
****** SOLVED *******
Took it to sprint, the tech said he asked HTC what causes this. They say it is static buildup on the ribbon for the display. They are able to take a strong magnet and run it across the ribbon to fix the problem.
Try holding power button a while longer, do you see the lights on the bottom started to flash? If so release power button and hold volume down.
Sent from my EVO using xda premium
Have you tried using adb to boot in to recovery?
adb reboot recovery
Sent From My Sweet Ass EVO LTE
k, think I got my phone into usb-fastboot. I did the exact same w/ my girls phone and counted the seconds for it to come up, then did the same on my phone.
Now, when I do the command "adb devices" either of the two phones. I was getting "device list attached". I then checked device manager and found "Android USB Devices" and under that "My HTC", but no ADB devices. I tried all the drivers I could find..... latest HTC sync.. updated from the SDK manager, etc. I cannot get adb to connect with the phones. I don't even know where to look, I've been at this for two days now.
Can someone that is far smarter than me please help. $15 paypal to whoever gets my phone back from hell.
-Mike
k, got the phone connected via adb, and was able to get the phone in recovery (TWRP), however, the screen is just static, so I can only navigate in the dark. I need to find a sure fire way to install the rom. I have a copy of the rom on the external SD, and on the phone. Is there a way I can view my phone's screen with my computer? Or another way of installing the rom using adb, or some other program?
uuuh. So damn frustrating. Someone PLEASE help. I am now just trying to relock bootloader and run RUU to get things back to sanity, but I cannot seem to get fastboot working. I can only be in recovery. I adb reboot-bootloader, give it a few, then press the power button once. Now I should be in fastboot-usb, but I cannot communicate via adb.... What the heck is going on?
You need to list your bootloader details: hboot, baseband, software version, etc. If you are hboot 1.15 or 1.19 I would go to the dirty racun site and follow their instructions through step #11 to get your phone working again. Follow their instructions exactly. Pay attention to step #9 and if you see the failure, use the arrow keys to move up in the cmd window and rerun the ruu. You don't have to continue all the way to s-off if you don't want to, but if you download the appropriate ruu for your current hboot and follow their instructions it will get you back to a working phone and you can go from there.
cruise350 said:
You need to list your bootloader details: hboot, baseband, software version, etc. If you are hboot 1.15 or 1.19 I would go to the dirty racun site and follow their instructions through step #11 to get your phone working again. Follow their instructions exactly. Pay attention to step #9 and if you see the failure, use the arrow keys to move up in the cmd window and rerun the ruu. You don't have to continue all the way to s-off if you don't want to, but if you download the appropriate ruu for your current hboot and follow their instructions it will get you back to a working phone and you can go from there.
Click to expand...
Click to collapse
Thanks, I will check it out if I get stuck again. Me screen gave me just enough where I re-installed the rom, and was able to install drivers for fastboot. I was then able to re-lock the bootloader. I am currently trying to run a RUU to see if that fixes the problem. At the very least, I can take it to sprint and have them deal with it now that it is back to stock.
-Mike
Related
I unlocked my phone with the htc method. I had root, and superuser. titanium backup worked fine. I made a nandroid backup before I started messing with ROMS. I decided to flash infected's ROM first. Everything seemed to be going ok. It rebooted, and I got the cool beats animation. Then I got the htc splashscreen. then it just flipped back and forth between them for a half hour or so. something was obviously wrong. I tried rebooting the phone: same results. I can get into bootloader, both by holding volume down while powering up, and through the command prompt, via adb. I have a nandroid backup through twrp recovery, so no problem, right? well, it didn't work. So now, I can boot into the bootloader screen, but nothing else. I tried flashing a different ROM, but to no avail. Eventually, I noticed that I had htc sync running while I did all this. Did that wreck me? Any ideas what I can do now? I just tried to restore my nadroid backup again, without htc sync running, but all I get is a white htc screen. Please help me unbrick my phone!!!
whenever I try to flash ANY other rom, I get to the part where I have to use fastboot to flash the boot.img, and it says "sending boot" and just stays there forever.
Tried flashinf recovery.img, and the same thing happens. "sending recovery" and screen pause
God I hope someone smarter than me feels generous enough to help here...
Are you on windows? Did you install htc drivers?
Sent from my PG86100 using XDA App
I am on windows 7, and I have the htc drivers installed. Like I said, I successfully completed the htc unlock method. I had no problems until I tried to flash a rom
So you hold volume down and power to enter fastboot. Select fastboot by hitting power again. Then plugin usb and it should say fastboot usb. Then what command do you type after that?
Sent from my PG86100 using XDA App
now it wont even go into hboot. not with vol down and power, or through command prompt. before, it was going into hboot just fine, and I was using fastboot flash boot boot.img to flash the rom, but everything froze
now when I plug it in and use the command prompt to enter adb reboot bootloader, it just says device not found. holding power and vol does nothing
Hmmm.. Not sure why you can't get into fastboot but your using the wrong command. You want to type fastboot boot recovery.img. Recovery being the name of the recovery image in your folder.
Sent from my PG86100 using XDA App
thanks. I'll try that if I can get back into the bootloader
What you did works for that only installs the kernel. Then you need to flash the rom. I never did it that way nor do I use twrp
Sent from my PG86100 using XDA App
I did flash the rom.zip from twrp recovery. when it rebooted, it started to work, then just went into a boot loop. then I started trying to fix it, now it wont even come on
For now, I'm hoping that the battery just discharged during the process. I'm gonna let it charge for a few hours, and see what happens. I'm afraid that I might have done a battery pull in the middle of the process, though. When I first flashed the InfectedROM, the phone rebooted and got stuck in a loop between the beats graphics, and the htc quietly brilliant screen. it just kept going from one to the other. It went on for quite a while, and eventually, I think I pulled the battery to stop it. However, I was still able to get into the bootloader after this. I tried to reflash the rom, and a couple of others to no avail. When I decided to try to reflash recovery.img, is when it hit the fan, so to speak. after that, I was unable to boot into fastboot, or even get adb to recognize that there was a device there at all. Man, I hope letting the battery charge works. Like a moron, I don't have any insurance on my phone.
when I plug it in, windows intermittently makes the gong noise that something is connecting or disconnecting, and windows explorer briefly recognizes that a removeable drive is present, but I can't get the thing to charge, or turn on at all, and adb refuses to recognize that it connected, so I still cant manually put it into fastboot
well, I left the phone plugged in for about 7 hours. I hooked it up to the computer and once again tried to get into bootloader through adb. The computer said that the "daemon was started successfully" then goes right back to device not found. I guess Im screwed if no one else knows any tricks or ideas..
izzy spun said:
well, I left the phone plugged in for about 7 hours. I hooked it up to the computer and once again tried to get into bootloader through adb. The computer said that the "daemon was started successfully" then goes right back to device not found. I guess Im screwed if no one else knows any tricks or ideas..
Click to expand...
Click to collapse
Pull the battery
Wait 2 minutes.
Put battery back in.
Hold down Vol - and power.
Do not be connected to anything. And are you SURE your battery is good?
PM me if you see this and I dont answer.
I pulled the battery and waited. I even grabbed the battery out of my girl's evo3d. I can get into bootloader via the vol down, and power, but it stopas and asks if I want to update. If I say no, it just reboots to the htc screen. If I say yes, it says updating, then says press power to reboot. Then it goes directly to the htc screen and freezes. While it's in the htc screen, I can use command prompt to get it back into bootloader via the "adb reboot bootloader" command, but I can't get to my recovery menu. I was going to mount usb storage, and put another rom on the sd card, then re-flash, but it won't allow me to get to recovery
izzy spun said:
I pulled the battery and waited. I even grabbed the battery out of my girl's evo3d. I can get into bootloader via the vol down, and power, but it stopas and asks if I want to update. If I say no, it just reboots to the htc screen. If I say yes, it says updating, then says press power to reboot. Then it goes directly to the htc screen and freezes. While it's in the htc screen, I can use command prompt to get it back into bootloader via the "adb reboot bootloader" command, but I can't get to my recovery menu. I was going to mount usb storage, and put another rom on the sd card, then re-flash, but it won't allow me to get to recovery
Click to expand...
Click to collapse
Ok, soundslike you have a "PG86IMG.ZIP" on the root of your SD card. Dont worry, just swap cards with your old lady but put the ROM on it first.
You wont be able to do anything until you swap Sd cards or otherwise delete the PG86IMG.zip.
when I use command prompt to enter bootloader, I get the opening menu: bootloader, reboot, reboot booloader, and power down. If I press power to choose booloader rather than fastboot, the phone immediately goes back to asking me if I want to update, and no matter what I choose, the results are the same. it reboots to the htc screen
Yesterday, battery was at 70% when I headed out. Phone wouldn't boot when I tried it later so I assumed battery died.
Put it on charger and it went to green quicker than expected but still wouldn't boot.
PWR Vol- wouldn't go to bootloader
Went home and connected to PC with ADB, adb devices showed me in recovery, screen stayed off. Issues an adb reboot command litt the screen briefly to the white background green HTC but went back to dark.
Issuing adb reboot-boorloader did bring me to bootloader screen but it wouldn't stay there.
Saw notes that my recovery may have been hosed. so tried to re-push cwm with fastboot flash recovery c:\reco.img (renamed cwm to reco.img)
I don't recall my prompt responses. I'm hoping that along the way I didn't flash recover to boot or vice versa. I think I have may have flubbed one of the commands along the way.
Anyway at this point the 3 button boot does nothing, nor does pwr vol - not does it appear via usb as a device on 2 separate pc's with frresh driver installs and fresh sdk installs.
I have dropped pc86img.zip in the root of the sdcard now just in case i get it to boot.
The usb port is being sorta wonky with my red light coming on only intermittently and I now have to wiggle carefully.
I had been running current rev of viper rom. hadn't touched kernel or poked the phone in naughty places for weeks.
Running RUU exe doesn't detect phone either.
Now for the conspiracy part, has anyone else noticed a few more postings of this ilk in recent days? I may now be paying more attention to 'I'm bricked' postings than normal but it feels like there are other similar stories of unexplained malfunctions. I'm not saying sprint or htc pushed something but maybe an update in apps that many of us rooted users have in common?
When boot key combinations do nothing, doesn't show in adb with usb connected and it won't boot is one truly "bricked?"
I'll head to sprint to diagnose usb connector. If that is the issue, I'll reflash to stock and revert to s-on. I don't feel that anything I've done recently contributed to the death f the phone. No OC or under volting.
thermbug said:
Yesterday, battery was at 70% when I headed out. Phone wouldn't boot when I tried it later so I assumed battery died.
Put it on charger and it went to green quicker than expected but still wouldn't boot.
PWR Vol- wouldn't go to bootloader
Went home and connected to PC with ADB, adb devices showed me in recovery, screen stayed off. Issues an adb reboot command litt the screen briefly to the white background green HTC but went back to dark.
Issuing adb reboot-boorloader did bring me to bootloader screen but it wouldn't stay there.
Saw notes that my recovery may have been hosed. so tried to re-push cwm with fastboot flash recovery c:\reco.img (renamed cwm to reco.img)
I don't recall my prompt responses. I'm hoping that along the way I didn't flash recover to boot or vice versa. I think I have may have flubbed one of the commands along the way.
Anyway at this point the 3 button boot does nothing, nor does pwr vol - not does it appear via usb as a device on 2 separate pc's with frresh driver installs and fresh sdk installs.
I have dropped pc86img.zip in the root of the sdcard now just in case i get it to boot.
The usb port is being sorta wonky with my red light coming on only intermittently and I now have to wiggle carefully.
I had been running current rev of viper rom. hadn't touched kernel or poked the phone in naughty places for weeks.
Running RUU exe doesn't detect phone either.
Now for the conspiracy part, has anyone else noticed a few more postings of this ilk in recent days? I may now be paying more attention to 'I'm bricked' postings than normal but it feels like there are other similar stories of unexplained malfunctions. I'm not saying sprint or htc pushed something but maybe an update in apps that many of us rooted users have in common?
When boot key combinations do nothing, doesn't show in adb with usb connected and it won't boot is one truly "bricked?"
I'll head to sprint to diagnose usb connector. If that is the issue, I'll reflash to stock and revert to s-on. I don't feel that anything I've done recently contributed to the death f the phone. No OC or under volting.
Click to expand...
Click to collapse
If you can get into hboot you arn't bricked.. Tho you usb port may be dicked like a broken part..
I would try to go stock for the hell of it.. I haven't had any issues.. I have in the past hung my phone locked it and dicked sense up.. But a battery pull always helped get back into hboot
So I wonder what is going on with yours.
Have you tried using a different usb cable ?? Or pluggin the phone in and let it charge over night ??
#Root-Hack_Mod*Always\
thermbug said:
Yesterday, battery was at 70% when I headed out. Phone wouldn't boot when I tried it later so I assumed battery died.
Put it on charger and it went to green quicker than expected but still wouldn't boot.
PWR Vol- wouldn't go to bootloader
Went home and connected to PC with ADB, adb devices showed me in recovery, screen stayed off. Issues an adb reboot command litt the screen briefly to the white background green HTC but went back to dark.
Issuing adb reboot-boorloader did bring me to bootloader screen but it wouldn't stay there.
Saw notes that my recovery may have been hosed. so tried to re-push cwm with fastboot flash recovery c:\reco.img (renamed cwm to reco.img)
I don't recall my prompt responses. I'm hoping that along the way I didn't flash recover to boot or vice versa. I think I have may have flubbed one of the commands along the way.
Anyway at this point the 3 button boot does nothing, nor does pwr vol - not does it appear via usb as a device on 2 separate pc's with frresh driver installs and fresh sdk installs.
I have dropped pc86img.zip in the root of the sdcard now just in case i get it to boot.
The usb port is being sorta wonky with my red light coming on only intermittently and I now have to wiggle carefully.
I had been running current rev of viper rom. hadn't touched kernel or poked the phone in naughty places for weeks.
Running RUU exe doesn't detect phone either.
Now for the conspiracy part, has anyone else noticed a few more postings of this ilk in recent days? I may now be paying more attention to 'I'm bricked' postings than normal but it feels like there are other similar stories of unexplained malfunctions. I'm not saying sprint or htc pushed something but maybe an update in apps that many of us rooted users have in common?
When boot key combinations do nothing, doesn't show in adb with usb connected and it won't boot is one truly "bricked?"
I'll head to sprint to diagnose usb connector. If that is the issue, I'll reflash to stock and revert to s-on. I don't feel that anything I've done recently contributed to the death f the phone. No OC or under volting.
Click to expand...
Click to collapse
youre not bricked... you get into hboot fine... its running that you have a problem with so we go tier up...the eMMC of it all...there is a post by unknownforce that is for downgrading hboot 1.5 to .14 or less but follow those directions to the T and it willrewrite everything in there and then if you choose to do so you caqn update to hboot 1.5 and the new RUU and all from there
Can't get into hboot anymore.
can't get into hboot anymore, and if I'm s-off I can't run the process.
thermbug said:
can't get into hboot anymore, and if I'm s-off I can't run the process.
Click to expand...
Click to collapse
Well flashing anything important via usb cable when you don't have a solid connection is a very bad idea, it's quite possible that you are bricked if your phone literally won't even turn the screen on. You can try going to the hboot downgrade thread (I personally bricked my phone while flashing an experimental ROM, and I recovered everything by using step 3 ONLY in the hboot downgrade thread), but I wouldn't try doing anything until you get that usb port on your phone fixed...it shouldn't have any "wiggle room" when the usb cable is plugged in
Edit: if you get a charging light when your phone is plugged in, you're probably not bricked. I never once saw a charge light when I was bricked
w0rdOo said:
Well flashing anything important via usb cable when you don't have a solid connection is a very bad idea, it's quite possible that you are bricked if your phone literally won't even turn the screen on. You can try going to the hboot downgrade thread (I personally bricked my phone while flashing an experimental ROM, and I recovered everything by using step 3 ONLY in the hboot downgrade thread), but I wouldn't try doing anything until you get that usb port on your phone fixed...it shouldn't have any "wiggle room" when the usb cable is plugged in
Edit: if you get a charging light when your phone is plugged in, you're probably not bricked. I never once saw a charge light when I was bricked
Click to expand...
Click to collapse
A slight wiggle is alright. If your led light is coming on and off then somethin is broke.
Sent from my PG86100 using xda premium
Try taking the battery out for a few hours and letting the phone rest. This worked somehow for a few users.
Here is the story. my parent bought my brother the amaze 4g for his birthday. he was messing with it trying to root it and such and today he was trying to install a new rom and while it was installing he disconnected the cable, the screen is a black background with green arrows and a phone. I'm not familiar with this but when i press the power button and down button it says unlocked at the top. When i tried to install the stock rom it keeps coming up with no image.
Is there a way to fix this? Thanks in advance
Was he trying to make it s=off? When I did that on my phone that happened, and it is easy to fix. Ask your brother first, but if he was trying to get s=off, all you have to do is get the leaked ICS image from the dev section and flash it. Download the file from here: http://forum.xda-developers.com/showthread.php?t=1615164&highlight=leak, rename it to PH85IMG.zip and put it on the external SD card, then boot into the bootloader and press the up volume button when it asks if you want to update. However, this only works on T-Mobile phones.
I tried that a bunch of times already but every time it starts checking and at the then it just says no image and goes back to H boot
Edit: It is a T-Mobile phone
Sorry, I just reread your original post, your bootloader has to be locked to flash the file, so boot into fastboot and run "fastboot oem lock" from your computer's command prompt.
I just tried it and it gets stuck on "waiting for device" and I don't know if it makes a difference but something happened with his SD card and my computer couldn't read it so I had to reformat it and its empty right now
If that doesn't work, I am not sure what can be done. I wouldn't think the SD card would matter, but make sure you formatted it as FAT32, just in case, and leave the zip file off of it, go into bootloader and use the volume buttons to go to fastboot, and click the power button to select it, then plug it into the computer. If it then says fastboot usb I would think the oem lock should work, but if that fastboot usb doesn't come up, there might be something wrong with the whole boot loader or something. Sorry I could not help any more.
I went into fastboot and connected the USB cable and it didn't change, it still just say fastboot highlighted in red
I have no idea what you could do to fix that, then. Again, I apologize that I couldn't help more, and I wish you the best of luck with this.
Thanks for trying to help anyway
edit
Adb debugging wasn't on I bet :banghead:
I don't get how he got in this position. I don't use a cord to install ROMs. If he were to unplug, I don't see what that would do except stop charging... Unless he was in disk mode and it caused a bad unmount and corrupted card.
I would try the steps above with a fresh sd card and it should work. Redownload the ics or gingerbread ruu and go through the steps.
He was in the process of flashing his phone with some rom he wanted but then somehow he accidentally disconnected the USB cable and it froze up. Now every time you turn the phone on, after the HTC screen it shows the picture that its being flashed (black background with green arrows going into the phone) so I can't turn the phone on at all but I do know that his phone had usb debugging on before he flashed it.
Ok so I found out he was actually trying to get S-off with some "wire trick" and he said at the beginning of the process the phone was restarting and he accidentally unplugged the usb and when the phone rebooted, it got stuck in the dark screen with the green arrows
This just means he needs to continue trying the wire trick. I was stuck at the screen too. I just kept running the program and attempting the wire trick until I got it right.
Sent from my HTC_Amaze_4G using XDA
I just tried the wire trick and it got all the way to counting 45 seconds and the phone keeps rebooting. So I tried to run the program again and now it says connect device and install drivers
Is there a way to get this phone to work again?
Djordje1000 said:
Is there a way to get this phone to work again?
Click to expand...
Click to collapse
install htc drivers, thats also why it didnt read the fastboot demands
I did I installed one from the htc website for the amaze 4g and one that someone posted on this forum
Djordje1000 said:
I did I installed one from the htc website for the amaze 4g and one that someone posted on this forum
Click to expand...
Click to collapse
i dont know what to say then :/ mabey the computer cant read the amaze
Since I can't get past the htc screen. The computer wont recognize that the phone is connected to it
I has a similar problem when trying to do s-off - try installing htc drivers again after plugging in the usb.
HTC Amaze. Tried toolkit but it will only boot to screen with circle of green arrows then red triangle with exclamation point. Try to boot to HBOOT and get nothing on the screen via toolkit or button combination. Tried factory reset by finally getting into recovery by just randomly pressing buttons on red triangle screen and factory reset throws many lines of errors where it cannot find /data /cache..... I can pull battery and boot into phone and use phone fine but I am trying to unlock bootloader, root, and flash a custom ROM. I have SCOURED these boards and the net. I have looked at screenshots of the bootloader and tried to see if the screen simply isnt showing the information and that is a possiblility since I pressed down once and power button and it went to the same recovery screen. How do I simply flash this whole thing back to stock? HBOOT, RECOVERY, ROM, EVERYTHING? Possible?
Help would be greatly appreciated!
wrong section only developer can post here
jtkknj said:
HTC Amaze. Tried toolkit but it will only boot to screen with circle of green arrows then red triangle with exclamation point. Try to boot to HBOOT and get nothing on the screen via toolkit or button combination. Tried factory reset by finally getting into recovery by just randomly pressing buttons on red triangle screen and factory reset throws many lines of errors where it cannot find /data /cache..... I can pull battery and boot into phone and use phone fine but I am trying to unlock bootloader, root, and flash a custom ROM. I have SCOURED these boards and the net. I have looked at screenshots of the bootloader and tried to see if the screen simply isnt showing the information and that is a possiblility since I pressed down once and power button and it went to the same recovery screen. How do I simply flash this whole thing back to stock? HBOOT, RECOVERY, ROM, EVERYTHING? Possible?
Help would be greatly appreciated!
Click to expand...
Click to collapse
htcdev.com gives you instructions to unlock the bootloader. then you go to the htc amaze all-in-one kit and flash 4ext as a custom recovery. then you can flash any rom you want (assuming you already have ICS installed).
P.S. A quick google for "how to unlock htc amaze bootloader" directs you to htcdev.com for the very first hit. SCOUR HARDER lol.
Moved
Please next time read the rules before posting
With all due respect I have done all of the items using the toolkit involving unlocking the bootloader with token ID. Are you saying to not use toolkit and just use HTCdevs instructions instead?
I apologize for having this in the wrong section. I do not get replies in general or QA sections on this forum or the Note 2 forum.
Sent from my HTC_Amaze_4G using xda app-developers app
jtkknj said:
With all due respect I have done all of the items using the toolkit involving unlocking the bootloader with token ID. Are you saying to not use toolkit and just use HTCdevs instructions instead?
I apologize for having this in the wrong section. I do not get replies in general or QA sections on this forum or the Note 2 forum.
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
You have to go to htcdev.com to get the token ID to use the unlocker utility in the htc amaze all-in-one program................. The instructions are there. Again, a quick google would have told you all this.
All that was completed. Any other advice?
Sent from my HTC_Amaze_4G using xda app-developers app
okay i just read this whole thread and i'm completely lost as to what your trying to do.. first off if your boot loader is still locked and you want to flash back to stock you need to download the correct RUU file for your carrier... if you supply that information i can help you look for the right one.. then you rename that file to ph85img.zip and place it on the root of your SD CARD and boot into bootloader by removing your battery and placing it back in and "HOLDING" volume down and the power button until you are in the bootloader menu... after that its just following the instructions to flash back to stock
these are the instuctions to Unlock Bootloader > FLASH 4EXT > ROOT > Flash ROM
download hasoon's AiO toolkit and instll the htc usb drivers...
use the toolkit to unlock the bootloader if not go to htcdev.com and follow the VERY easy instuctions listed there... (you can skip the first few about installing android sdk)
after you unlock your boot loader proceed to flash your recovery (id suggest using 4EXT since your prob S-ON)
once you have a custom recovery you can proceed to flash the super SU file including in the aio toolkit
then make a "NANDROID" backup of your phone using 4EXT before you continue to flashing any roms
the rest is simple just download what roms you want and read the instructions to flashing the rom..
Ninjistix said:
okay i just read this whole thread and i'm completely lost as to what your trying to do.. first off if your boot loader is still locked and you want to flash back to stock you need to download the correct RUU file for your carrier... if you supply that information i can help you look for the right one.. then you rename that file to ph85img.zip and place it on the root of your SD CARD and boot into bootloader by removing your battery and placing it back in and "HOLDING" volume down and the power button until you are in the bootloader menu... after that its just following the instructions to flash back to stock
these are the instuctions to Unlock Bootloader > FLASH 4EXT > ROOT > Flash ROM
download hasoon's AiO toolkit and instll the htc usb drivers...
use the toolkit to unlock the bootloader if not go to htcdev.com and follow the VERY easy instuctions listed there... (you can skip the first few about installing android sdk)
after you unlock your boot loader proceed to flash your recovery (id suggest using 4EXT since your prob S-ON)
once you have a custom recovery you can proceed to flash the super SU file including in the aio toolkit
then make a "NANDROID" backup of your phone using 4EXT before you continue to flashing any roms
the rest is simple just download what roms you want and read the instructions to flashing the rom..
Click to expand...
Click to collapse
------
I have done all of this to the T back when I originally started this thread and now that I tried it again today. When my phone is booted to bootloader using the toolkit it is just a black screen. When I unlock the bootloader using the token I received from the HTC Dev site the toolkit says it was unlocked successfully. I then flashed custom recovery that it says was done correctly. Then when I boot into recovery it is goes to a picture of a phone with a green circle of arrows for 5 seconds then a phone with a red triangle and exclamation point. If I play around mashing buttons I can get into the stock recovery with blue letters and options to restore (doesnt work, many errors) and 4 other options. It is like my screen is messed up and will not show the bootloader/hboot screens. I have never been able to see the screen with the option for fastloader before which other people can see. Does this make any more sense? When I boot my phone it is a black screen until I see the bleedover from the soft keys, then I have to press the power button to turn screen off and back on for the screen to start working. After that it always works fine!?!?!?! What is wrong here?!? Its like I should just load the stock firmware and start all over but I cannot see the screen to select fastloader so it will recognize the PH#### file I have downloaded and loaded onto my SD Card. I am at a loss over here!
okay so your phone can boot to stock recovery but you cannot boot into the boot loader? via either adb or from pulling the battery and holding the buttons?
Ninjistix said:
okay so your phone can boot to stock recovery but you cannot boot into the boot loader? via either adb or from pulling the battery and holding the buttons?
Click to expand...
Click to collapse
Pretty much, with the exception that the only way for me to get into the stock recovery is trying to flash a custom recovery and the phone going to the screen with the green arrow circle then the screen with the red triangle and exclamation and I start pressing random combinations of volume up and power.
I have never seen anything other than:
Green circle screen
Red triangle screen
Stock recovery with blue lettering after random buttons
Ok, this is quite confusing lol. Let's start from the beginning. Take your battery out, put it back in then power on the phone while holding down the volume-down button. This will get u into the botloader. On the top left there will be a few lines of writing, post back here what those lines say. Then we will see where you are and go from there...
sent from my
NRGized amaze
powered by Faux
aj_2423 said:
Ok, this is quite confusing lol. Let's start from the beginning. Take your battery out, put it back in then power on the phone while holding down the volume-down button. This will get u into the botloader. On the top left there will be a few lines of writing, post back here what those lines say. Then we will see where you are and go from there...
sent from my
NRGized amaze
powered by Faux
Click to expand...
Click to collapse
Can't get into bootloader using any method..........
jtkknj said:
Can't get into bootloader using any method..........
Click to expand...
Click to collapse
Are you sure? Have you taken out your battery, put it back on, put the cover of the phone back on, press AND hold Volume Up and Power Button until you get a white screen that has some options and with the android mascots on the bottom of the screen (in other words the bootloader)? If no, then you need to boot into bootloader through hasoon2000's kit. Now what you do is you install the HTC Drivers through his kit (highlight install HTC Drivers at the top left box, first option in his kit), then after that, have your phone connected to your computer with a USB, then on your phone, go to Developer options in Settings then check USB Debugging. Once that's done, with your phone connected to your computer still, go back to the toolkit and in the second to left box you'll see reboot to bootloader. Click on that and then click on the button below the box that says "Do Command".
nulcon said:
Are you sure? Have you taken out your battery, put it back on, put the cover of the phone back on, press AND hold Volume Up and Power Button until you get a white screen that has some options and with the android mascots on the bottom of the screen (in other words the bootloader)? If no, then you need to boot into bootloader through hasoon2000's kit. Now what you do is you install the HTC Drivers through his kit (highlight install HTC Drivers at the top left box, first option in his kit), then after that, have your phone connected to your computer with a USB, then on your phone, go to Developer options in Settings then check USB Debugging. Once that's done, with your phone connected to your computer still, go back to the toolkit and in the second to left box you'll see reboot to bootloader. Click on that and then click on the button below the box that says "Do Command".
Click to expand...
Click to collapse
LOL yes. Cannot get into bootloader using your method or the toolkit method which I have used over and over.
jtkknj said:
LOL yes. Cannot get into bootloader using your method or the toolkit method which I have used over and over.
Click to expand...
Click to collapse
That's weird...WHAT HAPPENED TO YOUR PHONE?!
Hi All,
I have an HTC One that is stuck in a bootloop and have no idea how to fix it.
Unfortunately, there was a screen lock and after failed attempts, it started to delete the data. Stupidly, I tried to reset the phone at this point. As a result, it is stuck in a bootloop.
I have tried holding power and volume down button, volume down button by itself, both volume buttons and still can't get it to fastboot screen.
I am using Mac OSX.
Also, nothing had been done to the phone prior to this. All stock.
Any help would be greatly appreciated.
You have a few options, though it would be helpful if you had access to a PC, because then you could just use the RUU program to set everything right. You will need to know which variant of the One you have as in from which carrier or region, if it is an international version, as well as the system update that it was on as you can not downgrade while stock. The phone will eventually reboot if you just hold the volume keys and power together for like 30 seconds.
Option 1) Find a Windows PC and download the RUU exe, put the phone in bootloader mode, and follow the directions of the RUU.
Option 2) Unlock the bootloader at htcdev.com, install a custom recovery such as TWRP, and use a custom rom to get going. (This one you should be able to do on a Mac - voids warranty if you have one)
Option 3) Find a way to extract the rom.zip from the RUU exe and use fastboot to flash it. (Might be able to do on a Mac, though not familar with it to tell you what tool you could use to extract files from an exe on OS X)
es0tericcha0s said:
You have a few options, though it would be helpful if you had access to a PC, because then you could just use the RUU program to set everything right. You will need to know which variant of the One you have as in from which carrier or region, if it is an international version, as well as the system update that it was on as you can not downgrade while stock. The phone will eventually reboot if you just hold the volume keys and power together for like 30 seconds.
Option 1) Find a Windows PC and download the RUU exe, put the phone in bootloader mode, and follow the directions of the RUU.
Option 2) Unlock the bootloader at htcdev.com, install a custom recovery such as TWRP, and use a custom rom to get going. (This one you should be able to do on a Mac - voids warranty if you have one)
Option 3) Find a way to extract the rom.zip from the RUU exe and use fastboot to flash it. (Might be able to do on a Mac, though not familar with it to tell you what tool you could use to extract files from an exe on OS X)
Click to expand...
Click to collapse
Thanks for replying.
It is the HTC6500L that was originally used with Verizon in the US. Not sure if it matters but it is currently unlocked and using Optus sim in Australia. I'm not sure what system update it was on
I am going to try and get it working on my Mac first but it is good to know that there are options for me with a windows PC.
So you say that the phone will eventually boot if I hold both the volume buttons and power button down for about 30 seconds?
The phone is currently off as the battery has drained. If I charge it, it automatically goes to the HTC logo and into the boot loop. In order to get anything fixed, I need to get to the recovery screen right?
Nick2910 said:
Thanks for replying.
It is the HTC6500L that was originally used with Verizon in the US. Not sure if it matters but it is currently unlocked and using Optus sim in Australia. I'm not sure what system update it was on
I am going to try and get it working on my Mac first but it is good to know that there are options for me with a windows PC.
So you say that the phone will eventually boot if I hold both the volume buttons and power button down for about 30 seconds?
The phone is currently off as the battery has drained. If I charge it, it automatically goes to the HTC logo and into the boot loop. In order to get anything fixed, I need to get to the recovery screen right?
Click to expand...
Click to collapse
You'll need to get it to the bootloader screen at least. It definitely should be able to. I have had to deal with similar issues before.
es0tericcha0s said:
You'll need to get it to the bootloader screen at least. It definitely should be able to. I have had to deal with similar issues before.
Click to expand...
Click to collapse
So, I just tried to hold the power button and both volume buttons down for a good couple of minutes and nothing happened. Is that method hit and miss or you are sure that it will work eventually?
Try this http://forum.xda-developers.com/showpost.php?p=41795693&postcount=5