I've been flashing various ROMs, but continuously am running into force close/waits, lag, apps shutting down, but only random reboots on one of the ROM's and it got fixed. I get fc/w's on android.process.acore, calendar storage, alarm clock, you name it, I've probably had it error out on me.
I'm wondering how I can clean up my phone entirely.
I don't know what a ROM writes, or doesn't, but I think I've got something in there that escapes a wipe and a flash that seems to be interfering with the system.
I'm not the only one in the Cyanogen's Experimental thread, nor the lastest stable thread that has had this issue. I haven't been keeping up on the other ROM threads, so I can't say if anyone has had these issues with other ROMs or not.
The Mod on Cyanogen's thread has recently threatened bans for non-ROM -related posts, and to be honest, I don't think this is the ROM because it happens to few, but not all. I'ts not a ROM related question, since it shouldn't matter what ROM I'm using, if I'm rooted, I just want to clean off my phone entirely.
I'm also wondering f these issues could be hardware related, perhaps a different manufacturer of a chip or something.
So, how do I really scrub the thing?
From what I understand, going back to a stock, unrooted phone and going through the rerooting process should "unclutter" things.
I followed this how to
http://forum.xda-developers.com/showthread.php?t=491350
I think I solved my issue
Going back to an unrooted phone doesn't deal with anything on the apps2sd partition that might be messing things up if I go back to it.
I ended up deleting the ext4 partition on my card and recreating it. The last time I cleaned up, which didn't do the trick, I just deleted everything I saw. I don't know if there was something left in lost&found or something hidden, but that's what I did.
I also flashed from RC29 instead of JF1.5.1. The first time I thought it would be easier to flash to a ROM I had on my PC that already had Terminal Emulator and Telnet already on it than to download the two apps. I don't think anything would get left in place from that, and I think people have had success with flashing CM's from JF, so I doubt it was that, but who knows. I did both just to be sure.
I also didn't enable any swapping, but i can't imagine that swapping would create acore force closes. ???
So, flashing from RC29 and starting from a freshly created ext4 did it for me.
Related
I've been flashing various ROMs, but continuously am running into force close/waits, lag, apps shutting down, but only random reboots on one of the ROM's and it got fixed. I get fc/w's on android.process.acore, calendar storage, alarm clock, you name it, I've probably had it error out on me.
I'm wondering how I can clean up my phone entirely.
I don't know what a ROM writes, or doesn't, but I think I've got something in there that escapes a wipe and a flash that seems to be interfering with the system.
I'm not the only one in the Cyanogen's Experimental thread, nor the lastest stable thread that has had this issue. I haven't been keeping up on the other ROM threads, so I can't say if anyone has had these issues with other ROMs or not.
The Mod on Cyanogen's thread has recently threatened bans for non-ROM -related posts, and to be honest, I don't think this is the ROM because it happens to few, but not all. I'ts not a ROM related question, since it shouldn't matter what ROM I'm using, if I'm rooted, I just want to clean off my phone entirely.
I'm also wondering f these issues could be hardware related, perhaps a different manufacturer of a chip or something.
So, how do I really scrub the thing?
You could flash a JF ROM those are about the cleanest. It should clean out your entire /system partition.
Every time I try to flash a Hero ROM, I get an error of sorts during the copy file portion saying that a "xbin" file of sorts is missing. I had JACxROM on the phone, and tried to go from that to a Hero ROM, with no avail. I just flashed to the newest CyanogenMOD no problem(I did flash the HTC ADP 1.6 recovery img first)
I have the newest radio, deathSPL, as well I have the RA1.2.3 recovery image. Is there something I am missing here?
Do I need to downgrade to 1.5, since as it stands I am running 1.6 ROMs?
Or is it likely something else was a "bad flash" and I should just go back to R29, and work my way forward from there?
are you sure you have the "death/danger" spl installed on your phone? make sure, but even if you don't, why not just install it again, it repartitions the phone memory, and makes it clean when you flash things on top of it.
that's the most common problem for xbin errors when flashing a hero rom , it's too big to fit in the stock system memory alone. Try re-doing everything. Make sure your ext partition is clean (format that) , do a wipe to clear cache/data, repair ext partition,
and if all else fails, maybe you might just wanna repartition your sd card, might have broken/corrupted partitions.
maybe you might even have a broken sd card. and you might have to get a new one
lotta maybe's , but try trouble shooting random things.
hope you can find your answer, noone can exactly help you with this one with any sorta direct guide or how two since they're not there to deal with your phone on site
goodluck flashing!
Thank you! I figured it could be one of many things... I am starting fresh, doing RC29 forward.
I am certain I had death, et al, I have been a bit of a lurker for a while on the Android end, and finally got a G1 about a week ago, so I don't have a lot of experience with it, but I have over a year with a Kaiser, and for several months I ran Android on it.
I tried a couple differnt SD cards, and unless both are dead, I think it is just a bad flash somewhere along the way that didn't show up until that broken file system got tested with a Hero flash.
Anyways, I am confident I will get it sorted out eventually. I am smart enough to not brick the damn thing...fingers crossed... not really, I should be all good.
YAY!!!!!!!!!!!!!!!1
I think my first time through I didn't wipe at some point I should have.
I'm fairly new to working with Linux and the Android OS, though I have pretty broad knowledge in most other systems. Hopefully someone here's willing to help me
First, a little background. From straight out of the box, I ran The Unlockr's steps to root and flash my phone. The root instructions I followed are located here.
I am running radio verison 2.22.19.26I
And using SPL version 1.33.2005
My SD card is partioned in a Fat32/EX2/Linuxswap configuration
And I'm using Dwang's Android 1.6 Donut rom. (Located Here!)
The problem:
During Black Friday, I found amazing deals on Micro SD cards. I'm moving from a 2GB to a 4GB. I copied everything over on the fat 32 partition from one to the other, but forgot about the other partitions When I switched SD cards, all of my apps and widgets crashed and whatnot. The problem is when I swapped back to the original card...they were still crashing.
I've tried a bunch of things, Nandroid restores, reflashing the ROM and starting fresh, and I'm still having problems with crashing apps. The interesting thing, is that only apps that were downloaded from the market, and use the internet refuse to work now. Here's a list of working VS non working apps.
Working apps:
App Manager
Melon (Notetaking program)
Any application that came "Stock" on the phone. (Youtube, Messaging, Browser)
Non-Working Apps:
Wikidroid
Autolock
Toggle Settings
Hi AIM
Almost anything downloaded from the market.
Other than that the phone runs fine. Texts, calls, uses the internet browser without a hiccup. It's just download apps either spam force close, or can't connect to the internet. (which the browser can)
I was wondering if anyone knew what causes a problem like this, or where I could be pointed in the direction of someone with a similar problem. I've google'd all morning and searched through the forums, but can't find anything. I'd try more things, but i have bricked a G1 in the past and am pretty damn terrified to mess with things too much.
Thanks in advance for any advice or help.
Just start from scratch.
1) Repartition the new card.
2) Wipe
3) flash
Problem solved.
Reformat the card, wipe the data in the recovery mode, and reflash the rom (Dwang's in my case?) I think I've done this which is what's causing my apps to act all funky anyway. I will try it one more time though. There's no risk in a brick doing this, no? Since I'm using the same rom that worked before?
Again terrified. If a brick shows up, I don't get a third chance
Plus I'm a mobile/program developer. I'd kinda like to know what causes this, or where I can find some resources so I can prevent it frmo happening in the future on stuff that I write.
[email protected] said:
Reformat the card, wipe the data in the recovery mode, and reflash the rom (Dwang's in my case?) I think I've done this which is what's causing my apps to act all funky anyway. I will try it one more time though. There's no risk in a brick doing this, no? Since I'm using the same rom that worked before?
Again terrified. If a brick shows up, I don't get a third chance
Plus I'm a mobile/program developer. I'd kinda like to know what causes this, or where I can find some resources so I can prevent it frmo happening in the future on stuff that I write.
Click to expand...
Click to collapse
Okay, for clarification, the only way you can brick is through flashing a radio image or SPL without the requirments for either. In other words, wiping and flashing ROMs physically can't brick your phone. Stop worrying
I'm honestly not sure what happened to your partition, so I can't tell you what caused it, but honestly, reformatting the card, wipe and reflash will solve your problem, as everything is clean. If the problem persists then something has been left behind.
flashing the roms and repartition the card should fix it. its most likely caused by corrupted permissions or something to the likes. The sdcard should not be removed while the rom is on or replaced with an unidentical ext partition. Some apps that are supposed to be in the card arent there, which will cause failures. since its a hacky method for getting apps on the sd, there is no fail-safes in place
I've tried an assortment of different costume firmware options. CM from bacon, up to the most recent. King's nexus2desire, etc. I've followed the directions as far as I know completely... But this always seems to happen, with either of the two roms.
I'll get some sort of random bug, and it causes a total freeze to where I have to pull the battery to restart it.. But then once I do that, the phone fails to reboot, in which I have to restore the firmware (factory data wipe + delete dav don't help).
It could be working fine for a couple of days, then all of a sudden this happens and screws everything up? Is this to be expected early on since it's development, or is there something wrong on my end?
wrong section, but yea, never happeend to me before.
I wasn't sure if should ask here, since it's based on the development roms here.
When I flash, I always do complete wipe (Factory, Dav, SD:ext, Batt, rotation), then reboot. I never wipe after flashing new rom. I'm using the newest radio, but have had these issues with all the previous radios too. Could there be a hardware malfunction possibly adding to this?
CDRacingZX6R said:
I wasn't sure if should ask here, since it's based on the development roms here.
When I flash, I always do complete wipe (Factory, Dav, SD:ext, Batt, rotation), then reboot. I never wipe after flashing new rom. I'm using the newest radio, but have had these issues with all the previous radios too. Could there be a hardware malfunction possibly adding to this?
Click to expand...
Click to collapse
Yeah something similar would happen to me. I said F it and had HTC send me a new one.
I have only had experience with CM 5, so if you install 5.0.4.1 and get this issue WITHOUT modifying the ROM with other mods, then you probably have a hardware fault. Warranty case that is.
Moved as not Android Development.
I've been tinkering with this phone for probably around a year now. I have a good understanding of flashing and whatnot, but that is probably the extent of it. I've had tons and tons of roms on this phone, and never once been given trouble.
Recently, I flashed to King's Eris2G1 rom, and that seemed to start my problems. I had lots of problems getting this ROM to work properly. Eventually, I got a working load, but I noticed that Apps2SD stopped working. Everything else seemed to work OK so I ignored it and used the rom.
Now, this morning, I went to flash his Legend2G1 rom, and got an error during verification that files were corrupt. Redownloaded and tried to reflash, same thing. So I said screw it, tried going back to an older 1.5 senses rom (I forget which, MLING or something like that), and I got errors on verification for that too. I never had any trouble previously installing that rom. So, I tried Eris2G1 again, and got the same errors there. Last time, it always flashed fine, just worked a little buggy.
So I tried Kings AOSP2.1. That worked. It flashed fine, booted fine, but I did notice, Apps2SD isn't working here either. So, my thoughts are all the Senses roms failed because they are larger and install files to the SD card, where as this smaller rom does not?
I went to test my theory by popping in a different SD card, but I got the exact same errors. So, it's not the card, it's the phone, but it appears to be related to the card. I am able to access the FAT32 partition without problems. I tried repartitioning the card many times (96-128MB swap, 128-512MB ext2) and I tried with ext2, 3, and 4. No luck no matter what.
So, does anyone have any ideas as to 1.) what happened and 2.) how can I fix it? I am not 100% sure what all I have on my phone as far as SPL, recovery, ect go. On recovery, it says "Build: RA-dream-v1.5.2". No idea what SPL I am using... I flashed it a little bit ago to whatever a particular rom I was interested in required. All I know is I never had a single problem like this, and now even the roms that used to work like a champ are not functioning. I've got my phone to a usable state with this current ROM, but i'd really like to play around with the Senses roms more (nevermind the fact that I want A2SD back). Can anyone help?
EDIT: For ****s I just tried flashing 1.6.2 recovery, as well as reflashing radio and SPL. Didn't make a difference.