Develop Bugs

[Q] Bootloop flashing rom HELP needed

Been flashing roms all day to figure out what's going on.
I'm currently back to a stock 2.2 rom odexed running clockwork recover.
Trying to flash to Virus' new rom. In attempts to flash the rom, I get stuck on the white htc evo 4g screen. I've wiped the dalvik cache, battery stats, cache, factory reset in that order before installing the rom.
I have no problems flashing other roms, I don't know what the issue is. Can someone point me in the right direction?
Thanks for any help.

ATownI20 said:
Been flashing roms all day to figure out what's going on.
I'm currently back to a stock 2.2 rom odexed running clockwork recover.
Trying to flash to Virus' new rom. In attempts to flash the rom, I get stuck on the white htc evo 4g screen. I've wiped the dalvik cache, battery stats, cache, factory reset in that order before installing the rom.
I have no problems flashing other roms, I don't know what the issue is. Can someone point me in the right direction?
Thanks for any help.
Click to expand...
Click to collapse
I have no experience with this ROM, but you may want to try RA Recovery. I personally have never had a problem with clockwork, but many say they have. I might also be a damaged copy of the ROM. In that case check the md5 sum to see. Hope this helps.

ATownI20 said:
Been flashing roms all day to figure out what's going on.
I'm currently back to a stock 2.2 rom odexed running clockwork recover.
Trying to flash to Virus' new rom. In attempts to flash the rom, I get stuck on the white htc evo 4g screen. I've wiped the dalvik cache, battery stats, cache, factory reset in that order before installing the rom.
I have no problems flashing other roms, I don't know what the issue is. Can someone point me in the right direction?
Thanks for any help.
Click to expand...
Click to collapse
When I did my first root/ROM-flash a few days ago, I was stuck on an infinite bootloop with Fresh Evo because I didn't properly unlock my NAND via Toastch's Part 2 root instructions. If this is your first custom ROM, try re-doing Part 2, which is the full NAND unlock (with the new PC36IMG.zip file).

ScaryBugThing said:
When I did my first root/ROM-flash a few days ago, I was stuck on an infinite bootloop with Fresh Evo because I didn't properly unlock my NAND via Toastch's Part 2 root instructions. If this is your first custom ROM, try re-doing Part 2, which is the full NAND unlock (with the new PC36IMG.zip file).
Click to expand...
Click to collapse
Turns out that I didn't have full nand unlock, didn't know there was a partial lol... Say that because I've flashed at least a dozen rom/kernel/mod setups with clockwork Mod with no problems.
I went through and did the full nand unlock and switched to amon ra recovery and that solved my problems.
virus' rom is a beast you guys should check it out.
Anyway thanks for the help, I appreciate it.
Sent from my HTC EVO

phone touch screen wont register my touch after rom flash

my first rom was evervolv for droid incredible. i decided to go with magnolia rom.. it all worked up to getting to the lock screen after flashing it. the lock screen wouldnt read my touch.. and i switched back to evervolv. it worked after i did. then i decided to go with Warm Z TwoPointTwo... and it did it again.. i'm getting sick of the same ole same old and i need help.. anyone have suggestions to fix this mess so i can get the roms i want???

Are you saying when you flash a different ROM, the touchscreen is not working, and if so, are you running the kernel that comes with the ROM, or something other before first boot?
Are you fully wiping data/cache/dalvik prior to flashing the other ROMs?
Do you have ample space on your SD card?

make sure you clear data/cache/dalvik and all that jazz.
you can also try flashing a new kernel in recovery, that might do something...

yeah i flashed a different rom to my phone and then it messes up.. the screen doesnt read my touch.. i restored my evervolv for it and it works fine again.. but i dont know how to flash a "kernel" that would work with the rom i want.. doesnt that come with a new custom rom?? and what is dalvik? i just press factory reset or whatever..

