Related
Hi,
I am having major Force Close issues on multiple applications. I've posted my logcat here: http://pastebin.com/m51550315
I've tried doing a system wipe, installing the Android 1.6 Recovery image, installing the latest cyanogenmod MOD, wiping Dalvik cache and running fix_permissions but I get the same problems. When I follow these steps I am missing all of the Google apps and when I try to install them I get error messages saying that they can't be installed.
Is there anywhere else besides Dalvik cache that retains settings that will throw my phone off? It seems like even after doing the system wipe and Dalvik-cache clear there is something causing problems.
I have a Rogers G1 but followed Haykuro's root guide to change my radio image so that I don't need a custom kernel.
what exactly is the dalvik cache
asb123 said:
what exactly is the dalvik cache
Click to expand...
Click to collapse
A place where the system writes things about your apps. Every app you've ever had installed gets it's own little file in the dalvik-cache, wiping the dalvik-cache tends to fix issues with apps.
But wiping my Dalvik cache didn't solve the problem which is why I want to know if there is another cache that needs to be cleared or a better way to wipe previous data.
You could try to wipe the /data/data/
cptnemo said:
Hi,
I am having major Force Close issues on multiple applications. I've posted my logcat here: http://pastebin.com/m51550315
I've tried doing a system wipe, installing the Android 1.6 Recovery image, installing the latest cyanogenmod MOD, wiping Dalvik cache and running fix_permissions but I get the same problems. When I follow these steps I am missing all of the Google apps and when I try to install them I get error messages saying that they can't be installed.
Is there anywhere else besides Dalvik cache that retains settings that will throw my phone off? It seems like even after doing the system wipe and Dalvik-cache clear there is something causing problems.
I have a Rogers G1 but followed Haykuro's root guide to change my radio image so that I don't need a custom kernel.
Click to expand...
Click to collapse
Iam in no way a dev or mildly knowledgeable about these things really, So DO NOT CARRY THIS OUT, IT IS MEANT TO POSSIBLY POINT OUT SOMETHING (Possibly) TO OTHERS WHO ARE MORE SAVVY............
Is signed-dream_devphone_userdebug-ota-14721 Needed?
I'll Wait for someone else to say Yay or Nay, I suggest you do too
KYA
evilkorn said:
You could try to wipe the /data/data/
Click to expand...
Click to collapse
Is /data/data/ wiped by factory reset? What is stored in /data/data/?
cptnemo said:
Is /data/data/ wiped by factory reset? What is stored in /data/data/?
Click to expand...
Click to collapse
Your app data...
killyouridols said:
Is signed-dream_devphone_userdebug-ota-14721 Needed?
Click to expand...
Click to collapse
Android 1.6 Recovery image is another name for signed-dream_devphone_userdebug-ota-14721
t1n0m3n said:
Android 1.6 Recovery image is another name for signed-dream_devphone_userdebug-ota-14721
Click to expand...
Click to collapse
Sweet! Knew someone would know better then me!
Back under my rock I go...
I tried deleting /data/data, /data/dalvik-cache, reinstalling the 1.6 recovery, the latest Cyanogen ROM and then running fix_permissions but I'm still getting errors. I even get an error trying to open settings: "Sorry! The process android.process.acore has stopped unexpectedly. Please try again."
Is there anything else I should try clearing?
With everything you try, your ext partition is untouched. There is something left in there messing you up. Reformat your sd card. Then flash the HTC recovery, then Cyanogen, and you should be set.
BACKUP anything you want to keep on the sdcard first.
How do I know if my sd card has an ext partition? I haven't used apps2sd. When I get home from work I'm going to try a new sd card.
I tried a new sd card but that didn't have any effect. I cleared my dalvik cache and wiped /data/data and then updated my Cyanongenmod from 4.2.11.1 to 4.2.12.2 and the Force Close problems were solved.
I have some new problems now:
When I try to install apps I get the message "(application name) could not be installed on this phone"
I can't receive calls
My screen doesn't lock when I press the End Call button
My Home button doesn't return me to the Home screen
I'm guessing there is still something stored during updates. Any ideas?
cptnemo said:
I tried a new sd card but that didn't have any effect. I cleared my dalvik cache and wiped /data/data and then updated my Cyanongenmod from 4.2.11.1 to 4.2.12.2 and the Force Close problems were solved.
I have some new problems now:
When I try to install apps I get the message "(application name) could not be installed on this phone"
I can't receive calls
My screen doesn't lock when I press the End Call button
My Home button doesn't return me to the Home screen
I'm guessing there is still something stored during updates. Any ideas?
Click to expand...
Click to collapse
I think you can probably fix this by flashing the HTC recovery image the CM 4.2.12.2 (probably do not need to wipe, but it would not hurt).
cloverdale said:
I think you can probably fix this by flashing the HTC recovery image the CM 4.2.12.2 (probably do not need to wipe, but it would not hurt).
Click to expand...
Click to collapse
I've tried that and it didn't help. I've tried wiping, not wiping, using the defanged image, using the HTC recovery and I'm always missing the google apps.
I am extremely frustrated at this point so I have decided to make a thread.
My hero has been a good phone and runs 1.5/1.6 roms without any problems, and has for 6+ months. However, as soon as the 2.1 leaks came around, I was eager to try them. NONE of them will work. I have tried 6 or 7 different versions. My phone will shut off very frequently, which essentially makes it unusable.
Has anyone else experienced this and was able to fix it, or otherwise have any advice for me?
Any help would be greatly appreciated.
pixie dust!!!..jk
I have no idea why.. have u wiped everything and flashed?
spiritcrusher33 said:
pixie dust!!!..jk
I have no idea why.. have u wiped everything and flashed?
Click to expand...
Click to collapse
Haha. Yeah man, factory reset + dalvik cache wipe. Would a bad SD card cause something like this?
sounds like you didn't properly wipe... once you wipe EVERYTHING.. (after a nandroid).. you shouldn't have problems installing any ROM whether it be 1.5, 1.6, 2.1, 4.2 (coming to the htc hero6 in 2013)
edit: you mentioned factory reset... are u doing the factory reset thats installed in the settings menu or are you wiping everything from recovery?
Have you tried to go back to 1.5/1.6 to see if the problem occurred? This might help eliminating the hardware issue.
Which ROM did you tried? The latest one that I ran which is stable (no over clocking) is Fresh 2.1.1, look for this thread title "[ROM] 05/14/10 | Fresh Rom 2.1.1 | Official Sprint RUU + The normal fresh rom goodies"
I have always do this when installed the new ROM.
-Back up all your private apps (not system apps) with Android Commander (search the forums) to your PC.
-Use Recovery and wipe the followings:
1. Wipe Factory / Data reset
2. Wipe Dalvik cache
3. Wipe EXT partition
4. Wipe Battery Stat
Trust me this will save you a lot of hassle and time.
- Re-Installed all your Apps from Scratch using Adroid Commander. This always work best for me. I found less problem and less time consuming doing it this way.
Most of my problems occurred when I am too lazy to WIPE and install new ROM on top of the OLD one with out wiping dalvik and ext partition. An this make it more time consuming.
That's my experience. Hope this help.
roadster92 said:
Have you tried to go back to 1.5/1.6 to see if the problem occurred? This might help eliminating the hardware issue.
Which ROM did you tried? The latest one that I ran which is stable (no over clocking) is Fresh 2.1.1, look for this thread title "[ROM] 05/14/10 | Fresh Rom 2.1.1 | Official Sprint RUU + The normal fresh rom goodies"
I have always do this when installed the new ROM.
-Back up all your private apps (not system apps) with Android Commander (search the forums) to your PC.
-Use Recovery and wipe the followings:
1. Wipe Factory / Data reset
2. Wipe Dalvik cache
3. Wipe EXT partition
4. Wipe Battery Stat
Trust me this will save you a lot of hassle and time.
- Re-Installed all your Apps from Scratch using Adroid Commander. This always work best for me. I found less problem and less time consuming doing it this way.
Most of my problems occurred when I am too lazy to WIPE and install new ROM on top of the OLD one with out wiping dalvik and ext partition. An this make it more time consuming.
That's my experience. Hope this help.
Click to expand...
Click to collapse
Couple of questions. Is wiping the ext partition wiping your SD card? Also, how do I wipe the battery stat? I just booted to my recovery mode but I didn't see that as an option. Maybe I need a new flashrec or something?
splayde said:
Couple of questions. Is wiping the ext partition wiping your SD card? Also, how do I wipe the battery stat? I just booted to my recovery mode but I didn't see that as an option. Maybe I need a new flashrec or something?
Click to expand...
Click to collapse
what recovery rom are u running? and no wiping the ext partition is not wiping your SD card... just the partition you created..
dont wipe the battery but wipe the sd ext.
the sd ext only wipes what apps you have installed when you partition your sd card. it doesn't remove music, picutres, etc...
splayde said:
Couple of questions. Is wiping the ext partition wiping your SD card? Also, how do I wipe the battery stat? I just booted to my recovery mode but I didn't see that as an option. Maybe I need a new flashrec or something?
Click to expand...
Click to collapse
The one I am using now is overclock. But the previous one that I used is "recovery-RA-heroc-v1.6.2-blue.img"
You might have the older version. Battery Stat Wipe is just reference for me every time I using a new ROM to see how the battery life is.
As mentioned above, wipe EXT partition will not wipe any pictures or data on the FAT32 of the SD card.
im having a similar issues i cant get my phone to stop restarting. ive wiped everything you can even repartitioned and it sill does it.
are we doing somehting wrong?
i have a thread i started not seeing this one.
http://forum.xda-developers.com/showthread.php?t=684727
check the hardware
As someone suggested, please be sure to rollback to 1.6 to rule out a hardware problem.
I have a battery -- one of four in rotation -- that consistently reboots the phone after it draws down to 80% or so. This is probably the battery that I misplaced and didn't use for a few months. Before I pinned the problem down to this particular battery, I thought 2.1 was haywire, rebooting all the time. Once I pulled the battery out of rotation 2.1 became relatively stable again.
Hi all, i installed the FroyoMOD 2.6.0 and its all good.
When i install one of the few next versions, i cant do a clean install.
After each installation, i still have all my apps and settings
Even after the three wipes.
Also when i try factory reset, still nothing.
The only thing i get after wipes or factory reset is to sign to my google account.
Any idea what can i do to get a pure clean install for the 2.7.0?
Tx, Shahar.
Sent from my SGT using my hands.
shahar2k9 said:
Hi all, i installed the FroyoMOD 2.6.0 and its all good.
When i install one of the few next versions, i cant do a clean install.
After each installation, i still have all my apps and settings
Even after the three wipes.
Also when i try factory reset, still nothing.
The only thing i get after wipes or factory reset is to sign to my google account.
Any idea what can i do to get a pure clean install for the 2.7.0?
Tx, Shahar.
Sent from my SGT using my hands.
Click to expand...
Click to collapse
Do you have an ext2 partition? Because I have one and I'm wondering if, even after a wipe, all of my apps are still there because of my ext2 partition.
Yeap, ext2.
Tx, Shahar.
Sent from my SGT using my hands.
I'm really wondering if because our apps are moved to the sd-card, if that is what is making all of our apps get reinstalled on the first boot of a new ROM.. It would mean I don't even need to restore from TB, it's doing it already
Try re-flashing the 2.2.1 sbf with vulnerable recovery, then achieving root, then updating to froyo mod. If you need help refer to this thread (only the beginning after you achieve root then apply the custom rom) or if mine is too difficult to comprehend, there is anotehr guide in this forum. : http://forum.xda-developers.com/showthread.php?t=932196 good luck
Using apps2ext means AOR cannot wipe your your app data and dalvik-cache because it looks for these on the phone, not on the EXT partition of your card.
So, before you flash a new ROM, manually delete the /app, /app-private and /dalvik-cache folders in /system/sd (or /sd-ext where applicable) to wipe these files off.
You can use Root Explorer or any similar app to do so.
Or if you use Linux, just mount the EXT partition and delete the files within.
Hello guys,
I have a little problem which seems to be coming when I move the dalvik cache to the EXT partition of my device.
I am using the latest version of MIUI. It has A2SD built in, but it doesn't seem to be working. It was working before though...
What happened:
I restored the NANDROID backup of the stock ROM I had made before flashing MIUI. Once I booted into it, it warned me about the 2.3.4 OTA update. I did it, but forgot that it overwrites the bootloader, removes root and I will not be able to revert to MIUI.
I pushed the Clockwork recovery and immediately started restoring the NAND backup of my MIUI ROM. Without gaining root on the Stock 2.3.4 ROM.
The Dalvik was moved to the EXT on the MIUI I was trying to restore and functioning properly.
The restore went fine, until it got to restoring the sd-ext. It stood there at some *.tmp file for an hour or so. I removed the battery, booted into recovery, wiped and started the restore again. This time it finished, but when I went to start the phone, it got stuck at the Nexus logo, not even showing the MIUI boot screen.
Wiped again. Tried booting into a previous backup, which didn't have the Dalvik moved to the EXT partition. Restored and booted just fine.
I tried several more times restoring the latest backup I had (the one with dalvik to ext) and got the same result.
Then I tried installing the MIUI backup that didn't have Dalvik moved to EXT and tried moving the Dalvik to EXT. The phone rebooted and same thing happened. Didn't want to get past the Nexus logo.
I then wiped everything except batt stats, formatted ext, and flashed the MIUI ROM. It booted perfectly, but A2SD was not working, just like before (solution was to move dalvik to sd). I downloaded the A2SD GUI only and moved the dalvik to EXT AGAIN. And AGAIN - not booting past Nexus logo.
The only thing I still haven't done is formatting the SD and re-creating the EXT partition.
Any other suggestions on what may be causing this and how to fix it?
I want to have a2sd on this ROM and moving the dalvik to EXT seems to be the only way of achieving this.
Repartition SD card, you've most probably corrupted the EXT partition by pulling the battery.
Do you think that restoring the last MIUI backup I had after this will do the job?
After repartitioning? As long as you back up the files from the main FAT32 partition on the computer, and restore them back - the EXT will be overwritten when restoring nandroid anyway.
Well.... I just formatted the card with Panasonic SD formatter. Transfered only the nandroid backup (without creating an ext partition beforehand) and restored it successfully, but when the phone starts booting it is stuck at the Nexus logo.
I also checked the MD5 of the backup and everything is fine.
Godzi said:
Well.... I just formatted the card with Panasonic SD formatter. Transfered only the nandroid backup (without creating an ext partition beforehand) and restored it successfully, but when the phone starts booting it is stuck at the Nexus logo.
I also checked the MD5 of the backup and everything is fine.
Click to expand...
Click to collapse
Wipe Cache and dalvic. Than try again. Your System Need a ext wenn you push dalvic to sd before.
I ran out of options.
Formatted the card, tried restoring - Nexus logo
Wiped Everything + Dalvik and Cache, restored - Nexus logo
Wiped Everything + Dalvik and Cache, didn't restore old MIUI backup - successful boot. When I tried to move Dalvik to EXT after the successful boot - Nexus logo after restart.
If anyone can suggest anything... Because this way I have no access to the A2SD on the device with this ROM. And everything was working fine before I restored the Stock Ginger.
Did you try installing DT on any other ROM and try and move dalvik to the sd to see if it does the same thing?
Dude Random21 said:
Did you try installing DT on any other ROM and try and move dalvik to the sd to see if it does the same thing?
Click to expand...
Click to collapse
No. I haven't tried with another ROM. I guess I will try CM7 and see what happens when I move the Dalvik to the EXT.
I repartitioned once again, this time using the same EXT size as before the breakdown (512MB). When the backup I am trying to restore was made.
Was using 1024 when I partitioned previously and got the Nexus logo again.
Edit: Same thing. Successful restore and then the Nexus Logo.
I suspect it's the ext partition. Why don't you try formatting through recovery, and do a clean install?
Which recovery do you use? I would avoid Clockwork 3.x...
Well. I formated using Panasonic SD Formatted and then partitioned using the recovery. I did a clean install after that and as soon as I move the Dalvik to the EXT, I can't boot past the Nexus logo.
Yes, Clockwork 3.x. I guess I will try Amon_RA as well. Nothing left to lose.
If you partition with Amon Ra, make sure you up the partition from ext2 to ext3 (available through the Ra menu options)...
Ok. Partitioned with RA.
Tried to transfer the nandroid backup made by Clockwork to a sd/nandroid folder so I can restore it from within RA but it kept giving out some error telling me to look at the recovery log when I selected *.img files from the list.
Good news. I booted into MIUI and installed a2sd GUI. Moved Dalvik to EXT without a problem. I guess Clockwork's partitioning is flawed. Everything is working fine now.
Thank you.
Can anyone suggest a method I can use to restore the Clockwork made NAND backup + the EXT backup now when my partitions are finally alright.
Any method would be fine. Even manual through adb. I don't care. As long as I restore my phone to yesterday.
Thank you guys once again.
You should be fine if you load a clockwork prior to v3.x. I think 2.5.1.4 was the latest version prior to the v3.x series. The issues only arise with v3.x.
But only clockwork is able to restore clockwork backups, and the same goes for Amon_RA.
As an alternative, you can just extract the img files and manually load your data back on. It is definitely more time consuming, but it wouldn't matter what recovery you use. It has been a while since I extracted anything from the img files, and when I did, I just got the data from apps stored on the internal (apps and dalvik were stored on the sdcard), and I think the only program I used was unyaffs2 to extract the data.
Thank you guys!
Partitioning the card with Amon_RA and restoring the old Clockwork-made backup with Clockwork 2.* worked perfectly.
I will not use Clockwork ever agian. Putting Amon_RA and that's it.
You will only have this problem with clockwork 3.x - there doesn't appear to be the same issue with clockwork 2.x
I have been using v2.x without any issues (never upgraded to v3.x). I prefer it because it gives me the option to wipe the /system partition, whereas Amon_RA is missing this feature and you can only do it with a flashable zip.
I use 2.x for a number of reasons. I tried 3.x a few times, but always had ext issues on my N1. Having said that, I've used 3.x on my nook, MT4G and G2, and never had issues with them - just on the N1...
I've used RA 2.2.1 on CM7, MIUI ,Sense rom. I never seen sd-ext issues on my Nexus One.
I've flashed custom roms many times, but I have a couple questions regarding Texas ICS p10.
Currently running:
MeDroid 4.1.
BlackRose with System 220MB Cache 16MB Data 200MB
Amon’s RA recovery
Here's a checklist of what I should do:
Backup everything.
Update Blackrose to system 210 / cache 8 / userdata 218.
Wipe everything / factory reset 3 times
What do I need to do regarding formatting/partitioning the sdcard? ext4? setting dalvik cache to use sdext or data partition? In Amon's RA recovery, I have a "partition sdcard" option, with options to
- Partition SD
- Repair SD:ext
- SD:ext2 to ext3
- SD:ext3 to ext4
Do I need to do anything to get a2sd working other than rebooting a couple times?
Flash Texas' p10.
Flash google apps.
Restore.
Done.
Thanks in advance.
Sounds like you got it
if you are ext4 from medroid, you should be fine--not sure, but ext3 may work too
your current partition sizes are ok
see this on a2sd
http://forum.xda-developers.com/showpost.php?p=21222591&postcount=1374
i think you only rin a2sd install one time
i went to p10 and tiamets kernel and had some issues, restored back to p9 and lost my app links--even a sdcard reformat didn't work with p9 so went back to a medroid nandroid
haven't had time figure it out
medroid 6.1 is pretty stable for me
Ken
How can I check if the sdcard is formatted as 4ext?
Isn't it dangerous having a cache partition of only 8 MB?
Sent from my Nexus One using Tapatalk
maybe gparted or a partition tool program
i am having sdcard issues atm so can't test--terminal em can check, forget command, but sometimes it wasn't accurate for me
i don't know that 8mb is dangerous--some larger apps may not work right--depends how rom handles them. cm7 handles them well--miui doesn't--or so folks say
Don't know about 8MB cache, but it's kinda vurnerable to have only 210MB system partition now. If you have any plan to switch to other ics rom, i.e. MeDroidMod, you'll only have a little size left, or even nothing left. I repartizied back to 220/16/200, which is acceptable for any rom.
Sent from my Nexus One
Ok, so I followed the checklist I listed above. p10 stalls at the blue X boot logo for 10 minutes now. Anyone know why it's doing this? I'm going to go do a full wipe/repartition/reinstall again. I left my hboot alone, as suggested twice.
Actually, I opened blackrose and it automatically installed the latest blackrose, which put my phone in recovery and apparently wiped the rom??? Anyway, now I couldn't change hboot partitions anyway, so I proceeded with the rest of the checklist...
Have a 220/16/200 partition?
Boot into recovery, if you have 4ext recovery, you can format everything except sdcard, then flash p10 & gapps.
Sent from my Nexus One
Yeah, I have that partition. I just wiped everything, repartitioned the sdcard and reflashed... currently 8 minutes in the boot animation...
Not sure what to do from here.
Installed latest medroid 1.3.2a and it just keeps booting back into recovery.... hrm.
Do I need to flash a boot img as described here?
http://forum.xda-developers.com/showthread.php?p=22731102#post22731102
Ok, it installed. Updating blackrose, which took out my ROM for some reason, reverted to the default hboot as far as I can tell. I put the 220 version back on wiped and reflashed and it booted just fine.
Ended up using Medroid 1.3.2a instead of TexasIce p10. Even though p10 has HWA, it has bugs (browser rendering on zoom takes 2 seconds, sometimes longer) and isn't as fast as Medroid in general.
just got 1.3.2a and is running great
samuaz is loading HWA version now, but may have same issues as T's
First boot on ICS may take a while ! Just chill out ^^