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
Related
hi, i recieved a eris from a friend of mine with the intentions on fixing it and using it. when i power it on there's just a black backlit screen.. no splash, nothing. if i plug usb in it goes to a htc screen with 4 triangles in the corners. i've tried the ruu update and it gives an 110 error at the end saying something about files not found, i unhooked the usb and it went to a white screen with hboot 1.49 , n s-on n all that stuff.. and it showed info from the ruu, and it showed that the system and boot(or recovery, i cant remember exactly) failed and they were red. i can connect with fastboot but not with adb.. is there anything i can do to atleast get the phone working.. fastboot oem boot doesnt work for me, it just gives a long list of errors
fastboot will do nothing useful for you if you have the 1.49.0000 S-ON bootloader.
The basic definition of a brick for the Eris is this:
1.49.0000 S-ON bootloader + no recovery + non-booting OS = brick
So, let's review.
1) You have 1.49.0000 S-ON. There is no PB00IMG.zip available to you that can change that using Hboot (without performing some magic with a custom recovery first), and fastboot is worthless with S-ON. So, no go there.
2) You didn't mention (or your description was lacking detail) what happens when you try to go into the Hboot menu (cold start with Vol-Down+End). From there you might be able use the menu to try to launch the recovery boot, to see whether (a) it is the stock recovery, (b) it is a custom recovery, or (c) it fails to start. You should try that next.
If that doesn't work, try a cold start with Vol-Up + End. (You need to keep holding both the buttons down until the screen lights up). That is an alternate way to get to the recovery (when a 1.49.xxxx bootloader is on the phone).
If you have a "stock" recovery, you will see a splash screen with an image of the phone and a triangle with an exclamation point in it. (Pressing Vol-Up+End after you see that splash screen will show a blue menu). If you have Amon_RA's custom recovery, you will see a green menu.
3) If your kernel boots, but the OS is "hanging", there is a remote possibility that you can initiate a factory reset from the "hung" OS. This is a long shot, but you power up the phone normally and then press together Vol-Up+Send+End after waiting a couple of minutes. This might make it bootable. (As I said, "long shot". The fact that you have 1.49.0000 on the phone suggests that the prior owner tried some things - and apparently failed at it.)
bftb0
thanks for the response
i tried all of that just now and all i get is a black backlit screen unless i connect usb which gives me a black screen with HTC n four exclamation point triangles in the corners. and there isnt anything i can do from that screen and its bricked huh?
SoSicWiTiT said:
thanks for the response
i tried all of that just now and all i get is a black backlit screen unless i connect usb which gives me a black screen with HTC n four exclamation point triangles in the corners. and there isnt anything i can do from that screen and its bricked huh?
Click to expand...
Click to collapse
That's not a very good sign. I will say, however, that it is very strange that you can get the phone into RUU mode but not have a working bootloader - those two observations are mutually exclusive.
For grins, you could check to see if perhaps your Vol-Up/Vol-Down keys are broken by doing the following:
- Cold start the phone by pressing Send + End simultaneously (make sure to press Send first so that you are not initiating a normal boot; hold both keys down until the screen lights up). Make sure you pull the battery and have the USB cable disconnected when you pull the battery before you try this (to insure that the phone is "really" off).
If that works, the phone will be in Fastboot mode. You might be able to get into Hboot (but not recovery if your Vol-Up/Vol-down keys are broken) at that point with the command
Code:
fastboot reboot-bootloader
from a USB-connected PC.
Under normal circumstances, you can navigate from Fastboot Mode to Hboot and then from there to the Recovery boot - but this requires working Vol-Up or Vol-Down keys.
There is a very, very slim chance that if you can get Hboot launched this way (that is "fastboot reboot-bootloader")... and try to apply the Leak-V3 "PB00IMG.zip" file. If I recall correctly, you don't need Vol-Up/Vol-Down to apply an HTC PB00IMG.zip file - just the trackball press.
I'm not optimistic though - I think that the Leak-V3 (and all other Leak PB00IMG.zip) files probably will just fail with "Main Version is Older Messages".
As for other avenues of approach, there are no publicly known exploits of the RUU mode (= oem-78 mode).
Good luck
well
actually after staying up n working at it for 48 hours, i'm halfway done with a solution...and maybe the first ruu exploit.
i decided to run the 2.1 RUU and after it does its install wizard thing, i navigated to the temp folder where it installed all the files. i took the root rom (pb00img.zip) n renamed it to "rom.zip" then over wrote the version in the temp folder and started the ruu (clicked next and what not).. it failed as usual with error 110.. but afterward i noticed my phone says
pb00100 xc ENG S-OFF
HBOOT-1.49.2000
and before i did the file swap and ruu it said
pb00100 XC ENG S-ON
HBOOT-1.49.0000
so now i might be able to flash a custom recovery thru fastboot since i have s-off now
if not.. still.. its progress
Hmmm, interesting.
Whether or not that qualifies as new behavior sort of depends on what your "friend" did to the phone prior to getting it into the nearly bricked state. If they had previously run the jcase "Flash any RUU" method, then the Root ROM would have "taken" with the Hboot method... although in your case, since you "couldn't get there from here", my hat's off to you for a clever way of making the best of what you have!
Since you have the S-off bootloader, you might be tempted to direct-boot Amon_Ra without even bothering to flash it:
Code:
fastboot boot recovery-RA-Eris-v1.6.2.img
to see if your phone springs to life... congrats if you see a menu!
bftb0 said:
Since you have the S-off bootloader, you might be tempted to direct-boot Amon_Ra without even bothering to flash it:
Code:
fastboot boot recovery-RA-Eris-v1.6.2.img
to see if your phone springs to life... congrats if you see a menu!
Click to expand...
Click to collapse
i did that right after i seen it say "S-OFF". i get to the menu but when i try to flash a rom it gives me an error after formatting system.
Code:
E:Can't symlink /system/xbin/arp
E:Failure at line 65:
symlink /system/xbin/busybox SYS
TEM:xbin/arp
and after hours or more reading, everything is pointing to the boot and system partitions being corrupted by a bad flash of some sort.
i think i might have hit the end of the road..
EDIT
i managed to somehow get all the regular hboot, fastboot, n recovery to work and flashed amon_ra and can get to it from volup+power.. even got the 3 skateboarding droids on normal power on..
but cant flash any roms , from amon's ( gives the error above )or pb00img from hboot (at the end has "failed-PU" next to system..)
any idea's?
I have a couple ideas (still typing them up) ... in the meantime, if you boot Amon_RA and then open up a shell from the PC ("adb shell") and then
- check the output of "dmesg" to insure that the MTD partition table is still intact; you should see something like this towards the beginning of the boot log:
Code:
NAND_EBI2_ECC_BUF_CFG: 1ff
flash_id: 5501bcec size 20000000
Creating 6 MTD partitions on "msm_nand":
0x00001ff60000-0x000020000000 : "misc"
0x000002c60000-0x000003160000 : "recovery"
0x000003160000-0x0000033e0000 : "boot"
0x0000033e0000-0x00000dde0000 : "system"
0x00000dde0000-0x000015fe0000 : "cache"
0x000015fe0000-0x00001ff60000 : "userdata"
- try mounting (in turn) each of /system, /data, /sdcard, e.g.:
Code:
mount /sdcard
mount /data
mount /system
/cache should already be mounted.
Which mounts fail?
bftb0
The scenario you describe has come up before - or at least very similar symptoms.
Note that Nandroid restore will fail because it uses standard Unix tools such as "rm" to clear filesystems, so if a partition will not mount because of a corruption issue, nandroid will fail. I suppose that the same thing is true of the /sbin/recovery utility running underneath the booted recovery kernel (but I have not read the source code to verify that it is attempting to "mount" the filesystems first - if it didn't do that, it would need to understand the raw format details of yaffs2, and I think that is a stretch).
Unfortunately the filesystem formatting tools provided by Amon_RA do not include tools for repairing the mtd (NAND flash) - they are for the SD card/ extN filesystems. It is my impression, however, that the "yaffs2" filesystem is "format free" - meaning that a clean (Flash memory) "yaffs2" filesystem is simply a bunch of zero'ed pages - no superblocks, or Inode lists, - none of that. This suggests that the equivalent of "dd if=/dev/zero of=/dev/mtd/mtdNNN bs=..." could "repair" a yaffs2 file system by simply wiping it... but let's try something a little less crude than that (see below).
I had one of the file systems in my phone in this state at one time and I was able to repair the problem by reflashing the Root ROM - otoh, XDA user "stick" tried this and it seemed to produce a permanent brick in his case, so I am reluctant to recommend you do that. (You might, however, want to perform the jcase "Flash any RUU" hack to the "misc" partition so that you have flexibility to apply any PB00IMG.zip file)
Because the "flash_image" tool (in /sbin/flash_image in Amon_RA) writes both boot images and yaffs2 image files to arbitrary mtd partitions (and raw binary files to "misc"!), there is a chance that it is merely the equivalent of "dd for the MTD device" - so that you could "repair" a corrupted yaffs2 filesystem by simply overwriting it with a valid yaffs2 image file. The repair strategy here would be to:
- Unpack any PB00IMG.zip file and move the contents to a folder on the SD card. (Verify the md5sums of the files on the SD card before you use them - use this reference)
- Use "flash_image" from Amon_RA to flash the corresponding image file for the offending ("won't mount") partition, e.g.
Code:
flash_image system /sdcard/unpacked-PB00IMG/system.img
If this succeeds, see if you can "mount /system".
bftb0
PS Don't try flashing "system.img" using fastboot. However it is engineered (by the HTC bootloader) it will fail due to space issues. It is possible that the HTC bootloader uses the /cache partition to temporarily stage the file, which is only 130 MB compared to 159.5 MB for the /system partition - but whatever the explanation, the experimental result is that that on the Eris, you can not flash /system from fastboot. All the other partitions, no problem - but not the /system partition.
thanks,
i tried what you suggested and it let me mount all 3 of those partitions, and i tried using flash_image to flash the system.img i extracted and in return got a million and one errors..
starting with mtd: ECC error soft 0 hard 1 (continuing until about a hundred something)
then
mtd: not writing bad block at (basically the entire /system hex range)
then finally
error writing system: no space left on device
SoSicWiTiT said:
thanks,
i tried what you suggested and it let me mount all 3 of those partitions, and i tried using flash_image to flash the system.img i extracted and in return got a million and one errors..
starting with mtd: ECC error soft 0 hard 1 (continuing until about a hundred something)
then
mtd: not writing bad block at (basically the entire /system hex range)
then finally
error writing system: no space left on device
Click to expand...
Click to collapse
Was the partition table information correct? (I have seen innocuous "write error" messages on my phone, but they only occurred on regular block boundaries - not for every page; but in that case I don't think I ever saw an "out of space" message. Assuming everything was performed correctly, your phone is behaving as if large blocks of flash memory are being skipped due to "bad blocks")
Did you unmount the filesystems prior to doing the writes?
That is very mystifying.
If you can mount /system, or /data, what happens when you go in and do a
Code:
mount /system
cd /system
rm -rf /system/*
mount /data
cd /data
rm -rf /data/*
cd /
If those succeed, unmount everything
Code:
cd /
for x in /system /data /sdcard ; do
umount $x
done
Run an Amon_RA "wipe data/factory reset", and try and flash a ROM.
???
bftb0
One other thing you could try - I have never used it, so I don't know what effect it will have - is to use fastboot mode to erase the "system" and "data" partitions, and see if that has any effect on your ability to flash a ROM.
In fastboot (boot w/ Send+End) mode:
Code:
fastboot erase system
fastboot erase data
And then afterward boot into Amon_RA and try flashing a ROM.
I suppose you could also erase the boot partition this way, but you probably ought to do them one at a time just to minimize erase operations - and then if an operation fails in Amon_RA, examine the log file at
Code:
adb shell cat /cache/recovery/log
to see if it provides further elaboration on the nature of the error(s).
bftb0
Something else to try:
The symptoms you have (esp. since it appears that /system and /data will mount correctly) appear as if you "run out of space" when flashing ROMs to NAND. I suppose that could occur if somehow a bunch of pages in flash memory got (erroneously) marked invalid. Unless there is some means to clear flash memory so that bad page indicators are cleared, there is no way to reclaim those pages. (It is my impression that brand new NAND flash chips are already programmed with bad pages pre-marked)
It would be nice if the partition erase function of fastboot actually performed the page reclaim/retesting/re-marking operation - but there is no way to know whether that happens, as the HTC bootloader acts as the interpreter of "fastboot commands" passed over the wire (USB). It is free to implement whatever bad page management strategy that HTC desires - and frankly, a "never reclaim bad pages" policy is fairly reasonable when you consider that most consumer phones are flashed perhaps only 3 or 4 times in their lifetime - if that.
Something to try: if you perform a manual wipe of either /system or /data (after mounting them), do a "df" to see how much free space the kernel thinks they have - for a normal phone, that should be pretty darn close to the partition size. E.G.
Code:
> adb shell
# mount /system
# df /system
# mount /data
# df /data
# umount /system
# umount /data
# exit
>
If it seems "short" by a substantial amount, try installing a "small footprint" ROM, such as CELBFroyo 3.2 - it only uses about 100216 KB (97.9 MB).
Just a thought; I realize this is grasping at straws, but there is little for you to lose (which you knew right from the get-go).
bftb0
wow seriously i appreciate all the help you've provided , you need a donate button lol.
the system partition is 66% used (bad blocks im guessing) after a format leaving 59,648 useable
but the data partition is fine with 1% used. and 162,176 usable
but i havent lost all hope yet and this is entertaining me.
custom mtd maybe..swap /data to mtdblock3 (the bad one, system) and and /system to mtdblock5 (where data currently is).. or use a memory card idk?
here's where i got the idea
http://forum.xda-developers.com/showthread.php?t=717874
SoSicWiTiT said:
the system partition is 66% used (bad blocks im guessing) after a format leaving 59,648 useable
Click to expand...
Click to collapse
Holy crap!
For grins, could you do a "cat /proc/yaffs" and post up the section for the "system" partition? (You need /system to be mounted when you run that command).
Here's what mine looks like after performing an erase with fastboot, booting into Amon_RA, and then mounting it:
Code:
Device 1 "system"
startBlock......... 0
endBlock........... 1359
totalBytesPerChunk. 2048
nDataBytesPerChunk. 2048
chunkGroupBits..... 0
chunkGroupSize..... 1
nErasedBlocks...... 1359
nReservedBlocks.... 5
blocksInCheckpoint. 0
nTnodesCreated..... 0
nFreeTnodes........ 0
nObjectsCreated.... 200
nFreeObjects....... 96
nFreeChunks........ 86976
nPageWrites........ 0
nPageReads......... 0
nBlockErasures..... 0
nGCCopies.......... 0
garbageCollections. 0
passiveGCs......... 0
nRetriedWrites..... 0
nShortOpCaches..... 10
nRetireBlocks...... 0
eccFixed........... 0
eccUnfixed......... 0
tagsEccFixed....... 0
tagsEccUnfixed..... 0
cacheHits.......... 0
nDeletedFiles...... 0
nUnlinkedFiles..... 0
nBackgroudDeletions 0
useNANDECC......... 1
isYaffs2........... 1
inbandTags......... 0
I wonder what your "nRetireBlocks" count is.
I only poked around in the HTC "msm_7k" kernel code a little while ago for some clues, so I'm no expert. There does not seem to be any useful knobs to turn by using mount options.
Because Flash filesystems have to deal with new bad pages as they develop, I'll bet the phone could be completely fixed if there was a way to clear the bad pages - ( if they were actually bad, then on the first write use the write would fail, the pages would be marked bad, and the FS driver would recover gracefully - just as normally happens).
But as you say, that would probably require a custom kernel at the minimum with patches to the mtd driver. I do wonder if the kernel driver for the MTD device exposes any hooks (ioctls, etc) that would let you write a (privileged) userspace app which could wipe the raw pages status info.
This YAFFs doc suggests that certain tuning operations can be performed by writing options to /proc/yaffs, including control of tracing. One of the things that seems possible to control is the number of write attempts per page.
I'll have a look at your URL; no promises, though.
bftb0
[ Edit ] PS - do you have any idea what your friend did to get the phone in this state? Maybe flashing a ROM with really, really low battery? It seems hard to believe that an actual hardware problem occurred - moreover, this is not the first phone where very similar symptoms were exhibited.
I'm wondering if a busybox with mtd-utils compiled in might be of some assistance; in particular the "flash_eraseall" tool. (Perhaps use it with the "-N" option?)
lookit recent versions of the "flash_erase.c" code (excerpted from above Git link):
Code:
static void display_help (void)
{
printf("Usage: %s [options] MTD_DEVICE <start block> <block count>\n"
"Erase blocks of the specified MTD device.\n"
"Specify a count of 0 to erase to end of device.\n"
"\n"
" -j, --jffs2 format the device for jffs2\n"
[COLOR=green][B] " -N, --noskipbad don't skip bad blocks\n"[/B][/COLOR]
" -u, --unlock unlock sectors before erasing\n"
" -q, --quiet display progress messages\n"
" --silent same as --quiet\n"
" --help display this help and exit\n"
" --version output version information and exit\n",
PROGRAM_NAME);
}
(I don't have that version of busybox - I see references made to it in a few posts here on XDA, but I don't know it's origin or where to get it)
bftb0
[ Edit ] looked around for a bit and couldn't find anything pre-built; looks like you might have to build mtd-utils using the NDK for Android. Time for bed for me; here's the link to the mtd-utils project.
i found out that my friend installed rom manager n clockwork recovery and did a flash that failed then ran the 2.1 ruu thinking it would fix it. and that's how the phone got to the state i started with.
i actually got a rom to flash (kinda) with some info from that link i posted. i patched my recovery with files from that link which gave it a custom mtd (table) , i shrunk cache and used the extra space to make up for the bad blocks in system and bind mounted cache to and ext partition on my sd card... and all would be great BUT i realized that the boot partition is corrupt too.. ( which makes sense, since clockwork is known to corrupt both)
so my solution was to flash boot.img to recovery and just boot normally with volup+powerand use amon ra by "fastboot boot " if i need to.
but i cant flash the zip file that patches the kernel to boot using the custom mtd because it's script copies,unpacks,patches then repacks boot.img from /boot but my boot.img is on recovery so im either going to have to edit the .sh in the zip or have someone do the whole custom mtd thing and use the same mtdpartmap.txt and have them nandbackup then give me the boot.img from the backup folder so i can flash it to recovery.
OR have someone manually patch my boot.img file... but i highly doubt i'm going to be able to figure that out or find anyone todo it.
and i'll post the system section of that command in a second.
SoSicWiTiT said:
i found out that my friend installed rom manager n clockwork recovery and did a flash that failed then ran the 2.1 ruu thinking it would fix it. and that's how the phone got to the state i started with.
i actually got a rom to flash (kinda) with some info from that link i posted. i patched my recovery with files from that link which gave it a custom mtd (table) , i shrunk cache and used the extra space to make up for the bad blocks in system and bind mounted cache to and ext partition on my sd card... and all would be great BUT i realized that the boot partition is corrupt too.. ( which makes sense, since clockwork is known to corrupt both)
so my solution was to flash boot.img to recovery and just boot normally with volup+powerand use amon ra by "fastboot boot " if i need to.
but i cant flash the zip file that patches the kernel to boot using the custom mtd because it's script copies,unpacks,patches then repacks boot.img from /boot but my boot.img is on recovery so im either going to have to edit the .sh in the zip or have someone do the whole custom mtd thing and use the same mtdpartmap.txt and have them nandbackup then give me the boot.img from the backup folder so i can flash it to recovery.
OR have someone manually patch my boot.img file... but i highly doubt i'm going to be able to figure that out or find anyone todo it.
and i'll post the system section of that command in a second.
Click to expand...
Click to collapse
I was going to say, holy crap that's a lot of work - but then I've been struggling for a couple hours trying to build mtd-utils (or at least "flash_erase"). I've got all the Makefiles happy (by dropping non-essential parts of the build that require "libuuid"), but now I'm struggling with the linker/toolchain issues to try to avoid the hassles of dynamic link libraries for Amon_RA.
I still think that whatever it is that Clockwork does to get all those flash pages marked as if they are bad is a software error or some sort - so that if you can get
flash_eraseall -N
to do its thing on mtd3, you will recover all those "bad" pages in the system partition. (It is hard to believe that massive physical damage to eeprom would only show up in one or two logical partitions).
Cheers.
bftb0
FWIW,
SoSicWiTiT said:
OR have someone manually patch my boot.img file... but i highly doubt i'm going to be able to figure that out or find anyone todo it.
Click to expand...
Click to collapse
Have a look at this android-dls.com tutorial if you haven't already seen it. Use "split_bootimg.pl" to split apart the boot image into the kernel and compressed ramdisk, and then the ramdisk is just a gzipp'ed "cpio" archive.
The hardest bit about this is finding a verstion of "mkbootimg" - there are some floating around on XDA, or you can build it from the github sources.
It's not too bad, the only secret sauce is the load address for the Eris, which is 0x11200000
This is an excerpt from a shell script I use for repacking boot images - it's the essential part (everything else in the script is just glue).
Code:
mkbootimg --kernel ${_KFIL} --ramdisk new-${_RAMDGZ} --cmdline 'no_console_suspend=1 console=null' --base 0x11200000 --output new-${_BNAM}
i edited the shell script thats supposed to patch it to the best of my abilities (changed all boot.img txt to recovery.img) and it has mkbootimg and everything it needs in the zip, so im going to replace the script in the zip and try flashing it...
and something weird just happened.. i forgot i put boot.img for my rom on /recovery . so in shell just now, i typed reboot recovery expecting amon RA and the phone booted into the os???
even though i patched amon ra with custom mtd to install the rom ( system :300,000 - enough to skip bad blocks, cache: 30,000 ) my boot.img is mtd is set to see 176,000 right?
EDIT
i think i flashed that zip with my version of the script earlier to see what happened and i guess it worked..
Code:
C:\droid\tools>adb shell
sh-3.2# df /system
df /system
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/mtdblock3 307200 229296 77904 75% /system
sh-3.2# df /cache
df /cache
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/mtdblock4 61440 36500 24940 59% /cache
sh-3.2# df /data
df /data
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/mtdblock5 101888 2608 99280 3% /data
sh-3.2#
My userdata.img probably became partially corrupt because I created it with cat while the phone was running, instead of in recovery mode :-(. Due to this, when I flash it, the phone doesn't boot and logs several messages related to not finding things on /data over and over, since it couldn't mount /data.
I can put back an older userdata.img just fine and boot the phone, so my methodology works. I'd guess the new userdata.img isn't entirely rubbish as a hex editor shows data.
Attempts to explore (loop-mount) or unpack (unyaffs) on my laptop or on the Android phone itself have failed without much explanations, for the new image as well as for the (known-good) old image. Notably, running the unyaffs2 coming with the latest yaffs2utils tells me it wants to unpack 147 objects but nothing ever shows up.
How can I recover?
You can also answer at android.stackexchange.com/questions/15592/how-to-recover-a-broken-userdata-img if you like.
Since the ViewPad 7 & Variants forum has not got a Q&A section, then please use this thread for any questions. Please dont open a new thread to ask your question, anyone found doing this will have their thread removed and will be warned.
[ask] Howto update to ice cream sandwich
Help me
I want to update to ice cream viewpad7 shandwich.
What should be prepared?
I would recomend you start HERE, this will provide you with all the info you need.
Youtube has a green line on top of the screen.
Now I am using tentone's CleanView Ice v1.3. When I watch videos (Youtube, PPS, etc.) there is a green line on top of the screen. Can someone help me? I can't post in the developer's section because I am new to this forum.
Edit: Is it caused by the 120 DPI?
Viewpad 7E
I purchased a Viewpad 7e that had to Rom. I managed to installed the Viewsonic rom from the sd card but I cannot install anything other rom or recovery.
I saw on this site, for Viewpad 7, that you could copy Flash_image and CWrecovery.img to the sd card and use Terminal emulator to install the CW recovery but it doesn't work "erro scanning partition: no such file or directory".
Does anyone have an idea how to flash a better recovery or a rom?
Recovery
afitzroy said:
I purchased a Viewpad 7e that had to Rom. I managed to installed the Viewsonic rom from the sd card but I cannot install anything other rom or recovery.
I saw on this site, for Viewpad 7, that you could copy Flash_image and CWrecovery.img to the sd card and use Terminal emulator to install the CW recovery but it doesn't work "erro scanning partition: no such file or directory".
Does anyone have an idea how to flash a better recovery or a rom?
Click to expand...
Click to collapse
Flashed the CW Recovery via Rom Manager, choosing the Mi700 option but it wouldn't work when I tried to reboot into recovery. I just got a message "enter recovery mode". Went down the root (excuse the pun) of trying to install a recovery from SD card via Terminal emulator but got nowhere. In the end, and out of desperation I flashed one of the Hauwei recovery roms via Rom Manager and was suprised when it worked.
Give that a try?
How can I get root access on one viewpad 7X?
Hauwei recovery rom compatibility on Viewpad 7e
modelman1968 said:
Flashed the CW Recovery via Rom Manager, choosing the Mi700 option but it wouldn't work when I tried to reboot into recovery. I just got a message "enter recovery mode". Went down the root (excuse the pun) of trying to install a recovery from SD card via Terminal emulator but got nowhere. In the end, and out of desperation I flashed one of the Hauwei recovery roms via Rom Manager and was suprised when it worked.
Give that a try?
Click to expand...
Click to collapse
sorrry if this is a wrong request, but can you please send me a link of that Hauwei recovery roms. i'm sooo tired of this rom
modelman1968 said:
Flashed the CW Recovery via Rom Manager, choosing the Mi700 option but it wouldn't work when I tried to reboot into recovery. I just got a message "enter recovery mode". Went down the root (excuse the pun) of trying to install a recovery from SD card via Terminal emulator but got nowhere. In the end, and out of desperation I flashed one of the Hauwei recovery roms via Rom Manager and was suprised when it worked.
Give that a try?
Click to expand...
Click to collapse
Someone else could confirm this?
modelman1968 which img file from this list http://www.clockworkmod.com/rommanager did you use??
viewpad e72
Hi, I have a viewpad e72 and I can not get root access ...
has icecreamsandwich 4.0.3, android system recovery e3 ... when I go to android system recovery jumps me the following dialog:
"E: bad arguments bootloader (null)"
"E: unknown volume for path [/ UDisk / factory_update_param.aml]"
"E: can not mount / UDisk / factory_update_param.aml]"
I tried several methods to get root access but none works!
locking the bootloader will not let me get accesoo root?
This tablet has a 1GHz Cortex A9 processor and 1 GB DDR3 RAM
any help is welcome! thanks
using google translator
Small Viewpad 7 issue
Hi there user!
im having small problems with my viewpad 7.
Q:What do i have?
A: A viewpad 7, ( Android 2.2.2) dated: 2010-12-04
Q:What do i want?
A: well basically im trying do upgrade android 2.2.2. to atleast 2.3.7. so i can run some games from the market that it wont play now. ( yes my girlfriend wants to play candy crush but its not compatible)
Qwhat have i already done & Tried?
A: i have followed a guide into rooting my device, this worked like a charm ( sorry link not working)
After that i went one to Flashing ClockworkMod Recovery.
i followed a guide from Theunlockr. com
but before i got there i had to install Android SDK, no problems there whatsoever.
so after i had done all that i downloaded the necessary software ( Flash_image and Cwrecovery )
Usb debugging mode was on and i openend USB Storage to cope/paste the files into root of SDCard(FAT)
i was ready to start Flashing ClockworkMod Recovery on the Viewpad 7
i started by opening C:\android-sdk\platform-tools and shift-rightclick to open command prompt
in there i did the following:
1- i entered ADB by typing in adb shell and hit enter.
2- I typed in su to gain superuser access. ( had to accept on the viewpad 7)
3- after that i typed in cat /proc/mtd
4- than i typed cat /dev/mtd/mtd3 > /sdcard/recovery.img to back everything up, no errors whatsoever
5- after that i had to start flashing with this command:
chmod 755 /system/bin/flash_image
flash_image recovery /sdcard/cwrecovery.imgchmod 755 /system/bin/flash_image
strangly it have me an error: Unable to chmod /system/bin/flash_image: No such file or directory.
after that i got stuck, and i have tried a few things but i cant get it to work. here is a copy of my command promt:
C:\android-sdk\platform-tools>adb shell
$ su
su
# cat /proc/mtd
cat /proc/mtd
dev: size erasesize name
mtd0: 00500000 00020000 "boot"
mtd1: 00200000 00020000 "misc"
mtd2: 00080000 00020000 "splash"
mtd3: 00500000 00020000 "recovery"
mtd4: 00500000 00020000 "ftm"
mtd5: 01a00000 00020000 "hidden"
mtd6: 00060000 00020000 "dbgmsk"
mtd7: 0a000000 00020000 "system"
mtd8: 00200000 00020000 "misc2"
mtd9: 05800000 00020000 "cache"
mtd10: 0ab80000 00020000 "userdata"
# cat /dev/mtd/mtd3 > /sdcard/recovery.img
cat /dev/mtd/mtd3 > /sdcard/recovery.img
# chmod 755 /system/bin/flash_image
flash_image recovery /sdcard/cwrecovery.imgchmod 755 /system/bin/flash_image
Unable to chmod /system/bin/flash_image: No such file or directory
any help would be appriciated,
thanks in advance and have a nice day!
Martijn
how i bootloader my viewbad
hello
i have viewsonic tablet 7 inche
i want bootloader it but there arn't volume bottun in my tablet
so there are any way to bootloader my tab
(there r bower + esc + menu + reset bottun)
usb dongle on 7x
Can I put an usb gsm dongle on a viepad 7x? If yes which models are supported? Thanks in advance
p.s. 7x has not builtin hsdpa , hasn'it?
VB80a
Not sure if its a variant of viewpad 7 or not, but I got this cheap ViewSonic VB80a pro (from dealextreme, SKU: 172665)
1.5GHz dual core, running 4.1.1 (JRO03C) with wlan and bluetooth, using reference board MID design g08refem618 .
Perfect to use in the for OBD interface, but it has some permission issues installing many apps saying it cant be installed on sdcard or usb.
However, this tablet sees the internal memory as an sd card (/storage/sdcard0) and the external sdcard is /storage/sdcard0/external_sdcard.
And those apps can't be installed to what it thinks is external sdcard...
It's an easy fix for the app coder, contacted one of them and got to try a modified package and it installed without a hitch.
But... there are MANY MANY apps that won't install, and asking all of them to re-write their permissions is hardly an option.
So I wanted to root the pad and try some stuff, like symbolic links, to see if that'd work...
I heard DooMLoRD's Easy Rooting Toolkit works on many of these cheap chinese tablets and gave it a go.
After copying the files to /data/local/tmp, chmodding etc, (which worked without any errors btw) it says:
VB80a Pro (JRO03C.eng.wei_song.20121213) is not supported.
You need to manage to get remap_pfn_range addresses.
So I came here trying to get in touch with him but since this is not a general community forum I'm not allowed to post in that thread,
and I hardly think he'll see this message either
But at least other people with this pad can find out why they get this message and can contact the app developer and just hope he's in a good mood...
If anyone find a way to root it without involving too complicated stuff - please let me know!
Cheers
//Greg.
Device: g08refem618
Model: VB80a Pro
Board: g08refem618
Product: g08refem618
Brand: MID
Manufacturer: MID
CPU+ABI: armeabi-v7a
Bootloader: unknown
Radio: unknown (does not have built in sim card slot/function)
Hardware: amlogic
Release: 4.1.1
SDK: 16
Type: user
Build: JRO03C.eng.wei_song.20121213
Locale: en_US
Cherry Mobile Superion TV2 phone & Tablet in one
Hi,
I recently got a hold of a Cherry Mobile dual sim phone & tablet in one from the Philippines and i have been searching for a custom rom for this. I'm not sure if it is a variant of the Viewpad but somewhere in my research I read it was. I have already rooted the device using framaroot. Super user is installed, rom manager installed but could not find any custom roms.
My apologies if this is not the correct forum for this and would appreciate it if someone can point me to the right direction.
Thanks in advance for any help!
Dennis
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
Hey All
I'm new to Android but not linux.
Bought cheap Allwinner type 5.1.1 tablet - 10.6" Fusion5 108 Octa Core Android Tablet PC
rooted it using KingRoot, messed around with Supersume to remove KingRoot and now device won't boot properly. Using adb I can see dmesg is complaining about debuggered which is actually now a zero byte file. su won't work now and I don't have the rights to fix it.
Before I did any of this the first thing I did as root was backup the mmc partitions to a USB stick.
The bootloader and recovery areas have not been changed.
Can I use my system partition backup to create a update.zip for use in recovery mode?
Or maybe in fastboot though I'm currently having problems getting fastboot to see my tablet whether I use linux or windows so recovery mode fix prefered..
lol
Looks like the solution is to post here, and then find a partial answer 5 minutes later.
fastboot command on linux didn't work (despite adb working, udev configured etc)
Then tried with manufacturer id
fastboot -i 0x1f3a
then works
Then did
fastboot -i 0x1f3a erase system
fastboot -i 0x1f3a flash system /home/user/android/13-11-16/system
It complained that about magic so I suspect this DIDN'T work. although data was sent.
fastboot -i 0x1f3a reboot
and device came up in a graphical environment asking for wireless password. Judging by network trace on my router I think it might be trying to download a factory image over the Internet. Will see.
Bit confused as my system parition backup is like 900Mb but when I did flash system I think it said device reported size was 32MB approx. More to learn
OK
The 32Mb was referring to buffer size, so can confirm system flash did work.
Device was booting, getting to graphical environment, and then trying to connect some web servers - not sure why really but seem to have got past that point.
Now can't install apps - get stuff like
W/art ( 9462): Unable to open /data/dalvik-cache/. to delete it's contents: Permission denied
W/art ( 9462): Unable to open /data/dalvik-cache/arm to delete it's contents: Permission denied
W/art ( 9462): Could not create image space with image file '/system/framework/boot.art'. Attempting to fall back to imageless running. Error was: Unable to relocate image '/system/framework/boot.art' from '/system/framework/arm/boot.art' to '/data/dalvik-cache/arm/[email protected]@boot.art': Only the zygote can create the global boot image.
Think /data is corrupt so will flash my backup of that.
I'm more thinking outloud at this point rather than expecting people to do it for me But I'll post anyway if that's ok if only for my own reference - though any insights by all means.
Can't flash data backup.
Ended up with 13Gb file from mmc copy when system was working so after img2img didn't seem to be working used ext2simg on it as it was a ext image.
Created a more reasonable sparse 887335016 file.
fastboot wouldn't flash it though complaining that data partition was unknown. Searching seems to suggest that sometimes the bootloader doesn't know about all partitions (though it does about system which was flashed ok).
Tried playing with other recovery environments. Not willing to flash anything at this point so trying flashboot boot <img>. No luck so far - device just stays on bootloader splash screen. Probably not great that this device is a Allwinner A38 to which there doesn't seem to be huge support at the moment.
Even tried flashboot boot <recovery partition dump> file I made and that doesn't work.
Trimmed the first 0x800 so image starts with kernel code without joy.
A binwalk of the initrd image inside the dump shows a init.recovery.sun8i.rc file, and a default.prop with
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
in init
# Always start adbd on userdebug and eng builds
on property:ro.debuggable=1
write /sys/class/android_usb/android0/enable 1
start adbd
So assuming default.prop is used (I'm still learning) then that's why I can't adb when in recovery mode. Seems stupid to design it that way.
I'm thinking if I can restore data partition it will fix the can't install apps problem, though perhaps the /system part is fundamentally busted. If I can reinstall KingRoot and root again I assume the device will be usable as it would effectively undo my supersume attempt to remove it.
Env partition dump I made used by the bootloader there is
Code:
boot_normal=sunxi_flash read 40007800 boot;boota 40007800 boot
boot_recovery=sunxi_flash read 40007800 recovery;boota 40007800 recovery
Usage:
sunxi_flash read command parmeters :
parmeters 0 : addr to load(hex only)
parmeters 1 : the name of the part to be load
[parmeters 2] : the number of bytes to be load(hex only)
if [parmeters 2] not exist, the number of bytes to be load is the size of the part indecated on partemeter 1
Click to expand...
Click to collapse
So maybe I need to specify the correct memory location when I'm fastboot boot'ing
There's no image type header specifing load address at the start of the recovery part dump I made.
Didn't manage to boot the recovery image - don't know why but a challenge for another day. Would probably be easier with UART access or similar to see what is actually happening.
In the end I mounted my /system backup on my linux server, cleaned it of KingRoot crap, and flashed it. Now everything is fine! Except no root access and the script I added to give me it comes us as unlabeled in selinux and isn't accessible.
The learning journey continues
og0 said:
Didn't manage to boot the recovery image - don't know why but a challenge for another day. Would probably be easier with UART access or similar to see what is actually happening.
In the end I mounted my /system backup on my linux server, cleaned it of KingRoot crap, and flashed it. Now everything is fine! Except no root access and the script I added to give me it comes us as unlabeled in selinux and isn't accessible.
The learning journey continues
Click to expand...
Click to collapse
I know this is a 2 year old thread... but does the OP still have that firmware that fixed the tab??
I have a Fusion5_108 with the A83T allwinner processor, stuck in a boot loop, wont get past the 'no command' screen when trying to recover,
think my only option is to make an sd card with a working firmware on it, and load it onto the devise like that, but i cant find a firmware or anything for this tablet