My G1 is running AmonRA 1.7.0 recovery and I recently switched from OpenEclair to Cyanogen 5.0.8. But when I wiped to factory reset/data wipe and installed the new ROM, all the applications were still there from the earlier ROM. I wiped ext partitions, cache and everything. I even tried partioning the SD card through the recovery, but it still lingered there. Anyone know what the problem is?
RodrigoKim said:
My G1 is running AmonRA 1.7.0 recovery and I recently switched from OpenEclair to Cyanogen 5.0.8. But when I wiped to factory reset/data wipe and installed the new ROM, all the applications were still there from the earlier ROM. I wiped ext partitions, cache and everything. I even tried partioning the SD card through the recovery, but it still lingered there. Anyone know what the problem is?
Click to expand...
Click to collapse
Yep. You didn't wipe one of either the ext partition or the userdata partition.
Use cyanogens recovery that has a console... then you can check type the scripts with the hard keyboard and check your work...
To wipe the ext partition:
mount /system/sd
rm -rf /system/sd/*
To see what is on the ext:
ls system/sd
Does nobody use switchrom.sh anymore?
-------------------------------------
Sent via the XDA Tapatalk App
will try that, thanks.
usually i use the console, but the options in the 1.7.0 recovery looked convenient and thought it would do the same thing as the commands on the console.
if you have found that you have wiped all sections in the recovery and the apps still appear. try going into your privacy settings and unchecking the option to back up system data to servers, then do a wipe.
Related
i have ongoing problems installing new roms inc hero one , i have correct spl and radio , i wipe ext partitions repair partitions and wipe factory data but i still have problems with no installs working
one thing i did find after i got a hero rom working is that it started to download some programs that i had installed previously on the phone , how do i completley wipe the phone memory ? as i think this is now my problem ?
mrcgibb said:
i have ongoing problems installing new roms inc hero one , i have correct spl and radio , i wipe ext partitions repair partitions and wipe factory data but i still have problems with no installs working
one thing i did find after i got a hero rom working is that it started to download some programs that i had installed previously on the phone , how do i completley wipe the phone memory ? as i think this is now my problem ?
Click to expand...
Click to collapse
im using cyans recovery 1.4 and when you come to the boot screen for it, theres an option for wiping memory. ive had to wipe whenever switching from one rom to the next.
if your using cyanogenmod v1.4 its alt+w to wipe clean.. then wipe your ext with alt+f as well
Problems with new ROM's huh?
Well...it could also possibly be your micro SD card,in which I found out was my problem about a week ago. I found Paragon Partition Manager on the internet.The free version called Partition Manager 9.0 Special Edition. Anyways...used Partition Manager to delete my old FAT32,EXT3,and Linux-Swap partitions and reformatted the entire micro SD then created new EXT3 and Linux-Swap partitions on my SD. Just thought this may be a solution to your problem. Good luck!
I'm not sure alt+f wipes your ext. there are commands you have to type.
to completely wipe your ext2 and ext3 you have to type:
mount /system/
rm -rf /system/sd/
or at least that's what I always used until I upgraded to ext3.
PlatinumMOTO said:
I'm not sure alt+f wipes your ext. there are commands you have to type.
to completely wipe your ext2 and ext3 you have to type:
mount /system/
rm -rf /system/sd/
or at least that's what I always used until I upgraded to ext3.
Click to expand...
Click to collapse
Code:
mke2fs -j /dev/block/mmcblk0p2
that will actually reformat and its less chars
any one know how to wipe dalvik NOT on sd with RA recovery?
its boggling my mind and ive searched this place believe me
why do you need to wipe it?
alt+x
mount /data/
rm -r /data/dalvik-cache
reboot
IT WILL take longer to boot after this because it has to rebuild the cache , then it will boot normally .....
thank you so much. the reason i want to wipe it is because i want to start with a fresh phone and try out the new bluetooth fix from eugene for hero roms. he has it working on his (ibelieve). its not neccasary i just wanted to do it.
well if you were going to flash a new rom, doing a wipe/data factory restore would have gotten the job done. You would only need to delete it if it were on your sd card.
Hey guys, I just got a Hero after switching from Android to winmo for a while, so I've been out of the loop since 1.6. I was able to get the phone rooted no problem, got the custom recovery image on it, got it to tether, even installed busybox. The only thing I can't seem to do is load a custom rom. Whenever I put any rom on it at all it gets stuck looping the boot screen. I tried 4 different roms, none work. The only way I can get it to boot after a custom rom is to do a nandroid restore since I backed up right after I rooted it. I've tried partitioning the sdcard from the recovery image as well, once with a swap and ext partition for apps added, and once with just the ext partition, neither of them had any affect. Anyone have any ideas on what else to try?
Solved
For those with this problem in the future, it was being caused by a2sd on my phone, specifically the dalvik cache. I did the following from the latest a2sd post:
"If you experience boot loops when you move the dalvik-cache to the cache partition, go into adb shell while the phone is boot looping and run the following commands:
a2sd nocache (if you want to put your dalvik-cache on your internal storage) or a2sd cachesd (if you want to put your dalvik-cache on your SD card)
a2sd resetcache (this clears the dalvik-cache and reboots)"
Then I ran logcat as the phone booted up to watch to make sure it didn't loop, and it took it a while but it did start up into the custom ROM.
Hey guys, I have a memory issue with my Nexus One when it comes to available storage space. The rom available memory seems to get lower and lower everytime I flash a rom than the previous time. When I load roms like CM6 or Kang-o-Rang or MicroMod Supercircle 2.7 or any others I have 4-16 MB available and nothing has installed yet. I usually use A2SD EXT3 for these but now its extremely difficult to do anything when booting with so little space to begin with. A week ago, on most roms I have well around 150 MB free before installing anything. What may have caused this issue? I even tried booting CM6 with a different SD card not partitioned for A2SD and wiping everything and same result and now I really can't install anything. So is my phone faulty or is there something I can do? I am currently running recovery Amon RA 1.7.0.1 and issues seemed to have come up since using this recovery. I was using Clockwork Mod latest one before this a few days ago.
Any ideas?
Have you been wiping data + cache each time you flash?
Make sure you're calculating data space and not system space (which can be as low as it gets to be, it doesn't matter).
codesplice said:
Have you been wiping data + cache each time you flash?
Click to expand...
Click to collapse
I have wiped, cleared cache, delvik many many times. I suspect that the wipe is not working properly. I have tried two different recoveries and nothing works. My available space now running on Nexus FRF91 stock with root only I have 53.64 MB free. I have installed no third party apps yet whatsoever. I have not even logged in to google yet because it will download all my apps again. I have rebooted as well. I think theres an issue with my device and memory. Should I call HTC or my warranty is void?
Sounds like a weird problem, I would've tried to wipe a time or two more. I just wiped my device after flashing nightlies for the last two months without wiping and I noticed I had 170MB free when I booted up with a few apps installed.
I agree with SBS_. It sounds like the wipe isn't doing the job properly. Try to do it in all the possible ways (wiping through the ROM - using "Factory Reset" option, wiping through recovery - clearing data, cache and Dalvik-cache, and wiping through ADB command line), see if it changes anything.
Jack_R1 said:
I agree with SBS_. It sounds like the wipe isn't doing the job properly. Try to do it in all the possible ways (wiping through the ROM - using "Factory Reset" option, wiping through recovery - clearing data, cache and Dalvik-cache, and wiping through ADB command line), see if it changes anything.
Click to expand...
Click to collapse
I've tried everything except ADB command line. I will have to read into doing that as I am unsure what to do. I have wiped from recovery and through the rom at least 15 times each! lol
When you load a new ROM, did you try to use Root Explorer to see what's on your DATA partition? (under directory /data).
Jack_R1 said:
When you load a new ROM, did you try to use Root Explorer to see what's on your DATA partition? (under directory /data).
Click to expand...
Click to collapse
Great idea. Actually I have but not sure what suspicious files I should be looking to delete. I do own root explorer so any suggestions would be great. Thanks!
timahawk said:
Great idea. Actually I have but not sure what suspicious files I should be looking to delete. I do own root explorer so any suggestions would be great. Thanks!
Click to expand...
Click to collapse
I have this exact issue. I know how to wipe. I have gone as far as reloading HBoot and placing the stock EPF30 image. I have gone thru using clockwork and Amon. I know how to do factory resets. I know how to go to storage options with clockwork and format all partition options. I have spent months on this. Below is a readout, after blowing away everything.
~ # du -hc /data
du -hc /data
2.0K /data/lost+found
4.0K /data
4.0K total
~ # df -h
df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 192.9M 0 192.9M 0% /dev
/dev/block/mtdblock5 196.3M 109.5M 86.8M 56% /data
~ #
Another user that I have been working with has the exact issues as the user here and me. He contacted HTC. They are replacing his N1. There is something weird going on with some of these units. Just like a few months back, no one knew anything about the bad boot blocks issue causing many developers to change their ROM installs to accommodate those users with this issue. This low space on /data issue is another one that sooner or later will start to show up more and more, IMHO. For instance, at best using either Evils Sense Roms or MicroMods Hybrid sense Roms, I have 23MB free on initial install. This is after basically wiping formatting, resettings factory Data etc etc. At best, lets say using Enoms latest AOSP, I have maybe 75Mb free Internal memory, after initial install and NO applications downloaded installed on my part.
I really wish that folks here and on other threads would start to take this issue a little more seriously than basically saying a user isn't properly wiping his setup prior to an install. I have my beloved N1 since third week of January this year. Never had a problem with rooting, installing any of the original CM, or Paul M stuff from the early days here and on their Kitchen setups. Something has basically changed to cause these issues on a number of Nexus one setups. I have root explorer too and no manner of deleteing, via changing partition permissions from RO to RW makes any difference after wiping, formatting whatever prior to a fresh clean install of any current ROM.
I have approximately the same issue. I can't install anything..
Even after a full wipe of /data and all caches, I installed latest nightly-219-passion and the only possible way to install apps is by manually typing the adb push commands in commandline. It DOES NOT WORK using Market, File Manager, Titaniumbackup, ....
When I nandroid restore I have all my apps back but still CANNOT install any new apps using Market, File Manager, Titaniumbackup, ....
I already tried the fix_permissions script in both Amon_RA and RomManager but without success. I have system:system permissions on /data.
Is there a way to wipe /system aswell prior to an install, or does that happen when you flash a .zip?
Saphroxx said:
I have approximately the same issue. I can't install anything..
Even after a full wipe of /data and all caches, I installed latest nightly-219-passion and the only possible way to install apps is by manually typing the adb push commands in commandline. It DOES NOT WORK using Market, File Manager, Titaniumbackup, ....
When I nandroid restore I have all my apps back but still CANNOT install any new apps using Market, File Manager, Titaniumbackup, ....
I already tried the fix_permissions script in both Amon_RA and RomManager but without success. I have system:system permissions on /data.
Is there a way to wipe /system aswell prior to an install, or does that happen when you flash a .zip?
Click to expand...
Click to collapse
How did you install the nightly. Even with my issues of 109Mb used up on data before I install anything, I have the latest nightly running along with latest Gapps and approx 50 of my own apps, with 79Mb free internal. I used clockwork recovery, then under storage options, you can run format options, on boot, system, data, cache, and SD-EXT and then under advanced, wipe dalvik-cache. I also added the data factory reset option also. I then clean installed the nightly. Then after an initial setup to just have it running, flashed the gapps. I did initially have approx 75Mb free Internal before the Gapps install. Then I went down to 53MB after gapps. I verified I had the correct settings in settings:Cyanogen Mod for the file system. I then flashed the latest Dark Tremor script, ran the commands for a2sd check, a2sd reinstall, a2sd zipalign and a2sd cachesd to move the dalvik-cache to sd. I have an EXT3 setup on my SD card. After moving Dalvik cache I jumped from 28Mb free to 79Mb free where it's pretty much staying now. Not as much as others that don't have the issues on /Data but at least useable.
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.