Database Info

[ROM] (update 7/22) Very speedy port of JacHero2.7.3 32B and now with Compcache

Hello all.
First many thanks to Fatal1ty Justanothercroud haykuro NK02 and the many other developers that made doing all this possible. Also now have to add on cyanogen thanks for the info on compcache as has been added to the rom.
This is a complete port including kernal with thankz again to dazcox5181 and made some modifications myself. Is very stable build on my 32B Ion and runs very quickly used for about 8 hours already and no loading screen yet. Al widgets are working and is FULL version for now. No lag between any screens. Is now a complete and very quick rom based on JAC heros build some fatal1ty thrown in and then some of my own mods.
Please try and let me know what you think.
Steps so far:
More optimized Rosie.apk but keeping most widgets here but foot prints and htc sync removed
32b boot img - fully working
correct wlan.ko file included - wifi works
swap on partiton 3 os sd card solved by dazcox5181 first used his idea in making boot.img for my next release good work dazcox. included your changes and working on other modifications to the kernal yet.
Browser don't always close anymore.
For board 32B only http://www.mediafire.com/?tldxy1i9zdn TheArtiszanR0.9 Released 7/22/2009 11.02AM EST
working well on my Google I/O device
next realease will have updated working boot.img and other modifications.
lightly modified rosie.apk for speed and looking in to persistant browser. (don't close all the time) keep same for other apps.
For this rom to working correctly you will need to have 3 partitions on your memory card.
Fat32
ext2/3
linux-swap
in that correct order The swap partition will need to be atleast 32 mb. Making larger won't help as that is the size I have left to. may change later but 32 seems to be more then suffcient.

space holder

Will you be using fatal1tys boot.img?

Apps
I would am only looking to try ROM's with Exchange support at this stage so I would love to see ActiveSync support...

As of right meow. Yes it will be using the same one fate does until I get time later to make other modifications.
As being it is a hero rom it will have the full htc mail app which suppers exchange over mobile network. I am not sure if activesync is capable yet or not.
Pretty much done with at least making the rom fully compaible with the 32B hardware. Just testing everythig now and there will be just a few minor changes and I will upload then first thing tomorrow as home Internet is out for now. Next up will be some more modifications for general optimization. Runs pretty smoothly now and is the full Rosie still with all clocks and weather app working. Will tinker with that some more later on.

what did u mean with direct port?
if you use the boot.img from fatality, the rom wil not be as fast as on the g1, because of the kernel (i hope i understand this right)
so you will get a port only with a different look as the one from fatal1ty
or do you port the moddifierd kernel from cyanogen?
you can get swapper working using this code
adb remount
adb shell mount -w -o remount -t yaffs2 /dev/block/mtdblock3 /system
adb shell ln -s /system/xbin/bb/busybox /system/bin/busybox
adb shell mount -r -o remount -t yaffs2 /dev/block/mtdblock3 /system
Click to expand...
Click to collapse

If your not porting the kernel its the same as has already been 'ported' so is there a point?

Hi mate
Once these commands have been run, I have then installed swapper from the market. What value do I set my swap partition to in swapper ? Assume I am setting swapper to use a swap parition rather than /sdcard/swapfile.swp ?
Thanks.
kingchris said:
what did u mean with direct port?
if you use the boot.img from fatality, the rom wil not be as fast as on the g1, because of the kernel (i hope i understand this right)
so you will get a port only with a different look as the one from fatal1ty
or do you port the moddifierd kernel from cyanogen?
you can get swapper working using this code
Click to expand...
Click to collapse

Sorry I beat you too it, see my posts it's so simple you'll kick yourself (like I did)
extract boot.img from normal jachero, rename init.trout.rc to init.sapphire.rc
repack
flash
done.

That is what I am working now I have the boot.imig extracted and looking the other code to see if can be made quicker. Going to have a customized Rosie as well so it will have most usability and less space more speed. Unlike the other one with flip clock and others not working to well. The one I posted above i working good on mines so far.

what do you guys think the best setup for swapper would be for the build as again I am trying to start with a FULL hero and will also keep superlite from JAC's crew as well
currently the userinit.sh is set to
32 / 60
I was thinking of
64 / 40
What is everyones opinion both seem to work fine for me atm I have 64/40 running for about 2 hours and have not had a rosie loading spin once. did get it once or twice on 32/60 but that was having flash games up in browser.

Uploading will be done soon. new version fully working and very speed with some new modifications.

how make i the 3 partitions on my memory card?
thanks for help

Hi all
I have 3 partitions on my class 6 SD, FAT32/EXT2/SWP in order, 7GB/500MB/32MB in size.
I got following mesage aplying update.zip after wiping.
--- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:Corrupt file:
data/app_s/htcmsgwidgets.odex
E:Verification failed
Installation aborted
Anyone can help?

the development of 32A Roms have not kept up with the ones of 32B Roms....
Im feeling lonely Here!

how make i the 3 partitions on my memory card?
thanks for help

phosphato said:
Hi all
I have 3 partitions on my class 6 SD, FAT32/EXT2/SWP in order, 7GB/500MB/32MB in size.
I got following mesage aplying update.zip after wiping.
--- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:Corrupt file:
data/app_s/htcmsgwidgets.odex
E:Verification failed
Installation aborted
Anyone can help?
Click to expand...
Click to collapse
I've got the same message

boy4ngage said:
how make i the 3 partitions on my memory card?
thanks for help
Click to expand...
Click to collapse
download ubuntu live linux cd
boot to cd and run partition manager
change drive type at top right to memory card, delete partitions, create new ones, make lage fat32 partiton, then 300-500meg for ext 3, and only 32-60 for swap

If you have a card reader you can use any partitioning program like paragon.
or in Recovery console in ADB on PC can do the following should work with a hypothetical 2 gb card.
#parted /dev/block/mmcblk0
#print (to verfiy we know what size card we are dealing with, the details should be straight forward)
rm 1
rm 2
mkpartfs primary fat32 0 1200
mkpartfs primary ext2 1200 1700
mkpartfs primary linux-swap 1700 1732

I got following mesage applying update.zip after wiping.
--- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:Corrupt file:
data/app_s/htcmsgwidgets.odex
E:Verification failed
Installation aborted
I'm sorry but why did we have this message when applying update ?
Can you answer us TheArtiszan
Thank you.

[INFO][32B] [PORT/FIX] for [ROM] JACxHEROSkiv2.1- JAC/CC 2.83.x posted in Dream Forum

This is for those who have a Sapphire 32B who had issues running Compcache in the 2.0/1 JACxHEROSki.
The problem is that the Magic convert script included copies a 32A .img file to the boot flash. I removed the lines that do this and things seem to work fine. This must be done after flashing the new image, but before running the script.
Here are the steps to be done immediately after booting to new image, but BEFORE running MAGIC script:
1. Download the modified MAGIC script attached to this message and rename it to remove the .TXT extension (should be just "MAGIC")
2. Use ADB Push to push the modified MAGIC script to /sdcard
3. Use ADB Shell and enter the following:
su
mount -o remount,rw /dev/block/mtdblock3 /system
cp /sdcard/magic /system/bin
cd /
rwsystem
magic
4. Choose MyTouch.
5. Edit user.conf for desired settings.
6. Use reboot command to reboot phone.
I would also like to qualify this by saying this worked for me, and this is my first share of this sort with this forum. So, please use this at your own risk.
Good luck.

Hello,
is there a chance for a 32A version of your latest rom?
regards
endebe

Thanks, ill try later

Yeah man ! Thx for the trick Works fine !

I'm still wondering what s best... compcache with backing swap, or linux swap alone ?
What's your opinion ?

on my 32b the g-sensor doenst work.. ist there a fix?!

psxx said:
on my 32b the g-sensor doenst work.. ist there a fix?!
Click to expand...
Click to collapse
You're right, doesn't work anymore on my 32B too

just run the shell script
su
rwsystem
magic
-then press M for mytouch
wifi and gsensor both work after

Very nice.
I'm just waiting for someone to package the JACxHeroSki 2.1 kernel so I can apply it directly over my MCR 2.2e from Paul @ MoDaCo! Right now, I'm using Cyanogen's 4.1.8 kernel, which isn't bad...but I hear that the JAC one is far superior.

dills84 said:
just run the shell script
su
rwsystem
magic
-then press M for mytouch
wifi and gsensor both work after
Click to expand...
Click to collapse
i already did this... but gsensort wont work after... i tried... no autorote... no apps with gsenor are working

compcache is working naow with this script, but no wifi and gsensor, without this scrips works g sensors and wifi

well this script is relativ simple... the first just remounts the fs to rw and the "2nd" part just replayces 3 libs..
i checked twice... but gsensor doenst work with my phone... i had tha same issue on 1.7r2... later i used the port from setenza01 which had a working g-sensor.
so please if someone know how to fix the G-sensor let me know!

jacko6969 said:
This is for those who have a Sapphire 32B who had issues running Compcache in the 2.0/1 JACxHEROSki.
The problem is that the Magic convert script included copies a 32A .img file to the boot flash. I removed the lines that do this and things seem to work fine. This must be done after flashing the new image, but before running the script.
Here are the steps to be done immediately after booting to new image, but BEFORE running MAGIC script:
1. Download the modified MAGIC script attached to this message and rename it to remove the .TXT extension (should be just "MAGIC")
2. Use ADB Push to push the modified MAGIC script to /sdcard
3. Use ADB Shell and enter the following:
su
mount -o remount,rw /dev/block/mtdblock3 /system
cp /sdcard/magic /system/bin
cd /
rwsystem
magic
4. Choose MyTouch.
5. Edit user.conf for desired settings.
6. Use reboot command to reboot phone.
I would also like to qualify this by saying this worked for me, and this is my first share of this sort with this forum. So, please use this at your own risk.
Good luck.
Click to expand...
Click to collapse
To be honest, you don't have to use this script at all, the script is already in there you just need to run this command.
rwsystem
magic
m
reboot

Hi... By stripping the sapphire.img from the script, you're only solving part of the problem (the compcache part).
Actually sapphire.img is important for you to be able to turn on g-sensors.
Here's the solution I posted on the T-Mobile Android forums. ( http://forums.t-mobile.com/tmbl/board/message?board.id=AndroidDev&thread.id=13826 )
It replaces the some of the files with the ones found in ZeroXd's Hero.
-----
Download the following file, that I put together: http://www.megaupload.com/?d=Q759VAG2
This file fixes the compcache problem found in JACxHeroSki v.2.0 and v.2.1. I don't know if this will work for any later versions of the ROM because they didn't exist when I tried it all.
I take no credit for any of this. I just put everything together and zipped it up. All the included files and the knowledge it took to put all this together came from the wonderful people at the Dream forums on xda-developers.com. --eatabagel
Thanks especially to the following awesome devs:
For the ROMs -
JustAnotherCrowd
CCyrowski
For the 32B files (from ZeroXd 5.2r4) -
Twistedumbrella
For the instructions -
Setenza01
============
Instructions
============
Run all of this after flashing JACxHeroSki 2.0 or 2.1, but before running the "magic" command. I assume that your install went well (that means you did everything you needed to do: wipe, clean out ext2/3, etc.). At the stage you run the following commands, you should have a working install of JACxHeroSki 2.0 or 2.1 that hasn't yet been 'fixed' for 32B. That means no WiFi yet.
1. Copy file onto /sdcard
2. Either from a terminal emulator (i.e., Better Terminal Emulator) or from adb shell, type the following:
cd /sdcard
unzip sapphire32bfix.zip
su
rwsystem
cp /sdcard/sapphire32bfix/sapphire/* /system/bin/sapphire
cp /sdcard/sapphire32bfix/sensors.sapphire.so /system/lib/hw
cd /
magic
3. Type 'm' for magic
4. Reboot. Compcache and Wifi should all run perfectly now. No more home screen loads!!!!

I was going to suggest the same solution but you beat me to it.
I dont know if I like the comp cache with vm... it seems slower...
I really like the ZeroXd 5.2rX it seems to be the most responsive...

zambezy said:
I was going to suggest the same solution but you beat me to it.
I dont know if I like the comp cache with vm... it seems slower...
I really like the ZeroXd 5.2rX it seems to be the most responsive...
Click to expand...
Click to collapse
Yea, I agree, having Compcache is definately slower, I don't know about the VM part though.
They did a comparison btwn Linux-Swap and Compcache and Linux-Swap is the winner for speed and I think so too. As for VM I don't think it does anything, I might turn it off to see what happens.

Sweetness! Did the fix and it worked. I finally have landscape and wifi works! Haven't tested bluetooth yet. But other than the messed up screen wake my phone runs flawlessly. I'd have to say that JACxHeroSki 2.1 is the best Hero rom out right now.

solved! thank your for there these files

eatabagel said:
Hi... By stripping the sapphire.img from the script, you're only solving part of the problem (the compcache part).
Actually sapphire.img is important for you to be able to turn on g-sensors.
Here's the solution I posted on the T-Mobile Android forums. ( http://forums.t-mobile.com/tmbl/board/message?board.id=AndroidDev&thread.id=13826 )
It replaces the some of the files with the ones found in ZeroXd's Hero.
-----
Download the following file, that I put together: http://www.megaupload.com/?d=Q759VAG2
This file fixes the compcache problem found in JACxHeroSki v.2.0 and v.2.1. I don't know if this will work for any later versions of the ROM because they didn't exist when I tried it all.
I take no credit for any of this. I just put everything together and zipped it up. All the included files and the knowledge it took to put all this together came from the wonderful people at the Dream forums on xda-developers.com. --eatabagel
Thanks especially to the following awesome devs:
For the ROMs -
JustAnotherCrowd
CCyrowski
For the 32B files (from ZeroXd 5.2r4) -
Twistedumbrella
For the instructions -
Setenza01
============
Instructions
============
Run all of this after flashing JACxHeroSki 2.0 or 2.1, but before running the "magic" command. I assume that your install went well (that means you did everything you needed to do: wipe, clean out ext2/3, etc.). At the stage you run the following commands, you should have a working install of JACxHeroSki 2.0 or 2.1 that hasn't yet been 'fixed' for 32B. That means no WiFi yet.
1. Copy file onto /sdcard
2. Either from a terminal emulator (i.e., Better Terminal Emulator) or from adb shell, type the following:
cd /sdcard
unzip sapphire32bfix.zip
su
rwsystem
cp /sdcard/sapphire32bfix/sapphire/* /system/bin/sapphire
cp /sdcard/sapphire32bfix/sensors.sapphire.so /system/lib/hw
cd /
magic
3. Type 'm' for magic
4. Reboot. Compcache and Wifi should all run perfectly now. No more home screen loads!!!!
Click to expand...
Click to collapse
Thanks you, its really works fine

Hi guys, could someone please host the fix file on mediafire or filehosting as i can't download it from megaupload nor rapidshare . Would be really nice
Thx in advance

[HOW-TO] ROM-HACKING: init.rc ext2-auto-mount / ROM Signing / ROM Kitchen

AS MENTIONED IN THE INTRODUCTION TEXT THIS HAS ONLY BEEN TESTED ON AMON RA ROM 1.6.2 BUT SHOULD REALLY WORK ON ANY ROM THAT HAS NO EXT2 AUTO-MOUNT. AND YEAH THIS WHOLE PROCESS HAS BEEN DONE ON A 32a BOARD. FOR THOSE THAT TRY THIS ON OTHER ROMS LET ME KNOW HOW IT GOES.
I've searched and shuffled through the entire forum and made inquiries to ROM authors without much light being shed on this issue. I doubt I am the only one who has been looking for a way of doing this so I decided to do a small HOW-TO. Here I will explain step by step as to how you can implement a script to be part of your ROM that will auto mount an ext2 partition on boot up if such partition is present. I have included all the tools I've used in order to pull this off, and as the title suggests this has only been done on Amon Ra's latest 1.6.2 ROM. In order to follow these instructions you are expected to allready have set up an adb enviroment on your linux box and for the signing process to work you must have sun-java present, the gnu java wont work. And of course a microSD card with an ext2 partition
1. Download install.sh to your home directory
Code:
wget http://www.grindhouse.no/androidtools/install.sh
chmod a+x install.sh
2. Now execute the install.sh script which will create a directory to work in and download a tool and script package and unpack it.
Code:
./install.sh
When the install.sh script is done you need to move the mkbootimg preferebly to your tools directory of your SDK.
Code:
mv toolstomove/mkbootimg <path/to/sdk/tools/mkbootimg>
3. Unpack the RA1.6.2 ROM into a directory in your home dir. In this HOW-TO we will use directory name "ra1.6.2" as an example through out the entire process.
4. Copy the boot.img from ra1.6.2 to the ROM-cooker dir
Code:
cp $HOME/ra1.6.2/boot.img $HOME/ROM-cooker/boot.img
cd $HOME/ROM-cooker
5. Use unpack.pl to extract the ramdisk from the boot image. I've modified the script a little so it automates the entire process and decompresses the ramdisk to a directory
Code:
./unpack boot.img
6. Now you can either replace the init.rc file here with the one I've included in this package or you can add these lines by yourself. In wich case do the following
Code:
cd boot.img-ramdisk
pico init.rc
Press CTRL+w and then CTRL+t and input 27. hit enter. This will take you to line 27 of init.rc so you can add a line right before the init process remounts the rootfs in read-only mode. Add following line:
Code:
mkdir /sdext2 0771 system system
Now scroll down to the end of the init.rc file and add the following:
Code:
service mountsdext2 /system/bin/mountsd
user root
group root
oneshot
7. You have now edited (or replaced) your init.rc file and prepared it to execute a script on boot that will detect an ext2 partition and boot it if there is one to be found. Now you have to make the mountsd script a part of the ROM. Do the following:
Code:
cd $HOME/ROM-cooker
mv toolstomove/mountsd $HOME/ra1.6.2/system/bin/mountsd
rm -rf toolstomove
8. Now that the init.rc file is sorted out and mountsd has been placed in /system/bin of the ROM so it is time to re-pack the boot.img:
Code:
cd $HOME/ROM-cooker
./repack boot.img-kernel boot.img-ramdisk boot.img
rm $HOME/ra1.6.2/boot.img
mv boot.img $HOME/ra1.6.2/boot.img
9. Your ROM now has a new boot image with an updated init.rc and the /system/bin dir has the script needed to auto-mount the microsd ext2. Now you must re-zip the ROM and sign it. Do the following:
Code:
cd $HOME/ra1.6.2
zip -r update.zip *
mv update.zip $HOME/ROM-cooker/update.zip
cd $HOME/ROM-cooker
./sign.pl update.zip
10. The ROM is now signed and you now have a file called update-signed.zip. Connect the phone to your computer and execute thus:
Code:
./push update-signed.zip
11. Now you are ready to flash the modified ROM which will auto-mount an ext2 partition on your microSD. There is no need to wipe before flashing. If you have no prior experience with ROM flashing or whatever just backup your current install. If you're using OpenHOME or anything similar, nothing will be changed or damaged but if you're using MontAlbert's themes with the ROM you will have to flash them again after flashing this modified ROM.
Code:
adb reboot recovery
12. Flash from choose zip and of course choose update-signed.zip. Reboot. After the system boots up again you can now check whats what with either one of the commands:
Code:
[email protected]:~$ adb shell mount | grep sdext2
/dev/block/mmcblk0p2 on /sdext2 type ext2 (rw,noatime,nodiratime,errors=continue)
[email protected]:~/boot$ adb shell busybox df -h | grep sdext2
/dev/block/mmcblk0p2 893.7M 13.0K 846.0M 0% /sdext2
13. Voila! Your RA 1.6.2 ROM now detects and mounts your microSD ext2 partition on boot. Woohoo?
I hope the HOW-TO was easy reading and that you have succeeded in hacking up your ROM. I know that certain ROMs have this as a built-in function but Amon Ra's does not. But since alot of people including myself use his ROM because of the high speed and stability I thought I should contribute to his project and add a cool (and missed?) function to it.
Mind you that you can use the ROM-cooker set to further adjust and hack up the ROM as you see fit. Happy learning!

Very nice!
Now the question many people will ask : why would you automount ext2 if you don't use apps2sd ?

I personally have ubuntu on my ext2 And besides this approach can be used for a number of things, people who have had the need, or wanted to experiment with init.rc doing things on boot, the mountsd script can easily be altered to do what ever needed.
For me its been a learning curve finding these things out, so by sharing it I may spare some people breaking their backs over this whole init.rc thing. people may want to modify init.rc for whatever reason, so I'm sure people wont have a problem finding a way of putting this to use, and its a subject that isnt all that covered on the forum .. and hey .. at least they get a rom kitchen out of the whole shabang

Very interesting! Thank you.
I used your unpack-program to unpack a recovery-image. It seems to work fine. What I am trying to do is change the state the recovery-image returns the phone to. Would it be possible to just replace your mountsd-script with, for example, a script that installs apps? Or is there a better way to do what Im trying to achieve?
Cheers,
edit: I noticed that on the emulator it is sufficient to just place an apk-file in "data/app" to get it installed. Could it be possible that this is all I need a script to do? :O or could I hurt my poor phone by doing so you think?

sandis84 said:
edit: I noticed that on the emulator it is sufficient to just place an apk-file in "data/app" to get it installed. Could it be possible that this is all I need a script to do? :O or could I hurt my poor phone by doing so you think?
Click to expand...
Click to collapse
That's indeed all you need to do.

Hi!
So I tried to create a signed update.zip, but it failed. It didnt create a "update-script"-file, so my device refused to install it. I wrote my own "update-script"-file, but then it complained "no digest" for the file. How do I solve this?

post the contents of your script people might see whats up

so is this all on linux?
also where are the script files for your tutorial
thanks for the time to put together

sitimber said:
so is this all on linux?
also where are the script files for your tutorial
thanks for the time to put together
Click to expand...
Click to collapse
Says where its at in the first line : )
Code:
wget http://www.grindhouse.no/androidtools/install.sh
But now that I checked, I have to apologize, I see I have a missed payment with my hosting, I'll fix that within the day. Also sorry I havent been answering the few questions here I've been afk cause of surgery.

sitimber said:
post the contents of your script people might see whats up
Click to expand...
Click to collapse
well, I looked in another "update-script" file and found this:
assert compatible_with("0.2") == "true"
assert getprop("ro.product.device") == "dream" || getprop("ro.build.product") == "dream"
show_progress 0.5 0
write_radio_image PACKAGE:radio.img
show_progress 0.5 10
Click to expand...
Click to collapse
So I figured that nothing was essential other then the line "write_radio_image PACKAGE:radio.img". Also ofcourse I made sure it contained the name of my image-file instead of "radio.img". This gave me the "no digest" message, so now I feel unsure on how to create a working update.zip.
edit:
SOLVED! How silly of me. When you sign the update, a hash of each file is put in manifest.mf. Since I added the update-script after signing the file, ofcourse the digest(hash) was missing. Now everything works alot better and I can proceed... until I get stuck again
Cheers,
edit2:
Just to get a better understanding, what exactly does each line do here? Or where can I read about this?
Code:
service mountsdext2 /system/bin/mountsd
user root
group root
oneshot
edit3:
Ok, so I have experimentet, but I still dont manage to solve those last steps. I tried to edit init.rc and just add "mkdir /testdir 0000 system system" where the other directories were created. I then repacked it, zipped it, signed it, put it on my sdcard, started up a custom recovery, installed the update and rebooted. Everything seems to work fine. But when I start adb and check around, I dont see the "testdir"-directory. Also when I check in init.rc my line is gone. Do you guys have an idea of where I went wrong?

sitimber said:
so is this all on linux?
also where are the script files for your tutorial
thanks for the time to put together
Click to expand...
Click to collapse
it doesnot necesarily have to be linux ...you can also do it in windows using cygwin and dsxda's android rom kitchen

[KERNELFIX] damageless/Fresh 2.0b2 kernel w/ Apps2sd REV 3

I have tested the following with the frest 2.1 2.0b2 build and it does enable Apps2SD.
Ver 3 now should work on fresh fine, and damageless (sometimes I found enabling apps2sd on damageless causes lockups at boot, these can be fixed by doing WIPE for DATA for now) :/
MAKE NANDROID BACKUP
This has been tested on: Fresh 2.0b2
ADDED INSTRUCTIONS TO ENABLE ON DAMAGELESS
Also this has been edited so the first few pages refer to the old style before I had signed zips working. xD
Flash the Update Zip Attached VIA recovery menu. That means copy it to the root of your sdcard (aka /sdcard/).
I tested this after a fresh wipe with a blank ext2 partition and one vfat (normal). I did not even boot it first run but you should be able to flash this on an existing rom. Others can test on other roms but I am using this for now on fresh 2.1 2.0b2.
Afterwards run the following after booting
FOR VER 3 SIGNED
Code:
[B]
adb remount
adb shell
cd /system/bin
ln -s /system/xbin/busybox /system/bin/sed
ls -l /system/bin/sed # make sure it exists
cd /
apps2sd on
# should say apps2sd enabled
reboot[/B]
FOR VER 1 SIGNED
Code:
[B]
adb remount
adb shell
cd /system/bin
busybox --install /system/bin
ls -l sed # make sure it exists
cd /
chmod 755 /system/bin/apps2sd
chmod 755 /system/xbin/apps2sd
apps2sd on
# should say apps2sd enabled
reboot[/B]
FOR VER 3 SIGNED for DAMAGELES
Code:
[B]
adb remount
adb shell
cd /
apps2sd on
# should say apps2sd enabled
# below fixes up the scripts generated by the 'apps2sd on' line.. who ever wrote that had it put DOS CR/LF on the ends and thats whats breaking APPS2SD on damageless!
cd /system/etc/init.d
dos2unix 04apps2sd
dos2unix 05userinit
reboot[/B]
Enjoy

Will this work on the other 2.1 ROMs?

I have only tested on fresh 2.1 2.0B . I would think that logically this should work on the other fresh 2.1 2.0 and perhaps Damageless's. As for darchstar's try it I havent run that rom in a few days.

kkruse said:
I have only tested on fresh 2.1 2.0B . I would think that logically this should work on the other fresh 2.1 2.0 and perhaps Damageless's. As for darchstar's try it I havent run that rom in a few days.
Click to expand...
Click to collapse
If someone could test this out and let me know if it works on my ROM then I would love to just use the same method to get it going with the author's permission (credit will be given).

i keep no space left on device when i do this command
cat /dev/zero > /dev/mtd/mtd2

networx2002 said:
i keep no space left on device when i do this command
cat /dev/zero > /dev/mtd/mtd2
Click to expand...
Click to collapse
same for me
cat: write error: No space left of device

If I remember right it is a different file than what he posted...
I will have to check.

Maybe you can help me w/ this... When I adb shell in recovery I get "/#" instead of "#" & I can't "mount -a"...

networx2002 said:
i keep no space left on device when i do this command
cat /dev/zero > /dev/mtd/mtd2
Click to expand...
Click to collapse
Another one with this issue.
Running Fresh 2.1 2.0b2 on a clean install.
Already have a partitioned SD card with apps installed (from fresh 1.1 rom)
Has anyone besides OP gotten this to work?

mrcharlesiv said:
Maybe you can help me w/ this... When I adb shell in recovery I get "/#" instead of "#" & I can't "mount -a"...
Click to expand...
Click to collapse
/# would mean you are adb into recovery......I think

Aye, / # means you are in recovery mode on the phone is all.
Not sure why you aren't able to mount -a. I'm curious if anyone has gotten this method to work yet..?

So I went ahead and did every step despite the errors it gave just to see what happens... It's booting....
EDIT: Seems like it worked. My internal memory dropped by a/b 20 megs and I'm reinstalling everything. Idk.

mrcharlesiv said:
So I went ahead and did every step despite the errors it gave just to see what happens... It's booting....
EDIT: Seems like it worked. My internal memory dropped by a/b 20 megs and I'm reinstalling everything. Idk.
Click to expand...
Click to collapse
K, I attempted to reboot and it hangs at the HTC screen, so I'm going to boot back into recovery and try to continue from the out of space error.

Last night I tried adding a2sd, e2fsck to /system/bin of Fresh and made a directory SD in /system
Then I added to the init.rc
on property:cm.filesystem.ready=1
class_start default
start a2sd
and
service a2sd /system/bin/logwrapper /system/bin/sh /system/bin/a2sd
disabled
oneshot
then mkbootimg and placed that boot.img into fresh's zip and resigned it.
It flashed ok. But still didn't take. I'm still learning, the stuff I did to iniit.rc I was just basically copying and pasting from other roms with a2sd init.rc's I was going to start a thread until I saw this one.

I was able to boot back into recovery and complete the setup past the out of space error (I still get it though) and reboot. It booted up, but apps are still installing to the internal memory, so it did not work.

mrcharlesiv said:
So I went ahead and did every step despite the errors it gave just to see what happens... It's booting....
EDIT: Seems like it worked. My internal memory dropped by a/b 20 megs and I'm reinstalling everything. Idk.
Click to expand...
Click to collapse
Try this from CMD Prompt
Adb remount
Adb shell
# cd /data/app
#pwd
let us know what you get
if data/app it didnt work.

So I've reinstalled about 15 apps and my internal memory is staying at 73...
I'm still kinda worried about those errors I got.

mrcharlesiv said:
Maybe you can help me w/ this... When I adb shell in recovery I get "/#" instead of "#" & I can't "mount -a"...
Click to expand...
Click to collapse
same here... anyone know where to go from here?

mrcharlesiv said:
So I've reinstalled about 15 apps and my internal memory is staying at 73...
I'm still kinda worried about those errors I got.
Click to expand...
Click to collapse
did you try doing what swaze said?
swaze said:
Try this from CMD Prompt
Adb remount
Adb shell
# cd /data/app
#pwd
let us know what you get
if data/app it didnt work.
Click to expand...
Click to collapse

kashb91 said:
did you try doing what swaze said?
Click to expand...
Click to collapse
Way to rain on my parade! Yeah it didn't work. Idk why my memory dropped and stayed lower then?

[A510] Root and Bootloader unlock

Hi,
just to put info at the right place.
A510 root is yet available, thanks to Acer dev..
A100 exploit is still working, at least on current firmwares.
Thanks to Jesse6749, ZeroNull and vdsirotkin (4pda.ru) :
see xda topic here:
http://forum.xda-developers.com/showpost.php?p=25036001&postcount=93
consider installing acer a510 drivers from their website(even if your a510 is currently recognized by your pc)
in addition, some user had bugs at the end of the script, but root is done (su + titanium backup working)
another tool should be mentioned :
http://forum.xda-developers.com/showthread.php?t=1661324
To unlock bootloader (Euclid's Brother ) :
You must have the ability to send adb commands to the tablet.
adb reboot-bootloader
fastboot oem unlock
As a reminder :
Code:
dd if=/dev/block/platform/sdhci-tegra.3/by-name/SOS of=/mnt/sdcard/recovery.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/LNX of=/mnt/sdcard/boot.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/APP of=/mnt/sdcard/system.img
out of this :
(thanks nikagl)
Code:
/dev/block/platform/sdhci-tegra.3/by-name/SOS /dev/block/mmcblk0p1 /recovery
/dev/block/platform/sdhci-tegra.3/by-name/LNX /dev/block/mmcblk0p2 /boot
/dev/block/platform/sdhci-tegra.3/by-name/APP /dev/block/mmcblk0p3 /system
/dev/block/platform/sdhci-tegra.3/by-name/CAC /dev/block/mmcblk0p4 /cache
/dev/block/platform/sdhci-tegra.3/by-name/MSC /dev/block/mmcblk0p5 /misc
/dev/block/platform/sdhci-tegra.3/by-name/FLX /dev/block/mmcblk0p6 /system/vendor /flexrom /flex
/dev/block/platform/sdhci-tegra.3/by-name/AKB /dev/block/mmcblk0p7 ?
/dev/block/platform/sdhci-tegra.3/by-name/USP /dev/block/mmcblk0p8 /aboot (bootloader.blob)
/dev/block/platform/sdhci-tegra.3/by-name/DE2 /dev/block/mmcblk0p9 ?
/dev/block/platform/sdhci-tegra.3/by-name/UDA /dev/block/mmcblk0p10 /data
So you can use these commands:
Code:
dd if=/dev/block/platform/sdhci-tegra.3/by-name/SOS of=/mnt/sdcard/recovery.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/LNX of=/mnt/sdcard/boot.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/APP of=/mnt/sdcard/system.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/CAC of=/mnt/sdcard/cache.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/MSC of=/mnt/sdcard/misc.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/FLX of=/mnt/sdcard/flexrom.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/AKB of=/mnt/sdcard/AKB.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/USP of=/mnt/sdcard/bootloader.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/DE2 of=/mnt/sdcard/DE2.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/UDA of=/mnt/sdcard/data.img

I hope a mod can move at least the AIO toolbox thread to this forum.

Instead of hoping, why don't you contact the A500 forum mod directly?

FloatingFatMan said:
Instead of hoping, why don't you contact the A500 forum mod directly?
Click to expand...
Click to collapse
Good idea. Done.

Update: Thread has been moved.

Has anyone been able to update their SU binaries?
I updated the superuser app and when I checked my binaries (and tried to update them), I get:
"remounting /system as rw... fail"
I'm thinking I need to update my busybox, but the steps in the OP links says I should not. Can anyone enlighten me on this?

salisbury_steak said:
Has anyone been able to update their SU binaries?
I updated the superuser app and when I checked my binaries (and tried to update them), I get:
"remounting /system as rw... fail"
I'm thinking I need to update my busybox, but the steps in the OP links says I should not. Can anyone enlighten me on this?
Click to expand...
Click to collapse
Using the recovery and root scripts I created I was able to update su, etc. I think the mempodroid exploit has some problem with newer version of busybox, also judging from the other thread (Full root for A10x / A5xx) - see my posts over there. The AIO tool also uses that mempodroid exploit... maybe it's better to start using the recovery & root script?
Regards,
Nika.
---------- Post added at 11:22 PM ---------- Previous post was at 10:32 PM ----------
nikagl said:
Using the recovery and root scripts I created I was able to update su, etc. I think the mempodroid exploit has some problem with newer version of busybox, also judging from the other thread (Full root for A10x / A5xx) - see my posts over there. The AIO tool also uses that mempodroid exploit... maybe it's better to start using the recovery & root script?
Regards,
Nika.
Click to expand...
Click to collapse
Sorry, got to recall this post. The new version of busybox does have some problems with mounting through busybox. Doing it directly works, but through busybox it fails. See my post here: 202
Regards,
Nika.

Thanks for the update. So for now... I just leave it as is, right?
Or should I try to update busybox? And yes, I'm using the mempodroid exploit.
Sent from my Acer Iconia A510

salisbury_steak said:
Thanks for the update. So for now... I just leave it as is, right?
Or should I try to update busybox? And yes, I'm using the mempodroid exploit.
Sent from my Acer Iconia A510
Click to expand...
Click to collapse
Yes, definitely leave it like it is.

How to UNROOT & LOCK
Is it poosible to lock and unroot an previously rooted A511? I am not 100% satisfied with the display and would like sending back my a511 and wait for a701.

loerkus said:
Is it poosible to lock and unroot an previously rooted A511? I am not 100% satisfied with the display and would like sending back my a511 and wait for a701.
Click to expand...
Click to collapse
Easiest methods:
Lock = install new ROM (FOTA, if available, or the 1.011 rom and then do FOTA)
Unroot = install new ROM (although that may not cleanup every trace) or factory reset (which is the best method -- but will wipe ALL your data)
Recovery = not possible yet - I don't recall seeing a stock-A511-recovery yet... you can try putting the A510 recovery on (I did that, it seemed to not work but at least wipes away most of the traces of your hack-attempt)
Regards,
Nika.

FOTA says my ROM is up-to-date. So I have to flash. I downloaded from the Stock-ROM forum Acer_AV041_A511_1.011.00_WW_GEN1.zip. But how can I flash it? Sorry to bother you but I don't want to brick my a511.

loerkus said:
FOTA says my ROM is up-to-date. So I have to flash. I downloaded from the Stock-ROM forum Acer_AV041_A511_1.011.00_WW_GEN1.zip. But how can I flash it? Sorry to bother you but I don't want to brick my a511.
Click to expand...
Click to collapse
I have downgraded twice with that ROM. Just rename it to update.zip, make sure the bootloader is unlocked and copy the zip to your external sdcard and reboot into recovery. It will start the downgrade automatically, reboots, will republish your apps (or something like that) and then you can do the FOTA to move up to 1.034 (I think - can't check as my tab is dead...).
Regards,
Nika.

nikagl said:
I have downgraded twice with that ROM. Just rename it to update.zip, make sure the bootloader is unlocked and copy the zip to your external sdcard and reboot into recovery. It will start the downgrade automatically, reboots, will republish your apps (or something like that) and then you can do the FOTA to move up to 1.034 (I think - can't check as my tab is dead...).
Regards,
Nika.
Click to expand...
Click to collapse
Thanks. Now in CWM I get the error:
...
...
Installing update...
assert failed: getprop("ro.product.name") == "a511_ww_gen1"
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted

loerkus said:
Thanks. Now in CWM I get the error:
...
...
Installing update...
assert failed: getprop("ro.product.name") == "a511_ww_gen1"
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
what is your actual firmware region ?
WW, EMEA or PA ?

loerkus said:
Thanks. Now in CWM I get the error:
...
...
Installing update...
assert failed: getprop("ro.product.name") == "a511_ww_gen1"
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
That means you don't have a ww_gen1 A511 device. Yours is probably German (for instance A511_EMEA_DE). You can check that in your device.prop file.
The following is on another forum (translated from Russian):
acer-club said:
On the firmware from another region will be ask only through Customise recovery (someone here wrote that your machines already have this), after removing the check of the firmware from the archive in the installation script (/ META-INF/com/google/android / updater-script) - something like this in the beginning of the installation script:
assert (getprop ("ro.product.name") == "a510_emea_cus1");
this part of the "a510_emea_cus1" on different firmware will be different. Remove all the line.
By necessity, that would not lose the unlock, you need to remove the fill from the new firmware bootloader'a (bootloader.blob file in the root of the archive firmware) and disable the recovery of stock recovery (file / system / etc / install-recovery.sh in the archive or rename the firmware removed), otherwise the whole tablet, and overwrite the unlock will be stitched completely stock firmware.
Next, fill up this way obtained the firmware on the SD card and flashed it through Customise recovery (recovery through the stock it does not work!).
Click to expand...
Click to collapse
It contains some info on what to do, but I think that's way to risky. It did also contain a good hint how to revert recovery! Try to rename the "install-recovery.sh" file back. It's either renamed by the script you executed for root or part of the instructions on how to install the cwm recovery. After this, try to boot a few times and I assume both the recovery and possibly even the unlocked bootloader will be reverted to stock! In that case you can also simply do a factory reset and it will remove the root as well

Rooting via the mempodroid exploid on Acer_AV041_A510_RV28RC02_WW_GEN1 worked as far as I can see (SuperUser and Titanium Backup install and run alright).
Only problem I see is that apps like Titanium Backup and ES File explorer are not able to mount /system as rw and thus are a little limited in there actions. They do not complain on gaining su, that works.
(Re)mount commands via adb shell:
mount -o remount,rw /system
mount -o remount,ro /system
do work as expected.
Any idea's on what is wrong / missing and how to correct it?
Edit:
It seems that a rw mount on / is going OK ???

i used aio tool and rooted and unlocked bootloader...2 questions:
1- how to install a rom now?
2- if i want, can i lock again bootloader and remove root in order to avoid acer assistence troubles?
if i can0t remove it, can i just leave it there? can i install any fota if acer releases it? or acer invalidates guarantee if i need it?

Not working
Hi, I tried this and unfortunately it failed.
PC: Windows 7 64bit
Acer A510: running Android 4.1.2, kernel 3.1.10+, build version Acer_AV051_A510_RV11RC01_WW_GEN1
The A510 is already unlocked using the fastboot method.
Logged inn as administrator, ran runit-win and got:
Full root for A100 ICS. Simple method.
-
-
Device connected. Preparation for executing of the main script.
mkdir failed for /data/local/tools, Permission denied
push: tools/su -> /data/local/tools/su
failed to copy 'tools/su' to '/data/local/tools/su': No such file or directory
Unable to chmod /data/local/tools/*: No such file or directory
remote object '/data/local/tools/mempodroid' does not exist
The file "mempodroid" isn't created!
-
Not getting root!
-
Error!
-
Press any key.

bob497 said:
Hi, I tried this and unfortunately it failed.
Click to expand...
Click to collapse
Install CWM 6.0.1.9 and flash in CWM this zip SuperSu by choose zip from external sdcard or choose zip from sdcard..