yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] soyasensei:
I am not more experienced than you :p I am trying to understand all this stuff by myself and doing some search online.

Some tweaks are included into Pimp My Rom app. I am using App Backup in order to save all my apk so that I can reset my tablet and test optimizations.

I did a full copy of the mmcblk0 & mmcblk0 partitions and they are saved as img files (4GB images) using this command in adb shell :

I did cat /proc/partitions so that I could see the partition map :

I don't know what are those smaller partitions acta / actb / actc / actd / acte / actk

I used dd command in order to copy the whole partitions. You will need a big enough microsd card min 4GB (I'm using a 8GB card).

I am trying to find those boot.img, build recovery.img so I am still searching online. Seems like this tablet doesn't use MTD so it makes it much more difficult..along with the MIPS architecture.

I still have to extract a stock .FW ROM so that I could understand more how it works.

UPDATE :

Seems like acta is the recovery.img and actb boot.img

Could you dd your partitions ? I have sent an email to Ananda and hopefully they are going to send me this 4.0.4 rom.
[Android Q&A, Help & Troubleshooting] releaser:
Hi again soyasensei

here's my partition map, it's way different from yours

C:\SRSRoot>adb devices

List of devices attached

Actions Semi. 0C0ACA15 device

C:\SRSRoot>adb shell

shell@android:/ $ cat /proc/partitions

cat /proc/partitions

major minor #blocks name

7 0 12506 loop0
7 1 2111 loop1
7 2 5229 loop2
7 3 2111 loop3
93 0 65536 acta
93 8 327680 actb
93 16 70656 actc
93 24 1024000 actd
93 32 65536 acte
93 80 2444288 actk
179 0 995328 mmcblk0
179 1 995203 mmcblk0p1
254 0 12505 dm-0
254 1 2110 dm-1
254 2 5229 dm-2
254 3 2110 dm-3

I can't make romdump with ADB because it's saying romdump isn't executable i'm getting error magic 7F45

I've been reading about romdump and the newer version needs some kind of exploit to run, have you tried v72 to see if that one works?

1|shell@android:/ # romdump
romdump
sh: /system/bin/romdump: not executable: magic 7F45

I can't make the dump of mmcblk fles because i don't have an sdcard with enough space (the only one available is 1GB)

Best regards
[Android Q&A, Help & Troubleshooting] soyasensei:
Yes, I have tried older versions of romdump, same error. This is the reason why I am trying to dump the rom manually by trying to find it. Should be acta for recovery and actb for boot img files. They are both vfat images so if I manage to mount them and extract the img files we should be able to adapt some tools.
[Android Q&A, Help & Troubleshooting] releaser:
Did Pimp My Rom take a lot to run on your device?

I made it to the changelog and when selected ok the app just stays there with a black screen, nothing happens.
[Android Q&A, Help & Troubleshooting] soyasensei:
Good news I have managed to access my img files on my computer. mmcblk0 seems to be only the sd-ext at least on my tablet (it is confirmed by the fact that your cat shows 1gb size)

acta contains the following files :

Looks like we are on the right path.. :good:

I am using Pimp My Rom (beta version). Disabled all animations in Android settings. Using Nova launcher, disabled all other desktops etc..

Could you try making a backup of all your actX / loop-x / dim-x using dd if=/dev/block/FILE of=/sd-ext/FILE.img ? You should have enough space on your usd card. After that you can try and mount them using ImDisk for example (Windows). Some partitions are not mountable using that tool because of ext filesystem I guess. We might finally find all the important img.
[Android Q&A, Help & Troubleshooting] releaser:
So if that's true, if we remove the sd-ext that partition will not be listed,or at least it will be listedwith 0 value.

My device i so slow i feel like i'm gonna throw it against the wall :confused:
[Android Q&A, Help & Troubleshooting] soyasensei:
I think so because after I mounted the mmcblk0.img, it showed exactly the same content as on the uSD that was inside of my tablet. So basically what I did was to make a backup of the uSD and saving it in that same uSD :silly: Another actX.img got the content of /sdcard or internal storage. I will list them all. I still have to mount those mysterious ext4 img actX files but so far acta.img seems to be one of the 2 boot/recovery.img files we need.

Read my previous post, I have written some instructions so that you can help me find out what is inside the actX.img files.

Thank you
[Android Q&A, Help & Troubleshooting] releaser:
Well, i removed ext-sd and no mmcblk partitions are listed, those blocks are the sd-ext. None of the mmcblock show so both mmcblk mount points are for ext-sd.

Please tell me what you want me to do, i can't help you using my device but i can try to help you with some other stuff you need. Put whenever files you need me to work on on a dropbox account or anywhere else and point me to them

---------- Post added at 05:45 PM ---------- Previous post was at 05:26 PM ----------

i found this Actions Tablet Product Tool, i don't know if that's useful...

Here's a link to my public dropbox folder

https://dl.dropboxusercontent.com/u...t Product Tool 1.02_02(Developer Edition).rar

Where can i find those files?

Just show me how to do it and i'll do it for you

Cheers

UPDATE: I found out how to backup those actX loopX and dmX, i'm doing it now ;)
[Android Q&A, Help & Troubleshooting] soyasensei:
Yeah I already have that one but no use for now. I am trying to unpack a FW file so that I could look at the internal structure. Hopefully we will be able to make custom roms.
[Android Q&A, Help & Troubleshooting] releaser:
I'm doing the last backup of actk which has 2GB, for now this is the only one left to backup. Next i will try and mount them to see what we got.

That would be great, by the way i made the changes you suggest about the animations and installed NOva Laucher and tablet is more responsive ;)

