My Nexus One is having low internal storage space issue again, despite moving all possible apps to SD.
This time I have decided to bite the bullet and root my precious phone.
Normally, you will have to unlock the bootloader to gain root access, this will imply that you void your warranty. But since I have my N1 for more than 2 years now, warranty is out of the question.
My main concern is more about security - Leaving bootloader unlock is a major security issue.
So I dig through the Internet and I found some exploits to change a few binaries in some file that will provide you root. <-- in layman terms
Anyway, there are some scripts created for gaining root access with those exploits, and the one I use was this:
DooMLoRD_v4_ROOT-zergRush-busybox-su
And here is a guide that I followed a bit for creating more internal memory:
Low internal memory problems on Nexus One
In a nutshell, this is what I did:
1)
- Manual Backup SD
- Take screenshots of my launcher
- Use "App List Backup" to create a list of currently installed app
2)
- Download and run the DooMLoRD_v4_ROOT-zergRush-busybox-su script to gain root access
- Use a Terminal app / adb shell and do "su" to see whether root access has been gained
3)
- Install Titanium Backup and Link2SD
4)
- Create a partition from SD card (I used Easeus Partition Master)
1GB maximum partition,
ext3 filesystem,
Primary for both existing FAT32 and the new ext3 partitions
5)
- Reboot device
6)
- Run Link2SD
- Create "boot script"
- Quick reboot (may need to reboot twice to work)
7)
- Move all existing apps from SD to phone (Internal)
8)
- Once low on memory appear, select all current Internal memory apps
- Create "Auto Link" for all apps in Internal memory (except for Play Store / Launcher / Link2SD!)
9)
- Repeat step 7 and 8 until all apps are Linked and moved to the new ext3 partition on SD
10)
- Create Backup as necessary - Titanium Backup / Manual SD card
- Freeze unwanted apps
Enjoy the free space! ;)
I have the same problem. Even removing most apps, low memory warning continues. You would think that Google would find a fix for this common problem, I believe inherent in its design or construction but not told to the consuming public.
ReplyDeleteThanks so much!!! This worked for me with one change: I had to use FAT32, not Ext3, as my Android phone didn't have the libraries to support Ext3.
ReplyDelete