yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] cha_indian:
I also bought this Flytouch 2 in November from aliexpress.com and i too have the same problem of boot process getting stuck at the green color screen that says "powered by wowpad"

I want to update the firmware to Froyo for Flash support. Can updating to Froyo solve the problem ??
[Android Software/Hacking General [Developers Only]] samiotis:
Thank you for our info
[Android Software/Hacking General [Developers Only]] isergio:
Hi Guys,

congratulations for the forum, this is my 1st topic.

I have a model tablet below:

WWE 10

Android 2.2 V1.8:#3656

Kernel 2.6.32.9

build FRF85B

Can I ask 2 questions about my problem?

- I can't to move app on sd1 card ( rooted, using Link2sd but; Mount script error invalid argument, i partitioned a card with fat32/ext2/linux swap)

Have you solution about it?

- if no, can I try to updatea tablet? which version I need/can install?

Thank you
[Android Software/Hacking General [Developers Only]] kiodo1981:
Froyo official? where you can download?
[Android Software/Hacking General [Developers Only]] merlot23:
Hello,

To get a SD-card working you can try to copy an .apk file to it from your PC and then put the SD in your tablet.

I do have the following problems:

Connection cable completely broke within 24 hours, grrrrrrrrrrrrrr.

Difficult to find the same plug in Spain.

But since the USB of the tablet is not available, can't get any power from that either. The files are on the tablet, included the dev debugging but "Connect to PC" is simply not in the settings menu.

I still have some oxigen left on the tablet and would be so happy if anyone can help me.

Helen.
[Android Software/Hacking General [Developers Only]] barrr:
Just follow the instructions on the first post and install Froyo.
[Android Software/Hacking General [Developers Only]] madman2182:
Just Ordered

i Just ordered the Fly touch 2 yesterday should get it in a few days Should i update to froyo right out of the box ?? does everything work right with it ??? Just not shure if i wanna brick my new toy right out of the box
[Android Software/Hacking General [Developers Only]] shentho:
I tried the Froyo upgrade and it froze

Thanks first for posting this thread and all your hard work.

I have a standard Flytouch II with 256MB memory.

I followed your instructions and was very excited to see the equalizer splash screen come up, then the word Android come up in the center, after 20 or so seconds, it froze and there was no further progress.

I will attach some files I think might be useful. I hope these files point to something

that will help you and us overcome this freezing.
[Android Software/Hacking General [Developers Only]] madman2182:
download link for the firmware is broken :(

is there a new place to get it ???
[Android Software/Hacking General [Developers Only]] Trig0r:
I grabbed mine from this thread..

http://xdaforums.com/showthread.php?t=1048776
[Android Software/Hacking General [Developers Only]] robert_tontoiu:
Superpad Problem

Hi ... new to this ... but reading a lot :)

I bought ( of course from china ) a superpad II flytouch 3 with Android 2.2 and 512mb RAM

Originally with Android 2.2 it worked only for 2 hours ... when I restarted I was stucked with ADROID _ and that's it .

Tried to talk with supplier ... no contact no response... start digging over internet ... did a lot of upgrades ... nothing worked.

Originaly my INFOTMIC said 0.6.1.5() with no version number.

I used burntool and putted 0.6.1.2 (587) or 0.6.1.5(587) any version ... I can still connect it to my computer but when I try to put a firmware on sd card it is stucked on Upgrading Linux .... and nothing happens.

Tried even iuw file ... but when I try this it is upgradind U0 and when extracting image it stays there ... doing nothing.

I opened the box and read everything from it ... seems like I have IMAPx210 ... only one micro sd port ( the other one is suspended ... not soldered but on the mainboard u can see the space for it )

The mainboard is WWE101-MAIN ver 3.4 the chip is TRXCOM TRC41604NL. Memory I guess ... some chip with 29LV800CTTI-70G if i read corectly.

Tried erase all data ... wipe ... but it cannot show the menu HOME + POWER nothing ... the only thing that works is connect to pc with MENU + POWER and restore factory with BACK + HOME + POWER but same .. .cannot find recovery info.