---------- Post added at 07:53 PM ---------- Previous post was at 07:36 PM ----------

Well, i don't know why but i can't mount any of the images with daemon tools, you think is has something to do with windows or with daemon tools?

Can't mount images with ImDisk also, not a valid filesystem
[Android Q&A, Help & Troubleshooting] soyasensei:
Use ImDisk for Windows you can easily mount them. The ones that are not mountable are the ext4 ones. Will have to find an ext4 tool.
[Android Q&A, Help & Troubleshooting] releaser:
Tried to mount all those act* files, including acta.img and i always get the "not a valid filesystem" message. Have i done everything wrong?

Do you want me to put my files acessible so you can try mount them?
[Android Q&A, Help & Troubleshooting] soyasensei:
Used the following options : Virtual disk drive + Removable media

You might want to post stock rom dumps since some of the actX img might contain personal files.

My tablet is in bootloop tried some tweaks that did not do well. Reflashing the tablet :(
[Android Q&A, Help & Troubleshooting] releaser:
That's bad...

What firmware will you use to reflash?

Maybe i try and reflashing mine with same you did to see if my tablet works better
[Android Q&A, Help & Troubleshooting] soyasensei:
It's restoring using this FW file : http://www.4shared.com/rar/bQSoZDvP/7013.html

For some reason it did not recognize CEMA10S24 & Q8 FW files..

Ok touchscreen doesn't work on this one.. WIll try another rom..
[Android Q&A, Help & Troubleshooting] releaser:
That's strange... never ear of no one complaining about those FW files

:p
[Android Q&A, Help & Troubleshooting] chodir:
brick atm7013 gs701b

hi, i have problem with my device ATM7013 GS701B with home button after flashing with CEMA10S24 Tablet product tool build 1.02. I can't go to RECOVERY anymore because my vol button doesn't work (when i push vol+ button it's going menu button, when i push vol- it's home button), my sdcard can't detected, touchscreen doesn't work and when i'm in landscape mode the tablet going to potraid mode and other side. any one can help me?pls. thanks and sorry for my bad english
[Android Q&A, Help & Troubleshooting] releaser:
Hi soyasensei

How did your restore went? All good?

I'm stuck with image mounting, can't mount any of the backup images, which tells me that be a problem with them, surely they aren't all ext4 so it must be something else.

Any news from Ananda and 4.0.4 firmware?

Best regards
[Android Q&A, Help & Troubleshooting] soyasensei:
After I flashed CEMA10S24 in ADFU mode using Actions Tools my touchscreen still didn't work.. The worse thing is that I have no longer access to Recovery mode and now the screen doesn't even turn on. I found a way to run ADFU just by plugging in the tablet via usb & holding Volume + but the problem is that it won't finish downloading the firmware to the tablet. Some firmwares download until 12%, others to 37% max.. Hopefully I will find a way to get back to the old recovery menu..
[Android Q&A, Help & Troubleshooting] releaser:
Sorry to ear that.

So you're telling me none of the firmwares available are suited for our tablets?!

Most of the problems regarding flashing were about flashing gs701b with home button with firmware for the version without home button, and those touch screen problems seemed normal, now I just don't know what to think. Now we are

even more needed of a backup of my ROM, I hope I can help with that.

Best regards
[Android Q&A, Help & Troubleshooting] soyasensei:
Seems like this has to do with specific display driver because I've tried all the firmwares for my tablet and none of them accepted touch input.. My tablet is a Polaroid MIDR477PR002 running ATM7013. I still have the dump with the tablet drivers but since I can't unbrick it I can't do anything. Actions Tablet tools & Media tools are both the same. The later provides more settings but even if they both show "successful" after the flash, the tablet doesn't turn on. It is stuck in ADFU mode and doesn't seem to turn off.
[Android Q&A, Help & Troubleshooting] releaser:
In that matter I don't even know the brand of mine, I can't see any brand at all.

How do I know which one is it?

Did you try to flash using SDCARD before using ADFU?

Cheers
[Android Q&A, Help & Troubleshooting] soyasensei:
Check at the back of your tablet, there should be some indications. Yes I tried with the uSD first with all the roms. The CEMA10S4 put my tablet into bootloop and ultimately into a brick.. No recovery mode was available.. After I tried to flash the rom using action tools the screen turned off. When flashing the screen turns on with a purple line and then turns off but can't turn the tablet on, it's stuck in adfu mode..
[Android Q&A, Help & Troubleshooting] releaser:
That means you now have a tablet which you can't do very much about. Unless you find the correct firmware.

I want to help you in any way I can, so please just tell me what can I do.

Best regards
[Android Q&A, Help & Troubleshooting] soyasensei:
The problem is that whatever firmware I use other than CEMA10S24, the Actions Tool doesn't seem to accept them. There is no version number on the other ROMs so it considers them as invalid. The only solution might be to unpack one of the other roms and try to add some fake version number but I'm not sure I could actually do this. If I could find a way to force the tool to flash without checking the version it might work. I might also explore linux for unbricking this tablet.

---------- Post added at 10:58 PM ---------- Previous post was at 10:05 PM ----------

Although I can't access to the tablet anymore, I managed to access the different img files using this tool : http://www.diskinternals.com/download/Linux_Reader.exe (Drives > mount > select the img file)

I believe that if you plug in a mouse using a mini-usb to usb female adapter, you could activate the developer mode and then inject the display driver using adb (root mode required of course).

The bad news is that apparently .fw files are encrypted. I saw that there were some Actions tool versions that allowed the user to flash separate img files for boot, recovery etc.. Interestingly enough, the ATM7029 do have separate recovery.img files which means I might be able to flash my tablet using my own img dumps (!)

This is what I got after mounting my img dump files :

acta.img > [FAT16] /RECOVERY 64MB

actb.img > [EXT] /SYSTEM 255MB

actc.img > [FAT32] /NO NAME 257MB

contains stock APK files

actd.img > [EXT] /DATA 1000MB

acte.img > [EXT] /CACHE 64MB

actk.img > [FAT32] /SDCARD 2190MB

this one is the internal SDCARD

mmcblk0 is the sd-ext and

mmcblk0p1

is just the only partition and is part of mmcblk0
[Android Q&A, Help & Troubleshooting] soyasensei:
Ok, that's so weird.. Tried to power it on and it DID ! :eek: I don't know why.. I'm still stuck with a non working touchscreen but I am planning to buy that usb adapter.. :good: I need to have access to ADB by activating the developer mode and then either connect to the wifi and use ADB CONNECT or else use standard USB ADB. Once it's connected I can try activate the touchscreen and eventually fix this nonexistent recovery mode.. I can still use brynthomas method here : http://xdaforums.com/showthread.php?t=1979248&page=4
[Android Q&A, Help & Troubleshooting] chodir:
brick gs701b after flash cema10s24

hi soyasei,

your device trouble same as mine. my vol button and touchscreen did't work, when i push vol+ => menu button, vol- => home button but it fixed and back to normal with editing atc260x_keylayout.kl , but i still have trouble with my touchscreen, i remember the touchscreen driver is gslx680.ko do you know how to install this kernel module.? thanks.
[Android Q&A, Help & Troubleshooting] soyasensei:
Hi chodir, how did you manage to modify this file and inject it into the tablet ? Without the touchscreen I can't activate debugging mode so no adb.. I have all my original drivers thanks to the dumps I have made before so I can still fix my touchscreen. The other issue is that my tablet can't be turned off it keeps turning on by itself.
[Android Q&A, Help & Troubleshooting] chodir:
hi soyasensei

i'am using usb keyboard, so i can go to menu setting and active usb debugging. after that i try rooting the tablet in command prompt

- usb shell

- su

- actions123

- mount -o remount,rw / ------->not { mount -o remount,rw /system ---> error invalid argument}

- mv /system/bin/su /system/bin/oldu

and then i'm using srsroot mips for completely root and reset userlock / gesture lock.

afther that for fix vol button back using adb in command prompt

- adb shell pull /system/usr/keylayout/atc260x_keypad.kl c:\adckeypad.kl

- exit

edit with notepad, just change key code home to be vol+ and back -> vol-

adb shell push c:\adckeypad.kl /system/usr/keylayout/atc260x_adckeypad.kl

done.

sorry for my bad english
[Android Q&A, Help & Troubleshooting] soyasensei:
Good to know ! I am waiting for my USB OTG cable to fix this. Thank you. Did you have this boot loop issue ? I can't seem to turn off the tablet. It keeps turning on by itself.
[Android Q&A, Help & Troubleshooting] chodir:
type adb reboot --> the tablet will be power off.

i don't know why, it must be restarting but it make shutdown.
[Android Q&A, Help & Troubleshooting] soyasensei:
Since I have my original ROM dumps. I'm gonna be able to replace the wrong files. I'm glad I did that prior having this issue !
[Android Q&A, Help & Troubleshooting] chodir:
a waiting fixed device from you. thanks
[Android Q&A, Help & Troubleshooting] soyasensei:
If you want I can send you that driver so that you could test.

Those are the .ko files I found in system/usr/lib/modules :
[Android Q&A, Help & Troubleshooting] chodir:
thank you and i'm waiting for the link. i'll try the best i can do.
[Android Q&A, Help & Troubleshooting] soyasensei:
I have uploaded all the *.ko modules. Hope it helps. Go ahead while I am waiting to receive my OTG USB cable ;)

