Develop Bugs

[03 JAN][IDEA] Ramdisk for CM6 builds with external data.img [NOT BUILD]

Features
- external data.img support.
- update kernel and system files without adb.
- easily update build with update.zip, don't have to re-flash.
- options to set data.img size, lcd density, etc in config file.
To enable external data.img
1. create '.data' folde under sdcard (/sdcard/.data).
2. create 'config.txt' under '.data' directory, add 'data_img=1' into 'config.txt'.
3. copy old data.img to '.data' directory, otherwise a new data.img will be created.
4. boot into Android.
If experiencing issue with 1 and 2, simply copy '.data' from View attachment data.zip to sdcard.
To disable external data.img
- delete 'data_img=1' in config.txt.
- delete config.txt.
To change kernel and modules
1. create 'update' folder under sdcard (/sdcard/update).
2. create 'boot' folder under 'update' directory, put zImage into 'boot'. (reboot is needed after updating)
3. create 'system/lib/modules' under 'update' directory, put bcm4329.ko, tun.ko, etc into 'modules'.
4. boot into Android.
To replace initrd.gz and system files
- same as change kernel and modules.
- put 'initrd.gz' under '/sdcard/update/boot'. (reboot is needed after updating)
- put system files under '/sdcard/update/system'.
To use update.zip
- create an update.sh and compress it with update files to update.zip.
- put update.zip under 'sdcard/update'.
- Try ClockworkMod Recovery for HD2
Downloads
- View attachment leo-initrd-0.1.1.zip
- if you want to test the ramdisk, download this build package. Don't forget to backup your data. (thanks to projection for the kernel)
If you've downloaded LEO-CM6.1.1-NAND-3.zip, to update to 3.1, please download the new initrd file, then try the update method above.
To do
- add desire builds support
- add squashfs support
Changes
0.1.1 - fix a stupid typo, sorry.
0.1 - initial.
About config.txt
Code:
data_img=0
- 0, default, use nand userdata, about 250 MB for cm builds
- 1, enable external data.img support (/sdcard/.data/data.img)
data_size=512
- size of data.img, only work when data.img support enabled and first install
data_sync=1
- 0, fast, default, disable sync option when mount data.img
- 1, safe, enable sync option when mount data.img, use this if experiencing data corruption
lcd_density=240
- size of icons
gps_zone=us
- country code, us, fr, jp, etc
Credit to DarkForces Team and everyone in this thread.

that will be very usefull one.another massive milestone in android-hd2 development.cheers

I'm just downloading RAM DISK build... why You strike it ? shoudn't I install it ?

it is becoming obvious that this will be essential for euro H2 NAND builds being that there is very little phone space to play with, where this would be best cooked into ROMs more detailed instructions for noobs would be good.

This is a great idea and will help with the euro versions of hd2 with limited space.
I wonder what will happen with sync, will we run into data corruption problems as with sd builds?
Can this be made so as the data can be on a seperate ext 3/4 partition in sync and the rest of the sdcard can be mounted / unmounted etc ?

DavidX_07 said:
I'm just downloading RAM DISK build... why You strike it ? shoudn't I install it ?
Click to expand...
Click to collapse
Found a stupid typo... will be back soon.

getting back on the horse Kouno? =P
d/l and will test it later
I need to update from your nandv1
had problems with your nandv2, can't change system/lib to r/w
Time to test nandv3

ikkon said:
getting back on the horse Kouno? =P
d/l and will test it later
I need to update from your nandv1
had problems with your nandv2, can't change system/lib to r/w
Time to test nandv3
Click to expand...
Click to collapse
Please download later since it is not available right now.
The lib and xbin is compressed with squashfs in v2, so you can't edit. That's just for test propose. And squashfs file systems have been removed in v3.

i love your job HD2One.
great idea
Is it become to HD2NAND?

LondonTownGuy said:
Can this be made so as the data can be on a seperate ext 3/4 partition in sync and the rest of the sdcard can be mounted / unmounted etc ?
Click to expand...
Click to collapse
I'm new to Android builds configuration, but after some research it looks like it's possible in theory. Personally I do not understand why everyone is so obsessed in data.img file, while it's linux partition in file, that stored on FAT partition. I think actual linux partition on sd card is more elegant solution.

lcd_density=xxx not changing dpi

DavidX_07 said:
lcd_density=xxx not changing dpi
Click to expand...
Click to collapse
Right, it is a typo issue and fixed in 0.1.1.
Please download the new initrd file, then try the update method, tell me if it works

hey Kouno
I just hope you know that Window users can't name a folder that starts with "."
We can always find a way but just giving you the heads up
Ready to Quadrant v.3.1

