Hi!
I have an MTC Unit with android 4.4, RK3188 processor, 7 inches, and it's already rooted. I want to know a few things:
1) I don't have physics buttons, how can I get into the recovery mode?
2) How can I know if my unit is MTCB, MTCD or MTCC?
3) If I have android 4.4 can I install android 5.1 with Malaysk ROM?
4) If I want to install Malaysk ROM, I have to use 800x480 or 1024x600?
5) Is there any way to use NAND flash memory to install apps, without install any custom ROM?
Thank's for your help!
Regards.
Related
I have a Pumpkin KD-C0109-US-A HU. It is a single DIN in which the android screen rolls out and flips up. I addition to the screen it has a radio LED display that shows data like input source, RDS etc. The problem is that when I install Malaysk custom firmware, the radio LED's never indicate that the upgrade process is completed. The letters INIT and the recovery mode graphics continue indefinitely even though the radio works and Malaysk's version of Android functions well. Is there some incompatability between the firmware and the MCU for this type of dual display arrangement? The MCU is MTCB-KLD5-V2.77. Is there a work around? Thanks.
The MTC apps are the ones that interface with the hardware. I'd suggest trying to extract them from stock rom and then install to custom rom
Brendo said:
The MTC apps are the ones that interface with the hardware. I'd suggest trying to extract them from stock rom and then install to custom rom
Click to expand...
Click to collapse
We need to first find a working stock ROM that hasn't been flashed over! Most of us flashed MalaySK before realizing that the LED wouldn't work, and don't have a proper image backup of the stock ROM.
That said, on the other thread, someone pointed out that the factory image available for download at http://huifei.fs-fileserver.de/cont...D 4.4.4/800x480/KLD 800x480 20150820 Factory/ restores functionality.
That's funny, because that is basically the same base that MalaySK has been using!
I have diffed that ROM with MalaySK's ROM. One difference that might bear investigation
MTCOEM3.APK -> on the "working" Rom.
MTCOEM4.APK -> on MalaySK. So obviously MalaySK is *NOT* based exactly on the rom linked above. It has a "newer" MTCOEM, which one would think wouldn't remove support for a relatively new feature? However, it's possible that MTCOEM3 would fix the problem.
There are a lot of edits of course done by MalaySK so I can't tell what he's done -vs- difference in the base Roms.
However, they ARE slightly different builds despite having the same build# according to build.prop:
MalaySK:
# Do not try to parse ro.build.description=rk3188-eng4.4.4 18092015.12:05:40
ro.build.description=rk3188-eng4.4.4 18092015.12:05:40
Stock:
# Do not try to parse ro.build.description=rk3188-eng4.4.4 20082015.17:14:44
ro.build.description=rk3188-eng4.4.4 20082015.17:14:44
Although both are labeled as 20150820, you can see that the actual build description is later on the second ROM.
Note (Probably important): I did thankfully screenshot my stock firmware before updating, and my flip-out KLD unit did indeed ship with 20082015.17:14:44... So even though I haven't tried it, I'm willing to bet money that it will indeed fix the issue as the other user has stated. The question is - what's different in those two builds? I don't have an original of 18092015.12:05:40 to diff against the other. But I bet MalaySK does.
I'm also curious if this ROM: EONON2_rk3188_p(20151019).rar (from the factory firmware thread) will operate the LED?
I have been out of the ROM developing game for several years, so I'm rusty on all this, however. Hoping MalaySK can find something obvious, but if not, I'm working on it.
lotherius said:
We need to first find a working stock ROM that hasn't been flashed over! Most of us flashed MalaySK before realizing that the LED wouldn't work, and don't have a proper image backup of the stock ROM.
That said, on the other thread, someone pointed out that the factory image available for download at http://huifei.fs-fileserver.de/cont...D 4.4.4/800x480/KLD 800x480 20150820 Factory/ restores functionality.
That's funny, because that is basically the same base that MalaySK has been using!
I have diffed that ROM with MalaySK's ROM. One difference that might bear investigation
MTCOEM3.APK -> on the "working" Rom.
MTCOEM4.APK -> on MalaySK. So obviously MalaySK is *NOT* based exactly on the rom linked above. It has a "newer" MTCOEM, which one would think wouldn't remove support for a relatively new feature? However, it's possible that MTCOEM3 would fix the problem.
There are a lot of edits of course done by MalaySK so I can't tell what he's done -vs- difference in the base Roms.
However, they ARE slightly different builds despite having the same build# according to build.prop:
MalaySK:
# Do not try to parse ro.build.description=rk3188-eng4.4.4 18092015.12:05:40
ro.build.description=rk3188-eng4.4.4 18092015.12:05:40
Stock:
# Do not try to parse ro.build.description=rk3188-eng4.4.4 20082015.17:14:44
ro.build.description=rk3188-eng4.4.4 20082015.17:14:44
Although both are labeled as 20150820, you can see that the actual build description is later on the second ROM.
Note (Probably important): I did thankfully screenshot my stock firmware before updating, and my flip-out KLD unit did indeed ship with 20082015.17:14:44... So even though I haven't tried it, I'm willing to bet money that it will indeed fix the issue as the other user has stated. The question is - what's different in those two builds? I don't have an original of 18092015.12:05:40 to diff against the other. But I bet MalaySK does.
I'm also curious if this ROM: EONON2_rk3188_p(20151019).rar (from the factory firmware thread) will operate the LED?
I have been out of the ROM developing game for several years, so I'm rusty on all this, however. Hoping MalaySK can find something obvious, but if not, I'm working on it.
Click to expand...
Click to collapse
I think that you are on the right track but I lack the expertise to figure this one out. I am the someone that pointed out the factory image that solved the problem. I will help in any way that I can to get this problem solved.
windseye said:
I think that you are on the right track but I lack the expertise to figure this one out. I am the someone that pointed out the factory image that solved the problem. I will help in any way that I can to get this problem solved.
Click to expand...
Click to collapse
I think the best option would be to run the factory firmware with a 2gb partition. Will test that over this weekend.
I confirmed that the latest "factory firmware" on the HuiFei unit (20150821) functions correctly with the LED display on our single-DIN KLD units. Others reported that the 20150820 download from the same site works as well.
MalaySK uses a 20150820 base that has a slightly earlier timestamp by a few hours. So either his earlier build doesn't support it, or one of the changes he has made has broken support for the LED.
Our units ship with the later 20150820 build and 20150821 build that has been confirmed to be working from the HuiFei firmware site (http://huifei.fs-fileserver.de/cont....4/800x480/KLD 800x480 20150821 DSA Modified/). The 20150821 (dunno about the 820) already has the 2GB partition mod and root, so it's ready to roll.
I don't think I'm going to test further, as I installed the 20150821 from DAS and it has the 2GB partition I wanted, and everything is working. I didn't try the newer build (20151019).
But with that said, I think this thread isn't going to be necessary as the standard KLD Roms *DO* support our single-DIN LED Display - it is just MalaySK that does not.
Yep, it all comes down to narrowing down what software is required to interface
I wonder if you installed working rom and replaced mtcradio with stock or custom version (or one from malaysk rom) if led still works. If it does, there must be another app in the background required (eg. mtcoem)
Brendo said:
Yep, it all comes down to narrowing down what software is required to interface
I wonder if you installed working rom and replaced mtcradio with stock or custom version (or one from malaysk rom) if led still works. If it does, there must be another app in the background required (eg. mtcoem)
Click to expand...
Click to collapse
Well personally I got it working buy using one of the "stock" roms with 2gb, so I'm satisfied for now. If anyone else wants to play with it further they can.
Found a workaround for the "Init- Problem" of the custom ROMs of MalaySK:
Install the Custom ROM normally.
Then edit the file "build.prop" in the /system directory:
- find the line "ro.product.customer=HCT4" and replace HCT4 with KLD
- reboot device
with that my display was showing the correct things again :laugh:
(tested with the ROM from 17.03.2016)
hope that helps
mgh33 said:
Found a workaround for the "Init- Problem" of the custom ROMs of MalaySK:
Install the Custom ROM normally.
Then edit the file "build.prop" in the /system directory:
- find the line "ro.product.customer=HCT4" and replace HCT4 with KLD
- reboot device
with that my display was showing the correct things again :laugh:
(tested with the ROM from 17.03.2016)
hope that helps
Click to expand...
Click to collapse
Great solution. Definetly will try that.
Any ideea if the MCU for this one-din units is a special one? I installed MTCB-KLD-V2.78 from (HuiFei Server) and now I cannot control the flip-up screen. My unit is MTCB KLD one-din with Android 4.4.
I bought a "Joying" lookalike unit on Aliexpress
The problem is now it has no recovery so can't change software
if i press power button and res then it boots in like a "red line bar with start update in right corner" but it does nothing with the update.img
in android when i try to flash a recovery like TRWP it tells me there is "NO recovery partition"
can someone help me out?
some pic of unit klik HERE
This does not look like a MTCB headunit - it does not have one of the CPU's or MCU's that these MTCB (formally known as HuiFei) units have. I don't think you will be able to use any of the ROM's in these forums.
it has a RK3188 cpu like other units..
Doesn't matter what cpu it has. If it's not an MTCB unit then these ROMs won't work.
Try googling the MCU type for help
Sent from my SM-G920F using Tapatalk
it's a unit based on http://4pda.ru/forum/index.php?showtopic=707069
see this thread on XDA
Allwinner R16 Cortex A9 Quad Core 1.6GHz
The firmware there works on the unit.
Now running the Navi IQ firmware and thats way better.
Greetings everyone. I wish to know more about flashing Resurrection Remix...
I watched the brief instruction on official XDA thread but I wish to know more detail...
- Current Phone Status -
My G3 D855, 32 GB memory, is running stock Android 4.4.2, ROM version “V10n-HKG-XX”, stock recovery, rooted with PurpleDrake (script by xda developer”. Kernel version 3.4.0. All things are stock except I have rooted, with SuperSU.
- Reason of wanting to flash Remix ROM -
I wish to change resolution to 1080x1920, even 720x1280. So I did this using build.prop editing and “wm size 1080x1920”，“wm density 480”. However in stock rom, build in LG apps like Phone, Messaging, Calender will crash. I fix this by installing Xposed & app settings with DPI 530. But I don’t quite want this to be the solution...
Plus I noticed there really are battery difference between 1440x2560 and lower resolution. So I started to think about custom Rom. I found that Resurrection Remix and Paranoid Android are quite slim, good looking, most importantly very customizable.
And Stock ROM has many software that I don’t need, so I wish to give it a try.
- My question -
I haven’t flash any custom rom before (I have flashed on my previous phone but messed up quite a bit).
- So I wished to know what is the prerequisite, anything that need to pay good attention into? I want to avoid bootloop or hard brick...
- Should I install official TWRP recovery on my current status and make a full system backup image? (is that called nandroid backup?)
- If any error occured, can I use TWRP recovery to restore everything in my current status (everything in stock but have root access)?
- Are the custom roms contain build-in Root access? Because I want the phone to be rooted.
- I use LG Flash tool 2014 to flash stock firmware kdz files), with CRC method to completely wipe the phone and back to stock. Is this method still applicable if I want to back to stock after flashing RR rom? Because I want everything to be clean each time I flash a new system...
- I watched YouTube video that changing AOSP rom resolution won’t mess up icons or apps. So I can still receive SMS, dial, calender sync to Google etc. Correct?
--------------------
Finally, I wish to flash the latest STABLE version of the Remix ROM / Paranoid Android ROM. Would be good to hear some recommendations. I wish things to be more customizable and slim. Thanks for reading this long article in advance!
Hello. At the beginning, I apologize for my English but I support myself with translator :RE.
Which ones do you recommend the best rom for my equipment? I will depend on the speed of action and the elimination of the 1gb application memory limit. Mtu update?
I will be very grateful for link to the recommended rom.
My equipment is:
S07
MTCB-ZD-V2.79
ANDROID 4.4.4
rk3188
kernel 3.0.36+, [email protected] #1443
cpu ARM [email protected] (x4)
resolution 800*480
RAM 1024
Hello,
Having a very similar unit with only 1GB memory, I would advise keeping a 4.4.4 Android version. I have tried several 5.1 roms but they become all laggy after some usage time.
sharinn said:
Hello,
Having a very similar unit with only 1GB memory, I would advise keeping a 4.4.4 Android version. I have tried several 5.1 roms but they become all laggy after some usage time.
Click to expand...
Click to collapse
Thank you for the advice, I expected it. And what rom 4.4.4 do you use now? Which one of the best you've ever done? Have you updated mtu? Is it worth updating them or is it better to change and change only rom?
Try the malaysk 4.X version, it works for me ( with the same HU, only 1GB ) perfect, the 5.x is much slower on it
I’ve been trying to find a 4.4.4 rom for mine but I keep running into dead links. Do you know where I can find one please?
Markyo96 said:
I’ve been trying to find a 4.4.4 rom for mine but I keep running into dead links. Do you know where I can find one please?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=3246370
ups, is down, i will upload the 4.x RK3188 / 1024 on share online, it takes some time, i have only 1Mbit upload
http://www.share-online.biz/dl/SBRM61NPEU9
klaralang said:
https://forum.xda-developers.com/showthread.php?t=3246370
ups, is down, i will upload the 4.x RK3188 / 1024 on share online, it takes some time, i have only 1Mbit upload
http://www.share-online.biz/dl/SBRM61NPEU9
Click to expand...
Click to collapse
Hey Guys, i know its 2023 and i am replying to the very old thread. If anyone had the live link to download 4.x RK3188 /1024 rom, please share, i will be very gratefull. Thanks.
Hello:
As this is my first posting, I hope I'm doing it correctly:
I have a Samsung Galaxy S4 Mini SGH-i257 (AT&T version). The unit is both unlocked (open lock symbol appears on the screen at each start-up) the unit is also Rooted I have Root Explorer, SuperUser, & APK Installer in my Apps. I want very much to upgrade the unit from KitKat 4.4.2 up to at least Lollipop or Marshmallow, so I am able to use several Apps. that are not compatible with KitKat.
Can someone provide me a link for the proper custom ROM?
You can use any i9195 rom on the i257/i257m
sequeens said:
Hello:
As this is my first posting, I hope I'm doing it correctly:
I have a Samsung Galaxy S4 Mini SGH-i257 (AT&T version). The unit is both unlocked (open lock symbol appears on the screen at each start-up) the unit is also Rooted I have Root Explorer, SuperUser, & APK Installer in my Apps. I want very much to upgrade the unit from KitKat 4.4.2 up to at least Lollipop or Marshmallow, so I am able to use several Apps. that are not compatible with KitKat.
Can someone provide me a link for the proper custom ROM?
Click to expand...
Click to collapse
i know its been awhile , but do you have a link or instructions on rooting , installing twrp , etc?
would be super helpful & appreciated.
all the best for you and yours ,
dave