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#
Hello. At first I want to ask if any of you working on Gingerbread experienced "Force Close" loop on restart for many applications (for repair required format /data backup or restore via CWM)?
I spent a lot of time to get to the source of the problem, because even though the system version of JB's okay, it's GB is more stable and does not eat much RAM, moreover is much better for multitasking in the current situation.
Get to the point. The problem appears to be that from time to time, as in any filesystem, in the user partition (/ data) errors may occur that normally are repaired at boot time by e2fsck program. Moreover, in the case of my own and yet another piece of Samsung I8160 e2fsck is unable to complete repairs due to an error related to the library supports file systems.
When I connect ADB in recovery mode, umount /data and issue the command "e2fsck -y -f /dev/block/mmcblk0p5" the mass of errors are discovered, and repairing starts, but of course does not end well:
Code:
"FILESYSTEM WAS MODIFIED,
invalid argument passed to ext2 library while rewriting block and inode bitmaps "
...which tells that filesystem was modified, but the wrong argument was passed to the filesystem library and the correct structure not been written completely, resulting in an even greater massacre on the partition. It is not difficult to guess that the system will not boot normally (/data mounted in read only mode), and applications will start the "Force close" loop .
The story is not only on my phone, but also in other arts. After formatting it for a few weeks until you see the error and restart. After restoring a backup via CWM has usually only until the next reboot.
Has anyone experienced this? Is anyone able to solve this problem?
I tried stock ROM and kernel, reflashing, substitution of e2fsck binaries and libext2fs libraries. Chip does not have bad blocks, checked by dd command and calculated CRCs.
Please don't reply "do full wipe," not considering myself an Android noob, I want to solve the problem.
Have you ever tried to do filesystem check on Gingerbread and did it work for you? "e2fsck -y -f /dev/block/mmcblk0p5" ?
Can you restart the phone without problem?
Can you try if it works now?
Part of the log with dmesg at boot:
Code:
<4> [10.306152] EXT4-fs warning (device mmcblk0p5): ext4_clear_journal_err: Filesystem error recorded from previous mount: IO failure
<4> [10.306213] EXT4-fs warning (device mmcblk0p5): ext4_clear_journal_err: Marking fs in need of filesystem check.
<4> [10.331756] EXT4-fs (mmcblk0p5): warning: mounting fs with errors, running e2fsck is recommended
============SOLUTION==============
No one in this and general android forum was able to help me. So I had to find solution on my own.
It seems, that CWM 5 (on my 2.3.6 XXLL2 Samsung I8160 kernel) formatting procedure has bugs, and after some restarts, e2fsck tries to repair filesystem, but it can't because of non standard(?) structure on partition.
How to solve this:
Get your own mke2fs binary and boot into CWM, connect ADB and format /data using mke2fs. This works fine with e2fsck. No more this problem, just don't use CWM to format/restore /data, just backup/restore it via dd.
If you want to go back to old good&stable GB on I8160 and need help, write me a PM, I'll send you gtalk/jabber.==
The best way to solve this problem, is to flash a new firmware / ROM and start fresh.
If you need a guide or help, feel free to ask me via PM or leaving a reply below.
Be sure to click dat THANKS button if I helped!
Ronny927 said:
The best way to solve this problem, is to flash a new firmware / ROM and start fresh.
If you need a guide or help, feel free to ask me via PM or leaving a reply below.
Be sure to click dat THANKS button if I helped!
Click to expand...
Click to collapse
If it was so simple, I wouldn't ask it on the main forum.
e2fsck is not able to properly end repairing process because of mentioned error:
Code:
invalid argument passed to ext2 library while rewriting block and inode bitmaps
Reflashing, factory reset DOES NOT help in this situation, because after some time every filesystem has some errors that need to be repaired and this does not work as it should.
I get it now.
Anyone else has any idea how to solve this?
bump
Hey guys,
unfortunately i think i bricked my prime
Today i flashed crombi-kk rom which worked flawlessly fine. I came from HairyBean 2.31 so all i did was to up update my TWRP via fastboot and then flash the rom. As said, that worked fine. After my first boot of the rom i thought that i would like to test the "F2FS" option. For this i updated TWRP to v2.8 via the zip-file from this thread: http://forum.xda-developers.com/showthread.php?t=2772093 . This also worked and i've got my TWRP to the new version.
Now i wanted to format the /data partition to F2FS so i went to
Wipe>>Advanced Wipe>>Choose Data>>Repair or Change File System>>Change File System>>F2FS
At this time it told me that it can't UNmount the partition and therefore it couldn't change the file-system.
Dumb as i am i thought: "Okay, then why don't just unmount the partition" so i did this (Mount>>Disabled "Data") an then retried to format the data partition with f2fs. During this process i have to assume that something went wrong? It gave me some error which i fool can't remember.
From this point i couldn't access the /data partition anymore, i can't mount it nor can i boot into Android.
I still have access to TWRP and can get to fastboot access. I have no ADB Access in TWRP - it just can't recognize the prime. In Windows-Hardware Manager it just says: Transformer?! (i have universal naked driver installed)
Forget the last sentence - it seems that my USB-Cable is partly broken. Sometimes it recognizes the prime and sometimes not!
Is it gone forever or is there still hope to recover it?
Hopefully someone can help me, i'm really desperate
P.S.: D didn't want to make things worse, so i stopped messing around with it - would it help to reflash the ne0zone75_tf300t.blob file? Is this even possible if i already updated the TWRP to a newer version?
NiffStipples said:
I still have access to TWRP and can get to fastboot access.
Click to expand...
Click to collapse
As long as this is the fact, we don' t call it 'bricked'.
Try following one after another:
1. TWRP>>Wipe>>Advanced>>[check / data]>>repair file system, flash ROM again.
2. Fastboot:
Code:
fastboot -i 0x0b05 erase userdata
- then flash ROM again.
3. Last ressort: Flash stock ROM and start from scratch.
... hope you've pulled your nvflash files. Good luck!
... you might also want to flash another TWRP, though ne0zone75's normally works well. Try the official 2.8.3.0 (for tf300t because you are on Hairy Bean), works good with my prime.
Thanks a lot for your reply
I've tried the steps you provided:
1) While repairing the data partition it said again that it can't mount the data partition. (Picture of it in the attachment)
2) Reflasing the rom worked okay but as expected it couldn't boot (stuck in bootscreen) - in TWRP the /data partiton was again unmountable
3) erasing the userdata via fastboot gave me the following:
Code:
erasing 'userdata'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.002s
At this time i didn't tried to reflash the rom because i don't think it would change anything?!
4) i only have the old nvflash files from ages ago when i started flashing with androwook - i fear they are the wrong ones? I don't have any clue what to do with these - are there good instructions to get the tab back to it's factory state?
Last but not least - do you have a link for the right TWRP you're talking about. I don't want to gave the wrong one a try
NiffStipples said:
Thanks a lot for your reply
I've tried the steps you provided:
1) While repairing the data partition it said again that it can't mount the data partition. (Picture of it in the attachment)
2) Reflasing the rom worked okay but as expected it couldn't boot (stuck in bootscreen) - in TWRP the /data partiton was again unmountable
3) erasing the userdata via fastboot gave me the following:
Code:
erasing 'userdata'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.002s
At this time i didn't tried to reflash the rom because i don't think it would change anything?!
Click to expand...
Click to collapse
Sounds as if partition table is faulty.
1. You could try to redo the Hairy Bean procedure.
2. If you feel lucky, then you could try to format partition manually using
Code:
mkfs.ext4 /dev/block/mmcblk0p8
4) i only have the old nvflash files from ages ago when i started flashing with androwook - i fear they are the wrong ones?
Click to expand...
Click to collapse
nvflash files don't grow sour; you could try without changing to wheelie your blob.bin. If it works, you are safe and can continue with the other blobs.
I don't have any clue what to do with these - are there good instructions to get the tab back to it's factory state?
Click to expand...
Click to collapse
Best instruction you find here: http://forum.xda-developers.com/showthread.php?t=1894867
Last but not least - do you have a link for the right TWRP you're talking about. I don't want to gave the wrong one a try
Click to expand...
Click to collapse
I have actually the (official) one from http://www.techerrata.com/browse/twrp2/tf300t
Good Luck!
Okay, now i know why they always say that flashing is nothing for noobs
I'm a little bit confused - what (in your opinion) is the best shot i should give a try?
Formatting manually (from where? In TWRP or via adb? I'm on Windows)
Reflash everything with NVFLASH (is that possible without any hassle - the NVFLASH files are from ICS-times and i'm on JB/KK?!)
I know it's annoying to help someone who doesn't know what he's doing - hope you have time to get me through this flashing nightmare :/
NiffStipples said:
Okay, now i know why they always say that flashing is nothing for noobs
Click to expand...
Click to collapse
Everybody starts as a noob.
I'm a little bit confused - what (in your opinion) is the best shot i should give a try?
Formatting manually (from where? In TWRP or via adb? I'm on Windows)
Click to expand...
Click to collapse
I would first do that manually from TWRP>>Advanced>>Terminal Command>>Select Folder (root)>>type in: mkfs.ext4 /dev/block/mmcblk0p8
Reflash everything with NVFLASH (is that possible without any hassle - the NVFLASH files are from ICS-times and i'm on JB/KK?!)
Click to expand...
Click to collapse
Important is, that blob.bin works with
Code:
wheelie.exe -r --blob blob.bin
After that you should flash 'bricksafeTF201.img' and 'unlock-token-TF201'. Then you can flash any blobs of unblobbed ROMs you can find in the internet or flash stock ROM (JB). Then proceed to fastboot custom recovery and zipflash custom ROM.
I know it's annoying to help someone who doesn't know what he's doing - hope you have time to get me through this flashing nightmare :/
Click to expand...
Click to collapse
I went through any misstep you can think of with the three of 'em: TF201, TF300T, TF700T.
Mmmmh, the command
Code:
mkfs.ext4 /dev/block/mmcblk0p8
gives me back:
Code:
mkfs.ext4: not found
NiffStipples said:
Mmmmh, the command
Code:
mkfs.ext4 /dev/block/mmcblk0p8
gives me back:
Code:
mkfs.ext4: not found
Click to expand...
Click to collapse
Oops! My bad, try
Code:
make_ext4fs /dev/block/mmcblk0p8
.
.... for information's sake type
Code:
fdisk -l /dev/block/mmcblk0p8
You should get
Code:
Disk /dev/block/mmcblk0p8: 29.6 GB, 29618601984 bytes
4 heads, 16 sectors/track, 903888 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Hooray! :victory: Thanks a lot - everything is back where it belongs
Just for the learning effect - do you have any idea what did go wrong in my case and how would i correctly change the format of the data partition to f2fs? I think i've read a lot of times that this would improve rom speeds a lot?!
NiffStipples said:
Hooray! :victory: Thanks a lot - everything is back where it belongs
Just for the learning effect - do you have any idea what did go wrong in my case and how would i correctly change the format of the data partition to f2fs? I think i've read a lot of times that this would improve rom speeds a lot?!
Click to expand...
Click to collapse
Congrats!
If you would care to tell what you did last, one could make a guess, what went wrong.
... and yes, changing /data (only!) to f2fs makes a tremendous difference in speed. Normally TWRP complies the job without probs. What TWRP do you have now?
I prefer @ne0zone75's which I linked some posts before. They work on all my tabs.
I have installed v2.8.3.0 from the site you gave me above
Mh, as said in the first post i did the following steps to change the format
I tried Wipe>>Advanced Wipe>>Checked "Data">>Repair or Change File System>>Change File System>>Choose F2FS
Then the system gave me an error that it couldn't access the partition because it was mounted or couldn't be unmounted or something like this
So i went back to Mount>>unchecked "Data"
And then again to Advanced Wipe>>...>>Change File System>>F2FS
After that something went wrong because after that step i couldn't mount the data partition anymore?!
NiffStipples said:
I have installed v2.8.3.0 from the site you gave me above
Mh, as said in the first post i did the following steps to change the format
I tried Wipe>>Advanced Wipe>>Checked "Data">>Repair or Change File System>>Change File System>>Choose F2FS
Then the system gave me an error that it couldn't access the partition because it was mounted or couldn't be unmounted or something like this
So i went back to Mount>>unchecked "Data"
And then again to Advanced Wipe>>...>>Change File System>>F2FS
After that something went wrong because after that step i couldn't mount the data partition anymore?!
Click to expand...
Click to collapse
Yes, but what did you to fix it then?
Oh sorry, now i get it
I just used your command for repartitioning(?!?): make_ext4fs /dev/block/mmcblk0p8
I am still of two minds of f2fs on these tablets.. Just gone back to ext4 to compare... As was getting to sticky on the F2fs with redraws and lag..
Anyway good to hear a successful conclusion on the come back by the OP
NiffStipples said:
Oh sorry, now i get it
I just used your command for repartitioning(?!?): make_ext4fs /dev/block/mmcblk0p8
Click to expand...
Click to collapse
Good! Glad, it helped you. Now you could try the 'mkfs.f2fs' command also.
Already tried that - this time it worked without problems :highfive:
Thanks again for the great help!! F2FS brings the prime to a whole new level, now i just have to figure out how to change the dock layout language
NiffStipples said:
Already tried that - this time it worked without problems :highfive:
Thanks again for the great help!! F2FS brings the prime to a whole new level, now i just have to figure out how to change the dock layout language
Click to expand...
Click to collapse
That should be no problem. If you click in dock, there should be a keyboard icon in notification area, clicking it settings dialog will appear. Additional in settings>>language and input>>physical keyboard you can set keyboard layout of dock.
das chaos said:
Oops! My bad, try
Code:
make_ext4fs /dev/block/mmcblk0p8
.
.... for information's sake type
Code:
fdisk -l /dev/block/mmcblk0p8
You should get
Code:
Disk /dev/block/mmcblk0p8: 29.6 GB, 29618601984 bytes
4 heads, 16 sectors/track, 903888 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Click to expand...
Click to collapse
DC,
I wonder if this is why my f2fs where playing up for me?
using your commands I get the following..
Code:
[email protected]:/ $ su
[email protected]:/ # fdisk -l /dev/block/mmcblk0p8
Disk /dev/block/mmcblk0p8: 29.6 GB, 29618601984 bytes
4 heads, 16 sectors/track, 903888 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p8 doesn't contain a valid partition table
[email protected]:/ #
Disk /dev/block/mmcblk0p8 doesn't contain a valid partition table
this is what I am looking at as a problem maybe?
is there a terminal command to see all the partitions and sizes?
I might have to take this thing back to scratch and start again as been flashing left right and center on it of late.
dgcruzing said:
DC,
I wonder if this is why my f2fs where playing up for me?
using your commands I get the following..
Code:
[email protected]:/ $ su
[email protected]:/ # fdisk -l /dev/block/mmcblk0p8
Disk /dev/block/mmcblk0p8: 29.6 GB, 29618601984 bytes
4 heads, 16 sectors/track, 903888 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p8 doesn't contain a valid partition table
[email protected]:/ #
Disk /dev/block/mmcblk0p8 doesn't contain a valid partition table
this is what I am looking at as a problem maybe?
is there a terminal command to see all the partitions and sizes?
I might have to take this thing back to scratch and start again as been flashing left right and center on it of late.
Click to expand...
Click to collapse
No that's normal for f2fs, only fat systems have readable PT. What I was interested was geometry of fs and that is the same as mine. So everything is o.k. You have your tab up and running - that counts.
There is a free app Storage Partitions in the store, which can do no more than show information about partitions. Mainly an exploit of commands
Code:
cat /proc/mounts
and
Code:
cat /proc/partitions
das chaos said:
No that's normal for f2fs, only fat systems have readable PT. What I was interested was geometry of fs and that is the same as mine. So everything is o.k. You have your tab up and running - that counts.
There is a free app Storage Partitions in the store, which can do no more than show information about partitions. Mainly an exploit of commands
Code:
cat /proc/mounts
and
Code:
cat /proc/partitions
Click to expand...
Click to collapse
Used that one and another to have a look..
This is what I get, just for the hell of it..
As said for me.. F2Fs on this one doesn't play nice and the last few days I am back to Ext4..
Running it in and let it settled, putting it through its paces with plenty of tabs in chrome open and multitasking back and forwards in to Tapatalk and it runs normal with out lag and redraws..
I am using apex as a launcher and under F2Fs with kept in memory set..it was redrawing to the max and timing out from coming out of sleep..
Playing with other tweaks to see if can get it to a sweet spot.
Will let it settle for a few days and play then swop back and see which is better with the tweaks added
Phone is Elephone P7000, I can flash various stock roms and custom to it, doesn't boot into recovery unless I use CWM, which I can boot into and connect via adb.
Chip is MT6752, I've never flashed over bootloader or userdata, just the rest. Got it working a couple times, with different roms though would freeze after a while or a x has stopped working (I've had this phone since it was released and never updated the stock rom - I got the x has stopped working error before ever flashing anything and it got stuck in a boot loop after that), resetting stuck in boot loop, haven't got it working since then despite multiple flashing attempts. I have not tried firmware upgrade with SP Tool since that does the whole lot also haven't tried formatting.
Typically rebooting from CWM would help (just regular, not into fastboot), but to no avail anymore.
Memory Test on sptool passed everything except for nand flash which says it was not found.
in adb shell frompc via CWM recovery running.
fdisk -l /dev/block/mmcblk0
fdisk: can't open '/dev/blockmmcblk0': I/O error
obviously mmcblk1 (the external SD card) works just fine.
parted /dev/block/mmcblk0 print
Error: /dev/block/mmcblk0: unrecognised disk label
Again mmcblk1 will be fine.
It shows up using cat /proc/partitions
major minor #blocks name
179 0 15267840 mmcblk0
e2fsck /dev/block/mmcblk0
e2fsck: Attempt to read block from filesystem resulted in short read while trying to open /dev/block/mmcblk0
Could this be a zero-length partition?
C:\adb>adb shell
~ # mke2fs -n /dev/block/mmcblk0
mke2fs -n /dev/block/mmcblk0
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
954720 inodes, 3816960 blocks
190848 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=3909091328
117 block groups
32768 blocks per group, 32768 fragments per group
8160 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208
~
Is there any chance of repairing this partition with a tool like you can on a PC?
Otherwise what should I do from here?
Athiril said:
Phone is Elephone P7000, I can flash various stock roms and custom to it, doesn't boot into recovery unless I use CWM, which I can boot into and connect via adb.
Chip is MT6752, I've never flashed over bootloader or userdata, just the rest. Got it working a couple times, with different roms though would freeze after a while or a x has stopped working (I've had this phone since it was released and never updated the stock rom - I got the x has stopped working error before ever flashing anything and it got stuck in a boot loop after that), resetting stuck in boot loop, haven't got it working since then despite multiple flashing attempts. I have not tried firmware upgrade with SP Tool since that does the whole lot also haven't tried formatting.
Typically rebooting from CWM would help (just regular, not into fastboot), but to no avail anymore.
Memory Test on sptool passed everything except for nand flash which says it was not found.
in adb shell frompc via CWM recovery running.
fdisk -l /dev/block/mmcblk0
fdisk: can't open '/dev/blockmmcblk0': I/O error
obviously mmcblk1 (the external SD card) works just fine.
parted /dev/block/mmcblk0 print
Error: /dev/block/mmcblk0: unrecognised disk label
Again mmcblk1 will be fine.kcuf
It shows up using cat /proc/partitions
major minor #blocks name
179 0 15267840 mmcblk0
Is there any chance of repairing this partition with a tool like you can on a PC?
Otherwise what should I do from here?
Click to expand...
Click to collapse
Ok bro heres how to repair your phone.You need a firmware image of your device and you need some way to flash it.Google
"your device" firmware then download and flash it.Everything will be repaired and your device will be in working order.
boyam99 said:
Ok bro heres how to repair your phone.You need a firmware image of your device and you need some way to flash it.Google
"your device" firmware then download and flash it.Everything will be repaired and your device will be in working order.
Click to expand...
Click to collapse
I'm not sure if you read what I've written, I've reflashed the phone repeatedly, apart from the preloader since that could be disastrous, and userdata partitions.
Anyone else reading: I want to try parted mklabel to give it a new label, but not sure what label to give it, and then try resuce under parted.
Athiril said:
I'm not sure if you read what I've written, I've reflashed the phone repeatedly, apart from the preloader since that could be disastrous, and userdata partitions.
Anyone else reading: I want to try parted mklabel to give it a new label, but not sure what label to give it, and then try resuce under parted.
Click to expand...
Click to collapse
hey am trying to help you dont say am not helping
---------- Post added at 08:39 AM ---------- Previous post was at 08:30 AM ----------
Athiril said:
I'm not sure if you read what I've written, I've reflashed the phone repeatedly, apart from the preloader since that could be disastrous, and userdata partitions.
Anyone else reading: I want to try parted mklabel to give it a new label, but not sure what label to give it, and then try resuce under parted.
Click to expand...
Click to collapse
do u have a backup of your device.If the stock rom isnt working its either a software problem or its the phone
---------- Post added at 08:39 AM ---------- Previous post was at 08:39 AM ----------
Athiril said:
I'm not sure if you read what I've written, I've reflashed the phone repeatedly, apart from the preloader since that could be disastrous, and userdata partitions.
Anyone else reading: I want to try parted mklabel to give it a new label, but not sure what label to give it, and then try resuce under parted.
Click to expand...
Click to collapse
do u have a backup of your device.If the stock rom isnt working its either a software problem or its the phone
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