The Afterlife6.0 was said to be compatible with my Nitro 401D which has the aame MTK no.
However, whenever I try to flash it (using cwm) it says installation aborted. It doesnt say any status about it eg Status 6 or Status 7 but i still used the fix for one which is trying to change the name in the updater script to fit the name of my phone but when I looked, it doesnt have that particular line for checking the name. And the other one was changing the directory of the lines in it but I didnt want to change it because i wasnt so sure about the directories myself.
Ive tried downloading from another source, still didnt work. Now Im wondering maybe its my phone so Ive been considering using SP flash to force it in(? Im still not quite sure what it does tho) and also change my custom recovery (currently cwm) to twrp or ctr. Maybe my phone cant flash anything at all so ive been also considering trying to flash a small file or like a test rom, are there any of those?
What should I do next? Im scared of forcing it in causr it says that if the phone has the wrong preloader my phone can never be recovered..
rexel325 said:
The Afterlife6.0 was said to be compatible with my Nitro 401D which has the aame MTK no.
However, whenever I try to flash it (using cwm) it says installation aborted. It doesnt say any status about it eg Status 6 or Status 7 but i still used the fix for one which is trying to change the name in the updater script to fit the name of my phone but when I looked, it doesnt have that particular line for checking the name. And the other one was changing the directory of the lines in it but I didnt want to change it because i wasnt so sure about the directories myself.
Ive tried downloading from another source, still didnt work. Now Im wondering maybe its my phone so Ive been considering using SP flash to force it in(? Im still not quite sure what it does tho) and also change my custom recovery (currently cwm) to twrp or ctr. Maybe my phone cant flash anything at all so ive been also considering trying to flash a small file or like a test rom, are there any of those?
What should I do next? Im scared of forcing it in causr it says that if the phone has the wrong preloader my phone can never be recovered..
Click to expand...
Click to collapse
Your Device name and SOC?
MTKcROM said:
Your Device name and SOC?
Click to expand...
Click to collapse
My device name is Arc Mobile Nitro 401D but I dont know what SOC means (system on a chip if i guessed right) and or what it refers to but if it refers to the MtkXXXX then its mtk6572
rexel325 said:
My device name is Arc Mobile Nitro 401D but I dont know what SOC means (system on a chip if i guessed right) and or what it refers to but if it refers to the MtkXXXX then its mtk6572
Click to expand...
Click to collapse
Do you install CWM successfully? Did you try another custom rom?
MTKcROM said:
Do you install CWM successfully? Did you try another custom rom?
Click to expand...
Click to collapse
From everything I have done on trying to root this phone, I guess MTKdroid tools installed CWM in the process. It is rooted now tho, checked with rootchecker basic. I havent tried any other roms since Afterlife 6.0 is the only one i found.
UPDATE:
Apparently, the CWM wasn't properly installed, my bad :crying:
I tried to install another ROM like Lollifox (will try MIUI later, still downloading) but I don't think I ported it successfully tho because it just showed installation aborted, no Status whatsoever.
I have now flashed Afterlife6.0. However, its now stuck at boot but a while ago it was on boot loop but after wiping caches and doing a hard reset, its now on boot forever. By boot I mean it just shows the Sony logo (supposedly the Arc Mobile logo before I flashed the rom) then the logo disappears and then its just a black screen (a black screen as in its still turned on and not a black screen as you would see when a phone is off).
I'll try to flash my stock rom and root it again so that I could flash other roms for now while waiting for your reply.
try stock rom on the official site. than try to update cwm and try rooting again.
I already fixed it by flashing the stock tho so no worries I guess.
I successfully ported Lollifox but I encountered a problem where I couldn't save anything because my phone doesn't recognize my SD card. It can be seen in the settings/storage though but what the rom can't do is recognize that the "SD card" is internal not external. Its sort of hard to explain, I have 2 storages: Internal memory and Phone storage. The internal memory is the default place where apps go while the Phone storage acts like the SD card of this phone but its internal as well ( at least that's how it acts on the stock ROM). I tried unmounting it (apparently I have that option on Lollifox but its internal so I don't know how that's possible) and remounting it but no dice. Also, since it doesn't recognize the SD card, it kind of explains why there's no USB mass storage option when I connect it.
I tried to port the MIUI and did the 2 ways of porting it told in the site where the rom came from but whenever I flash it, it boots up and gets stuck at the logo of MIUI.
I'm leaning away from Afterlife 6.0 now cause I can't really see it would be a better ROM (and you got to give it that the themes of MIUI and Lollifox are pretty AF) but I think its more suitable (still can't flash it tho) . Can anyone give thoughts on the best rom for this or a fix for these problems?
rexel325 said:
sometimes you need to format the phone memory at the beginning for one time after you install new ROM. Try that and restart the phone. One time i did this like this problem. Sorry for my english.
Click to expand...
Click to collapse
Solved
I think I already solved my own problem though. I just had to do a few tweaks and do a little bit of trial and error myself. However, I still couldn't flash Afterlife (also tried porting it myself and Im suppose to do a logcat or something but I lack free time) but I still have a rom flashed don't worry. Kind of feel sorry it feels like a waste of a thread.
Now Im asking for this thread to be closed(or atleast I think thats how it works cause I dont seem to have that option myself)
Thank you
Related
Hey guys,
I have a problem, which i couldn't solve using the search. Sorry if i was too stupid to search at all
The thing is this:
I have a Nexus S I9020T which i bought as "broken"
It is stuck at the Google logo with the open lock. I thought i could save that device easily but i can't get that thing to work again.
At first: I still have my first android phone here: a Milestone. I had it for a year now and i would say that i flashed pretty much everything to that device. So i know a thing or two about android and flashing. But i have never had a nexus s in my hands before.
So i did this:
I Opened the Bootloader -> success
I flashed a few different CWM recovery -> also no problem here
I flashed a SU_2.3.6.1 which was already on the sdcard and it flashed without an error
I tried to delete all the files of the previous uswer -> at first I could delete all but as soon as i unmount and mount the usb storage, everything is back to the way it was. Means I can't delete or write anything onto the sdcard
Sometimes i have luck and i can write a .zip file to the card but as soon as I try to flash the ROM CWM says : e:can't open /sdcard/***.zip (bad)
so i know, that sometimes the zip files is just... bad. So i downloaded at least 10 different roms. Always the same problem.
I can'T format the SDcard, at every new mount, everything is back to how it was when i got the phone.
I tried to flash with Odin. But the only thing that changed was that i lost the recovery. So i flashed it new and here i am still stuck with that thing
Odin gets stuck while flashing with som PK[][][] thing -> screenshot. Doesn't seem to get further.. so flashin failed... any ideas?
So my question is:
Is there a problem with the SD card?
Is there just a problem with drivers?
Can My Phone be repaired?
Please you guys help me with your knowledge.
I am living in germany and the nexus is bought in the USW at bestbuy in december 2010. Does someone know how the warranty thing is handled for such a scenario?
Thanks a lot guys for even reading my problem.
Help.
I completely screwed up but do not know where.
Had problems rooting but eventually made it with 'Automatic-Root-Enabler--U8510--v1.1' which worked first time.
Then used rom manager to install HuaweiU8510.zip which did not work so tried U8500_Huaweid.zip.
cache and Delvic cleared, rebooted and red huawei came on screen and there it stayed.
Removed battery, boot into recovery went into firmware update(image in dload but cant remember name) starts step 1 unpacking get yellow triangle with ! and says update failed. also tried again with zip files on sd card but back to red Huawei
Any one got any ideas please as I can get to the sd card but not to the internal memory and not adb/fastboot. So no way of getting a new recovery image into dload
Keith
Here in the netherlands there are no huawei phones too bad because on the wmc they announced some pretty good phones ..
But on topic...
Does your phone still start normal?
If not try flashing it back to stock firmware..
Maybe it's a problem with the custom rom...
Sarvesh50 said:
Here in the netherlands there are no huawei phones too bad because on the wmc they announced some pretty good phones ..
But on topic...
Does your phone still start normal?
If not try flashing it back to stock firmware..
Maybe it's a problem with the custom rom...
Click to expand...
Click to collapse
Thanks
1. no
2. trying once I get original rom
3. Funny it is every one I tried
Keith
I do own a galaxy s...
Once i had a similar problem...
It was caused by the filesystem
Samsung uses the rfs system but custom roms prefer ext4 which is better...
When your filesystem isn't compatible with your custom rom than you will have a startup problem so try to figure out if you have to change the filesystem.
can't post links from other sites cause i am a newby to xda forums this is really annoying
Check this
http://forum.xda-developers.com/archive/index.php/t-1200195.html
There's been some discussion recently of the leaked ICS ROM for the Lenovo A1, which is a little difficult to install, because Clockworkmod won't flash it due to failed assertions. I've modified it so that it can be flashed through CWM.
Be warned that it will overwrite U-Boot, the kernel, and the RAMdisk (these are not usually backed up by CWM 5.0.2.7). If you've installed it, and you want to go back to your old backup (very likely as you'll soon get tired of nothing working properly), use the following steps:
1. Boot into recovery
2. Restore your backup using the normal CWM functionality
3. Install ub-fastboot.zip from this post.
4. Reboot into fastboot mode and restore the correct kernel and ramdisk for your ROM with:
Code:
fastboot flash inand-kernel <kernel>
fastboot flash inand-ramdisk <ramdisk>
5. Reboot.
If you don't know what the correct kernel/ramdisk is for your ROM then I'd advise you not to try using this ROM.
DISCLAIMER
There is no guarantee of anything going right if you install this ROM. I'll try and help with problems (and I'm sure other people will too) but if things get messed up it'll be your fault. Don't take the risk without understanding it and being comfortable with it.
Download: here.
So now you've flashed ICS to your A1, but you can't use it. Duh. Everything is broken right now.
For those scared of using ADB commands during a restore to CM7/Stock gingerbread... Here's the stock RAMDISKS, and Kernel as CWM .Zips... [Links taken from the other A1 threads, stock kernel .zip by yours truly. ;-) ] Flash ONLY the ones you need before you flash your Stock rom/CM7 rom/nandroid restore. In this order.
ROW 2375 / ROW 2525 builds ONLY RAMDISK
(1.){^^vv If you don't know which you're supposed to have, DO RESEARCH FIRST
ROW 2643 build only RAMDISK
(2.)Stock Kernel
(3.) Then Stock ROM/CM7 ROM (your choice) (skip step 2 if flashing a 4/28 or later CM7 build it includes a kernel.)
(4.)Fastboot bootloader mod
Click to expand...
Click to collapse
_________________________________________________________________________________________
Now if only we could get Wifi and USB working... That would be a decent start...
Weird part is, on the leaked one, the device name under settings is "Zoom2"
(haven't flashed this one yet, but I assume it's the same)
Makes me wonder if this is infact the real deal... or at least an attempt by a third party? (see post below)
Though it's nice to see it being possible.
monsieurtalbot said:
Weird part is, on the leaked one, the device name under settings is "xoom2"
(haven't flashed this one yet, but I assume it's the same)
Makes me wonder if this is infact the real deal... or at least an attempt by a third party?
Click to expand...
Click to collapse
It says "Zoom2" - that's an OMAP3 development kit that the hardware in the A1 is very similar to - they'll have started with the device-specific files for the Zoom2, and haven't bothered to change them yet. See http://www.omapworld.com/zoom.html
gmarkall said:
It says "Zoom2" - that's an OMAP3 development kit that the hardware in the A1 is very similar to - they'll have started with the device-specific files for the Zoom2, and haven't bothered to change them yet. See http://www.omapworld.com/zoom.html
Click to expand...
Click to collapse
...That explains it. haha "xoom". Typo. :-/
How to fix Wi-fi
Wi-fi work= ICS for daily use
dawkon13 said:
How to fix Wi-fi
Wi-fi work= ICS for daily use
Click to expand...
Click to collapse
It's not worth trying to fix with this ROM. It'd be better to work on a proper build of ICS instead of wasting time augmenting this early build.
Anyone trying this rom - can you take a look if /proc/config.gz exist and if so - make an upload. I'm just curious, but don't want to waste my time ....
Dear gmarkall, i flashed from CWM and it says installation aborted.. ! now i can't boot up to normal stock ROM ..
it stops in lenovo logo.. Pls ..
Tint Ag Khaing said:
Dear gmarkall, i flashed from CWM and it says installation aborted.. ! now i can't boot up to normal stock ROM ..
it stops in lenovo logo.. Pls ..
Click to expand...
Click to collapse
If you can still boot into recovery, flash an OTA zip file.
If you can't, then follow these instructions.
Brancaleone said:
Anyone trying this rom - can you take a look if /proc/config.gz exist and if so - make an upload. I'm just curious, but don't want to waste my time ....
Click to expand...
Click to collapse
I'm not running the ROM right now, but I tried extract-ikconfig on the kernel and it didn't find a config - I don't know how reliable that tool is though, since I've never used it before.
An update for the ICS ROM was posted in a German forum. Wifi is said to be working now. You can download it here. To use it, you need to flash the original ICS firmware (A107_.rar) and then install the update.zip with the stock recovery from an external sd card.
I've tested the update on my device. Wifi and sound output are working now. The build props show a Lenovo device now (ro.build.fingerprint=Lenovo/IdeaTab_A1107/A1107:4.0.4/MR1/eng.user.20120503.193509:eng/test-keys). The main issue seems to be that the Google Apps are not working (including Play).
EDIT: The problem with Google Play seems to be caused by the file permissions of drmserver. After this, I can download apps from Play Store (but only until rebooting):
Code:
adb remount
chmod 777 /system/bin/drmserver
./system/bin/drmserver&
Confirmed wifi works and sound works fine.
Google store not so much but looks to be a quick fix.
Gps seems to be working but haven't had time to test.
Mounting sd card and usb mounting are messed up.
Also for anyone considering this 4.03 they should know its based on a phones os and not a tablet os.
I can't update on 2GB A1 - there is an error in the middle of process.
The first version was running ok.
Pls!
Dear gmarkall,
I redownloaded and flashed again and now it's running OK.
Now from the above posts, i see that an update that fixes wifi and sound 's available to download again here.https://skydrive.live.com/?cid=56E49CF4B3C46641&id=56E49CF4B3C46641!106&action=Download
So pls tell me what i've to do again. Can i flash this update from CWM ?
Thanks !
Plaease help! Not work on IdeaPad A1 2GB
CWM log:
size:3833856assert failed: run_program("/tmp/fuse:, "mbr", "/tmp/mbr2GB.img")
E;Error in /sdcard/update.zip
(status 7)
Installation aborted
Can you help me?
This Update doesn't work with cwm and I wouldn't recommend to anyone flashing it. It screwed up my whole file system including rescue partition and took me several hours to get rid of it. On top, it doesn't contain config.gz.
If you are using CWM, you can go back to stock recovery in just a few minutes. It is described here. This shouldn't be an issue?
Clearly this is not a actually preview from lenovo but rather a home-brew that does a decent job of getting many things working.
The first preview had a tablet based 4.03 and this supposed update has a phone 4.03 layout.
Still not bad just not from lenovo.
Hi all. Tried my first root + custom rom installation and i messed up the device..
i had the newest KIES firmware update (phone XXBMA5) and (XXBMA6) and i rooted the device with odin (3.07). That went OK.
Then i installed the CWM recovery with odin and that was OK too.
Then i downloaded the latest Omega Rom (i missread that it supports N8020) and followed the installation instructions to the point where it started installing Omega V2.0 from SDCARD and then it asked me to select device from a list that included only (N8000,N8010,N8013)..
So the situation now is that i have working odin, working CWM and backup of the EFS (img+tar) but no working recovery. i live in Finland and the device is Sonera locked i think, so the stock roms (international) do not work i guess.
KIES has a backup of my Note but i can't even get to a point where KIES discovers the device.
So basically i think i need a working ROM for my model (Note 10.1 4G N8020), or can i recover the original samsung software somehow ?
Any advices ?
Removed
Just a thought, but can't you reflash CWM or the stock recovery?
If you didn't install the rom why do you need to re-install anything. Just powering down and powering up should have left you as was....
Alajarvi84 said:
working CWM .......... but no working recovery.
Click to expand...
Click to collapse
Maybe i'm missing something but isn't CWM your custom recovery?
It doesn't sound like you've actually installed any rom yet.The Omega installer doesn't actually install anything until a few steps after the one you mentioned about the model type.
I'm with ultramag69 on this one. You should still be on a stock rom unless you already wiped your original rom.
Hi again. Problem solved, just had to do emergency thing from KIES. Like i said this was the first time trying root + custom ro install and to be honest it went to ****. Somehow i managed to delete the stock firmware so that is why the recovery gave me (no files). I did make some backup but when tried to restore it said MD5 mismatch or something. At first the KIES emergency recovery could not find the device, but after i switched from CWMcto stock recovery it worked.
So what did i learn from all this ? Nothing, because i am getting too old (tired+lazy ) to do proper investigation. So one could say my strategy is to bang my head to the wall as long as it takes to go trough. Even if i could just go around it
So basically i am now at the point where i started, with stock 4.1.2 rooted. Used the triangle away to wipe the (6) custom installs or something away, but it still says custom in the settings> information. Does this mean that OTA won't work ? Any way around it ? Because i would like to check now and then that is my version of android the newest one..
Could someone recommend a custom ROM for my Note 10.1 4G (LTE) N8020 4.1.2 because the only one i was able to find was the CyanogenMod (or something) and it basically makes the S-Pen (almost) useless. What i would like is the Omega ROM, but like stated before the installation only supported N8000, N8010 & N8013...
Added screenshot from info.
Thanks anyway
What is truly amazing is that i did not brick the device tough..
switch from cwm to stock
Alajarvi84 said:
Hi again. Problem solved, just had to do emergency thing from KIES. Like i said this was the first time trying root + custom ro install and to be honest it went to ****. Somehow i managed to delete the stock firmware so that is why the recovery gave me (no files). I did make some backup but when tried to restore it said MD5 mismatch or something. At first the KIES emergency recovery could not find the device, but after i switched from CWMcto stock recovery it worked.
So what did i learn from all this ? Nothing, because i am getting too old (tired+lazy ) to do proper investigation. So one could say my strategy is to bang my head to the wall as long as it takes to go trough. Even if i could just go around it
So basically i am now at the point where i started, with stock 4.1.2 rooted. Used the triangle away to wipe the (6) custom installs or something away, but it still says custom in the settings> information. Does this mean that OTA won't work ? Any way around it ? Because i would like to check now and then that is my version of android the newest one..
Could someone recommend a custom ROM for my Note 10.1 4G (LTE) N8020 4.1.2 because the only one i was able to find was the CyanogenMod (or something) and it basically makes the S-Pen (almost) useless. What i would like is the Omega ROM, but like stated before the installation only supported N8000, N8010 & N8013...
Added screenshot from info.
Thanks anyway
Click to expand...
Click to collapse
How did you switch from CWM to stock? I have having a problem syncing with kies also using omega rom on n8013.
jjndimp said:
How did you switch from CWM to stock? I have having a problem syncing with kies also using omega rom on n8013.
Click to expand...
Click to collapse
I was not easy, i just tried the download mode over and over again with KIES open in windows and somehow it finally did find my device and offered a emergency restore. That is it, and the device was restored to default "original state".
OMG.... one would think after nearly having bricked your device you would either A) stop messing around with it or, B) read and learn more about what you're wanting to achieve and THEN maybe trying something with the ABSOLUTE certainty that a backup to restore is available to you in case of any mishap!
Moral of story :
Don't do anything until you are absolutely sure you have read EVERYTHING about what you are going to do.
For others wanting to mess with their devices, take heed! You may not be as lucky as OP (or troller) whichever is applicable.
There comes a certain point, that when crossed one does not care what happens to the device at hand. After fighting with my n8020 for several days in a row i couldn't care less, and like said before i dont have the level of enhusiasm like i had when i was younger. Of course i know now what went wrong.. But seriously, these are just overpriced toys, so it's not a matter of life and death.
Sent from my GT-N8020 using XDA Premium HD app
Hey gang, I got this Flytouch 8 tablet last week, model number is BC1003, android version 4.0.4, baseband version 1.5rc4, kernel version 3.0.8+ [email protected] #68 Sat Dec 8 08:54:36 CST 2012, build number crane_bc1003-eng 4.0.4 IMM76D 20121217 test-keys.
I've tried several options to load the recovery partition, only way I can access the recovery is through the backup and reset menu in settings, if I try to do it with the device powered off and holding the menu and power it just boots normal. I've tried a number of options home+power, vol up or down + home, none work. When I do get into the recovery, I cannot scroll through the options only thing there is the android robot with a red triangle and an exclamtion point.
Recovery version says android system recovery 3e EVB-V13.
I also cant get the sd card to mount. I've tried refromatting it with fat32, fat16, ext3 ext4. everything I get a message saying sd card damaged. I've tried 3 different card and same thing.
Any ideas XDA friends? I would like to put a custom rom like AOSP or CM9 or CM10 on it and clockwork recovery if that is an option. I've searched the net high and low for roms, I find many for other Flytouch tablets, but not Flytouch 8. This is the allwinner A10 processor in this one.
Thanks for your help friends.
I
Same problem her with a rooted FT 8 (same as yours)
.
After reboot i get sd card damage error.. after give this da RW i can mount this card again in settings/ storage.
After a reboot i get alway the error sd card damage....
I can get CWM 6.02 on this flytouch but didn`t get any custum roms or CWM backup installed...so get back tio basic image file with Livesuite.
have same recovery : recovery 3e EVB-V13 but cannot do anything with it. It don`t react with all the combination button on my flytouch.
Hopefully you can?
Same problem her with my fluytouch 8 32GB any halp pleas.
Recovery menu
hi
I've got the same tablet from china, am stuck at same spot as you are all, but I figured out how to move through menu in recovery, use usb mouse or keyboard.... any news on some custom rom and installation on this lousy tablet would be appreciated......
Solved Recovery Issue.
Hey everyone. I found this thread today, I tried it and it works perfectly. http://forum.xda-developers.com/showthread.php?t=2189640
I also read somewhere that Allwinner A10 and A13 cannot be flashed using stock recovery, you must use a program like Livesuit to flash firmwares. You can flash custom roms using CWM once it's installed on your device.
fldave612 said:
Hey everyone. I found this thread today, I tried it and it works perfectly. http://forum.xda-developers.com/showthread.php?t=2189640
I also read somewhere that Allwinner A10 and A13 cannot be flashed using stock recovery, you must use a program like Livesuit to flash firmwares. You can flash custom roms using CWM once it's installed on your device.
Click to expand...
Click to collapse
thanks man, this is good news, first step forward in cracking this damn slow tablet....now we need decent rom to install, any ideas?
Possible bricked BC1003..
Hi there I've got the exact same tablet with you BC1003 Model Flytouch Allwinner A10 Superpad 8 1GB Ram version running Android 4.0.4 stock.
So after following guides and researching a lot I ended up trying to upgrade to Jelly Bean.
I got CWM 6.02 installed fine. So I started the flash process.
Firstly I backed up my stuff and then I did a wipe data / factory reset.
Then proceeded and installed the latest possible rom version which I found to be : AOKP JB 4.1.2 ALLWINNER A10.zip
So I installed that one and the process went fine.
Then I installed this compatibility pack : t05a-v3_compatibility_1.2.0.zip
It also went fine.
Then I installed this google apps pack : gapps-jb-20120726-signed.zip
And it also installed normally.
So I was ready to reboot my tablet and so I did.
It turned off and then on again and here we are :
I now notice the screen turn on but it never shows anything..
Before flashing it it would turn on and show the Android OEM screen, then show the android loading text and then turn off and on and show the locked screen which I had to unlock and enter my desktop.
I notice that the screen light follows that pattern so the system is running normally only I don't get to actually see anything on it.
Now I'm kinda stuck here.. I've installed LiveSuite but when I try to install the recovery.img I have from my backup it says invalid image..
Have I bricked it or is there a way out of this mess?
Actually it's not entirely bricked.. well I finally got it to work with LiveSuit 1.09 and managed to flash its firmware to a couple more roms.
1. sun4i_crane_t05a_20120409.img -> Ends up showing some messy stuff on the screen. Looks like the resolution is not correct.
2. sun4i_crane_futekoA90universal_20120531.img -> Shows lots of white stuff and colors switching jelly-like.. But still it doesn't work.
3. TAB360-364_Android_411_Jelly_Bean.img -> This is the official A10 Jelly Bean firmware for Yarvik TAB364 GoTab Gravity 8".. No wonder I still got back to the blank screen issue. I only notice the back light turn on and off following the pattern of normal functionality, only I'm not able to actually see it..
Well, at least I'm still able to keep flashing roms to it.. Any ideas?
I can't even find my stock rom to turn back to 4.0.4. Where exactly is it located in my recovery-mode backup?
Btw, in case it plays any part my tablet is 10.2''.
Any help would be greatly appreciated.
EDIT : Finally I figured it out! My correct stock rom is : sun4i_crane_bc1003.img
I found it through google and after flashing to it I managed to get my tablet at a working state. (ICS 4.0.4 ICS 4.0.3)
So, I'll now try to use more Jelly Bean roms without worrying about bricking it.
Oh, something I noticed that might help others too.. even though on the packaging it says Flytouch Superpad 8 Allwinner A10 this tablet model (BC1003) is actually the Flytouch Superpad 7 and that helped me find my correct rom. Keep that in mind from now on. I'll keep you updated if I succeed in booting to Jelly Bean.
Finally some success..
Well, I finally have some interesting updates on the subject.
I managed to get Jelly Bean to work (Versions 4.1.2 and 4.1.1) on my BC1003 tablet without a compatibility pack (still none has worked for me).
Details on 4.1.2 Version :
Rom File Name : AOKP-4.1.2-3.0.52-Revb.zip
System running smoothly with wifi working fine.
Sound is fine and no crashes occurred.
Touchscreen, screen rotation and camera do not work.
I noticed that I can't browse to my external sd card.. it doesn't seem to get mounted.
Details on 4.1.1 Version :
Rom File Name : cm10_a10_20120913.zip
System running extremely smooth with wifi working fine.
Sound is fine and I experienced no crashes.
Touchscreen, screen rotation and camera do not work.
Also could not mount my external sd card.
Important bug noticed : When I try to change the brightness of my tablet's screen it enters suspended mode no matter what I do and is not fixable. I had to reflash the rom to recover from that state.
I think most of the problems would go away if I found a compatible jelly bean compatibility pack for this tablet.
If anyone has any clue please let me know.
So far I've tried these with no luck :
t05a-v3_compatibility_1.2.0.zip
t05a-unk_compatibility_1.2.0.zip
907c_compatibility_1.2.0.zip
By the way the BC1003 ICS rom that I found to be working was actually not my manufacturer's and it was version 4.0.3 instead of 4.0.4 that my original one was.
So, @fldave612 if it's possible could you please backup and upload yours somewhere so that I can also have it?
EDIT: Actually I figured out that I had kept a good backup form my ICS 4.0.4 using clockwork backup/restore and switched back to that for now.
But I've kept a backup of my Jelly Bean installation too so it's very easy to switch to that now. I'll try again once we get a compatibility pack working.
I feel we're very close to completely upgrading to Jelly Bean now on this tablet. We only need a working compatibility pack.
How did you succeed to install these ROMs, I tried both, installation went OK, but after reboot, only black screen......
Sent from my GT-P5110 using xda app-developers app
baschelik said:
How did you succeed to install these ROMs, I tried both, installation went OK, but after reboot, only black screen......
Sent from my GT-P5110 using xda app-developers app
Click to expand...
Click to collapse
I just installed them without a compatibility pack. It's not the jelly bean build that fails.. it's just the compatibility pack.
I researched it a bit and starting to look for a compatibility pack that works on very similar tablets (10.2'' - 1024 x 600 - 1GB Ram).
I found some, and got it to boot without a blank screen. Some showed messy colors others seemed to be working fine but still no touch..
So until we get one working on our specific precious tablet, we're kinda stuck here..
The 4.1.2 version seemed to be working fine but without touchscreen it's pretty much useless.
We could live without a camera or screen rotation, but not without touchscreen..
I even figured out that I could browse to the external sd card by going to root and then storage folder.. instead of mnt..
Actually now I'm stuck with ICS 4.0.3 since the original backup I kept proved to not be working fine.. it kept on crashing all the time..
So if someone has the original BC1003 ICS 4.0.4 that came from the manufacturer please upload it somewhere and post a link here.
Also if someone works on it to create a touchscreen driver for the world would become more beautiful..
Go to this link: http://www.maixin-china.com/software-download.asp Scroll down about half way and go to the link for "MaPan F10B (Cortex A8 Flytouch 6 and Flytouch 8) Software". I used the newest one 11-28.
This is a firmware is the one for this tablet. Use Livesuit to flash it, it will restore the tablet back to 4.0.4 factory.
It is virtually impossible to brick an A10 tablet from what I'm reading because it can be flashed via usb and have to boot loader re-imaged.
This link is very helpful to flash via Livesuit: http://elinux.org/Hack_A10_devices
Hope this helps you all as much as it did for me. Hopefully in the near future some developers will build a CM10 or higher version that will work on this tablet, until then I'll use this rom with Clockwork recovery mod.
Moin @all
Ich have chrashed my tab too but the download link is dead.
Any ideas where ich can load the file ?
Sorry for my ****ty bad English :silly:
Gothfather
I've also got this tablet (BC1003) - thank you for all the useful information posted on this thread so far.
If I've understood correctly, it's possible to install custom firmware using LiveSuite but at the moment none of them fully support this tablet - is that right?
At the very least I'm looking for a way to increase the size of the internal memory partition - the stock partition table has this unnecessary virtual sdcard partition taking most of the 2GB internal memory...
i have one of these damn slow tablets
i watched a vid on youtube about how to remove the internal sd card it is so simple to do it only take like 3 mins and 7 screws ive done this and put a 16gb card in there
i cant post a link but heres the name of the vid "Flytouch 5 / Superpad 6 V10 - Disassembly - Access to internal TF"
it is not the same tablet but is pretty much the same
Tip use a knife to pop the caps off the outside i found this easier
try not to stab yourself.
thanks if i helped you out
noob
okay so i tried to install a new rom on my allwinner a10 bc1003 and ended up only booting a black screen i dont know what im doing as this is my first tablet an very little computer knolage but im interested i had seen in a post he used livesuit to flash the new rom.... i dont understand how that works if anyone could sit down and teach me that would be apriciated
---------- Post added at 12:21 PM ---------- Previous post was at 12:16 PM ----------
SolidSnakeGr said:
Actually it's not entirely bricked.. well I finally got it to work with LiveSuit 1.09 and managed to flash its firmware to a couple more roms.
1. sun4i_crane_t05a_20120409.img -> Ends up showing some messy stuff on the screen. Looks like the resolution is not correct.
2. sun4i_crane_futekoA90universal_20120531.img -> Shows lots of white stuff and colors switching jelly-like.. But still it doesn't work.
3. TAB360-364_Android_411_Jelly_Bean.img -> This is the official A10 Jelly Bean firmware for Yarvik TAB364 GoTab Gravity 8".. No wonder I still got back to the blank screen issue. I only notice the back light turn on and off following the pattern of normal functionality, only I'm not able to actually see it..
Well, at least I'm still able to keep flashing roms to it.. Any ideas?
I can't even find my stock rom to turn back to 4.0.4. Where exactly is it located in my recovery-mode backup?
Btw, in case it plays any part my tablet is 10.2''.
Any help would be greatly appreciated.
EDIT : Finally I figured it out! My correct stock rom is : sun4i_crane_bc1003.img
I found it through google and after flashing to it I managed to get my tablet at a working state. (ICS 4.0.4 ICS 4.0.3)
So, I'll now try to use more Jelly Bean roms without worrying about bricking it.
Oh, something I noticed that might help others too.. even though on the packaging it says Flytouch Superpad 8 Allwinner A10 this tablet model (BC1003) is actually the Flytouch Superpad 7 and that helped me find my correct rom. Keep that in mind from now on. I'll keep you updated if I succeed in booting to Jelly Bean.
Click to expand...
Click to collapse
okay im sitting at this point but i dont understand the flashing with livesuit
With the Windows utility "Phoenix Card" it is possible to burn the MaPan image mentioned above to a micro SD card. After inserting the micro SD card into the tablet and booting up the image will be flashed onto the tablet, indicated by a progress bar and a ticking sound.This works for our tablet, and should work for firmware for several Allwinner A10 and A20 tablets plus some other processor families (vimicro?).
where can i get Windows utility "Phoenix Card"
cant find 1 that works the inside says Yones toptech BC 1003 all winers A10
flusspferd said:
With the Windows utility "Phoenix Card" it is possible to burn the MaPan image mentioned above to a micro SD card. After inserting the micro SD card into the tablet and booting up the image will be flashed onto the tablet, indicated by a progress bar and a ticking sound.This works for our tablet, and should work for firmware for several Allwinner A10 and A20 tablets plus some other processor families (vimicro?).
Click to expand...
Click to collapse
hi ... i have a Yones toptech BC 1003 all winers A10 (superpad 8 / flaytouch) that im trying to fix...
after 3 days trying every possible firmware, and booting them from external sd card
all i could do was change de logo at boot start from (mapan to kosaco, to oem etc..)
than i had the idea of removing the internal sd card to look at it ...
and guess what it still runs the same with out no sd card in or out
so i thought ... the sd card was never read in the first place cause is damage or corrupted...
so on the 4th day im trying to format and partition the new internal sd card... hoping for the best.
so...
is the firmware installed in a built in memory ??
and how do i format the internall card TF card , and install all the software again
Problems with CWM v6.0.2.8
Sorry to interrupt people, but I'm quite new at this and I guess I made a mess....
I have a Flytouch Superpad VIII with A10 inside (BC1003), which is bricked.
Don't ask me how I got it this way, I guess **** happens.
Downloaded and installed CWM-based Recovery v6.0.2.8 only to find that on the log it cannot mount...
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache recovery/last log
My idea is that I probably used the wrong version of CWM, but if not the case, please tell me.
Anybody know a fix on this?
I've already intalled ADB drivers on my PC and at least I can communicate with my device using ADB.
Any help on unblocking the device and then flashing it would be greatly appreciated