MatalicZ said:
yeah i flashed a different rom to my phone and then it messes up.. the screen doesnt read my touch.. i restored my evervolv for it and it works fine again.. but i dont know how to flash a "kernel" that would work with the rom i want.. doesnt that come with a new custom rom?? and what is dalvik? i just press factory reset or whatever..
Click to expand...
Click to collapse
Dalvik is under the advanced tab in recovery. I do data, cache, dalvik before flashing a new row. I do cache, dalvik, battery(also under advanced) before flashing kernel. Dl krnel to root of sd card, flash in recovery like rom. I nvr use rom mgr for flashing anymore. Make sure u use sense kernel for sense rom, aosp kernel for aosp roms. Couple of good threads on kernels. Chads kernels work great for my phone, but its preference. Any problems just use the search function on xda, cant find answer then just ask. Good luck.
yes, i am one who likes to flash then flush

This sounds like the same issue you would get with a kernal that is not compatable with a rom. or a theme/mod ment for a different rom. I run evervolv myself and if I try anything else i need to clear/factory reset everything before i flash

i'm very grateful for your guys help. but.. i just ran into that same fix again. i flashed another kernel so i could run the rom i want and it still did it.. so i need to know the kernels that are compatible with roms.. specifically the one i want. (right now its Warm Z TwoPointTwo) but if there is a thread with this info i will try and find it. and also do i flash the kernel for the rom after i flash the rom or do i flash the rom then boot up then go to recovery and apply the kernel.. i'm sorry if i'm sounding too noobish.. i'm learning. very slowly lol

You are flashing Sense kernel with Sense ROM, yes? The kernel is flashed AFTER the ROM install.
Sent from my ADR6300 using XDA Premium App

How do I go back to the stock ROM?

I want to go back to a stock ROM till sense 3.5 ROMs start having 4G.

kariuki said:
I want to go back to a stock ROM till sense 3.0 ROMs start having 4G.
Click to expand...
Click to collapse
Ok, have you read the stickies? They are there to help you.
If you have installed a custom rom, the process for installing the stock rom is exactly the same: download the stock rom zip, put on sd card root, boot into recovery, make nandroid backup, wipe everything, and flash the zip.

Here is a stock rooted ROM, wipe everything except SD card 3x and flash it http://forum.xda-developers.com/showthread.php?t=1319881
There are Sense 2.1 and Sense 3.0 ROMs that have 4G. It's only Sense 3.5 ROMs that don't have 4G.
MikG is my personal favorite for a Sense 2.1 + 3.0 hybrid, and it has 4G and everything working. It is ridiculously stable.
For a full Sense 3.0 ROM, I use Synergy-Kingdom or r3chargeD. Both are quite stable and have 4G.

sitlet said:
Ok, have you read the stickies? They are there to help you.
If you have installed a custom rom, the process for installing the stock rom is exactly the same: download the stock rom zip, put on sd card root, boot into recovery, make nandroid backup, wipe everything, and flash the zip.
Click to expand...
Click to collapse
tropicalbrit said:
Here is a stock rooted ROM, wipe everything except SD card 3x and flash it http://forum.xda-developers.com/showthread.php?t=1319881
There are Sense 2.1 and Sense 3.0 ROMs that have 4G. It's only Sense 3.5 ROMs that don't have 4G.
MikG is my personal favorite for a Sense 2.1 + 3.0 hybrid, and it has 4G and everything working. It is ridiculously stable.
For a full Sense 3.0 ROM, I use Synergy-Kingdom or r3chargeD. Both are quite stable and have 4G.
Click to expand...
Click to collapse
Thank you for the quick and helpful replies. I meant 3.5, sorry. I've installed the stock rom.
...I'm going to look for another ROM now, I forgot how much stock sucked.

why cant i

hey all so i know this is a bit of a noob question but i was just wondering why you cant flash a 2.2 rom over a 2.3 rom but you can flash a 2.4 rom over a 2.3 rom i mean i just understand why you cant does it have something to do with the recoveries?

matrixzone5 said:
hey all so i know this is a bit of a noob question but i was just wondering why you cant flash a 2.2 rom over a 2.3 rom but you can flash a 2.4 rom over a 2.3 rom i mean i just understand why you cant does it have something to do with the recoveries?
Click to expand...
Click to collapse
Why can't I....complete the question in the subject....LOL
We don't have 2.4 so I guess you mean 4.0 meaning CM9, and that requires full wipes. What 2.2 ROM are you trying to flash? You should be able to flash a Froyo ROM over a Gingerbread ROM BUT data is not compatible so you need to do a Factory Data reset to clear all data first. Also wipe dalvik cache.

