Jump to content

Acer Gallant Duo root / hacking tools


Guest PaulOBrien

Recommended Posts

Guest newuser1234567

Has anybody seen significant improvements to battery life after rooting it?

I'm only interested in improving that, and am wary of rooting. Think it's worth it?

Link to comment
Share on other sites

Guest jaapstreepjan

Has anybody seen significant improvements to battery life after rooting it?

I'm only interested in improving that, and am wary of rooting. Think it's worth it?

yes it's worth it, if you uninstall the hogging system apps

Link to comment
Share on other sites

Guest jaapstreepjan

could anybody help me creating a working recovery.fstab?

I need it for compiling Clockworkmod Recovery.

it should be something like this:

/boot emmc /dev/block/mmcblk0p1

/cache ext4 /dev/block/mmcblk0p2

/data ext4 /dev/block/mmcblk0p3

/recovery emmc /dev/block/mmcblk0p21

/sdcard vfat /dev/block/mmcblk1p4 /dev/block/mmcblk4

/system ext4 /dev/block/mmcblk0p26

maybe Paul could help ?

Link to comment
Share on other sites

@jaapstreepjan

I am glad you are working on CWM for the Liquid Gallant. It is important to have this tool

for nandroid backup and it is the base for future custom ROM, if any.

Apparently the first thing is to get the partition mapping and mainly the /boot and /recovery

in the phone.

As a simple user, I gathered some information below.

There are some interesting script/applicatoins for online nandroid backup:

Online Nandroid backup script :

http://forum.xda-dev...d.php?t=1620255

Currently for the Liquid Gallant, the right command line script is:

onandroid --phone --old --storage /mnt/sdcard2

but of course it cannot find /boot and /recovery.

Online Nandroid backup Android application using the above script :

https://play.google....r3t1c.onnandbup

The Android app is interesting since it updates automatically the script,

and optionally installs utility like makeyaffs if missing on the running phone.

Currently it uses /mnt/sdcard per default as storage and hence fails since there is not

sufficient disk space. And since there is no patch file yet for the phone, it cannot

find /boot and /recovery for backup.

For nandroid backup for Liquid Gallant, there are particularities to be considered:

- /mnt/sdcard2 is the external SD card where nandroid backup should be stored.

- /mnt/sdcard is to be backuped

- /mnt/sdcard/.android_secure is empty, maybe sec_ro to be backuped ?

From the scatter file (number of sectors for each partition), from the size of partitions dump using 'dd' command,

from the size of each file from Acer_AV041_E350_1.000.08_EMEA_FR.zip, one probably could

deduces a right mapping.

So if /boot is mapped to emmc /dev/block/mmcblk0p1, there is probably a problem

since this partition has only 1 KB (result of dd command), and boot.img size is 3660KB.


In Acer_AV041_E350_1.000.08_EMEA_FR.zip:

http://vache-android.com/?dir=Smartphones/Liquid%20Gallant

http://vache-android.com/Smartphones/Liquid%20Gallant/OS%20Images/Dual%20SIM/EMEA_FR/Acer_AV041_E350_1.000.08_EMEA_FR.zip


system.img 452MB 474 229 044 bytes

logo.bin 25.2KB 25 840 bytes

MT6575_Android_scatter_emmc.txt 448 448 bytes

preloader_simcom75_cu_ics.bin 102.1 KB 104 588 bytes

uboot_simcom75_cu_ics.bin 166.5KB 170 480 bytes

boot.img 3660KB 3 747 840 bytes

recovery.img 4178KB 4 278 272 bytes

secro.img 4252KB 4 354 232


adb shell

shell@android:/ # ls -l

ls -l

drwxr-xr-x root	 root			 2012-10-11 22:30 acct

-rw-r--r-- root	 root		 1203 1970-01-01 01:00 advanced_meta_init.project.rc

-rw-r--r-- root	 root	 31594 1970-01-01 01:00 advanced_meta_init.rc

drwxrwx--- system cache			 2012-10-12 17:02 cache

dr-x------ root	 root			 2012-10-11 22:30 config

lrwxrwxrwx root	 root			 2012-10-11 22:30 d -> /sys/kernel/debug

drwxrwx--x system system		 2012-10-11 22:31 data

-rw-r--r-- root	 root		 168 1970-01-01 01:00 default.prop

drwxr-xr-x root	 root			 2012-10-11 22:31 dev

lrwxrwxrwx root	 root			 1970-01-01 01:00 emmc@android -> /dev/block/mmcblk0p6

lrwxrwxrwx root	 root			 1970-01-01 01:00 emmc@cache -> /dev/block/mmcblk0p2

