Hello,
I am new to modding/creating ROM's but have ok experience with android and linux themselves. I recently bought a Pumpkin android 4.4.4 head unit that has a RK3188-T SOM with 32GB nand and 2GB RAM at 1024x600. I thought it would work with malaysk's rom because it's a RK3188, but it gets stuck in a bootloop with the google stock android boot animation (the silver ANDROID with a shimmer going across). I've been trying to self teach/google how to mod the rom to make it work with my device but haven't been able to yet. I have the update.img's for both malaysk and pumpkin unpacked as well as their recovery and boot img's. I've also been trying to learn what it takes to pre-root the stock rom so I can at least get xposed up and running, but there's not really any good tutorials on that either. If anyone could help me out learning how to pre-root or how to/what to mod to get malaysk's rom working I'd be extremely grateful!!!!
Oh, also, with the unit at the boot animation, is that still the boot.img, or has boot.img passed control off to system.img at that point? Trying to narrow down where the problem is.
Thank you in advanced,
-Kyle
Your head unit unfortunately (or fortunately) is not an MTCB model, so Malaysk's MTCB ROM would never work on it.
Therefore the appropriate forum section for your question is this:
Android Head Units
or this other one should your HU's MCU version start with MTCD:
MTCD Discussion, Questions, Development
themissionimpossible said:
Your head unit unfortunately (or fortunately) is not an MTCB model, so Malaysk's MTCB ROM would never work on it.
Therefore the appropriate forum section for your question is this:
Android Head Units
or this other one should your HU's MCU version start with MTCD:
MTCD Discussion, Questions, Development
Click to expand...
Click to collapse
That might explain why even once I get the malaysk recovery up and reinstall a second time, the unit seems to boot up, but both the recovery and system are almost comletely off the left side of the screen, only about 10% is visible on the left edge of the screen. I don't even know what the options are in that recovery screen, I know there's 7 options and I've found that option one boots into system, option 3 installs the update.img, option 2 does something but not sure what, and options 4-7 bounce right back to that recovery screen. Sadly, even with adb on by default I can't get this thing to connect to my pc. So, since those roms won't work, can you tell me how to pre-root the stock rom please? I've tried all the root apk's I could find, KingRoot would work, but with it I couldn't get SuperSU binaries installed properly so it's not the right kind of root I guess. And I'd love to know how to pre-root a rom anyways! Thx a ton!
-Kyle
kjcsg said:
That might explain why even once I get the malaysk recovery up and reinstall a second time, the unit seems to boot up, but both the recovery and system are almost comletely off the left side of the screen, only about 10% is visible on the left edge of the screen. I don't even know what the options are in that recovery screen, I know there's 7 options and I've found that option one boots into system, option 3 installs the update.img, option 2 does something but not sure what, and options 4-7 bounce right back to that recovery screen. Sadly, even with adb on by default I can't get this thing to connect to my pc. So, since those roms won't work, can you tell me how to pre-root the stock rom please? I've tried all the root apk's I could find, KingRoot would work, but with it I couldn't get SuperSU binaries installed properly so it's not the right kind of root I guess. And I'd love to know how to pre-root a rom anyways! Thx a ton!
-Kyle
Click to expand...
Click to collapse
Not sure if it's the same for your unit but with MTCB head units go to settings/factory settings and when asked for the password type *#hct#root#
If you want to turn adb on go back to settings/factory settings and for the password type adbon
Goose247 said:
Not sure if it's the same for your unit but with MTCB head units go to settings/factory settings and when asked for the password type *#hct#root#
If you want to turn adb on go back to settings/factory settings and for the password type adbon
Click to expand...
Click to collapse
Unfortunately, my factory settings password entry only allows for numbers. I can't get the on screen kb to come up or the usb kb to type letters in the box.
Update: I got malaysk's rom up and running...However the touch screen is messed up (it receives input about an inch above where I tap). Then when I tried to reinstall the rom from settings with wiping it went back to the display off the left side of the screen. How I did it:
1) Install malaysk's rom from stock recovery (with "Check parameter..., E:Check failed at 0x4, Update Parameter..., Check parameter after update..." the first install part, and "E:1 parse errors" and "handle script error! ignore..." the second part)
2) Boot loop - USB kb hit ALT PRTSCR I until I get the recovery sliver on the left hand side of the screeen
3) This time I tried using the second option instead of third installing the pumpkin stock update.img and it boot looped the pumpkin boot animation
4) Reinstalled malaysk's rom using the pumpkin recovery again
5) Malaysk's rom booted up! Touch screen messed up but it booted up!
Now I'm redoing that and going to try to install the kld mcu.img's to get the touch screen working right along with the buttons and volume knob. Still no usb recognition on my pc tho sadly.
I'm trying to install the mcu img from recovery but even with the rom positioned correctly on screen the recovery is still a sliver on the left of my screen. Can someone tell me the options in recovery so I know what I'm selecting please and thank you.
Sent from my VS990 using XDA-Developers mobile app
Nvm, I found a picture online. Next question, does anyone know how to copy the mcu partition or modify mcu data? The pumpkin mcu is in bin format n the converter I have won't convert it to img because it's too big.
Sent from my VS990 using XDA-Developers mobile app
If you get it to work, please let us know here.
Well, from what I can tell, it won't work because the custom roms have different kernels causing the display to be off the screen, at least for the fused roms. I tried a non fused malaysk rom and it wasn't off the screen, but I couldn't get the mcu to work. To get the mcu to work you could try to copy the stock settings mcu update, I tried but it's over my head once I got it decompiled and tried following the code to see what it actually does when you click mcu update in the pumpkin settings. Because of kernels and reverse engineering the pumpkin mcu update are over my head for my current knowledge and understanding, I'm trying to get a refund for this unit and going to buy a joying unit since joying actively works with us, the modding community, giving us stock firmware and root and kernels and help and thus we get a much better unit and rom in the end! Joying understands the meaning of android and how it's supposed to be open source and collaborative for the community to work together to make the best goodies possible. I mean, for crying out loud, Google has gotten many of their features that they've put into their kk, lp, mm releases from us, from modders creating what they want and tuning android to it's best!!! Pumpkin, and as a related note, Verizon sucks!!! Alright, rant complete, any questions, let me know!
-kjcsg
Related
I just purchased a unit that has TV AddOns Custom Wizzard Edition that was advertised to be rooted with the latest custom rooted firmware installed. The unit shows up as having the latest 4.0 Amazon firmware on it and yet the seller says that it's a custom image and that the unit is indeed rooted. I honestly can't tell, but Super SU won't work on the unit and I'd like to downgrade the firmware to a rootable custom version and remove what he has on it to install my more familiar standard XBMC setup to it and then lock updates.
Can someone point me to a guide for downgrading the firmware or better yet removing the entire setup so that I can configure the unit in the manner to which I am accustomed to? I'd certainly appreciate any help....I honestly do not believe this unit is rooted, but he's swearing that it is and that the latest firmware that I'm seeing on it is a custom rooted firmware. I really need help here in finding out if it really is rooted and would greatly appreciate anyone's advice on downgrading the firmware or removing the setup entirely without losing root if it is in fact rooted. I'm in the dark as to cwm since I've never worked with it....
Thanks in advance for any help anyone can offer!
Use the Fresh Start program in TV Addons to remove all of the Custom Wizard stuff in XBMC.
Adb connect to the unit and then
Adb reboot recovery.. If cwm loads it's probably rooted as I don't think u can run stock Roms with it.. If it's on stock recovery.. Then u are on stock firmware.. Don't flash anything either way.. Just reboot the machine bacj to the fire os and Goto manage applications and uninstall the tv addons version. . Then side load xbmc.. Or kodi I guess it's called now. I always preferred not running any wizards that modify xbmc.. I like my splash screen the way it is thanks.
nhumber said:
Adb connect to the unit and then
Adb reboot recovery.. If cwm loads it's probably rooted as I don't think u can run stock Roms with it.. If it's on stock recovery.. Then u are on stock firmware.. Don't flash anything either way.. Just reboot the machine bacj to the fire os and Goto manage applications and uninstall the tv addons version. . Then side load xbmc.. Or kodi I guess it's called now. I always preferred not running any wizards that modify xbmc.. I like my splash screen the way it is thanks.
Click to expand...
Click to collapse
Thanks guys.... As I suspected it was not rooted......another eBay seller who either doesn't know what rooting is and simply uses it in his title since others do or is pulling a scam. It was his only unit....not a bulk seller so I think it's more ignorance than anything else. In any case....back it goes!
I appreciate your help... for a non rooted unit I actually like the Custom wizard xbmc add on....being pre configured makes it quick and simple to load a unit and not have to change too much to have what you want. Different story on a rooted unit.... I have a backup that loads with all the repos and shortcuts already installed. It's almost as quick as using the wizard edition and is setup to exactly what I personally want.
As always though.... it was great to get a quick and accurate response from those who know so much more about this than I.
Thank you again!
fxbill said:
Thanks guys.... As I suspected it was not rooted......another eBay seller who either doesn't know what rooting is and simply uses it in his title since others do or is pulling a scam. It was his only unit....not a bulk seller so I think it's more ignorance than anything else. In any case....back it goes!
I appreciate your help... for a non rooted unit I actually like the Custom wizard xbmc add on....being pre configured makes it quick and simple to load a unit and not have to change too much to have what you want. Different story on a rooted unit.... I have a backup that loads with all the repos and shortcuts already installed. It's almost as quick as using the wizard edition and is setup to exactly what I personally want.
As always though.... it was great to get a quick and accurate response from those who know so much more about this than I.
Thank you again!
Click to expand...
Click to collapse
glad you got it all straightened out. you can still adb push your backup files on a clean xbmc install.. so you just sideload xbmc then adb push your backup to the correct location, i forget that exact location at the moment tho.. theres alot of good instructions on the xbmc wiki. http://kodi.wiki/view/Amazon_Fire_TV#Copying_files . the xbmc backup addon also works from what i was reading, i havent personally tried it myself.
Hi guys,
I have a problem, my eonon is in bootloop after i have install a new rom but I have no idea what the key combination to enter in recovery mode...
Pls help me!!!
Thanks!
thefaber said:
Hi guys,
I have a problem, my eonon is in bootloop after i have install a new rom but I have no idea what the key combination to enter in recovery mode...
Pls help me!!!
Thanks!
Click to expand...
Click to collapse
Press the reset button.
Press both Power and Home button for about 15 seconds.
Release both and press Power again.
The unit will boot into recovery.
Very very thanks!!!
m00n61 said:
Press the reset button.
Press both Power and Home button for about 15 seconds.
Release both and press Power again.
The unit will boot into recovery.
Click to expand...
Click to collapse
Thanks for the advice, and a little more if you have it. Where could I find the original firmware file for the Eonon G2110F unit? Mine seems to have an issue with one part of the OS, namely the reversing camera which doesn't seem to be working, even after all wiring was installed correctly. Cheers in advance...
djshotty said:
Thanks for the advice, and a little more if you have it. Where could I find the original firmware file for the Eonon G2110F unit? Mine seems to have an issue with one part of the OS, namely the reversing camera which doesn't seem to be working, even after all wiring was installed correctly. Cheers in advance...
Click to expand...
Click to collapse
You can request it from EONON customer support. They are pretty responsive. The only problem is you can never know what will they send you
Alternately, you can either install a firmware suitable for your unit from the huifei server (look in Malaysk's signature for the link) or go with one of the custom ROMs - Booroondook's or Malaysk's. Both are waaaaaay better than any factory firmware.
m00n61 said:
You can request it from EONON customer support. They are pretty responsive. The only problem is you can never know what will they send you
Alternately, you can either install a firmware suitable for your unit from the huifei server (look in Malaysk's signature for the link) or go with one of the custom ROMs - Booroondook's or Malaysk's. Both are waaaaaay better than any factory firmware.
Click to expand...
Click to collapse
I pretty much posted that question without going looking for answers first. All good, my unit is now running the rooted Lollipop ROM that Malaysk cooked. Thanks to all who made such an update possible, I now have a car stereo which pretty closely resembles my Galaxy S6 that's running stock rooted Marshmallow...
Do you have a link to the ROM you used?
asianmulder said:
Do you have a link to the ROM you used?
Click to expand...
Click to collapse
Here:
https://forum.xda-developers.com/showthread.php?t=3246370
Can you help me please?
Does anyone know what is the combination of keys to enter in recovery mode (boot menu) on eonon GA7165S? Thank you
It remains stuck on eonon logo picture after the text "optimizing app xx of xx"
It is not the same h/u
It is other model. Mine is eonon ga7165s and has android 6. And i ve tryied the key combination written above and many other but still not entering in recovery mode.
Ps: someone says that my hu is mtcd not mtcb ( i dont know what that means and which are the differences). Soryy if i said smthing stupid.
hi,
I bought an used Eonon G2110F, MTCB, rk3188 800x480, was came with on board a Malaysk 4.4, I tried to install the update to 5.1 but after few days recognize more bugs.
so decided to install an update to 7.1 do all wipes, but the update no works because I used a wrong rom.
now, my Eonon never stars in recovery, tried more combinations but nothing, I’m unable to create an sdbootable, because the software Sd software update 1.4 stopped during the process, I dowloaded others suite and tried on other pc, but always the same result.
anyone have a solution for me?
sorry for my english,
maurizio
mzampa said:
hi,
I bought an used Eonon G2110F, MTCB, rk3188 800x480, was came with on board a Malaysk 4.4, I tried to install the update to 5.1 but after few days recognize more bugs.
so decided to install an update to 7.1 do all wipes, but the update no works because I used a wrong rom.
now, my Eonon never stars in recovery, tried more combinations but nothing, I’m unable to create an sdbootable, because the software Sd software update 1.4 stopped during the process, I dowloaded others suite and tried on other pc, but always the same result.
anyone have a solution for me?
sorry for my english,
maurizio
Click to expand...
Click to collapse
You cant install Android 7.1 roms on MTCB head units, you can use any MTCB Android 4.4 or at maximum 5.1.1 roms
mzampa said:
I decided to install an update to 7.1 do all wipes, but the update no works because I used a wrong rom. Now, my Eonon never stars in recovery, tried more combinations but nothing.
Anyone have a solution for me?
maurizio
Click to expand...
Click to collapse
Well, have you tried installing a Quick Start app. on the device? Because the stock ROM you currently have going is pre-rooted, you can put onto the head unit an app. which gives you choice of restart, either normal restart, restart into Recovery or restart into Download mode. All you need do is give the app. Superuser permissions. Here is one of the best restart apps on Google Play Store...
Code:
[URL="https://play.google.com/store/apps/details?id=com.antaresone.quickreboot&hl=en"]https://play.google.com/store/apps/details?id=com.antaresone.quickreboot&hl=en[/URL]
Oh, and 99.9% of the time an install of a Nougat ROM on your device will fail, because
iRcKenny said:
You can't install Android 7.1 ROMs on MTCB head units, you can use any MTCB Android 4.4 or at maximum 5.1.1 ROMs
Click to expand...
Click to collapse
hi,
thanks for yours replies, now termine to check the system, all it’s ok, but the HU doesn’t turn on.
I think to have bricked the HU, the current, directly and under key are ok, tried various mode to restart,
also connect to pc, but don’ t recognize the HU. are dead!
solution?
regards
maurizio
mzampa said:
hi,
thanks for yours replies, now termine to check the system, all it’s ok, but the HU doesn’t turn on.
I think to have bricked the HU, the current, directly and under key are ok, tried various mode to restart,
also connect to pc, but don’ t recognize the HU. are dead!
solution?
regards
maurizio
Click to expand...
Click to collapse
Maybe this post can help you
pumpkin nd0294b
i brick my pumpkin nd0294b ( px5 with oreo 8.0 mcu like in attached photo)and i can't enter in recovery mode just freeze . any idea? thanks
Please rom greek
treliarhs7 said:
Please rom greek
Click to expand...
Click to collapse
Eonon G2110f
Hello everyone, I'm looking at installing Malaysk rom on my Android Car head unit i imported. However i see all this discussion about MTCB/MTCD and nothing about MTCC. which Rom should i use? Will it be compatible? Any help would be greatly appreciated.
Brand
ROCKCHIP rk3188
MCU version
MTCC-KLD6-V2.91
Android version
5.1.1
1024*600
Kernel version
3.0.101+
[email protected] #42
Tue May 17 21:50:34 CST 2016
Build number
rk3188-userdebug 01062016:18:49:08
Model number
S07
CPU
ARM [email protected] (x4)
Memory
1024 MB
Hi Yabbie
I just recieved one of these at the weekend from Pumpkin, but the lower resolution screen
From the reading i have done I beielve these are MTCB units but have a new MCU , v 2.91, and for some reason they are now being indentified as MTCC - maybe a proper expert in here can clarify that.
I have sucessfully flashed a MTCB Malaysk 5.11 ROM , make sure you get the correct resolution for your screen but these do work. Do NOT try to change the MCU - the version we have appears to be the most recent but again that would need confirming by expert.
I installed into a BMW E92 and its working well, have DAB+ adapter as well ( from Joying , you need to download there .apk to get i working )
Cheers
ferrari312_uk said:
Hi Yabbie
I just recieved one of these at the weekend from Pumpkin, but the lower resolution screen
From the reading i have done I beielve these are MTCB units but have a new MCU , v 2.91, and for some reason they are now being indentified as MTCC - maybe a proper expert in here can clarify that.
I have sucessfully flashed a MTCB Malaysk 5.11 ROM , make sure you get the correct resolution for your screen but these do work. Do NOT try to change the MCU - the version we have appears to be the most recent but again that would need confirming by expert.
I installed into a BMW E92 and its working well, have DAB+ adapter as well ( from Joying , you need to download there .apk to get i working )
Cheers
Click to expand...
Click to collapse
Thanks so much for your reply, have just flashed MTCB Malaysk 5.11 ROM also and all is work as expected very happy
Ive noticed my button LED lights are not working , the screen still dims when i put the car lights on but the LEDs don't light up. Also the option to change the colors in settings is missing, i believe it was called Elements. any ideas?
note: when i enter recovery mode they come on in the menu.
Kind regards Yabbie
YabbieAu said:
Ive noticed my button LED lights are not working , the screen still dims when i put the car lights on but the LEDs don't light up. Also the option to change the colors in settings is missing, i believe it was called Elements. any ideas?
note: when i enter recovery mode they come on in the menu.
Kind regards Yabbie
Click to expand...
Click to collapse
Hi YabbieAu, I just got exactly same firmware version as you. Do you have other issues apart from above one after installing Malaysk ROM MTCB?
paulnorinn said:
Hi YabbieAu, I just got exactly same firmware version as you. Do you have other issues apart from above one after installing Malaysk ROM MTCB?
Click to expand...
Click to collapse
Apart from that I've had no issues with the rom , if i change RGB option to just G in Factory Settings and reboot the head unit the elements option returns under settings. In the elements menu i can get every colour working again expect red/yellow.
YabbieAu said:
Apart from that I've had no issues with the rom , if i change RGB option to just G in Factory Settings and reboot the head unit the elements option returns under settings. In the elements menu i can get every colour working again expect red/yellow.
Click to expand...
Click to collapse
Cool, I think I am going to try it soon.
Meanwhile, did you have a chance to get root working on original firmware? I just try it with Kingroot and did not seem to work...
Hi.
I've just installed the Auto Pumpkin MTCC KLD6 V2.91 into my Mondeo and was looking for ROM/ROOT options when I came across this thread
YabbieAu, Did you stick with the Malaysk ROM? How is it doing now?
The main reason I want to root and use a custom ROM is to get a better DAB+ app (I am trying some out on the stock ROM to see if any work first though) and to re-map some of the hardware buttons. I bought the DAB+ box from Auto Pumpkin and it works well, it's just that nasty GUI I want to change!
Hi guys,
I have just installed Malaysk ROM on my unit, I chose this one -> http://forum.xda-developers.com/and...rom-malaysk-roms-lollipop-5-1-1-mtcb-t3394209
and so far so good! I find boot time is quicker than the factory ROM. Also see a lot of feature that I can play with.
paulnorinn said:
Hi guys,
I have just installed Malaysk ROM on my unit, I chose this one -> http://forum.xda-developers.com/and...rom-malaysk-roms-lollipop-5-1-1-mtcb-t3394209
and so far so good! I find boot time is quicker than the factory ROM. Also see a lot of feature that I can play with.
Click to expand...
Click to collapse
I tried the same ROM for an MTCC device (1024x600) and can also confirm that is running very well
Bluetooth with Android 6.0.1
I have MTCC-KLD6-V2.97. I'm having issues with the bluetooth connecting to a Galaxy phone that has 6.0.1.
When i connect the phone via bluetooth, the bluetooth icon shows at the top of the screen then disappears after 5-10seconds. I can see on the phone that when it connects initialy it connects for Call Audio (HSP) and Media Audio (A2DP). After 5-10 seconds the phone shows that HSP is off leaving A2DP on. The Phone shows its still connected via bluetooth. No calls go through to the head unit.
Has anyone had this working with an Android 6.0.1 Phone? I was thinking maybe I should try Malaysk's ROM however I'm unsure if its an OS,MCU or Hardware issue. Any help or ideas would be appreciated.
I have the exact same issue. I'm also using a Note7 running 6.0.1. I'm running a Malaysk 5.1.1 ROM on my HU and having the same problem you described. Hoping there is a way to make this work in the future.
sixstrum said:
I have the exact same issue. I'm also using a Note7 running 6.0.1. I'm running a Malaysk 5.1.1 ROM on my HU and having the same problem you described. Hoping there is a way to make this work in the future.
Click to expand...
Click to collapse
I've been doing a bit of research. While I don't know for sure it looks as if the issue lies with the MCU. I think the Bluetooth drivers are in there. Sadly I'm running the latest version. The supplier is going to talk with the factory who made it but don't like my chances.
moodie007 said:
I've been doing a bit of research. While I don't know for sure it looks as if the issue lies with the MCU. I think the Bluetooth drivers are in there. Sadly I'm running the latest version. The supplier is going to talk with the factory who made it but don't like my chances.
Click to expand...
Click to collapse
Likely shouldn't get our hopes up, but if you hear any good news please let me know!
sixstrum said:
Likely shouldn't get our hopes up, but if you hear any good news please let me know!
Click to expand...
Click to collapse
Here is an interesting update...... Ive just tried an Experia Z3 running Android 6.0.1...... It connected and maintains both Call and Media connections. What does that tell us.......
Sorry I've hijacked this thread. I've setup a new one in relation to my issue. Thanks.
http://forum.xda-developers.com/and...id-6-0-1-phone-bluetooth-issue-t3471331/page1
YabbieAu said:
Hello everyone, I'm looking at installing Malaysk rom on my Android Car head unit i imported. However i see all this discussion about MTCB/MTCD and nothing about MTCC. which Rom should i use? Will it be compatible? Any help would be greatly appreciated.
Brand
ROCKCHIP rk3188
MCU version
MTCC-KLD6-V2.91
Android version
5.1.1
1024*600
Kernel version
3.0.101+
[email protected] #42
Tue May 17 21:50:34 CST 2016
Build number
rk3188-userdebug 01062016:18:49:08
Model number
S07
CPU
ARM [email protected] (x4)
Memory
1024 MB
Click to expand...
Click to collapse
Sorry for posting on wrong thread. :crying:
E:Failed to mount /cache /dev/block/rknand_cache (block dev required)
I have recently acquired the same unit as YabbieAu.
I've just attempted to install Malaysk ROM however its turned to poo.
After it rebooted it took a long time but eventually loaded... sort of. Loaded as a black screen. Top tool bar but no launcher. Buttons don't work and it reboots after about 30 seconds.
If I boot to recovery I can not recover from SD. I get error messages. E:Failed to mount /cache /dev/block/rknand_cache (block dev required)
Other error message are related. i.e. cant open or mount cache etc due to the fact the /cache symbolic link could not be mounted.
It appears the cache partitions need to be re-created?
Can anyone assist?
YabbieAu said:
Hello everyone, I'm looking at installing Malaysk rom on my Android Car head unit i imported. However i see all this discussion about MTCB/MTCD and nothing about MTCC. which Rom should i use? Will it be compatible? Any help would be greatly appreciated.
Brand
ROCKCHIP rk3188
MCU version
MTCC-KLD6-V2.91
Android version
5.1.1
1024*600
Kernel version
3.0.101+
[email protected] #42
Tue May 17 21:50:34 CST 2016
Build number
rk3188-userdebug 01062016:18:49:08
Model number
S07
CPU
ARM [email protected] (x4)
Memory
1024 MB
Click to expand...
Click to collapse
moodie007 said:
I have recently acquired the same unit as YabbieAu.
I've just attempted to install Malaysk ROM however its turned to poo.
After it rebooted it took a long time but eventually loaded... sort of. Loaded as a black screen. Top tool bar but no launcher. Buttons don't work and it reboots after about 30 seconds.
If I boot to recovery I can not recover from SD. I get error messages. E:Failed to mount /cache /dev/block/rknand_cache (block dev required)
Other error message are related. i.e. cant open or mount cache etc due to the fact the /cache symbolic link could not be mounted.
It appears the cache partitions need to be re-created?
Can anyone assist?
Click to expand...
Click to collapse
All good. I fixed it. Obtained latest image from supplier ver 2.97 Aug 02 2016
Removed unit from car. Connected USB cable to front USB port of head unit and other end to laptop.
Downloaded and installed RockChip Driver assistant v4.4 on laptop.
Downloaded RockChip Factory Tool v1.39 on laptop.
Applied power to yellow wire only (no acc) while holding power button. Once computer saw USB connection let go of power button. Screen remains black on head unit. This is bootloader mode.
Ran Factory Tool and and used the restore option to restore the update.img file provided by the supplier.
Once restore completed powered off and applied power to both yellow and red wires - power and acc.
Let unit complete boot. Took some time to do fresh install of apps etc.
All fixed.
moodie007 said:
All good. I fixed it. Obtained latest image from supplier ver 2.97 Aug 02 2016
Removed unit from car. Connected USB cable to front USB port of head unit and other end to laptop.
Downloaded and installed RockChip Driver assistant v4.4 on laptop.
Downloaded RockChip Factory Tool v1.39 on laptop.
Applied power to yellow wire only (no acc) while holding power button. Once computer saw USB connection let go of power button. Screen remains black on head unit. This is bootloader mode.
Ran Factory Tool and and used the restore option to restore the update.img file provided by the supplier.
Once restore completed powered off and applied power to both yellow and red wires - power and acc.
Let unit complete boot. Took some time to do fresh install of apps etc.
All fixed.
Click to expand...
Click to collapse
Were you able to install Malaysk ROM?
Hey guys,
sorry if my english isn't right but I am so tired so now and so frustrated that I don't know what I could do.
The story is simple: I have a android head unit, running allwinner t3 (aka R40) with stock rom and stock recovery.
So far, there isn't any custom recovery available (I would like to create/compile CWM but CWM-Builder have some 502 Bad Gateways...) and the only way to root on 4.4.2 is with 360Root (On 6.0.1 for the newer Models only with Kingroot).
So far not bad but it takes a lot of patience sometimes and sometimes you can try over 1 week every day many hours and it still don't work!
So where do I need help? I want to add Root/SuperSU/... manually but I have many limitation.
First one is that I can only modify the system.img without any chmod and else (Maybe because I am using windows? Maybe because the Firmware has to be flashed while the Head Unit is powered off aka "Dead flash")
Secondly, ADB is not working, to be honest, the head unit act only as a receiver! It accepts any devices like Keyboard, UMTS/WCDMA Stick, USB Stick, ... but MTP fom HeadUnit or ADB, ... don't work. The only way for ADB is ADB over Wifi but I don't know whether it's good or bad. I saw that the USB is plugged into a slot which seems to be bend out, maybe they plugged it in wrong? I don't know how I can test that but I heard that connecting two devices with wrong polarity will break at least one of them!
Thirdly is, that I can't notice a difference between a rooted stock rom and a unrooted stock rom.
According to WinMerge, the rooted ROM have two new files (/etc/install-recovery.sh and /bin/su) but that's it!
If I transfer those files to my custom ROM with the same rooting app, it wont recognize them! I can try and try until I die.
And last, maybe worst, I can't just update something over. Every change outside the Android OS is mainly done by flashing the whole firmware! They changed that policy a little bit after Android 6.0.1 but this Android have the worst stability, worst GPS Modules and completely bricked Bluetooth! Also the stock recovery on 4.4.2 is useless, touch isn't working and the touch-buttons are also not working. I also tried to use a usb keyboard but also useless. Only the 6.0.1 stock recovery recognizes the touch screen and the touch-buttons but as I said, the Android 6 is terribly made...
I know what it sound like a noob and I didn't provided much information but I want to know whether someone can help me or want to help me... maybe someone say that I have to provide information xyz so yeah, feel free to ask
Best regards
Pascal
At what point did you install the ADB device drivers (kinda important) for your device, so that when you plugged it into anything, the thing could register you were plugging in the HeadUnit......
Hello all,
I've run into an issue with my new head unit. I was just trying it out before installing it, got it powered up from my bench supply to test, and as soon as I installed a couple of apps (Plex and Google Play Music) it started bootlooping on me.
I figured I would go ahead and install a CFW since I do that for all my android devices anyway, but I've gotten myself into a pickle now. I can prompt the unit to attempt a firmware update, but all of the firmware releases I've found are in nupdate.img format, and the recovery is looking for a "kupdate.zip" format. I did try using the SD_Firmware_Tool to build an sdcard for this, but it seems to just be getting ignored.
The current behavior is that I get the "Pumpkin" bootloader logo, then it reboots. It no longer even shows the "android" loading screen as It did before I tried using the SD_Firmware_Tool.
For reference, I was trying to use the Hal9k rom from here
Getting to the onboard update menu works by holding the power button (pushing down the volume wheel) and hitting the reset button. I haven't been able to get it to boot into any other recovery modes yet, but if anyone happens to know of another button combo that should be working, please let me know.
I've put in an email to pumpkin support but I have a feeling they'll take a while to get back to me with the firmware, so hoping someone else might have something I can use in the meantime.
Well apparently I was mistaken about what CPU is under the hood of this thing (was going by a user review on the amazon page where I purchased it.)
According to the recovery it's loading into, this has an RK3368 rather than the RK3188 I expected
Little Update:
I'm trying out this unbrick for the PX5 to see if I can get it to use a more robust recovery. The current one keeps trying to mount a nonexistant drive location to run the kupdate.zip, and most of the pictures I've found of people's recoveries floating around on here have had the option to choose update files from different locations, so I think the recovery on this needs an update.
It's so far booting to a black (backlight on) screen and not progressing, so I hope the firmware update is going in the background and I just need to wait it out. Anyone know how long that firmware update process should take?
well I think my unit may just be new or different somehow, as none of the unbrick metbods seem to be working at the moment.
I've attached some pics of the unit's internals to see if that can help find a solution
How have you ascertained it to be an MTC(D/E) - it isnt
marchnz said:
How have you ascertained it to be an MTC(D/E) - it isnt
Click to expand...
Click to collapse
I suppose there were some assumptions made based on what's already available on the market.
If it's not an MCT(#) then what is it?
Pyr0ball said:
I suppose there were some assumptions made based on what's already available on the market.
If it's not an MCT(#) then what is it?
Click to expand...
Click to collapse
An XDA search for [kupdate] yeilds the information.
Made some progress on figuring this module out