Kouno.Takaaki said:
Right, it is a typo issue and fixed in 0.1.1.
Please download the new initrd file, then try the update method, tell me if it works
Click to expand...
Click to collapse
Yup, it works BTW blazing fast, testing more now

ikkon said:
hey Kouno
I just hope you know that Window users can't name a folder that starts with "."
We can always find a way but just giving you the heads up
Click to expand...
Click to collapse
I know, so I've provided data.zip and .data folder in the flash package.
Why I use .data instead of data or data2sd? Just want to keep it hidden.

Using the Ramdisk file, when I first turn on the device.
Code:
# cat /proc/meminfo | grep "MemFree"
cat /proc/meminfo | grep "MemFree"
MemFree: 273232 kB
And 5 minutes later.
Code:
# cat /proc/meminfo | grep "MemFree"
cat /proc/meminfo | grep "MemFree"
MemFree: 25596 kB
Memory gets really low, I wonder why?
EDIT: Could just be me. :s

SystemPanel shows 270MB free ram

shadiku said:
Using the Ramdisk file, when I first turn on the device.
Code:
# cat /proc/meminfo | grep "MemFree"
cat /proc/meminfo | grep "MemFree"
MemFree: 273232 kB
And 5 minutes later.
Code:
# cat /proc/meminfo | grep "MemFree"
cat /proc/meminfo | grep "MemFree"
MemFree: 25596 kB
Memory gets really low, I wonder why?
Click to expand...
Click to collapse
Try 'free' command or check the cached memory size.

updating works fine...
framework-res.apk updated succesfull

Sorry , may i ask a stupid question ?
does it work on MDJ Revolution HD v.2.2 build ?
my English is not good !
Sorry for ask this

Simple Android swap partition solution

Didn't see much on this as I was looking around today, so I decided to post my eventual fix:
After first setting up froyo on my Rhodium 400, I was having alot of issues with the phone running out of memory and crashing, so I ended up adding a swap partition. Below is an easy way to do this and have the swap mounted at boot without having to use an external app like swapper:
NOTE - before doing this I suggest that you copy rootfs.img from your SD card onto your computer, and then copy it back once you're finished. I also suggest you make a backup copy of rootfs (rootfs.img.backup etc) before trying mods like this so you can recover your file system if something goes wrong.
on a linux machine, make a mount point and mount the kernel image as a loop device:
Code:
mkdir /mnt/mounthere
mount -o loop rootfs.img /mnt/mounthere
cd into mount point you created (ie, cd /mnt/mounthere) and list the contents with ls. You'll see something like this:
Code:
acct dbgfs init.cfg mnt shared_prefs
bin default.prop init.etc proc sqlite_stmt_journals
cache dev init.rc res sys
config etc installer sbin system
d init lib scripts tmp
data init.android lost+found sdcard ueventd.rc
you want to open the script init with a text editor like nano and add the following lines just before the line that says exec /init.android:
Code:
modprobe ramzswap
swapon /dev/block/mmcblk0p2
where /dev/block/mmcblk0p2 is a pre-created linux swap partition on your SD card.
Once you're done, simply unmount rootfs.img and copy it back onto the SD card you're using for android
Its a pretty simple solution that I've found to make my own phone much more stable and responsive, and you only have to worry about it once. The downside is that on slower sd cards, the phone may slow to a crawl when installing apps, but hey, it beats the phone locking up and crashing back to windows mobile, right?

This really is not needed if you are running the latest versions of everything (and using XDANDROID). If you are experiencing problems with the full official latest version of everything (all info is in the thread in my sig) make sure you post in the ANDROID section

flashplayer 10.3 not working on rooted evo

my flashplayer 10.3 isnt working never did,on rooted 2.2 evo please help,, thank you!!

Uninstall the update then uninstall flash player (the one that was part of the rom). Then navigate to system/lib and delete libflashplayer.so (I think thats the name of it but I forget) if it is still there. Then download and install flash from the market. That should fix it.

lovethyEVO said:
Uninstall the update then uninstall flash player (the one that was part of the rom). Then navigate to system/lib and delete libflashplayer.so (I think thats the name of it but I forget) if it is still there. Then download and install flash from the market. That should fix it.
Click to expand...
Click to collapse
when i try to deleted the lidflashplayer.so it say cannot be deleted the file system is ready-only, need help....