lrwxrwxrwx root	 root			 1970-01-01 01:00 emmc@ebr1 -> /dev/block/mmcblk0p1

lrwxrwxrwx root	 root			 1970-01-01 01:00 emmc@fat -> /dev/block/mmcblk0p4

lrwxrwxrwx root	 root			 1970-01-01 01:00 emmc@sec_ro -> /dev/block/mmcblk0p5

lrwxrwxrwx root	 root			 1970-01-01 01:00 emmc@usrdata -> /dev/block/mmcblk0p3

lrwxrwxrwx root	 root			 2012-10-11 22:30 etc -> /system/etc

-rwxr-x--- root	 root	 106928 1970-01-01 01:00 init

-rwxr-x--- root	 root		 149 1970-01-01 01:00 init.aee.customer.rc

-rwxr-x--- root	 root	 12600 1970-01-01 01:00 init.factory.rc

-rwxr-x--- root	 root		 2344 1970-01-01 01:00 init.goldfish.rc

-rwxr-x--- root	 root		 3511 1970-01-01 01:00 init.project.rc

-rwxr-x--- root	 root	 26841 1970-01-01 01:00 init.rc

-rwxr-x--- root	 root	 12063 1970-01-01 01:00 init.usb.rc

-rw-r--r-- root	 root		 9609 1970-01-01 01:00 meta_init.rc

drwxrwxr-x root	 system		 2012-10-11 22:30 mnt

dr-xr-xr-x root	 root			 1970-01-01 01:00 proc

lrwxrwxrwx root	 root			 1970-01-01 01:00 res -> /system/res

drwx------ root	 root			 2012-07-30 11:58 root

drwxr-x--- root	 root			 1970-01-01 01:00 sbin

lrwxrwxrwx root	 root			 2012-10-11 22:30 sdcard -> /mnt/sdcard

lrwxrwxrwx root	 root			 2012-10-11 22:30 sdcard2 -> /mnt/sdcard2

drwxr-xr-x root	 root			 2012-10-11 22:30 sys

drwxr-xr-x root	 root			 2012-10-04 12:57 system

-rw-r--r-- root	 root		 272 1970-01-01 01:00 ueventd.goldfish.rc

-rw-r--r-- root	 root		 4388 1970-01-01 01:00 ueventd.rc

lrwxrwxrwx root	 root			 2012-10-11 22:30 vendor -> /system/vendor

shell@android:/ #



partno: start_sect nr_sects partition_name

emmc_p1: 00000020 00000002 "ebr1"

emmc_p2: 0010f720 00100000 "cache"

emmc_p3: 0020ff20 00200000 "usrdata"

emmc_p4: 00410720 003328e0 "fat"

emmc_p5: 00009f00 00002800 "sec_ro"

emmc_p6: 0000ef20 00100000 "android"


From the Liquid Gallant :

emmc@android -> /dev/block/mmcblk0p6

emmc@cache -> /dev/block/mmcblk0p2

emmc@ebr1 -> /dev/block/mmcblk0p1

emmc@fat -> /dev/block/mmcblk0p4

emmc@sec_ro -> /dev/block/mmcblk0p5

emmc@usrdata -> /dev/block/mmcblk0p3




ls -l /dev/block

brw------- root	 root	 254, 0 2012-10-11 22:32 dm-0

brw------- root	 root	 254, 1 2012-10-11 22:32 dm-1

brw------- root	 root	 254, 2 2012-10-11 22:32 dm-2

brw------- root	 root	 254, 3 2012-10-11 22:32 dm-3

brw------- root	 root	 254, 4 2012-10-11 22:32 dm-4

brw------- root	 root	 254, 5 2012-10-11 22:33 dm-5

brw------- root	 root	 254, 6 2012-10-11 22:33 dm-6

brw------- root	 root	 254, 7 2012-10-11 22:33 dm-7

brw------- root	 root	 254, 8 2012-10-11 22:33 dm-8

brw------- root	 root	 254, 9 2012-10-11 22:33 dm-9

brw------- root	 root	 7, 0 2012-10-11 22:30 loop0

brw------- root	 root	 7, 1 2012-10-11 22:30 loop1

brw------- root	 root	 7, 2 2012-10-11 22:30 loop2

brw------- root	 root	 7, 3 2012-10-11 22:30 loop3

brw------- root	 root	 7, 4 2012-10-11 22:30 loop4

brw------- root	 root	 7, 5 2012-10-11 22:30 loop5

brw------- root	 root	 7, 6 2012-10-11 22:30 loop6

brw------- root	 root	 7, 7 2012-10-11 22:30 loop7

