Been installing custom roms for a while now.
Whenever i try to install a new rom ( tried several ones, next sense, leedroid , defrost) i get stuck on the first white boot screen with the green htc screen.
Iv used full wipe, cache, wiped sd partition, formatted sd card, different sd card.
I can install an older version of next sense rom, but that is about all i can do.
im on bootloader v0.8, used the latest version of clockwork mod ( have tried with several versions) iv tried booting with the sd card out.
iv tried so many different times with different variations but none have been successful other than the nextsense v4.0 that i can boot to, or an nandroid back up of nextsense v4.0.
Any help?
I had the same this morning after fixing a recovery boot problem (re-pushing the reboot file to the system/bin/ directory on the device).
I resolved the hanging white screen problem by rebooting (via volume down + power button) into recovery with Clockwork Mod (v2.5.0.7 for Desire) and manually reflashed (N.B. without wipe!) the already installed ROM (I had upgraded to Nextsense 6.0 earlier that morning without difficulty, so reflashed that version).
Maybe this helps, but sounds like you may have already passed this station...
Good luck!
After that my Desire booted up normally.
Edit: Bootloader is v0.75
Can you get any response from running
#adb logcat
??
If it sits there saying "waiting for decice" for ages then yeah, something isn't right (possibly a bad flash of boot parition), but if you get anything, even a bootloop of sorts, the output may help narrow down whats going on!
I'm stuck here too. After I flash a custom ROM it just sits there after booting for the first time. I've tried so many ROMs, but I haven't even gotten to see a single one, yet!
Related
I was originally running the rooted sense 2.2 rom and I attempted to switch to Leedroid using Rom Manager's "Install from SD Card". That went fine until it crashed at the end of the install process in recovery... Then it wouldn't boot (stuck at white background with green HTC). I attempted to redo the r5 root flash as it was the only other rom I had and I could still get into fastboot, but now (I'm assuming) it's stuck on the radio update part of the flash in step1... The fastboot flash zip command completed with an OKAY, but it hasn't yet rebooted - all I have is a black screen with the HTC logo and a full green progress bar.
I know unplugging it while doing a radio update is a big no-no, so what should I do? It's been sitting there like that for the last 20 minutes.
Edit: Well, after waiting for a while I bit the bullet and just unplugged it... And it works fine. No idea why it froze, though...
Hey guys,
I went to flash a new stable build of Froyo on my Desire this morning.
And i backed up using Clockwork, and then the ROM all installed fine. But once the phone had booted up, it stayed on the custom boot logo, despite the keypad lighting up, the green charge LED coming on and me being able to lock and unlock the phone.
So i figured that this was a problem and went to back to restore my old ROM and carry on like i have done many times before. However once i have booted into Clockwork, and gone to the recovery section, i select my most recent backup and the device then says "No Files Found" in the recovery zip.
And when i try to install update.zip from my SDCard the device just flashes up with installation text for about 2 seconds then vanishes and goes back to the clockwork menu having done nothing
What can i do?
i wouldnt worry about it too much
your phone completely works and youre not restricted of any access
seeing that clockwork is not finding any files have you tried making a new backup?
have you tampered with the recovery lately?
if recovery is not finding any files then maybe there is a problem with it, and if i were you i'd reroot my phone with unrevoked to re-install recovery.
if your recovery actually just does not work it could mean that the recovery image is corrupt, this can be fixed by installing a RUU (note that this will unroot your phone but re-install the recovery image).
if this is not the case then im sure im soon to be corrected by someone more knowledgeable than me
Well, i wiped the Cache and Data and now the phone boots up and functions fine, however both mobile internet and Wi-Fi both dont work, but i figure this is just the rom i am using.
So i'm just gonna reroot, sideload clockwork and what not and then try putting the Desire HD rom on it haha.
Thanks for the help
I flashed the incredibly re-engineered v2.2 rom a week or so ago and it worked great till today it was giving me a force close on a bunch of apps, so i restared it and it still didn't help. Did a *228 and when it restated it just goes to the black screen that says htc incredible Loading then after several seconds it flashes blank for half a second then says same thing. I used rom manager to flash it. I've also used virtuous and skyraider 3.5. I'm good at computers but android is new to me as i've only had this fon 2 months. I have to do a battery pull to restart it. Any Ideas on how to fix this? I can boot into recovery but havn't been able to do anything... Never used it so not sure what to look for but like when i click recovery or factory reset, nothing happens. Oh, and i did a search but didn't come up with similiar problem.
htc incredible s-off
radio 2.15.00.07.28
Flash a different rom.
sent from my Dinc
How do I do that? When I boot in recovery mode I have option of fastboot, recovery, clear storage, simlock, and factory reset. When I select recovery it goes to bootloader, reboot, reboot bootloader, and power down, with reboot highlighted. Wen I select that it boots like normal than gets stuck on boot up screen.
Try fixing permissions through Rom Manager first, if not I would reinstall the rom. Be sure to do a full wipe, don't just flash over your previous rom.
If neither of those work, I would follow this thread
http://forum.xda-developers.com/showthread.php?t=786436
Flash back to stock 2.2 and see if your phone starts acting the same way. If so I would take it back to verizon. If everything seems ok, re-root and flash JUST the rom and apps that you want, no kernel, themes, anything extra yet. See if that fixes the problem.
I made sure I did full wipe when I installed it so that shouldn't b problem. The issue Is i can eve get to rom manager because he Fon wont load past the boot image. And its out of warany so vzw prolly wuldnt be much help.
mennotech said:
I made sure I did full wipe when I installed it so that shouldn't b problem. The issue Is i can eve get to rom manager because he Fon wont load past the boot image. And its out of warany so vzw prolly wuldnt be much help.
Click to expand...
Click to collapse
I would re-download a different ROM (making sure you don't have a corrupt download), check the MD5 SUM's to verify integrity of your download, mount USB Storage in Recovery to transfer the file to your USB card (when phone is off, hold down the Power and Volume Down buttons at the same time), wipe all user data/factory reset and Dalvik, and then reflash the ROM of your choice.
mennotech said:
I made sure I did full wipe when I installed it so that shouldn't b problem. The issue Is i can eve get to rom manager because he Fon wont load past the boot image. And its out of warany so vzw prolly wuldnt be much help.
Click to expand...
Click to collapse
Go to that link in my post, download the PB31IMG from the 2.2 Stock OTA, put it on the root of your SD card, boot into the bootloader and let it update. You will go back to being completely stock and unrooted. Root it and then try installing the rom again.
I tried to flash the latest (at that time) Synergy Rom on Sunday. I had been trying out Sense 3.0 Roms since being on Cyanogen for 3 months and low in behold after flashing and rebooting, the phone hung on the splash screen, wouldn't even get to the boot animation. I pulled the battery out to reboot and kept doing the same things. So then i just figured I go through bootloader to get to recovery. When I hit recovery, the phone hung on the splash screen and thus I was forced to report my phone lost because I use it for work and was able to get a new one the next day (had to pull out my old bb 8530). The phone charges, but it will not do anything when powering on, or hitting recovery but go to splash. Once again when i try to go into recovery, it won't get there.
Any Help Please.
dels28 said:
I tried to flash the latest (at that time) Synergy Rom on Sunday. I had been trying out Sense 3.0 Roms since being on Cyanogen for 3 months and low in behold after flashing and rebooting, the phone hung on the splash screen, wouldn't even get to the boot animation. I pulled the battery out to reboot and kept doing the same things. So then i just figured I go through bootloader to get to recovery. When I hit recovery, the phone hung on the splash screen and thus I was forced to report my phone lost because I use it for work and was able to get a new one the next day (had to pull out my old bb 8530). The phone charges, but it will not do anything when powering on, or hitting recovery but go to splash. Once again when i try to go into recovery, it won't get there.
Any Help Please.
Click to expand...
Click to collapse
You need to reflash your recovery. Is it just hanging at the splash screen, or is it rebooting at the splash screen?
Download this PC36IMG I attatched (it's Amon RA recovery v2.3). Place the file on the main directory of your sd card (you'll probably need to take the SD card and use a card reader to get the file on the card....or put the card in another phone with an sd slot if you have access to one...just get the PC36IMG.zip file on your card). Once it's on the card and card's back in the phone, boot to your bootloader. It should scan and find the PC36IMG then ask you to update...select vol up to say yes. Should finish in 10-15 seconds. Then when it asks you to reboot, say no. Now from the bootloader menu, choose recovery. Do you successfully boot to recovery now, hopefully?
Ok, I got that, I put cyanogens latest release candidate from 5/5 on the card, I have Ra's recovery up, i guess i jumped ahead and the install aborted, tips please.
dels28 said:
Ok, I got that, I put cyanogens latest release candidate from 5/5 on the card, I have Ra's recovery up, i guess i jumped ahead and the install aborted, tips please.
Click to expand...
Click to collapse
So what part aborted? When you were flashing the rom? Just to clarify, you did successfully get the recovery flashed, right? Now it's the rom you're having trouble flashing?
If so, I'd be sure that you don't have a corrupted download. Check the md5 checksum, or simply try redownloading it and trying again. Good luck.
It starts to install the ROM, then it all of a sudden aborts after getting 50-75 percent complete. I'm trying RC 7.3 now, wala, it worked, well i have an extra evo now i need to figure out what to do with it. BIG THANKS.
dels28 said:
It starts to install the ROM, then it all of a sudden aborts after getting 50-75 percent complete. I'm trying RC 7.3 now, wala, it worked, well i have an extra evo now i need to figure out what to do with it. BIG THANKS.
Click to expand...
Click to collapse
You're welcome, glad you got it squared away.
As far as having two Evo's...just be careful. If I'm not mistaken, when you report a phone lost or stolen to Sprint, they will make the ESN bad. I'd check into that, to make sure that one them doesn't have a bad ESN. I didn't even catch that part of your OP that you had already gotten a new one, lol.
So I guess that will make the phone useless if I give it to my father in-law.
turn it back in n say u found it...in other words the right thing
after doing amon ra3.0.7 nandriod
sorry if question is silly. but last night i flash from cwm to amon ra 3.0.7 everything went good, rebooted phone fine. i rebooted into recovery did a nandriod back evrything fine. i did a reboit to recovery wipe everything except sd card and flash a custom rom and rebooted fine. i went back into revovery did a nandriod backup went fine. i went to reboot my phone and its stuck at splash screen. I followed Hip Kat instruction to the letter. di i miss something
any help would be greatly
I've been running a Sense ROM the last few days and wit the 3 different Sense Kernels I've flashed, I got stuck on the ROM's Splash Screen, had to do a battery pull and reboot and it was fine.
That could be your problem right there.
HipKat said:
I've been running a Sense ROM the last few days and wit the 3 different Sense Kernels I've flashed, I got stuck on the ROM's Splash Screen, had to do a battery pull and reboot and it was fine.
That could be your problem right there.
Click to expand...
Click to collapse
it was me i jump the gun after i flashed custom rom. i di all kinds of mods then i tried to nandriod. md5 check sum mismatch, so i just wiped everthing except sd card, reflashed custom rom its all good now. By the way thanks for your input about cwm being junk you were right amon ra is awesome, no more cwm for
Hi!
So just a quick background. I have S-OFF'd and flashed a custom ROM on my mates Desire HD few years back and have a bit knowledge about the device.
Today I showed him some of the 4.1-4.2 ROMs available for DHD. In TWRP I did a nandroid backup of his current Blackout ICS and flashed CM10.1. Everything went just fine, but the ROM was not the right for him, so I tried Venom Sense 4.1. I did a clean install on the Venom ROM and wiped everything in Aroma.
Apparently I was not focused enough and the Aroma installation failed with just the wipe. No ROM installed. Phone rebooted with no ROM and the caught stuck while booting. I thought this was no biggie and I would just restore the backup from TWRP.
Then all suddenly went to hell in a hand basket. Phone was/is unable to boot into bootloader with any vol+/- combination. It won't boot into recovery ether. Just straight into the ROM, which is not there -> bootloop.
TL;DR No ROM installed, unable to boot into bootloader or recovery. ADB/Fastboot showing no signs of connection.
Did I just buy myself a dead DHD and an angry friend?
EDIT: SOLVED. So, issue was solved by 1000 times randomly pulling the battery and pressin vol up and down. 999 tries straight booted into the OS, but 1000th try somehow got me into the hboot. No idea why or how.