[Q] I may be bricked, and noticing a number of related posts - HTC EVO 3D

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.

Related

Is my phone bricked?! (grey battery screen)

Hi guys,
I figured I'll post again here since I think I bricked my phone.... I was trying to install Eugene's Vibrant6.zip and I got stuck on the Vibrant Logo with Samsung at the bottom. I tried to reset with both volume buttons and power button and got to grey battery and nothing else...
What I did prior to this was I formatted system and data on the recovery screen as per some posts here and it would just boot into a loop. Windows won't recognize a device and it just shows grey battery image and it doesn't seem to be charging. Anyone can help me?
EDIT:
Out and in the battery, plugged in to USB and it just loads the battery image and it's all grey color as if fully discharged and just stuck on it. Device is also not found in my system so I can't do any adb commands. If I just reset it without the cable it would just sit on the Samsung boot loop. Anything I can do?
UPDATE: Ok, some good news! I heard the sound as it connected via USB, I can see the 2 drives, but they read as Removable Disk and I can't access them...
adb reboot recovery or download
error: device not found
What if simply format the drives via Windows right click menu? Will that do any good or bad? What are my options here? Any help will be appreciated!
UPDATE: Well... looks like this is pretty much a dead phone.... I right clicked and selected Format in My Computer and it just says There is no disk in Driver F: Insert a disk and try again.
Can I a mount an image somehow via MagicISO? Or is there something simpler that I just can't figure out?
Again, thanks for your help!
Thanks.
Has anyone experienced this or am I the only one?
M5devil said:
Has anyone experienced this or am I the only one?
Click to expand...
Click to collapse
Sorry I have never heard of this or witnessed it while flashing anything to my device. Obviously the battery screen signifies that the phone is off but is in charging mode and hitting the power button will boot the device up. (I'm sure you already know of this). Never heard of it being stuck at that screen after flashing. Hopefully you can get this solved soon. Good luck
M5devil said:
Hi guys,
I figured I'll post again here since I think I bricked my phone.... I was trying to install Eugene's Vibrant6.zip and I got stuck on the Vibrant Logo with Samsung at the bottom. I tried to reset with both volume buttons and power button and got to grey battery and nothing else...
What I did prior to this was I formatted system and data on the recovery screen as per some posts here and it would just boot into a loop. Windows won't recognize a device and it just shows grey battery image and it doesn't seem to be charging. Anyone can help me?
EDIT:
Out and in the battery, plugged in to USB and it just loads the battery image and it's all grey color as if fully discharged and just stuck on it. Device is also not found in my system so I can't do any adb commands. If I just reset it without the cable it would just sit on the Samsung boot loop. Anything I can do?
UPDATE: Ok, some good news! I heard the sound as it connected via USB, I can see the 2 drives, but they read as Removable Disk and I can't access them...
adb reboot recovery or download
error: device not found
What if simply format the drives via Windows right click menu? Will that do any good or bad? What are my options here? Any help will be appreciated!
UPDATE: Well... looks like this is pretty much a dead phone.... I right clicked and selected Format in My Computer and it just says There is no disk in Driver F: Insert a disk and try again.
Can I a mount an image somehow via MagicISO? Or is there something simpler that I just can't figure out?
Again, thanks for your help!
Thanks.
Click to expand...
Click to collapse
Slow down for a second. Your phone is definitely not bricked. Ive been over the edge, and been able to bring my phone back to life.
To clarify, you flashed vibrant6.zip through clockwork mod, and then the phone got stuck on the samsung S? How long did you let it sit there?
It sounds like just your ROM is messed up.
Are you able to "get into recovery"? Holding both volume buttons while you power on the phone, without it being plugged into usb.
Do you have Odin? And have you ever used it?
Its totally frustrating when your phone gets messed up and you don't know what to do.
I flashed the stock ROM via Odin and then wanted to install Vibrant6.zip. For that I entered into a recovery mode via Clockwork and as someone in the other thread advised, I formatted system and also data, don't recall exactly. Then it looped to a standard recovery mode and I just rebooted the phone. This is where it got stuck... Vibrant in the center and Samsung at the bottom of the screen. To test it I left it like that from night till this morning. In the morning I woke up it was on the same boot screen.
Before that at night, after seeing it hand at the boot, I held both volume keys and power, waited for it to reboot, and immediately it showed a circular progress bar, but not moving just highlighted the 12 o'clock bar and second later I see the battery image all in gray and nothing else. It just sits on that grey static image without actually charging it (no green section or flashing dots)
Boot logo only appears if I am trying to reset without the USB cable. On the boot loop I plug in the cable and I hear the USB connecting it, I see the 2 Removable disks, but both inaccessible and adb commands don't recognize the device.
Very weird, as in turned off mode it's not charging at all.. just shows this grey battery image with a circle progress froze on 12 o'clock bar.
That's pretty much it.... I was never able to enter into recovery nor download via the buttons. It would just always reboot into this grey battery screen....
Completely helpless.... I did order a new battery from TMO, maybe the battery is fried and that's why it's not charging and just sits on this stupid static grey battery screen.
ArbitrageMan said:
It sounds like just your ROM is messed up.
Are you able to "get into recovery"? Holding both volume buttons while you power on the phone, without it being plugged into usb.
Do you have Odin? And have you ever used it?
Its totally frustrating when your phone gets messed up and you don't know what to do.
Click to expand...
Click to collapse
Holding both volume keys and releasing power once screen goes blank, only show Vibrant logo again... I have tried this a million times
With USB cable it shows grey battery screen, without the cable just a Vibrant boot loop...
I'm assuming that you have the Samsung drivers installed.
Try the following steps:
Take out the battery and then put it back in but don't turn the phone on.
Plug it via USB.. does anything show up on the screen?
zephiK said:
I'm assuming that you have the Samsung drivers installed.
Try the following steps:
Take out the battery and then put it back in but don't turn the phone on.
Plug it via USB.. does anything show up on the screen?
Click to expand...
Click to collapse
Yes, I have the drivers installed as I was able to locate my device and use adb commands to enter into recovery and download. Also Kies worked.
Doing what you asked simply load the grey battery image and nothing else with a progress bar not spinning. Just sort of hangs on this image and that's all.
Booting without the USB cable loads the Vibrant boot loop. Connecting USB at this boot loop state, would play a sound as if it connected to my windows, but I can only see Removable disks that are inaccessible and adb doesn't find the device...
Very strange.... trying to use the button keys to enter into recovery or download is no use, as that just won't ever happen, even when phone was working fine.
Any other suggestions? I would return the phone for replacement... but I am not sure how it would look with all the files still on the internal disk including root if I am not mistaken... I had only few hours of sleep because of this headache
M5devil said:
Yes, I have the drivers installed as I was able to locate my device and use adb commands to enter into recovery and download. Also Kies worked.
Doing what you asked simply load the grey battery image and nothing else with a progress bar not spinning. Just sort of hangs on this image and that's all.
Booting without the USB cable loads the Vibrant boot loop. Connecting USB at this boot loop state, would play a sound as if it connected to my windows, but I can only see Removable disks that are inaccessible and adb doesn't find the device...
Very strange.... trying to use the button keys to enter into recovery or download is no use, as that just won't ever happen, even when phone was working fine.
Any other suggestions? I would return the phone for replacement... but I am not sure how it would look with all the files still on the internal disk including root if I am not mistaken... I had only few hours of sleep because of this headache
Click to expand...
Click to collapse
Are you sure that you're doing the right things to get to download? I've been in this situation and I wasn't able to get into recovery but I was able to get back into download mode.
I believe if you return it back and they find out it was rooted, they will charge you for it. If not, it'll appear on your bill.
I'm sure that you're doing the wrong things to get into download mode. If something is appearing on your screen it is a soft-brick and you're not bricked.
1. Take out battery, put it back in. (to turn the phone fully off)
2. Don't turn it the phone on!
3. Plug the phone into your PC, do not hit the power button!
4. See if the phone shows anything on the screen (powers on its own when plugged in)
IF the phone screen does 'turn on' after being plugged in without you hitting the power button, so far so good.
5. Now while it's on like this, hold the volume up and volume down buttons.
6. Hold the power button as well as the volume buttons until the screen goes black.
7. As soon as the screen goes black, let go of the power button! But DON'T let go of the volume buttons!
Click to expand...
Click to collapse
A tip to get into download mode is to put the phone HORIZONTALLY (sideways) and it will make it a lot easier.
I am pretty much positive about it. I know a lot of people can easily enter into recovery or download modes, but I know many can't and I am one of them. It would just load the grey battery image instantly as I let go of the power button.
1. Take out battery, put it back in. (to turn the phone fully off) DONE
2. Don't turn it the phone on! DONE
3. Plug the phone into your PC, do not hit the power button! DONE
4. See if the phone shows anything on the screen (powers on its own when plugged in) FIRST THING THAT APPEARS IS A CIRCULAR PROGRESS BAR THAT CHANGES TO A GREY BATTERY IMAGE WITH A BAR IN THE MIDDLE OF IT. STATIC IMAGE, NOTHING ELSE.
IF the phone screen does 'turn on' after being plugged in without you hitting the power button, so far so good.
5. Now while it's on like this, hold the volume up and volume down buttons. DONE
6. Hold the power button as well as the volume buttons until the screen goes black. DONE
7. As soon as the screen goes black, let go of the power button! But DON'T let go of the volume buttons! DONE
THE STUPID GREY COLOR BATTERY IMAGE APPEARS AS BEFORE....
I'm thinking maybe battery is fried and that's why the grey color screen appears and not the usual screen where you see the battery charging...
After reading this thread it's clear that my handset is one of the new ones that have recovery/download modes disabled via the volume+power buttons.
So that pretty much covers it... I hope TMO will not ***** about the files that are on the internal sd that I am unable to access and remove... unless anyone else has any fresh ideals how to gain access to the disk
I think I might have a similar problem.
I accidentally deleted the touchwiz framework so I can't do anything ON the phone. It boots up, and gets me to the lock screen. As soon as I unlock, I am greeted with dozens of unending force closes.
I can get into both download and recovery mode, however, I have not been able to get ADB to recognize the device. I am attempting to push the stock ROM to the internal memory to flash over everything.
I'm not sure what to do to get ADB to work but it's driving me nuts!
Stuck at vibrant? I have a fix
Check out android Dev Section... I figured out how to access download mode or stock recovery mode when you are stuck at the vibrant screen!!!! BACK IN BUSINESS VIBRANT OWNERS!!!
i got the same problem and nothing seems to work
Try this out http://forum.xda-developers.com/showthread.php?t=1103706
Feels like I'm having same issues..
the previous post requires opening the phone and I don't have tools for that..
Here's my issue.
I can't get into Recovery or Download and computer won't see phone to Odin.
I've got drivers installed and AIO Toolbox as well as ADB(which won't work because of computer not seeing phone.
Using the manual option(vol+ vol- power), nothing works.
I've done all the tricks like unplug it then hold vol keys plug it insert battery..
When I do plug in the phone to to even just get a charge in it goes the the battery, but my is is frozen or something. doesn't turn green or have a charging animation. After about a minute or so it was start up and boot loop. I read something about a bad battery? I've got two of them and they seemed fine before..
Before all this I had to Odin and go to stock. I was attempting to get ics back but I was being lazy and trying to do as little as possible..bad idea. I was following slim ics install and flashed cm9 daily, slimics and commons..and now this..
I'm not sure what to do..I usually search around xda or google..10 hours later.. idk..Anyone able to give help please?
:crying:
eduardo_reflex said:
i got the same problem and nothing seems to work
Click to expand...
Click to collapse
... do i even have to say it?
droyd666 said:
Try this out http://forum.xda-developers.com/showthread.php?t=1103706
Click to expand...
Click to collapse
this problem is most likely solved. After 2 years!
mylostlonelysoul said:
Feels like I'm having same issues..
the previous post requires opening the phone and I don't have tools for that..
Here's my issue.
I can't get into Recovery or Download and computer won't see phone to Odin.
I've got drivers installed and AIO Toolbox as well as ADB(which won't work because of computer not seeing phone.
Using the manual option(vol+ vol- power), nothing works.
I've done all the tricks like unplug it then hold vol keys plug it insert battery..
When I do plug in the phone to to even just get a charge in it goes the the battery, but my is is frozen or something. doesn't turn green or have a charging animation. After about a minute or so it was start up and boot loop. I read something about a bad battery? I've got two of them and they seemed fine before..
Before all this I had to Odin and go to stock. I was attempting to get ics back but I was being lazy and trying to do as little as possible..bad idea. I was following slim ics install and flashed cm9 daily, slimics and commons..and now this..
I'm not sure what to do..I usually search around xda or google..10 hours later.. idk..Anyone able to give help please?
:crying:
Click to expand...
Click to collapse
Try asking another question. But I suggest using a USB jig. They usually work. Then odin
Sent from Mount Olympus via Hermes
Did you ever get it fixed man? I literally did the very same to mine a while back and It works like butter as we speak. It is fixable with a mini-usb jig or dongle. You can make your own with about $3 worth of parts from radio shack but I recommend buying one, it will be easier. I for the record made mine simply twisting together the resistors and though it was tough to touch the right pins it did eventually work and get me back into download mode.
Hopefully you already got it fixed though. If not I can help you out.

[Q]stuck at splash screen and wont go into bootloader

So I just used Bootmanager for the first time. I was having alot of issues so I rebooted and now it sits at the splash screen and it isn't going into the bootloader. Kind of freaked out.
What do I do to fix this?
Thanks.
are you s-on or s-off?
I'm S-off on 1.49
edit: sorry, I meant 1.40
If u can get to recovery, go to install zip and find the boot manager folder, look in there for a phone Rom folder, their will be an update.zip, flash it and reboot.
I can't get to the recovery. It wont even boot to the spash screen unless it's plugged in.
Pull the battery, put it back in, hold vol down and power, what happens?
Well if it's unplugged it wont do anything. But, if it's plugged in, it goes to the splash screen.
Plugged into what, ac power or USB to comp? Try taking out the sd card and then try vol down and power.
Either the usb to computer or AC. It does it for both.
Took out the sd, no change.
I haven't seen a prob like this, without hboot you'd never see the splash screen, it has to be there. Maybe leave the battery out for a few minutes then try holding vol down+power. If you can get to hboot then you're good but with no hboot your not so good.
Hmm, so my red charging led is blinking now while the phone is off, wasn't doing that before, any idea on what that means?
I know that when I drain my battery all the way till it shuts off, it won't charge and I get the blinking red led. I have to put in a spare battery and let the other sit for a few hours befor it'll charge.
What's it do when u just press power? Just goes to the white HTC screen and stays?
Yeah it does that, I'm wondering if there is something wrong with my vol down.
Does it feel like it "clicks"? Take the case off and try to press vol down+power.
edit..Lol, just tried it without the case and its not as easy as I thought.
It does click, I tried it without the case, it was working earlier today though. The last time I had it on, I was rebooting into recovery and the screen went black and just sat there, so I did a battery bull and that is where I am now, Would something have happened if I did a battery pull in that state?
I wouldn't think so... I've had to pull it in situations like that, generally you just don't want to pull the battery during an ruu update or a pg86img update, when its writing to certain partitions. What recovery are you using and what Rom did you try to flash with boot manager?
I'm using TWRP 2.0 and my phones rom was on mean rom. I put ics playground on slot 1 and was having alot of issues getting the phone to wake up and random freezes and crashes. I attempted to boot back to my phones rom but it wasn't doing it. So I attempted to flash Chads AnthaX ICS playground kernel and bootmanager crashed. so I decided I would just boot into recovery and do flash the update zip for bootmanager.
That is everything I did
brenstar said:
It does click, I tried it without the case, it was working earlier today though. The last time I had it on, I was rebooting into recovery and the screen went black and just sat there, so I did a battery bull and that is where I am now, Would something have happened if I did a battery pull in that state?
Click to expand...
Click to collapse
It just sounds like something weird happened to your recovery partition. If you pull out the battery and put it back in, then plug a usb cable into your computer. Do not turn it on. Run the command "adb reboot bootloader" (from your computer). that should turn on the phone and put it into the bootloader. From there, redownload your custom recovery of choice to your computer. Make sure you have a .img file. Type in "fastboot flash recovery [NAMEOFRECOVERYIMAGE].img". Now run your custom recovery and restore the update.zip for your ROM.
~co~
I'd be very surprised if your phone is broken. Sounds like an easy fix and I wish I could help more. You really can't do anything without getting to the hboot screen. No ruu, no turning s-on to re downgrade, no loading a recovery from fastboot.... I'm trying to think, maybe somebody else will jump in here and teach both of us somethin.
I know that a couple of other ppl had prob with a certain release of playground and twistedumbrella fixed them right up. Maybe you could hit him up. He's way more pro than I am.

Need Help!

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.

Apparent Bricked SGS2!

I've just spent many hours trying to revive my AT&T I777 phone that was running CM9 until I tried to flash it back to bone stock GB, then ICS.
First, I used ODIN to flash the standard default UCKH7 Gingerbread ROM from Sammy via One-Click "I777_UCKH7_OCD_No_BL.7z". After performing the ODIN, the phone flashed successfully and rebooted into a boot loop "Rethink Possible".
I searched for hours to find a solution, but one solution lead to another problem, and so on...
Currently:
- I cannot get into recovery mode, but it boots reliably into download mode. Tried the 3 button tango in EVERY way, but it will only go into DL mode.
- I've tried many different ODIN flashable images per recommendation in this forum, even the one that contains all of the extra files (recommended by creepyncrawly). All flashed fine, but none fixed the boot loop issue.
- Most recommendations say to "wipe/factory reset" to fix the bootloop issue, but I can't do that since I can't get into recovery.
- Tried to do ADB REBOOT RECOVERY, but can't get the driver to connect and list the device. The install guide says to enter "debug mode", but I can't even boot the phone.
- Tried Kies and the phone was not recognized in either DL mode or boot loop. Was hopeful Kies could reinstate the firmware.
I have a physically PERFECT SGS2 I want to sell, and unless I can fix this boot issue, it's nothing but a brick now. Any advice is much appreciated! Pulling my hair out so far...
tone_la said:
I've just spent many hours trying to revive my AT&T I777 phone that was running CM9 until I tried to flash it back to bone stock GB, then ICS.
First, I used ODIN to flash the standard default UCKH7 Gingerbread ROM from Sammy via One-Click "I777_UCKH7_OCD_No_BL.7z". After performing the ODIN, the phone flashed successfully and rebooted into a boot loop "Rethink Possible".
I searched for hours to find a solution, but one solution lead to another problem, and so on...
Currently:
- I cannot get into recovery mode, but it boots reliably into download mode. Tried the 3 button tango in EVERY way, but it will only go into DL mode.
- I've tried many different ODIN flashable images per recommendation in this forum, even the one that contains all of the extra files (recommended by creepyncrawly). All flashed fine, but none fixed the boot loop issue.
- Most recommendations say to "wipe/factory reset" to fix the bootloop issue, but I can't do that since I can't get into recovery.
- Tried to do ADB REBOOT RECOVERY, but can't get the driver to connect and list the device. The install guide says to enter "debug mode", but I can't even boot the phone.
I have a physically PERFECT SGS2 I want to sell, and unless I can fix this boot issue, it's nothing but a brick now. Any advice is much appreciated! Pulling my hair out so far...
Click to expand...
Click to collapse
From powered off, how long are you holding power and vol+ and vol- to get into recovery? On both mine and my wife's phones, I have to hold all three down until the second time the Sammy logo flashes up on the screen. Most people seem to get it after the first time, but I've heard of a few others like mine...
Sent from my SGH-I777 using Tapatalk 2
dandrumheller said:
From powered off, how long are you holding power and vol+ and vol- to get into recovery? On both mine and my wife's phones, I have to hold all three down until the second time the Sammy logo flashes up on the screen. Most people seem to get it after the first time, but I've heard of a few others like mine...
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
When I hold down the 3 buttons, it never actually shows the Sammy logo. It takes about 8-12 seconds and shows the Download prompt that says "press volume up" to continue to enter DL mode; "press volume down" to cancel/restart. Both of these work fine. If I ignore the prompt and continue holding the 3 buttons, it never does anything else. Thanks for your post.
tone_la said:
When I hold down the 3 buttons, it never actually shows the Sammy logo. It takes about 8-12 seconds and shows the Download prompt that says "press volume up" to continue to enter DL mode; "press volume down" to cancel/restart. Both of these work fine. If I ignore the prompt and continue holding the 3 buttons, it never does anything else. Thanks for your post.
Click to expand...
Click to collapse
Unplug the USB when you do that
Sent from my Galaxy Nexus
Stop using brick. It turns on it is not a brick
Sent from my GS4 running CM11 Kandy Kane
Pirateghost said:
Unplug the USB when you do that
Click to expand...
Click to collapse
It does the same thing whether the USB cable is plugged in or not. However, you gave me an idea...
This phone has been sitting in the drawer for a few months since I got my GNex. When I charged it up, after unplugging the charger the icon stayed with a "plug" symbol on the notify bar as if it was still connected to the charger.
Is it possible the phone is stuck thinking there's a cable plugged in and that's why I can't 3-button boot to recovery? Seems like I've read about other people having connector issues. Does this sound plausible? And if so, what's the best remedy?
tone_la said:
It does the same thing whether the USB cable is plugged in or not. However, you gave me an idea...
This phone has been sitting in the drawer for a few months since I got my GNex. When I charged it up, after unplugging the charger the icon stayed with a "plug" symbol on the notify bar as if it was still connected to the charger.
Is it possible the phone is stuck thinking there's a cable plugged in and that's why I can't 3-button boot to recovery? Seems like I've read about other people having connector issues. Does this sound plausible? And if so, what's the best remedy?
Click to expand...
Click to collapse
A simple Google search is the best remedy. This is one of the most asked questions on this forum.
tone_la said:
It does the same thing whether the USB cable is plugged in or not. However, you gave me an idea...
This phone has been sitting in the drawer for a few months since I got my GNex. When I charged it up, after unplugging the charger the icon stayed with a "plug" symbol on the notify bar as if it was still connected to the charger.
Is it possible the phone is stuck thinking there's a cable plugged in and that's why I can't 3-button boot to recovery? Seems like I've read about other people having connector issues. Does this sound plausible? And if so, what's the best remedy?
Click to expand...
Click to collapse
Could be...Sounds like a symptom of bad or dirty usb port. Try cleaning gently with tooth brush and rubbing alcohol. Dry with canned air if you have some.
Sent from my SGH-I777 using Tapatalk 2
Phalanx7621 said:
A simple Google search is the best remedy. This is one of the most asked questions on this forum.
Click to expand...
Click to collapse
I've tried very hard to not "waste" anyone's time by doing my research, searching, and thinking; BEFORE posting. My question above is not so much "how" to clean the port, but "does this symptom I'm experiencing sound like a 'bad port' issue?". Believe me, I've done tons of searching to try to solve this problem before posting so that I can be worthy of receiving assistance.
And to the guy who says, "don't use the term brick". Sorry I said "Apparent brick"; just looking for some neighborly help to get my phone working again. At any rate, I very much appreciate any advice to help me get this fixed.
Trying hard to keep the forum clean and think for myself when possible!
dandrumheller said:
Could be...Sounds like a symptom of bad or dirty usb port. Try cleaning gently with tooth brush and rubbing alcohol. Dry with canned air if you have some.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Thanks so much for this post, I will do this and post again with the results. Much appreciated!
tone_la said:
Thanks so much for this post, I will do this and post again with the results. Much appreciated!
Click to expand...
Click to collapse
I should elaborate a little for safety's sake - probably a no brainer, but in case - TAKE YOUR BATTERY OUT BEFORE CLEANING THE PORT. Don't know if it matters or not, but I wouldn't want you to short stuff during cleaning - rubbing alcohol IS part water.
Adb wait-for-device reboot recovery
Plug in your phone and let it attempt to boot. If you need adb, use the link in my signature for adb portable. It includes batch files to reboot to download or recovery modes.
This issues the reboot command if at any point in the boot process your phone is detected.
You might want to install the android sdk and ensure you have the nexus drivers installed.
Sent from my SGH-I777 using xda premium
Red_81 said:
Adb wait-for-device reboot recovery
Plug in your phone and let it attempt to boot. If you need adb, use the link in my signature for adb portable. It includes batch files to reboot to download or recovery modes.
This issues the reboot command if at any point in the boot process your phone is detected.
You might want to install the android sdk and ensure you have the nexus drivers installed.
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Well, I cleaned the heck out of the USB port with rubbing alcohol and a toothbrush, followed by a thorough drying with compressed air. Yes, battery removed during the process; thanks for that! Unfortunately, same exact symptom. Only goes into DL mode and boot loop.
I'll now try your portable adb suggestion and see if I can get a connection.
Does anyone else have any thoughts on what may have gone wrong and/or anything I can flash via ODIN to fix the issue? Many thanks!
Installed your portable adb and followed your instructions. Ran the recovery_mode batch file and adb initialized (daemon not running, starting daemon...) followed by red text "Waiting for your device to be detected". I already installed the Android SDK yesterday and the following modules are installed: Android SDK Tools, Android SDK Platform-tools, and Google USB Driver
Powered on the phone and after a few seconds the "Rethink Possible" logo showed up and shortly thereafter, I heard the computer beep indicating it connected with the phone. Win7 device manager shows "SAMSUNG Mobile USB Modem" under the Modems category.
However, the portable ADB continues to show "Waiting for your device to be detected" and the boot loop continues. Did the same thing in DL mode, same result.
I reinstalled the Samsung I777 driver from Samsung's site. Going to reboot my PC now to see if that makes a difference.
Reboot did not help. Seems like the phone is not being identified as "Android Composite ADB Interface", and therefore ADB cannot see the phone. I've looked for other drivers, but no matter what I've tried, the SGS2 I777 shows as "SAMSUNG Mobile USB Modem" under the Modems category in Win7 Device Manger.
Any advice on ADB here? Doing the best I can, but keep running into stops. Thank you
tone_la said:
Reboot did not help. Seems like the phone is not being identified as "Android Composite ADB Interface", and therefore ADB cannot see the phone. I've looked for other drivers, but no matter what I've tried, the SGS2 I777 shows as "SAMSUNG Mobile USB Modem" under the Modems category in Win7 Device Manger.
Any advice on ADB here? Doing the best I can, but keep running into stops. Thank you
Click to expand...
Click to collapse
Try in Linux? Make yourself an ubuntu live CD and go from there? As long as you have the most current drivers, it should work in Win - unless the problem is a totally hosed USB port??
Tried these? http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-II-i777-USB-Driver-for-AT-T.shtml
dandrumheller said:
Try in Linux? Make yourself an ubuntu live CD and go from there? As long as you have the most current drivers, it should work in Win - unless the problem is a totally hosed USB port??
Click to expand...
Click to collapse
Why would it work better in Linux? I'm willing to try this, but fairly unfamiliar with Linux.
Phalanx7621 said:
Tried these? http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-II-i777-USB-Driver-for-AT-T.shtml
Click to expand...
Click to collapse
I used the Samsung drivers. Kinda leary of these drivers from softpedia. They download as SETUP.EXE and seem like inauthentic/spyware.
After many many hours of frustration and dead ends, I've finally recovered my phone! YAYYYYY!!!!!
Here's how I got it done...
- No matter what I flashed, I kept getting the boot loop. This was really throwing me for a "loop" when I thought I was flashing standard original Sammy full ROM with ODIN; yet that wasn't enough to recover the phone.
- Something was missing with the boot process, so I started looking for CWM that I could flash via ODIN. Most sites had the zip CWM file, but only a few had the TAR file. Finding a valid file proved more difficult than I thought with all the download sites that went offline for legal reasons. But I did find one!
http://www.mediafire.com/?bjhx33o4viz8tza
The above link is for file name: SGH-I777_ClockworkMod-Recovery_5.0.2.3.tar
- Once I installed the above via ODIN, all of a sudden ADB recognized the phone and I was able to run: ADB REBOOT RECOVERY
It's very possible that the 3-button recovery may have worked too, but when I saw the device show up on ADB, I didn't want to take the chance.
- The device then rebooted and entered RECOVERY mode! FINALLY!!!!
- I then did a factory reset / wipe and rebooted the phone. It came up just fine, NO MORE BOOT LOOP!
Thanks to those who replied to this thread. The responses helped me think hard about what was going wrong and ultimately I dug up a solution.

[Q] Black screen, no lights, no sounds, but usb detects = hard brick? :(

Hey guys,
As of 1 hour ago, I'm a sad panda. I think i hard-bricked my Jewel. While flashing the the 3.17.651.4 "Full" Firmware zip from here.
Battery was low, so i plugged it into USB while flashing. After it rebooted, screen wouldn't come back on (maybe a driver glitch, it happens sometimes and all is fine), so I unplugged it and tried pressing the power button to reboot it. It probably went into bootloader mode, found the IMG zip and started flashing it. I plugged it back in, nothing. Now cannot get any response out of it. Once the battery dies, maybe it will happily come back to life and all will be okay, but maybe it won't.
I've been flashing for years and have soft-bricked many times and been able to ADB my way out of it, but this time is different. Symptoms are:
- Screen is black, no lights no sounds.
- Phone will not turn off after holding pwr button for 30+ secs
- The only way i know that it's on is when I plug it into my desktop, i hear the usb connection sound. (Win 8.1 x64 with driver signing disabled)
- Device manager does not show any new device, no ADB or Android or HTC Phone.
- Phone will probably run out of battery in a couple hours it was around 5% to begin with
I'm on Hboot 2.09.2222 (DirtyRacun S-OFF) Firmware was 1.12.something. Was happily running CM10.2 and Clockworkmod 6.0.4.8.
anything I should try?
thanks a lot,
Leon
I don't know that CWM was ever fixed to work properly on this device, which means that, combined with trying to flash firmware with a low battery could be bad news.
Leave it on a charger all day, and then come back to it and see if it turns on.
leeoniya said:
Hey guys,
As of 1 hour ago, I'm a sad panda. I think i hard-bricked my Jewel. While flashing the the 3.17.651.4 "Full" Firmware zip from here.
Battery was low, so i plugged it into USB while flashing. After it rebooted, screen wouldn't come back on (maybe a driver glitch, it happens sometimes and all is fine), so I unplugged it and tried pressing the power button to reboot it. It probably went into bootloader mode, found the IMG zip and started flashing it. I plugged it back in, nothing. Now cannot get any response out of it. Once the battery dies, maybe it will happily come back to life and all will be okay, but maybe it won't.
I've been flashing for years and have soft-bricked many times and been able to ADB my way out of it, but this time is different. Symptoms are:
- Screen is black, no lights no sounds.
- Phone will not turn off after holding pwr button for 30+ secs
- The only way i know that it's on is when I plug it into my desktop, i hear the usb connection sound. (Win 8.1 x64 with driver signing disabled)
- Device manager does not show any new device, no ADB or Android or HTC Phone.
- Phone will probably run out of battery in a couple hours it was around 5% to begin with
I'm on Hboot 2.09.2222 (DirtyRacun S-OFF) Firmware was 1.12.something. Was happily running CM10.2 and Clockworkmod 6.0.4.8.
anything I should try?
thanks a lot,
Leon
Click to expand...
Click to collapse
Did you ever get this working? I've got the same symptoms with my phone. Appears to be off and wont turn on but when plugged into the pc, the pc detects it.

Categories

Resources