Develop Bugs

[Q] Stuck at bootscreen after every single custom ROM flash.

hi
I´ve rooted and flashed my desire several times. rooted with unrevoked3 everytime and tried different roms like leedroid 2.2d, 2.2 f and rcmixhd 0.13. First time i did it i flashed leedroid 2.2d and it worked fine. After 1,5 months running leedroid my phone rebooted due to the overheating problems that 50 % of us suffer from (i rebooted it manually several times during those months and it worked until this day).
It got stuck at the bootupscreen with white background and green HTCtext. couldn´t install RUU via windows, had to grab the PB99IMG.zip onto my SD and boot into bootloader and restore my phone this way. Then i rooted it AGAIN, and flashed rcmixhd 0.13. Success! But only until i rebooted it manually, stuck at bootupscreen again.
I restored the phone from SD with pb99img as earlier. Flashed rcmixhd again and made sure i wiped everything (dalvik, cache, formatted sdcard and created a EXT), success! Until i rebooted my desire...back again.
Now im running stock non-rooted froyo. I´m getting tired of spending the night fixing it but i still want to use senseHD and i like tweaking stuff..
Do any of u guys recognize this problem and what can i do to fix it?
If any of you are from sweden, plz answer in swedish!

Same problem here, the only way i got to install a custom rom was by installing update-cm-6.1.0-Desire-signed.zip. Then installed a custom rom by using the "Rom Manager" tool.
Downloading and flashing through recovery mode, "No, can do!"

Ok, but "update-cm-6.1.0-Desire-signed.zip" isn´t that a custom ROM? Did you install that through ROM manager?
And did you flash another ROM on top of it?

Suddenjr said:
Ok, but "update-cm-6.1.0-Desire-signed.zip" isn´t that a custom ROM? Did you install that through ROM manager?
And did you flash another ROM on top of it?
Click to expand...
Click to collapse
yes this is a custom rom, i did a normal flash first to "update-cm-6.1.0-Desire-signed.zip" (some how that worked???). Then i reflashed through the "ROM manager" tool.

Do you remember to always wipe everything in Recovery before flashing a new rom?
Seems like I always used to have a bootloop or bootfreeze when did not do the proper wipe.

remmyhi said:
Do you remember to always wipe everything in Recovery before flashing a new rom?
Seems like I always used to have a bootloop or bootfreeze when did not do the proper wipe.
Click to expand...
Click to collapse
i wiped everything even the Dalvik Cache, didn't help a thing.
Could is be that is has something to do with rom's that are not signed?

I have this same problem now, any possible sollutions?

Perdonally i would suggest to reformat your sd cards and try again. Dont forget to wipe everything.
Sent from my LeeDroided Desire HD

Happend to me once or twice.
What to do is, Turn of the phone take out battery do the neccessary wipes and formatting,
root
install clockwork mod from market, go to it and choose install recovery
install rom
install kernel (might affect it somehow)
reboot

Phone stuck at ''HTC'' boot screen after flashing ROM?

Heya guys,
New on these forums but not new to flashing roms.
I followed the guides and flashed the Android Revolution HD ROM 2.1.
Everything went well and I just pressed reboot.
Now it has been like 10 minutes and im still stuck on the white background HTC (green letters) bootscreen. Is this always taking that long after flashing or should I try to remove and reinsert the battery?
Thanks in advance!

I think I read that some people may take 10+ minutes on the first boot, but usually it only takes me around 3-5 minutes.
But you sure it's not a bootloop?

Is your clockwork updated to 3.0.0.6? Take the battery out and try again.

I assume you flashed only the rom and no themes and also did a full wipe? If so adb logcat will help a lot in diagnosing your error.
-----
Sent from my pimped up Desire HD in association with Rcmix HD v3.3.

equlizer said:
Is your clockwork updated to 3.0.0.6? Take the battery out and try again.
Click to expand...
Click to collapse
Yes it was updated to 3.0.0.6.
I tried removing the battery, same thing so I flashed another rom.
Now works like a charm.
dr.m0x said:
I assume you flashed only the rom and no themes and also did a full wipe? If so adb logcat will help a lot in diagnosing your error.
-----
Sent from my pimped up Desire HD in association with Rcmix HD v3.3.
Click to expand...
Click to collapse
Yeah did a full wipe. I flashed the full rom package from ''Android Revolution HD 2.1'' so I don't know it had a theme or not. Afterwards I did another full wipe and flashed CoreDroid HD 3.1. This one works like a charm. It's super fast and it's also good looking!
Thanks for the help