Can anybody help me restore something on my pad .... anything ... ANDROID 1.6 anything ... It was a gift for my child but when I arrived home it didn't started anymore ... or can I consider it a brick ...

Thanks a lot ! Appreciate any ideas ... anything ... paid 160 $ for 2 hour of use :)
[Android Software/Hacking General [Developers Only]] _barsuk_:
You tablet has some differences from Flytouch2. Try read there.
[Android Software/Hacking General [Developers Only]] openuser0101:
2.2 firmware

I just got an email from the suppier of my Superpad. he gave me a link for the Android 2.2 Firmware upgrade for an sd card upgrade. I am looking for instructions on how to sd upgrade. but here is the link

3w. filefactory.com/file/b572g6d/n/zt-update.rar

any help would be great.

I know it says zt-update but I do have the true Superpad with the infotex A11 1GH cpu with 2 sd card slots.

Thanks to anyone that can help me.
[Android Software/Hacking General [Developers Only]] molecular2:
Bricked Pad

Unfortunately I had a "Brain Failure" and burned the WRONG file whilst trying the update?????

I can't find any solution on the Forums but in the remote chance that someone can help I make this appeal for help.

Thanks:(:mad::confused::eek:
[Android Software/Hacking General [Developers Only]] sykopompos:
Hey stragulus, check your email when you get a chance. You should have a dropbox invite from me with a present in there that will make your builds work much better. Please don't share with anyone till I know what I can legally share and then I will post the source up on github and give you the go ahead to share.

Gonna have a lot of very happy people real soon
[Android Software/Hacking General [Developers Only]] Onedroidev:
Superpad iptables

Hello all,

I have a superpad and I should hack its kernel in order to add iptables support. I have read here that stragulus made a porting from froyo superpad II to superpad I.

I downloaded the packets suggested which are all binaries, but I found that stragulus mantains four repositories

github.com/stragulus in which some sources are availables. I am interested on the repository status.

Have someone of you informations related to that?

How does the 4 different repositories interact each other?

Thanks.
[Android Software/Hacking General [Developers Only]] alexander_sciv:
Long time trying to alter device Infotm X200, 1GHz ARM11, Operative memory RAM: DDR 256MB with Firmware Froyo 2.2 v2.1 #3925 the loader 0.6.1.5 (), having re-read all forums and having executed all recommendations Has come to steady result. Loading of any insertions, leads any way to device loading Only before inscription occurrence _ANDROID. It has occurred fastest at installation of insertion Superpad 3245 firmware, when The file zSYS.img has been rewritten. After that even reinsertion Froyo 2.2 v2.1 #3925 which was loaded a demon of problems, Too has ceased to work. The loader 0.6.1.5 () means devices initially stitched by insertion Firmware Froyo 2.2 v2.1 #3925 Cannot be stitched by older insertions and consequently on this device it is impossible to leave in the menu recovery (has tried Any variants at different u-boot-nand). Reacts only on: = NEW ÕÀÐÄÐÅÑÅÒ At THOSE WHERE is not present BOOT MENU It is necessary to clamp home on the centre and home from above and to press power as it will be cut it is wrung out power and there will be an inscription press the required keys if you wont to apply a factory reset. system will boot normally in 5 seconds further it is wrung out home the top And again it it is pressed, it is started õàðäðåñåò = but also ñäåñü at attempt of dump of options on factory,

I receive the message: In vaid file system, please check your zSYS.img. As a part of insertion Froyo 2.2 v2.1 #3925 it The file is not present. It turns out the file zSYS.img is necessary. For Froyo 2.2 v2.1 #3925. I ask experts me to correct and To prompt how to cure zSYS.img?
[Android Software/Hacking General [Developers Only]] Onedroidev:
I changed strategy

... In the meantime I changed strategy... I downloaded the Android-kernel (2.6.32.9) and I compiled the modules required for iptables support after having some errors related to repo and above all to the Mac support for elf format.

Then I rooted my device and I added a busybox

I activated the USB debug mode and I connected the device to adb using the 5555 port.

After this I pushed the modules on the filesystem, but when I try to use insmod I receive an error

Exec format error.

in my system

file ip_tables.ko: ELF 32-bit LSB relocatable, ARM, version 1, not stripped

and should be good. Arm11 is supposed supporting both BE than LE, I will try tomorrow with BE format... but I don't think the problem is related to the file format

Tomorrow I will download one of the 3 kernel object present into the board, just to check the format.

Maybe can be a problem in the magic number I will check it with dmesg.

Now It's time to stop

Some other suggestions?
[Android Software/Hacking General [Developers Only]] _barsuk_:
Look in dmesg. And try to change kernel build options for...
[Android Software/Hacking General [Developers Only]] Onedroidev:
Next step

The problem was on the magic number.

ip_tables: version magic '2.6.32.9-g049a746 ARMv5 ' should be '2.6.32.9 mod_unload ARMv6 '

From dmesg on the board I saw

- Kinux version 2.6.32.0 gcc version 4.4.0

- Changed toolchain to adapt this setting, selected

prebuilt/darwin-x86/toolchain/arm-eabi-4.4.0/bin

- CPU: ARMv6-compatible processor [4117b365] revision 5 (Acetti RMv6TEJ), cr=00c5387f

- Selected an ARMv6 family processor which fit that one ARM integrator v6 support

- Adapted the magic number.

Now if I try to load ip_tables.ko it is not loaded because symbols are missing as expected. When I try to load x_tables.ko which defines all the symbols used from ip_tables.ko superpad reboots ...

I am trying to understand why...

I downloaded the galcore.ko driver from the board

galcore.ko: ELF 32-bit LSB relocatable, ARM, version 1 (SYSV), not stripped

while the drivers that I am compiling ELF 32-bit LSB relocatable, ARM, version 1, not stripped

So no sysV. I am actually trying to change this, but I am not sure it will fix everything
[Android Software/Hacking General [Developers Only]] _barsuk_:
I was doing some research on this issue. Look for my modules in this thread.

I got working ntfs and nls_utf modules. But:

root@droidtest:~/droid# file cifs.ko
cifs.ko: ELF 32-bit LSB relocatable, ARM, version 1 (SYSV), not stripped

got kernel panic when it is used. Any call to functions related to memory allocation leads to it. I'm stuck on this one.

PS

Sample crashdump

<1>[ 6318.355000] Unable to handle kernel paging request at virtual address 00400004
<1>[ 6318.360000] pgd = c5ee0000
<1>[ 6318.365000] [00400004] *pgd=00000000
<0>[ 6318.370000] Internal error: Oops: 5 [#1]
<0>[ 6318.370000] last sysfs file: /sys/devices/virtual/timed_output/vibrator/enable
<4>[ 6318.370000] Modules linked in: cifs slow_work(P) rt2070sta permfd galcore
<4>[ 6318.370000] CPU: 0 Tainted: P (2.6.32.9 #1)
<4>[ 6318.370000] PC is at cifs_mount+0xb8/0x2268 [cifs]
<4>[ 6318.370000] LR is at kmem_cache_alloc+0x80/0x8c
<4>[ 6318.370000] pc : [<bf0a8f34>] lr : [<c00e72b8>] psr: 60000013
<4>[ 6318.370000] sp : c5f99e80 ip : 00000000 fp : cd92b000
<4>[ 6318.370000] r10: c8e3a000 r9 : cfc64d00 r8 : c8e3a000
<4>[ 6318.370000] r7 : 00000000 r6 : cc3b47f8 r5 : cc3b47e0 r4 : c8e3a000
<4>[ 6318.370000] r3 : 00400000 r2 : 000080d0 r1 : 0000000f r0 : cc3b47e0
<4>[ 6318.370000] Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user
<4>[ 6318.370000] Control: 00c5387d Table: 45ee0008 DAC: 00000015

Looks like some kernel build options is incorrect. But I don't find which exactly.
[Android Software/Hacking General [Developers Only]] Onedroidev:
found

In the meantime I found the problem, it was related to

CONFIG_AEABI=n

in the .config

now with

CONFIG_AEABI=y

the file format is correct.

I cannot test it now... I am leaving for a trip this weekend, anyway on monday I'll let you know the results. So we can compare them
[Android Software/Hacking General [Developers Only]] Onedroidev:
It seems to be a paging error maybe an issue in the memory model, did you try disabling MMU or changing memory model? just in case...

Or maybe they compiled a non SMP kernel, while your model is for a preemptive kernel or viceversa, or the preemption model is different.

It is very difficult to say.

This crash is in the module loading isn't it? Same for me, but I had the wrong file format today.

Did someone tried to create an hello_kernel_mod which just allocate memory and releases it?

Anyway I will test my module on monday and we will check results
[Android Software/Hacking General [Developers Only]] _barsuk_:
Yes. First of all. And many options have been tried.

Just for a tick. Preemption is disabled for these kernels.

I know. ;)

Crash does not happen at load. It happens when using mount.

I didn't. :)

Good luck with this. :)
[Android Software/Hacking General [Developers Only]] Onedroidev:
Crash does not happen at load. It happens when using mount.

Good luck with this. :)
[Android Software/Hacking General [Developers Only]] Onedroidev:
x_tables.ko

