Hi,
I tried downgrading from HC to GB because I wanted to install the official Update from this Thread.
But then the Flyer was stuck in Bootloop (white HTC Logo).
Fastboot was working anyway, and it displays:
-Revolutionary-
FLYER PVT SHIP S-OFF RL
HBOOT-6.11.1111
MICROP-0950
RADIO-3822.10.08.07_M
...
Now I wanted to go to fastboot, but the Flyer turned off immediately. When I plugged the Charging Cable in, the LED starts to blink. I've read several Threads about similar Problems, but I'm not sure what I have to do now. Wait until the Battery is empty, or let the Charger plugged in for several hours?
Can the Flyer be rescued?
What file did you use for the dd command?
Did it boot to fastboot/bootloader then power off immediately, or just never power on?
Start off by trying to charge it for a few hours.
I was unfortunately using the Guide "Revert from HC with HTC Unlock to GB - After any upgrade method..." and overlooked the red Warning (it was late...).
After running RUU the Bootloop appears.
Fastboot/bootloader was working (until the Battery was empty).
I'm trying to charge it over night.
Should I do this as the next step?
Thank you.
yes, if your hboot version is still 6.11.1111 you should do that next if you can get enough charge into the flyer to flash them.
Where are you located? ( what country )
In Germany.
Here I am back again. Charging and flashing the two files was successful, and now I'm trying to follow the steps from your advice. But I'm not sure whats the correct RUU for me. The CID of the Flyer is HTC__E11.
Do I have to use RUU_Flyer_HTC_WWE_2.23.405.3_R_Radio_20.3504.30.089BU_3809.07.04.06_M_release_204108_signed or RUU_Flyer_HC_S_HTC_WWE_3.55.405.1_Radio_20.4801.30.0822U_3822.10.08.07_M_release_226690_signed (because my Radio is Version 3822.10.08.07)?
I tend to the first one, the Gingerbread RUU?
Regardless of the Version: when I try to boot into recovery, I get the same error as jcrouzzo - I'm stuck at the HTC Screen...
Yes, of course you do. You don't have a complete ROM. If you set up a teamviewer session I'll help you out. It will only take 20-30 minutes to fix everything.
You want this RUU:
RUU_Flyer_HTC_WWE_2.23.405.3_R_Radio_20.3504.30.08 9BU_3809.07.04.06_M_release_204108_signed
Hey I have a similar issue. I tried to revert to S-off GB using the 3rd post from http://forum.xda-developers.com/showthread.php?t=1358758
I flashed PG41IMG-WIFI.zip using fastboot. The file did not have an android-info.txt so I copied one from another file. It flashed fine. I didn't know what rom's I could flash having an s-off "incomplete" on my flyer so I downloaded leedroids latest GB. I held vol up and power to get to bootloader this morning. I let it sit there while I turned back to my computer.
When I turned back to my flyer a few minutes later, the screen had gone dark. I tried the power button, holding power for a minute, holding vol up and power.
The amber/orange light keeps blinking. Holding the power button causes a fast blink, no light for 5 seconds, then it starts blinking again. It just keeps blinking when it's plugged in.
ADB and fastboot don't detect anything. I thought I had a full battery last night.
Any ideas are appreciated. In summary, it powered to bootloader successfully then went to "sleep".
EDIT: False alarm. It started working (for a little bit) after 2 hours of charging. I guess it charges a lot slower without a proper rom
hlp meeeeeeeeeeeeeeeeeee
i have same problum but i read this thread v v v late my phone is now not switch on due to charging pz help me
Related
After my battery was empty i had to restart my Hero and now it's stuck in HBOOT
I tried already almost everything. I can't go to recovery, only to clearstorage.
I've connected my phone and tried many ways to boot in recovery but my computer doesn't recognize my phone(error: device not found).
When I'm in HBOOT i have two options, simlock and fastboot.
If i press back for fastboot nothing happens, and if i press send for simlock it says open file fail, Reboot device?
Some extra informaton
HERO CVT SHIP S-ON
HBOOT-1.76.0004 (HERO10000)
MICROP-010f
TOUCH PANEL-SYN0104
RADIO-6.35.08.22
Jul 3 2009, 15:22:21
HBOOT
Anyone who has any idea?
Have you tried rebooting in recovery to see if that works?
Can't seem to get into recovery... It just always comes back to hboot( or clearstorage), no matter what combination of buttons i try
i have the exact same problem, i am in need of a solution as well
Someon who can help us?
simonflore said:
After my battery was empty i had to restart my Hero and now it's stuck in HBOOT
I tried already almost everything. I can't go to recovery, only to clearstorage.
I've connected my phone and tried many ways to boot in recovery but my computer doesn't recognize my phone(error: device not found).
When I'm in HBOOT i have two options, simlock and fastboot.
If i press back for fastboot nothing happens, and if i press send for simlock it says open file fail, Reboot device?
Some extra informaton
HERO CVT SHIP S-ON
HBOOT-1.76.0004 (HERO10000)
MICROP-010f
TOUCH PANEL-SYN0104
RADIO-6.35.08.22
Jul 3 2009, 15:22:21
HBOOT
Anyone who has any idea?
Click to expand...
Click to collapse
Did you install any other ROM aside from the official ROM code?
I installed the Modaco Rom 2 weeks ago, and it worked fine all the time
Damn, I'll guess it's bricked if nobody knows the answer...
Strange, without doing anything...
have you tried booting/flashin the recovery image from fastboot mode?
simonflore said:
Damn, I'll guess it's bricked if nobody knows the answer...
Strange, without doing anything...
Click to expand...
Click to collapse
I guess I also had a similar issue this morning when I was trying to root my phone and it was stuck at 41% while updating ROM. I just did it again after plugging out the USB Cable and running the Ruu.exe and it updated the ROM within 5 mins. I guess in my case it was a case of my Windows getting hung (I was running it within Mac using Parallels), and it just worked after inserting the USB cable again.
Try running the update from another computer (after installing HTC Sync on that ..)
Good luck!
Hi guys, I have exactly the same problem.
One night the volume button would not work. So i rebooted to fix the problem. It rebooted into HBOOT. The screen with the 3 skateboards?
I only get two options
<Back> Fastboot Mode
The back button does not trigger fastboot!!
<Send> Simlock
Doing this only says
FAT32 Init Ok
Open File Fail
Reboot Device?
<Menu> Reset Device
I do so but it reboots directly into hboot again.
It also does a SD card check when it boots up onto this screen, says something like
herodiag.zip
etc etc
and it says not found i think, it goes very fast.
Anyway I am very frustrated. I was using Modacos 3.0. Without many problems.
I have a bad feeling that my phone is bricked.
Any help would be much appreciated.
And yes I have already tried countless combinations of button presses, all still go back to the skateboard screen.
dwarfhero said:
One night the volume button would not work. So i rebooted to fix the problem. It rebooted into HBOOT.
Click to expand...
Click to collapse
this may sound like a silly comment, but to me it sounds like your VOlume Down button is stuck.
anyone else with a perfectly working hero can try this.
no matter what combination of buttons you press, if you have volume down pressed, it goes into hboot (or it seems to on mine, anyway)
O ok, any idea how I can sort of unstick it?
Seems like a good explanation.
on my cdma hero, following the directions i found online everywhere(hold home and boot) i was getting a HBOOT screen with only an option to erase all settings until i:
1. pop battery
2. reboot while holding vol-down, back arrow and power button
3. this time at the HBOOT screen there is an option to enter recovery mode(i think with a home press) fastboot or simlock
moisture in your HTC hero
It's possible that your 'volume down'-button is stuck because of moisture in you hero. I had the same problem. You have to warm your hero with warm air. CAUTION, make your hero NOT TOO HOT.
Hello!
My friend's Flyer 3G has some kind of problem, and I can't go through it.
I would like to install the original GB RUU, but I can't get to the recovery. I put the flyer onto the PC then happens nothing. Just the flashing orange led at the power button.
How can I recover this problem? I need your help guys!
What did you do to get here
Sent from my HTC Flyer P510e using xda premium
What is the battery level? I foolishly started my rooting with only 15% battery and needless to say I had to stop halfway through and charge it on the wall charger.
same problem with me, please help
solved
i found the guide here
now my flyer can turn on...
proceed to the next step
Flyer Now With Stock Shipped ROM (Solved)
jendar_hoppus said:
i found the guide here
now my flyer can turn on...
proceed to the next step
Click to expand...
Click to collapse
download the correct RUU here
- go to fastboot,
- connect the fyer to PC
- at the command line is typed fastboot oem lock
if the top line menu fastboot *** RELOCKED ***
without leaving the menu fastboot start installing the Correct RUU
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.
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.
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.