Related
Hello everyone,
I have bought various Android TV boxes in the past, and haven't had problems getting them up and running.
I recently ordered 2 chinese models from eBay however, which are giving me nothing but grief. I apologize in advance for such a loooong post, but I am at my wits end and I am really hoping someone can help me out.
The action was for this model here:
www.ebay.com.au/itm/231275032090
It appeared to be a pretty standard model, like a Justop 4.0, but with a hard switch where the optical should be, and a cut down remote.
Firstly, the Specifications according to the auction:
1GB ddr3
4GB nand flash
Allwinner A20 dual core 1GHz CPU
On closer inspection after receiving the unit, an additional physical difference is that the reset button appears to be between the USB ports, instead of behind the AV out - not a big deal.
After powering it up, I am having huge problems with them.
Firstly though, what the software says about the hardware:
Advanced Settings/About Tablet:
Model Number : BBA22
Android Version : 4.2.2
Firmware Version : V2.0
Kernel Version : 3.4.39 [email protected] #10 Wed May 14 22:36:36 CST 2014
Build Number : BBA22-UI4-V2.0.1
And what Droid Info says about the (relevant)hardware:
Model : BBA22 (sdk-normal)
Manufacturer : unknown
Chipset : sun7i
RIL version : sw-dataonly-ril-0.5
Build Number : BBA22-UI4-V2.0.1
Build Bingerprint : softwinners/ninss/ninss4.2.2/NinssSoftware/20140521:eng/test-keys
OS Version : Jelly Bean MR1 (4.2.2)
SDK : 17
CPU Architecture : ARMv7 Processor rev 4 (v71)
Now, the BIGGEST issue these things have, is that at random points of use, it comes up with a message "Warning - System configuration is inconsistent with the production configuration, please contact your supplier, thank you!". This message will flash over and over again for anything from 30 seconds to half an hour. I half suspect it has tablet code SOMEwhere in it also, as it keeps coming up with 'touch the circle' walkthroughs for applications like avia. This might be unrelated though, I have no idea.
So anyway, I have tried doing the Justop 4.0 flash method with a SD card, however it will not turn on if there is a card in the slot. Also, when you hold the reset button down and power it up, it does not seem to go into the diagnostic mode so I can't flash it that way either. I am guessing the ONLY way I can update short of soldering in a serial port, is to use the backup/restore function.
I read through this whole thread here, but cound not fine anything to help me:
http://forum.xda-developers.com/showthread.php?t=2398632
If anyone has any ideas, please let me know, I seriously can't get anything to work. I thought maybe the 'hotspot' being enabled was causing the incinsistency problem, but I used a process killer to stop that at startup, still no luck. Doing a system reset through advanced config didn't help either, I got the error almost as soon as turning the unit back on.
I've attached pictures of the error I am getting, the top of the board, and the back if the board.
Cheers,
Smak
PS - I am yet to hear back from the seller, but if I ever do, I will post the result here...
Smakky said:
Advanced Settings/About Tablet:
Model Number : BBA22
Android Version : 4.2.2
Firmware Version : V2.0
Kernel Version : 3.4.39 [email protected] #10 Wed May 14 22:36:36 CST 2014
Build Number : BBA22-UI4-V2.0.1
Click to expand...
Click to collapse
I seem to be in a very similar situation. My device also reports as being "BBA22" but it's a different form factor and the identification on the board is "TXCZ_A20_v1.0". I tried contacting the people that made the board (Shenzhen Tianxing Chuangzhan Electronic Co.) but they refused to help. I also tried contacting the company that made the firmware images (Shenzhen NINSS Technology Ltd.) and they also refused. The supplier I bought the device from says they have the image file but they can't seem to figure out how to get it to me (they tried emailing the +200mb file then they gave up and stopped responding). The build number on my device is "BBA22-UI4-V2.0.4" so apparently there's an update available that may work on your device.
I'm pretty sure you need to flash the image using the Phoenixsuit program to make a special sdcard that you place in the device and boot from to reflash the device.
Please post your image file if you ever get it!
tisdall said:
I seem to be in a very similar situation. My device also reports as being "BBA22" but it's a different form factor and the identification on the board is "TXCZ_A20_v1.0". I tried contacting the people that made the board (Shenzhen Tianxing Chuangzhan Electronic Co.) but they refused to help. I also tried contacting the company that made the firmware images (Shenzhen NINSS Technology Ltd.) and they also refused. The supplier I bought the device from says they have the image file but they can't seem to figure out how to get it to me (they tried emailing the +200mb file then they gave up and stopped responding). The build number on my device is "BBA22-UI4-V2.0.4" so apparently there's an update available that may work on your device.
I'm pretty sure you need to flash the image using the Phoenixsuit program to make a special sdcard that you place in the device and boot from to reflash the device.
Please post your image file if you ever get it!
Click to expand...
Click to collapse
That is good to know, I might email them again now. Will let you know the outcome!
OK, so I got a reply from the seller.
I've attached the patch file and the instructions to this message, but theres a few things to note.
- Its only like 20 meg big, so it isnt a full firmware update
- The instructions talk about pressing the reset button at the start.., I don;t think this is neccesary if its rooted already
- The instructions are VERY engrish-y, basically just dump the update.zip onto a sd card, and apply the patch through the settings menu
- The default language is changed to some form of Chinese after applying, theres plenty pictorials on how to change the android language though.
- The version has been updated from BBA22-UI4-V2.0.1, to BBA22-UI4-V2.0.3 - This is still lower than the one you mentioned @ BBA22-UI4-V2.0.4
So far though, I have re-installed all my apps, and haven't seen the error.. yet. I was a little concerned it is still giving me touchpad tutorials, but mouse mode on the remote is making short work of those.
I'll just have to wait and see, I guess.
Smakky said:
OK, so I got a reply from the seller.
I've attached the patch file and the instructions to this message, but theres a few things to note.
- Its only like 20 meg big, so it isnt a full firmware update
- The instructions talk about pressing the reset button at the start.., I don;t think this is neccesary if its rooted already
- The instructions are VERY engrish-y, basically just dump the update.zip onto a sd card, and apply the patch through the settings menu
- The default language is changed to some form of Chinese after applying, theres plenty pictorials on how to change the android language though.
- The version has been updated from BBA22-UI4-V2.0.1, to BBA22-UI4-V2.0.3 - This is still lower than the one you mentioned @ BBA22-UI4-V2.0.4
So far though, I have re-installed all my apps, and haven't seen the error.. yet. I was a little concerned it is still giving me touchpad tutorials, but mouse mode on the remote is making short work of those.
I'll just have to wait and see, I guess.
Click to expand...
Click to collapse
That seems very promising for you! Unfortunately it probably won't help me at all... It sounds like it's a sort of update patch instead of a whole image. Starting the device with the reset button causes it to load the recovery partition instead of the regular partition (I'm guessing you saw a green android with a text menu with options for recovery). I full flashing would/could involve an SDcard, but I think you would have to create it with Phoenixsuit and not just copy the file contents over (it would then just boot directly from the SDcard and you wouldn't need to press the reset button).
In my case, both the regular boot partition and the recover partition are wrecked so I couldn't even try this patch if I wanted to.
Thanks for posting, though... Hopefully it helps someone else out.
tisdall said:
That seems very promising for you! Unfortunately it probably won't help me at all... It sounds like it's a sort of update patch instead of a whole image. Starting the device with the reset button causes it to load the recovery partition instead of the regular partition (I'm guessing you saw a green android with a text menu with options for recovery). I full flashing would/could involve an SDcard, but I think you would have to create it with Phoenixsuit and not just copy the file contents over (it would then just boot directly from the SDcard and you wouldn't need to press the reset button).
In my case, both the regular boot partition and the recover partition are wrecked so I couldn't even try this patch if I wanted to.
Thanks for posting, though... Hopefully it helps someone else out.
Click to expand...
Click to collapse
Hmm, is clockworkmod still a thing? I could try taking a backup of my ROM and see if that's something you can use.., only problem is I will need a bit of time. If I get a chance, I'll do it over the weekend. I will need a place to dump the image though, it will be too big to attach here, can sort that out later though.
Smakky said:
Hmm, is clockworkmod still a thing? I could try taking a backup of my ROM and see if that's something you can use.., only problem is I will need a bit of time. If I get a chance, I'll do it over the weekend. I will need a place to dump the image though, it will be too big to attach here, can sort that out later though.
Click to expand...
Click to collapse
I'd appreciate that... Your board seems to have a completely different layout, but all the same components. I'm not familiar with clockworkmod, though, so I'm not sure how that backup would work. I guess I'd need to get clockworkmod flashed on to the recovery partition first and then I could flash the backup to the NAND from there?
tisdall said:
I'd appreciate that... Your board seems to have a completely different layout, but all the same components. I'm not familiar with clockworkmod, though, so I'm not sure how that backup would work. I guess I'd need to get clockworkmod flashed on to the recovery partition first and then I could flash the backup to the NAND from there?
Click to expand...
Click to collapse
I'm not actually too sure. The last timed I used clockworkmod was for flashing a galaxy s2 phone, so I'm not even too sure if its still around or compatible with tv boxes. There will definately be SOME sort of tool though, that can take a full backup suitable for restoring. I'm about at the limit of my knowledge, so I am sort of playing by ear and going into a google-learn-try sort of cycle as I try different things. Maybe someone with more experience will stumble in here and let us know what we need to do
This is interesting... I found another device with an identical PCB board: YBKJ_A20 (I can't post links yet, but a Google search will find it) Several chips are different so the firmware would differ. It's so hard to work with these devices when no one claims credit for making a lot of these things!
What is J4?
http://dl-1.va.us.xda-developers.com/2/9/3/6/8/3/3/DSC_0207s.jpg
I was wondering what the upper left 2 pin connector is for? (the little white 2 pin plug next to the USB)
Is it SPDIF? Power input? output? Something else? I see in this picture a cable connected so i'm hoping you can tell.
Ask BBA22-V.1.50 TV BOX Model Android 4.2 Firmware
Smakky said:
OK, so I got a reply from the seller.
I've attached the patch file and the instructions to this message, but theres a few things to note.
- Its only like 20 meg big, so it isnt a full firmware update
- The instructions talk about pressing the reset button at the start.., I don;t think this is neccesary if its rooted already
- The instructions are VERY engrish-y, basically just dump the update.zip onto a sd card, and apply the patch through the settings menu
- The default language is changed to some form of Chinese after applying, theres plenty pictorials on how to change the android language though.
- The version has been updated from BBA22-UI4-V2.0.1, to BBA22-UI4-V2.0.3 - This is still lower than the one you mentioned @ BBA22-UI4-V2.0.4
So far though, I have re-installed all my apps, and haven't seen the error.. yet. I was a little concerned it is still giving me touchpad tutorials, but mouse mode on the remote is making short work of those.
I'll just have to wait and see, I guess.
Click to expand...
Click to collapse
Hello
Thank You For This Firmware But It Work For BBA22-UI4-V2.0.1, to BBA22-UI4-V2.0.3.
My Device Model is ((BBA22-V.1.50)) with Android 4.2 and I had to update it with your firmware file to fix problem black page after boot.
after update my device with your firmware, black page broblem is solved but device not work properly and it show Error message for (android.process.acore) systematically in loop!
also I can not make very actions because this error message show repeatedly.
also the default device language is china and i can not change language (error message show repeatedly)
have you original firmware for ((BBA22-V.1.50)) with Android 4.2 device???
thank you for help me...
H.SHAFAGHI said:
have you original firmware for ((BBA22-V.1.50)) with Android 4.2 device???
Click to expand...
Click to collapse
So... For everyone looking for a full firmware for this box, and stumbled upon this thread from google like I did: DESPAIR NO MORE.
I found a compatible firmware for this device (exacly as described and same board as the one OP has) It will work even if your box came preinstalled with another software version, but its the same hardware
Found it in another thread, posted by @daaviles30 Its not EXACLY the same as the one I had originally loaded but appears to work without any issue whatsoever (even the remote works), if a little bit better.
So here it is:
daaviles30 said:
A20_V20_SDK_EN_XBMC_0703-2.img*491.4 MB
*https:/ /mega.co.nz/#!XAIRiD5Q!aIb0tvvjvzUdaf11vIR7PAadeXPV8XizYJ9X2mAzpQI
RH46-update-a20.zip*582 KB
*https:/ /mega.co.nz/#!HZwTgQIT!LQGxb6R-lCIKe58RgIGROfufY-aq5PODSAq3-NPKOeo
PhoenixCard_V309
*http:/ /mega.co.nz/#F!HAIhBJyS!L_UQPNnYdPyHTD3ggnJ6OA
After flashing update and then go to the play store and download SuperSU update that and your ready to go.
---------- Post added at 03:57 PM ---------- Previous post was at 03:29 PM ----------
Titanium Backup Pro v6.1.5.3.apk*6.2 MB
*https:/ /mega.co.nz/#!vAAWRJga!vOFKlAq_25ssrG5kvwa3-oC-d0saL06YGBIWIyN2jss
You can delete all the unwanted system apps with this app.
Hope this helps Happy New Years.
Click to expand...
Click to collapse
The flashing process is exacly as described earlier in this thread. Use phoenix card to burn the img to an SD card, turn the device on with the card inserted in the slot and enjoy your restored android box.
It Working Only With Booting From Memory Card Slot...
amedeh123 said:
So... For everyone looking for a full firmware for this box, and stumbled upon this thread from google like I did: DESPAIR NO MORE.
I found a compatible firmware for this device (exacly as described and same board as the one OP has) It will work even if your box came preinstalled with another software version, but its the same hardware
Found it in another thread, posted by @daaviles30 Its not EXACLY the same as the one I had originally loaded but appears to work without any issue whatsoever (even the remote works), if a little bit better.
So here it is:
The flashing process is exacly as described earlier in this thread. Use phoenix card to burn the img to an SD card, turn the device on with the card inserted in the slot and enjoy your restored android box.
Click to expand...
Click to collapse
Hello My Friend And Thank You For Replay...
This Android is Working And is Very Good But i Can Not Install This To My Device. I Copy The IMG File To A External Memory Card (Using PhonixCard Application) and put the Memory Card To My Device And PowerOn My Device. My Device Automatically Boot From Memory Card And New Android is Appear. It Is Very Fast And Have No Errors.
Now...
HOW I CAN INSTALL THE IMG FILE TO MY DEVICE (INTERNAL MEMORY) AND BOOT MY DEVICE WITHOUT USING MEMORY CARD (FOR ALL TIMES)???
H.SHAFAGHI said:
Hello My Friend And Thank You For Replay...
This Android is Working And is Very Good But i Can Not Install This To My Device. I Copy The IMG File To A External Memory Card (Using PhonixCard Application) and put the Memory Card To My Device And PowerOn My Device. My Device Automatically Boot From Memory Card And New Android is Appear. It Is Very Fast And Have No Errors.
Now...
HOW I CAN INSTALL THE IMG FILE TO MY DEVICE (INTERNAL MEMORY) AND BOOT MY DEVICE WITHOUT USING MEMORY CARD (FOR ALL TIMES)???
Click to expand...
Click to collapse
Wow.
The Phoenixsuite makes an sdcard that flashes the internal memory. After it's finished flashing, you take the card out and it runs off of the internal NAND. That's it. It never runs the Android from the sdcard.
My device can boot from sd-card!!! I need to flash this to install your android!
tisdall said:
Wow.
The Phoenixsuite makes an sdcard that flashes the internal memory. After it's finished flashing, you take the card out and it runs off of the internal NAND. That's it. It never runs the Android from the sdcard.
Click to expand...
Click to collapse
Hello My Friend And Thank You For Replay...
1- My Device Can Boot From SD-CARD With A Bootable Memory Card! (Such As OpenSuse Linux)
2- I Use PhonixCard Application That You Send.
(PhoenixCard_V309
*http:/ /mega.co.nz/#F!HAIhBJyS!L_UQPNnYdPyHTD3ggnJ6OA
3- I Can Not Use PhonixSuit Application And I Don't Know How To Use PhonixSuit. When I Connect My Device To My Computer To Use PhonixSuit, My Computer Don't Find Any Hardware And Can Not Connect!
4- I Copy The IMG File To A SD-CARD (Using PhonixCard Application) and put the Memory Card To My Device And PowerOn My Device. My Device Automatically Boot From Memory Card And New Android is Appear. If Unplug The SD-CARD And Power On My Device, Old Android Is Appear!!! Master Android Software Is In My Device And I Need To Clear This From My Device And Install Your Android!
HOW I CAN INSTALL YOUR ANDROID TO MY DEVICE (INTERNAL MEMORY) AND BOOT MY DEVICE WITHOUT USING MEMORY CARD???
I need help!!!!
no any answer???
For those that want a rooted stock ROM, without having to use Kingoroot, here you go.
jy190_rooted.zip
This is the JY 1.90 ROM + SuperSU installed, no garbage, no Kingoroot or whatever. I took the 1.90 Joying image, unpacked it, manually installed SuperSU (basically duplicating what the SuperSU installation script does), and repackaged it. It is running on my Jeep HU right now and SuperSU is fully functional.
I've made two harmless changes to stock that you can change after flashing:
Default Bluetooth device name is "JoyingJeep" instead of "CAR-KIT" (tired of changing it manually to the name I want)
Default Timezone is America/Detroit instead of China/Shanghai (same reason as above)
Prerequisite: Probably you will want to get the JY1.90 ROM from Joying directly, and update your HU with it because Joying includes an updated MCU image. I am *not* including the MCU image here because one of you is going to flash it onto the wrong hardware and brick your HU. I am only providing the ROM image, just like Malaysk does.
1. To install, first extract dupdate.img from the zip.
2. Copy dupdate.img to the root directory of a USB stick or SD card
3. Enter recovery, flash. If coming from stock you can probably flash without clearing all. If coming from Malaysk you might want to clear all first.
Understand what you are doing. Read Malaysk's thread about flashing, and read all of his warnings, as they all apply here.
Thanks to Malaysk for his ROM and all of the other tweaks he's done. If you want something beyond stock, try his.
Thanks to Joying for making this unit, there is nothing else like it on the market. As long as continues to work, I'll continue to be very happy with it.
Thanks once more to Joying for being (so far) pretty friendly to the DIY/modding/hacking crowd. I've never seen a company so open with flashing and modding, and continuing to update their own firmware for their customers. It is nice to see, so let's not abuse it. Mod responsibly.
There won't be any additional support from me. This is a rooted stock ROM, that's it.
Edit 5-Nov-2016, some FAQ:
Unpacking and repacking a rockchip ROM
Adding root to the ROM
Make it easy on yourself: ROM kitchen by da_anton
it starts video playback on boot. its not your rom, its the original as well, but weird.
---------- Post added at 07:41 AM ---------- Previous post was at 07:28 AM ----------
What tool you use to unpack rom?
Hi!!! Thanks for your work I'm going to wipe my ROM (I think there's some garbage after deleting Kingoroot) and put your ROM into my unit.
Great work
wskelly said:
For those that want a rooted stock ROM, without having to use Kingoroot, here you go.
jy190_rooted.zip
This is the JY 1.90 ROM + SuperSU installed, no garbage, no Kingoroot or whatever. I took the 1.90 Joying image, unpacked it, manually installed SuperSU (basically duplicating what the SuperSU installation script does), and repackaged it. It is running on my Jeep HU right now and SuperSU is fully functional.
I've made two harmless changes to stock that you can change after flashing:
Default Bluetooth device name is "JoyingJeep" instead of "CAR-KIT" (tired of changing it manually to the name I want)
Default Timezone is America/Detroit instead of China/Shanghai (same reason as above)
Prerequisite: Probably you will want to get the JY1.90 ROM from Joying directly, and update your HU with it because Joying includes an updated MCU image. I am *not* including the MCU image here because one of you is going to flash it onto the wrong hardware and brick your HU. I am only providing the ROM image, just like Malaysk does.
1. To install, first extract dupdate.img from the zip.
2. Copy dupdate.img to the root directory of a USB stick or SD card
3. Enter recovery, flash. If coming from stock you can probably flash without clearing all. If coming from Malaysk you might want to clear all first.
Understand what you are doing. Read Malaysk's thread about flashing, and read all of his warnings, as they all apply here.
Thanks to Malaysk for his ROM and all of the other tweaks he's done. If you want something beyond stock, try his.
Thanks to Joying for making this unit, there is nothing else like it on the market. As long as continues to work, I'll continue to be very happy with it.
Thanks once more to Joying for being (so far) pretty friendly to the DIY/modding/hacking crowd. I've never seen a company so open with flashing and modding, and continuing to update their own firmware for their customers. It is nice to see, so let's not abuse it. Mod responsibly.
There won't be any additional support from me. This is a rooted stock ROM, that's it.
Click to expand...
Click to collapse
wskelly said:
This is the JY 1.90 ROM + SuperSU installed, no garbage, no Kingoroot or whatever. I took the 1.90 Joying image, unpacked it, manually installed SuperSU (basically duplicating what the SuperSU installation script does), and repackaged it. It is running on my Jeep HU right now and SuperSU is fully functional.
Click to expand...
Click to collapse
Great idea and thanks for the work! Thought of that myself! Could you perhaps tell me how you made that ROM? How did you manage to extract the img file and put everything back together? Did you use imgRePackerRK? Thanks!
da_anton said:
Great idea and thanks for the work! Thought of that myself! Could you perhaps tell me how you made that ROM? How did you manage to extract the img file and put everything back together? Did you use imgRePackerRK? Thanks!
Click to expand...
Click to collapse
Yes, I used imgrepackerrk on Linux. After dumping the contents you are left with more img files. These are all block storage. In Linux, it is possible to mount these img files and manipulate their contents just like any block device.
Afterward, you can repack everything again with imgrepackerrk.
Sent from my Moto G using Tapatalk
wskelly said:
[*]Default Bluetooth device name is "JoyingJeep" instead of "CAR-KIT" (tired of changing it manually to the name I want)
.
Click to expand...
Click to collapse
hey I also named my Joying that
This is great! If I hadn't install the Sept Joying image last weekend, I would have totally installed this. Thank so much!
One suggestion though, if you decide to make another one at some point, you might want to install the xposed framework (I did this via flashfire) and appsettings 1.13. I can provide a link to each, that are known good, as the 'regular' framework and App Settings 1.10 (from xposed directly) doesn't work. I know it's designed as 'stock' but at minimum the framework just makes sense, I think.
wskelly said:
Yes, I used imgrepackerrk on Linux. After dumping the contents you are left with more img files. These are all block storage. In Linux, it is possible to mount these img files and manipulate their contents just like any block device.
Afterward, you can repack everything again with imgrepackerrk.
Sent from my Moto G using Tapatalk
Click to expand...
Click to collapse
Thanks! Great work! Got it working today and made my first ROM based on yours. I removed some apps which are just wasting RAM and I don't need.
Greetings,
I am very new to these head units got my first one 2 months ago. been reading and learning a lot here. I have a KGL and installed this rom, its working great and its a bit visually different then the one's I have used for KGL. Glad to know we have options on roms and tweaking we can do.
I do have a small annoyance that I hope some one can help me with. I had hoped this rom would solve it but unfortunately not. The radio RDS feature, on all the roms I have used the problem stays the same. I am in the US and its set to Europe RDS PTY code. So I can see the all the station and song information but the Station genera is wrong. like country music stations listed as pop and rock stations listed as Drama. I figure their is a file that the radio ap references to know what label to use and display. I have searched for this file or ap location but have had no luck in finding were it would be located. Can anyone point me in the right direction on how to possible fix it so the radio displays the correct station type? Sorry to hijack a thread but my post count is not high enough to allow me to start my own. search has not helped. Thanks all.
da_anton said:
Thanks! Great work! Got it working today and made my first ROM based on yours. I removed some apps which are just wasting RAM and I don't need.
Click to expand...
Click to collapse
Awesome! Keep tinkering! This is how everyone gets started. ?
Sent from my Moto G using Tapatalk
Hi !, I'm not 100% sure but try to change radio reg at the Factory options.....
pinkpanther28 said:
Greetings,
I am very new to these head units got my first one 2 months ago. been reading and learning a lot here. I have a KGL and installed this rom, its working great and its a bit visually different then the one's I have used for KGL. Glad to know we have options on roms and tweaking we can do.
I do have a small annoyance that I hope some one can help me with. I had hoped this rom would solve it but unfortunately not. The radio RDS feature, on all the roms I have used the problem stays the same. I am in the US and its set to Europe RDS PTY code. So I can see the all the station and song information but the Station genera is wrong. like country music stations listed as pop and rock stations listed as Drama. I figure their is a file that the radio ap references to know what label to use and display. I have searched for this file or ap location but have had no luck in finding were it would be located. Can anyone point me in the right direction on how to possible fix it so the radio displays the correct station type? Sorry to hijack a thread but my post count is not high enough to allow me to start my own. search has not helped. Thanks all.
Click to expand...
Click to collapse
Thank you for the work!
Question, how did you extract the img file. the typical utilities i use for android seem to be incompatible with this system image.
Found!
http://forum.xda-developers.com/showthread.php?t=2257331
Yes. Earlier post
mlkemac said:
Thank you for the work!
Question, how did you extract the img file. the typical utilities i use for android seem to be incompatible with this system image.
Found!
http://forum.xda-developers.com/showthread.php?t=2257331
Click to expand...
Click to collapse
See post #5.
@wskelly could you maybe tell me exactly what you did to include SuperSU in ROM? I would like to integrate it into the ROM builder scripts here https://github.com/da-anton/MTCD_ROM-cooking. Would be great!
da_anton said:
@wskelly could you maybe tell me exactly what you did to include SuperSU in ROM? I would like to integrate it into the ROM builder scripts here https://github.com/da-anton/MTCD_ROM-cooking. Would be great!
Click to expand...
Click to collapse
Yes, I kind of did already. If you look into the SuperSU thread here in Xda, you can get the latest version. Inside the flashable zip, there is a dir
META-INF/com/google/android
Then you'll find install-binary, which is actually a shell script. (this directory structure is the actually standard format for recovery-flashable zips)
In the shell script the author goes into great detail about what his where and with what permissions.
The big caveat for your efforts is that we have sdk 22 (5.1.1) and things are different depending on which version of Android you have (some Joying units are KitKat). The installation script handles every version of Android so far and this is all detailed by the author in the script.
Another warning: the installation script runs another binary tool that will "convert" wine of the binaries to "pie" executables. Because the ones I want are compiled for ARMv7, and I'm on Intel modding the ROM, I'm not sure if I can run that tool with confidence. So, I took the su binary files from Malaysk's ROM, which I know work. This is why SuperSU tells you that the binary is out of date right away. You must follow the chaos and chcon instructions in the installation script exactly. (I think malaysk is missing some of those steps because his rom would always fail to update su via the app)
So my recommendation is to look at the installation script, and follow the instructions in the comments section which are very detailed about what goes where. Except instead of using SuperSU installation files, you should take the files from my ROM. **You may try to use the files from SuperSU, but likely you will get a bootloop (because of the pie format issue), worth trying though. Also worth trying the pie conversion on Intel.
I'm on my phone so hopefully spellings and the path names aren't too messed up.
I'm curious if removing the recovery.img and bootloader.img if it will still flash. Flashing those two partitions every time is asking for trouble eventually.
Sent from my Moto G using Tapatalk
pinkpanther28 said:
Greetings,
I am very new to these head units got my first one 2 months ago. been reading and learning a lot here. I have a KGL and installed this rom, its working great and its a bit visually different then the one's I have used for KGL. Glad to know we have options on roms and tweaking we can do.
I do have a small annoyance that I hope some one can help me with. I had hoped this rom would solve it but unfortunately not. The radio RDS feature, on all the roms I have used the problem stays the same. I am in the US and its set to Europe RDS PTY code. So I can see the all the station and song information but the Station genera is wrong. like country music stations listed as pop and rock stations listed as Drama. I figure their is a file that the radio ap references to know what label to use and display. I have searched for this file or ap location but have had no luck in finding were it would be located. Can anyone point me in the right direction on how to possible fix it so the radio displays the correct station type? Sorry to hijack a thread but my post count is not high enough to allow me to start my own. search has not helped. Thanks all.
Click to expand...
Click to collapse
Yea, this post is *completely* off topic and deserves its own thread. Maybe someone here will start a new thread for you.
Sent from my Moto G using Tapatalk
wskelly said:
So my recommendation is to look at the installation script, and follow the instructions in the comments section which are very detailed about what goes where. Except instead of using SuperSU installation files, you should take the files from my ROM. **You may try to use the files from SuperSU, but likely you will get a bootloop (because of the pie format issue), worth trying though. Also worth trying the pie conversion on Intel.
Click to expand...
Click to collapse
OK. I created a module in the MTCD ROM builder for that. How exactly did you set the links without chroot? Maybe you could have a look a my version and could tell me if anything is missing :angel:
https://github.com/da-anton/MTCD_ROM-cooking/blob/master/modules/install_supersu.sh
da_anton said:
OK. I created a module in the MTCD ROM builder for that. How exactly did you set the links without chroot? Maybe you could have a look a my version and could tell me if anything is missing :angel:
https://github.com/da-anton/MTCD_ROM-cooking/blob/master/modules/install_supersu.sh
Click to expand...
Click to collapse
Awesome script! I was way too lazy to do this but I wished I had it! ? I actually started to mod the SuperSU script to root the local ROM but I just got lazy.
To link without chrooting you can use the -f (force) option.
I am on my phone and didn't get to look at the whole script yet but you could just try to root stock and see if it works?
Nice job!
Sent from my Moto G using Tapatalk
wskelly said:
Awesome script! I was way too lazy to do this but I wished I had it! ? I actually started to mod the SuperSU script to root the local ROM but I just got lazy.
To link without chrooting you can use the -f (force) option.
I am on my phone and didn't get to look at the whole script yet but you could just try to root stock and see if it works?
Nice job!
Click to expand...
Click to collapse
Thanks! I already tried that and my unit is stuck in a boot loop now. Guess it's because I forgot to include the binary from Malaysk and used the official one instead will try the next days to fix my unit
hello,
i have buy multimedia car android.
At first start it's slow?
Almost 1 minute to launch sistem ??
mcu version
mtcd mx v1.70_1
android 5.1.1
(Photo attached)
My rom is up to date?
Or can you change rom to work even faster? yes please link new rom...
Thank you for helping me
Read: http://forum.xda-developers.com/and...lopment/rom-malaysk-roms-mtcd-device-t3385309
and
http://forum.xda-developers.com/and...rom-joying-rom-supersu-tweaked-speed-t3475086
All you need to know.
Last one is faster but less options...
dude-nl said:
Read: http://forum.xda-developers.com/and...lopment/rom-malaysk-roms-mtcd-device-t3385309
and
http://forum.xda-developers.com/and...rom-joying-rom-supersu-tweaked-speed-t3475086
All you need to know.
Last one is faster but less options...
Click to expand...
Click to collapse
It looks like the rom Malaysk ROMs has more success!
What you meen with more succes?
da-anton's is using less RAM and running better on my and my friends unit.
Faster boot time
No issues
Malasyks is the most complete one, but had some issues on my device (slow start and often memory problems).
The base of the ROM is the same. Only da-anton left fome stuff out to improve starting and memory.
I'm gonna upgrade to 2GB (already ordered) and are gonna use Malasyks rom again if it runs better with 2GB. For now I'm sticking to da-anton just because of the faster boot time and better response while on load.
It starts in how many seconds?
Me 40seconde
One can add in addition 1 gb of ram or should the ram be replaced by a 2 gb?
Hello !
How to be in recovery mode?
Me car multimédia img.
Thx
Rts reset..
I can not get into recovery mode .. How do I get it please?
Yes I have uptade
I do not see any change...
Update MCU is nog vissible change, it's on the background.
Now download Malasyk or da-anton's rom and install
Mcu update shown as v1. 97a_1
Getapped and getalked with 6603
Hi all you clever people
I just bought this unit, https://www.aliexpress.com/item/7-I...igation-Sat-Nav-Radio-Player/32772807019.html, and installed in my car.
I have set up a bluetooth connection with my phone and using a hotspot from the phone to give Internet access.
I have a lot of questions, and I have searched this site, but haven't really found clear answers.
First the facts. here are the data from my settings:
Model: px5(1024x600)
Android version: 8.0
Android security patch level: October 5. 2017
Kernel: 4.4.93+
[email protected] #336
px5-userdebug 8.0.0 OPR5.170623.007 eng.htc.20180804
MCU version: MTCE_MX_V2.92.1
Aug 21 2018 20:10:21
CPU: 8 core 64-bit CPU Coretex-A53 @ 1.5G
Memory: 3891 MB
I know I'm asking a lot of questions, it's just a bit confusing to get started in this new world. I have numbered my questions, so it's easier to reference
1) I would like to get hands free phone calls and texting and navigation. I tried Android Auto, and that was very stable, but I couldn't get the phone to work. I assume thats because it's meant to be run on a phone and then mirrored to the head unit. Now I'm trying with Google Assistent, but it's not really stable. At first it worked pretty well, but now it just works as Google Now, so it won't make phone calls for instance. Any advice on what to choose, and how to get it to work?
2) I found this thread about a custom ROM, https://forum.xda-developers.com/an...t/rom-hal9k-rom-3-mtcd-e-head-units-t3847477/, my unit should be compatible for that, right?
3) As far as I understand, I can not go back to the stock ROM, if I install the new ROM. Then I should flash it with my old ROM. But how do I find out the name of my existing ROM? Is it risky to flash a new ROM, or will I always be able to flash back, if something goes wrong?
4) It's a requirement for the Hal9k ROM, that my MCU is upgraded to at least 2.93. I found this thread, https://forum.xda-developers.com/an...asaita-mcu-updates-rockchip-px5-octa-t3575155, but how do I find out if this MCU upgrade is compatible with my MCU?
5) Finally, I installed Tidal app, so I could download playlist for my head unit, but when I start the app and enter my credentials (and they are correct, because I get an error if I enter a wrong password) it just starts up with a black screen with a play icon in the middle, and previous and next symbols, but no menu, except for a hifi menu in the top left corner, where I can choose streaming quality. I will post a picture tomorrow. Does anyone know how to fix that?
Can someone please help me or at least point me in the right direction? I have spent multiple hours searching this site, but right now I'm a bit confused
Kind regards
Allan
Hi! Ok I should be able to answer most of these:
1) If you use the Hal9K 3.1.1 ROM then calling is linked to the phone through Android Assistant, but I haven't got a good solution for SMS at this stage.
2) Yes is is definitely compatible with your unit.
3) Not true, you can definitely go back, just flash a stock ROM. In my case I was sent the ROM by my seller Eonon
4) Your MCU is MX so just find the correct version of that. Check for the MX version here: https://forum.xda-developers.com/an...ent/mod-cs-x-mod-mtcd-e-mcu-firmware-t3816042
5) Not sure, but hopefully the Hal9K rom will help fix that!
Good luck Allan
millab said:
Hi! Ok I should be able to answer most of these:
1) If you use the Hal9K 3.1.1 ROM then calling is linked to the phone through Android Assistant, but I haven't got a good solution for SMS at this stage.
2) Yes is is definitely compatible with your unit.
3) Not true, you can definitely go back, just flash a stock ROM. In my case I was sent the ROM by my seller Eonon
4) Your MCU is MX so just find the correct version of that. Check for the MX version here: https://forum.xda-developers.com/an...ent/mod-cs-x-mod-mtcd-e-mcu-firmware-t3816042
5) Not sure, but hopefully the Hal9K rom will help fix that!
Good luck Allan
Click to expand...
Click to collapse
Thank you very much, it sound like it should be pretty safe to try the Hal9K ROM. I just have a couple of extra questions:
3a) My seller on AliExpress seems to have no clue, when I'm asking for stock ROM. But I should be able to find something close to my Stock ROM, if I don't succeed with Hal9K, right? Something like the Original Android 8.0 MX ROM mentioned in this thread: http://www.androidiani.com/forum/au...ndroid-rockchip-px5-2-4-gb-ram-32-gb-rom.html
4) I found this thread, https://forum.xda-developers.com/an...evelopment/update-media-auto-mtcd-mx-t3828177, with a link to yadi.sk, where I can find a MTCE_MX_V3.00.rar. That should be compatible with my device, right?
I hope you will bare with my ignorance, I'm really trying to get into this
Kr
Allan
Did you manage to get Tidal working ?
for Android Auto. I'm running the app called `Head Unit Reload` that would turn the Android system as host. essentially it's helper app for `DHU` (Desktop HeadUnit by Google for android auto debugging).
with HUR you can do either wireless Android Auto or USB tethered. This would handle SMS and phone call hands free.
I'm running Hal9K 3.1.1 ROM on my MCUE HK + Car launcher pro as launcher.
Hello, Do you know a custom rom compatible with the Box T9 RK3318 ? The stock rom is too ... Stock ^^ Thank you in advance.
searching too ;-)
I found a Android 9 Stock rom for the T9 64GB 4GB ram version of this box. Best way to upgrade it is by using a SDcard formatted in Fat32 and use the SD card using SD_Firmware_Tool_v146_eng_AndroidPC.zip and the firmware file name is 3318_9.0-TVBOX-Z2_0820.img Make the SD card with the program. Insert the SD card while the box has no power. Hold the button inside the AV port while holding it in. Plug in the power. Then release the button when you see the T9 boot logo come up and it will automatically program the TV box to version 9. The only issue I had was with playstore would not install the apps. But if you install them manually it would update them or using a phone or computer and pick what you want from playstore works it will download and install from there when you select the TV box. Also it will not connect to WIFI while plugged into Ethernet where as the 8.1 allowed both Ethernet and WIFI to be connected at the same time. I am currently searching for the Android 10 version.
Update:
This file is more updated. 3318_9.0-TVBOX-Z4_1025.img Then once its installed run the updater to get the next update to have the latest 9.0 installed.
flood404 said:
I found a Android 9 Stock rom for the T9 64GB 4GB ram version of this box. Best way to upgrade it is by using a SDcard formatted in Fat32 and use the SD card using SD_Firmware_Tool_v146_eng_AndroidPC.zip and the firmware file name is 3318_9.0-TVBOX-Z2_0820.img Make the SD card with the program. Insert the SD card while the box has no power. Hold the button inside the AV port while holding it in. Plug in the power. Then release the button when you see the T9 boot logo come up and it will automatically program the TV box to version 9. The only issue I had was with playstore would not install the apps. But if you install them manually it would update them or using a phone or computer and pick what you want from playstore works it will download and install from there when you select the TV box. Also it will not connect to WIFI while plugged into Ethernet where as the 8.1 allowed both Ethernet and WIFI to be connected at the same time. I am currently searching for the Android 10 version.
Update:
This file is more updated. 3318_9.0-TVBOX-Z4_1025.img Then once its installed run the updater to get the next update to have the latest 9.0 installed.
Click to expand...
Click to collapse
hello, sorry for my English I live in France I would have a question about the box: TV T9 RK3318, 4gb / 64gb. the problem is that the time is desynchronized on restart and creates problems to connect to applications when the time is out of order, I tried everything changed the time zone to deactivate and entered the time Manual it goes out of order all the time . is there a custom version or a version 10?
As far as I know there is no Android 10 available for this TV box. If you want Android 10 time to buy a different Box other than a rockchip based one. As for the time resetting whenever the box is restarted this is normal it only resync when it connects to a time server on the internet. Not sure how you go about fixing that. There is no internal battery to keep time on it like a other devices would have.
Android 10 GSI ? Since the T9 was released on Android 9 and hence Treble compatible
yes no custom rom no Android 10, for now, even with an internal wifi connection sometimes she does not want to synchronize
Hello,
Before going further with this, if you wish to test those firmwares go ahead but you are the only responsible for your acts
I don't want any credits it's just to help ppl out, I was just testing the device myself.
I was also looking for a custom rom for the T9 Rk3318 but couldn't find one (in the box it was mentioned 3318 but when I opened the device in the mainboard it was saying rk3328 :/ )
I flashed some firmwares that I found (not custom) and finally bricked the box.
Then I did the testpoint and recovered it with two firmwares that I found in the link below that seems to be very compatible, all the credits goes to the owner.
https://cloud.mail.ru/public/PqyA/6YkwGagu9/ANDROID 10/
A95XR5_RK3318_Android10_2020-07-10 -- is working great
The one below I found it a bit slower but it also works
RK3318_DC_R1_AP6330_10_20200707.0137working
What doesn't work:
- original remote control
- display leds
...you can tell
You need a tool to flash them
-Rockship factory Tool
-Usb male to usb male cable (you can also find some videos on youtube to make one yourself)
you can find some instructions how to flash here:
Regards
li70 said:
Hello,
...............
Regards
Click to expand...
Click to collapse
This post helped me a lot, didn't have to search aimlessly and after flashing the a95xr5 rom its way better than the Z5 one the tvbox had before. It's still slow but man, compared to the old ROM its usable and not so damn sluggish. Thanks for taking the time to post this.
caxhatq said:
This post helped me a lot, didn't have to search aimlessly and after flashing the a95xr5 rom its way better than the Z5 one the tvbox had before. It's still slow but man, compared to the old ROM its usable and not so damn sluggish. Thanks for taking the time to post this.
Click to expand...
Click to collapse
Yeah that looks identical to my tv box board. The firmware will work that I posted a link to works.
flood404 said:
Yeah that looks identical to my tv box board. The firmware will work that I posted a link to works.
Click to expand...
Click to collapse
I've found an Android 11 ROM for this box, works amazingly well compared to the A95X and the sluggish T9 Z5 ROM. Here is a link to it:
RK3318_DC_HK1_COOL_AP6330_11_20210522.1453.zip
drive.google.com
WIFI works, only the front panel and infrared remote does not work. By the way, I flashed this ROM with an SD card because the USB cable I made was wonky and stopped flashing midway causing the box to not boot at all. It's simple, download the tool I've attached to this post and use it to either flash or just boot the img if you don't wanna flash it to eMMC (Haven't tested the SD Boot function myself but it should work)
This website also helped me a ton: https://forum.armbian.com/topic/17597-csc-armbian-for-rk3318rk3328-tv-box-boards/
caxhatq said:
I've found an Android 11 ROM for this box, works amazingly well compared to the A95X and the sluggish T9 Z5 ROM. Here is a link to it:
RK3318_DC_HK1_COOL_AP6330_11_20210522.1453.zip
drive.google.com
WIFI works, only the front panel and infrared remote does not work. By the way, I flashed this ROM with an SD card because the USB cable I made was wonky and stopped flashing midway causing the box to not boot at all. It's simple, download the tool I've attached to this post and use it to either flash or just boot the img if you don't wanna flash it to eMMC (Haven't tested the SD Boot function myself but it should work)
This website also helped me a ton: https://forum.armbian.com/topic/17597-csc-armbian-for-rk3318rk3328-tv-box-boards/
Click to expand...
Click to collapse
It says this is Android 9.0 here. https://romprovider.com/soudamini-hk1-cool-firmware-support/
Hi,
I know it's an old thread but i'm try'n to revive this box without success.
On board it's written 2G/16B tried 3318_9.0-TVBOX-Z4_1025.img firmware but restoration give me errors (see screenshot) would like to try 3318_9.0-TVBOX-Z2_0820.img firmware but didn't find it so if someone somewhere had this deep in his storage,please upload it again,it would be helpfull.
Regards
Hi i have used so many hours on this. If someone is interessted in recover this device back to stock firmware, here it is:
All the usefull links i have used:
Rockchip firmware update guide for Android TV-Box 2023
Tutorial to update, recover or unbrick with a firmware file our Android TV Box with SoC Rockchip RK3188, RK3368, RK3228, RK3229, RK3566...
androidpctv.com
Introduction — Firefly Wiki
RK3328-based firefly open source motherboard, has very powerful performance, USES a quad-core 64-bit processor Rochchip RK3328, and integrates 2.4g WIFI and bluetooth 4.2 module on the tiny motherboard, with usb2.0, usb3.0, hdmi, 1000M Ethernet, i2s and other diverse interfaces.
wiki.t-firefly.com
I have successfully restored my device back to Android 9.0. Using Driverassist 4.7 and RKdevTool v.2.58.
If anyone knows how to update the device to android 10 or higher WITHOUT bricking the device or some functions not working so please tell me.
Remember to give the device some time to startup after the firmware downloaded successfully.
caxhatq said:
I've found an Android 11 ROM for this box, works amazingly well compared to the A95X and the sluggish T9 Z5 ROM. Here is a link to it:
RK3318_DC_HK1_COOL_AP6330_11_20210522.1453.zip
drive.google.com
WIFI works, only the front panel and infrared remote does not work. By the way, I flashed this ROM with an SD card because the USB cable I made was wonky and stopped flashing midway causing the box to not boot at all. It's simple, download the tool I've attached to this post and use it to either flash or just boot the img if you don't wanna flash it to eMMC (Haven't tested the SD Boot function myself but it should work)
This website also helped me a ton: https://forum.armbian.com/topic/17597-csc-armbian-for-rk3318rk3328-tv-box-boards/
Click to expand...
Click to collapse
works perfectly I used still using the same Rom about months ago