Above all my configuration seems to be worse than yours....

In my case the kernel_panic arise in

<1>[ 1715.175000] Unable to handle kernel NULL pointer dereference at virtual ad

dress 00000000

<1>[ 1715.180000] pgd = c9384000

<1>[ 1715.180000] [00000000] *pgd=477b3031, *pte=00000000, *ppte=00000000

<0>[ 1715.190000] Internal error: Oops: 17 [#1]

<0>[ 1715.190000] last sysfs file: /sys/devices/platform/battery.0/power_supply/battery/technology

<4>[ 1715.190000] Modules linked in: x_tables(+) rt2070sta permfd galcore

<4>[ 1715.190000] CPU: 0 Not tainted (2.6.32.9 #1)

<4>[ 1715.190000] PC is at sys_init_module+0x94/0x1e0

<4>[ 1715.190000] LR is at sys_init_module+0x98/0x1e0

So the kernel crashing while it is trying to load x_tables modules, it does not exit from the kernel function sys_init_module, so I guess there is still something wrong in the module format.

I also tried to dump the configuration from the image.

$ ./extract_uImage.sh kernel.img

$ ./scripts/extract-ikconfig ../../__test_environment/zImage > ../../__test_environment/orig_config

$ cat ../../__test_environment/orig_config

ERROR: Unable to extract kernel configuration information.

This kernel image may not have the config info.

I was unlucky here, there are not symbols stored in the kernel.

Still looking for a solution...
[Android Software/Hacking General [Developers Only]] Onedroidev:
Seems to be ok

OK!

Now the driver can be loaded :D.

And it seems that it can allocate memory.... I will give u results after more tests
[Android Software/Hacking General [Developers Only]] Jiggity Janx:
Best of luck with all of the above guys! It would be great if I could at least begin to use DroidWall...
[Android Software/Hacking General [Developers Only]] SamuelYan:
Thank u,man.This does help me a lot.
[Android Software/Hacking General [Developers Only]] Onedroidev:
ip_tables

x_tables.ko loaded

hello_superpad.ko loaded.

ip_tables.ko cannot be loaded because

netfilter support is missing.

There is no option to compile netfilter as a kernel module so I should patch the kernel in my opinion ... but I have seen in this forum that there are persons which load ip_tables.ko and netfilter.ko. It sounds new to me. I will ave a look to the .config again but I do not find a way to do that.

Everyday one step done :) and one step missing. :(
[Android Software/Hacking General [Developers Only]] _barsuk_:
Will you share your current kernel config?
[Android Software/Hacking General [Developers Only]] pichuerca:
How is current state the overclocking of the flytouch2?

Thanks

Javier
[Android Software/Hacking General [Developers Only]] Onedroidev:
Hi

Sure I can. Anyway it seems to be still broken, because the module loading causes a stack corruption (i am sure that it is true for x_tables.ko but I am going to test it with the hello_flytouch2.ko module).

After sending ifconfig a couple of times the kernel crashes

<0>[ 304.560000] Internal error: Oops - undefined instruction: 0 [#1]

<0>[ 304.560000] last sysfs file: /sys/devices/platform/battery.0/power_supply/

<4>[ 304.560000] Modules linked in: x_tables rt2070sta permfd galcore

<4>[ 304.560000] CPU: 0 Not tainted (2.6.32.9 #1)

<4>[ 304.560000] PC is at 0xc0605ed4

<4>[ 304.560000] LR is at dev_ioctl+0xb4/0x750

<4>[ 304.560000] pc : [<c0605ed4>] lr : [<c02e2260>] psr: 20000013

<4>[ 304.560000] sp : c8d99ea8 ip : 00000018 fp : c0605ecc

<4>[ 304.560000] r10: c0605ca0 r9 : 00000140 r8 : 00000000

<4>[ 304.560000] r7 : 00017550 r6 : c8023800 r5 : 37fdc800 r4 : be8b5b84

As you can see here there should be an instruction which is not present in the location required so it should be the result of a stack corruption.

Sending ifconfig ra0 you will need to run more times the command before the kernel panic but sooner or later it will arise.
[Android Software/Hacking General [Developers Only]] Onedroidev:
Tested with hello_flytouch2

I tested with a simple module which just allocate memory using kmalloc and release it using kfree and the system is stable, no crashes experienced.

The crashes arises only when x_tables.ko is loaded. It looks like this module is actually changing something in the kernel network stack, so you can try the configuration. It should be good for your module.

Let me know results.

In the mean time I continue with my investigation. :confused:
[Android Software/Hacking General [Developers Only]] _barsuk_:
Hmmm. Looks like bug into rt2070sta and not into x_tables isn't it?

Which exactly kernel you use for testing? Tested this with no custom modules?
[Android Software/Hacking General [Developers Only]] Onedroidev:
This is the situation

It seems that the x_tables.ko corrupts the network stack and when rt2070 try to access to a memory area it is corrupted... but I am still investigating. As I wrote before, the hello_superpad.ko does not cause this problem, but maybe is only too short to do that... :rolleyes:

I am using the last release 2.6.32 in the android kernel source chain (which is 2.6.32.9 anyway).

I am arranging a test using a script, because it will need more time to crash if it will.... I'll give u results later.
[Android Software/Hacking General [Developers Only]] _barsuk_:
Maybe you right but stock rt2070sta very unstable itself. This usually does not result to crash the kernel. But OS is periodically reload this module itself.

You didn't understand me. I'm not asking about the sources. I'm asked from which firmware kernel were taken for testing.
[Android Software/Hacking General [Developers Only]] Onedroidev:
Test results

test results (running for 10 minutes each)

-no custom modules. No kernel panic

-hello_superpad.ko. No kernel panic

-hello_superpad.ko netfilter.ko No kernel panic

-x_tables.ko Kernel panic.

All test were made sending busybox ifconfig every second.

Same problem using busybox cat /proc/net/dev

Different result running cat /proc/net/dev or ifconfig ra0 (Not using busybox....) It takes longer to crash.

The last test shows that maybe it's a memory corruption but not related to the ethernet stack (same command different result). It seems to crash by a command sent after a timeout instead of after a command (a periodic scheduler should create it).

Maybe I am not still understanding. Anyway

The build on the superpad is deb-r.2.1.1561

I am using the wowpad version (not the froyo porting)

the android present on the board is 2.1

The kernel that I am compiling comes from http://android.git.kernel.org/

I put <project path="kernel/common" name="kernel/common" revision="android-2.6.32"/> in the .repo of the android building system

I do not know if I answered :confused: quote me if you need more informations.
[Android Software/Hacking General [Developers Only]] _barsuk_:
Maybe I'm wrong but with

busybox ls -la /dev | busybox grep mem

we get ashmem. My kernel from firmware 3925 (froyo).

CONFIG_SHMEM=y
# CONFIG_ASHMEM is not set

That is answer. :) And sorry for my bad english. :(

PS

Read this.

# CONFIG_OABI_COMPAT is not set

is wrong?
[Android Software/Hacking General [Developers Only]] Onedroidev:
Continuing the job

That is what I have

crw-rw-rw- 1 0 0 10, 62 May 17 13:20 ashmem
crw------- 1 0 0 1, 2 May 17 13:20 kmem
crw------- 1 0 0 1, 1 May 17 13:20 mem
crw-rw-rw- 1 1000 1000 111, 111 May 17 13:20 memalloc

and you are right regarding to the memory model. But there is not

ashmem_create_region

call inside the module I built so changing it will not cancel the crash I am experiencing, anyway thanks, we have a better .config file now

The problem is not your english, because it is very good, the problem is that on Android world everything is called firmware or kernel and sometimes I do not understand because I am coming from the linux world where kernel, firmware and distribution should very different, maybe I am still confused. Sorry I am new in this world......

What was changed on that distribution? Are linux kernel and board firmware the same that I am actually using? Does It worth to change my actual fw/distro?

I am still trying to understand what's going on my board.... very hard job.
[Android Software/Hacking General [Developers Only]] Onedroidev:
Oabi_compat

Same story of EABI_COMPAT.... they are both compatibility wrappers and they should not be longer useful

I do not think that the original kernel was compiled with this option because it increase its size. Anyway I am looking to the memory model. I hope I will answer soon to this question.

/*
* The legacy ABI and the new ARM EABI have different rules making some
* syscalls incompatible especially with structure arguments.
* Most notably, Eabi says 64-bit members should be 64-bit aligned instead of
* simply word aligned. EABI also pads structures to the size of the largest
* member it contains instead of the invariant 32-bit.
*
* The following syscalls are affected:
*
* sys_stat64:
* sys_lstat64:
* sys_fstat64:
* sys_fstatat64:
*
* struct stat64 has different sizes and some members are shifted
* Compatibility wrappers are needed for them and provided below.
*
* sys_fcntl64:
*
* struct flock64 has different sizes and some members are shifted
* A compatibility wrapper is needed and provided below.
*
* sys_statfs64:
* sys_fstatfs64:
*
* struct statfs64 has extra padding with EABI growing its size from
* 84 to 88. This struct is now __attribute__((packed,aligned(4)))
* with a small assembly wrapper to force the sz argument to 84 if it is 88
* to avoid copying the extra padding over user space unexpecting it.
*
* sys_newuname:
*
* struct new_utsname has no padding with EABI. No problem there.
*
* sys_epoll_ctl:
* sys_epoll_wait:
*
* struct epoll_event has its second member shifted also affecting the
* structure size. Compatibility wrappers are needed and provided below.
*
* sys_ipc:
* sys_semop:
* sys_semtimedop:
*
* struct sembuf loses its padding with EABI. Since arrays of them are
* used they have to be copyed to remove the padding. Compatibility wrappers
* provided below.
*
* sys_bind:
* sys_connect:
* sys_sendmsg:
* sys_sendto:
* sys_socketcall:
*
* struct sockaddr_un loses its padding with EABI. Since the size of the
* structure is used as a validation test in unix_mkname(), we need to
* change the length argument to 110 whenever it is 112. Compatibility
* wrappers provided below.
*/

So it should be useful is somewhere the old ABI syscall are used instead of the new EABI.... The header is dated 2005 so I do not expect someone is still using that format. :O Maybe I am wrong in this