Database Develop

roms not flashing correctly.

this is on my own phone and has nothing to do with the other thread I posted.
I thought I'd try out open ecclair, so i wiped and flashed it, but I was still stuck on the "tmobile g1" screen for about an hour.
thats when I pulled the batteryand tried again.
same problem.
I pulled the battery, wiped, and flashed cyanogen.
still stuck on g1 screen.
I pulled the battery, wiped, and flashed superD
now I'm on super-D, but I have apps that aren't supposed to be in superD but actually come in cyanogen (Log Collector and Slideme Market)
whats going on?

...you didn't full wipe or did you. Try flashing again.

Wipe EXT
Wipe Dalvik
Wipe Factory Reset
Repair EXT
Try that.

Macrophage001 said:
Wipe EXT
Wipe Dalvik
Wipe Factory Reset
Repair EXT
Try that.
Click to expand...
Click to collapse
yeah pretty much...

thanks.
I think the problem with the apps is that I probobly forgot to wipe ext, although I usually do.
and I've never wiped Dalvik. what is it?
and I've never repaired ext either but it always seemed to work fine.
those two are probably why I couldn't change the rom.

I actually dont know much about the Dalvik-Cache except for...well its a cache lol. So yeah I always wipe everything

HELP!!!! I am stuck under "htc" while booting

Phone: CDMA Hero
ROM: Freshhh2.0d
Recovery Image: 1.5.2
Well the story begins:
Last week installed Freshh2.0d rom everything worked perfect...... until I tried to screw with the lock screen (tried to install vanilla lock screen and for some reason it messed the rom soon I assign password to lock screen!!) To even realize it was the lock screen I had to reboot and flash the rom several times (maybe like 8-10!!!) then finally it started working!!!
But after the last flash, I started having force close issues with several core apps, like touch screen, google apps etc..... so this morning decided to reflash the rom one last time and see if it fixes the issues.... but I feel like I have done more than just that..... here is what I have done....
1. Re-flashed Freshhh2.0d rom, after reboot got stuck at "htc" screen that comes up after all the animations
2. I wiped or did a factory reset and flashed again..... same result
3. Wiped again and this time I wanted to download the rom again and while downloading rom, I stumbled up on new recovery image 1.6.2
4. I applied new recovery image with wiped or factory reset phone, rebooted in recovery and flashed rom
5. Again stuck under htc screen after all animations....
6. Went back to recovery image 1.5.2 and flashed rom
7. After all this the net result is still same...... stuck in htc screen....... not booting the phone!!!!
Can somebody point me to the right direction???? I am even thinking about trying a different rom and see if that comes up!!!

Ok, first go back to the 1.6.2 recovery.
Next, wipe the following:
Factory Reset
Dalvik Cache
SD: EXT (if you were using apps2sd this will nuke your apps, so be sure you have a backup).
Then reflash Fresh 2.0d (or whatever ROM you want to use).
If you still have problems I recommend doing the RUU to return it to stock and start over.

Same with me I have been trying to flash fresh 20d. On my first reboot it always gets stuck on HTC screen. I'm comming from Fresh 2.0b2. Don't know what else to try. Though I can do Nandroid and get back to Fresh2.0b2

smw6180 said:
Ok, first go back to the 1.6.2 recovery.
Next, wipe the following:
Factory Reset
Dalvik Cache
SD: EXT (if you were using apps2sd this will nuke your apps, so be sure you have a backup).
Then reflash Fresh 2.0d (or whatever ROM you want to use).
If you still have problems I recommend doing the RUU to return it to stock and start over.
Click to expand...
Click to collapse
I do not have back up of my apps and I am using apps2sd, is there a way at least I can get a list of apps in my sd? I tried to do cd /data/app under shell and it won't let me ......

bigd1231 said:
Same with me I have been trying to flash fresh 20d. On my first reboot it always gets stuck on HTC screen. I'm comming from Fresh 2.0b2. Don't know what else to try. Though I can do Nandroid and get back to Fresh2.0b2
Click to expand...
Click to collapse
When in doubt, always wipe before going to a new rom. When NOT in doubt, wipe anyhow.
Sure you can go to a new rom sometimes without a wipe...but 80% of the time you do much better going clean.
Also, how long have you waited on the HTC screen? I've seen that take upwards of 10 minutes.

I have waited as much as an hour. Also, I did do a Factory reset many times. I just don't know what else to try.

if none of that works. just use the right ruu for your device.

bigd1231 said:
I have waited as much as an hour. Also, I did do a Factory reset many times. I just don't know what else to try.
Click to expand...
Click to collapse
Did you wipe dalvik and SD: ext as well?
You should wipe everything there's an option for.

