Related
This is only for use on the X10 Mini Pro.
Credits go to nobodyAtall & D4rKn3sSyS for the actual CWM files. Other credits in the README.txt file.
Both version currently use CWM v3.x r5
Windows
Requirements:
Windows PC
USB Cable
Phone driver installed
Android Version 2.1 Stock ROM (2.1.1.A.0.6) (May work on Froyo and Gingerbread ROM's but any custom ROM should have a recovery already installed)
Usage:
You need to set your phone in Debugging Mode.
Connect your phone to your computer
Open up install.bat and follow the instructions inside that.
CWM Usage:
When booting your phone and when the 'Sony Ericsson' letters appear, press and release continuously the 'back' button.
Once you are in the CWM recovery, use the volume keys to navigate upwards / downwards, the 'home' or camera button key to select, the 'back' key to go back.
Last Update:
21-03-2012 v5
Updated Superuser apk and su to version 3.0.7
Replaced SuperOneClick with alternative method
Prefixed relative paths with %~dp0 to complete full paths. This is to combat over zealous group policies. Thanks go to satanselbow
Linux
Requires your phone to be ROOTed but there is now a ROOTer for Linux that can ROOT your phone if not already done. Can be found in this forum.
Requirements:
*nix PC/Laptop
USB Cable
Android Version 2.1 Stock ROM (2.1.1.A.0.6) (May work on Froyo and Gingerbread ROM's but any custom ROM should have a recovery already installed)
Usage:
You need to set your phone in Debugging Mode
Connect your phone to your computer
Open up terminal
Go to the directory it is extracted to
Start the installer by typing "sh cwm-x10minipro.sh"
CWM Usage:
When booting your phone and when the 'Sony Ericsson' letters appear, press and release continuously the 'back' button.
Once you are in the CWM recovery, use the volume keys to navigate upwards / downwards, the 'home' or camera button key to select, the 'back' key to go back.
Last Update:
23-Sept-2011 (v4)
Fixed question about USB Debugging
Fixed permissions on ADB
Links:
Original X10 Mini CWM Thread: http://forum.xda-developers.com/showthread.php?t=1105745
Original X10 Mini Pro CWM Thread: http://forum.xda-developers.com/showthread.php?t=1106146
Changes:
The changes for the latest version are included in the relevant sections above. A more detailed list of changes across all versions is in the CHANGES.txt file that is in the archive file.
Download:
Windows: Download
Linux: Download
Please do not re-host or re-release without permission.
Don't forget if you found this helpful please push the "Thanks" button
copy failed read only file system
is this basically a batch file?
because if so i could port it to linux for you
mopgawka - Did you get the correct mtdblock number. The file would set the system dir as r/w to enable you. The mtdblock number is the number directly after the text mtdblock, in the image below it is 0.
Another question was there an error after the "Getting ROOT rights" text? This was the bit that caused me the most issues.
x10man - Yes it is just basically a batch file. If you want to port to linux then go ahead
ClockWorkMod Recovery Installer for X10 Mini Pro by rect2409.
Requirements and credits are listed in the README.txt file.
Please make sure requirements are met before continuing.
...
..
Для продолжения нажмите любую клавишу . . .
Starting ADB Server if not started.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Getting ROOT rights.
rootsh: permission denied
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Enter the mtdblock number listed "/dev/block/mtdblock? on /system"
Enter mtdblock number: 0
Mount system as R/W.
mount: Operation not permitted
Do you already have a recovery installed? (Y/N):n
Pushing recovery tar file.
failed to copy 'recovery\recovery.tar' to '/system/bin/recovery.tar': Read-only
file system
Pushing chargemon.
failed to copy 'recovery\chargemon' to '/system/bin/chargemon': Read-only file s
ystem
Setting permissions for recovery tar file.
Unable to chmod /system/bin/recovery.tar: Read-only file system
Setting permissions for chargemon.
Unable to chmod /system/bin/chargemon: Read-only file system
Stopping ADB Server.
* server not running *
..
i always rooted
Ok, Currently working on a new version which hopefully fixes your issues.
Thanks I will dl it and take a look later and post the result here
Sent from my U20i using XDA App
how did you root your phone? I also don't have a script called "rootsh". also you can check if you are rooted with "id". many ppl like me are just rooted after entering the shell
also it's better to use "su" when calling commands that have to be done by root: "su - -c 'mount xyz' "
also don't forget the "*" if you check for keyboard inputs (there are people that may miss the key they wanted to push .D)
good luck.
Finnaly! Thank you! Would love to see cwm being imported in the slades kernel, that way we never have to deal with broken files!
Snoopo said:
how did you root your phone? I also don't have a script called "rootsh". also you can check if you are rooted with "id". many ppl like me are just rooted after entering the shell
also it's better to use "su" when calling commands that have to be done by root: "su - -c 'mount xyz' "
also don't forget the "*" if you check for keyboard inputs (there are people that may miss the key they wanted to push .D)
good luck.
Click to expand...
Click to collapse
Yeah I just noticed that i left rootsh in there. Was just something I was playing with.
One thing I hate is Permission Denied error's with adb... Oh fun.
damn. i just did the port and managed to delete the files. DAMN windows temp file thingys anyway tommorow it will be done
TY man u awesome!!!!! thx u all work fine!!!!
rect2409 said:
mopgawka - Did you get the correct mtdblock number. The file would set the system dir as r/w to enable you. The mtdblock number is the number directly after the text mtdblock, in the image below it is 0.
Another question was there an error after the "Getting ROOT rights" text? This was the bit that caused me the most issues.
x10man - Yes it is just basically a batch file. If you want to port to linux then go ahead
Click to expand...
Click to collapse
In linux we used to set the mount point to a variable and then issuing the r/w command. I don't know how you can do this trick in windows.
Code:
mtd=mount | grep system | awk '{print $1}'
echo "Mounting /system rw"
mount -o remount,rw -t yaffs2 $mtd /system
The question about the mount point isnt in the newer version. It just assumes that the system mtdblock is 0.
If it causes a problem in the future I may change it back to selecting the mtdblock number but from all the times I have tried the mtdblock on the x10 mini pro has always been 0.
In windows the answer is just saved as a variable that you assign to the question.
Sent from my X10 Mini Pro using XDA App
Updated with v3.
Just added new way of gaining ROOT access and another check to make sure phone is ROOTed.
EDIT: Oops forgot I had posted last :/ Sorry
3.2.0.0-r3 is old newest is 3.2.0.0-r5
I tried to fix permissions but it's been doing that for almost an hour now... Is that normal, to take that long? Should I remove the battery?
EDIT: Forget it, after looong time waiting, it's finished
EDIT 2: It erased all my preferences! Is that supposed to happen?
I have never had to fix permissions myself so I don't know the process it uses. You could try in the CWM thread where they should be able to help you. Link is http://forum.xda-developers.com/showthread.php?t=1106146
Sorry
quangnhut123 - I don't have that version of CWM and the CWM thread only has r3. If you have r5 then could you give me the files please and will update it.
rect2409 said:
I have never had to fix permissions myself so I don't know the process it uses. You could try in the CWM thread where they should be able to help you. Link is http://forum.xda-developers.com/showthread.php?t=1106146
Sorry
quangnhut123 - I don't have that version of CWM and the CWM thread only has r3. If you have r5 then could you give me the files please and will update it.
Click to expand...
Click to collapse
r5 is the one with multiboot i believe
x10man said:
r5 is the one with multiboot i believe
Click to expand...
Click to collapse
Ahhh. Okay didn't realise that.
Have uploaded a version that includes r5 for the people that have to have the latest... Also kept v3 up as all that has changed is the CWM version.
so i had to make a split second decision this morning, the store i work at had the Polaroid android tab for 80$, they only had 20 of them with 300+ people waiting outside, so i hid one and bought it later. Now, is there a way to root it and flash a ROM? its pretty decent for 80$, runs on 2.3.1. doesnt come with market though lol. amazon appstore works on it though so no biggie.
Have you tried rooting it using Superoneclick, Gingerbreak and/or z4root?
Curious how it turns out.
Sent from my PC36100 using XDA App
I have tried 'em all, Z4, superone click, gingerbreak...no luck. I've rooted a xoom and droid x, so I'm not a stranger, but won't claim to be an expert either lol! specs are below.
I usually get "killing adb server" daemon started successfully then nothing. perhaps don't have the right adb drivers. this is a southern telecom tablet branded under polaroid (the menard's black friday deal) - thanks in advance for any help rooting this thing...
model PMID700
Android version 2.3.1
kernel version 2.6.32.27
build number 20110918.170336
Firmware version 2.2
Me to
If you get anywhere with this can you please pm me and let me know I got the same one and have been searching to do the same thank you
some progress...
I uninstalled the drivers from device manager and scanned for hardware changes, then used windows update for different drivers. I was then able to get a few of the root choices, superone click and gingerbreak to communicate with the device. now, i'm getting read only file system errors and "file exists" when it tries to install things like super user...below is an example. i'm not all that familiar with ADB and i'm sure there is some sort of command that would make this -rw...that person just doesn't happen to be sitting with me at the moment! lol...good luck and let me know if you have any success!
Unable to chmod /system/xbin/su: Read-only file system
This is all the further I have gotten so far also. Gonna keep trying things for a while longer, but hopefully we can get someone in here who actually knows what they are doing! lol
*UPDATE*
Have been trying everything I know to try and get into recovery or bootloader, no luck though, not even adb reboot commands work.
yes, i bought it at Menards also. anyone get the market to install correctly? i downloaded the APK for it and am able to enter my email and everything but it crashes whenever i open it.... anyone else notice how unresponsive the screen is? i did the calibration nut still doesnt feel sensitive enough. i guess we get what we pay for
it would be cool to see some of the skilled devs tackle this one since im betting alot of people will be getting this for a gift/got it on black friday.
thanks for the replies! if we get enough attention with this thread maybe someone will make a breakthrough?
Yah, I've noticed the screen isn't so great and calibration didn't help. If you use a stylus (or the back of a pen) it responds much better. It appears that I'm literally fat fingering it and the pressure point is bleeding over. AKA crappy screen.
I also have been working on this for a couple days. My original goal was to get the andriod market on the phone but since we cant move the googleframeworkservice.apk over to the system/app folder things don't quite right and crashing begins. Since the system drive is read only it makes things much more difficult.
I originally was posting on this thread: http://forum.xda-developers.com/showthread.php?t=1364310
*edit* Link repost
Sent from my PMID700 using XDA App
PMID700
I very much enjoy this tablet. Its my first, so I really don't have much to compare it too. Your right about the screen. At first, it was really disheartening, but the stylus definately makes it much much better. We just purchased a package of DS styli from walmart. I too would like to be able to root this tablet because the lack of google apps. I'm fairly new to all of this.
I'm not an expert but I have been working my butt off trying to root this. I'm pretty close. I can get super one click and gingerbreak.apk to run. Gingerbreak doesn't seem to do anything. Super one click when using the zerg exploit runs and roots but it won't reboot for me, constant bootloop. I have logcats and I'm gonna look them over. If anyone is interested in getting this s.o.b. rooted, contact me via pm and we can chat. I'm not a super dev or anything but I'm no noob to this either. Another thing I noticed is that adb worked for me without driver installation. But I also have an evo shift and htc sync was installed, and when I plugged in the tablet my htc sync notified me about an attached device... I have also been getting help from indirect (the guy who rooted the nook)... let's put our brains together and root this *****!
Polaroid Tab
I also bought my Polaroid Tab (at a Menards here in Madison). If you do get any updated info, I'd love to know... I wonder if we are able to install some break on a Micro SD Card and then try to hack it that way...
drob311,
if you check out the other thread i posted on you will see that none of the one-click programs will work for us. Our file system is cramfs (compressed ROM file system) its compressed and read only which is what is stopping us. So far i have been able to dump the system img off the tablet but it seems to be encrypted and standard tools for reading images don't work. I'm still working on it but currently I'm stuck. If anyone can help that would be great.
What i've done so far:
You need to open the adb shell and do an rkdump on the images (ex. /data/rkdump /dev/block/mtdblock5 /sdcard/update.img). From that image you need to unpack it with AFPTool.exe which will give you the system.img. I'm currently stuck trying to open this image and modifying it. Once I'm able to open it we should easily be able to add the root tools and the Andriod market and push it back to the tablet.
I've got the rkdump file to be pushed and I will be messing around with this... pm sent as well... thanks!
Sent from my PG06100 using Tapatalk
When I try to get the rkdump from mtdblock5 it says "unknown image (00 00 00 00)". Kind of strange
Sent from my PG86100 using XDA App
I did it without issue on mtdblock4... I as well cannot unpack the update.img... I'm gonna try more tonight...
Sent from my PG06100 using Tapatalk
I too was able to get the system.img from mtdblock4. I also got boot, recovery, and kernel, but I still can't get update.img
This is what I did for the dumps:
Code:
C:\rooting\pmid700\adb>adb shell
# cat /proc/mtd
cat /proc/mtd
dev: size erasesize name
mtd0: 00400000 00004000 "misc"
mtd1: 00800000 00004000 "kernel"
mtd2: 00400000 00004000 "boot"
mtd3: 00800000 00004000 "recovery"
mtd4: 10000000 00004000 "system"
mtd5: 10400000 00004000 "backup"
mtd6: 07400000 00004000 "cache"
mtd7: 20000000 00004000 "userdata"
mtd8: 00400000 00004000 "kpanic"
mtd9: 2d800000 00004000 "user"
# chmod 755 /data/rkdump
chmod 755 /data/rkdump
# /data/rkdump /dev/block/mtdblock1 /sdcard/kernel.img
/data/rkdump /dev/block/mtdblock1 /sdcard/kernel.img
kernel.img found (4869392 bytes)
dumping...
crc found (4 bytes, 0x56c2c7ce)
done
# /data/rkdump /dev/block/mtdblock2 /sdcard/boot.img
/data/rkdump /dev/block/mtdblock2 /sdcard/boot.img
kernel.img found (340979 bytes)
dumping...
crc found (4 bytes, 0x1b3353f7)
done
# /data/rkdump /dev/block/mtdblock3 /sdcard/recovery.img
/data/rkdump /dev/block/mtdblock3 /sdcard/recovery.img
kernel.img found (4372988 bytes)
dumping...
crc found (4 bytes, 0xd48da563)
done
# /data/rkdump /dev/block/mtdblock4 /sdcard/system.img
/data/rkdump /dev/block/mtdblock4 /sdcard/system.img
cramfs found (94093312 bytes)
dumping...
done
# /data/rkdump /dev/block/mtdblock5 /sdcard/update.img
/data/rkdump /dev/block/mtdblock5 /sdcard/update.img
update.img found (103901184 bytes)
dumping...
crc found (4 bytes, 0x4207c1ec)
done
I was able to get all the images and was able to unpack the update.img as well.
Code:
C:\rooting\pmid700\sandbox>AFPTool.exe -unpack update.img Temp/
Check file... OK
------- UNPACK ------
package-file 0x00000800 0x00000227
RK29xxLoader(L)_DDR3_400Mhz_V1.64.bin 0x00001000 0x00027346
parameter 0x00028800 0x00000267
Image/misc.img 0x00029000 0x0000C000
Image/kernel.img 0x00035000 0x004A4D14
Image/boot.img 0x004DA000 0x000533F7
Image/recovery.img 0x0052D800 0x0042BA00
Image/system.img 0x00959800 0x059BC000
SELF 0x00000000 0x06316804
Skip SELF file.
update-script 0x06315800 0x000003A5
recover-script 0x06316000 0x0000010A
Unpack OK!
The problem i still have is getting the system.img from within the Image folder from the unpack command to open. I still plan to try to do the cramfsck from my linux box to see if it can work there. Also i sent the polaroid customer service an email asking for the current firmware (not holding my breath though).
I plan on working on this more tonight so i will update back with any of my findings. Also i have been keeping some instructions on the steps I've taken so far so if I do get this figured out I will share them.
Nice work rozz, I have a question though. Has anyone figured out how to boot this thing into recovery or any other mode?
*off topic* just noticed all of us here are in Wisconsin! lol
Hello:
I'm a buyer of an Iview 760TPC (chinese 1.3Mpx camera version).
The reason I'm writing is because its some days reading and trying things to get everything unlocked, and seems that is really impossible to flash a new firmware or to get root. I'm getting really mad.
- I have managed to get adb recognize the tablet on linux and on windows. Despite of that, I get "adbd cannot run on production builds".
- If I do an 'adb shell', I get a prompt (with no superuser privileges). If I try to 'su', I get a "Passwd:" prompt , so I cannot get a superuser prompt to remount the filesystems, neither push any file to /system.
Browsing, I see there's no 'su' on /system/bin but there's on /system/xbin. Is a read-only filesystem and I cannot push anything.
- I installed root explorer but cannot mount R/W the filesystems.
- Installed Busybox installer. Says that the tablet is rooted, but when I try to install busybox, says that I have not permissions. Same if I try one of the upgrade menus of superuser. There are not privileges.
- I tried many times, to flash a firmware with the livesuit method, but the tablet is not being recognized. When I do the combination to enter the flashing mode, it boots a like a recovery with 4 options:
1) erase user data partition
2) enter adfu
3) upgrade firmware from sdcard
4) exit menu
I'm interested in the 3er option, but I can't find any information of the process itself (where to put the firmware, if its the same img as with the livesuit method, and what name needs to have the file)
There's also an ADFU mode, that I don't understand, but windows recognizes a new device when I enter there (but there's no driver or information I can found). The screen gets like a bit of white color, and the only way to exit from there is to press home+power buttons without the usb cable.
I've tried superoneclick but it doesn't work because there's not 'su' binary. Same happens with the installers of the CWM, not working because there's no 'su' (so I could flash a file with any kind of name)
Any help would be aprecciated. Sorry for my engrish and for asking so much, but I don't know how to proceed ;-)
Thanks
What version of Android is the device running? You could try manually pushing an exploit binary (e.g. zergrush) onto the device and executing to get temp root, at which point you should be able to mount /system as R/W and then push the su binary to /system/bin
The exploit binary to use would depend on the version of Android though. zergrush is for 2.3 I think (maybe 2.3.something). For early versions of ICS (4.0), there is mempodroid (might have spelt that wrong).
EDIT: Also, everything you can do over ADB, you could do by installing SSHDroid on the device and connecting via SSH from a computer.
Thanks a lot for your answer SifJar:
The tablet comes with ICS 4.0.3 and 3.0.8 kernel.
Superoneclick has the psneuter and zergRush exploits(neither of those seem to work for me).
Found this thread:
http://forum.xda-developers.com/showthread.php?t=1461736
Edit: It does not work for me:
./adb shell
[email protected]:/ $ chmod 777 /data/local/mempodroid
[email protected]:/ $ /data/local/mempodroid 0xd9ec 0xaf47 sh
/system/bin/sh: /data/local/mempodroid: not executable: magic 7F45
Thanks
Installed SSHDroid from the Play Store, but does not work either.
I get:
Can't generate RSA keys: sh <stdin>[1]: /data/data/berserker.android.apps.sshdroid/dropbear/dropbearkey: not executable: magic 7F45
Don't really know what else can I do.
Thanks
mempodroid requires a different offset for each device. "0xd9ec 0xaf47 sh" is for the Eee Pad Transformer Prime. You need to get the right offset for your device. You can try this to do that: http://forum.xda-developers.com/showthread.php?t=1612591
EDIT: But it looks like your device may not be able to run standard Android binaries, which would be quite an inconvenience for trying to root it.
SifJar said:
mempodroid requires a different offset for each device. "0xd9ec 0xaf47 sh" is for the Eee Pad Transformer Prime. You need to get the right offset for your device. You can try this to do that: http://forum.xda-developers.com/showthread.php?t=1612591
EDIT: But it looks like your device may not be able to run standard Android binaries, which would be quite an inconvenience for trying to root it.
Click to expand...
Click to collapse
I think I should reflash a new firmware from that recovery that has from factory, but there's no way I can do it. I mean, it is supposed to have an special mode that you enter with a button combination and to flash then with livesuit, but in this chinese clone, does not seem to work that combination of buttons.
From the recovery, ADFU seems to mean Actions Device Firmware Update. There's some information here http://wiki.s1mp3.org/USB_modes
- If I put the device in ADFU mode, windows ask for an USB driver (that I don't have or does not exist either)
- Another thing. There's a flashing from sdcard, that seems to support, but there's no information or manual of where is supposed to put the firmware, the name of the file or if it needs to be zipped (and what file/s inside and names),...
Thanks
It's possible the flashing from sd card supports standard update .ZIPs. You could try this one, it's a ZIP that should work for rooting most Android devices I believe. Superuser.zip
(This is from a topic on the HTC Explorer phone, but there is nothing specific to that phone in the ZIP as far as I know)
EDIT: This ZIP doesn't overwrite the firmware or anything, all it does is add su, busybox and Superuser to the existing /system partition.
EDIT: If selecting the "Update firmware from SD card" option doesn't give the option to browse for a ZIP, rename it to "update.zip" and place it in the root of the card and try again.
SifJar said:
It's possible the flashing from sd card supports standard update .ZIPs. You could try this one, it's a ZIP that should work for rooting most Android devices I believe. Superuser.zip
(This is from a topic on the HTC Explorer phone, but there is nothing specific to that phone in the ZIP as far as I know)
EDIT: This ZIP doesn't overwrite the firmware or anything, all it does is add su, busybox and Superuser to the existing /system partition.
EDIT: If selecting the "Update firmware from SD card" option doesn't give the option to browse for a ZIP, rename it to "update.zip" and place it in the root of the card and try again.
Click to expand...
Click to collapse
Thanks a lot. Does not have a browsing option so I need to know the needed name. Does not seem to work with the update.zip method
Does it try to install update.zip and give an error or does it say there is no update on the SD card?
Also, can you try and extract the su binary you said is in /system/xbin and post it here? There's something I would like to check.
EDIT: From adb shell, type the following, without quotes, "cat /proc/cpuinfo" and post the output here please
EDIT: Another silly suggestion - you could try guessing the password su asks you for. Maybe it's something obvious like "root" or "admin".
SifJar said:
Does it try to install update.zip and give an error or does it say there is no update on the SD card?
Also, can you try and extract the su binary you said is in /system/xbin and post it here? There's something I would like to check.
EDIT: From adb shell, type the following, without quotes, "cat /proc/cpuinfo" and post the output here please
Click to expand...
Click to collapse
Seems that it does not even try to update, no error message, nothing. I tried putting the update.zip in both /sdcard (internal sdcard) and /sd-ext (microsd)
Code:
[email protected]:/ $ cat /proc/cpuinfo
system type : actions-atv5201
processor : 0
cpu model : MIPS 74Kc V5.0 FPU V0.0
BogoMIPS : 719.25
wait instruction : yes
microsecond timers : yes
tlb_entries : 32
extra interrupt vector : yes
hardware watchpoint : yes, count: 4, address/irw mask: [0x0000, 0x0000, 0x0460, 0x0868]
ASEs implemented : mips16 dsp
shadow register sets : 1
core : 0
VCED exceptions : not available
VCEI exceptions : not available
I have attached the 'su' binary from /system/xbin
Also:
Code:
$file su
su: ELF 32-bit LSB executable, MIPS, MIPS32 rel2 version 1 (SYSV), dynamically linked (uses shared libs), with unknown capability 0xf41 = 0x756e6700, with unknown capability 0x70100 = 0x1040000, stripped
But the table description of the manufacturer, says that has an Allwinner A10 (Cortex A8). Does not seem to be true, right?
Thanks
Looks like a MIPS processor then, not an ARM as most android devices have. That explains why exploit don't run and SSH didn't work, both use code compiled for ARM processors. It also means a standard su binary won't work on that device. You'll need one compiled for MIPS.
Does the update from sd card give any sort of error?
No. It does not say anything. I'll try to find the right update.zip for the MIPS architecture. Perhaps it could work.
Edit: Found this https://rapidshare.com/files/2288417520/Superuser-3.0.7-mips32r2-ics_signed.zip , but does not seem that I can flash it from the recovery with the update.zip method
Thanks a lot Sifjar
I'm afraid I'm now out of suggestions. The last piece of advice I can give is try and find an official update for the tablet from the manufacturer and investigate the format of that update, to try and identify how an update should be formatted/named for your device.
Thank you SifJar. You helped me a lot to find what happens with this tablet ;-)
I've read from more people, buying Allwiner A10 tablets on efox, and receiving different ones (lower specs and usually MIPS based). I'd not recommend to buy to this seller because it does not even answer your questions or does give you support.
I'm pretty sure, that could be one of the clones of the Ainol Novo7 Paladin/Basic. I'll try to find it
dreamer_ said:
Thank you SifJar. You helped me a lot to find what happens with this tablet ;-)
I've read from more people, buying Allwiner A10 tablets on efox, and receiving different ones (lower specs and usually MIPS based). I'd not recommend to buy to this seller because it does not even answer your questions or does give you support.
I'm pretty sure, that could be one of the clones of the Ainol Novo7 Paladin/Basic. I'll try to find it
Click to expand...
Click to collapse
Well I believe from a bit of reading about the Ainol tablet you should be able to type "adb remount" and then "adb root" to get root access from adb on that tablet. Then you can push a MIPS su binary to the device and be done with it. But it depends how close a clone it is whether the same will be true for your tablet I guess.
EDIT: Have you found any way to access a fastboot mode? (Possibly the command "adb reboot bootloader" would work) If the bootloader isn't locked, you may be able to extract the system.img, root the img and then flash it back with fastboot. Although that is something I have only heard about, I have no experience in how one would go about rooting the system.img. (Extracting it from the phone and flashing back isn't overly hard).
I have tried both things with no success. The remount, fails and I don't have root access then (and R/O Filesystems)
adb reboot bootloader, just reboots the device
I have found a post from a guy http://tabletrepublic.com/forum/other-tablets/actions-cpu-android-tablet-actions-atm7013-1-3ghz-cpu-2087.html#post20776, that seems to have my same tablet (or both tablets seem to be the same MIPS based).
I still think that could be a novo 7 basic/paladin clone and it does have the same recovery and the DFU mode. I'm downloading the tools and FW from the paladin, but seems to be impossible to find anything more about my tablet.
Thanks
dreamer_ said:
I have tried both things with no success. The remount, fails and I don't have root access then (and R/O Filesystems)
adb reboot bootloader, just reboots the device
I have found a post from a guy http://tabletrepublic.com/forum/oth...ctions-atm7013-1-3ghz-cpu-2087.html#post20776, that seems to have my same tablet (or both tablets seem to be the same MIPS based).
I still think that could be a novo 7 basic/paladin clone and it does have the same recovery and the DFU mode. I'm downloading the tools and FW from the paladin, but seems to be impossible to find anything more about my tablet.
Thanks
Click to expand...
Click to collapse
This is one of the big issues with China based devices. Not only is it have really limited development they tend to use none standard hardware so none of the current things work on it. Then toss in the fact that the hardware is not always what it is said to be.
Sent from my SGH-I897 using Tapatalk 2
The USB drivers for the novo paladin, didn't work for me....If I only could flash a CWM recovery for my tablet, perhaps I could then flash the superuser.zip with the 'su' binary that SifJar said.
zelendel said:
This is one of the big issues with China based devices. Not only is it have really limited development they tend to use none standard hardware so none of the current things work on it. Then toss in the fact that the hardware is not always what it is said to be.
Click to expand...
Click to collapse
Yes...my problem has been mainly that in the efox website, they are basically lying you in the product description, and selling a thing that is not true.
Casually, there's also an IVIEW tablet on the market, exactly like mine, made only for the chinese market (without the IVIEW letters and 1.3mpx camera)...and that was what I thought I bought, a chinese IVEW (and my mistake)
You really need to see the cpuinfo to see that, and not everybody will do it....
Thanks
If you download this: usbview.zip
You can use it to find the vendor ID (app shows it as IdVendor) for your device (put it in the DFU mode thing first), and then you could try using fastboot and specifying the vendor ID with -i argument, it might work without drivers then (not sure if this is right, but I think something similar was done with the Kindle Fire)
just try something like
Code:
fastboot -i 0xFFFF devices
replacing 0xFFFF with the vendor ID from that app, to see if it detects it at all
Thanks. Does not seem to return anything (a return). It works with '-i device' at the end of the line.
Code:
fastboot.exe devices -i 0x10D6
ADB does give me this:
Code:
c:\sonec>ADB\adb.exe devices
List of devices attached
Actions Semi. 23711DF4 device
Hi all, hoping some kind person knows how to compile a CWM recovery image for me (don't care about version) for my Alcatel One Touch 983. I did try the CWM builder but it failed so I guess I'm doing something wrong.
The output for cat /proc/mtd is:
dev: size erasesize name
mtd0: 01000000 00020000 "modem"
mtd1: 00100000 00020000 "sysparm_ind"
mtd2: 00a00000 00020000 "comms"
mtd3: 000c0000 00020000 "dsp_pram"
mtd4: 00300000 00020000 "dsp_dram"
mtd5: 00100000 00020000 "bootloader"
mtd6: 00080000 00020000 "systemdata"
mtd7: 00040000 00020000 "deviceinfo"
mtd8: 00040000 00020000 "ckdatablock"
mtd9: 00100000 00020000 "bootloader2"
mtd10: 00080000 00020000 "FOTAFLAG"
mtd11: 00500000 00020000 "boot"
mtd12: 00500000 00020000 "recovery"
mtd13: 00040000 00020000 "misc"
mtd14: 00080000 00020000 "boot2icon"
mtd15: 07600000 00020000 "system"
mtd16: 03c00000 00020000 "cache"
mtd17: 00100000 00020000 "kpanic"
mtd18: 08300000 00020000 "custpack"
mtd19: 0a000000 00020000 "userdata"
Attached is the recovery.img (in zip format) for the device.
I'm hoping to load this via fastboot (unless instructed otherwise).
Can anyone help please ? there is very little support for this device anywhere at the moment.
Thankyou.
bump....was hoping someone could spend 15mts doing this..ah well !!
give it a day or 2, i'm sure someone will be along to get support for this phone going
and i'll be waiting
Would there be any way to do a recovery via update.zip?
My 983 just got soft locked (loops on turning on and can't even turn off unless removing battery).
I got some bad flashing going in there
Thing is, I don't have access to root, can't turn it in.
I'm a newb in all this android stuff, but I can't seem to use fastboot and turning it on with the up volume key only brings me to a big window that asks me if I want to do a factory reset (factory reset doesn't solve prolly due to that bad flashing).
I can get to recovery screen via adb tho.
Over there I only have the choice to install the update.zip or to reset to factory.
So, as I can see, my only chance is to get an update.zip (can put it on sdcard using my laptop card reader) and run it.
If you have a way to do it, I'll be really grateful.
ahkronn, this is precisely why we need a proper CWM recovery build for this device. With the Alcatel recovery partition you cannot do much, definetly not save your existing ROM. Even if we at least had a factory stock rom you could load it up via 'update.zip', but I have not been able to track one of those down either.
Root is not going to win you much if you're having boot loops, unless you can actually completely boot your device then maybe you can use root explorer to see what's missing or install logging utilities and then look at the logs. As it stand this device doesn't seem to have support anywhere by anyone I can track down across the vast cyberspace. It's a pity, cause I own some 20 android devices and this Alcatel compares quite well in the low to mid-range space. Even unlock (SIM unlock) turned out to be a pain, I had 3 online unlockers refund me the money because they couldn't do it. I guess the lesson here is if you want supported devices (especially on this site) then your HTCs and Samsungs are the way to go.
I wish we could do something about the internal storage space filling up so quickly. If we could even get rid of all the additional Touchpal languages that would be a start.
There is an official application called "Alcatel One Touch Upgrade NB v1.02" that may be able to restore people's broken phones to their default brand new state: http://www.alcatelonetouch.com/glob...ne-touch-upgrade-nb-1-0-3-setup-medoclite.exe
The .exe name says v1.03 so does their website but it is actually v1.02.
I really hope someone makes a stock android 2.3.7 rom for this without all the junk that alcatel forces on us such as their horrible keyboard and large foreign language files. There are a few programs that can unlock the phone via usb now btw. GB-Key is one of the small number of programs, there isn't any programs that can generate unlock codes yet, only direct unlocks via usb.
This phone is just £40 delivered from o2 uk btw. It has a 1ghz broadcom BCM21552G cpu, 512mb ram, 512mb rom, 2gb micro sd. This is literally the perfect best bang for buck phone on the planet. It comes with android 2.3.7, alcatel have already said they won't be bringing out android 4.0+ which is understandable considering it is such a cheap phone. The camera is 3.2mp, there is no camera flash. The screen is 320x480 3.5". It has 802.11b/g/n dual band (2.4/5ghz) wireless, bluetooth 4.0 and nfc, gps and glonass and fm radio. It basically has virtually everything you want yet the phone is just £40 locked to o2 network.
More processor info here: http://www.broadcom.com/press/release.php?id=s638212
help me
when i upgrate my alcatel ot-980 with cynogen it was update sucessfully but i reebbot it . it was stuck in alcatel boot screen dont know what to do....
Here is the Alcatel OT-983 rom: https://www.dropbox.com/s/g2ljtrpqru3uihm/rom 983.zip?m
this .zip file contains the boot.img, system.img and recovery.img
Someone needs to create a clockwork mod recovery for our phones now.
here is the sourcecode for this phone: http://www.mirrorcreator.com/files/85KDRTYP/OT_983_20130103.7z_links
Still hoping for a CWM and CM, or somesuch, for this phone.
hajj_3 said:
I really hope someone makes a stock android 2.3.7 rom for this without all the junk that alcatel forces on us such as their horrible keyboard and large foreign language files.
Click to expand...
Click to collapse
They're in the /system partition so uninstalling doesn't get you any more user mem. I deleted the extra language files anyway, though, as I was sick of the sight of them.
Further information on recovery + boot
This is my first Android phone, and so far I've managed to get out of a few scrapes with it not booting, but this isn't for the faint-hearted....
Anyway, I've been trying to install some recovery software on it, to make life easier. As xzyk has noticed, there are some interesting partition names when doing 'cat /proc/mtd' . When turning on the phone, I think that:
Pressing volume up when powering on enters some sort of recovery mode, where the only option is to wipe the data (recovery partition)
Pressing volume down when powering on enters fastboot mode where I can connect the phone via the USB cable to a linux computer and type fastboot flashing commands (bootloader partition).
I've found out that the Alcatel OT 983 is very similar to the Vodafone smart II aka Alcatel v860 aka Alcatel MTC-962 (if you have used ALCATEL ONE TOUCH Upgrade NB V1.0.2 you can see you either select the MTC-962 or One Touch 983 model). There's a lot of information on this phone in this thread:
Vodafone smart II/Alcatel v860 Reocovery !ROOT!. Look out for posts by phenomenalxp, aka roeddie, the author of roeddie rom. His web site contains an 'extended recovery' image which I think comes from the MTC-962 (a Russian version of the v860). This extended recovery has an option to 'backup and restore'. I can't post URLs but google for 'Vodafone Smart II Recovery roeddie' to see this. Interestingly there's a screenshot of the "All data will be lost,continue?" screen which the OT 983 recovery provides.
I tried installing this image to the recovery partition and it started up by pressing volume up + power on, however it did not recognise the OT 983
keyboard layout, and only the volume up key worked. But it was interesting that it started up at all.
I took a closer look at the image (google "HOWTO: Unpack, Edit, and Re-Pack Boot Images" for info on this). I downloaded split_bootimg.zip, used this command to strip away the header in it
Code:
dd if=recovery.img of=nh_recovery.img bs=2048 skip=1
and then ran
Code:
$./split_bootimg.pl nh_header_recovery.img
Page size: 2048 (0x00000800)
Kernel size: 3141432 (0x002fef38)
Ramdisk size: 1363027 (0x0014cc53)
Second size: 0 (0x00000000)
Board name: RF42W0W0
Command line:
Writing nh_recovery.img-kernel ... complete.
Writing nh_recovery.img-ramdisk.gz ... complete.
$mkdir ramdisk
$ cd ramdisk/
$ gunzip -c ../nh_recovery.img-ramdisk.gz |cpio -i
which extracted the ramdisk, and I found the recovery binary in sbin/recovery.
I ran this binary from a terminal on my phone, and it started up. The text was hidden by Android, but I could see that pressing volume up and down highlighted the different options.
Next I unpacked the original recovery image, replaced the recovery binary with this one, and rebuilt the image using the header from the original image. This time recovery mode didn't boot at all. phenomenalxp thinks that the bootloader is locked, and I think he is right. Using a hex editor on the original recovery and boot images, I noticed that the header is mostly zeros, but interestingly contains these hex codes at offset 0x20:
Code:
BA BE FA CE 28 XX XX 00
BABEFACE looks suspiciously like a marker of some sort. Let's search for this string in the first partition, modem.img (I used 'dd if=/dev/mtd/mtd0 of=modem.img' on my phone to generate this image).
Code:
strings modem.img > modem_strings.txt
If you search for babeface in this file you will see
Code:
ERROR: Couldn't find 0xbabeface in comms image!!!
So there is some sort of checking going on here that the image file is 'valid'. Next I downloaded an ARM disassembler for Windows called disarm (google "Binary file ARM code disassembler for PC") and searched for babeface in the disassembled code.
Code:
000002ec: ldr r4,#0x664 ; = #0x28003000
000002f0: ldr r0,[r4,#0x20]
000002f4: ldr r4,#0x66c ; = #0xbabeface
000002f8: cmp r0,r4
Look, it's checking for babeface at offset 0x20
Code:
000002fc: beq #0x304
00000300: b #0x31c
So let's see what happens if it fails this check
Code:
0000031c: ldr r4,#0x574 ; = #0x8880018
...
00000334: b #0x334
So if the check doesn't work it goes into an infinite loop and never boots.
The word after 'babeface' is some sort of checksum which is checked using some iterative code. So I think if we want to know how to generate this checksum, we need to analyse this code further. This I believe is what we need to do if we want to install CWM recovery or other recovery software on the OT 983.
A cautionary tale...
I had a go at porting roeddie ROM to work on the OT 983. The partition sizes are slightly different between these models, but I thought I could move some apps from the smaller system on the 983 to custpack, which is bigger on the 983. Firstly I used dd to make a backup of the existing yaffs2 partitions (data, system, custpack). Then I used unyaffs from the yafuse project to extract the roeddie ROM and copied the files to the phone via adb, deleting bits and copying things across as I went. Eventually the system became unstable and some binaries weren't working correctly, probably due to having a new system/lib directory. When I rebooted, the system didn't boot up fully, and adb said it couldn't find /system/bin/sh.
So I flashed my backup images back to the phone to restore the original state. But nope, it didn't work. I used unyaffs to extract the contents of the backups, but it said they weren't valid yaffs images.
OK, I thought, One Touch Upgrade NB will restore the phone state, as I've used it before. But when it started up it read the phone, checked online, then told me I already have the latest and greatest version of the software, so it wouldn't allow me to reinstall it! I erased the system and custom partitions to remove system.ver and custpack.ver, but One Touch Upgrade still gave the same message.
Now I was getting really stuck, thinking maybe the software version was in the deviceinfo or systemdata partitions, or that I might have to somehow have One Touch Upgrade to force it to reinstall the software.
I had a go at flashing hajj_3's system image and that made the screen go blank after the usual Android robot had appeared. I guessed it needed information from the custpack partition to make the rest of it work. I extracted hajj_3's system image using unyaffs2, and it said it was a valid yaffs2 image. I had already made a tarball of /system and /custpack using tar running on the phone, so I extracted them, used mkyaffs2image to recreate the images, and flashed them. And...
Success :victory:
So in summary,
You can't backup the yaffs2 images using dd or dump_image - it creates invalid yaffs2 images.
[*]You can't rely on One Touch Upgrade NB reverting your phone's state because it thinks you already have the latest software, and refuses to help.
[*]Keep a tarball of /system and /custpack handy.
[*]Life would be a lot easier if we had decent backup and recovery software on the phone (see my previous post).
Interesting posts, although I must admit alot of it goes over my head - I'm still and Android/Linux noob.
You've somewhat cleared up a mystery for me with what you say about Vodaphone. When I did eventually manage to boot into recovery, I was surprised to see a Vodaphone logo displayed in the background, despite the phone being bought from, and locked to, O2.
And yes, there's definately something funky going on with the bootloader. I've never been able to boot into it.
superusr said:
I had a go at porting roeddie ROM to work on the OT 983. The partition sizes are slightly different between these models, but I thought I could move some apps from the smaller system on the 983 to custpack, which is bigger on the 983. Firstly I used dd to make a backup of the existing yaffs2 partitions (data, system, custpack). Then I used unyaffs from the yafuse project to extract the roeddie ROM and copied the files to the phone via adb, deleting bits and copying things across as I went. Eventually the system became unstable and some binaries weren't working correctly, probably due to having a new system/lib directory. When I rebooted, the system didn't boot up fully, and adb said it couldn't find /system/bin/sh.
So I flashed my backup images back to the phone to restore the original state. But nope, it didn't work. I used unyaffs to extract the contents of the backups, but it said they weren't valid yaffs images.
OK, I thought, One Touch Upgrade NB will restore the phone state, as I've used it before. But when it started up it read the phone, checked online, then told me I already have the latest and greatest version of the software, so it wouldn't allow me to reinstall it! I erased the system and custom partitions to remove system.ver and custpack.ver, but One Touch Upgrade still gave the same message.
Now I was getting really stuck, thinking maybe the software version was in the deviceinfo or systemdata partitions, or that I might have to somehow have One Touch Upgrade to force it to reinstall the software.
I had a go at flashing hajj_3's system image and that made the screen go blank after the usual Android robot had appeared. I guessed it needed information from the custpack partition to make the rest of it work. I extracted hajj_3's system image using unyaffs2, and it said it was a valid yaffs2 image. I had already made a tarball of /system and /custpack using tar running on the phone, so I extracted them, used mkyaffs2image to recreate the images, and flashed them. And...
Success :victory:
So in summary,
You can't backup the yaffs2 images using dd or dump_image - it creates invalid yaffs2 images.
[*]You can't rely on One Touch Upgrade NB reverting your phone's state because it thinks you already have the latest software, and refuses to help.
[*]Keep a tarball of /system and /custpack handy.
[*]Life would be a lot easier if we had decent backup and recovery software on the phone (see my previous post).
Click to expand...
Click to collapse
Hi, after i playing with that recovery and custom, rom, really works like in your case, but when i was playing with aroma mods, e brick everyhing, at this moment, my phone don+t boot, don't ebter in fastboot, only one toutch upgrade detect wit android alcatel onetoutch mobile phone(com9), i can´t recover any of my backups and i can´t acess phone adb or fastboot, can you give me some help?
rwaver said:
Hi, after i playing with that recovery and custom, rom, really works like in your case, but when i was playing with aroma mods, e brick everyhing, at this moment, my phone don+t boot, don't ebter in fastboot, only one toutch upgrade detect wit android alcatel onetoutch mobile phone(com9), i can´t recover any of my backups and i can´t acess phone adb or fastboot, can you give me some help?
Click to expand...
Click to collapse
Not sure what you should do here. If fastboot doesn't work that might mean your bootloader partition is corrupted, or that the 'modem' partition which calls the bootloader is corrupted. What happens when you run One Touch Upgrade? Does it detect the version of software running on the phone?
I don't know how One Touch Upgrade works but it might use fastboot to boot a custom kernel. There's a couple of .img files within One Touch Upgrade - if you replace these with your bootloader image (containing fastboot), does fastboot start then?
superusr said:
Not sure what you should do here. If fastboot doesn't work that might mean your bootloader partition is corrupted, or that the 'modem' partition which calls the bootloader is corrupted. What happens when you run One Touch Upgrade? Does it detect the version of software running on the phone?
I don't know how One Touch Upgrade works but it might use fastboot to boot a custom kernel. There's a couple of .img files within One Touch Upgrade - if you replace these with your bootloader image (containing fastboot), does fastboot start then?
Click to expand...
Click to collapse
HI, One Touch Upgrade detect but says doesnt exist new version, i tried replace, don't work,
Anyone can help-me? The phone is stuck on android logo, don't enter on recovery mode or fastboot, only One Toutch Upgrade NB can detect with driver Alcatel One Toutch Mobile Phone on COM1, with thant i can´t do anything .....an ideas?
superusr said:
I had a go at porting roeddie ROM to work on the OT 983. The partition sizes are slightly different between these models, but I thought I could move some apps from the smaller system on the 983 to custpack, which is bigger on the 983. Firstly I used dd to make a backup of the existing yaffs2 partitions (data, system, custpack). Then I used unyaffs from the yafuse project to extract the roeddie ROM and copied the files to the phone via adb, deleting bits and copying things across as I went. Eventually the system became unstable and some binaries weren't working correctly, probably due to having a new system/lib directory. When I rebooted, the system didn't boot up fully, and adb said it couldn't find /system/bin/sh.
So I flashed my backup images back to the phone to restore the original state. But nope, it didn't work. I used unyaffs to extract the contents of the backups, but it said they weren't valid yaffs images.
OK, I thought, One Touch Upgrade NB will restore the phone state, as I've used it before. But when it started up it read the phone, checked online, then told me I already have the latest and greatest version of the software, so it wouldn't allow me to reinstall it! I erased the system and custom partitions to remove system.ver and custpack.ver, but One Touch Upgrade still gave the same message.
Now I was getting really stuck, thinking maybe the software version was in the deviceinfo or systemdata partitions, or that I might have to somehow have One Touch Upgrade to force it to reinstall the software.
I had a go at flashing hajj_3's system image and that made the screen go blank after the usual Android robot had appeared. I guessed it needed information from the custpack partition to make the rest of it work. I extracted hajj_3's system image using unyaffs2, and it said it was a valid yaffs2 image. I had already made a tarball of /system and /custpack using tar running on the phone, so I extracted them, used mkyaffs2image to recreate the images, and flashed them. And...
Success :victory:
So in summary,
You can't backup the yaffs2 images using dd or dump_image - it creates invalid yaffs2 images.
[*]You can't rely on One Touch Upgrade NB reverting your phone's state because it thinks you already have the latest software, and refuses to help.
[*]Keep a tarball of /system and /custpack handy.
[*]Life would be a lot easier if we had decent backup and recovery software on the phone (see my previous post).
Click to expand...
Click to collapse
Thanks superusr,
That was superb info!
Keep going
Sent from my NexusHD2 using xda app-developers app
Hello all,I had bought a local tablet from calcutta called ICE Xtreme on which I had nightmares,but it also helped me learn n now here is it,a short yet complete guide for ur allwinner devices.
Like me,some of u might have been bored enough abt the stock rom that we decide to experiment.since allwinner CPUs can boot over USB(livesuit mode) n SD cards (phoenixcard) we think nothing will b wrong n flash without a full rom backup (i hav a script uploaded here,find it n hav a look), after the flash we find the stock ROM gone,camera,touch,wi-fi etc gone haywires n cache is mounted as SDCARD!!! Yes,those who used livesuit hav been in stuff lik this. Now I was also in one n upon reading alot I hav seen ppl editing bootloaders,using keyboard mouse,plugging HDMI(lcd broken). After a month of fiddling wit my device its time i share a shortcut that can save many hours of ur life.
Also do backup the boot n bootloader on ur pc as sumtimes flashing destroys the SD.
1st step. Backup ur bootloader n boot images. Use "cat dev/block/nandc > sdcard/dump/boot.img" to backup boot..nw backup bootloader the same way,by replacing nandc wit nanda.
Now u use adb pull method to backup ur system,etc,data(its optional,only do it if u want ur apps).n any other folder from the root of ur device.my script can help u do it instantly. Anyways,u must get the etc n system folder.
After that ur free to flash any ROM image through any method (actually,livesuits the best if u can find the img). Now after flash ur device is on right?? Does the SDCARD mount??if no then turn on USB debug,in adb shell type cd dev/block <enter> then type ls n ull see a list of nand partitions,the last one is the SDCARD in raw format.so format is by: su busybox mkfs.vfat dev/block/nand[drive letter,i.e. nandj] n then type vold.ur sdcard will mount.
Now send those boot n bootloader files to SDCARD/dump. U can use mkdir or mannually make the dir n copy. Thn simply type "cat sdcard/dump/boot.img > dev/block/nandc" n same way type nanda n bootloader to restore the bootloader. Now use adb to push the files of ur stock ROM system/vendor/modules(which u backed up earlier) to tablets system/vendor/modules. N the contents of etc folder to etc on the tablet.nw reboot.
Hey!!! Its working.the LCD shift is gone,cam n wi-fi doing good,touch is not reversed or stuff. Congratulations u restored ur tablet,n now running a completely diffrent ROM on it.enjoy.
Heres another shortcut ive learned. U can get any update.zip n convert it to licesuit image. Just extract the system dir. Thn copy it to ur SDCARD. Make modification if needed,copy the modules u backed up.In adb shell type make_ext4fs -s -l 300M -a system <filename.img> (dir of ur system,i.e mnt/sdcard/system) it will make u a .img file which is same as the system.fex file u get when u break a livesuit image. Copy n replace the ROMs boot n bootloader.fex files wit ur backed up boot n bootloader.img (rename .img to .fex) pack the image again to livesuit format n burn it. It will install like a normal ROM. BUT MAKE SURE FILE PERMISSIONS OF READ WRITE N EXECUTE IS INTACT. ELSE ULL ENJOY HOURS OF BOOTANIMATION. but if ur stuck use the method above n flash any other ROM n fix the RON fr ur device. Guys ROM developing n editing fr allwinner devices are not easy...BTW id lik to thank user [iamabadduck] fr his actual A10 backup script. On which i made mine. Im still doing experiments. Hope this info i shared makes the readers modest enough to make the hit thanks. Bye. [ ill b around,so if any quests,ill ans them].
I was very excited to see someone finally post a guide for these mysterious tablets! Thank you!
However, I ran into some difficulties trying to make use of them, but I think this has more to do with my hardware and trying to match it with the appropriate ROM and compatibility zip.
You see, I have a Kocaso M1060W. It's a very nice little tablet but trying to identify it has been difficult. As far I can tell, it's a clone of the Protab2XXL (I don't know what version) or something called the BC1077. It seems easier identifying other Allwinner A10's, apparently. I know some identifying information can be found in the build.prop file and that's how I figured out the tablets of which it is a clone. I even tried finding a database of different ImageSuit images I could try to use, but either there is none or my Google skills are suffering. Does it matter that Kocaso chose to go with PhoenixCard for flashing their tablets? Some documentation suggests the images for both are the same.
Can you help me find documentation that would help me identify the board and the hardware? Let me know what information you need from the tablet, and I will get it to you. Identification would go a long way towards me making use of your steps.
Also, a question. After the rom is flashed and you "adb shell" in, you have me trying to mount the sdcard directory via the nand block devices, and then entering "vold". It doesn't error but nothing seems to happen. Even stranger, running "mount" tells me that it's done something. Is it because most of the ROM flashes require the data wipe that I should assume I have the capability to read/write within the SDCARD directory?
Allwinner A10 ghost touch (Icoo D70W, goodix chip)
Hello There!
I've got this tablet since last year, but it worked brilliantly for four minutes only.
Here is some detail:
ICOO D70W, Allwinner A10 board , 1 Gb of RAM and 8Gb storage, ICS android.
7 inch IPS display on 1024X600 resolution capacitive multitouch.
The original firmware was a nightmare, so slow , and full of chinese thing with no google play, quick decision -> get another firmware.
I've installed an actual version of AOKP ( I think it was the 9th version) and I used one of those comp file which was for an ainol tablet same hardware details.
After this , my big four minetes has started until a figured out the camera does not work.
I used another compatibility file, from a hyundai tablet same camera details, camera ok , but the touch chip went down and cannot get back, since that.
Ghost touches on the screen, but the normal touches are recognised as well.
Do you have any idea, how to reflash that touch driver chip?
attached files from the original firmware, maybe give some help:
And a video on y_-tube, with this watchcode: YfNZf2BgL3w or use "ICOO D70W ghost touch problem" keyword
Thanks in advance.
Zsolt
Compatability
konyazsolt said:
Hello There!
I've got this tablet since last year, but it worked brilliantly for four minutes only.
Here is some detail:
ICOO D70W, Allwinner A10 board , 1 Gb of RAM and 8Gb storage, ICS android.
7 inch IPS display on 1024X600 resolution capacitive multitouch.
The original firmware was a nightmare, so slow , and full of chinese thing with no google play, quick decision -> get another firmware.
I've installed an actual version of AOKP ( I think it was the 9th version) and I used one of those comp file which was for an ainol tablet same hardware details.
After this , my big four minetes has started until a figured out the camera does not work.
I used another compatibility file, from a hyundai tablet same camera details, camera ok , but the touch chip went down and cannot get back, since that.
Ghost touches on the screen, but the normal touches are recognised as well.
Do you have any idea, how to reflash that touch driver chip?
attached files from the original firmware, maybe give some help:
And a video on y_-tube, with this watchcode: YfNZf2BgL3w or use "ICOO D70W ghost touch problem" keyword
Thanks in advance.
Zsolt
Click to expand...
Click to collapse
If you could Post an lsmod from both the Working Firmware and the Non-Working I will take a swing at answering your question...The problem is likely one compat file is installing drivers for one of Your pieces of hardware and not the other and the other compat file is istalling the driver for the other piece but not the One... confusing sounding...
But Bottom Line is If I had the Lsmod from the working Hardware and the 2 compatability files you tried I could likely alter one of the compatability files to cover All of your hardware.
Or better yet pull the Bootloader.img and the Boot.img out of your Tab and send them to me...
you can do this by opening a cmd window from a directory where you wish to store the .img files then type the following :
adb shell su -c "cat /dev/block/nandc > /mnt/sdcard/nandc-root.img" (Press enter Key)
adb pull /mnt/sdcard/nandc-root.img (Press enter Key)
That will give you the Boot.img (named nandc-root.img)
adb shell su -c "cat /dev/block/nanda > /mnt/sdcard/nanda-bootloader.img" (Press enter Key)
adb pull /mnt/sdcard/nanda-bootloader.img (Press enter Key)
That will give the bootloader.img (named nanda-bootloader.img)
send those from both your OEM Rom that is working and the Target Rom you wish to make work .... from that I can either write a compat patch for it or send back the edited ones from your Target Rom (the one you wish to work)
Srry i cudnt keep my promise of being around. Had been pretty busy looking for stock JB ROMs in livesuit format. Found some. Some worked n some didnt. Will abt the touchscreen issue if that Rom has a focaltech ftx_5x touchscreen its broken. U hav to compile it again leaving out the multitouch part in a header file. Do a google search. There r alot of articles. N abt da nand part well not all roms break the internal SD partition. The busybox thing u do only when ur internal cards dont mount. It will NOT WORK FOR A MICROSD IF U HAV ONE. Its generally mounted as extsd.
Try reading from here:
konyazsolt said:
Hello There!
I've got this tablet since last year, but it worked brilliantly for four minutes only.
Here is some detail:
ICOO D70W, Allwinner A10 board , 1 Gb of RAM and 8Gb storage, ICS android.
7 inch IPS display on 1024X600 resolution capacitive multitouch.
The original firmware was a nightmare, so slow , and full of chinese thing with no google play, quick decision -> get another firmware.
I've installed an actual version of AOKP ( I think it was the 9th version) and I used one of those comp file which was for an ainol tablet same hardware details.
After this , my big four minetes has started until a figured out the camera does not work.
I used another compatibility file, from a hyundai tablet same camera details, camera ok , but the touch chip went down and cannot get back, since that.
Ghost touches on the screen, but the normal touches are recognised as well.
Do you have any idea, how to reflash that touch driver chip?
attached files from the original firmware, maybe give some help:
And a video on y_-tube, with this watchcode: YfNZf2BgL3w or use "ICOO D70W ghost touch problem" keyword
Thanks in advance.
Zsolt
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1520943
It's a thread about the allwinner A10 or EKEN T01A.. it shows how to reflash to original and updated EKEN firmwares via livesuit. And also i think they mentioned something about touchscreen issues. Hope it helps
Hi please help me! I have nightmares too with my tablet:
Hi, i have a mid tabler model HBD-Mid-708G like that http://marcopolocompany.fucsio.com/e...oducts/MC-708G . This is a Boxchip a10 with 11 partitions, i get this info throw ADB.
My problem was try to install CWM getting the error Can´t Mount / Read!!!!!
I have been used this roms:
F1-4.1.1-20130319.2.0.6-A721_v4.2
pdf_android4.0.10_ctp7_public_en_0319
Q7_512M+flash+Gmail
rom_woo_comet_404_291112_0cd4d
RSH-A10-C2
speed.1.1.1
sun4i_crane_t01a-linsay-20120411
and only rom_woo_comet where some Ok! .
Solved this CWM problem flashing a rom_woo_comet using LiveSuit but the result is an screen resolution problem: (the image attach) .
So please any can say me a correct rom?
Thanks
accessing nand
hi there,
this is interesting stuff you are talking about here. Unfortunately, I get stuck to the beginning. How do you access the nand???
you say sart with cat dev/block/nandc > sdcard/dump/boot.img
I'd love to but where do you enter these commands? When I connect my tablet to my computer, I see certains parts as usb storage, and I have no way of entering commands to the tablet. From within android, everything is blocked...
thanks for your help
nacxo said:
Hi please help me! I have nightmares too with my tablet:
Hi, i have a mid tabler model HBD-Mid-708G like that http://marcopolocompany.fucsio.com/e...oducts/MC-708G . This is a Boxchip a10 with 11 partitions, i get this info throw ADB.
My problem was try to install CWM getting the error Can´t Mount / Read!!!!!
I have been used this roms:
F1-4.1.1-20130319.2.0.6-A721_v4.2
pdf_android4.0.10_ctp7_public_en_0319
Q7_512M+flash+Gmail
rom_woo_comet_404_291112_0cd4d
RSH-A10-C2
speed.1.1.1
sun4i_crane_t01a-linsay-20120411
and only rom_woo_comet where some Ok! .
Solved this CWM problem flashing a rom_woo_comet using LiveSuit but the result is an screen resolution problem: (the image attach) .
So please any can say me a correct rom?
Thanks
Click to expand...
Click to collapse
You need to edit your script.bin inside the bootloader.img... there is a utility to do this on techknow.me...
to do it manually you need to extract the script.bin file from the bootloader.img ... easiest way is from adb shell
Open a windows command window (this assumes you have adb.exe in your Path .. if not you must do this from the
same folder where adb.exe is located)
type the following
adb shell su -c "cat /dev/block/nanda > /mnt/sdcard/nanda-bootloader.img"
adb pull /mnt/sdcard/nanda-bootloader.img
this will place a file called nanda-bootloader.img in the folder where you ran the windows command window.
Now copy the file to your Linux Machine or VM
and from a terminal do the following:
mkdir bootloader
sudo mount -t vfat ./nanda-bootloader.img bootloader
This mounts the bootloader image to the bootloader folder.... in the bootloader folder copy the script.bin file to another location for editing.
to edit it must be converted to fex... you will need the fex tools for this I have them posted here: http://www.4shared.com/zip/Nzn6PV-b/tools.html
your Linux machine has to be x64 for those to work.
from the folder containing the tools folder and script.bin file open a terminal and do the following:
./tools/bin2fex script.bin > script.fex
this will create the script.fex file which is editable in a linux text editor, open the file and edit the [lcd0_para] section
to correct your screen shift ... the exact settings needed are impossible for me to determine as I do not
have your tab nor the rom you originally had on it.. if you have the original rom available (with screen position correct)
you can pull the script.bin from that rom and replace the entire [lcd0_para] section with the same section from your working rom
to solve the issue.
once edited convert back to .bin from a terminal with the following commands:
./tool/fex2bin script.fex > script.bin
now open the bootloader folder as superuser and delete the script.bin and script0.bin located inside...
copy the new script.bin file in and also copy it and rename the copy to script0.bin and place that there as well.
then from folder containing bootloader folder open a terminal and do the following:
sudo umount bootloader
now copy nanda-bootloader.img to windows machine.
open a Command window in the folder containing your new nanda-bootloader.img file and do the following
adb push nanda-bootloader.img /mnt/sdcard
adb shell su -c "cat /mnt/sdcard/nanda-bootloader.img > /dev/block/nanda"
adb shell rm /mnt/sdcard/nanda-bootloader.img
adb shell su -c "sync"
adb shell su -c "reboot"
if all was done properly your tab should now reboot with the correct screen geometry. The utility I mentioned does
pretty much all of this for you, but i cannot link it here as it is on techknow.me which requires registration to
download ... and the rules forbid links to such sites here.
I hope that all helps you.
---------- Post added at 12:24 PM ---------- Previous post was at 12:16 PM ----------
djahma said:
hi there,
this is interesting stuff you are talking about here. Unfortunately, I get stuck to the beginning. How do you access the nand???
you say sart with cat dev/block/nandc > sdcard/dump/boot.img
I'd love to but where do you enter these commands? When I connect my tablet to my computer, I see certains parts as usb storage, and I have no way of entering commands to the tablet. From within android, everything is blocked...
thanks for your help
Click to expand...
Click to collapse
You must have the ADB drivers installed and know where they are located, placing them in your Path statement is a good idea if you intend to do much ROM editing or direct Tablet commands from and adb shell.
NOTE: To open a command window from any folder on your computer in Explorer browse to the folder you want to open command window from
then in an area of the folder window that is empty right click mouse while holding shift then select open command window here
Once you have ADB INstalled, if the adb.exe is in your path open a command window from any folder you like on windows and type the commands in the command window. If ADB.exe is not in your path you must open a command window in the folder containing adb.exe
(Usually the android SDK Platform tools folder)
I Hope that helps
Thanks fsebentley, I've now copied all nandX partitions.
what I'm trying to do now, is to create a bootable sd card. I believe I must tailor u-boot.bin to boot a specific kernel with my specific hardware setup.
I've found a lot of resource for arm boards, but almost none for tablets, except for direct flashing but I'm not ready to go this far.
So, do you know about a nice tool to read what's in u-boot.bin and eventually modify it?
Touchpad driver
Hi!
I need some help!! I want to include touchpad driver an cm9 installer because when I instal the system with CWM but the touchpad not working!!!
Here is the topic where you can find the ROM: http://forum.xda-developers.com/show....php?t=1861445
Sorry I write here because I can't write in the original topic.
Thank for help!!!
Apad 711 stuck at boot logo
Hi Guys,
I need help. one of my friend has a Apad711 tablet and his stock android recovery was changed by cwm 5.08 incorrect version and hence the power + - or power button was not responding.
I took over and had flashed 6.0.2 8 cwm by following this forum http://forum.xda-developers.com/showthread.php?t=2189640
and recovery was working properly, but then i though of upgrading it to cyanogen mod 9 and downloaded the files using this forum
http://forum.xda-developers.com/showthread.php?t=1760929
however after the update was completed the touchscreen didnt work and I had to connect a usb OTG cable along with usb mouse to get into recovery. I then did a little research and tried flashing a couple of compatibility zip
711i_compatibility_1.1.0.zip, lyf1_compatibility_1.1.0.zip, 711i_compatibility_1.2.0.zip, lyf1_compatibility_1.2.0.zip which had similar specs from this website http://old.androidfilehost.com/main/Allwinner_A10_Developers/christiantroy/misc/
but even after doing so touchscreen,camers etc didnt work.
since i had made a backup of stock rom using cwm before flashing cyanogenmod 9 i thought of restoring it back using cwm 6.0.2.8
i was able to restore the back up but to my surprise i am now stuck at apad boot logo and cannot boot to recovery using the volume - and power key. i tried to connect the tablet to pc so that i can get into adb interface and reboot to recovery but the computer detects the tab as unknown device
I now need help to get into recovery and flash a rom that would make it work or complete tutorial to install/flash a new /stock rom or cyanogenmod to get the device back to life.
please refer to the manufacturers website link listed below for specs:--
http://www.apadtab.com/711_spec.php
Any help would be greatly appreciated.
allwinner a10., broken bootloader
Hi i've got a eneoze tablet with an allwinner A10., now i've flashed my bootloader with berryboot en it was working., later i wanted to change some things in de configs of the berryboot bootloader and i messed up. Now my tablet is completely dead.
It doesn't doe anything when i try to turn it on., de screen doesn't even light up., it isn't recognised when i connect it to the pc so fastboot., adb aren't working eather.
Do you have any ideas on how to resolve this.?
Greets Sam
sammekevremde said:
Hi i've got a eneoze tablet with an allwinner A10., now i've flashed my bootloader with berryboot en it was working., later i wanted to change some things in de configs of the berryboot bootloader and i messed up. Now my tablet is completely dead.
It doesn't doe anything when i try to turn it on., de screen doesn't even light up., it isn't recognised when i connect it to the pc so fastboot., adb aren't working eather.
Do you have any ideas on how to resolve this.?
Greets Sam
Click to expand...
Click to collapse
If you can't flash it from your pc, create a bootable sd card. For example, you could copy your berryboot image to the sd card and boot from it.
Supposedly, you saved your tablet nand into an image before messing up with that nand. Once you boot from sd, flash the nand again with that saved image. Good luck to you
need a little help
i wnt to increase resolution of my a10 tab from 800x480 to 1024x600....to do so i need to edit the bootloader(bootloader.fex)
but,the problem is i can't edit the bootloader.fex correctly......how to edit properly