HELP_Stuck on Boot with Flashed ROM - Desire General

Hey guys, I am afraid I have quite a problem.
I have flashed roms before (latest one was Defrost 1.8), but then got stuck into a bootloop. I then re-rooted my desire, and now I cannot flash any non-stuck ROMs. They all install just fine, but then get stuck on the green HTC screen.
Any Ideas what I Could do? I did factory reset, Cache Wipe, Dalvik Wipe... and tried flashing again. It just gets stuck in the first HTC screen, with the screen turned on at maximum brightness...
Any ideas???'
Thanks

Wipe and reflash a stock HTC ROM
Root it
Then reflash upto Defrost 1.8 again
See if that makes any Diff and post up and update

I have done that before, provided using MODACOs update.zip Stock rom does count.
I started from that again. You think I should unroot and root again?
I just wiped, and plugged into USB mode, entered Recovery, and installed update.zip provided (Stock but rooted sense 2.1 rom)
BTW. Tanks a lot for your help

If your on Stock but a rooted ROM try making a nandroid backup so you can flash to that quickly again and then have a shot with a Cooked ROM, if it fails nandroid covers

I have done that multiple times, this is exactly when I get stuck on that green boot screen, with nothing happening anymore. (I have waited over 15 minutes...)
I always have to go back to recovery, and nandroid restore to my 2.1....

Have you updated the Radio or anything recently??

Nope.... Nothing fancy really. I had fixed the permissions through Rom Manager... that's about it....

Related

Anrdiod 2.2 Update Problem

i recently updated to froyo for evo 4g but as i noticed it started reboot frequently.... i tried clearing everything and still as it loads back up it still does it i tried eferything and this thing just keeps restarting... i tried restoring my old nand backup still .... i searched everywhere and still no solution.... please i need help desperatly!!!!!
what rom are you using? did you change kernals? do you overclock?
I am assumign you are rooted since you said you restored an old nandroid.
did you do a full wipe before upgrading if you did which recovery did you use?
If you used clockwork recovery you may try using Amon RA and wipe with ti and reflash.
i was told to wipe dev. cache and wipe factory reset and take the battery out put it back in 15 secs or 30 and it should work...did the trick for a while but once im getting all my setting how i want it with my contacts and my apps downloading.... it starts the problem all over... SMH....
i used nandriod to recover...when all other failed i was told to use clear storage....so now everytime i turn my phone on i have 2.2 but it restarts the phone for no reason...how do i use amon ra and wipe with ti? i think i havent tried that....and im using build 3.36.651.6 (Rooted) Odexed rom....
i really need some help with this anybody got a related post with a solution or a fix for this my phone still turning off and on...
Flash the eng-PC36IMG zip in bootloader, then restore.

[Q] (Help Please)RA revovery and ENG hboot in one flash after UR Forever

I flashed this file and after wards every time that I tried to boot it would go to hboot. Someone suggested flashing a custom rom. I flashed fresh and thought this fixed my problem but it would just bootloop the fresh splash screen. nand restores say that they are successful but I still can not get past hboot or the fresh splash screen. PLEASE HELP!
I'm assuming you're talking about this PC36IMG.zip from this thread? http://forum.xda-developers.com/showthread.php?p=7978758#post7978758
If so, it seemed to work fine for me...make sure you're flashing the one in post #18 not the OP.
the only thing I can guess is to make sure you wipe your cache and dalvic before flashing the rom and/or restoring a nand backup.
I had flashed fresh 3.2 and I flashed the pc36img file and I didn't even need to flash the rom again or my nand backup.
I would pull the battery, boot to bootloader, check what hboot you have to see if the pc36img flashed correctly, then go into recovery and make sure the recovery updated to 1.8 (look at the bottom of the screen in recovery), then do a factory data reset, wipe data twice, wipe dalvic twice, and then try to restore your backup and report back.
You mention you cant get past hboot or the fresh flash screen. Do you mean fresh's boot animation?
when I've flashed fresh roms the boot animation usually is on for about 5 minutes before it proceeds. Make sure you're waiting long enough once you get to that point.

[Q] absolutely cannot flash custom rom