Kernal
Donno if this topic is still relevent or not, but if you don't flash a kernal specific to the rom (sense) It won't boot.

9v9 said:
Donno if this topic is still relevent or not, but if you don't flash a kernal specific to the rom (sense) It won't boot.
Click to expand...
Click to collapse
Well Roms come with the kernels so that usually isn't the problem, and when you do use kernels that aren't intended you'd quickly be able to troubleshoot and the effects i imagine could differ. When I've use wrong kernals i've been able to boot but things just wouldn't work. i.e. on hardware buttons working, extreme sluggishness etc.

Help any ideas

i cannot load any 2.3 rom on my evo none, only froyo an ideas

Did you fully wipe before you flash
sent from my HTC evolution running a freshly baked gingerbread with the 4gs in it

foresure84 said:
i cannot load any 2.3 rom on my evo none, only froyo an ideas
Click to expand...
Click to collapse
Its either your recovery, not wiping correctly, or bad downloads.

neither, i can load any froyo rom, just not 2.3

what do you think
teh roxxorz said:
Its either your recovery, not wiping correctly, or bad downloads.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1277431

foresure84 said:
http://forum.xda-developers.com/showthread.php?t=1277431
Click to expand...
Click to collapse
No, because its for the 3D. Another user tried flashing it and it just doesn't flash; luckily it didn't brick his phone.

teh roxxorz said:
No, because its for the 3D. Another user tried flashing it and it just doesn't flash; luckily it didn't brick his phone.
Click to expand...
Click to collapse
thnks i'm stumped

foresure84 said:
thnks i'm stumped
Click to expand...
Click to collapse
What he's saying is that the ROM you linked to is for the EVO 3D, not the regular EVO. Make sure that you are attempting to flash an EVO ROM and if you still have problems then please post a description of exactly what happens when you try to flash a gb ROM.
Sent from my PC36100 using XDA App

every time, i try to load a 2.3 rom, it just bootloops at the slash screen, i've done many, phones, prior to this, so i'm familiar with most of the does and don'ts (this is my tester phone), my daily evo i had no problems updating to GB
i cant load any GB roms on this evo....( it's my testing evo) strange they all do the same thing just keep rebooting on the splash screen this evo is hardware 003, the last rom on this is
android 2.21
baseband 2.15.00.09.1
kernel is 2.6.32.24- kings-havs ocUv
build bumber
caulkins evio 2 rom v1.5
software number
3.30.651.2
pri 1.77-003
prl version
60662

foresure84 said:
i cant load any GB roms on this evo....( it's my testing evo) strange they all do the same thing just keep rebooting on the splash screen this evo is hardware 003, the last rom on this is....2
Click to expand...
Click to collapse
What recovery are you using? I would suggest you install AmonRa 2.3, if you are already using it reinstall it from a fresh download. Next wipe everything except your SD, wipe system, wipe boot, sdext, ect...

dafunk60 said:
What recovery are you using? I would suggest you install AmonRa 2.3, if you are already using it reinstall it from a fresh download. Next wipe everything except your SD, wipe system, wipe boot, sdext, ect...
Click to expand...
Click to collapse
every time, i try to load a 2.3 rom, it just bootloops at the slash screen, i've done many, phones, prior to this, so i'm familiar with most of the does and don'ts (this is my tester phone), my daily evo i had no problems updating to GB

foresure84 said:
every time, i try to load a 2.3 rom, it just bootloops at the slash screen, i've done many, phones, prior to this, so i'm familiar with most of the does and don'ts (this is my tester phone), my daily evo i had no problems updating to GB
Click to expand...
Click to collapse
I wasn't trying to insult your intelligence and I understand the issue you are trying to resolve. If I recall correctly it is caused by the boot partition not being wiped. This does not cause an issue when switching from 2.2 rom to 2.2 rom because kernels are specific to the version of android (and sometimes other system elements such as sense / asop). And again, if I recall correctly, the "wipe all" command on many older recoveries did not wipe the boot partition, or wipe it completely so when you go to boot your 2.3 system with a 2.2 kernel it doesn't work and you get a boot loop. Hence my question & suggestion. Best of luck finding a fix.

please update your radio to one of the ones that came with gingerbread and try again..remember the safer way to update radios is through bootloader and not recovery...and remember the phone will reboot during the update, do not touch the phone until it reboots a second time or you may brick it..

Okay here is what I did to get GB, on my (evo tester phone)
1) booted the evo into recovery
2) factory reset 2x
3) ran VR_SUPERWIPE 2x
4) then I ran, SNS SUPER WIPE 2x, still could not run 2.3 GB at all!!, trying all kind of things for a little over a week.
5) Went through my files, found an old RUU. (RUU_SuperSonic_S_Sprint_WWE_3.26.651.6_Radio_2.15.00.07.28_NV_1.71_003_release_147044_signed) THIS IS THE ON YOU HAVE TO PLUG THE EVO INTO THE COMPUTER TO RUN.
6) Booted the evo into bootloader, then ran the RUU.
7) REBOOTED PHONE,… okay looks like stock,
8) Rebooted to bootloader s-off, is now s-on…. Dayum
9) I said F**K IT… repeated steps 1-3, then ran (deo_4.54.651.1)
10) This is the same rom I tried to install all week, now it install, verified, the version, guess what. 2.3.3.. wtf
11) I then installed, GW (signed_Team-Nocturnal_Stock_RLS.02).. (it also restored my custom splash screen)
12) IT INSTALLED NO PROBLEM… WTF…
13) STILL WITH SUPER USER PRIVIELGES
14) How is this possible with s-on

