Related
Thanks to user Nefirim over at Android Tablets Coby has released a new firmware update to the Coby Kyros Mid8024. he notes that it fixes the white screen of death that some users have experience when flashing modified images for this device.
http://www.cobyusa.com/files/software/MID8024-Firmware.zip
This link is the updated info about ICS on Coby Kyros ICS
http://forum.xda-developers.com/showpost.php?p=25904980&postcount=11
Edit : This post was about Coby Kyros 8024 , but recently Kernel Dev. NamKo over at slatedroid has pushed an alpha kernel that is for herotab c8 but happens to work slighty on Coby Kyros 1024.Using official source from urbetter..The kernel is not perfect but it allows us to use CM9 and ICS 4.04 on this tablet. There are many things not working but hoping to attract people with more knowledge to help out
http://www.slatedroid.com/topic/312...from-urbetter/page__view__findpost__p__337939
mid8024 firmware
did anyone actually use this. my mid1024 was semi-bricked, so i decided to try this. the manual also specified 1024, so what the hell.
The process was pretty smooth, but upon boot the screen (logo) was all messed up, it made it to the desktop and all i could make out was the time.
tried several times, zipped, unzippped. it accepted the procedure, but for the worst.
pretty bad. device will be going back to where it came from anyhow.
cfirpo99 said:
did anyone actually use this. my mid1024 was semi-bricked, so i decided to try this. the manual also specified 1024, so what the hell.
The process was pretty smooth, but upon boot the screen (logo) was all messed up, it made it to the desktop and all i could make out was the time.
tried several times, zipped, unzippped. it accepted the procedure, but for the worst.
pretty bad. device will be going back to where it came from anyhow.
Click to expand...
Click to collapse
I hope you got your deviced fixed,but the 8024 and 1024 are different The 1024 is capacitive screen while 8024 and 7024 have resistive screen.. Coby has released firmwares for the 7024,8024 and 1024. Also the update only fix devices which were soft bricked and had white screen of death...They do not update the android os
cfirpo99 said:
did anyone actually use this. my mid1024 was semi-bricked, so i decided to try this. the manual also specified 1024, so what the hell.
The process was pretty smooth, but upon boot the screen (logo) was all messed up, it made it to the desktop and all i could make out was the time.
tried several times, zipped, unzippped. it accepted the procedure, but for the worst.
pretty bad. device will be going back to where it came from anyhow.
Click to expand...
Click to collapse
The rom is chinese, click the settings icon go down and find the keyboardy icon and change language to english.
coby 8024 dead
hi can any body can help me i try to update coby 8024 with wrong firmware, and now phone is dead black screen only leds light when i push power and turn off.
Help me pleaseee
Kyros 8024 update
To whom it may concern... I have a tablet that looks exactly like the 8024 Kyros. The specs are the same, it's branded as Allview Here is a Gingerbread update. It's in Romanian. use Google translate
It says there don't use an microSD bigger than 1 Gb. Don't. I did and it bricked it. Luckly the service is like 3 miles away and they fixed it.
http://allview.ro/produse/droseries/lista-droseries/alldro-2/descriere.html
Friend I leave the gingerbread version for 8024 Kyros me based on the Romanian tablet "Tablet AllDro2" which is exactly equal to the Kyros 8024. - Official Firmware
This will only change CFW languages are by default (Romanian to English) , Build.prop, the wallpapers and logo.bmp.
Works 100% points.
htt*s://rapidshare.com/files/4287186128/CFW-Kyros_8024_2.3.rar
jmv_10 said:
Friend I leave the gingerbread version for 8024 Kyros me based on the Romanian tablet "Tablet AllDro2" which is exactly equal to the Kyros 8024. - Official Firmware
This will only change CFW languages are by default (Romanian to English) , Build.prop, the wallpapers and logo.bmp.
Works 100% points.
htt*s://rapidshare.com/files/4287186128/CFW-Kyros_8024_2.3.rar
Click to expand...
Click to collapse
Mine came with 2.2. From what I read initially Coby 8024 was Froyo too. I assumed that someone else might be interested.
Problems with COBY KYROS MID8024
I am also having problems after the firmware update
TABLET allview
after updating my firmware with this Kyros not turn over, it is only black screen and the buttons light up and then hangs up. Already tried the process of giving short pin 7 & 8 of the NAND memory but could not succeed.
What to do?
Apologies for the bad english, I'm from Brazil and I speak little English language.
Help me ... Did I miss my tablet?
my email is
[email protected].
thank.
All kyros model 7024,8024 & 1024 Now have a fully working gingerbread mod. All features working.
Sent from my Coby Kyros 7024
[WIP]Coby Kyros 1024 Running ICS
Disclaimer. This is not my work. This is CM-9 ported by SMDKV210 with NAMKO's Kernel(4/22/2012)
Flash this at your own risk. I take NO Responsibility for Bricking Your Device.
This rom is a work in progress. There are numerous things not working, because the kernel is not directly made for Coby Tablets.
This thread is to post your findings and possibly to help get a Kernel thats made for our tablets.
To flash this rom. Prepare a clean fat 32 formatted sdcard.This will format your internal Sdcard and erase your tablet contents.
Press and hold Home center button and Power Button,simultaneously, release when you see mid upgrade in progress. Do not press any buttons or attempt to power off your tablet. Let it up grade your software and it will shutdown when its done.
TESTED ON 1024N board Not sure if this will work on any other device. This kernel did not boot on my 8024 but I haven't tried with the new OS.
On first boot (well every boot) Kernel panics right away(The black penguin) and sometimes the display is snowy or has a faded effect. Just wait and the bootanimation will start. After tablet boots up There you are CM-9 on Coby Kyros 1024.
I suggest you restart tablet after first boot. I am just an end user like most of you I will help in any way possible. I am not a developer I made this so that others would be able to see and help with the development.
Home button works. Soft buttons do not work and I haven't figured out how to kill the lights
included:
Youtube
Aldiko Reader
Google Play(untested)
tapatalkxda
twitter
Nova Launcher
5/09/12
1024 board
nothing new except Namkos kernel on 5/2/2012. Built with thunderstorm beta 10 installer....
cm9 is the SMDKV210 version
4.04 is Namko with tuens tweaks to get wifi to connect manually...extsd is still not mounting and the usual non working items.....
Some apps are tweaked and the build.prop may need to be edited....I believe youtube vids are using hq in the 4.04 build added lastest aldiko reader to 4.04
http://www.mediafire....pclubp1k4p9np4
@Vernox701
how is the Coby MID 1024 performance? Any bugs or any issues encountered?
nice1_101 said:
@Vernox701
how is the Coby MID 1024 performance? Any bugs or any issues encountered?
Click to expand...
Click to collapse
Performance is fine
USB
Camera
Axis Rotation
Wifi Connection
HDMI ?
The kernel is made for a different device so things written on the kernel level are not communicated to the os.
You have to enter your wifi settigs manually to connect, turning off wifi shuts tablet down. Camera does not work but someone found sources so kernel dev maybe able to incorporate them soon.
I get over 10 hours of battery without use maybe 6 hours when I am using but there are no tweaks added other than reducing wifi scan in the build prop.
Vernox701 hello, is there any other site that I can follow the development step by step ROM compatible with Kyros 1024?
Do you have any prediction for a new release?
thank you
Coby Kyros MID7024
Where is the file? please update me.. thanks a lot..
link not found
Hello,
I know this is not the first time this topic is brought, although it is usually part of an unrelated thread.
I have this AllWinner A10 mk802 , a strange device (it looks like a usb flash drive, but is an Android 4.0.4 computer on which you plug your own screen, mouse and keyboard, making it a Desktop PC on a stick running Android).
Not being a big fan of tablets, I thought I'd give it a try -- Android with a keyboard and a mouse (!). It doesn't look too bad even if it is not powerful enough for my tastes and I can't install CM9/10 on it because of the issue I'll bring here in a second. (In the meantime I installed Uberoid 1.2, which is the stock chinese Android 4.0.4 image which most of its cruft removed -- still doesn't feel right, though.)
There are experimental builds of CyanogenMod 9 and 10 for it, there is a ClockworkMod for it, but I can't use it: when I get into recovery mode, I get a visually awkward-looking (see http://i.imgur.com/Nchso.png ) CWM screen, which wouldn't be a problem if I were able to move through the menus. I've tried with three different mice, three different keyboard, the only thing I was able to do was to flash the screen (it turns black 2 ou 3 seconds) and that's all.
Now, I'm almost there. I just need to be able to wipe the existing system, install CM10, its support (legacy) file and GApps. For that, all I have to do is a dozen of key presses. But I think that I've tried everything.
Has anyone here fought this or a similar issue and won? If so, how did you proceed?
Thanks!
cpl593h said:
Hello,
I know this is not the first time this topic is brought, although it is usually part of an unrelated thread.
I have this AllWinner A10 mk802 , a strange device (it looks like a usb flash drive, but is an Android 4.0.4 computer on which you plug your own screen, mouse and keyboard, making it a Desktop PC on a stick running Android).
Not being a big fan of tablets, I thought I'd give it a try -- Android with a keyboard and a mouse (!). It doesn't look too bad even if it is not powerful enough for my tastes and I can't install CM9/10 on it because of the issue I'll bring here in a second. (In the meantime I installed Uberoid 1.2, which is the stock chinese Android 4.0.4 image which most of its cruft removed -- still doesn't feel right, though.)
There are experimental builds of CyanogenMod 9 and 10 for it, there is a ClockworkMod for it, but I can't use it: when I get into recovery mode, I get a visually awkward-looking (see http://i.imgur.com/Nchso.png ) CWM screen, which wouldn't be a problem if I were able to move through the menus. I've tried with three different mice, three different keyboard, the only thing I was able to do was to flash the screen (it turns black 2 ou 3 seconds) and that's all.
Now, I'm almost there. I just need to be able to wipe the existing system, install CM10, its support (legacy) file and GApps. For that, all I have to do is a dozen of key presses. But I think that I've tried everything.
Has anyone here fought this or a similar issue and won? If so, how did you proceed?
Thanks!
Click to expand...
Click to collapse
I just got one also and have found a forum that is pretty comprehensive. I am doing a lot of reading before I jump to it. Try here:
http://www.rikomagic.co.uk/forum/index.php
Let me know how it goes as I am sure to root and flash CM10 as soon as some one gets it figured out.
Mac N Ts Daddy said:
I just got one also and have found a forum that is pretty comprehensive. I am doing a lot of reading before I jump to it. Try here:
http://www.rikomagic.co.uk/forum/index.php
Let me know how it goes as I am sure to root and flash CM10 as soon as some one gets it figured out.
Click to expand...
Click to collapse
I have dug this site also and wasn't able to find anything (or anything actually working) for my CWM problem. If you find something there that helps you, please share.
Thanks!
I have the same issue, Maybe someone can make Livesuit .img from the CM9/10 packages and compatible gapps and comp zips?
I just got a MK802 for testing and if it works fine with CM I will keep it or even better get a new one, but I am dealing with the same issue, the mouse/keyboard entry reboots the recovery, as if any movement is an enter and reboots the MK into recovery...
If anyone of you guys were able to fix this I would appreciate the info..
LuciusK said:
I just got a MK802 for testing and if it works fine with CM I will keep it or even better get a new one, but I am dealing with the same issue, the mouse/keyboard entry reboots the recovery, as if any movement is an enter and reboots the MK into recovery...
If anyone of you guys were able to fix this I would appreciate the info..
Click to expand...
Click to collapse
+1
Hi all.
I had the same problem.
My mouse works perfectly in both versions of stock MK802+ firmware, but in CWM it switches the screen off for a few seconds every time I move it. The same is happening with my keyboard, so I am struggling to flash cyanogenmod.
SOLUTION:
I changed the mouse to a wireless one (not bluetooth, but standard 2.4), I had lying around and it worked fine.
I think it's because the first mouse I tried has a laser pickup which draws more power or maybe its just a cwm driver issue.
The keyboard and mouse I originally used are quite fancy gaming products, so maybe they are just too "high-tech" for Clockword Mod.
Cheers
Steve
CWM video anomaly on MK802
Hey Everyone !
XDA noob here but I've been modding my junk for several years now since HTC Eris.
I'm having the exact same problem as cpl593h, screenshot is identical.
I wanted to use TWRP, I love that recovery -best thing in device modding ever IMHO, but I can't see anythig about mouse support. It's all touchscreen I guess. I tried GooManager but it were a no go. Still trying to find a recovery alternative to CWM. I know it's been around a long time but I've had more trouble with it that successes.
If I find a workaround, I'll post it here!
CyberCorgi3K
CM10 livesuit image
avishayil said:
I have the same issue, Maybe someone can make Livesuit .img from the CM9/10 packages and compatible gapps and comp zips?
Click to expand...
Click to collapse
hey there,
btsimonh from miniand.com managed to make a livesuit compatible .img of CM10. What's also included is zulu99's work of including droidmote compatibility. So no need to struggle with CWM any more.
Simon said that he will put some efforts in optimizing the ROM further.
So if there's any progress, I'll post that.
Sadly, as a new user, I'm still not allowed to post some links.
So I guess it's good to PM me until I reached URL posting threshold.
cpl593h said:
Hello,
I know this is not the first time this topic is brought, although it is usually part of an unrelated thread.
I have this AllWinner A10 mk802 , a strange device (it looks like a usb flash drive, but is an Android 4.0.4 computer on which you plug your own screen, mouse and keyboard, making it a Desktop PC on a stick running Android).
Not being a big fan of tablets, I thought I'd give it a try -- Android with a keyboard and a mouse (!). It doesn't look too bad even if it is not powerful enough for my tastes and I can't install CM9/10 on it because of the issue I'll bring here in a second. (In the meantime I installed Uberoid 1.2, which is the stock chinese Android 4.0.4 image which most of its cruft removed -- still doesn't feel right, though.)
There are experimental builds of CyanogenMod 9 and 10 for it, there is a ClockworkMod for it, but I can't use it: when I get into recovery mode, I get a visually awkward-looking (see /*NO LINKS*/ ) CWM screen, which wouldn't be a problem if I were able to move through the menus. I've tried with three different mice, three different keyboard, the only thing I was able to do was to flash the screen (it turns black 2 ou 3 seconds) and that's all.
Now, I'm almost there. I just need to be able to wipe the existing system, install CM10, its support (legacy) file and GApps. For that, all I have to do is a dozen of key presses. But I think that I've tried everything.
Has anyone here fought this or a similar issue and won? If so, how did you proceed?
Thanks!
Click to expand...
Click to collapse
Hi2all!
I have exact the same problem with device "appolo-mele" (allwiner a10 platform) - graphics looks to bad, also when i try to switch menu entry - screen turns off and then turns on (on next menu entry), but CWM works fine (backup and restore functions).
I tried:
1. CWM for Allwiner A10 ("CWM 6.0.2.8 for Allwinner A10 & A13 Tablets - v2a") - "graphics problem"
2. Some other CWM 5... and 6... versions for Allwiner A10.
3. Build cwm recovery from sources, using native boot.img, following the "[GUIDE] Build CWM recovery " by buffo1987 and "[GUIDE] Compile CWM Recovery" by Shaaan. - "graphics problem", anything else works fine.
Here is some info about device:
1. It is a TV Box device with HMDI, WiFi, LAN, SPDIF optical audio out and AV-TV out ("3.5 4contact jack in device to 3 tulip connectors to TV"), 2 usb
2. Complied 6.0.3.7 CWM
3. cpuinfo: ARMv7Processor rev 2 (v71) , sun4i
4. other info is similar to "Rikomagic MK802+"
Maybe I should try to use custom "graphics.c"?
Can some help me with my problem?
Attached is the latest version of the recovery file.
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
Hello. i want to ask if someone have Clockwork mod or some custom firmware on Prestigio PMP5670c Android 4.1.1.
I managed to root it, but i realy dont like this Android version and Prestigio is not intrested in upgrading.
Hey can someone make a recovery for this tablet.
Sent from my PMP5670C_DUO using xda premium
Shawes said:
Hello. i want to ask if someone have Clockwork mod or some custom firmware on Prestigio PMP5670c Android 4.1.1.
I managed to root it, but i realy dont like this Android version and Prestigio is not intrested in upgrading.
Click to expand...
Click to collapse
I started to do some work on that tabled, but stuck with kernel touchscreen configuration. See here.
Touch chip is Goodix GT911, screen size is 800x1280 px. I managed to get touch working but partialls. First aprox 1.2 inches of top of screen are not responsive to to touches. After that 1.5" touch works normally.
I'm pretty sure I'm sending wrong configuration data array to chip and thats why its not working as it should, but have no time at the moment to toy with it. If anyone experienced with Goodix chips, pm me with ideas...
stane1983 said:
I started to do some work on that tabled, but stuck with kernel touchscreen configuration. See here.
Touch chip is Goodix GT911, screen size is 800x1280 px. I managed to get touch working but partialls. First aprox 1.2 inches of top of screen are not responsive to to touches. After that 1.5" touch works normally.
I'm pretty sure I'm sending wrong configuration data array to chip and thats why its not working as it should, but have no time at the moment to toy with it. If anyone experienced with Goodix chips, pm me with ideas...
Click to expand...
Click to collapse
Update: I started to toy with stock kernel and cm10.2 (my first CM ever, was working with AOSP based SoC manufacturers sources). Problem is that device uses separate partition for internal sdcard, so have to disable emulated storage.
Things done:
- recovery
- android is built against precompiled stock kernel
Status:
- after bootanim and starting apps screen android reboots and starts back with bootanim. This was one day tryout, will debug it later today. Thanx to TeamNostalgia's preparation for cm10.2 on Amlogic MX. I used their framework and device stuff, upgraded with latest amlogic version of sources. Because of SLA I have with Amlogic, I cannot put it online.
any news abouth root final this tablet?
thx for info
stane1983 said:
I started to do some work on that tabled, but stuck with kernel touchscreen configuration. See here.
Click to expand...
Click to collapse
klobasica said:
any news abouth root final this tablet?
thx for info
Click to expand...
Click to collapse
On the link abouve is posted rooted stock firmware (mine post). To lazy ones click here
no, no...sorry i mean custom rom if is posable to create for this tablet...
klobasica said:
no, no...sorry i mean custom rom if is posable to create for this tablet...
Click to expand...
Click to collapse
It is. I'm not CM guy really, but its possible. If anyone interested, TeamNostalgia's github does have decent tree for Amlogic MXS tablets. I did some CM10.2 work for that tablet, but ended up with bootloop and reboot eventually. Didn't had time do debug it.
Here 4pda.ru/forum/index.php?showtopic=504411&view=findpost&p=29560411 is a customized firmware from Prestigio PMP3970B to work on Prestigio PMP5670C. But it does not run on PMP5670C, stands on the splash screen. Maybe someone will take to complete the firmware, it is better factory firmware for the tablet PMP5670C
ksh2000 said:
Here 4pda.ru/forum/index.php?showtopic=504411&view=findpost&p=29560411 is a customized firmware from Prestigio PMP3970B to work on Prestigio PMP5670C. But it does not run on PMP5670C, stands on the splash screen. Maybe someone will take to complete the firmware, it is better factory firmware for the tablet PMP5670C
Click to expand...
Click to collapse
I fixed U-Boot (wrote my own to support device tree kernel - 3.10.10) and fixed touch screen. I did not upload this fw, started to work yesterday on amlogic's 4.4 sources (they support both mx and m8 chipsets) (no, I cant share, I have SLA with them), I have boot, only left few things to test and then I'll upload 4.4.2.
Thank you for keep working! Waiting for rom)
Sent from my GT-I5510 using xda app-developers app
cyanodeff said:
Thank you for keep working! Waiting for rom)
Sent from my GT-I5510 using xda app-developers app
Click to expand...
Click to collapse
Here's beta version of rom: http://www.stane1983.com/prestigio_pmp5670c/
Read install instructions, needs to be installed twice, uboot still not perfect. Waiting for feedback
Btw, it's 4.2.2 rom, KitKat doesn't work good (unstable) on MXS chip.
Installed today morning. Seems all good! Thank you very much
Sent from my GT-I5510 using Tapatalk 2
babicsbalu said:
Unfortunatelly I can not able to install it because the second install is freezing all the time, now I can not install official 1.0.0.5 ROM, it stucked during the installation.
Click to expand...
Click to collapse
Rename uImage_recovery to recovery.img (when installing back stock firmware).
babicsbalu said:
Now I successfully installed the 1.0.05 but there is a quite big issue: I can not able to install anything from Play, the Download Manager is acutally (lots of system apps too) 0.0kb
Click to expand...
Click to collapse
I'm really sorry for inconveniences. With 1.0.05 files on sdcard, delete factory_update_param.aml file and boot into recovery (as if you want to install firmware). From menu using vol +/- and power for select choose factory reset (data partition is not formatted using old partition layout, thats why you have 0kb). After that you also can reflash firmware if you want (just select zip from sdcard).
stane1983 said:
Here's beta version of rom: http://www.stane1983.com/prestigio_pmp5670c/
Read install instructions, needs to be installed twice, uboot still not perfect. Waiting for feedback
Btw, it's 4.2.2 rom, KitKat doesn't work good (unstable) on MXS chip.
Click to expand...
Click to collapse
My daughter get this tablet from her grandfather on 03.05.2014 ( I guess she is lucky about that date ), and it was so slow and ugly and everything.
I installed your bety rom and everything is perfect. BUt after first reboot i get setup wizard again, but the first time after Install I only get FC ( just like I should ) but it didnt throw me back to setup wizard again.
Can I expect wizard setup every time I reboot or?
And Yes, thank you a lot for this awesome and fast work. The tablet is now so much more usable.
HVALA TI STANE MNOGO => THANK YOU STANE A LOT
@stane1983 I have the same problem as @babicsbalu. My pmp5670c is also stuck at black screen after rebooting and installing new stock firmware. I did both, renaming from uImage_recovery to recovery.img and deleting factory_update_param.aml and every time with the same result.
Please help me!
Or you can PM me (I'm from Croatia)
Hvala ti!
Well I also have prestigio tablet pmp5670C_BK_DUO and within a week it got bricked somehow. I guess that broken charging pin on cable had something to do with it - probably did a short circuit or something and boot loader got corrupt. Tabled was responding to connection of new charging cable, but only backlight turned on. There was no logo or anything.
I browsed several pages and nothing worked. I tried with official upgrade from SD card but it didn't work. It started to upgrade, android-upgrade logo came up, but after reboot nothing happened. Damaged bootloader was unable to start the tablet.
After a day or so I finally found a way how to unbrick it! Yeah.... So in attached file there is the detailed procedure, which I found on some Russian page.
Good luck!
Recovery.rar no longer available
imarkic said:
Well I also have prestigio tablet pmp5670C_BK_DUO and within a week it got bricked somehow. I guess that broken charging pin on cable had something to do with it - probably did a short circuit or something and boot loader got corrupt. Tabled was responding to connection of new charging cable, but only backlight turned on. There was no logo or anything.
I browsed several pages and nothing worked. I tried with official upgrade from SD card but it didn't work. It started to upgrade, android-upgrade logo came up, but after reboot nothing happened. Damaged bootloader was unable to start the tablet.
After a day or so I finally found a way how to unbrick it! Yeah.... So in attached file there is the detailed procedure, which I found on some Russian page.
Good luck!
Click to expand...
Click to collapse
I had a similar problem here and this method seems promising, but the recovery file indicated on the PDF is no longer available. Would you still have it lying around somewhere?
Thank you!!
PMP5670c Duo
I got this tablet 2 month ago, i have found on w w w 4pda ru 4 custom rooms for this tablet and i used google chrome to translate in english to understand what i have to do, i have instaled every one rom but i got a problem, with all custom rom the internal storage disapear. I instaled stock version now and the internal storage is there ready to be used. Custom roms are better than stock rom but it's annoyng me the missing internal storage. Anyone with this problem or anyone know how to fix it?
Edit: I instaled stock rom then i instaled again Firmware v.1.0.10 from MrCheba Repack and now i have internal storage working maybe reinstall the stock rom fix it.
Has anyone tested the AOPP (Android Open Pwn Project) ROM for our Shields? I just came across it yesterday while catching up on the Pwnie Express site.
Link: https://wiki.pwnieexpress.com/index.php/Supported_Devices
Note: ROM is *not* for the K1 variant.
Would love to hear anyone's experience.
I was going to try building from source to get it to work on the K1, as from what I'm reading the hardware is essentially the same so there shouldn't be *too* many errors... Right?
Shield's in the mail, so I'll report back with results later. Will be super excited if it works.
equi_design said:
Has anyone tested the AOPP (Android Open Pwn Project) ROM for our Shields? I just came across it yesterday while catching up on the Pwnie Express site.
Link: https://wiki.pwnieexpress.com/index.php/Supported_Devices
Note: ROM is *not* for the K1 variant.
Would love to hear anyone's experience.
Click to expand...
Click to collapse
Seeing as how it hasn't been updated since August....
It's Alive!
Managed to get it up and running on the Shield Tablet K1, which I forsaw as it's the same hardware, minus one stylus.
However, I will say this - update the nVidia app/software before doing anything or you'll be stuck in a boot loop. It flashes the firmware to be compatible with the latest TWRP, which I found out after having to flash back to the 'fallback' base image from nVidia. Other than that, smooth sailing - though it does appear to have the 'random reboot' problem still, which I've seen a few people mention on the forums.
Now I just need some OTG cables and the fun can begin.
Question
c0rsana said:
Managed to get it up and running on the Shield Tablet K1, which I forsaw as it's the same hardware, minus one stylus.
However, I will say this - update the nVidia app/software before doing anything or you'll be stuck in a boot loop. It flashes the firmware to be compatible with the latest TWRP, which I found out after having to flash back to the 'fallback' base image from nVidia. Other than that, smooth sailing - though it does appear to have the 'random reboot' problem still, which I've seen a few people mention on the forums.
Now I just need some OTG cables and the fun can begin.
Click to expand...
Click to collapse
Are the random reboots that bad?
Also for a total newbie would you recommend this ROM?
It's ancient, why would anyone want to flash this?