so i've installed both the new cyanogen and new eclair roms, my phone still crashes often, very often- especially when just browsing through menus and whatno.... it crashes to the point where the only way to "reset" is to pull the battery, obviously. of course, i did a wipe before, installed the new radio and ota, and then installed the new rom. i always do a wipe before installing a rom, and this problem has still not been resolved. like now, with the new eclair, after pulling the battery to reset the phone, i get a "application android keyboard (in.process.com.android.inputmethod.latin) is not responding" when the phone boots up.what gives? any advice would be greatly appreciated, thanks.
Cobra281 said:
so i've installed both the new cyanogen and new eclair roms, my phone still crashes often, very often- especially when just browsing through menus and whatno.... it crashes to the point where the only way to "reset" is to pull the battery, obviously. of course, i did a wipe before, installed the new radio and ota, and then installed the new rom. i always do a wipe before installing a rom, and this problem has still not been resolved. like now, with the new eclair, after pulling the battery to reset the phone, i get a "application android keyboard (in.process.com.android.inputmethod.latin) is not responding" when the phone boots up.what gives? any advice would be greatly appreciated, thanks.
Click to expand...
Click to collapse
So when you get the input FC why do you reboot?
You know you can press Force-Close right?
I think you should consider Super-D & Wesgarner, those are faster than cyan.Cyan is good for stability but the others have the plus that blood-craved speed.
Ace42 said:
So when you get the input FC why do you reboot?
You know you can press Force-Close right?
I think you should consider Super-D & Wesgarner, those are faster than cyan.Cyan is good for stability but the others have the plus that blood-craved speed.
Click to expand...
Click to collapse
i do force close it, but the phone constantly crashes... so everytime eclair finishes booting up, i get the same FC message, again. and the phone seems to crash from google apps, like messaging, dialing, etc.
i tried the WG build about 2 versions ago, same issue...
Cobra281 said:
i do force close it, but the phone constantly crashes... so everytime eclair finishes booting up, i get the same FC message, again. and the phone seems to crash from google apps, like messaging, dialing, etc.
i tried the WG build about 2 versions ago, same issue...
Click to expand...
Click to collapse
Your problem appears to be a bad flash. I never had that problem with the Eclair ROMs. Do a full wipe of the system and ext partition and reflash. I too would recommend starting with another ROM first... SuperD/Dwang are great... I'm sure Wes Garner's builds are solid too.
Cobra281 said:
so i've installed both the new cyanogen and new eclair roms, my phone still crashes often, very often- especially when just browsing through menus and whatno.... it crashes to the point where the only way to "reset" is to pull the battery, obviously. of course, i did a wipe before, installed the new radio and ota, and then installed the new rom. i always do a wipe before installing a rom, and this problem has still not been resolved. like now, with the new eclair, after pulling the battery to reset the phone, i get a "application android keyboard (in.process.com.android.inputmethod.latin) is not responding" when the phone boots up.what gives? any advice would be greatly appreciated, thanks.
Click to expand...
Click to collapse
How large is your swap? I have seen similar behavior when the swap gets to be too large.
uansari1 said:
Your problem appears to be a bad flash. I never had that problem with the Eclair ROMs. Do a full wipe of the system and ext partition and reflash. I too would recommend starting with another ROM first... SuperD/Dwang are great... I'm sure Wes Garner's builds are solid too.
Click to expand...
Click to collapse
will try that, what's the easiest way to format the ext partition in cyanogen 1.4 recovery?
this:
mount /system/sd
rm -rf /system/sd/*
or this?
mke2fs -j /dev/block/mmcblk0p2
cloverdale said:
How large is your swap? I have seen similar behavior when the swap gets to be too large.
Click to expand...
Click to collapse
my sd card is only 1 gig, and it's not a high class, so i can't use anything other than ext... and 729mb is fat, the rest is ext...
bump guys, for questions above. did a full format and wipe, still the same problem with the new cyanogen
Have you tried another rom other that Cyanogen and Eclair.. why not try Dwangs or superD or WED those are well Stable and fast
Update your radio and spl if not update. Helped me.
The LatinIME has issues in the eclair ROMs thats why its been removed from some of them. If doing CM ROMs, after a wipe have you ever tried reflashing the HTC image first just to try and clean stale things?
This is a typical issue that you can get when installing ROM's that are built by people who really don't have any idea what they are doing and/or are pushing the limits SO far that it breaks things.
Seems to me that what you need is a MILD mod ROM. Look at "TheOfficial" roms posted by enomther. They are stock roms with community apps2sd and an expansion pack that adds in a few power user features rather than completely borking the whole system.
alright, so i installed RA recovery, did a full wipe, formatted and partitioned the SD card properly and made a 64mb swap, flashed new radio and spl properly(flash radio, reboot, flash spl, reboot) and then flashed the new Super D v1.8. it worked fine yesterday, today my phone started crashing. it crashes(sometimes, but often) while doing the same stuff; trying to unlock the phone with the unlock pattern, and sometimes while trying to use the search box. sometimes, i can't even get to the unlock screen(as it's crashed), so i'd have to pull the battery.
any more help\advice would be greatly appreciated.
Related
I'm just wondering what's so good about the Modaco ROMS... From what I was reading it's the best thing to ever happen to Hero but I've flashed it and it actually seems slower/laggier than my stock ROM... should this be?
My stock ROM was 2.73.XX but I can't remember the exact build number. I'm using Modaco 3.0... are there any other ROMS out there I should consider trying? I'm looking for the fastest and most responsive ROM out there. I do A LOT of multitasking so I'd like to have a ROM that can keep up.
If you did a complete data wipe/factory reset, while having the Modaco Rom, the Hero should be a lot more responsive and faster.
I like Modaco rather than stock rom because it removes some useless apps and allows for more customization. Btw, another alterative to the stock and Modaco is the [email protected] and the Clean ION Roms.
There are several different Roms, the differences is the types of apps removed/installed and the Android firmware.
i like modacos roms, because they work reliable and good. with pauls roms i am sure that he has tested them well, and i can use them as basis for my own modifications, or just can push them to my friends' heros without having them complain that something doesn't work. also in case you need support you can ask paul, he is really a nice guy.
there are some other roms, but imho mcr3.0 is by far the most evolved rom, esp. for everyday use. check the development section here for other roms, including the brandnew android 2.1 roms
Well here's the thing. I didn't wipe/factory reset before I Flashed the ROM. After flashing it went into a reboot loop, it would keep rebooting and when it got to the last boot animation, reboot again... I then did a wipe using the recovery boots wipe option and then it booted fine... Maybe I should do another wipe and flash again? It sucks though because now I've customized it back to the way I like it... I hate having to do that all over again. I guess I need to do the A2SD thing so I don't have to redownload my apps again... that was annoying when I had to do it after flashing Modaco's.... I couldn't even remember all that I had installed lol.
Anyone think reflashing might make it better?
I've been using MCR since about 2.2 so I can't speak for 3.0, but when I first flashed with 2.2 I didn't factory reset or format my SD card and it was a complete fail... apps force closing constantly, unable to recieve SMS, and other assorted weirdness.
So I factory resetted, reflashed and from that point MCR has run very smoothly and each update has gone OK (except for one where i had to format and repartition my SD card for A2SD, but didn't lose any settings).
So my advice would be that if you go to the effort of starting with a clean slate you'll get a much better user experience, which is what all us existing MCR users have...
streetdaddy is spot on. Do a clean wipe and then a rom flash.
I'm using MoDaCo 2.9. For my Hero, 3.0 ate up a lot of my phone's internal memory and kept saying I was running out of memory. The differences are minuscule and the speed improvement is about the same.
I started using Pauls ROM as soon as I got my Hero (which was a few days after release) because the stock ROM was toilet, and I've not looked back. The ROM itself is excellent and the support is first-class.
Make sure to wipe before installing. Once you've got it up and running you shouldn't have to wipe it when you upgrade next time.
i have tried the fresh roms, and the TTG CDMA rom, regardless of the rom i get force close errors on settings in the phone and i dont have data or voice service. everything else works perfectly EXCEPT for settings and service.
help?
ae you performing a wipe before you flash? I know a lot of these roms say that they are no wipe but I have found that that it is always better to wipe then flash that way you know you are getting a clean install. also do you have a ton of apps? it is a known problem that the phone will freak if you have more than like 60 apps
yeah, i have wiped also. but one thing i only wipe data/factory reset
should
i wipe
dalvik cache also? alsong with anything else?
when I install a new rom I wipe both the factory/data reset and delvik cache. I also do this when I am going from say TTG 1.6 back to my backup of fresh 1.1. It just assures me that anything that one dev did in their rom will be wiped out and replaced by what the other did with no problems. the only FC I get is google voice ( which FC's on EVERYTHING for no particular reason)
ok wiping data, and dalvik because jusr assuming battery status, rotate settings and partition doesnt matter.
from my personal use I dont use all the options in recovery. the partition SD is going to be usefull once you get the ROMs running if you want to run apps2sd
nope...
ive unrooted used kitchen numerous times to auto root aswell then just apply update and I can get everything to work except FC on settings and no service, im trying to figure out how to use ruu 1.2.3 instead of the 1.5 one idk just gonna try.
samrozzi said:
nope...
ive unrooted used kitchen numerous times to auto root aswell then just apply update and I can get everything to work except FC on settings and no service, im trying to figure out how to use ruu 1.2.3 instead of the 1.5 one idk just gonna try.
Click to expand...
Click to collapse
RUU 1.29 will not work for you if you have used 1.56. Are you sure you're running a Sprint CDMA Hero? Can you step by step explain the process you go through when RUU'ing and when flashing, and when the problems start?
ok if i wanted to start from scratch, i will unroot my phone with htc sync and reload the stock rom.
then i use kitchen and run the tests and everything checks out good.
i auto root and its successful and working.
then say I download fresh 1.1, load it onto the root of the sd card.
Power off the phone then power on while holding home.
apply .zip on sdcard. it applies the fresh 1.1 update says successful
i click reboot, phone goes through startup process everything seems fine, rom loads up i can navigate through menues. except i get force close errors anytime i goto settings, and i have no service, no data or voice signal.
I have tried renaming fresh and other roms to update aswell, i have tried numerous roms, one of the most recent was the TTG cdma hero rom. and i get the same errors.
One interesting thing is the first rom i tried on the cdma hero was eclair 2.1 beta and that worked flawlessly like all the roms i tried on my g1. but i decided to go to fresh and nothing works.
samrozzi said:
ok if i wanted to start from scratch, i will unroot my phone with htc sync and reload the stock rom.
Click to expand...
Click to collapse
I'm not sure what you mean by unrooting it with htc sync and reloading stock rom? You need to be using the RUU to flash back to stock.
Also if you are using apps2sd then I would recommend temporarily formatting your sdcard back to 100% fat32 (you will lose all data) and then try RUU and flash. Or just grab another sd card and put it in there. If you are using apps2sd and there is an app on your sdcard that is breaking things then it will persist even after a wipe.
1. Partition sdcard to 100% fat32 or replace it with another temporarily
2. Run 1.56 RUU to return to bone stock. Confirm everything works.
3. Run auto-rooter in kitchen. Confirm everything works.
4. Flash a rom, confirm everything works.
If you follow those steps exactly then everything will work out for you.
ok gonna try it again when wiping sd card and foratting to fat32.
any way or know how to get htc sync to recognize my phone?
it picks it up on my vista laptop but on my windows 7 64 bit it doesnt, but atm all i have is my windows 7 one.
samrozzi said:
ok gonna try it again when wiping sd card and foratting to fat32.
any way or know how to get htc sync to recognize my phone?
it picks it up on my vista laptop but on my windows 7 64 bit it doesnt, but atm all i have is my windows 7 one.
Click to expand...
Click to collapse
http://www.mydigitallife.info/2009/08/24/workaround-for-htc-hero-sync-problem-in-windows-7/
ok about to return to stock, when i apply the fresh 1.1 rom after i use kitchen auto rooter i jsut stick it on root of sdcard and DO NOT change file name?
just used to most roms from g1 have to be renamed update.zip
samrozzi said:
ok about to return to stock, when i apply the fresh 1.1 rom after i use kitchen auto rooter i jsut stick it on root of sdcard and DO NOT change file name?
just used to most roms from g1 have to be renamed update.zip
Click to expand...
Click to collapse
You can do it either way. But you don't have to rename it.
WOW IT WORKS, their had to be something wrong with my sd card, because it wouldnt let me format it.
I had to delete all the files, then install some 3rd party software that would let me format it. idk what was wrong, but working great !!!
so excited finalllly lol
thanks everyone and especially flipz
i am running fresh 1.1 defreshed atm, love it but curious about what AOSP i think its called. what exactly is that, looking at it and seems interesting,
im hoping we get a rom similar to nexus, love the app drawer etc..
It may have worked because when you wiped your Sd, you deleted your apps, if you install too many, you'll have the same issue. I went round and round with mine before I figured it out, then found a thread on it.
AOSP stand for "Android Open Source Project" they are ROMs that are crated and developed from scratch by various developers.
I have played with AOSP builds and I have found that out of them all I like AOSP 1.6 best. The thing you have to rememeber about AOSP builds right now is that A. we still dont have the Kernel source so not everything is working correctly and they can be kinda buggy and B. all the AOSP builds are vanilla android, meaning they dont use sense UI which in my opinion defetes the purpose of having a hero. If I didnt care about sense then I would have gotten a moment.
that being said I will say that the AOSP builds are REALLY fast.
if you want to try a ROM that is close to an AOSP build but still has sense try TTG1.6 its really fast and has a really small memory footprint due to it being almost completely gutted and optimized.
Not sure what they did on this thing. I thought 2.1 was supposed to IMPROVE performance...and add some BT functionality.
I got no BT improvement. Instead, I got:
1. Random reboots
2. Slow/crashing Navigation
3. Useless voice recognition on Navigation
4. Random phone calls placed when fiddling with BT
5. Slow opening notifications
6. WIFI won't turn on
I could go on and on...
Sprint says I can't go back to 1.5, but I'm sure there's a way to do it.
HELP PLEASE! I'm rooted, if that helps.
Greg
theres noway. your H-Boot has been updated. thats the end of it. 1.5 just wont work anymore.
Sent from my Hero CDMA using the XDA mobile application powered by Tapatalk
troublestylist said:
HELP PLEASE! I'm rooted, if that helps.
Click to expand...
Click to collapse
Yes it does. Just find a 1.5 ROM for CDMA hero. However, before most of our devs moved on to the EVO almost all of them stop developing 1.5 and moved to 2.1
I would suggest trying out some 2.1 ROMs and see what you like.
If you are rooted you should have put a recovery on your phone that you can get to by pressing home and turning on your phone. The first thing you will want to do is make a nandroid backup in case you don't like things. Then stick a ROM on your sdcard. Select all the wipe options except for battery and rotate and then flash a new ROM.
Id try wiping and reloading a 2.1 rom. I never had any of those problems when I went to 2.1.
I'm running the latest DamageControl and can honestly say I am not having any of those issues. I say you should try using a different ROM.
centran said:
Yes it does. Just find a 1.5 ROM for CDMA hero. However, before most of our devs moved on to the EVO almost all of them stop developing 1.5 and moved to 2.1
I would suggest trying out some 2.1 ROMs and see what you like.
If you are rooted you should have put a recovery on your phone that you can get to by pressing home and turning on your phone. The first thing you will want to do is make a nandroid backup in case you don't like things. Then stick a ROM on your sdcard. Select all the wipe options except for battery and rotate and then flash a new ROM.
Click to expand...
Click to collapse
I didn't root until I got 2.1, so I surmise the 1.5 is gone, right?
derekwilkinson said:
I'm running the latest DamageControl and can honestly say I am not having any of those issues. I say you should try using a different ROM.
Click to expand...
Click to collapse
RegawMOD was also recommended. Any reason why to pick one or the other?
Thanks for all the help. Sad that unpaid and unsupported independent developers can do this job better than HTC.
In a best case world, I'd be able to get ad hoc networking to work. I followed the directions but didn't have any success. My ultimate goal was to enable my Hero to display photos wirelessly from my computer. Many programs do it the other way around.
Originally I thought BT would be the easiest wireless protocol, but it seems pretty weak for that sort of data transfer. So 802.11 seemed a better solution...but for some reason Android folks decided to cripple the OS from recognizing ad hoc networks. Odd.
troublestylist said:
I didn't root until I got 2.1, so I surmise the 1.5 is gone, right?
Click to expand...
Click to collapse
You can still flash 1.5 ROMs. You just can't flash the 1.5 RUU.
Great...
Tried Damagecontrol 2.09, did a clean wiped install, and everything seemed fine. Didn't seem much faster, but whatever.
Too bad I waited until I was at work to reboot. Now it's in a bootloop, and I'm stuck at work with no phone.
Sprint sent me a new phone. Once I confirm it's got 1.5, they can have this 2.1-infected POS back.
troublestylist said:
Tried Damagecontrol 2.09, did a clean wiped install, and everything seemed fine. Didn't seem much faster, but whatever.
Too bad I waited until I was at work to reboot. Now it's in a bootloop, and I'm stuck at work with no phone.
Sprint sent me a new phone. Once I confirm it's got 1.5, they can have this 2.1-infected POS back.
Click to expand...
Click to collapse
Look... there's a good chance your new Hero WILL have 2.1 on it. If it does, just root it and install a custom 1.5 rom.
troublestylist said:
Tried Damagecontrol 2.09, did a clean wiped install, and everything seemed fine. Didn't seem much faster, but whatever.
Too bad I waited until I was at work to reboot. Now it's in a bootloop, and I'm stuck at work with no phone.
Click to expand...
Click to collapse
This might mean you simply didn't wipe everything before you flashed the new ROM. Always perform a full wipe before flashing new ROMs.
Take the battery out of your phone. Put it back in and reboot to Recovery (hold Home and press Power). Then select the Wipe option, and go down that list and wipe every single category (I do them each twice just to make sure).
Then go back to the main menu and flash the ROM again. That should probably solve any bootloop problems.
(I don't know if it works exactly this same way with the rooted 2.1 RUU [I'm still on rooted 1.5], so if any of the above is wrong, anybody please correct it...)
HeroMeng said:
Look... there's a good chance your new Hero WILL have 2.1 on it. If it does, just root it and install a custom 1.5 rom.
Click to expand...
Click to collapse
Yeah, I was thinking about that. If so, I might as well keep MY phone and install a 1.5 ROM on it. Less work, and they can have their "new" phone back.
chromiumleaf said:
This might mean you simply didn't wipe everything before you flashed the new ROM. Always perform a full wipe before flashing new ROMs.
Take the battery out of your phone. Put it back in and reboot to Recovery (hold Home and press Power). Then select the Wipe option, and go down that list and wipe every single category (I do them each twice just to make sure).
Then go back to the main menu and flash the ROM again. That should probably solve any bootloop problems.
(I don't know if it works exactly this same way with the rooted 2.1 RUU [I'm still on rooted 1.5], so if any of the above is wrong, anybody please correct it...)
Click to expand...
Click to collapse
Wow, so working with this ROM is like dealing with my kids. I have to tell it everything twice No thanks. Not worth the hassles.
2.1 doesn't do anything better that I can see. I'll deal with wired tethering considering how rarely I use it. The Navigation on 1.5 works better, or at least the voice recognition does.
Why exactly are you still using 1.5??? What custom 1.5 ROM would you guys recommend? Any that have ad hoc networking built in so I don't have to hack it myself?
Any that have ad hoc networking built in so I don't have to hack it myself?[/QUOTE]
Pretty sure all of them do.
Sure wish we could get WPA working for us....stupid kernel.
troublestylist said:
Wow, so working with this ROM is like dealing with my kids. I have to tell it everything twice No thanks. Not worth the hassles.
Click to expand...
Click to collapse
You don't have to do them all twice, I was just saying that I do to make sure -- personal preference. Considering how those wipe options only take like 1 second each, there is no "hassle" of which you speak. Adds maybe an extra 4 to 5 seconds to your day at most.
troublestylist said:
Why exactly are you still using 1.5??? What custom 1.5 ROM would you guys recommend? Any that have ad hoc networking built in so I don't have to hack it myself?
Click to expand...
Click to collapse
I'm not still on a 1.5 ROM, I just haven't yet updated my phone to stock 2.1 using the can't-ever-go-back-again 2.1 RUU. What I meant is that I still have the 1.5 root, but I have been using 2.1 ROMs over top of that for at least a couple months now. I think all these 2.1 ROMs are much faster than 1.5 ever was. Slow speed and lag were my biggest annoyances in stock 1.5.
We probably won't be able to answer all your questions or remove all your doubts. You won't know completely until you try some of them yourself.
If you look in the Wiki there are several 1.5 Roms out there that you can use. However, there are some apps that will only work with 2.1. Once your rooted you can flash any ROM from 1.5 or 2.1. You might also consider an AOSP rom which doesn't have Sense UI. But as I stated in another thread yesterday, most people end up adding apps to try and emulate certain characteristics of Sense UI. I don't like vanilla android, but it is supposed to be faster.
Here are all of the ROMs available. If you want a 1.5 Rom I would suggest Gumbo 1.5c, Modaco 2.2, or Fresh 1.1.
Thanks all. I honestly can't imagine how anyone could find 2.1 faster than 1.5, but I guess maybe once I'll reload 1.5, it may remind me. The "other half" of the people are (like me) saying the CPU can't handle the extra 2.1 features.
I never found 1.5 slow for anything other than phone calls. Now, those are WORSE, and the lag time to do anything else now exists, where it didn't before.
I ran DC all day, and it was just as annoying as the stock ROM. Maybe a little better in places, worse in others.
I guess I'm running "basic" stuff compared to all you guys running heavy apps or something.
Pancake 1.5 running now...refreshingly smoothly Yea, a bit of the glitz is gone, but wow, no lag.
And I have a Navigation program back that has a functional voice recognition. I hesitate to update because I'm not sure how far the revs go under 1.5. I don't want the new version back and I don't know if it's 2.1-only.
Hello dear forum users.
I need your thoughts and advices on my problem.
I'm closely following the Android development on HD2 and learned nearly all methods accept "CLK".
What I recently realize is when I try to install a custom Anroid ROM I'm watching logcat and I mostly see that its giving some errors not always the same error but sometimes it stops after Iampc's(correct me if I'm wrong) sound script and starts bootloop and some times it installs without giving any errors but when it boots is giving lots of FC's after I entered the PIN or sometimes before entering the PIN. Some times it seems to load everything OK but when I turn my phone off and on again it is giving me the sound script bootloop, or not booting at all or sometimes it starts checking or reinstalling the .apks.
I've tried tytungs NexusHD, Tyween's CM mod, ponster's Hyperdroid, crawlingcity's UD etc... I tried lots off android roms and errors are the same.
I'm doing task 29, magldr 1.13, CWRmod, althoug I've fromatted the sd and partitioned it wih CWR I also did wipes of factory reset, cache and dalvik, than rom installation but results are the same.
I tried with different micro sd's and partitioning with cwm and under linux etc. etc..
I tried installing without the sd-ext partitioning and its still the same.
I've tried installing the winmo rom Energy and it setups and loads ok.
I really don't understand what is causing this and it is really making me angry.
I don't think it is related to the hardware because than winmo should give me the same kind of errors but it is not.
Does anyone faced this kind of behaviours? Please share your ideas and thoughts. Thank you.
webmanya said:
Hello dear forum users.
I need your thoughts and advices on my problem.
I'm closely following the Android development on HD2 and learned nearly all methods accept "CLK".
What I recently realize is when I try to install a custom Anroid ROM I'm watching logcat and I mostly see that its giving some errors not always the same error but sometimes it stops after Iampc's(correct me if I'm wrong) sound script and starts bootloop and some times it installs without giving any errors but when it boots is giving lots of FC's after I entered the PIN or sometimes before entering the PIN. Some times it seems to load everything OK but when I turn my phone off and on again it is giving me the sound script bootloop, or not booting at all or sometimes it starts checking or reinstalling the .apks.
I've tried tytungs NexusHD, Tyween's CM mod, ponster's Hyperdroid, crawlingcity's UD etc... I tried lots off android roms and errors are the same.
I'm doing task 29, magldr 1.13, CWRmod, althoug I've fromatted the sd and partitioned it wih CWR I also did wipes of factory reset, cache and dalvik, than rom installation but results are the same.
I tried with different micro sd's and partitioning with cwm and under linux etc. etc..
I tried installing without the sd-ext partitioning and its still the same.
I've tried installing the winmo rom Energy and it setups and loads ok.
I really don't understand what is causing this and it is really making me angry.
I don't think it is related to the hardware because than winmo should give me the same kind of errors but it is not.
Does anyone faced this kind of behaviours? Please share your ideas and thoughts. Thank you.
Click to expand...
Click to collapse
Maybe your problem is like mine
I had posted similar problem, you can check my threads here: http://forum.xda-developers.com/showthread.php?t=1000190
Pay special attention to post #42
Cheers
silverwind said:
Maybe your problem is like mine
I had posted similar problem, you can check my threads here: http://forum.xda-developers.com/showthread.php?t=1000190
Pay special attention to post #42
Cheers
Click to expand...
Click to collapse
Thank you for your advice. I don't know but I'll try to see if its really about the bad blocks. Thank you again.
I don't think my problem is about the bad blocks in the nand. Because what is funny is that I can flash the imilka's ROM's without any problems.
And one more think I realized is that I'm facing this problem with the gingerbread ROMs. I guess they are sharing something and I can not delete them so I'm facing these problems. I think it is really about that you can not delete the nand fully or format it with task 29.
Becuase I realized that when I change ROMs although I've wiped several times I'm getting errors but If I flash the ROM after flashing the original HTC ROM I don't get the same errors. So I guess what we really need is a better tool to wipe and format the NAND for us.
I don't know if this is possible.
webmanya said:
Thank you for your advice. I don't know but I'll try to see if its really about the bad blocks. Thank you again.
I don't think my problem is about the bad blocks in the nand. Because what is funny is that I can flash the imilka's ROM's without any problems.
And one more think I realized is that I'm facing this problem with the gingerbread ROMs. I guess they are sharing something and I can not delete them so I'm facing these problems. I think it is really about that you can not delete the nand fully or format it with task 29.
Becuase I realized that when I change ROMs although I've wiped several times I'm getting errors but If I flash the ROM after flashing the original HTC ROM I don't get the same errors. So I guess what we really need is a better tool to wipe and format the NAND for us.
I don't know if this is possible.
Click to expand...
Click to collapse
In fact, I still can use Imilka's, Rafdroid and few other Nandroid ROM
But, I dont want to make it worse knowing that there is some badblock(because I want to sell it)
So, I am back with Winmo and SD Android. It is much safer for me
Cheers
A few days ago my phone just started randomly flashing the boot screen. At the time I just thought it was annoying and was bogged down or something but would soon be gone.
But it hasn't!!
My phone is rooted with the gfree method and I was running this ROM
http://forum.xda-developers.com/showthread.php?t=1401556
The problem is this: anytime I'm not giving my phone a command and the screen is about to timeout, the boot animation starts up and loads to the home screen. At that point I have a few as ones to unlock.it and use my phone which will work.just like normal or if I don't respond soon enough it will start over and flash it again.... It repeats.continuously. If a webpage is loading or I am backing up something and don't keep touching the screen it will stop.the task and go into this "continuous boot mode"...
I've wiped everything, tried other roms.... It does it right after the intial setup everytime and won't go away...
I believe you're answering yourself. If you wiped everything and flashed different ROMs, but problem persisted - it means that your phone is most likely faulty.
k15goose said:
A few days ago my phone just started randomly flashing the boot screen. At the time I just thought it was annoying and was bogged down or something but would soon be gone.
But it hasn't!!
My phone is rooted with the gfree method and I was running this ROM
http://forum.xda-developers.com/showthread.php?t=1401556
The problem is this: anytime I'm not giving my phone a command and the screen is about to timeout, the boot animation starts up and loads to the home screen. At that point I have a few as ones to unlock.it and use my phone which will work.just like normal or if I don't respond soon enough it will start over and flash it again.... It repeats.continuously. If a webpage is loading or I am backing up something and don't keep touching the screen it will stop.the task and go into this "continuous boot mode"...
I've wiped everything, tried other roms.... It does it right after the intial setup everytime and won't go away...
Click to expand...
Click to collapse
The question is, what other roms have you tried? I seem to get the same problems on sense 3.5 roms which is why i am not using them currently. If this is happening on a clean install of cm7 or miui as well as sense then you may genuinely have a problem.
Things to try: full wipe system/data/cache/dalvik/sdcard
reboot recovery after wipe to start clean. verify md5sum of the rom you are flashing to eliminate possibility of error. dont install any of your own apps for 1 to 2 days and then if you still have the problem then you may want to unroot and try to get a warranty exchange if at all possible. Good Luck!
Dumb question, but how exactly do I verify that?? And yes it does seem to be with all the 3.5 sense Roms so I tried miui and a sense 3.0... While that did eliminate that problem another unique one showed up...the market wouldn't download anything! No apps.. it would always say due to an error "(-101)"
Just for the record, I rooted it a few weeks ago and the miui and energy 3.5sense both worked fine for at least a week.. does that help in any way??
k15goose said:
Dumb question, but how exactly do I verify that?? And yes it does seem to be with all the 3.5 sense Roms so I tried miui and a sense 3.0... While that did eliminate that problem another unique one showed up...the market wouldn't download anything! No apps.. it would always say due to an error "(-101)"
Just for the record, I rooted it a few weeks ago and the miui and energy 3.5sense both worked fine for at least a week.. does that help in any way??
Click to expand...
Click to collapse
Well that's good to hear that it isn't happening on all roms. I usually fix the market problems by doing a data wipe and then force close it. Usually will start being able to download after a fc. To check the md5sum on a file download mand5 free from the market and check the file that way.
Sent from my HTC Glacier using xda premium