I have been searching like crazy through every thread on every forum and cannot find anyone with a similar problem. I had CM7 running fine then everything started force closing. I wiped data/cache and dalvik cache and reinstalled CM7 and now cannot get past the Splash screen. I went into HBoot and flashed the stock RUU went back to stock re-rooted tried everything again and cannot get past the splash screen again. Tried to flash a stock PB31IMG with s-off already and that booted fine. Flashed clockwork through a PB31IMG and got to recovery tried to wipe and install and same results. Did everything I just did back to stock then flashed the alternate recovery same issue. Anyone have any idea why I cannot get a custom rom going?
whyteboyello said:
I have been searching like crazy through every thread on every forum and cannot find anyone with a similar problem. I had CM7 running fine then everything started force closing. I wiped data/cache and dalvik cache and reinstalled CM7 and now cannot get past the Splash screen. I went into HBoot and flashed the stock RUU went back to stock re-rooted tried everything again and cannot get past the splash screen again. Tried to flash a stock PB31IMG with s-off already and that booted fine. Flashed clockwork through a PB31IMG and got to recovery tried to wipe and install and same results. Did everything I just did back to stock then flashed the alternate recovery same issue. Anyone have any idea why I cannot get a custom rom going?
Click to expand...
Click to collapse
Did you try fixing permissions? I hear doing that can help fix constant fc's. You can do it either through ROM Manager or in recovery. The only way I know how to do it in recovery is in Clockworkmod, as I have not tried out amon_ra. Advanced > Fix Permissions.
Sent from my Droid Incredible running CM7.0.3.
Have you tried flashing peanut and formatting internel storage, wiping sd card and reformatting to fat32? What ever you do, never restore data, it will cause issues.
Sent from my ADR6300 using XDA App
whyteboyello said:
I have been searching like crazy through every thread on every forum and cannot find anyone with a similar problem. I had CM7 running fine then everything started force closing. I wiped data/cache and dalvik cache and reinstalled CM7 and now cannot get past the Splash screen. I went into HBoot and flashed the stock RUU went back to stock re-rooted tried everything again and cannot get past the splash screen again. Tried to flash a stock PB31IMG with s-off already and that booted fine. Flashed clockwork through a PB31IMG and got to recovery tried to wipe and install and same results. Did everything I just did back to stock then flashed the alternate recovery same issue. Anyone have any idea why I cannot get a custom rom going?
Click to expand...
Click to collapse
did you reroot after flashing to stock just b.c. your s-off and flash a recovery dont mean you can flash a rom successfully... i would run the ruu again then reroot with unrevoked...... then wipe and flash again.. if that dont work then you prob have a harware problem
Are you doing wipe data/factory reset, wipe cache, and wipe dalvik cache?
Sent from my ADR6300 using XDA App
Thanks
Hey guys thanks for the response, I was about to give up and stay on stock sense and for the hell of it tried root wipe and install again and it worked. No clue what was causing me issues so I am probably going to stay on my current setup for now haha

[Q] boot loop on reboot