Like ca1ne said. I am 99% sure your issue is outdated radios. Update those then flash a gingerbread Rom, preferably one based on the ota 4.54.
tapatalk signature here. lovely.

tommytomatoe said:
Like ca1ne said. I am 99% sure your issue is outdated radios. Update those then flash a gingerbread Rom, preferably one based on the ota 4.54.
tapatalk signature here. lovely.
Click to expand...
Click to collapse
tried that previously, also did you read the post above?

[Q]droid gtr rom v1.0 not booting

Ok so I flashed it the first time and it was successful but noticed market was not opening so I flash the latest gapps for cyonogen mod and then everthing fc so wiped and flash and now it won't even boot it gets stuck on splash screen. Is it cause of SD card is on ext 4 or is it smellkus recovery or what?? Any help is much appreciative

Try wiping cache and dalvik then fix permissions in recovery.

Did you flash the correct ROM for your specific phone model and carrier? I had the the problem of flashing a T-Mobile ROM for my GS2 a while back, due to my excitement about using an ICS rom.

Ryan_28 said:
Did you flash the correct ROM for your specific phone model and carrier? I had the the problem of flashing a T-Mobile ROM for my GS2 a while back, due to my excitement about using an ICS rom.
Click to expand...
Click to collapse
Exactly...I've never heard of this rom for the evo. So I question it.

teh roxxorz said:
Exactly...I've never heard of this rom for the evo. So I question it.
Click to expand...
Click to collapse
no its for the evo its under evo general development it was just released

Can you boot into recovery? If so, I think your best bet is to restore a backup, delete the faulty ROM, and try reinstalling it if you want that specific ROM badly enough. That has worked for me a few times.