rotzie said:
when i try to deleted the lidflashplayer.so it say cannot be deleted the file system is ready-only, need help....
Click to expand...
Click to collapse
You can use either root explorer or terminal emulator. You would need titanium backup to uninstall the flash that came with the rom.
If you don't have root explorer here are the terminal commands. Press enter after each command.
Code:
su
mount -o rw,remount /dev/block/mtdblock3 /system
cd system/lib
ls
After entering ls you will see a list of all the files in this directory. Look through it and find the one file that says libflashplayer.so
If you have libflashplayer.so then do these next commands
Code:
rm libflashplayer.so
mount -o ro,remount /dev/block/mtdblock3 /system
If you don't have libflashplayer.so just issue the mount command to set the system back to read-only (mount -o ro,remount /dev/block/mtdblock3 /system).

i have rootexplorer and i got i deleted,did not use titanium,but my 10.3 player sits in my apps just saying uninstalling.no date,no force stop nothing....

I had the same problem.. I deleted the app and went to explorer and deleted the folder and reinstalled.. works fine now

[Q] How do i transfer files to GNex when in recovery mode?

So i've made a mistake. I forgot to download GAPPS but i've already done a factory reset and installed a new rom. I cant seem to mount the usb storage trough clockwork recovery. Is there a way to push the zip file to the device?? Or what should i do?
Thanx

xclusiv8 said:
So i've made a mistake. I forgot to download GAPPS but i've already done a factory reset and installed a new rom. I cant seem to mount the usb storage trough clockwork recovery. Is there a way to push the zip file to the device?? Or what should i do?
Thanx
Click to expand...
Click to collapse
If you only forgot gapps you can restart, the ROM and the phone will work fine you just won't have Google apps. Once it's on you can just copy the file like usual and return to recovery and flash it
Sent from my Galaxy Nexus using xda premium

Good question though. What IF he didnt flash the ROM, how do you get a file on the SDcard if you cant mount it in recovery?

adb push ./"filename.zip" /sdcard

Phone will boot just fine w/o GAPPS.
But you can just use adb push <FILE> <DIRECTORY>
for example:
Code:
adb push gapps.zip /sdcard/

Thanx for the help guys =)

This happens to me all the time. The Mounts section of CWM select "mount as USB" drive. Windows should see this drive and transfer away.

merge5 said:
This happens to me all the time. The Mounts section of CWM select "mount as USB" drive. Windows should see this drive and transfer away.
Click to expand...
Click to collapse
GN internal storage can't be mounted as USB - not even in recovery.
The only way I've found to push/pull files in CWM on the GN is over ADB. If the files in /sdcard/ don't appear, go into mounts and storage, and mount /data. Then try again.

/sdcard/ is nothing more than a symlink to /data/media.
I transfer files over ADB with
'adb push update.zip /data/media/'
no need to mount /data before.

just reboot open up your computer and youll see the gnex just transfer the gapps to your sd card and then reboot in recovery to flash

cmstlist said:
GN internal storage can't be mounted as USB - not even in recovery.
The only way I've found to push/pull files in CWM on the GN is over ADB. If the files in /sdcard/ don't appear, go into mounts and storage, and mount /data. Then try again.
Click to expand...
Click to collapse
Good point. I stand corrected. That was how I did it on my OG Droid. Sorry for the confusion.

bk201doesntexist said:
/sdcard/ is nothing more than a symlink to /data/media.
I transfer files over ADB with
'adb push update.zip /data/media/'
no need to mount /data before.
Click to expand...
Click to collapse
I'm not sure why but CWM on my phone used to auto mount /data and now it doesn't anymore. So to see anything from adb in recovery, I now have to go to mounts first.
Sent from my Galaxy Nexus using Tapatalk

cmstlist said:
I'm not sure why but CWM on my phone used to auto mount /data and now it doesn't anymore. So to see anything from adb in recovery, I now have to go to mounts first.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
What cwm version are you on, for instance?

Latest CWM touch as of today, and also tried it with latest CWM non-touch.
Incidentally I just bumped into a caveat of transferring files to the GN in recovery mode. The permissions are set strangely when you push files over ADB in recovery, and as a result when booted into the OS I was unable to rename any of the pushed files/folders or put new files in. Since the DCIM directory was one that I'd pushed over, new photos weren't saving. And I did not have permission to change permissions.
This is pretty much a brute force method - so I rebooted into recovery again, mounted /data, did adb shell, cd sdcard, and then:
chmod -R 777 *
And upon booting back into the OS, everything works properly again.
I know that messing with permissions is usually a dangerous thing. My logic was that anything stored in /sdcard is supposed to be a file that any app would be allowed to access as long as it has SD permissions - it's been that way in every version of the OS through to 4.0.
But anyway, if there's something I should do to decrease the "unsafeness" of this situation, please advise me. I guess in theory this would give a malicious app permission to execute code from /sdcard, which would make me more vulnerable?
EDIT: Okay more to report. To see the permissions properly when booted into the OS, you have to go into /data/media rather than /sdcard (same directory but permissions appear differently).
When I went in there and typed ls -n, I found that all the files I had pushed in recovery have UID & GID of 0. All files I had created afterwards had UID & GID of 1023. That explains everything. The owner is root for files that came from ADB in recovery, and media_rw for files created in the OS.
I can use chown, but it looks like the version of chown that comes with busybox does not have -R recursion implemented. Hrm. Aha! In CWM, chown does support -R. And we're off to the races. So from recovery I did:
cd /data/media
chown -R media_rw.media_rw *

