Hey guys,
The patient is an Android RK3188 5.1 unit from Xtrons for a BMW. The manufacturer is "GS".
After installing basic apps the unit started to really lag, not to mention that the touchscreen stopped working. So I flashed it with a factory MTCD 5.1 KGL rom and the installation went without any problems. After that I had to flash it back to a GS ROM, so I used something I found here on XDA a while ago, namely "GS_NEW4_rk3188_5.1(20160305)".
The installation went without any problems, but the unit then stopped on the "Lollipop" logo. It doesn't go to the car logo after that, just stops dead at the Lollipop screen and that's it.
When I try entering recovery, it works like it should, but the unit blurts out a crapload of info and errors, like the ones you can see in the attached pictures.
Updates don't work anymore.
Please note: I did NOT try to update the MCU on this unit. Only the Android software.
What's the problem with this unit? How to get it back to its normal state?
Picture descriptions:
1 - how recover looks like upon entering it.
2, 3 - sorry for the blurry pictures, but it's hard to snap a good picture of the moving text. You get the idea - a thousand errors or so.
4 - when I try flashing a regular KGL rom that worked on the unit before.
Did you tried this from sd card in GPS slot?
Never had success with that, only from usb drive.
Maybe you try this and it helps...
makes2068 said:
Did you tried this from sd card in GPS slot?
Never had success with that, only from usb drive.
Maybe you try this and it helps...
Click to expand...
Click to collapse
Yes. USB doesn't work.
Test it with another usb stick.
I have the same problems with some of the USB3 32GB Sticks from Sandisk.
SanDisk SDCZ43-032G-G46 Ultra Fit 32GB USB-Flash-Laufwerk USB 3.0 ✓
SanDisk Ultra Dual USB-Flash-USB Stick 32GB USB 3.0 X
Test all USB Ports and formate the sticks fat32
Use stick as small as possible.
Same to gps card. Use 16GM max, and all works as expected. Got some problems with 32gb cards. Took too long to show covers...
So, essentially, the problem here is the SD cards or USB sticks?
I don't think that's the problem.
I know how to update headunits, and it never mattered whether I used this card, that card or that USB stick... in fact, I only use microSD cards for updates, nothing else.
What the problem is is that the update breaks the unit, rendering it impossible to use.
I need to know what is the cause of that, and how to REVERT the damage.
Please read my first post again.
looks like the internal flash memory is broken. From your pics there is a line where the recovery is trying to make a partition and fails. It might be a pain in the ass but try to get xtrons to send you another SOM board.
vinhZ said:
looks like the internal flash memory is broken. From your pics there is a line where the recovery is trying to make a partition and fails. It might be a pain in the ass but try to get xtrons to send you another SOM board.
Click to expand...
Click to collapse
Thanks for your reply.
Can you, or somebody else explain how is it that the unit got screwed when installing a new ROM?
I did not touch the MCU or anything else. The unit is a RK3188 MTCD Android 5.1 one, and I used a different MTCD ROM.
It could be anything, like any flash drive/thumb drive, sometimes they just go bad. It accounts for the slowness when you originally flashed the new rom, then just gave out when you tried to flash again.
Me so nothing I can do
I have had your same issue: follow this guide: https://forum.xda-developers.com/showpost.php?p=67184851&postcount=50
Sure that it's a MTCD rom and not MTCB?
When i installed malaysk rom for the first time, i have had the same issue. My hu is a kd one too.
Inviato dal mio Redmi Note 3 utilizzando Tapatalk
dude-nl said:
Sure that it's a MTCD rom and not MTCB?
Click to expand...
Click to collapse
Yes.
@colostro - the recovery card doesn't work.
NaviPR said:
Yes.
@colostro - the recovery card doesn't work.
Click to expand...
Click to collapse
Why does not it work ? You can make a video? We did everything as written here? - https://forum.xda-developers.com/showpost.php?p=68717214&postcount=877
GS_NEW4_rk3188_5.1(20160305) - This firmware from MTCB !!! You have loaded the firmware from another device !!
NaviPR said:
Hey guys,
The patient is an Android RK3188 5.1 unit from Xtrons for a BMW. The manufacturer is "GS".
After installing basic apps the unit started to really lag, not to mention that the touchscreen stopped working. So I flashed it with a factory MTCD 5.1 KGL rom and the installation went without any problems. After that I had to flash it back to a GS ROM, so I used something I found here on XDA a while ago, namely "GS_NEW4_rk3188_5.1(20160305)".
The installation went without any problems, but the unit then stopped on the "Lollipop" logo. It doesn't go to the car logo after that, just stops dead at the Lollipop screen and that's it.
When I try entering recovery, it works like it should, but the unit blurts out a crapload of info and errors, like the ones you can see in the attached pictures.
Updates don't work anymore.
Please note: I did NOT try to update the MCU on this unit. Only the Android software.
What's the problem with this unit? How to get it back to its normal state?
Picture descriptions:
1 - how recover looks like upon entering it.
2, 3 - sorry for the blurry pictures, but it's hard to snap a good picture of the moving text. You get the idea - a thousand errors or so.
4 - when I try flashing a regular KGL rom that worked on the unit before.
Click to expand...
Click to collapse
Unfortunately I have the same issue "block device required " and I haven't found any solution over a month now.
Hope someone help you to find a solution as from my side I disappointed and my device is now decorate my room.
With the described method, you can't enter in recovery mode?!? Did you put sd card into gps slot? Sure?
Inviato dal mio Redmi Note 3 utilizzando Tapatalk
Hey guys,
I have a similar error but after install the ROM. I have installed malasyk rom MTCD 5.1.1 without problems, but when update the device with my stock ROM i don´t have internal_sd or flash and don´t can install GPS apk.... The device work fine but without internal_sd. If install other time the malasyk ROM the internal_sd appears.
Can you help me how i can mount internal_sd or flash?
Malaysk said:
Why does not it work ? You can make a video? We did everything as written here? - https://forum.xda-developers.com/showpost.php?p=68717214&postcount=877
Click to expand...
Click to collapse
@Malaysk - everything has been done to the letter, as always. I have had successes beforehand with the recovery card.
It just simply doesn't work in this case. The unit doesn't react to the card.
GS_NEW4_rk3188_5.1(20160305) - This firmware from MTCB !!! You have loaded the firmware from another device !!
Click to expand...
Click to collapse
How do you know that it is a MTCB rom?
Same problem to me.
The HU is booting on Lollipop logo, and this is it.
I can flash MCU, but cannot flash ROM.
The device is going in Recovery Mode, but cannot flash ROM.
Also, it cannot be connected to PC, to flash it with RkBatchTool.
When i am trying this: https://forum.xda-developers.com/showpost.php?p=67184851&postcount=50
the HU doesnt power on with SD card inserted.
My device was MTCD KGL. IS written on the pCB as well, and i took pictures before first flashing.
Any help is apreciated!
Related
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.
Hello guys.
I tried to flash the ROM of my device and now I am a bit screwed. Honestly I cannot remember what I did exactly but now I have two main problem:
- Hardware buttons LEDs do not work
- Volume knob only decreases sound no matter where you turn it to
At the moment my device is showing MTCD_GS_V21 but I am pretty sure it was not "GS" before I tried to flash it with dmcu.img and dupdate.img files at the same time.
More precisely I did the following:
I randomly downloaded two files from a topic here. I uploaded them ot a SD card and put it in the GPS slot. I went to my device > Settings > Software update and fhe device ran an update. I tried to use different ROMs after ( Malaysk and so on ) but the problems remain - no leds and volume knob does not work.
Now how can I know the correct MTCD version for my device and more important - how to flash it back propery so it can all work again?
Any help is appreciated.
Thanks!
Sent from my SM-G925F using Tapatalk
spitfirebg01 said:
Hello guys.
I tried to flash the ROM of my device and now I am a bit screwed. Honestly I cannot remember what I did exactly but now I have two main problem:
- Hardware buttons LEDs do not work
- Volume knob only decreases sound no matter where you turn it to
At the moment my device is showing MTCD_GS_V21 but I am pretty sure it was not "GS" before I tried to flash it with dmcu.img and dupdate.img files at the same time.
More precisely I did the following:
I randomly downloaded two files from a topic here. I uploaded them ot a SD card and put it in the GPS slot. I went to my device > Settings > Software update and fhe device ran an update. I tried to use different ROMs after ( Malaysk and so on ) but the problems remain - no leds and volume knob does not work.
Now how can I know the correct MTCD version for my device and more important - how to flash it back propery so it can all work again?
Any help is appreciated.
Thanks!
Sent from my SM-G925F using Tapatalk
Click to expand...
Click to collapse
Hi,
I also have an Erisin ES3062 with Android 5.1.1 which is stock. The MCU is MTCD_LM_V1.56_1 (May 10 2016 19:16:12).
I hope this can help you, although you message is rather old.
Regards, Chris
Sorry if the question sounds weird, it's probably because I don't fully understand this. I know that the OnePlus 6 has two software slots, an A slot and a B slot, and I also have a vague idea about what those slots are doing during an update.
Looking around, I found a thread that recommends flashing software on both slots, saying that it could fix some issues. I'm currently on Oreo, and I'm planning to get back to 9.0.4., but I remember that during 9.0.2. I think, when I was upgrading from Oreo again, I locally installed the same update file twice. I installed it once, everything went well, I went back to the local upgrade menu after the restart, and installed it again. And the phone seemed to be faster for some reason, that's what I'm trying to achieve again.
The thread that I found mentioned how to flash the software on both slots while on TWRP, would locally installing it twice achieve the same effect? Or is there something else that I can do?
Thank you very much in advance
TheMadKing said:
Sorry if the question sounds weird, it's probably because I don't fully understand this. I know that the OnePlus 6 has two software slots, an A slot and a B slot, and I also have a vague idea about what those slots are doing during an update.
Looking around, I found a thread that recommends flashing software on both slots, saying that it could fix some issues. I'm currently on Oreo, and I'm planning to get back to 9.0.4., but I remember that during 9.0.2. I think, when I was upgrading from Oreo again, I locally installed the same update file twice. I installed it once, everything went well, I went back to the local upgrade menu after the restart, and installed it again. And the phone seemed to be faster for some reason, that's what I'm trying to achieve again.
The thread that I found mentioned how to flash the software on both slots while on TWRP, would locally installing it twice achieve the same effect? Or is there something else that I can do?
Thank you very much in advance
Click to expand...
Click to collapse
Yupp. Same effect ??
whizeguy said:
Yupp. Same effect ??
Click to expand...
Click to collapse
Thank you!
Hey guys,
I have a question for you, cause I am not familiar with the woring of the headunits. I bought an Isudar headunit, but the coreboard gave up (PX30) quite soon. Now I have a Witson coreboard in it and it's working. My problem is, although the headunit is working, the wifi and the usb doesn't. What should I do to syncronize the hardware and software of the headunit. Should I stay with the Isudar MCU and install an Isudar rom to the headunit somehow? If you have any idea, please share with me!
Thanks in advance!
UP
clorid said:
UP
Click to expand...
Click to collapse
Perhaps read through the forums - suggest the MCU cross compatibility thread - and also figure out if it matters which Android MTCD/E ROM could be applied.
I did a firmware update back to the original stock. Unfortunately the wifi and usb still not working. Do you have any idea?
Ok, so I have some news. I did a firmware update back to the original stock rom. Wifi and usb not worked. I randomly find a rom for PX30 and I flashed it to the headunit. The usb started to work, but after a few power on it's not working again. I tried to flash another mcu but it didn't work, so now back to the original. The seller said if I can't power up the head unit's wifi with the stock firmware that's a hardware issue. What do you think?
Can someone help me how can I root the head uni? It's PX30, with GS mcu, running android 9. Unfortunately I don't have wifi and the usb recognises just pendrive. Besides I can use my sd card to copy and use files. Please let me know how to root the device with this conditions! Thanks!