Ryan_28 said:
Can you boot into recovery? If so, I think your best bet is to restore a backup, delete the faulty ROM, and try reinstalling it if you want that specific ROM badly enough. That has worked for me a few times.[/Q
Yes I could go into recovery and I actually fixed the issue. I'm guessing it was the recovery itself that I was using because now I flashed Among RA recovery and now is booted and working fine. A great Tom overall. Thanks guys for your help
Click to expand...
Click to collapse

Not to bother anyone, but I was trying to run the droid GTRv2.0 ROM on my EVO 4G and it wont get past the first screen.

[Q] Incredible 2 Bootloop and ROM Problems

Hey Guys Thank You For Taking A Look At My Thread.Lets Cut To The Chase.I Have A HUGE PROBLEM with my Replacement Incredible 2.I Rooted my phone with Tacoroot,and everything was fine.Flashed Condemed CM7.2 and started realizing i didn't like it as much,so i made a BACKUP just in case i wanted to return to the CM goodness.Went to TSMTrinity's Sense 2.1 Version 4.5 S,and here's where the problem started happening. After I set up everything on my Sense 2.1 ROM,i backed it up,the screen would get to the boot animation,get past the boot animation,id see my lock screen for 1 SECOND,and then it would start the bootup again.seeing as this was a problem,i WIPED All Cache and Factory Reset/Wipe Data on My Revolutionary Recovery.Then,I Restored the 2.1 Backup that i created and everything was fine again.Then again,i decided to Flash Mikrunny's Sense 3.5 ROM,which after i set up,worked fine,UNTIL YESTERDAY.I was driving in my car yesterday,listening to music on The STOCK HTC Music app on Sense 3.5,and the phone rebooted on its own.And it would not stop until i took the battery out.I got home,charged the battery for a bit,(shut down that is),then headed to recovery.I took out the SD card and rebooted the phone,but no luck.tried this rebooting process for an hour,until i decided to wipe cache and factory reset to my 2.1 ROM BACKUP.it works,but i just wanna know,am i doing something noobingly wrong when backing up and restoring roms? Also,i use Revolutionary's Backup,or I think its called Nandroid,to do backups and restores,and ROM MANAGER to edit their names and delete them.Also,an added side to his problem,when i boot to the Hboot screen,when it loads,for a few of the items it says,missing or wrong image.could that be the problem?? THANK YOU SO MUCH WHO REPLIES AND HELPS.:crying:

DroidUser_Wind said:
Hey Guys Thank You For Taking A Look At My Thread.Lets Cut To The Chase.I Have A HUGE PROBLEM with my Replacement Incredible 2.I Rooted my phone with Tacoroot,and everything was fine.Flashed Condemed CM7.2 and started realizing i didn't like it as much,so i made a BACKUP just in case i wanted to return to the CM goodness.Went to TSMTrinity's Sense 2.1 Version 4.5 S,and here's where the problem started happening. After I set up everything on my Sense 2.1 ROM,i backed it up,the screen would get to the boot animation,get past the boot animation,id see my lock screen for 1 SECOND,and then it would start the bootup again.seeing as this was a problem,i WIPED All Cache and Factory Reset/Wipe Data on My Revolutionary Recovery.Then,I Restored the 2.1 Backup that i created and everything was fine again.Then again,i decided to Flash Mikrunny's Sense 3.5 ROM,which after i set up,worked fine,UNTIL YESTERDAY.I was driving in my car yesterday,listening to music on The STOCK HTC Music app on Sense 3.5,and the phone rebooted on its own.And it would not stop until i took the battery out.I got home,charged the battery for a bit,(shut down that is),then headed to recovery.I took out the SD card and rebooted the phone,but no luck.tried this rebooting process for an hour,until i decided to wipe cache and factory reset to my 2.1 ROM BACKUP.it works,but i just wanna know,am i doing something noobingly wrong when backing up and restoring roms? Also,i use Revolutionary's Backup,or I think its called Nandroid,to do backups and restores,and ROM MANAGER to edit their names and delete them.Also,an added side to his problem,when i boot to the Hboot screen,when it loads,for a few of the items it says,missing or wrong image.could that be the problem?? THANK YOU SO MUCH WHO REPLIES AND HELPS.:crying:
Click to expand...
Click to collapse
1..update your recovery which is probly clockwork mod....i suggest you get your phone usable for a few minutes and go to 4ext.net and download and install that..its touch based recovery or also check out twrp if you want an alt if you dont like it
2....update your radio ...newest one can be found in the venom rom thread i think there are directions there http://forum.xda-developers.com/showthread.php?t=1953899
3.....wipe everything ....check out my wipe script in the dev section if you want max cleanification http://forum.xda-developers.com/showthread.php?t=2013242
4...flash what ever rom...if you like sense use viper i hear good things or check out my incredibly paranoid rom or all the other roms ..pick your poison

chillybean said:
1..update your recovery which is probly clockwork mod....i suggest you get your phone usable for a few minutes and go to 4ext.net and download and install that..its touch based recovery or also check out twrp if you want an alt if you dont like it
2....update your radio ...newest one can be found in the venom rom thread i think there are directions there http://forum.xda-developers.com/showthread.php?t=1953899
3.....wipe everything ....check out my wipe script in the dev section if you want max cleanification http://forum.xda-developers.com/showthread.php?t=2013242
4...flash what ever rom...if you like sense use viper i hear good things or check out my incredibly paranoid rom or all the other roms ..pick your poison
Click to expand...
Click to collapse
DUDE.THANK YOU so MUCH FOR REPLYING.Ill try what you told me tonight,and ill let you know how it goes down.thanks again chills.:good:

chillybean said:
1..update your recovery which is probly clockwork mod....i suggest you get your phone usable for a few minutes and go to 4ext.net and download and install that..its touch based recovery or also check out twrp if you want an alt if you dont like it
2....update your radio ...newest one can be found in the venom rom thread i think there are directions there http://forum.xda-developers.com/showthread.php?t=1953899
3.....wipe everything ....check out my wipe script in the dev section if you want max cleanification http://forum.xda-developers.com/showthread.php?t=2013242
4...flash what ever rom...if you like sense use viper i hear good things or check out my incredibly paranoid rom or all the other roms ..pick your poison
Click to expand...
Click to collapse
What OP wrote applies to me as well. I am looking for something better than aerovan's CM9 (which has been my DD), and thought I would give Viper a try. Without fail, bootlooping (which I could have guessed since I did tacoroot and this seems to be an issue with sense based roms).
That said, I tried steps 1 through 4 and the bootlooping stopped in Viper - it goes through startup and just shuts down before leaving the boot screen. One strange thing that I noticed is that the ICS Firmware/radio with Viper (which I loaded in CWM), wouldn't load in 4ext. Maybe I'll give paranoid a go if I can't resolve this bootlooping issue in Viper! I hope OP has better luck.

U don't flash radio in cwm..look for a how to.. can't explain I'm working sry
Sent from my Incredible 2 using xda app-developers app

I'm not as knowledgeable as Chilly, but a thought did occur to me. if the cm9 rom included a kernel on the flash and then you went to a sense based rom that didn't include a kernel that could cause a problem. I believe that I read that cm using a kernel that is asop based while sense roms use a different based kernel. You may check to see what kernel you have and then check for the recomended kernel for that rom and flash that kernel. don't forget to wipe.

Jasonp0 said:
I'm not as knowledgeable as Chilly, but a thought did occur to me. if the cm9 rom included a kernel on the flash and then you went to a sense based rom that didn't include a kernel that could cause a problem. I believe that I read that cm using a kernel that is asop based while sense roms use a different based kernel. You may check to see what kernel you have and then check for the recomended kernel for that rom and flash that kernel. don't forget to wipe.
Click to expand...
Click to collapse
All of the roms come with a kernel for our phone, but certainly, don't flash a sense kernel with aosp or vice versa after rom flash. Chilly is right. Flashing a newer radio should fix the problem and the radio is flashed with a PG32IMG.zip in the bootloader, not in the recovery.

gtdtm said:
All of the roms come with a kernel for our phone, but certainly, don't flash a sense kernel with aosp or vice versa after rom flash. Chilly is right. Flashing a newer radio should fix the problem and the radio is flashed with a PG32IMG.zip in the bootloader, not in the recovery.
Click to expand...
Click to collapse
Good call. When chilly said you don't flash kernels in recovery I hit my head. I flashed the radio, but now my challenge is getting back into recovery since I renamed the file and bootloader always finds it and wants to reboot or I load CM9 which stays on flash screen. I'll figure something out, maybe with adb. Thanks.

Power down, pop the sd out, boot to recovery, rename file, profit.

gtdtm said:
Power down, pop the sd out, boot to recovery, rename file, profit.
Click to expand...
Click to collapse
Didn't think of that. adb did the trick though. In business with VenomInc!
Thank you all.

digitalshepard said:
Didn't think of that. adb did the trick though. In business with VenomInc!
Thank you all.
Click to expand...
Click to collapse
good lucking going back to aosp lol

almost thesame problem
chillybean said:
U don't flash radio in cwm..look for a how to.. can't explain I'm working sry
Sent from my Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
i made a stupid mistake of flashing radio in recovery, in fact the radio is for Samsung at&t and now my phone vibrates it doesnt show htc quietly brilliant, only vibrates and orange light with black screen untill i pull out the battery... i was able to return to stuck and it can only boot if its connected to power, it doesn't read sd card while android is booted and in recovery to, only in bootloader it reads sd... error in mounting if i try to... i flashed RUU.exe 2.3.3 and 2 other RUUs for my droid inc 2 but it keeps vibrating... please help me!!! thanks

I made the same mistake when i first gained s-off for my dinc2. the thing with the venom rom tho is if you ever want to go back to aosp ull need to gets chill's anti-venom zip and flash it through recovery because doing a normal wipe wont do the trick. also a helpful trick that worked for me with roms if i ever start getting boot loops i go into recovery from the bootloader menu and i wipe the dalvik cache under advanced and then wipe the chache under mounts and storage and it always works like a charm for me. but ive also learned that you have to be careful which kernel you flash with the rom of your choice because not only will it cause lags if you happen to get past the boot animation to the main screen but in some cases it can cause breaks in your framework like your wifi data etc. im not an expert tho those are just suggestions that im familiar with because theyve already happened to me before. hope this helps in any way.