brw-rw---- root	 root	 7, 8 2012-10-11 22:33 loop8

brw-rw---- root	 root	 7, 9 2012-10-11 22:33 loop9

brw------- root	 root	 179, 0 2012-10-11 22:30 mmcblk0

brw------- root	 root	 179, 8 2012-10-11 22:30 mmcblk0boot0

brw------- root	 root	 179, 16 2012-10-11 22:30 mmcblk0boot1

brw------- root	 root	 179, 1 2012-10-11 22:30 mmcblk0p1

brw------- root	 root	 179, 2 2012-10-11 22:31 mmcblk0p2

brw------- root	 root	 179, 3 2012-10-11 22:31 mmcblk0p3

brw------- root	 root	 179, 4 2012-10-11 22:30 mmcblk0p4

brw------- root	 root	 179, 5 2012-10-11 22:30 mmcblk0p5

brw------- root	 root	 179, 6 2012-10-11 22:30 mmcblk0p6

brw------- root	 root	 179, 24 2012-10-11 22:30 mmcblk1

brw------- root	 root	 179, 25 2012-10-11 22:30 mmcblk1p1

drwxr-xr-x root	 root			 2012-10-11 22:30 platform

drwxr-xr-x root	 root			 2012-10-11 22:31 vold



---

brw------- root	 root	 179, 8 2012-10-11 22:30 mmcblk0boot0 boot ?

brw------- root	 root	 179, 16 2012-10-11 22:30 mmcblk0boot1 ?

brw------- root	 root	 179, 1 2012-10-11 22:30 mmcblk0p1 ebr1

brw------- root	 root	 179, 2 2012-10-11 22:31 mmcblk0p2 cache

brw------- root	 root	 179, 3 2012-10-11 22:31 mmcblk0p3 usrdata = data ?

brw------- root	 root	 179, 4 2012-10-11 22:30 mmcblk0p4 fat

brw------- root	 root	 179, 5 2012-10-11 22:30 mmcblk0p5 sec_ro

brw------- root	 root	 179, 6 2012-10-11 22:30 mmcblk0p6 android = system ?

brw------- root	 root	 179, 24 2012-10-11 22:30 mmcblk1

brw------- root	 root	 179, 25 2012-10-11 22:30 mmcblk1p1 sdcard ?


# 'dd' execution time, size of file produced

# < 1s 1MB

dd if=/dev/block/mmcblk0boot0 of=/sdcard2/clockworkmod/backup/boot0.dsk	 bs=8192

ls -l /sdcard2/clockworkmod/backup/


# < 1s 1MB

dd if=/dev/block/mmcblk0boot1 of=/sdcard2/clockworkmod/backup/boot1.dsk	 bs=8192

ls -l /sdcard2/clockworkmod/backup/


# 115 s 512 MB

dd if=/dev/block/mmcblk0p6 of=/sdcard2/clockworkmod/backup/system.dsk	 bs=8192

ls -l /sdcard2/clockworkmod/backup/


# 37s 512 MB

dd if=/dev/block/mmcblk0p2 of=/sdcard2/clockworkmod/backup/cache.dsk	 bs=8192

ls -l /sdcard2/clockworkmod/backup/


# < 1s 1KB

dd if=/dev/block/mmcblk0p1 of=/sdcard2/clockworkmod/backup/ebr1.dsk	 bs=8192

ls -l /sdcard2/clockworkmod/backup/


# < 1s 5MB

dd if=/dev/block/mmcblk0p5 of=/sdcard2/clockworkmod/backup/sec_ro.dsk	 bs=8192

ls -l /sdcard2/clockworkmod/backup/


# 104s 1.5 GB

dd if=/dev/block/mmcblk0p4 of=/sdcard2/clockworkmod/backup/fat.dsk	 bs=8192

ls -l /sdcard2/clockworkmod/backup/


# 62s 1022.3 MB

dd if=/dev/block/mmcblk0p3 of=/sdcard2/clockworkmod/backup/data.dsk	 bs=8192

ls -l /sdcard2/clockworkmod/backup/


# seems to be the /sdcard2, size > 3GB at least! operation interrupted

dd if=/dev/block/mmcblk1p1 of=/sdcard2/clockworkmod/backup/sdcard.dsk	 bs=8192

ls -l /sdcard2/clockworkmod/backup/


Link to comment
Share on other sites

Hi, we had an upgrade yesterday on the acer gallant, and of course the superuser have been deleted. Do u think we can retry Paul's rooting method ?

I used bin4ry method, it works well. I did not try Paul's method this time.