NO I actually didn't do that I'm going to try right now and post back THANK YOU Didn't wipe SD: ext

bigd1231 said:
NO I actually didn't do that I'm going to try right now and post back THANK YOU Didn't wipe SD: ext
Click to expand...
Click to collapse
Wipe all 3 again, then reflash.
Factory
Dalvik
SD: ext
Then let us know how it goes.

Your problems are caused by apps2sd... plain and simple. Fresh 2.0d's release notes tell you that you are going to have to wipe your sd:ext (as well as data wipe). That is because there were several versions of apps2sd floating around before and they aren't all compatible.
http://geekfor.me/new-release/fresh-20d/
Secondly make sure you are using ext3 and not ext2.
http://geekfor.me/faq/apps2sd/

Yes It worked Finally. I wiped all Three and reflashed it and waited 15 mins and it worked.

yes it worked. I wiped all 3 and worked

smw6180 said:
Wipe all 3 again, then reflash.
Factory
Dalvik
SD: ext
Then let us know how it goes.
Click to expand...
Click to collapse
Great! that did the trick!!!

Flipz, there is one shortcoming with 2.0d (not sure if its something inherent to the original rom itself!) When I use my corporate email on my Hero it forces me to assign password and when I do that and lock my screen phone stops responding there after. This happens when I am using vanilla screen lock update.... I can't unlock for anything.... any idea how to fix this?

Glad to hear you're both up and running.

Phone refuses to boot after new ROM

EARLY this morning I decided to try out a new ROM. I flashed Clockworkmod recovery and installed Fresh 2.1.1 from my SD card. Now my phone is stuck in a constant loop of trying to boot up. This same process went fine when I installed Damage Control a few weeks ago. Only thing I've done since then was partition my SD card (also done thru Clockwork app). I would really appreciate any help. Thanks in advance

ksharp5580 said:
EARLY this morning I decided to try out a new ROM. I flashed Clockworkmod recovery and installed Fresh 2.1.1 from my SD card. Now my phone is stuck in a constant loop of trying to boot up. This same process went fine when I installed Damage Control a few weeks ago. Only thing I've done since then was partition my SD card (also done thru Clockwork app). I would really appreciate any help. Thanks in advance
Click to expand...
Click to collapse
Wipe everything (data, dalvik, and your SD card) and reflash. Yes, I know you just partitioned that's probably the problem.

This sounds like a silly question, but would a complete wipe UNDO the partition? Or is that just a way to get the system to wipe ext?

ksharp5580 said:
This sounds like a silly question, but would a complete wipe UNDO the partition? Or is that just a way to get the system to wipe ext?
Click to expand...
Click to collapse
it just wipes the ext it doesnt undo the partition

I'm in recovery mode right now. Wipe Dalvik is in advanced options. On main screen I see wipe data/factory reset. Is that the one I want?

ksharp5580 said:
I'm in recovery mode right now. Wipe Dalvik is in advanced options. On main screen I see wipe data/factory reset. Is that the one I want?
Click to expand...
Click to collapse
You want both data and dalvik at a minimum. If you want to try to reflash without reformatting your card, do the following:
Boot to recovery
Wipe data/factory reset
Wipe dalvik
Flash the ROM
(optional but I always do this anyway - takes 10 seconds and is extra insurance)
Wipe data/factory reset
Wipe dalvik
Boot
If that doesn't work, I'd recommend removing your microSD card and formatting it cleanly on your PC (fat32 format) and re-copying the ROM and attempting the above again.
Give it a go and report back.

if you're using the latest version of clockwork recovery, it's not compatible with a2sd on any rom but darch. I suggest godspeed or amon ra 1.6.2 if not running DD 2.7

Question, why would u wipe after installing the rom?
Sent from my ADR6300 using XDA App

no reason to, but most roms it won't hurt anything, as it only wipes /data and /cache, however, some roms do add apps to /data/app on flashing, and you would be removing those apps then.

Is that a Hero thing or is that in general?
I just had someone test the ClockworksMod on Darktremor Apps2SD for a Nexus One and it worked just fine.
danaff37 said:
if you're using the latest version of clockwork recovery, it's not compatible with a2sd on any rom but darch. I suggest godspeed or amon ra 1.6.2 if not running DD 2.7
Click to expand...
Click to collapse

I don't know. Clockwork mod gave me a lot of problems. Stick with amon ra based recoveries and had much fewer problems.
Sent from my Hero CDMA using XDA App