Hey guys,
Got a very weird problem here. I have previously flashed a CM10 nightly to my One X (international) and everything has been fine for around 3 weeks. Decided i wanted to try our the ViperX ROM. Previously upon flashing this ROM it just bootlooped but after another try with a slightly different method, i managed to get it to boot and all was merry. After titanium restore i rebooted, and this once again put me into a bootloop. Cannot get the ROM to boot. Why is this!!! Switched back to CM10. :good:
You need to do
fastboot flash boot boot.img
You may have done
fastboot boot boot.img
BenPope said:
You need to do
fastboot flash boot boot.img
You may have done
fastboot boot boot.img
Click to expand...
Click to collapse
Still doesnt boot man, im sure i flashed the boot image properly. This is the rundown of my flash process:
1: install from sd
2: in recovery, factory reset, wipe cache, wipe dalvic cache
3: Boot into fastboot and flash the boot.img
4: Reboot.
So it booted but into viper X, but after restoring with Titanium i was unable to get it to boot again.
I also tried "fastboot erase cache" to no avail
In fastboot type fastboot erase cache
Jamekerr said:
So it booted but into viper X, but after restoring with Titanium i was unable to get it to boot again.
Click to expand...
Click to collapse
Did you restore system apps or data?
Where does it stop booting, what is on the screen?
With tb, make sure you restore user apps only, none of the system apps.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
eyosen said:
With tb, make sure you restore user apps only, none of the system apps.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
Sorry forgot to mention I also used the "fast book erase cache" command.
As for titanium I restored all user apps and data and now that you mention it that could be the problem. I'll have another crack tomorrow and let you know.
Main reason I want to switch is I need much better battery life than CM10 but only temporarily. Can anyone recommend viperx as being a significant improvement?
BenPope said:
Did you restore system apps or data?
Where does it stop booting, what is on the screen?
Click to expand...
Click to collapse
It comes up with "HTC" vibrates then the viper crawls across the screen and it stops at the "htcONE" logo.
Restored apps and app data and guess what. Still doesn't boot. WHY! Going to just try apps, no data at ALL. Will report back.
I dunno why it won't start, double check you have the right boot.img (download it again and flash it again), in recovery erase cache and dalvik cache.
same issue
Hi i am also getting the same problem, i used the viper rom and others but it goes past the HTC logo looks as though it works but the lock ring is froze up and then it reboots itself over and over doing the same thing each time. Ive tried One_X_All-In-One_Kit_v1.2 and the manual CMD fastboot tutorial i dont know what to do to fix this, can anyone help me please?
EDIT* I seem to have it working now (fingers crossed), i used 'Nocturnal_Special_Edition_4.0_Odex' so thx to their good work that i now have a working rom for my phone phew
EDIT 20 MIN LAter* OK looks like i did something i shouldnt, it seemed to work, i made a change in the settings and then it rebooted and continued to reboot over and over so i tried installing a rom again and now it just stays at the htc quietly brilliant screen, what have i done this phone is now not so brilliant as its looking more and more that ive goosed it Any help apreciated.
boot.img
Help please
Hello,
I have 1x (CID 203) unlocked and rooted with cwm recovery. I had Cyanogenmod 10 nighly on it, well in hope of no bugs like in CM10 I flashed this http://forum.xda-developers.com/showthread.php?t=1763240 to it. Well it seemed to work a moment but then the device started rebooting randomly. I couldn't boot to recovery (strange?), the recovery screen flashed less than a second and the phone started to boot normally again. After a few tries (and reflashing recovery) I luckily got into the recovery. Tried to restore a nandroid backup which I made earlier yesterday. CWM said that the restore was successful but the device didnt boot anymore. Only shows htc logo and cyanogenmod loading screen. But nothing happens. Well, then I flashed Android Revolution HD 10.3. (with wiping the system data and so on) but it wont load any longer than the htc one logo screen. Rom installed fine and I flashed the boot.img.
Now I'm able to get into recovery and fastboot and charge my phone but how could I safely and surely return my phone to stock or make the ARHD work without completely bricking it? I'm thinking that relocking my device is not very safe if the RUU fails to install. What do you think? Can the firmware updates cause this problem to happen? Can I flash ARHD 9.7.2 to my device? Too bad I can't ask these questions in the ARHD thread....
In bootloader my phone says
Code:
hboot-0.94.0000
radio 1.1204.104.14
Any advice is highly appreciated, I'm not ready to bury my phone yet
Edit. ARHD 9.7.2 flashed correctly. Any ideas why the ARHD 10.3 keeps bootlooping? Yes, I have flashed the correct boot.imgs.
BenPope said:
I dunno why it won't start, double check you have the right boot.img (download it again and flash it again), in recovery erase cache and dalvik cache.
Click to expand...
Click to collapse
If I restore apps only it does boot however any sort of data and it refuses to. Very annoying as I am not able to retain texts accounts etc. I have a feeling it's because I originally backed up on a jellybean ROM and the data just doesn't want to work on ics
Squbbe said:
Hello,
I have 1x (CID 203) unlocked and rooted with cwm recovery. I had Cyanogenmod 10 nighly on it, well in hope of no bugs like in CM10 I flashed this http://forum.xda-developers.com/showthread.php?t=1763240 to it. Well it seemed to work a moment but then the device started rebooting randomly. I couldn't boot to recovery (strange?), the recovery screen flashed less than a second and the phone started to boot normally again. After a few tries (and reflashing recovery) I luckily got into the recovery. Tried to restore a nandroid backup which I made earlier yesterday. CWM said that the restore was successful but the device didnt boot anymore. Only shows htc logo and cyanogenmod loading screen. But nothing happens. Well, then I flashed Android Revolution HD 10.3. (with wiping the system data and so on) but it wont load any longer than the htc one logo screen. Rom installed fine and I flashed the boot.img.
Now I'm able to get into recovery and fastboot and charge my phone but how could I safely and surely return my phone to stock or make the ARHD work without completely bricking it? I'm thinking that relocking my device is not very safe if the RUU fails to install. What do you think? Can the firmware updates cause this problem to happen? Can I flash ARHD 9.7.2 to my device? Too bad I can't ask these questions in the ARHD thread....
In bootloader my phone says
Code:
hboot-0.94.0000
radio 1.1204.104.14
Any advice is highly appreciated, I'm not ready to bury my phone yet
Edit. ARHD 9.7.2 flashed correctly. Any ideas why the ARHD 10.3 keeps bootlooping? Yes, I have flashed the correct boot.imgs.
Click to expand...
Click to collapse
Try the fast boot erase cache command and see if that solves the boot issue. If not make sure in recovery your have cleared cache partition performed a factory reset and also cleared the dalvik cache. Again if none of these work try re flashing the boot.img or perhaps try another rom that is known to be stable.

