[Q] Whats wrong with my HTC hero? - Hero CDMA Q&A, Help & Troubleshooting

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

Related

HERO to CYANOGEN?

G1 is stuck on T-Mobile G1 screen for over 10 mins HELP! I wiped everything.
If you want help, I recommend telling us specifically what you did (what Hero you were on, what version of Cyan you flashed, what recovery you're using)
But without knowing any of that, I'm going to suggest (assuming you have Amon_Ra's latest recovery) that you boot to recovery and wipe everything a couple times, then flash Cyan. By everything, I mean Factory Reset, Wipe EXT, Wipe Dalvik-Cache, and to be safe, Repair EXT. And do all those at least once, factory reset again, and flash.
guitargler said:
If you want help, I recommend telling us specifically what you did (what Hero you were on, what version of Cyan you flashed, what recovery you're using)
But without knowing any of that, I'm going to suggest (assuming you have Amon_Ra's latest recovery) that you boot to recovery and wipe everything a couple times, then flash Cyan. By everything, I mean Factory Reset, Wipe EXT, Wipe Dalvik-Cache, and to be safe, Repair EXT. And do all those at least once, factory reset again, and flash.
Click to expand...
Click to collapse
Yes Amon RA latest recovery. I wiped all that but i didnt do the repair part. Im trying to flash the latest cyanogen.
Well it's best to be safe rather than sorry, so wipe, wipe, and wipe again. afaik, wiping will do you no harm
guitargler said:
Well it's best to be safe rather than sorry, so wipe, wipe, and wipe again. afaik, wiping will do you no harm
Click to expand...
Click to collapse
Hahah alright thanks for the quick reply and i was on mlign 3.3
Don't forget the Htc Recovery first also
JAguirre1231 said:
Don't forget the Htc Recovery first also
Click to expand...
Click to collapse
Yup! Thanks i was trying to figure it out all night i wiped and wiped like he stated. Then i flash the HTC recovery and got cyanogen to work again. BTW how do i delete a thread? Like this one for instance. Keep it clean and less cluttered on XDA
androidboi209 said:
Yup! Thanks i was trying to figure it out all night i wiped and wiped like he stated. Then i flash the HTC recovery and got cyanogen to work again. BTW how do i delete a thread? Like this one for instance. Keep it clean and less cluttered on XDA
Click to expand...
Click to collapse
You don't mods will, and it wasn't flamed or anything so it'll probably stay for awhile

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

[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?

Problems after factory reset

I've majorly screwed up. I'm using a samsung galaxy ace s5830. After partioning my sd card I found that I couldn't root my phone since cwm was not allowing it. So I got frustrated and did a factory reset. Now my phone will not get passed the samsung intro and the blinking samsung sign. Please help
Reflash a rom with odin, it will wipe anything wrong (just remember to wipe data, wipe cache, and wipe dalvik cache)
Thanks will do so. can you shed some light as to how a simple factory reset got me into a boot loop
sjg2797 said:
Thanks will do so. can you shed some light as to how a simple factory reset got me into a boot loop
Click to expand...
Click to collapse
After wipe data/factory reset, bootloops can be solved by wiping cache and dalvik cache.
If something got messed in the kernel while trying to flash the root zip, then wiping everything will still keep an error, maybe that's what caused the bootloop, this is fixed with a fresh odin flash.
Check that your root zip is compatible and thay you use the correct recovery to flash it (sometimes it must be done through stock recovery, sometimes through cwm)

[Q] Installed CM10 but didnt wipe the data now its stuck at boot, what do I do?

I did everything right exceept for forgeting to wipe the data, now its stuck at boot, the cyanogenmod logo just stays on the screen spinning. Not sure whst to do. I tried wiping the data/factory reset through android recovery but that didnt work so I'm ouot of ideas
jarentzen3 said:
I did everything right exceept for forgeting to wipe the data, now its stuck at boot, the cyanogenmod logo just stays on the screen spinning. Not sure whst to do. I tried wiping the data/factory reset through android recovery but that didnt work so I'm ouot of ideas
Click to expand...
Click to collapse
How long did you let to boot logo spin? It can take a while before it gets past that the first time you run it.
Have you wiped cache and dalvik cache? Those usually fix the issue. You could also try fixing permissions to see if that helps too.
When you say you wiped in android recovery, do you mean safestrap?
jarentzen3 said:
I did everything right exceept for forgeting to wipe the data, now its stuck at boot, the cyanogenmod logo just stays on the screen spinning. Not sure whst to do. I tried wiping the data/factory reset through android recovery but that didnt work so I'm ouot of ideas
Click to expand...
Click to collapse
if I'm right, you should wipe in the custom recovery instead of stock recovery.

Categories

Resources