Link to comment
Share on other sites

Guest Neticus

Happy to see that my FTP is used :)

Greetings to the forum, and specially to Vache. I'm a reader of this forum more than one year ago and this is my first post. I've learned a lot here and wanna thank to Vache for all good things done whith my Liquid MT. I still use it on ROM Gingerounay 3.1 and works great, better nowadays just with a couple of tweaks more.

This has been the reason to upgrade to Gallant Duo bought @ Expansys website, after being sure to reach root (thanks Paul)

but now I would like to see something like Gingerounay on my new Gallant Duo.

Of course we need CWM for it, and maybe anybody will go on as well......

I've tryed to download sdcard_update and the other file (i guess is the image of original OS) but got network failure at 10%

When finnally downloaded (will try again later) how do we handle this files, with flashtool or from sdcard?

I hope will finish both downloads... ACER_AV041_E350 is reaching 30%

Regards,

Neticus

Gallant is great for 200€, and I think just few tweaks would make it even better.

Link to comment
Share on other sites

Hello,

There is a difference in the scatter file from Acer and from Modaco.

Is it important?

From latest Acer's ROM (OS_Acer_E350.1.000.18.EMEA.FR_A40I_A.zip) :

MT6575_Android_scatter_emmc.txt

__NODL_BMTPOOL 0xFFFF0050

From Modaco:

MT6575_android_scatter_emmc.duo.modaco.txt

__NODL_BMTPOOL 0xE89E0000

Link to comment
Share on other sites

Guest Abducted

Thanks for the guide! I just flashed my phone with the ROM from vache's server. I already rooted my phone before but this time i want to try your method to keep the system update function.

However i have a SOLO version not a DUO and the scatter file says it for DUO. Just want to make sure i can also use this scatter file to flash my SOLO gallant?

Edited by Abducted
Link to comment
Share on other sites

Guest Abducted

Oke, didn't want to gamble on trying the flashing root method, so i just rooted my device using the Bin4ry method.

However ROM toolbox for some reason cant set my governor to on demand anymore like i used to :( (like with the previous rom).

Could this be related to the new ROM?

Edited by Abducted
Link to comment
Share on other sites

Guest Abducted

Thanks i'll give it a try, but dont these tools all do the same thing in basicly the same way? ROM Toolbox did work for me before...

EDIT: Just installed System Tuner, but also noticed there was an update for ROM Toolbox which i installed. Figured i'd give ROM toolbox another try first, and of course... now it work :D

Weird stuff. Maybe it just needed a couple of reboots. Maybe it's the updated version. (didn't mention anything in the "what's new" section about something like this) Either way, it works. :) Me is happy again.

Edited by Abducted
Link to comment
Share on other sites

I have made cwm 6.0.1.4/5 and twrp 2.2.2.1 Touch with porting from other device but need help for fstab in etc kernel.

Problem on backup is boot.img and recovery.

Boot emmc /dev/boot not ok.... same for recovery. I have try other but never backup boot and recovery.

Is possible for this device mt6575 bakcup all?



/boot emmc /boot ----> 0 byte

/cache ext4 /dev/block/mmcblk0p2 ----> 14 Kb

/data ext4 /dev/block/mmcblk0p3 ----> 482 Mb

/misc emmc /dev/misc

/recovery emmc /recovery ----> 0 byte

/system ext4 /dev/block/mmcblk0p6 ----> 460 Mb

/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1

/sd-ext auto /dev/block/mmcblk1p2 ----> ??? auto or vfat or ext4???

This is link of my porting of twrp 2.2.2.1 touch recovery ----> copy this file into Images directory and use flash tool. Look guide Using SuperRecovery - step by step of Paul Here the link of this recovery mod. I have porting this recovery from other chinese device with mt6577 ----> V1277. This recovery is only for testing. Tomorrow upload recovery CWM 6.0.1.5 touch and no touch.
 

Your warranty is now void.

I am not responsible for bricked devices, dead SD cards,

thermonuclear war, or you getting fired because the alarm app failed

Edited by Guest
Link to comment
Share on other sites

Guest adamenko

Paul, I work in China and learn about "Acer Liquid Galant Duo" while being here. A bit more research - China's version is called AK330. Got one for myself and the problem I run into - I cannot install Google Play and add it to the list of my Android devices. Run into your topic, but cannot locate how to make a backup from my device. I do not need a brick in case I make a mistake - first time flashingexperiment for me.

Can you help me and give a link on your site to making ROM Dump (if it is the correct term) (backup) or link to the manual for Flash Tool? Spent 3 hours looking for those. no luck yet...

Thanks,

Mike

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.