https://www.dropbox.com/s/b8amxohzwwi1046/ATM7013-modules.rar
[Android Q&A, Help & Troubleshooting] chodir:
thanks and i'll try. hope it can
[Android Q&A, Help & Troubleshooting] chodir:
hi soyasensei,

can you upload yours recovery image (acta.img), i would try it to ?. thanks
[Android Q&A, Help & Troubleshooting] soyasensei:
Here you go : https://www.dropbox.com/s/h7kesf7utlevpoc/ATM7013-acta.rar

If you want the compressed img acta file : https://www.dropbox.com/s/sfplvzeczoeca58/ATM7013-acta-img.rar
[Android Q&A, Help & Troubleshooting] releaser:
Welcome chodir

Nice to see someone else is trying to help you in the best possible away soyasensei.

I was able to mount my dumps with that driver_linux software you point me to.

Anything i can do to help you guys, just say.

It seems I'm the only one with a fully working tablet so I would be much happy to help you guys.
[Android Q&A, Help & Troubleshooting] soyasensei:
Check your private messages. I should get my OTG usb cable tomorrow so that I could adb into it.
[Android Q&A, Help & Troubleshooting] releaser:
I have what you asked already done and saved on my hard drive, I'll make it available when I get home soyasensei.

Best regards
[Android Q&A, Help & Troubleshooting] themrlsk:
Hi everybody !

