Hello everyone,
Short and simple....I've f*cked up.
A) I have no recovery flashed to my device
B) Fastboot/ADB is not working with my device, because the original cable it came with got destroyed, and all other microsd cords I've tried, charge only.
C) I have no rom on the phone.
All I have access to is a 8GB microsd card with adapter to read it in my computer.
My phone is useless right now and any help would be greatly appreciated.
HTC Amaze 4G
WindMobile
I have to ask, how did you end up with no rom or recovery? Have you tried putting a recovery on the phone yet?
http://forum.xda-developers.com/showthread.php?t=1521169
Use the second option (marked easy), granted that works then it should be a matter of loading a rom onto the sd card and flashing?
Good luck!
If you can't get into fastboot, you're pretty screwed... Try and get your hands on an original cable
freddy009 said:
Hello everyone,
Short and simple....I've f*cked up.
A) I have no recovery flashed to my device
B) Fastboot/ADB is not working with my device, because the original cable it came with got destroyed, and all other microsd cords I've tried, charge only.
C) I have no rom on the phone.
All I have access to is a 8GB microsd card with adapter to read it in my computer.
My phone is useless right now and any help would be greatly appreciated.
HTC Amaze 4G
WindMobile
Click to expand...
Click to collapse
well good news is that you're not bricked... bad news is that you need a working cable to get into fastboot to flash a recovery as previously mentioned lol
also for future reference this should have been posted in the general sub-forum btw lol
im sorry but i think the only difference between the original cable and the USB Cable Micro USB is that i htink the Original cable has a better layout so it doesn't fall out now? like on my other blackberry the usb comes off so quickly. Here its imposible for it to come off. Shouldn't they function the same? it just has a different head size.
freddy009 said:
Hello everyone,
Short and simple....I've f*cked up.
A) I have no recovery flashed to my device
B) Fastboot/ADB is not working with my device, because the original cable it came with got destroyed, and all other microsd cords I've tried, charge only.
C) I have no rom on the phone.
All I have access to is a 8GB microsd card with adapter to read it in my computer.
My phone is useless right now and any help would be greatly appreciated.
HTC Amaze 4G
WindMobile
Click to expand...
Click to collapse
why dont you trt an RUU? stick that on your sd, boot into hboot, it should flash by itself.
alx294 said:
why dont you trt an RUU? stick that on your sd, boot into hboot, it should flash by itself.
Click to expand...
Click to collapse
+1. Best option if you dont have a cable.
You can find what you need here:
http://forum.xda-developers.com/showthread.php?t=1521162
Rom||RUU|| Shipped Ruby ROM Collection
Sent from my NRGized Amaze...
via xda premium
I tried to use the wind RUU, but don't you need to be oem locked, which is done through fastboot?
If I was to gain access to fastboot, what would be recommended to do right away.
freddy009 said:
I tried to use the wind RUU, but don't you need to be oem locked, which is done through fastboot?
If I was to gain access to fastboot, what would be recommended to do right away.
Click to expand...
Click to collapse
Why don't you elaborate a little, how did you get to where you are now. What did YOU do to brick the phone?
freddy009 said:
I tried to use the wind RUU, but don't you need to be oem locked, which is done through fastboot?
If I was to gain access to fastboot, what would be recommended to do right away.
Click to expand...
Click to collapse
First off, this shouldn't be here but in General/Q&A. I'm sure binary will move it there.
Secondly, just to go step by step... When you pull the battery and restart while holding the volume down key what happens?
Lastly, I would recommend placing the wind RUU on your sdcard's root.
Step 1) Visit this thread http://forum.xda-developers.com/sho...;<br />Rom||RUU|| Shipped Ruby ROM Collection
Step 2) Download the appropriate PH185,,.zip file to the root of your SD card...
Step 3) Put the sd card in your phone, Boot into HBOOT by Pressing VOL DOWN + POWER together...
When you can get into HBOOT, the system will identify the PH185 image on your card and will ask you if you want to update. Press VOL UP for YES to confirm... and let it flash.
Step 4) Grab a beer and enjoy your Amaze
p.s. If you cant get into HBOOT, than your screwed...
I am able to get into hboot, when I get into hboot, it takes a while for it to read thr file, when it finishes it just dissappears, no prompt to apply update.
I think my usb port is short circuited or something, because sometimes it shows hboot usb, but it flickers on and off. Tried three other wires, only the one shows any sign of usb functionality for me. If going out and buying another wire will help I will go, but I have no idea if it will.
I had the cwm 5.5.504, I had the dual cpu rom on it, but i wanted to change to sense 3.5, and I got stuck in the bootloop. Then when I boot into recovery again, my batt died and now when I try to get into recovery, flashes for a second then goes to white htc screen and hangs there indefinitley.
Usb wires only charge my device as of now.
freddy009 said:
I am able to get into hboot, when I get into hboot, it takes a while for it to read thr file, when it finishes it just dissappears, no prompt to apply update.
I think my usb port is short circuited or something, because sometimes it shows hboot usb, but it flickers on and off. Tried three other wires, only the one shows any sign of usb functionality for me. If going out and buying another wire will help I will go, but I have no idea if it will.
I had the cwm 5.5.504, I had the dual cpu rom on it, but i wanted to change to sense 3.5, and I got stuck in the bootloop. Then when I boot into recovery again, my batt died and now when I try to get into recovery, flashes for a second then goes to white htc screen and hangs there indefinitley.
Usb wires only charge my device as of now.
Click to expand...
Click to collapse
this is why you flash stuff with a full battery... you probably got stuck in a bootloop because you didnt flash the sense3.5 kernel, so my first recommendation would be to flash the dual core rom.. but since you cant get into recovery... hm...
HOLD ON. cant you flash the older cwm through hboot?! wasnt that the old method? place the pxxxx.zip on your sd and wait? why dont you try that and see if you cant get into recovery?
Do i rename the wind RUU PH85.img as well? or .zip?
I just went through all these steps, and then the PH85IMG.zip loads and reads, but no prompt comes up to update or not.
My phone is relocked via fastboot oem lock
so you got fastboot working, or what?
if so, there was some method to flash that PH85IMG.zip manually
kind of 'fastboot oem rebootRUU' something like that
I just tried that, it brought me to an hboot screeen with a RUU highlighted option, no option to do anything with it.
it should been reboot you in to RUU flashing mode (black screen with some logo in the middle of it)
you didn't answered, your fastboot is working now, right?
so why don't you just flash a recovery? or you tried?
I ended up with this.
my fastboot is working, only because i have the wire contorted in this weird way
If fastboot is working then try downloading the toolkit and using it to flash recovery. First thing to do though is make sure that battery is charged up.
Related
I used Rom Manager to apply an update to my DasBamf 2.0-beta5, and the phone reset but did not into Clockwork. Instead it got stuck in a boot loop.
I thought nothing of it, held down the volume button and went into the bootloader. Turns out I left a radio update on the root of my SD Card, so no biggie, I plugged the SD Card into my pc, removed the radio update file. I put the card back into my phone and now I cannot get into Clockwork!
Every time I get to bootloader, click recovery, then it goes into clockwork for a second, says:
E: Can't Mount /cache/recovery/command
E: Can't Mount /cache/recovery/log
E: Can't Open /cache/recovery/log
E: Can't Mount /cache/recovery/last_log
E: Can't Open /cache/recovery/last_log
What should I do? I do not have any idea what the issue is here!
Uhhhh flash a new rom... It appears clockworkmod is still partially useable
Sent from my ADR6400L using XDA Premium App
I wish it were that simple. Clockwork is unusable. After the error message appears, the phone reboots into a boot loop with the White HTC Logo.
Load the stock rooted ruu through the bootloader than reflash can in the stock ruu than reupdate to gb
Sent from my ADR6400L using XDA App
Can you boot into your ROM?
If so, the just reflash CWR via Rom Manager.
If not, grab a root stock RUU and flash that via HBOOT. Then download Rom Manager from the market, then reflash CWR.
Only bad thing about the second option is that you will loose /data.
I *think* there is a way to flash CWR via adb, but I'd have to look it up.
I feel really stupid because I thought I had a grasp on this whole thing...I got rooted without any trouble!!!
BUt I am not sure what is up at this point. I took the advice of those above, and loaded the stock rooted RUU through HBOOT (http://forum.androidcentral.com/thu...8597-ruu-return-rooted-stock-leaked-ruus.html).
- Put zip on SD-root folder
- Rename to PG05IMG.zip
- Boot into HBOOT
- Press Vol Up To start update
- Reboot phone
- Boot loop (never goes past the white HTC screen before resetting)
But afterwards I still am stuck in a boot loop! When I boot to recovery I get into CWR, and can move through the menus, but the phone reboots after a second or two (not enough to restore a backup).
Am I doing something wrong?
Sounds to me like the RUU didn't take when flashed via HBOOT. Is S-ON?
Try reflashing that RUU again.
If that doesn't work, try downloading and flashing another RUU. If all else fails, get the unrooted stock RUU. You might have to reroot but you will have a function device.
Damn. I really only trust stuff posted by Jcase, but all of his links are broken!!!
http://forum.xda-developers.com/showthread.php?p=13921164
http://forum.xda-developers.com/showthread.php?t=1082114
I have an idea what it is, my phone did this before after I walked in and out of a walk in freezer... Blah blah
Go into hboot and find the selection that says system info.or something along those lines and if it says touch panel - fail or something along those lines then it will.never boot up
Sent from my ADR6400L using XDA Premium App
I think thats ok!
TOUCH PANEL-ATMELC12_20aaT
OS Ver.-1.12.605.6
Dang well we know it's not a hardware failure
I would just try to.boot it.up after flashing a ruu and don't touch it for awhile and see if its just taking forever to boot
Sent from my ADR6400L using XDA Premium App
Well multiupload is back up! I will try some other RUUs
Any tips to charge the battery again though? I am fearful that I may have depleted it too far at this point, and plugging it in sends it into a boot loop!
The best thing is to do a battery pull and plug it in right after you put the battery in
It shouldn't boot up... But who knows I could be wrong
>--The Game--<
I have loaded multiple RUUs in an attempt to fix this...no luck
I followed the Jcase to return to stock for rooted users - I am now stuck with S-ON, but it does not boot still. Just the same old White HTC Screen.
It could be that it wasn't a CWR problem to begin with since you have loaded the stock RUU, replacing CWR with the stock recovery, and it still won't boot.
Try taking the battery out and pressing the power button for about 10 seconds. Then put the battery back in. Do not press the power button. Now plug in the wall (AC) charger. Let the battery fully charge, no bump charging required. then unplug the charger. Now press Vol - and the Power button. The phone should boot into the bootloader (If it doesn't, then its bricked). Select RECOVERY. Now let the stock recovery program run and reboot.
I hope that fixes it, but if it doesn't...
Well, it comes down to a question that you need to ask your self...
Do you continue down the path of trying to fix this device?
Or
Do you take it in to a vzw store (or call warranty dept.) since its still under warranty and get a replacement?
If you want to press on with trying to fix it (keep in mind that all your data is already gone) in the hope that this process will help someone later who might run into the same problem and is out of warranty, I can try to help. But outside of flashing the unroot stock RUU, there isn't a bunch more that I can think of.
Let us know what you want to do.
barcodelinux said:
It could be that it wasn't a CWR problem to begin with since you have loaded the stock RUU, replacing CWR with the stock recovery, and it still won't boot.
Click to expand...
Click to collapse
I agree. I kind of think that Rom Manager corrupted the file that it tried to install.
Try taking the battery out and pressing the power button for about 10 seconds. Then put the battery back in. Do not press the power button. Now plug in the wall (AC) charger. Let the battery fully charge, no bump charging required. then unplug the charger. Now press Vol - and the Power button. The phone should boot into the bootloader (If it doesn't, then its bricked). Select RECOVERY. Now let the stock recovery program run and reboot.
Click to expand...
Click to collapse
I will try this tonight. I think that my battery is dead at this point. I can get it to reset to HBOOT (S-ON). I can click recovery. The stock recovery opens, and then within 5 seconds the phone resets. From this point (until I pull the battery), it will boot loop to factory recovery. Is this due to a dead battery? Every time I plug in my phone to my wall AC Adapter, the phone actually turns on and boot loops. Because of this I have not been able recharge it.
I hope that fixes it, but if it doesn't...
Well, it comes down to a question that you need to ask your self...
Do you continue down the path of trying to fix this device?
Or
Do you take it in to a vzw store (or call warranty dept.) since its still under warranty and get a replacement?
If you want to press on with trying to fix it (keep in mind that all your data is already gone) in the hope that this process will help someone later who might run into the same problem and is out of warranty, I can try to help. But outside of flashing the unroot stock RUU, there isn't a bunch more that I can think of.
Let us know what you want to do.
Click to expand...
Click to collapse
I have a replacement in the mail at this point, but I am willing to experiment in the meantime so that anyone in the future can avoid my problems!
vypurr said:
I agree. I kind of think that Rom Manager corrupted the file that it tried to install.
Click to expand...
Click to collapse
You are not the first one to say that. While using a GUI front end to CWR is handy, it doesn't have a great track record.
I have gotten away from using Rom Manager for anything except flashing CWR.
But then again, I make it a habit to wipe /system, /data, and /cache before flashing a new ROM. You can't do that from Rom Manager.
Anyways, back to the topic...
The battery being in a low charge state wouldn't make the phone reboot (I wouldn't think). In the past when my battery has died, the phone never rebooted...it just turned off. However, I have never had the phone boot when I plugged up my wall charger either. (My old OG Droid used to do that and it pissed me off)
Has anyone else had this happen? If not, that might suggest a hardware malfunction of some sort too.
Was this phone dropped or does it have any kind of water damage?
At this point, I think it is a hardware failure of some sort. And chasing a hardware failure with a software fix is kind of a fruitless endeavor.
I know the phone has been babied its entire life (except for many many roms).
I remember that the phone used to turn on when CWR was first put onto the TB, but it should not do that stock, and it was cleared up with recent CWR updates.
I am just going to cut my losses and get the replacement that Verizon has offered me. Maybe I can have a couple more break and just get the Galaxy S2 when it lands!
Well I am not alone!!!
http://www.droid-life.com/2011/05/2...ght-want-to-consider-reverting-back-to-froyo/
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.
Hello i got a problem im not sure but i think i bricked my phone i dont really know how to expalin it either, well i want it to update it so i downloaded update from htc website for sprint but i think i had to download it for hero G2 with i found later so i installled it i had an error phone turned off now i cant do anything with it it wont turn on only vibrate 5 times? if i connect it with usb laptop wont see it i cant boot it or nothing but when i put it on charge it heats up? any ideas?
Sounds like a brick to me... Do you get any output on screen, what OS are you using on your PC, any response from it ?
nothing happens when i use usb cable and windows 7. Today when i was trying to turn my phone on again power on/off + home it vibrated 5 times?
Pull out your battery, plug it back in, hold POWER+VOL DOWN, and it sould take you to HBoot, if you cant do that then im very sorry and your phone is hard bricked...
i was wondering would that work?
How to flash stock ROM through SD-Card
*This only works with current stock ROM or newer version. Downgrading will fail till we have SuperCID. More about that in here!
1. Run the RUU and get the rom.zip from it. (Find it in here "c:\users\%usrename%\appdata\temp\")
2. Copy rom.zip to the SD-Card and rename it to PJ46IMG.zip
3. Put the SD-Card in the card reader.
4. Put the card reader onto the USB Y-Cable.
5. Plugin the USB Y-Cable to your One X.
6. Hold volume down and press the power button while keeping the volume down pressed. This will get you into HBOOT.
7. Wait a couple of seconds and you'll see that it finds PJ46IMG.zip
8. Follow the instructions on your screen =)
Barteko96 said:
i was wondering would that work?
How to flash stock ROM through SD-Card
*This only works with current stock ROM or newer version. Downgrading will fail till we have SuperCID. More about that in here!
1. Run the RUU and get the rom.zip from it. (Find it in here "c:\users\%usrename%\appdata\temp\")
2. Copy rom.zip to the SD-Card and rename it to PJ46IMG.zip
3. Put the SD-Card in the card reader.
4. Put the card reader onto the USB Y-Cable.
5. Plugin the USB Y-Cable to your One X.
6. Hold volume down and press the power button while keeping the volume down pressed. This will get you into HBOOT.
7. Wait a couple of seconds and you'll see that it finds PJ46IMG.zip
8. Follow the instructions on your screen =)
Click to expand...
Click to collapse
Biggest question is - can You go into fastboot mode? Because there is a way to flash Your phone is You can go into fast boot, and there should be a manual somewhere here, not using One X, but hero ;]
Let us know, does the phone respond by going into fastboot.
Additionaly : how did You downloaded firmware for sprint, as You should give IMEI number on HTC site.
brat.haneq said:
Biggest question is - can You go into fastboot mode? Because there is a way to flash Your phone is You can go into fast boot, and there should be a manual somewhere here, not using One X, but hero ;]
Let us know, does the phone respond by going into fastboot.
Additionaly : how did You downloaded firmware for sprint, as You should give IMEI number on HTC site.
Click to expand...
Click to collapse
i cant go in fastboot mode it only vibrates :/ and i went on to some forum and they had link to download it :x
Barteko96 said:
i cant go in fastboot mode it only vibrates :/ and i went on to some forum and they had link to download it :x
Click to expand...
Click to collapse
bricked