Custom Rom help

Hey All
I'm in need of some help. For some reason this whole SBF thing is completely confused me
My Defy
System Version: Moto_Version.34.30.3601.MB525.Vodacome.en.GB
Firmware Version: 2.2.2
Baseband Version: EPU93_U_00.59.02
Build number: JEM_3.4.3-36-1
(Unsure if these will help)
Anyway, I'm wanting to put CM7 or another custom rom onto my phone, but they all seem to be version 2.3 or so, but I want to be able to drop down to my original rom in case I need to return the phone for something
I did the official update to 2.2.2 from 2.1, which was lucky as with my 2.1 stock rom Clockworkmod couldn't read my memory card, seemed to be a common glitch with the SBF version it had, but it seems fine now
I read somewhere to use a Nordic nandroid backup for some reason, cant remember, just found it in my download folder from attempting to get clockworkmod to work on 2.1, restored the image onto my phone, which worked fine, but that seemed to be a no risk flash
So now I'm confused on how to proceed to putting on a custom rom, I fear that I'm going to **** up something, or going to run into issues if I try change to different custom roms
I'm possibly just over thinking what is meant to be done, and it is way simpler than it seems at the moment
anyone have some advice?

Using nordic as a base is old, custom runs like cm7 work on any base.
As long as you don't flash full sbf of gingerbread builds via rsdlite you can always go back to your original 2.2 by flashing full sbf through rsdlite.
Okay coming to installation of custom roms, first thing is to root it. You can use super one click for that. Then install defy 2ndinit after that boot menu and recovery.then you are all set to install custom roms.
For cm7, down load the zip and install through cwm.
Restart phone and as soon you see blue led press volume down, this would put you into boot menu.then select custom/stable recovery. Select wipe user data/factory reset.then go to advanced and select wipe dalvik cache. Come back and select install from zip and give cm7 zip, after finished reboot. It will now boot with cm7, first boot will take few minutes 2-3. It is generally cm7 first boot is in loop, if you are stuck just remove battery and put back and restart.
You can go through cm7 installation thread for better clarity.
Enjoy flashing!
Sent from my MB526 using XDA App

Thanks for the reply
So basicly I just flash the rom straight in clock work mod, no need for fixed SBF's or anything?
Do I need to back up/make full SBF of my stock SBF or something?
Is CM7 7.1 based on Froyo, and you'd just flash it straight from the memory card in Clockwork mod?
Or have I missed the point and meant to flash a fixed SBF to allow for gingerbread or any roms and then reflash 2.2 back on when I want to retore stock again?

Well I went ahead and installed Motogamer, which I downloaded last night and its working fine, but it seems to be based on the froyo kernal
I'm still a little confused as CM7.1 looks like its gingerbread, unsure of the downgradeability to my froyo stock rom, but this rom had no issue when I used my nandroid backup to restore to my stock rom
Thanks for the help

CM7.1 stable is android 2.3.7 with froyo kernel. And there is CM7.2 nightlies with both froyo and gingerbread kernels. I use the defy+ CM7.2 with gingerbread kernel from Quarx (this gives me better battery life) http://quarx2k.ru/, since i have redlens defy.
You dont have worry about the downgradability as long as you dont flash full sbf of gingerbread using rsdlite. All the dev custom roms have no problem in downgrading back to your original stock froyo. Look at if there is any WARNING IN RED regarding downgradability when you download any rom.
There are good number of ROMs to try, whenever you change ROM remember to do full wipe (factory reset and wipe dalvik cache), back up your apps and other information before you do this. If you are upgrading to night revision of same ROM, for example next nightly of CM7.2 we dont have do to full wipe, just cache and dalvik cache wipe would be fine.
If you like Stock ROM, try MS2ginger3.0 which gives awesome battery life and with full blur functionality if you like.

Awesome, thanks
I'm really keen to try more custom roms out, really happy so far with this new one at the moment, but will probably try CM7 soon
Thanks for the advice, not sure I'll go back to stock rom for a long time, just feared that I'd **** something up and not be able to return to stock if needed to
Really keen to start seeing what android really has to offer now