Actually, was just looking back into it, and I may be wrong on it's compatibility, but it is just in my experience that it doesn't work too well for whatever reason. I like the idea of some of the features it offers, but it never worked right on backing up and restoring for me, and I may have just assumed that was the reason. Our I may have confused it with amon ra 1.7
Sent from my Hero CDMA using XDA App

I use Godspeed and been really happy with it. I was just curious since I've never used ClockworksMod.
danaff37 said:
I don't know. Clockwork mod gave me a lot of problems. Stick with amon ra based recoveries and had much fewer problems.
Sent from my Hero CDMA using XDA App
Click to expand...
Click to collapse

[Q] Whats wrong with my HTC hero?

So I used to have CyanogenMod running on my phone, but it was messing up so I decided to flash the FroYo rom. My hero is sprint and the rom was for sprint phones. But when I flashed the rom my phone wouldn't start up. It just stays on the big "HTC" screen. Ive tryed everything. Any help?http://media.xda-developers.com/images/smilies/frown.gif

Did you wipe (everything!) before flashing the other ROM?

As andythegreenguy asked, did you wipe everything prior to flashing?
Also, how long has it stayed on the HTC screen? Booting a new ROM for the first time can take as long as 15 minutes...

How to wipe?
c00ller said:
As andythegreenguy asked, did you wipe everything prior to flashing?
Also, how long has it stayed on the HTC screen? Booting a new ROM for the first time can take as long as 15 minutes...
Click to expand...
Click to collapse
What is the correct procedure to wipe everything off? If I plan to reinstall the same ROM?

mumbaiyya said:
What is the correct procedure to wipe everything off? If I plan to reinstall the same ROM?
Click to expand...
Click to collapse
Boot into recovery, and do a full factory wipe

Getting stuck there is a bootloop.
It's usually caused from not wiping the cache(s).
New Rom:
(Boot into Recovery)
Wipe Data/Factory Reset
Wipe Cache
Wipe Dalvik
I like to wipe Batt Stats but you don't really need to.
Just Factory Reset, wipe both caches.
I assume the recovery is similar to the evo's, I've never seen the hero's recovery so it might be different.
A new rom will take a little longer than usual because it needs to rebuild the caches while its on the HTC screen.

xNotta said:
Getting stuck there is a bootloop.
It's usually caused from not wiping the cache(s).
New Rom:
(Boot into Recovery)
Wipe Data/Factory Reset
Wipe Cache
Wipe Dalvik
I like to wipe Batt Stats but you don't really need to.
Just Factory Reset, wipe both caches.
I assume the recovery is similar to the evo's, I've never seen the hero's recovery so it might be different.
A new rom will take a little longer than usual because it needs to rebuild the caches while its on the HTC screen.
Click to expand...
Click to collapse
That's correct

[Q] CM7 bootloop initial boot

Well, i am stuck at bootlooping after flashing CM7.1 onto my friend's device, we've tried many times flashing it with different ways, but it seems to get stuck everytime at the bootscreen, i know the initial boot can take up to something like half an hour but after 2,5 hours we gave up, downgraded to 2.3.4 again using odin, and tried again on a different way (different recovery)
this is how we flashed it:
-made sure we had 2.3.4
-wiped data and cache with CWM 4.0.0.idk (the odin package for this CWM was included in the thread)
-installed CM7, everything went smooth
-rebooted, and then it got stuck
I really want to get this to work for him, any help from you guys?
is it because i wiped after flashing ?

Well the process should be like this :
1. Wipe data - Wipe cache - Wipe Dalvik-cache - Wipe Battery stats
2. Flash ROM
3. Wipe data - Wipe cache - Wipe Dalvik-cache - Wipe Battery stats

So twice?
He's not here right now with the device, but i want to gather enough info for tomorrow to retry

`leon said:
So twice?
He's not here right now with the device, but i want to gather enough info for tomorrow to retry
Click to expand...
Click to collapse
Yeah, it is safe to wipe before and after flashing.
And you're sure you did wipe dalvik-cache right ?

errrrmm, i don't remember, i think i did tho, i will, as again, retry tomorrow with also wiping dalvik

Well, as for me, when something went wrong, i flashed my device back to stock froyo first.
Then flash GB, Flash CWM, clear data and cache, flash the rom, clear data and cache again.
Reboot.
That's it
Sent from my GT-S5570 using xda premium

K, he's not here, i will give it a try now, fingers crossed :x
i know though what went wrong before

`leon said:
K, he's not here, i will give it a try now, fingers crossed :x
i know though what went wrong before
Click to expand...
Click to collapse
Always explain what went wrong, if someone with the same issues is reading the thread they'll know what not to do then.
So, what went wrong before?