So I posted this already overhere -> HERE but its in the wrong forum, and I quickly saw the topic go to the back of the board ...
Seeing how it really should have been here, I'll try again.
Just a quick recap:
I'm trying to port the Honeycomb 3.1 SDK to my Archos 7HTv2. I messed with the boot.img and system.img from the SDK and put it in my update.img. I tried to flash it, and it works for a little, then it complains about running out of space.
Code:
Writing KERNEL:...
Checking KERNEL:...
Writing BOOT:...
Checking BOOT:...
Writing SYSTEM:...
E:Write failed(No space left on device)
E:Failure at line 16:
write_image PACKAGE:system SYSTEM:
Update failed, please reboot and update again!
The system.img for the HC rom is ~112mbs, the total update.img is ~123mbs
The system.img for the stock rom is ~51mbs the total update.img is ~54mbs
The stock system is 200mbs, so it should work. I don't really know where to go from here. I'll keep messing with it but I'd like a point in the right direction. I changed the partition information in the HWDEF and PARAMETER file, and got the same error. More info what I did in the link.
BTW i know that it may not boot, but now I just want it to flash.
Found some stuff about custom partition layouts Here & Here so checking it out. Though not really sure if this is the problem or not.
Related
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.
I was given an AC100 by a friend who didn't want it running on Android at all, with the task of wiping it and installing ubuntu. Figuring I didn't need the Android partitions I followed to the letter this guide to get back the internal memory occupied by the unneeded partitions. I did make a full backup before this, according to these instructions; this includes the partition table (converted to cfg) and bct file.
Here is my repartition script, edited with the appropriate .cfg file name (the cfg is the same you find on the repartition guide, only there it's called part.cfg) and location of the nvflash and bin files: http://pastebin.com/DLB8h6tC
And here is the console output: http://pastebin.com/5QyRfrjy
At this point it dumps me back to the console. I tried uploading fastboot again manually to regain control of the AC100 and either resume the process or restore the full backup and start from scratch, but this happens: http://pastebin.com/SjbffjCc
I can't figure out what caused the script to fail; from what I can see all the files are where they should be. What do I do now? How do I regain control of it so I can at least do a full backup?
Edit: SOLVED IT. Nvflash fails if /usr/lib/nvflash/fastboot.bin is not copied to the work folder before running it. Not sure why this is, but thanks to the #ac100 IRC channel for pointing this out to me. Manually running the steps in the script from the one that failed onward repartitioned correctly, and now the bootloader runs.
Ye olde bumpe. The poor thing is looking at me and I think I can hear it screaming for help.
Another bump. I still haven't figured out how to fix it.
Hello everyone, i recently purchased one of these from newegg at a reasonable price, but I can't seem to find rom's for them anywhere. Does anyone have any ideas on where to look, i've been hunting on google for hours. It's currently running 4.2.2
Kernel 3.0.36+
Firmware: CT9706_RK610
Im not sure what else to do. I would hate to have to stick with stock considering it's a little laggy with the junk that they piled onto it. Not to mention i know it has the chinese OS installed on it. Luckily i WAS able to root it, and even get cwm installed on it, but i have no rom to flash to it as of yet. Any help is appreciated, thanks!
Soft Bricked Taipad 10s
I have this tablet, and was able to root it, and all was fine until I realized that it was not utilizing the Nandflash. The internal storage was full, and the Nand was empty (ish). SO i decided (as a newb) to pull the boot.img, edit the init.rk3066.rc and attempt to re-route the emulated storage to /mnt/sdcard. Recreated the new_boot.img, and pushed it and cat to mtdblock2 as i got it..(correct base address) - and reboot takes it to recovery. over and over.
I am looking for a rom that will work, from what i find CWR and CWM are a no go due to stopped development, but im still searching. There must be a similar tablet somewhere.
Oh and b4 the softbrick i used to get adb shell cmd line "[email protected] #" or something like that - now i only get "#" - so i could not cat the original boot.img - yay fail.
Adulator12 said:
I have this tablet, and was able to root it, and all was fine until I realized that it was not utilizing the Nandflash. The internal storage was full, and the Nand was empty (ish). SO i decided (as a newb) to pull the boot.img, edit the init.rk3066.rc and attempt to re-route the emulated storage to /mnt/sdcard. Recreated the new_boot.img, and pushed it and cat to mtdblock2 as i got it..(correct base address) - and reboot takes it to recovery. over and over.
I am looking for a rom that will work, from what i find CWR and CWM are a no go due to stopped development, but im still searching. There must be a similar tablet somewhere.
Oh and b4 the softbrick i used to get adb shell cmd line "[email protected] #" or something like that - now i only get "#" - so i could not cat the original boot.img - yay fail.
Click to expand...
Click to collapse
hi... i have a taipd 9x- but i had a mistake.. and i dont have rom files and im stuck!!.. my android os does not work.. and i need the files to make it work the touch and wi fi hardware..can you help me how to do or find that rom file?
MAXIMAURO said:
hi... i have a taipd 9x- but i had a mistake.. and i dont have rom files and im stuck!!.. my android os does not work.. and i need the files to make it work the touch and wi fi hardware..can you help me how to do or find that rom file?
Click to expand...
Click to collapse
Do either of you still have the original firmware for the Taipad 9X? I've essentially bricked mine by loading an incompatible firmware and would love to get back to the original.
I'd be willing to pay a small fee to get it.
Short story. Bought a local cheap china tablet based on MTK6852 chipset with 8GB internal storage, running KitKat 4.4.2, but only 500MB available for apps. Being a complete android noob, but a savvy computer guy, started investigating and playing with link2sd, which did not work. Eventually found out I can simply edit EBR1 and EBR2 and that will increase internal storage to ~4G which would be great. Again, being an android noob, I installed droid tools for MKT, did a scatter backup and a whole system backup.
then, just when I was about to manually edit EBR files, I discovered this app: youtube video id: V9aFPNcwajw (sorry as I a new poster I am unable to post outer links) Being super happy about it and forgot to read comments I just went to run it. It failed. Later I discovered its only for MTK6577 devices and it most likely messed up my EBR.
Now I am stucked; I cen get into recovery mode, but factory reset does not work, leading into "mount /data error force format /data" error (my guess is because my EBR is messed up recovery cannot find /data folder?). SP flash tools worked and I have downloaded a couple of different EBR files, but none worked.
The biggest problem: my recovery seems to be incorrect, no idea why thou. All I see is: firmware.info mount.info, phone.info, scatter.txt file and a big "system" folder. Now to do a SP flash tools ready file I would have to select "prepare blocks for flash" in the MTK droid tools, but that requires "files.md5" file, which I dont have (again, no idea why not as I've done a complete backup from same droid tools, unless I forgot to thick something?)
Also the company that makes this tables, actually brands them, refuses to send me any files and wants me to bring in the tablet.
Is there anything else I can do on my own or its time for repair service? My guess is I cant do much without EBR files, but have no idea where to find the correct ones as this is a small country based company and I have yet not found under what other brands it is sold.
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