[Q] Stuck after ROM flash

I have the Sprint S3 with 4.1.2. Last night I rooted it and it worked fine. I then flashed CWM Recovery and rebooted, all was fine. Tried to put on Liquid Smooth rom and didn't have gapps, attempted to flash gapps but came up with error. Got fed up with it and tried to flash the Synergy Rom. I cleared dalvik and cache, made a backup and flashed. Went through the whole process and auto rebooted afterwards. Went to SAMSUNG on boot and screen went black before finishing and will not go further. I can get into stock recovery but not CWM Recovery. I'd like to have the liquidsmooth rom on there but i also downloaded the stock 4.1.2 rom just in case. How can I get past this to get into either CWM recovery or somehow flash a rom from Odin? I'm stuck.
jsaye2002 said:
I have the Sprint S3 with 4.1.2. Last night I rooted it and it worked fine. I then flashed CWM Recovery and rebooted, all was fine. Tried to put on Liquid Smooth rom and didn't have gapps, attempted to flash gapps but came up with error. Got fed up with it and tried to flash the Synergy Rom. I cleared dalvik and cache, made a backup and flashed. Went through the whole process and auto rebooted afterwards. Went to SAMSUNG on boot and screen went black before finishing and will not go further. I can get into stock recovery but not CWM Recovery. I'd like to have the liquidsmooth rom on there but i also downloaded the stock 4.1.2 rom just in case. How can I get past this to get into either CWM recovery or somehow flash a rom from Odin? I'm stuck.
Click to expand...
Click to collapse
So you were able to get into the custom recovery (CWM) a couple of times before flashing Synergy Rom, but now it's reverted to stock recovery? When you turn your phone off and hold Volume up, menu, and power it boots into the stock recovery? I've never heard of that happening before.
The best way is to re-do your root process through Odin a-la qbking77's tutorial. This will install CWM again and then you can flash away. Make sure you check your md5sums on the Rom files you downloaded before flashing them. That's the most common cause of bad flashes around these parts.
topherk said:
So you were able to get into the custom recovery (CWM) a couple of times before flashing Synergy Rom, but now it's reverted to stock recovery? When you turn your phone off and hold Volume up, menu, and power it boots into the stock recovery? I've never heard of that happening before.
The best way is to re-do your root process through Odin a-la qbking77's tutorial. This will install CWM again and then you can flash away. Make sure you check your md5sums on the Rom files you downloaded before flashing them. That's the most common cause of bad flashes around these parts.
Click to expand...
Click to collapse
I've ended up fixing it but had to flash stock 4.1.1 on it from Odin and then it automatically went to 4.1.2 after reboot. Thanks
But yes, it was going to CWM just fine before I flashed Synergy after Liquidsmooth. Thats how I put on Synergy. But at least it was just a soft-brick.
Did you wipe (everything) between flashes? Even roms of the same version can have issues if you flash one over the other
By everything I mean /system, /data (factory reset), dalvik cache, and cache

Categories

Resources