hello all,
I am new here and I have been searching the forums for a few days as well as the internet but I could not seem to find one that had my same problem, but if there is can you please direct me to it and apologies for that.
I was installing a new rom, the Blackout ICS Incredible v3.0.0 FULLY WORKING!!! [4.0.4][Sense 3.6], onto my inspire i did a full wipe using FULL_WIPE_1.5_EXT4_.zip and I cleared the caches. the install i thought went well because it went to 100% and i even chose what kind of background i could as well as choosing to over clock my processor. The phone the restarted after all of that and it went to the htc screen then faded to black, after about ten minutes of it being black screen i pulled out the battery.
Now when i try to recover it it wont go into hboot and it just goes to the htc white screen then it quickly fades to a black screen and stays like that.
so my question to you all is a Jtag the only way i can save my phone or is there something else i can do?
http://forum.xda-developers.com/showthread.php?p=30480411
Sent from a dream.
Teichopsia said:
http://forum.xda-developers.com/showthread.php?p=30480411
Sent from a dream.
Click to expand...
Click to collapse
Im sorry but I dont understand. I cannot enter hboot no mater what i do and don't you need to enter hboot to reflash it?
True, but I'm hoping you are doing something wrong.
Pull battery, wait a few minutes, place back in. Press and hold Volume down, then power button. Does it go into hboot? If not.
Read this.
http://forum.xda-developers.com/showthread.php?p=20382502
Edit: you are the first report with that issue after trying to flash that rom. My bet (that is, if you are new), you are not doing something wrong.
2nd edit: if you are new, then read the guide in post#7
http://forum.xda-developers.com/showthread.php?p=30007255
Sent from a dream.
Teichopsia said:
True, but I'm hoping you are doing something wrong.
Pull battery, wait a few minutes, place back in. Press and hold Volume down, then power button. Does it go into hboot? If not.
Read this.
http://forum.xda-developers.com/showthread.php?p=20382502
Edit: you are the first report with that issue after trying to flash that rom. My bet (that is, if you are new), you are not doing something wrong.
.
Click to expand...
Click to collapse
I really appreciate the help Teichopsia , but I've tried the power /volume - method many times and it still wont go to hboot. if it helps this is the 5 time i have have flashed a rom on my phone (and it is rooted) and yes sadly i had to be the first person to be unlucky enough to get my phone bricked from the blackout rom :crying:
i think i could get out of this mess if i could only get into hboot.
reading the method you linked to me will it work if i cant even get to the hboot screen? my phone only stays of the white htc logo screen for about 3 seconds then it goes to a lit black screen
on a side note should i report what happened to team blackout to see if they have any soloutions?
The only thing I can think of is trying to get into hboot without the sd card and sim card.
The rest is beyond my knowledge.
You'll need to wait for someone more knowledgable than myself to help you.
Remember, first press and hold the volume down button, while holding that down press the power button. Do not release either button till it shows the hboot. If that doesn't work, pull the battery for five minutes and try again. If you did this part exactly like that, then you can skip it.
Well, you already posyed your issue here, just wait for someone to help you. Glevitan is bound to show up sooner or later.
Sent from a dream.
I would see if you can send commands to it from adb while its in the blacked out state. adb is pretty easy to use and can be found easy online. if you get it installed type "adb devices", if it recognizes your device type "adb reboot bootloader" or "adb reboot recovery".
Novius vi said:
hello all,
I am new here and I have been searching the forums for a few days as well as the internet but I could not seem to find one that had my same problem, but if there is can you please direct me to it and apologies for that.
I was installing a new rom, the Blackout ICS Incredible v3.0.0 FULLY WORKING!!! [4.0.4][Sense 3.6], onto my inspire i did a full wipe using FULL_WIPE_1.5_EXT4_.zip and I cleared the caches. the install i thought went well because it went to 100% and i even chose what kind of background i could as well as choosing to over clock my processor. The phone the restarted after all of that and it went to the htc screen then faded to black, after about ten minutes of it being black screen i pulled out the battery.
Now when i try to recover it it wont go into hboot and it just goes to the htc white screen then it quickly fades to a black screen and stays like that.
so my question to you all is a Jtag the only way i can save my phone or is there something else i can do?
Click to expand...
Click to collapse
i also have the same problem. i'm using a DHD. and to add to that, my volume rocker is broken. i wonder why the warning not to select reboot immediately after installation wasnt part of the download as a readme or something. i may have just lost a perfectly good phone as a result
I can confirm as a third user and one knowledgable in flashing roms that the ICS blackout does the same thing to my phone. I can also confirm that pulling the battery and then trying hboot just results in the white htc screen instead of just popping up hboot. I was able to boot into recovery from the white htc screen by using adb and doing the "adb reboot recovery" command. I am able to restore my backup just fine so you guys will be able to fix it. it must just have a bad boot image for the version of hboot that we have installed.
Gizmoe said:
I can confirm as a third user and one knowledgable in flashing roms that the ICS blackout does the same thing to my phone. I can also confirm that pulling the battery and then trying hboot just results in the white htc screen instead of just popping up hboot. I was able to boot into recovery from the white htc screen by using adb and doing the "adb reboot recovery" command. I am able to restore my backup just fine so you guys will be able to fix it. it must just have a bad boot image for the version of hboot that we have installed.
Click to expand...
Click to collapse
Im sorry but this is the first time i have ever done something like that can you give me a step by step instruction how to do it or a link that says how, i dont want to sound lazy but I scared to mess up my phone even more
Use this guide its very easy. if you have already used your phone on your pc and the drivers are installed all you need to do is download the easyadb and follow the instrucions to where is says to type adb.exe. once it is started just type adb devices to make sure it sees your device and then adb reboot recovery
Ignore the fact the instructions are written for a xoom as it will work for any android device with the drivers already installed, which they should be from rooting, syncing and all the other stuff you have probably already done on pc.
UPDATE: I reinstalled ICS blackout but instead of wiping myself i just let aroma installer do it and everything went fine this time. I noticed the aroma installer reformats everything to ext4. its not mentioned in the op as a requirement but seems thats the case. Hboot version has nothing to do with it like i previously commented. It really is a cool rom with both ics and sense. I have only tried the sense version so far
Hope this helps?
Novius vi said:
Im sorry but this is the first time i have ever done something like that can you give me a step by step instruction how to do it or a link that says how, i dont want to sound lazy but I scared to mess up my phone even more
Click to expand...
Click to collapse
Just in case-- to get into recovery you must press and hold the volume down for a few seconds and then hold the power button. Do not do press them both at the same time. I realize you wrote that your volume rocker seems or is broken but I wrote above just in case-- when I first tried to root my phone, I was pushing them both at first and thought my rocker was broken....
Since you rooted the phone originally-- not sure how you did it. But if you go to this link you can download recovery flash. Read the "readme" file:
http://forum.xda-developers.com/showpost.php?p=29208930&postcount=10
Assuming you can get into recovery-- then reload the blackout ROM but you MUST let the aroma installer wipe and format do not use any other wipe/format tool. Then do NOT press the "FINISH" button-- instead press the back arrow-- you want to go back to flash recovery and reboot from there. If you press finish (like I did multiple times, the phone will just lockup).
Best of luck!
Three of us confirmed that hboot was inaccessible even after battery pull. I am no stranger to this device as well. The only fix was using adb reboot. Also if you actually reformat your partitions to ext4 before install, then aroma will install correctly. It's just not mounting anything if it's still in ext3 format. Definitely better to just do the full wipe within aroma though. I do agree with not hitting restart from aroma but someone already mentioned that a few posts up.
Thank you thank you thank you
After putting it into abd it recognized it and then i was able to put it into hboot. Im not out of the woods yet, but after not being to see hboot in so long, well its just amazing to see it again
ok now its in hboot it gives me 4 choices
bootloader
Reboot
Reboot Bootloader
power down
apologies again but just for reassurance which one should i select?
THANK YOU GUYS for getting me this far!!!
special thanks to Gizmoe for suggesting the adb route
Novius vi said:
After putting it into abd it recognized it and then i was able to put it into hboot. Im not out of the woods yet, but after not being to see hboot in so long, well its just amazing to see it again
ok now its in hboot it gives me 4 choices
bootloader
Reboot
Reboot Bootloader
power down
apologies again but just for reassurance which one should i select?
THANK YOU GUYS for getting me this far!!!
special thanks to Gizmoe for suggesting the adb route
Click to expand...
Click to collapse
Select bootloader to get to recovery option.
1shukla said:
Just in case-- to get into recovery you must press and hold the volume down for a few seconds and then hold the power
Assuming you can get into recovery-- then reload the blackout ROM but you MUST let the aroma installer wipe and format do not use any other wipe/format tool. Then do NOT press the "FINISH" button-- instead press the back arrow-- you want to go back to flash recovery and reboot from there. If you press finish (like I did multiple times, the phone will just lockup).
Best of luck!
Click to expand...
Click to collapse
I did exactly as you said I pressed finished and it asked if i wanted to reboot i said no. then it sent me back to recovery mode crossing my fingers hoping to see that it works:fingers-crossed:
Now, just manually reboot.
Sent from a dream.
You saved my phone!!
Thank you guys sooo much this Rom is great once I got past that minor issue
My phones working better than ever I even oced it a little bit
Again I am eternally grateful to you guys and team black out for this great Rom!
Related
Hey guys I was having some problems with my xoom's wifi on Tiamat's 1.4.4 so i decided to relock the device and use stock.
It's a US model and had build HMJ37 but i decided to follow this thread
http://www.xoomforums.com/forum/mot...4600-thinking-about-unrooting-read-first.html
I downloaded img build HRI66 and followed all the steps and it was ok. Then, i rebooted and now my device is at the motorola logo's dual core screen. Everytime i manually reboot with power and volume up it automatically reboots the device instead of shutting it down, it literally won't shut down and keeps hanging at the moto logo. It just keeps rebooting and getting stuck at the motorola logo. I then unlocked again, and performed the same process with the HRI39 img and still got the same problem
So im stuck. Please help me out guys, i'm in serious ****.
So you have gone as far as the "fastboot erase cache" and "fastboot oem lock" right? This is kind of funny because I tried to install Tiamat 1.1 ROM tonight and ended up going through this HUGE loop of problems.
Here's the problem I had: some time ago I installed ROMManager from the market. I thought it would be easier. It SHOULD be easier. I let it update my recovery to its own version 4.something. It allowed me to SORT OF install the ROM, but I wound up with some persistent system files that weren't getting wiped and a bcm4329.ko version mismatch.
This stumped me for a long time because all I could see was an "Error" message where I was supposed to be able to toggle the wifi on and off. I tried rolling back to my previous ROM. No go. And the culprit the whole time was ROMManager's CWM.
I tried rolling back my recovery.img file to the Tiamat version recommended in this forum. I kept getting all of these crazy "could not mount" errors for pretty much EVERYTHING. I thought my recovery partition was effed. So I rolled back to stock. Followed pretty much the same instructions you linked to.
From there I was able to boot into the stock OS. WiFi worked. I breathed deeply for a minute or two then dove right back in.
If I was in your position I would (and I did, though not from a boot loop) boot into fastboot and unlock the bootloader again. You can do it by holding the Vol down key as the device boots. When fastboot loads type "fastboot oem unlock". Press the Vol down key then the Vol up key. Do that again. Your device is unlocked now! Hooray!
Now you need to install a recovery.img. (I just did this too.) Get the .img file here: http://forum.xda-developers.com/showthread.php?t=1074979
Boot into fastboot again. Put the recovery img file you downloaded into the same directory as your adb and fastboot executables (if you haven't already linked to them in your PATH). Type "fastboot flash recovery recovery-lotsofstuffhere.img". Type "fastboot reboot". 2 seconds after the Motorola logo pops up press the Vol Down key. Then press the Vol Up key to enter recovery.
Ok, here's where I found out what a dumbass I was. I got all of the stupid "can't mount anything" errors again. I thought, HOLY ****. I just did all of that work, spent hours troubleshooting and reformatting and bringing it back to stock and flashing the custom recovery all over again just to run into the SAME error. I really thought I was screwed. Then I found some forum where a guy was complaining about the same error. He realized he was getting it because his sd card was half-way out. I thought - "SD CARD?!?" Some guys told me I needed one earlier too, but the ROMManager CWM didn't require it. It just screwed up my system files. So I popped one in and rebooted. Voila. Everything's kosher. If YOU have the same problem, make sure you've got an SD card in.
Ok, so now you're in recovery. You'll need to flash an OS of course. If you haven't already got it, get Tiamat 1.1 rom. Put it on the sd card. Wipe data/factory reset. Install zip from sd card. You're golden. At least I was. 5 hours later.
-Mike
Hey Mike I'm gonna give this a go. Just when i downloaded the img file to flash through fastboot i got an error saying battery was too lower to perform the recovery....damn it! The xoom isn't able to charge at the moment so i have to wait until it dies i guess (or i hope at least) and then charge it up and try again later.
Thanks again dude, hope i sort this out too. I'll download tiamat 1.1 in the meantime.
DUDE YOU'RE MY ****ING HERO!!!! I got it running can't say if everything is 100% just yet but the fac tthat im back in is enough to thank you so very much Mike!!! What a guy!
It worked? Great that's excellent news. Just out of curiosity - did you get there because you had ROMManager's ClockWorkMod? Or maybe you didn't do a full wipe before flashing a new rom? Or maybe you restored some WiFi settings with Titanium Backup after a new flash? How did you wind up with tthe problem in the first place - you know, for posterity.
well to be honest i am not 100% sure. I think the source of the problem msut have come from my previous installation of tiamat's 1.4.4 rom, it was always actin up on me and i don't believe i wiped the mod before i updated it and that may have done it. I wish i could give you more than just a pseudo answer.
DeeJayCruiser said:
Hey Mike I'm gonna give this a go. Just when i downloaded the img file to flash through fastboot i got an error saying battery was too lower to perform the recovery....damn it! The xoom isn't able to charge at the moment so i have to wait until it dies i guess (or i hope at least) and then charge it up and try again later.
Thanks again dude, hope i sort this out too. I'll download tiamat 1.1 in the meantime.
Click to expand...
Click to collapse
This is why they say to make sure you're plugged in when doing this important stuff, lol.
okantomi said:
This is why they say to make sure you're plugged in when doing this important stuff, lol.
Click to expand...
Click to collapse
Normally, I'd agree but in this rare case, he actually needed it to fully drain because he couldn't get it to power off using any normal method. Weird! so, it seems his only shot was to let it die to finally kill the screen and then start over. Very odd...
From original post
DeeJayCruiser said:
Everytime i manually reboot with power and volume up it automatically reboots the device instead of shutting it down, it literally won't shut down and keeps hanging at the moto logo.
Click to expand...
Click to collapse
farmsatguy said:
Normally, I'd agree but in this rare case, he actually needed it to fully drain because he couldn't get it to power off using any normal method. Weird! so, it seems his only shot was to let it die to finally kill the screen and then start over. Very odd...
From original post
Click to expand...
Click to collapse
You are right...I had forgotten that from the OP. Very strange indeed.
Yeah I dunno why, my xoom was just acting up. It's fantastic now, albeit the wifi still has a couple kinks but android market issues have been resolved, i get much better streams and with tiamat 1.1 everything is already built in and with a quickboot option =)
Xda...where would i be without you!
farmsatguy said:
Normally, I'd agree but in this rare case, he actually needed it to fully drain because he couldn't get it to power off using any normal method. Weird! so, it seems his only shot was to let it die to finally kill the screen and then start over. Very odd...
From original post
Click to expand...
Click to collapse
You should be able to reboot the device using vol up + power, then holding vol down and vol up until it says "Cold booting Linux.....".
This should do the same as letting the battery drain, plugging it in and turning it on.
DeeJay - dunno if you've done this already, but if you haven't you should go back to the Tiamat 1.1 thread and find the Modpack. It fixes the Market update issue and gives you built-in screenshot capabilities and an option to reboot into recovery from the power off menu. It's in there - you just have to scroll down a bit before you find it.
Also - what issues are you having with WiFi?
Thanks for that important tidbit, solarnz. I'm going to file it away for future use.
OMG!!!! Dude you just saved my life! I thought my baby was out the window. I had the exact same problem as you did. I was trying everything from every thread that had anything to do with this problem. I just finished installing and it booted. WHEWWW!!!
Thank u thank u thank u!!
Glad it helped. I'm seeing all kinds of posts in here about the ROMManager CWM. Not good.
Sent from my Xoom using Tapatalk
I am def a newB and have taken the plunge into custom roms. I followed the directions to installing Infuse with modded 3e recovery and cwm going to rom mgr and doing the download and now my phone is just displaying "SAMSUNG" across screen its been about 10 minutes. Question is, is the rom installing or is the phone bricked and what are the signs of a brick? How would long does a wiped Infuse download usally take?
It shouldn't take that long
infuse 4g "a lot a screen real estate"
So how would i know if the phone is bricked???
supadupadoug said:
So how would i know if the phone is bricked???
Click to expand...
Click to collapse
take battery out and try turning it on again after putting it back in. if it starts booting and you get the lady talking, your good, but if it just sits there, you most likely have a brick.
No worries though. Just follow these steps to get back to stock and your golden:
Ultimate Unbrick Thread:
http://forum.xda-developers.com/showthread.php?t=1116251
once your back to stock you can flash the community kernel via odin:
Community kernel:
http://forum.xda-developers.com/showthread.php?t=1119598
Once this is done, your rooted (just need to download superuser from market), and you have been lagfixed(with the lady talking on boot) and you have CWM to flash roms easily (accessible via: turning phone off, holding down volume buttons, press power till you see samsung logo, then keep holding volume buttons till red text comes up)
Then you should be back to the game
I really appreciated my heart is racing right now with uncertainty. I havent done what u mentioned but i did hold the power button and volume keys and now I do have access to a red menu that says ClockworkMod recovery v2.5.1.3 - Voodoo lagfix. does this mean anything???
supadupadoug said:
I really appreciated my heart is racing right now with uncertainty. I havent done what u mentioned but i did hold the power button and volume keys and now I do have access to a red menu that says ClockworkMod recovery v2.5.1.3 - Voodoo lagfix. does this mean anything???
Click to expand...
Click to collapse
try to reboot... and relax, your phone will be fine
If you want, stop into the #infuse4g channel on webchat.freenode.net
I'm in there and could probably help you out better
Im at work LOL so they have filters on video but I've tried to reboot and the screen displays SAMSUNG never heard a lady or anything like that, but I'll give it some time and if all else fails follow the procedure u suggested previously. S/N I while in the red screen i selected to apply the unzip package update.zip. the screen flashed and quickly and i guess it did its thing the went back to the menu and i chose reboot so I guess we will see what happens... I really do appreciate your time and effort in helping me resolve this problem
supadupadoug said:
Im at work LOL so they have filters on video but I've tried to reboot and the screen displays SAMSUNG never heard a lady or anything like that, but I'll give it some time and if all else fails follow the procedure u suggested previously. S/N I while in the red screen i selected to apply the unzip package update.zip. the screen flashed and quickly and i guess it did its thing the went back to the menu and i chose reboot so I guess we will see what happens... I really do appreciate your time and effort in helping me resolve this problem
Click to expand...
Click to collapse
the update.zip wont do anything. there's nothing to flash...
Another thing you can try is to flash the rom again, since you have access to red CWM... then if that doesnt work, follow the unbrick procedure
May be dumb question but how do i flash rom from red screen(link???) thanks
Assuming you have the zip for the ROM installed to your internal SD (CWM can't find stuff on the external SD unfortunately...)
Use VolUp/VolDown to navigate through CWM.
Wipe Data/Factory Reset should always be done when changing from one ROM to another. Usually not needed when updating a ROM from a previous version of the same one.
Then choose "Install zip from sdcard" then "Choose zip from sdcard" and navigate to the zip for the ROM.
However if Voodoo Lagfix is interacting strangely with your phone, other steps may be needed.
Good news is that if you can get into CWM, at least your kernel is in decent shape.
For whatever reason I never heard the lady speaking when I installed my ROM, although I may have gone into the other room and done something else.
Well for some reason I cant go to the page with the GTG unbrick download which sucks idk maybe u can email me the zip file [email protected] if not I guess i'll be back once I get home and try to figure this thing out. smh phone down
Thanks Entrophy512 I will give this a try and get back w the results
Entrophy512 followed your directions screen is displaying SAMSUNG you have any idea about how long the phone should be in this state???
Not long
5 minutes ish
is the lady talking??
well yea mine is stuck on that screen for well over 15 mins. guess i have to start at square 1. Does anybody know what this means???
supadupadoug said:
well yea mine is stuck on that screen for well over 15 mins. guess i have to start at square 1. Does anybody know what this means???
Click to expand...
Click to collapse
could be anything. something went screwey on the flash... so just try again and follow the instructions
OK finally after reading and digging deep into the INFUSE I found the correct zip file which was in the clockworks recovery folder which i accessed though the red menu. I am now running infused 1.5.3. Thank you all for the support. One last question how do I refress all my data from stock. I did a Titanium backup of everything how to i get all that stuff onto my phone???
And again many thanks
supadupadoug said:
OK finally after reading and digging deep into the INFUSE I found the correct zip file which was in the clockworks recovery folder which i accessed though the red menu. I am now running infused 1.5.3. Thank you all for the support. One last question how do I refress all my data from stock. I did a Titanium backup of everything how to i get all that stuff onto my phone???
And again many thanks
Click to expand...
Click to collapse
Install TiBu from the market.
Restore user apps + data - don't restore system data. You may in that case still need to put in the info for your Google account, etc and tweak some settings.
Ok im finally up and running. Question what is the proper way to turn the device completely off. I tried yesterday and I see I have an extended power off menu with various options. What do they mean? Yest I chose turn phone off and the phone went to the downloading screen with the big yellow android w the shovel. Again thanks to you all.
Hello all, im fairly new to 'rooting' world and wish my first post wasn't on this, however, i'm not too sure where else to look for help! I believe my phone may be lost, but thought I'd ask before giving up completely. I was running ARHD 3.6.7 rom on my HTC Sensation. rooted, everything working like a charm, til last nite... I d/l and flash the ARHD 3.6.7 Hard Version Brightness Tweak from this post... http://forum.xda-developers.com/showthread.php?t=1350580. However, instead of going into recovery, I used rom manager ( I've read at times not to use this for certain things, so guessing this is one of em..noob mistake that may cost me my phone). While in rom manager, the following 2 options were checked, which I think is where I went wrong, 1) wipe data and cache 2) wipe dalvik cache. When my phone rebooted, the old 'android' boot image was showing instead of the 'Beats Audio' from the ARHD Rom. This is where I am at. The phone seems to be stuck at reloading this image over and over. I can not boot into recovery by holding the down volume and power. Any help would be greatly appreciated. Thanks
Chase79 said:
Hello all, im fairly new to 'rooting' world and wish my first post wasn't on this, however, i'm not too sure where else to look for help! I believe my phone may be lost, but thought I'd ask before giving up completely. I was running ARHD 3.6.7 rom on my HTC Sensation. rooted, everything working like a charm, til last nite... I d/l and flash the ARHD 3.6.7 Hard Version Brightness Tweak from this post... http://forum.xda-developers.com/showthread.php?t=1350580. However, instead of going into recovery, I used rom manager ( I've read at times not to use this for certain things, so guessing this is one of em..noob mistake that may cost me my phone). While in rom manager, the following 2 options were checked, which I think is where I went wrong, 1) wipe data and cache 2) wipe dalvik cache. When my phone rebooted, the old 'android' boot image was showing instead of the 'Beats Audio' from the ARHD Rom. This is where I am at. The phone seems to be stuck at reloading this image over and over. I can not boot into recovery by holding the down volume and power. Any help would be greatly appreciated. Thanks
Click to expand...
Click to collapse
Sholdn't have wiped anything when installing a mod, you need to open your recovery and reinstall ARHD ..if you don't have the .zip on your sdcard then just take it out of the phone and put it into the computer and copy over a .zip
you need to wipe everything before installing the ROM so user the super wipe
All can be found here..
http://forum.xda-developers.com/showthread.php?t=1098849
Friend I doubt you're bricked. Id say you had a bad install. I'd reinstall and is be happy to walk you through it. So good news is you're not bricked.
Sent from my HTC Sensation 4G using XDA App
Ok, not bricked is great! However, I do have another question. I have a pretty good uderstanding of what to do once in recovery, my question is ' how do I get there?' When I hold the down volume and power buttons, I still boot to the android screen which I am currently stuck on. I have the zip files I need on my sd card, just can't get to em... Is there another way to get into recovery to wipe and reinstall? Again, thx for the help, this is most definitely a learning experience
Chase79 said:
Ok, not bricked is great! However, I do have another question. I have a pretty good uderstanding of what to do once in recovery, my question is ' how do I get there?' When I hold the down volume and power buttons, I still boot to the android screen which I am currently stuck on. I have the zip files I need on my sd card, just can't get to em... Is there another way to get into recovery to wipe and reinstall? Again, thx for the help, this is most definitely a learning experience
Click to expand...
Click to collapse
HAve you tried pulling the battery out, then turning on to recovery
I have tried pulling the battery out, pulling the sd card out, seems like no matter, still loads to android screen. While at this screen, if i hold down power, nothing, phones stays on, if i hold down vol down + power, phone reboots to same screen. Seems like getting into recovery is my real problem...
ARHD doesn't recommend the use of Rom manager if you carefuly read the flashing instructions .further than that I had a problem like that in the past with my HTC desire ,what I did was to follow the unrevoked once again and did everything from the begining eventualy I got the recovery mode and flashed my new rom.maybe be if u follow a similar procedure by reinstalling the revolutionary kit will give u the desired outcome... Maybe sounds a bit odd but it worked for me .I don't think u have anything to lose if u try .your phone isn't bricked though by any means so no worries. Good luck maye
Sent from my HTC Sensation using xda premium
Chase79 said:
While at this screen, if i hold down power, nothing, phones stays on, if i hold down vol down + power, phone reboots to same screen.
Click to expand...
Click to collapse
Do you mean you're pressing volume down and power while your phone is already on ?
K, agreed, nothing to loose, gonna give that a go.. I am having detection issues. When I connect to pc, the device 'android phone' is recognized, but I can't access any files, HTC sync, fastboot for example saying no device connected, please check connection. I assume because the phone will not go past the boot screen? Anyhow, gonna try your suggestion. Thanks!
Mercvtio said:
Do you mean you're pressing volume down and power while your phone is already on ?
Click to expand...
Click to collapse
Yes, I have done both. While the phone is off, I have pressed vol down and power with no luck. I have also tried it while the phone was on (trying anything at that point). Still only going to android boot image.
Is there another way to enter recovery if vol down + power while phone is off doesnt work?
HALLELUJA..... Reboot into recovery successful! Not sure why, but after numerous attempt, I got it. Thx for all the quick replies. Wiping and reflashing now!!
Hey chase. Good job and have a look at coredroid Rom. Beautiful and fast. 2nd charge and at 20 hours at 49% battery left with moderate use.
Sent from my HTC Sensation 4G using XDA App
I'm having this same issue, I have used super-wipe and tried reflashing no change. still sits at the 'beats audio' flash screen. When I first tried to root the phone I believe i flashed the wrong radio zip but the hboot is version 1.23.0000 radio version is 10.14.9035.01_M whenever i try to reflash hboot or radio zips i get errors usually (status 7). It still boots into hboot and recovery just fine, but I'm not sure whats wrong or how exactly to fix it, any help would be appreciated. If you need any more information just ask. Thanks
messbarger said:
I'm having this same issue, I have used super-wipe and tried reflashing no change. still sits at the 'beats audio' flash screen. When I first tried to root the phone I believe i flashed the wrong radio zip but the hboot is version 1.23.0000 radio version is 10.14.9035.01_M whenever i try to reflash hboot or radio zips i get errors usually (status 7). It still boots into hboot and recovery just fine, but I'm not sure whats wrong or how exactly to fix it, any help would be appreciated. If you need any more information just ask. Thanks
Click to expand...
Click to collapse
Did you flash an ICS rom without installing the ICS firmware first?
If this is the case, take out your sd card, copy over the ICS firmware to the root of the sd card, boot into the bootloader, and it'll walk you through updating the firmware.
it says
model id incorrect
update fail!
press <power> to reboot.
i think the radio i tried to flash was for a different phone maybe, but it was in a tutorial to root and install arhd the tutorial said you have to update the radio to use ics. any ideas?
"model id incorrect" <- you need to super CID your phone.
Do you have adb running on your computer?
my bad guys i had supercid i hadnt changed it to 11111111 did that re-wiping and flashing now thanks for the help
Problem Solution
adamgaltress said:
Sholdn't have wiped anything when installing a mod, you need to open your recovery and reinstall ARHD ..if you don't have the .zip on your sdcard then just take it out of the phone and put it into the computer and copy over a .zip
you need to wipe everything before installing the ROM so user the super wipe
All can be found here..
http://forum.xda-developers.com/showthread.php?t=1098849
Click to expand...
Click to collapse
Follow these instructions and you will get your phone back - Had the same problem and this fixed it first time
Its been a while since this last post and I have had same problem today, 2012 March,..Using Htc super tool, while phone is off, and connected to usb cable, open htc super tool, and hit 4, it will cycle and press continue until it auotmatically boots the phone into recovery screen. Hope this helps it worked for me.
HTC Sensation Stuck at boot screen..Bricked?
I had the same issue and I was able to restore and get back to my old version.
As mentioned in
HTML:
http://forum.xda-developers.com/showthread.php?t=1192300
I followed everything, but still I cant flash my device correctly.
Here are my details.
I tried to flash ARHD 6.5.3 XE
-Revolutionary-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.17.1111
RADIO-10.14.9035.01_M
eMMC-boot
Jun 2 2011, 22:31:39
Has bought from the USA of HTC Inspite 4g (AT&T). Wanted to receive Root, S-OFF, Rom manager with ClockworkMod. Has started to do to change an insertion. Has received goldcard. After an overload phone has started to change an insertion. This process proceeded 2 hours (in the end of process there was a black screen). I have decided to overload phone. Has stopped process. After that problems have begun. Root, S-OFF, Clockworkmod I have received. But after reboot of phone it does not work about 10 minutes. 5 minutes at it absolutely black screen, then the white screen with an inscription of HTC simultaneously work 3 minutes the motor, loading of 2 minutes then begins. Process of switching-on or reboot of phone proceeds 10 minutes. Tried to replace an insertion once again. After that changes nothing. Did before setting of an insertion full surep wipe. It has not helped. I still have a problem. I want to enter into engineering menu HBOOT. I push down+power. I wait for 5 minutes (phone so is overloaded). I enter in HBOOT, but thus buttons (volume up and down, power) any more do not work. As to me to receive normal phone. I can not HBOOT make in it recovery. Where to me to take for HTC INspire 4G (AT&T) PD98IMG.zip. Also help me with the instruction. How to apply this file in RECOVERY.
I'm having a hard time with your English (or is it just fed into google translate?).
It looks like you installed the ENG hboot on a later model device that is incompatible.
You need to get it to boot (it will eventually) and put the newer hboot back on it. You can do this through ADB from a console. Here are the instructions:
http://paste.pocoo.org/show/495273/
@ Gene Poole
I had a hard time with his English too, but I understand exactly what he is saying because I did the same thing. I will try to re-explain it and hopefully someone can help us out.
In a nutshell, it sounds like we both flashed an Engineering HBoot starting with a stock US ATT Inspire 4G that came with Gingerbread. Specifically, what I did was I followed a guide on Cyanogenmod's wiki for the Inspire 4G which gave direction to downgrade to Froyo, root, and setup to use eng hboot. This apparently was a huge mistake. After the downgrade, when rebooting or powering on the phone, nothing would happen for a long time (black screen for 5 - 10 minutes, i.e. phone was off), then, screen would turn on with white background and HTC logo and phone would vibrate non-stop for several minutes, and eventually, phone would turn on. After the downgrade and making it to the home screen, I copied CM7 zip on to the SD card and rebooted into recovery via adb. Same exact weird process happened with phone being off for several minutes, then vibrating, then eventually i made it to cwm recovery. After installing CM7 and rebooting, same crazy startup process and made it into CM7 home screen.
I was hoping once CM7 was installed that the crazy startup process would disappear but it didn't. I saw afterwards in a CM forum that this happened to someone else and they had asked if the wiki could be updated to point to the Ace hack kit guide to rooting the Inspire 4g (which mentions that eng hboot shouldn't be used with the phone I had as configured). I then rebooted into bootloader via adb and after crazy startup and fastboot did not work at all (fastboot devices returned nothing). Further still, no buttons work in hboot at all (Vol Up, Vol Down, Power).
At this point, I could still get into the phone, but I wanted to try to undo everything I did and start over using the Ace hack kit. I then tried to use the Ace hack kit to unroot the phone by using the ATT GB RUU. The process seemed to go pretty far, but after a reboot, the phone never came back, and that's where I am currently. If I start the phone, it does crazy startup but never fully boots...stays on white HTC screen forever...which means I can't use adb (to my knowledge). I was able to get to hboot by putting elastics around volume down button and waiting a very long time, but it looks like hboot is still the eng hboot because none of the buttons work and I can't use fastboot. I was hoping that as part of RUU flashing that hboot would be restored to original one. I put the RUU (PD98IMG.img) on SD card, but again I can't get to it because buttons don't work.
So, it sounds like spv4 above is in a very similar boat. I have no idea what else to try. Only thing I can think of is if it's possible to somehow modify an RUU to start automatically when getting to hboot without any user input.
If anyone has any suggestions, I am more than willing to try anything. Thanks very much.
EDIT: So, as I was typing this post earlier, I had been "sitting" in hboot the whole time. When I was done, I looked at phone and PD98IMG.zip was been applied to phone automatically! Don't know if this was common knowledge or not, but everything updated OK. When it was done, hitting the power button to reboot didn't work, but I just removed battery and when putting it back in, phone booted normally back to what looks like stock RUU. Hopefully this info helps someone else.
JayB059 said:
@ Gene Poole
EDIT: So, as I was typing this post earlier, I had been "sitting" in hboot the whole time. When I was done, I looked at phone and PD98IMG.zip was been applied to phone automatically! Don't know if this was common knowledge or not, but everything updated OK. When it was done, hitting the power button to reboot didn't work, but I just removed battery and when putting it back in, phone booted normally back to what looks like stock RUU. Hopefully this info helps someone else.
Click to expand...
Click to collapse
Great! Glad you got it back, but you could have saved a lot of time.
The main problem is that the ENG hboot (or pre-GB hboots) doesn't recognize something in the hardware of the new phones. The end result is that the hboot runs at about 50x slower. It eventually gets booted, and once booted to an OS (either the main OS or the recovery OS) it runs fine since hboot has exited and passed control to the OS. So anytime hboot is in control, things crawl at a snail's pace.
Because the OS runs fine and hboot has exited, it is possible to overwrite the hboot partition from the booted OS. That's what you are doing in the instructions that I posted a few posts back. Once the correct hboot is installed, all is fine.
I agree that someone needs to update the cyanogenmod wiki. It's way out of date.
I'm currently experiencing the same problem.
I followed the instructions on how to downgrade using a goldcard, successfully rooted and i also flashed TrickDroid on it, but every time i turn the device on i have to hold the power button for 20 seconds and wait 10 minutes till the HTC logo appears, then it takes 2 minutes vibrating and i seriously can't deal with this.
can you please tell me how to fix this?
Revolver95 said:
I'm currently experiencing the same problem.
I followed the instructions on how to downgrade using a goldcard, successfully rooted and i also flashed TrickDroid on it, but every time i turn the device on i have to hold the power button for 20 seconds and wait 10 minutes till the HTC logo appears, then it takes 2 minutes vibrating and i seriously can't deal with this.
can you please tell me how to fix this?
Click to expand...
Click to collapse
Find the fix in the guide in my signature....you need to have basic knowledge of adb commands. If you need further help just let me know. :good:
Moved to Q & A section.
Sent from my Galaxy Nexus using Tapatalk 2
edit
I had the hTC EVO Design 4G as pretty much my first Smart Android. (Im not including the LG optimus M). The Switched to the Galaxy note & S3 for a while NOw Im using the HTC one S. I normally never have these problems or ever post on the forums. But Im desperate for fast help. I know how to do everything on both the htc evo 4g and design.
but The Ville is diff. without the removable battery
im blabbering....
let me try to STEPbySTEP explain my steps up to my not working Device.
!. I tried to Flash the Energy_9.07.2012.OneS.zip rom through TWRP at first. (thats was the suggesttion in the thread. So that the recovery would Flash the correct Kernel. But upon reboot. I discovered that contrary to the devs suggestion the WiFi still didnt work. So I flashed CWM through ROM manager. reboot into recovery flash wiped cache/ factory reset. But I dont think I wiped system, data, or anything not in the main Menu, Energy_9.07.2012.OneS.zip and I reboot. Upon reboot the HTC screen had the warning for use in htc do not distribute...then the bootanimation popped up and finally the booted up fine. Wifi was working this time. But now my network wasnt right. I didnt give the rom time to settle in though. I panic and open CMD and ran adb reboot fastboot.
Waited waited
now the boot loader was up. I had to unplug my deviice for the screen to show fastboot usb.
then this is where I think I ****ed up my phone
(I extracted the boot.img from the Energy_9.07.2012.OneS.zip and placed it in my android folder on C I also adb pulled my twrp recovery to
C:\android and renamed to recovery,img I wanted TWRP back I hate how CWM automaticaly boots when you plug it in tp charge from dead)
Now I had in my C:\Android\boot.img and \recovery.img.
I ran the command (im not sure if I ran boot or recovery first)Also my phone was anywhere near a full battery cloase to dead but my CMD window showed complete.
C:\Windows\system32>fastboot flash boot C:\android\boot.img
C:\Windows\system32>fastboot flash recovery C:\android\recovery.img
Now my phone is plugged into my Lenovo Thinkpad t410 with Win7 Pro OEM The red light to the top right isnt blinking like the battery to low to power on notification. Its steady. but when I hold down to turn on either the lights for the capacitie buttons flash untill I let go of the button or I do a combo of plugging in and out the usb and holding the power and volume bottons not sure Which order. PLEASE HELP! iM EXPECTING A PHONE CALL ABOUT A JOB INTERVIEW RESULTS.
In my time in CMD this error did pop up a few times. But I open HTC sync let it load. and then it would work.
C:\Windows\system32>adb reboot device
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
Would A ruu fix this????? Although I haven't once successively used one.
COMMENT, PM, IM, ME I DON'T CARE JUST PLEASE HELP ME AN MY POOR [PHONE] GUARANTEED THANKS BUTTON!!!!!!! USAGE AS FOR HELPING.
why would you flash something made for HTC ONE S if you have HTC EVO
especially when you're just starting to learn about
sorry, but I would guess that you're chance is to find somewhere a ruu for your model
ultimul said:
why would you flash something made for HTC ONE S if you have HTC EVO
especially when you're just starting to learn about
sorry, but I would guess that you're chance is to find somewhere a ruu for your model
Click to expand...
Click to collapse
I have the HTC One S Ville
I was stating how I use to have the evo
gisaac2157 said:
I had the hTC EVO Design 4G as pretty much my first Smart Android. (Im not including the LG optimus M). There is no development forum for that devices in XDA so I used SDX-DEV I actually started learning how to kang my own roms.
im blabbering....
let me try to STEPbySTEP explain my steps up to my not working Device.
!. I tried to Flash the Energy_9.07.2012.OneS.zip rom through TWRP at first. (thats was the suggesttion in the thread. So that the recovery would Flash the correct Kernel. But upon reboot. I discovered that contrary to the devs suggestion the WiFi still didnt work. So I flashed CWM through ROM manager. reboot into recovery flash wiped cache/ factory reset. But I dont think I wiped system, data, or anything not in the main Menu, Energy_9.07.2012.OneS.zip and I reboot. Upon reboot the HTC screen had the warning for use in htc do not distribute...then the bootanimation popped up and finally the booted up fine. Wifi was working this time. But now my network wasnt right. I didnt give the rom time to settle in though. I panic and open CMD and ran adb reboot fastboot.
Waited waited
now the boot loader was up. I had to unplug my deviice for the screen to show fastboot usb.
then this is where I think I ****ed up my phone
(I extracted the boot.img from the Energy_9.07.2012.OneS.zip and placed it in my android folder on C I also adb pulled my twrp recovery to
C:\android and renamed to recovery,img I wanted TWRP back I hate how CWM automaticaly boots when you plug it in tp charge from dead)
Now I had in my C:\Android\boot.img and \recovery.img.
I ran the command (im not sure if I ran boot or recovery first)Also my phone was anywhere near a full battery cloase to dead but my CMD window showed complete.
C:\Windows\system32>fastboot flash boot C:\android\boot.img
C:\Windows\system32>fastboot flash recovery C:\android\recovery.img
Now my phone is plugged into my Lenovo Thinkpad t410 with Win7 Pro OEM The red light to the top right isnt blinking like the battery to low to power on notification. Its steady. but when I hold down to turn on either the lights for the capacitie buttons flash untill I let go of the button or I do a combo of plugging in and out the usb and holding the power and volume bottons not sure Which order. PLEASE HELP! iM EXPECTING A PHONE CALL ABOUT A JOB INTERVIEW RESULTS.
In my time in CMD this error did pop up a few times. But I open HTC sync let it load. and then it would work.
C:\Windows\system32>adb reboot device
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
Would A ruu fix this????? Although I haven't once successively used one.
COMMENT, PM, IM, ME I DON'T CARE JUST PLEASE HELP ME AN MY POOR [PHONE] GUARANTEED THANKS BUTTON!!!!!!! USAGE AS FOR HELPING.
Click to expand...
Click to collapse
If you hold down the power button long enough the leds should stop flashing. You should try that and then once it goes off, hold down the volume down and the power button.
That should get you back into bootloader. From there you may want to try flashing a custom kernel (the SENSE version of Fusion, for example).
An RUU could help, but you would need to relock your bootloader in order to flash it. You would need to be able to get to your bootloader screen. RUUs are EXE files and are pretty self explanatory when you run them and have your phone connected. See http://www.4shared.com/folder/jKN2qjTl/HTC_Ville_RUU_Collection.html for RUUs. There is also a thread on RUUs in the development thread. Read that too.
But first things first, you need to be able to access your bootloader! Keep fiddling with your power button and volume down button.
AKToronto
gisaac2157 said:
I have the HTC One S Ville
I was stating how I use to have the evo
Click to expand...
Click to collapse
can you reboot into recovery/fastboot? press the power button for 5-7 seconds until the keys start blinking;
the phone should reset after it
some RUU, you can find here:
http://androidforums.com/one-s-all-things-root/560329-ruu-download-mirrors.html
Thanks so much.
AKToronto said:
If you hold down the power button long enough the leds should stop flashing. You should try that and then once it goes off, hold down the volume down and the power button.
That should get you back into bootloader. From there you may want to try flashing a custom kernel (the SENSE version of Fusion, for example).
An RUU could help, but you would need to relock your bootloader in order to flash it. You would need to be able to get to your bootloader screen. RUUs are EXE files and are pretty self explanatory when you run them and have your phone connected. See <font color="red"> as a new member cant post links</font> for RUUs. There is also a thread on RUUs in the development thread. Read that too.
But first things first, you need to be able to access your bootloader! Keep fiddling with your power button and volume down button.
AKToronto
Click to expand...
Click to collapse
I feel really stupid for not knowing THAT. Now whats up with the energy rom? the thread says stable. How am I suppose to flash it?