cmstlist said:
Latest CWM touch as of today, and also tried it with latest CWM non-touch.
Incidentally I just bumped into a caveat of transferring files to the GN in recovery mode. The permissions are set strangely when you push files over ADB in recovery, and as a result when booted into the OS I was unable to rename any of the pushed files/folders or put new files in. Since the DCIM directory was one that I'd pushed over, new photos weren't saving. And I did not have permission to change permissions.
This is pretty much a brute force method - so I rebooted into recovery again, mounted /data, did adb shell, cd sdcard, and then:
chmod -R 777 *
And upon booting back into the OS, everything works properly again.
I know that messing with permissions is usually a dangerous thing. My logic was that anything stored in /sdcard is supposed to be a file that any app would be allowed to access as long as it has SD permissions - it's been that way in every version of the OS through to 4.0.
But anyway, if there's something I should do to decrease the "unsafeness" of this situation, please advise me. I guess in theory this would give a malicious app permission to execute code from /sdcard, which would make me more vulnerable?
EDIT: Okay more to report. To see the permissions properly when booted into the OS, you have to go into /data/media rather than /sdcard (same directory but permissions appear differently).
When I went in there and typed ls -n, I found that all the files I had pushed in recovery have UID & GID of 0. All files I had created afterwards had UID & GID of 1023. That explains everything. The owner is root for files that came from ADB in recovery, and media_rw for files created in the OS.
I can use chown, but it looks like the version of chown that comes with busybox does not have -R recursion implemented. Hrm. Aha! In CWM, chown does support -R. And we're off to the races. So from recovery I did:
cd /data/media
chown -R media_rw.media_rw *
Click to expand...
Click to collapse
that would explain it: i always use /data/media, didn't find any permission issues yet. thanks.

Problem with permissions in folder (Installing GTA3 on Jelly Bean)

I was going to install GTA 3 on my nexus and left him downloading the game data... when i return to my phone after a while the download stopped and when i open the app it crashes...
I re install the app without success, because now GTA3 crash on accepting EULA!!!
When i remove the app wiping data and cache i have verified that in /sdcard/Android/data/ a folder called "com.rockstar.gta3" remains, and when i tried to delete it says that i have no permissions.
i tried to change permissions on Root Explorer and with adb from my PC with no luck, it keeps saying that i can´t change permissions on that folder.
Code:
[email protected]:/storage/sdcard0/Android/data # ls -l
drwx------ system sdcard_rw 1970-01-01 00:00 com.rockstar.gta3
[email protected]:/storage/sdcard0/Android/data #
Try to change permissions:
Code:
[email protected]:/storage/sdcard0/Android/data # chmod -F 777 com.rockstar.gta3/
Bad mode
10|[email protected]:/storage/sdcard0/Android/data #
even if i try to change the owner of the file it wont let me...
Code:
10|[email protected]:/storage/sdcard0/Android/data # chown root com.rockstar.gta3/
Unable to chown com.rockstar.gta3/: Operation not permitted
10|[email protected]:/storage/sdcard0/Android/data #
By the way i'm on Jelly Bean and dont want to setup all over again...
Does anyone have a clue how can i solve this?

Have the same problem. Cant get rid of that folder

GTA 3 has a downloader that easily corrupts the files it downloads. You need a stable internet connection to download and install the game.
Your screen also must stay on for it to download properly.
Sent from my Galaxy Nexus using xda app-developers app

The installer really messes up the filesystem of a JellyBean GNex. Apps like "Diskusage" sees the "com.rockstar.gta3"-folder as a partition
The only solution i found to fix this is to make a nandroid backup + manual backup of the "sdcard" and then relocking and unlocking the bootloader of the phone. (Only method i know to completely wipe the phone and "sdcard").
Then restore nandroid and copying the sdcard files back.

maybe this help. Just flash it. http://forum.xda-developers.com/showpost.php?p=27515966&postcount=20011

Same with me

me too
i can't play gta 3 too it crashes

Same problem on my galaxy nexus and on my galaxy s plus cm10 ROM

You should be able to delete from /data/media
If you want to chown, you would have to do that from /data/media also.
The sdcard is a symlink...