Getting worried now.
I just unrevoked my Desire and put the latest radio onto the SD Card named update.zip
I used Rom Manager option to install ROM update and checked both the Wipe/Reset options..
My Desire is currently stuck on the screen with the White Warning Triangle and Yellow Exclamation mark, with the little Android.. for over an hour now.
Pulling the battery seems to be a complete no-no, but is over an hour wait normal ?
What do i do now...!?
Nevermind, I took a deep breath and pressed a few of the buttons and the Clockwork Recovery screen popped up with an Authentication Error for the update.zip...
er .. i think you have to press vol up + power simultaneously for the recovery menu to show up while you're in that screen... though I'm not 100% sure if that's the combo for the desire.
..and it all works!
Hacking phones gone 2am.. it's been a while!
Anyways, it's all working now. I decided to try the custom ROM update first which took just a few minutes, followed by another Recovery Reboot for the Radio ROM which took a few more minutes in the end.
I'm assuming the Signature Verification thing was something that is turn on/offable, because after trying the Custom ROM update first I then noticed in Clockwork Recovery that there is an option for having verification on or off.. but it was already set to off!
I'm sure in the myriad of HOWTO posts it's written in there, but believe me, during that hour and a half of waiting to see if i'd bricked my phone, I was reading just about every HOWTO that's been written!!
Anyways, knowing now how easy it actually is to unrEVOke, then apply custom ROMs/Radio I wish i'd done it sooner.. or at least started earlier in the day.
Related
Hi,
I'm a real neewbie so please be gentle.
I've rooted my phone and put defrost 5.4 on it.
Works good and i'm figuring out how things work.
I found out now that when i reboot the phone it gets stuck in starting up.
The colors exploding from the left and the right side to become a "X", but then after a while the x is not made any longer and after half an hour it is still trying to make an X.
Take out the battery, put it back and start the phone and it starts normal.
When i install something from the "defrost setup" its downloaded and when i press install the phone restarts, it is unpacking the file, reboots and then gets stuck again.
Have to take out the battery to start the phone again.
What can be the couse of this??
Just found out that also a "normal start" ends up in a endless bootscreen.
The only way to start the phone is take the battery out, put it back and press "start".
Do a full wipe and try another ROM is my first suggestion.
So idid a wipe, after that a recovery (had to start all over again) but the endless bootscreen still remains.
???
1) Find a new ROM and put it on the root of your SDCARD
2) Boot into Recovery by pressing BACK and the POWER button
3) Perform a full wipe (data/factory reset) and cache
4) Flash the new ROM
5) Boot the phone
If you still have problems post logcat.
i've cleaned and whiped (i think) almost everything.
Installed a fresh defrost 5.6.
Installed the defrost apps addon, the phone reboots and a screen apears with a android an a box with an arrow out.
Text is passing by, the phone reboots and starts up.
So far so good, but when i restart or reboot the phone its hangs in this endless lashing coulorfull screen.
I've tried to make a "logcat".
Hopefully it tells you more than it tells me.
i am having the same problem.
first off all: you can press power + volume down + optical joystick to restart phone.
no need to remove battery
my last logcat (with Error filter): www wog-fds.de/log_bootloop.txt
i started to have this problem when i redid the unrevoked process (dont really remember why, thou).
thx for help
edit: not sure but the first logcat looks like somethings missing
heres anotherone without filter www wog-fds.de/log_bootloop2.txt
thx
OK, maybe this is getting somewhere.
I also did a re-revoke, but i do know why.
the first attempt to root my phone ended up in a small disaster.
At the end of the proces i found out that i have a SLCD screen and not an AMOLED, so my phone was as good as dead.
Thanks to someone on a Dutch forum i was able to get my phone back to life.
After that i rooted my phone with the latest version of unrevoked, and this time i was succesfull.
But now i am encountering this problem and it is no fun.
I have at the moment nothing running on the phone because after a re-re-reinstallation i can start all over again with al the apps and so on.
It hangs at the final stages of the boot it looks like.
I had a similar problem when I was messing around with my old framework.
So why you're getting it, I have no idea.
First thing is first Bud
Download DeFrost 5.7 And use the latest version (Illuminate some issues to start with)
What your saying is the Boot Animation (The Multi Colour X animation "Nexus Boot Animation"
You get a boot loop on there....
How long have you left it trying to boot? the first boot after a Reflash does take alot longer than normal as it has to write to a number of files first.
(This only occurs on a New ROM or a Reflash of the frameworks)
So first off Lets Get that latest ROM on the SD Card:
Use w/e method you need to to get it on there
Turn the Phone Off "Where going to load recovery"
Press the Down Volume Key and press the power button Once.
You will see a white screen with Android images at the bottom:
Press the Volume down once (Recovery) when this is highlighted press the power button
Where now in a black screen Press Volume Up and Power
(We should now have a Blue Menu (Am taking it by the issues you talk about your using Clockwork Recover.......)
Go down to Apply sdcard:update.zip
And press the power button. So where now Clock Work Recovery
(If you dont have Clockwork i.e. Fake Flash Update.zip maybe someone can post it for me, Limited for time in work, But search for Fake FLash Clockwork if you dont have it.
Then go down to Wipe Date/Factory Reset
Select the only line that is Populated.
Go back to main menu and go to install Zip from SDCard and press the OJ
Select Choose Zip from SDCard.
Find you ROM and press the OJ
Wait some time and press the back button a few times, and select the reset option?
DO NOT INSTALL NO MODS OR THEMES, THIS CAN ONLY BE DONE AFTER A FULL BOOT OF A CLEAN ROM.
Leave it some time, as the first boot is always the longest.
Fingers crossed you should be OK.
What your talking about is a problem with the ROM (as the bootanimation is called by the ROM)
dave7802 said:
DO NOT INSTALL NO MODS OR THEMES, THIS CAN ONLY BE DONE AFTER A FULL BOOT OF A CLEAN ROM.
Click to expand...
Click to collapse
That'd be my guess too. If you try to apply a mod before you've let the ROM unpack itself it does exactly as you describe.
What your saying is the Boot Animation (The Multi Colour X animation "Nexus Boot Animation"
You get a boot loop on there....
How long have you left it trying to boot? the first boot after a Reflash does take alot longer than normal as it has to write to a number of files first.
(This only occurs on a New ROM or a Reflash of the frameworks)
I've installed the defrost.
After it came in full working conditions i've added the defrost add-on.
Phone shuts down, starts again in the screen with the one doid and a box with an arrow out.
Some writing apears and the phone starts again.
The colours apears and making a cross and this goes faster and faster and then a screen where i have to enter my sim-unlockcode and the phone is up and running.
So far so good.
When i now switch the phone off or give it a reboot ( in the screen after a long press on the powerbutton) the phone starts in the white screen with HTC logo, then the colours apear making a cross, but after time this goes slower and slower until the cross is not ever made again.
The colours appear trying to make a cross and diappear and comming back again, and this goes on for ( i left it once for 1/2 an hour)
I will give it a go with the 5.7
thanks for the help.
Really, i heave my phone for one month now and it is my first android thing.
Never worked with linux etc etc.
What does "press the OJ" means ??
oj = optical joystick
@dave7802
thanks for the answer but i have the bootloop also when i do a manual restart without flashing anything.
i use defrost 5.7
i did a restart after flashing
bye
strange thing to happen. it must be in the ROM because it wasn't happening on the stock ROM.
so try another ROM some like cyanogen or opendesire. is it happening also?
Wel, i've come to the point that i think "WTF", it works and the only thing is the start/reboot.
I'm not going to re-re-re-re sign in to my google account, and not want to re-re-re-re-enter my mail account again.
Thanks to "olaxe" i know how to start the phone wthout taking out the battery.
anyway, everybodie, thanks for reading etc.
OK so you guys are still having the same issue.
Can we provide as much info as possible,
As i use DeFrost 5.7 and i just done a normal reboot and its working fine,
if its a problem with the ROM everyone would have the issue,
All i can think is a MOD you have installed is conflicting,
So some info you can provide:
What MODS are you running / installing, like Super Circle Battery, or Custom HAVS and SVS?
What version where they developed for?
i.e. are you installing MODS that where developed for an older version of defrost? as the frameworks change on each version and so do the HAVS and SVS
If your not flashing anything how about installing it?
It could be an app you used worked for an older version, and since the update its no longer working?
olaxe
thanks for the answer but i have the bootloop also when i do a manual restart without flashing anything.
i use defrost 5.7
i did a restart after flashing
Click to expand...
Click to collapse
You say you have not flashed anything? and then you said you restarted after flashing? i dont follow?
What settings are you using and apps do you have installed?
What are you doing in clockwork recovery, are you wiping then installing JUST DEFROST then letting your system start up?
or
Are you flashing a couple of things like defrost and super circle battery?
Dave,
A nephew, who ownes a desire and is "into android" from the moment of the first googlephone, was going to root my desire.
The great misstake (we found out after we've dit it) was that he used a version of unrevoke witch was mend for use with amoled and i own a slcd.
So my phone would'nt show anything anymore. Only the bootscreen when pressed vol down and power.
I've followed several advises of diehards, have put "this.zip" on the sdcard, "that.zip" and even "ifthisdon'twork.zip" shoot me.
All i got in the bootscreen was "no image" "no image or wrong image" and "version is older".
After a week a guy on a dutch forum told me to download some files to my computer, take the sdcard out of the phone, connect the phone to the computer and then type the following:
3. Typ in je commandprompt:
code:
1
2
3
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip rom210.zip
After that the phone came back to live and i was happy as a child.
After that i did the unrevoked thing with the latest version and the phone was rooted.
Put the sdcard back, formatted it whitin the phone and after that i placed the defrost 5.4 on the root of the sdcard.
Did the full wipe, dalvikwipe and flashed the defost 5.4
After a while i had the defrost up and running.
In the defrost setup i found the defrost addon.
downloaded it (all IN the phone) and after that pressed "install".
The phone shuts down a screen appears with the one droid and a box, the phone restarts and is up and running.
Then i found in the defrost setup a file "no adds"
Installed that to and then the troubles start.
Hangs in the bootscreen.
I can only start the phone when the power is completely turned of ( battery out) or with vol down, power and trackball pressed at the same time.
NOOB here. Looking for some serious help.
OK. back for round 2. Tried to install the froyo rom, followed instructions and when using system recovery,it said installing; stood that way for 2 1/2 hrs than battery died ( when started battery was full ) when I tried to restart ( had a backup battery full power ready ) it'll show me the M sign for motorola, it'll show the blur right next to it, than goes to the next screen showing the tmobile stuff, when the pink box becomes a full pink square, it reboots and doesitall over again. Tried doing a soft and hard reset, when I say ok apply update.zip, it says can't pass verification.
Also, when I plug the phone to charge, shows me a black battery with a question mark inside of it.
Is there an update.zip that I can use? As far as I know I'm still stock.
What to do, this is already my second phone, first one died when doing a backup. Don't know if I'm still good on warranty anymore. So, can I fix it or am i screwed???
Which rom you are trying to flash? In this case, you should flash a "boot only" sbf.
its update-cm-6.3.5.3-MilestoneXT720-KANG-signed
but i think its not for this phon !!
open recovery not wirking too !!
im stuck !!
I sold my old incredible to a kid. It sat for about 7months due to me upgrading to new phone. It had CM7 on it running fine when sold it. When he went to activate it, problems problems problems. I took it back him and told him I would fix it before paying me. I'm having troubles.
- No working recovery. can't get it to boot properly. I had the "5 vibrates of death" couple times.
- I'm trying a couple ruu's but when finished it will get to the lock screen, look normal, then reboot to lock screen then after a couple times will 5 vibrates then black screen.
1. I've tried [HOW-TO] Fix 5 vibrate and black screen (http://forum.xda-developers.com/showthread.php?t=1110865) I can seem to do the sdcard fix but not sure how to complete the usb fix or if that will even help me along. I can't "run terminal in anroid" because I can't get the Rom to boot up. All I can do is fastboot.... Compouter recognizes device.
2. I've tried multiple RUU's including PvilleComp's at http://pvillecomp.com/?page_id=22
3. I'm using hboot .92 and radio is 2.15.10.07.07 s-off
I realize problems like these have been asked before, I've looked through them, uesd the search button, etc.... But I'm still really stuck and would like to fix this before reimbursing kid money.
Thanks
red3razor said:
I sold my old incredible to a kid. It sat for about 7months due to me upgrading to new phone. It had CM7 on it running fine when sold it. When he went to activate it, problems problems problems. I took it back him and told him I would fix it before paying me. I'm having troubles.
- No working recovery. can't get it to boot properly. I had the "5 vibrates of death" couple times.
- I'm trying a couple ruu's but when finished it will get to the lock screen, look normal, then reboot to lock screen then after a couple times will 5 vibrates then black screen.
1. I've tried [HOW-TO] Fix 5 vibrate and black screen (http://forum.xda-developers.com/showthread.php?t=1110865) I can seem to do the sdcard fix but not sure how to complete the usb fix or if that will even help me along. I can't "run terminal in anroid" because I can't get the Rom to boot up. All I can do is fastboot.... Compouter recognizes device.
2. I've tried multiple RUU's including PvilleComp's at http://pvillecomp.com/?page_id=22
3. I'm using hboot .92 and radio is 2.15.10.07.07 s-off
I realize problems like these have been asked before, I've looked through them, uesd the search button, etc.... But I'm still really stuck and would like to fix this before reimbursing kid money.
Thanks
Click to expand...
Click to collapse
Have you tried reflashing cwm recovery thru hboot? Then wipe everything and flash a rom.
Yes I did try this. Got CMW re-installed, and when I tried to select any option in recovery just goes to picture of hat and hangs there. I press power button and goes back to CMW main menu.
I also tried a fix from your post:
cmlusco said:
Not sure where you got those instructions or files from, but there not for the incredible.
Heres what you do.
Download this file http://dinc.does-it.net/Stock_Images/4.06.605.3/PB31IMG.zip, and put it on the root of your sdcard in no folders.
Pull the battery, reinsert, and press vol down +power for 5 secs then wait for 5 mins not touching anything.
Press vol up and then wait for 20 minutes touching nothing. The phone will reboot once during the process, this is normal just let it be.
Press vol up, the phone should reboot and come up being able to see things and boot to the os normally.
Click to expand...
Click to collapse
This is where I've gotten the furthest. Got thru HTC quietly brilliant. Droid animation (red computerized looking stuff), "Droid" sound, then got to lock screen. Sit there for 5sec or so then would reboot, do the same thing over again and get to lock screen. Reboot again, then usually "5 vibes of death"
The kid does not have a phone other than this one I'm trying to fix, and they would really like it fixed and in their hands by Friday.
I just tried re-installing CMW again, and just hangs on white HTC screen, doesn't even make it to CMW menu. This is kicking my butt.
Fruitcake? Back to stock? That worked on my phone once..not sure if it was sim or not
Sent from my MB860 using Tapatalk 2
He would like back to stock. S-off or S-on. Root or no root. Just working properly.
red3razor said:
Yes I did try this. Got CMW re-installed, and when I tried to select any option in recovery just goes to picture of hat and hangs there. I press power button and goes back to CMW main menu.
I also tried a fix from your post:
This is where I've gotten the furthest. Got thru HTC quietly brilliant. Droid animation (red computerized looking stuff), "Droid" sound, then got to lock screen. Sit there for 5sec or so then would reboot, do the same thing over again and get to lock screen. Reboot again, then usually "5 vibes of death"
Click to expand...
Click to collapse
What button are you using to select things in recovery? Pressinh power on the main menu brings up the orange hat, press the trackball to select items power to go back.
I have to admit I was using the power button (used to my Rezound) but now I cannot even get CMW to work. Flashed it with the .zip in hboot/bootloader. Tried both restart and not restart after running recovery update. Both ways, phone will just hang at white HTC screen and not enter CMW anymore. Sometimes screen goes black then back to white screen or just stays on white screen indefinitely.
Could a bad battery be causing this? I'm trying 2 different ones. I'm not sure if either are bad, just trying to troubleshoot. Is there a way to check battery health on a non-bootable phone?
Any other suggestions to try? Thanks everyone for your help. I'm giving this phone just a few more hours of me fussing with before it gets retired.
UPDATE:
after battery sitting on charger all day while at work (10hrs or so), tried to boot up phone. went well. got to OS right away. I let it sit for 1/2hr to see if it would reboot or not. it stayed alive. i tested making a phone call: OK. I browsed the the XDA website for less than 1 minute, it then rebooted on me. white HTC screen then black. white HTC. then black. white HTC then rebooted fine. couple seconds later shuts off again. this time the same white HTC then black 3 times same as before. then instead of rebooting, got the 5 vibes of death.
the phone while working also asked me to update to lastest android 4.08.605.2
i'm not sure which RUU i ran to get this far, but must have been an earlier.
so i guess now i will attempt the 5 vibes fix, that's if i can get the phone booted for long enough to install terminal emulator from market and follow the steps.
any ideas guys? thanks in advance.
i did the sd card fix and attempted 5 vibes fix: http://pvillecomp.com/?page_id=33
pulled the battery. put it back in. powered on the phone. once the first white "HTC Droid Incredible" screen came up, I plugged phone into PC. instead of one audible ding from computer saying device connected, i recieved 3 very quick dings from PC and phone shuts off. no charging light indicator. if i single press power button, unresponsive still.
now i unplug device from PC, remove battery, put battery back in, hoping for it to reboot normally. instead i get white HTC then black. white HTC then black screen with no boot up.
I believe so far I've tried the GB RUU from PvilleComp and the RUU provided by cmlusco in my post #3.
I guess now I'll try the Froyo RUU from PvilleComp's site: http://pvillecomp.com/?page_id=22
It could be your battery, but usually the phone will just turn off not reboot. 4.08.605.2 does not have a PB31IMG.zip so you have to use an ruu exe, but that requires you to be able to boot. You could try the froyo PB31IMG and hope it works. My only other sugestion would be to try and upgrade your hboot to the new 1.02, and then use the htcdev site to unlock it. Then fastboot flash cwm recovery and hope you can access it.
i upgraded the hboot. unlocked via htc site. reinstalled CMW and was working fine. flashed ota stock GB. same problems still. i left him long enough without a phone, so the fixer project is ended.
thank you all for your help, greatly appreciated
red3razor said:
i upgraded the hboot. unlocked via htc site. reinstalled CMW and was working fine. flashed ota stock GB. same problems still. i left him long enough without a phone, so the fixer project is ended.
thank you all for your help, greatly appreciated
Click to expand...
Click to collapse
No problem. Sounds like it may be a hardware issue.
Hey,
Title is slightly more dramatic than my situation but basically my phone wont do anything more than loading the bootloader. Recovery doesnt do anything anymore (it just sits on the HTC screen) and the Factory Reset loads up the Reset screen for a few seconds then reboots and sits at the HTC screen.
This happened after the battery fell out while I was Restoring a backup from the Recovery menu, it was on the CRC check when the power cut. Any ideas how to get access to the recovery back?
Ironic thing is, T Mobile are meant to be ringing in 30 mins to offer me phone upgrades haha
Thanks,
-----------------EDIT------------------------
I dont know how I fixed it but I did, this may be helpful to others with a similar problem.
I restarted and took the battery out several times (7 or 8 times)
I loaded up fast boot and then clicked on recovery (which took me back to the main bootloader page)
Clicked on Recovery and took a minute or so to load.
Im guessing the fastboot did something (though im not sure what since its not connected to my computer or anything :S
I would love to know why this fixed it (if it did) and why it likely stopped working in the first place.
Did you have a stock recovery or a custom one? Arent you supposed to press volume up+power keys to get into stock restore? That's where the red HTC logo sits. I watched through a 5 minute video the first time I did it just to figure out I had to press that key combo!
Hi guys
I've searched the forum for something like this but I'm coming up empty handed. But then again, I'm freaking out a bit.
I just tried flashing ARHD 9.7.0 and I've hit a big snag... For a bit of background, I was previously running ARHD 9.4.2 with the Endeavoru-Faux123-010b3 kernal. The battery was at 35% when I started the process...
I downloaded the zip, put it onto my SD card and rebooted into CWM. No worries there.
Did a wipe/factory reset and wiped the cache aswell. No worries there.
I did NOT flash the boot.img in the zip as I believed it would work okay with the current kernel (possibly the issue)
Went to install zip from SD card and chose the zip to install. AROMA starts up and I go through the familiar install process. No problem there.
I checked the reboot now option in AROMA and let it reboot. This is where the fun begins...
I get the beepy boopy start up sound and let it sit there because, as we all know, first boot can take a while. 10 minutes later, it's stuck at the HTC One splash screen. So I thought I'd reboot into CWM and start over like I've done with other ROM/kernal incompatibilities.
So I hold down the power button, let the three lights blink and the screen go blank and hold down the volume down button. And it goes back to attempting to boot up. I've tried different combinations of holding the buttons down and letting them go and hell, I've even sat there hammering the volume down button while it starts up! Still, I can't get into the bootloader.
Obviously, no bootloader, no ADB connection so I can't go through CMD and can't re-flash the kernel.
I'm currently sitting here looking at it. The USB cable is plugged in and the orange light is lit up so I hope it's charging. I'm at a loss here guys. Please, if anyone can give me some help, I will be most appreciative.
I'm really sorry to have wasted your time. It worked eventually after about 50 tries! :laugh:
Looks like it ws a kernel incompatibility.
But out of curiosity and for anybody else who gets this problem and really can't boot into the bootloader, what would be the steps involved in recovering a device in that state? I'd rather look like a knob in public as long as something constructive comes from it. :silly:
It's a bit tricky to get into hboot after a forced reboot, I think we've all been there
Just avoid the problem altogether by flashing the boot.img inside the zip first to make sure that it boots. Once up and running, flash your custom kernel and modules.
Try this http://forum.xda-developers.com/showthread.php?t=1734365
And don't let go when reboots keep hold of buttons and it should go to bootloader
Sent from my HTC One X using xda premium