I've a bootloop on android logo, i would like to flash the official firmware, i don't have the root, i can only access to the "recovery pink screen" (i don't remember the name)

Somebody can post a link to the firmware which can be flash ?

Thanks !!
[Android Q&A, Help & Troubleshooting] soyasensei:
Are you running on stock rom ? Try letting it run until it's out of battery.
[Android Q&A, Help & Troubleshooting] themrlsk:
Yes stock rom, it's the trick i use to stop the tablet, i launch and again ... and i wait for out of battery .. :(
[Android Q&A, Help & Troubleshooting] soyasensei:
Ok guys, I have received my OTG USB adapter. Mouse is not working but keyboard did work. I've managed to access USB debugging and now trying adb. Let's start the fun !
[Android Q&A, Help & Troubleshooting] releaser:
Great soyasensei, keep us posted on your results.

Just my two cents, my tablet came with that USB adapter included :P
[Android Q&A, Help & Troubleshooting] soyasensei:
Ok I found something interesting inside of the /system/usr/idc folder. The idc folder of my tablet lacks one calibration file (ssd2532_ts.idc) which I believe is needed in order for our touchscreens to work. I believe that you could change the actual idc file in order to make it work.

Here is the content of /system/usr/idc/ folder :

Here is the content of that missing ssd2532_ts.idc file taken from my actb.img dump :

I'm still trying to compare the dump with my actual system. Could you confirm me that your tablets lack that file ? Could you upload it or paste their content ?
[Android Q&A, Help & Troubleshooting] releaser:
I'll take care of all those requests when I get home soyasensei.

Regards
[Android Q&A, Help & Troubleshooting] soyasensei:
In /system/lib/modules, ssd2532-tp.ko and uor6x5x_ts.ko are missing.

I was thinking about renaming them along with the idc files so that it would trick android to load them instead. I don't know what uor6x5x_ts.ko does but the ts extension seems to point out to TouchScreen. Just a guess.

adb reboot recovery doesn't work since it is turning of the tablet so it won't boot to recovery. That's another problem.. Priority is the touchscreen for now.

---------- Post added at 04:53 PM ---------- Previous post was at 04:39 PM ----------

I'm gonna try and load those modules (ssd2532-tp.ko & uor6x5x_ts.ko)and then create a script in order to load them on startup.

We can do that by adding the insmod command in the init.rc file at the root of the android system.

Of course, ssd2532 idc file has to be present inside /system/usr/idc folder.

For the reboot loop, we can just assign reboot command to shutdown for now this can do the trick.

The only problem I see with this is that recovery is still not accessible.. If I manage to find out how to fix this, it will be possible for you to upgrade to Android 4.0.4 (ovo lite rom) and then install the touchscreen modules after that using USB OTG cable and loading the modules & idc file at least for releaser & my tablet models since we have the dumps and consequently the modules+idc in our possession.
[Android Q&A, Help & Troubleshooting] releaser:
Maybe I have those missing files in my dumps and I can provide them to you.

All this problems are leading us forward in understanding our firmware's and getting us closer to a custom rom.

I don't know if this has something to do about it but after seeing all the problems I have with my tablet I think this is probably firmware related.

Just some considerations:

Don't know about you guys but my CPU is rated at 920mhz Max speed and 700 min speed, I think this CPU is build to run at 720mhz which means mine is overclocked, can that mean my battery problems (it lasts about 6 hours idle), my freeze problems and memory use (most of the time I'm stuck with about 75% used memory even with no apps running) may be due to that overclocked CPU?

