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.
Related
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.
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.
My Amaze has been off for about a week or two and now it wont even power on.
If I press and hold the power button I get no indication that it is doing anything. However, if I press the buttons on the bottom of the screen I get a slight vibration indication that it is indeed getting power to it. Tried booting into recovery with no luck.
Any thoughts?
What recovery are you using? I know most recoveries don't support charging while off. I suggest 4EXT but you will need to charge the battery externally first in order to flash it. Good luck.
do you have an external battery charger to charge the battery out of the phone?
did you try to charge the battery ?
Here's an interesting update.
Was able to plug it in USB and using ADB restart into recovery. From recovery I hit restart and the phone booted up like normal.
BUT, about 5-10 seconds in Android it reboots again back to the black screen with the vibrating buttons. Had to run back to work so I wasn't able to play around with it anymore than that.
BiznessMan said:
Here's an interesting update.
Was able to plug it in USB and using ADB restart into recovery. From recovery I hit restart and the phone booted up like normal.
BUT, about 5-10 seconds in Android it reboots again back to the black screen with the vibrating buttons. Had to run back to work so I wasn't able to play around with it anymore than that.
Click to expand...
Click to collapse
if your running a custom rom maybe it got corrupted somehow, happens to my phone often due to the fact im trying to find a way around to cloning one rom to another phone, try to reset your phone back to stock by flashing a ruu stock rom or a different rom, flash 4EXT and wipe everything from the phone (including sd card) don't forget to check and realign the partitions and then toggle usb mode and put the rom on the sdcard and flash it , hope that helps
Ninjistix said:
if your running a custom rom maybe it got corrupted somehow, happens to my phone often due to the fact im trying to find a way around to cloning one rom to another phone, try to reset your phone back to stock by flashing a ruu stock rom or a different rom, flash 4EXT and wipe everything from the phone (including sd card) don't forget to check and realign the partitions and then toggle usb mode and put the rom on the sdcard and flash it , hope that helps
Click to expand...
Click to collapse
Thanks for the reply but I can't even get it to recognize via USB anymore
Buttons still vibrate, screen is still black. I can't get anything to work on it
BiznessMan said:
Thanks for the reply but I can't even get it to recognize via USB anymore
Buttons still vibrate, screen is still black. I can't get anything to work on it
Click to expand...
Click to collapse
Battery pull, hold volume down(or is it up? I work on too many android phones..) and power button and it should boot into bootloader. From there reboot into recovery. Flash a custom rom of your choice after doing a full wipe. Problem should be solved unless there is a hardware issue, at which point it must have been dropped, battery issue, etc..
What it really seems like is your battery doesn't have enough juice to sustain power, (I get bootloops when my battery goes really low and I try turning it on). Just let it charge a bit and if the battery isn't holding its charge, then time for a new battery
Sent from my Amaze using xda app-developers app