These are some of the questions I made to myself while using my tablet and I would appreciate your opinion about them.

Thanks in advance
[Android Q&A, Help & Troubleshooting] chodir:
cema10s24 firmware

hai soyasensei

i guess after flashing cema10s24 firmware there's no touchscreen driver (kernel module) has been installed.

- mount -t sysfs /dev/block/actc /mnt/obb

- ls /mnt/obb/

- cd /mnt/obb/module

- ls

i guess we have to install one. i have tried inject your acta img but still not working

- mount -o remount,rw /

- cp -f /sdcard/acta.img /dev/block/acta

- mount -t vfat /dev/block/acta /mnt/obb

- ls /mnt/obb {like your original acta file}

- reboot -p

any idea?

sorry for my bad english and hi releaser.

do you have gslx680.ko in you device, /system/lib/module cause my device using it.

thanks.
[Android Q&A, Help & Troubleshooting] soyasensei:
I don't have that ko. You might ask releaser, maybe his dump has this kernel module. I am having a vermagic issue when trying to load my ko. Insmod -f doesn't seem to work. I will have to modify them with an hex editor.
[Android Q&A, Help & Troubleshooting] releaser:
Hi chodir and soyasensei

Well i hope this means good news for both of you

Contents of /system/usr/idc

atc260x-tp.idc
ft5x06-touch.idc
[B]gslX680-touch.idc[/B]
gt801-tp.idc
PixcirTouch.idc
qwerty.idc
qwerty2.idc
[B]ssd2532_ts.idc[/B]
Truly_tp.idc
UOR-touch.idc

Contents of /system/lib/modules

2g_uart.ko
8188eu.ko
8192cu.ko
ansi_cprng.ko
aotg_hcd_3g.ko
aotg_init1_3g.ko
aotg_init_3g.ko
aotg_udc.ko
asix.ko
atc260x_adckeypad.ko
atc260x_audio.ko
atc260x_tp.ko
atv5201_cpufreq.ko
atv5201_matrixkey.ko
atv5201_mmc.ko
atv5201_tvout.ko
cdc-acm.ko
dm9601.ko
focal-tp.ko
gadget_console.ko
galcore.ko
gc0308.ko
gc0309.ko
gc0329.ko
gl5201_camera.ko
gslX680-tp-old_ic.ko
gslX680-tp.ko
gt2005.ko
g_android.ko
g_ether.ko
g_serial.ko
g_stub.ko
g_switch.ko
hdmi.ko
install_image.sh
ip6table_filter.ko
ip6table_mangle.ko
ip6table_raw.ko
ip6t_ah.ko
ip6t_eui64.ko
ip6t_frag.ko
ip6t_hbh.ko
ip6t_ipv6header.ko
ip6t_LOG.ko
ip6t_mh.ko
ip6t_REJECT.ko
ip6t_rt.ko
ip6_queue.ko
ip6_tables.ko
mii.ko
mmc_block.ko
mmc_core.ko
nf_conntrack_ipv6.ko
oprofile.ko
option.ko
ov2659.ko
ov5640.ko
pixcir-tp.ko
print.txt
remotefs_inode.ko
scsi_wait_scan.ko
sit.ko
sndrv.ko
[B]ssd2532-tp.ko[/B]
truly-tp.ko
umonitor.ko
[B]uor6x5x_ts.ko[/B]
usb-libusual.ko
usb-storage.ko
usbcore.ko
usbhid.ko
usbnet.ko
usbrect.ko
usbserial.ko
usb_wwan.ko
virtual.ko
vpx_drv.ko
wifipreload.ko
xfrm6_mode_beet.ko
xfrm6_mode_transport.ko
xfrm6_mode_tunnel.ko
xt_hashlimit.ko

Here's the link to my public DB folder, enjoy!!!

https://www.dropbox.com/sh/mzdyo0gmmwl9mol/EXYRnMu95o

Regards
[Android Q&A, Help & Troubleshooting] chodir:
hi releaser,

thanks for sharing your files but i can't find

-gslx680-touch.idc

-gslx680-tp.ko

-gslx680-old-ic.ko

in you dropbox, would you upload that file again ?. thanks