I hope I got the right place to post.
I have a Measy U4K miniPC stick that came with an Android 4.1.1 ROM. Measy did not make this ROM public, nor have they provided the promised 4.2.2 update.
However, the TV Box CS918S has had multiple releases of 4.2.2 ROMs and has the very similar architecture. I can flash the ROM but wifiand SD card don't work. After a lot of investigation and meddling I have traced this to the Wifi Power pin being different, the CS918S uses dld01 whilst the U4K uses aldo1.
I have used both Windows and Ubuntu based kitchens to try to amend the ROM to work on the U4K but with no joy. The key files that controlled config in the 4.1.1 builds such as sys_config.fex, bootloader.fex and script.bin seem no longer to matter. In fact, script.bin no longer exists.
From what I can see u-boot.fex has the config compiled in. I've tried hex modding to change dldo1 to aldo1 but then the image won't flash, presumably due to CRC error.
Can anyone help me out with this?
For ref the latest firmware can be downloaded from [link deleted as I do not have privilige yet]
Related
Hey guys, Ive got a question.
My company has an android application that we license to companies, and we would like to purchase a few hundred android devices to load our application on to and then sell the devices at cost, but license the software that is on the device.
We have looked at several different android devices and saw the Archos 43 at a good price point, with the screen size we want. We are currently using Motorola i1's, but want something cheaper, and something that give us the ability to customize what firmware is on the device.
I was wondering if there is quick way (remember, we are going to have hundreds of these devices) to load our application on this device, and strip/remove all pre-loaded applications that came with the device.
We only need the wifi and the camera to work.
Would it be easiest to have a custom ROM that has basic Android with our program built in? Can this even be done, and are there any restrictions on this device as far as flashing a custom programmed Android OS. I see on Archos's website they talk about being able to load custom images, but not much detail about it.
On their website it states, "...ARCHOS has ‘opened up’ their Internet Tablets allowing users to install or even replace the Android system installed on the device."
This statement says that its "opened" up the tablets, but throughout the forums I see that the device doesn't already come rooted, and you need to root it before flashing a new ROM.
Thanks,
Christopher
1. Std. Archos is not rooted and is not even able to be rooted atm.
2. Archos has provided the SDE, a customised FW that allows a second kernel and Initram to be installed.
3. because you can then remove the Archos Android you can have a "custom rom".
You can't really stip down the Android to a point where it is secure without a very good knollage of android and the device itself.
To see how easy a custom ROm could be installed, look at UrukDroid installation.
http://code.google.com/p/urukdroid/wiki/Installation
Hey Chris
What you've read on the ARCHOS website is the SDE firmware. This "special" firmware from ARCHOS will not replace the operating system but it will you allow to install any custom kernel / initramfs.
So I think you better stick with the original firmware, but modify the system image as far as you want to go. Then you modify the init script in the initramfs to do not check the signature of the system image and there you go, easily customized Android, based on the original ARCHOS firmware.
BUT: Even though it's quite easy to flash a custom kernel / initramfs (just boot into recovery mode), it's not that easy to replace the system image because you have to write some scripts in the initramfs to do so and to be able to "upgrade" the image, etc..
That's just my input. Have a look at the links in my signature for further tricks and hints how to do stuff and links to my projects which are based on SDE and ARCHOS firmware.
There might be another solution, stick with UrukDroid (search the forums), an already highly customized and improved version of the official ARCHOS firmware, including installer, tools, etc..
Thank you both for the fast replies.
I'd rather not try go the two routes you have mentioned just for legality reasons, because the devices will be resold and I wouldn't want to get into that area...
Do you know of any devices that are more open to modification?
Thanks again.
Just yesterday i stumbled across http://www.taztag.com/index.php?opt...e&id=75:tazcard&catid=38:slideshow&Itemid=125
I don't know a price, but esp. for my needs the nfc part is interesting.
Please need some help with C12R1. I have this:Telechips TCC8803, 2Din Car Media Center Running Android 4.0.4 ICS
2 Din Car DVD Stereo GPS+ CD Player +MP3 +Bluetooth +Ipod +WiFi+ 3G+7 inch Android 4.0 Tablet Car PC Media
Android: ICS 4.0.4 rooted
Hardware Pad
CPU:Telechips TCC8803,1.0GHz; Cortex-A8 Kernel, 45nm processing.
RAM: DDR III 512M
ROM FLASH:4GB
Power IC:TDA 7388/LA47002/TA2929/TA2939
Extended memory card:Up to 32GB SD/TF card
WiFi:Bulit-in High performance, low power consumption, Atheros 6302 WiFi802.11b/g/n.
3G:3G Universal Drive ---Support extral USB Dongle:WCDMA,EVDO,TD-SCDMA GPS,JRC G591Receiving Module
G-SENSOR:3 axis acceleration sensor and 3D IC hardware acceleration,could realize dynamic 3D game and 3D interface.
CAMERA: support 0.3-2 Megapixels rear camera
Speaker:built-in speaker,1pc 1W,8Ohm
Micphone:built-in, high sensitivity input, right&left channel
Indicator light:built-in red charging indicator light,built-in vibration motor
Hardware CarAudio System
Operation System DVD platform
CPU:Toshiba TMP86FS49UG
Display:Supplier:Innolux
LCD:7 inch 800*480 HD, TFT digital screen, Resistive touch screen.
MODEL Nr: C12R1 (crane)
Baseband version: 1.4rc2
Kernel version: 3.0.8 [email protected] - 102 # 447
Build number: crane_C12R1-eng4.0.4 IMM76D 20131114 test-keys
took it from this thread: http://forum.xda-developers.com/showthread.php?t=2572265
My problem is I've accidentialy deleted my /system/app/* and /data/app* files trying to free some space / I wanted to copy it on extsd card with X-plore app but it didn't work out for me I've copied the files above the number of the sdcard and they're gone / don't do this it's dangerous, and I've lost all of them. And my tablet started with the errors and stuff and I wanted to throw it off the window, than I settled down for a bit.And before a week or so I've started looking for 4.0.4 roms compatitable system apps for my rom, I've tried maybe 40 roms by now /I download the rom / extract the /system/app, and /data/app folder and try to run the tablet, but it didn't work out. I managed to run it with modacocustomrom reading one of xda threads but it started throwing exceptions. Then I've started deleting one by one system apps and I've come to the conclusion that the system could run only with 3 apk's - launcher, settings and settings storage. It started but it is not the same and I've lost all my preffs and stuff.
Please if someone have C12R1 send me /system/app/ and /data/app files. for 4.0.4 android
Appreciate it. Thanks in advance.
And could you tell me how to unpack this rom (WooComet-MiOptimusOne.com -ICS_4.0.4- F1中性－20120920.1.0.3－A721_V4.2.img) from this thread - http://forum.xda-developers.com/showthread.php?t=1925577 without the device connected to pc and this program: LiveSuit.exe. I've tryed with dd in linux on flash and with mounting img in linux but it coudn't work out why?
I've tried to unpack the img with ext4 unpacker and ext2 explorer too but it couldn't work out.
please help!
Ok guys I managed to do this, I've made the last step /flashing the rom (I wanted just to copy the system files in internal memory in /system/app and /data/app but couldn't find it anywhere), I did'nt wanted to do it this way but I've done it cause it wasn't anything else left to try after long sleepless nights
I've installed a new stock rom sun4i_crane_t02a.img and android launched but now I have another significant problem - I dont have a proper driver and my touch screen does not work.
And my android's usb debugging is not with turned on and I cant use adb or so....
Any ideas?
Please if someone have this touch screen drivers or stock or other rom that works on this device please send it to me!
This is the exact device:
http://www.aliexpress.com/item/2-Di...92768377.html&cv=11032041&af=cj_6149808&vd=30
but I cant find roms anywhere for it
Hi Razer69
I see you still have problems with your device.
Well before i wend on a Rom hunt i have managed to install CWM recovery on mine and make a backup of the stock rom, in order to test various roms, and if they do not work i restore the stock.
If you want i can create a link for you so you can download it and install it. Bare in mind though i have made some mods prior to the stock rom so it worked a bit better that when it arrived.
Did also find a link for your issue with the touch screen ----> http://www.pandawillforum.com/archive/index.php?t-12129.html
Cheers
G
Could you share how did you managed to install custom rom - clockworks - CWM because that is my problem now.
I can't install the rom because I've flashed my device - all partitions - kernel, recovery, rom - with LiveSuite and .img file but eventually
I found out this rom is not for my device - the rom I've installed is C12 not C12r1, and I'm still looking for C12r1.
Thank you for your answer
I've come to the conclusion I'ts wrong rom that's why the touch screen is not working.
This guys are writing the same here:
http://www.pandawillforum.com/archive/index.php?t-12129.html
"sun4i_crane_t02a.img is not work with FT5306DE4 Chipset,is wrong point of touch screen"
Today I'll try their methods
thanks
Hi all,
I'm quite new with android and this explains why I'm here asking for help and direction to solve a problem. I've a chinese phone based on MT6577 hw; it's branded ORDRO P550 4.1.1. Well, months ago I was able to root it but after some months it started to be unresponsive and very slow. Perhaps because I moved some software from ROM to SD in order to get more free memory. In fact, MT65xx comes out with only 512 MB of ROM/RAM. So, I found and application named MT65xx_repartition and I decided to check if it did what it promised. Basically, it claims to be able to repartition the internal memory, using phone's internal memory to increase phone's RAM.
I made a backup of what I needed and I was able to find a stock ROM of the same model from a web site.
After running the repartition program my poor phone did not start up again; it only showed the small robot wit a big exclamation mark. OK, I thiught, I've the original ROM.....let's re-flash and learn something new. After several attempts to install USB drivers on my virtual Win7/64 box I was able to re-flash the ROM again. Et voila'....it was reborn but, alas, a little bit handicapped.
First of all the IMEI was wrong or not existent so I got no carrier and secondly, the camera didn't work at all.
For the IMEI issue I was able to fix it thanks to Mobileuncle Tools (fortunately I made a backup of IMEI before proceed) but I could not find a solution for the camera.
I checked and googled everywhere and I think that it could be a driver issue...something related with libcam*.so files but I have absolutely no idea how to fix them; do I need to recompile the drivers? I checked init.rc file but I found no evidence of libcam*.so modules nor any insmod instruction to load them. I'm not really familiar with linux; I'm moving my first steps with it and the only complicate thing I did was to recompile wifi drivers for my Debian Virtual box.
Here a partial list of phone's details collected by Mobileuncle Tools:
CPU
CPU ARMv7 rev 0 (v7l)
Hardware MT6577
Kernel
Linux Version 3.4.0
OS
OS brand ORDRO
Model P550T
Bootloader unknown
Prouct e1901_v77_gq2002
Display e1901_v77_gq2002_2013.03.25
Release 4.1.1
fingerprint alps/e1901_v77_gq2002
MTK Build
.platform = MT6577
.chip_ver = S01
.wlan.chip = MT6628
The main difference between this ROM and the previous one (for completeness I forgot to download) is the ROM size; now is 878MB (?) instead of the previous one that was 493 MB.
Thanks a lot for any support or direction you can give me; I'm looking for a set of instruction to solve this problem and learn something new.
PK
Hello,
I've purchased this one: http://www.dx.com/p/x96-tv-box-andr...-2gb-ram-16gb-rom-us-plug-449347#.WPuxONryuUk
Just wondering what ROMs and recoveries work. I've searched a bunch and found some dead links and conflicting information so I'm hesitant to flash it especially where I do not have a stock image to go back to if it renders it bricked.
If anyone can help out, it would be much appreciated.
Thank you,
Scott
Note: Keeping a repository here as I find more information about this box: https://drive.google.com/open?id=0Bzj6JjnAJZjjczVIbFlHS3VUWlU
Working on it
Custom TWRP and stripped down/modded firmware is on the way.
I hope we can get a pure Android Rom working on it
Again: Working on it
Fully unbranded and hopefully with unlocked custom bootanimation (Original Google would be my prefered option over Mbox).
Give me a bit of time and you will find flashable ZIP soon
All done
Another question about the box: is-it possible to have Android TV instead of a modded android marshmallow? Because the interface would be a lot easier to use.
Android TV is a complete different story and you can't really compare the two like this.
Android TV uses the Leanback launcher if I am not mistaken.
Already tried to include it into a testrom but so far no real luck as it uses a lot more binaries that are not included in the standard system.
Will have to create some symlinks, add binaries and do a lot of testing - not to mention finding all the included apps for android TV and figuring out how to make them work.
If the interface is your only trouble check some nice launchers first, like Apex for example.
Once I have something cooked up that actually works as expected you will find it in this section somewhere
Also interesting to test that , as mine is not even root ^^
Rom
Any news about the firmware for this device?
Nope, still no updates coming from the chinamen, seems they already abandoned firmware updates and moved on to different devices.
See this thread (beta 6 I used for.mine)
https://forum.xda-developers.com/an...gic/rom-x96-2-16gb-root-supersu-twrp-t3596525
I join the thread because because of a storm my X96 looks brick. I've been looking everywhere but I do not find the guide for unbrick. I wanted to save it not to throw it but I do not know where to download the firmware how to do unbrick. I know I'm in the wrong thread but I did not want to open it a lot like this and make it confusing. Thank you all
As long as you get into the TWRP recovery on the SD card all should be fine - assuming the box is a X96.
If that fails only the burn tool or burn card maker can help with a genuine firmware to get going again.
Hi guys sorry to bump an old thread. I'm still trying to find the TWRP zip for these so I can do a complete back up and then paste on other boxes.
Have an X96 Amlogic S905X Quad Core 2G/16G Android 6.0 Wifi HD 4K TV Box.
I flashed the FULLY UNBRANDED Kodi 17, everything looked fine but the box's red light just stays on after the reboot.
Does not go into TWRP at all or nothing on screen.
It now a paperweight?
Downloaded the Stock firmware (Android 6.0.1 X96 Amlogic S905x 20161122) and am trying to start box with a bootable SD-card.
BurnCardMaker asks for an IMG file with all the relevant (aml_autoscript, factory_update_param.aml, firmware.zip, recovery.img, u-boot.bin, etc) files in but i cannot find this IMG file.
Without these BurnCardMaker does not work at all or nothing happens on TV box at least.
Must also say, i use a 64gig SD card but it worked for the initial flash.
Am i wasting my time with this box now?
Thanks for help.
Hi everyone,
as title suggests, I'd like to "port" clean AOSP to be able to install and run it on the custom device.
Basically, the situation is following: I got a custom device, based on rockchip rk3288 SoC. The device currently runs Android 5.1 successfully. I'd like to update Android to version 6 (got AOSP sources and AWS builder image up and running), but the company that created Android v5 for us no longer exists.
Thus I am here to ask for advice(s) on how to proceed (or whether it even is a good idea to do that myself, given the fact that I have zero experience with Android ROMs development), possibly a step-by-step guide on what to do.
The question is, do I just find drivers for hardware components present in the device (usb hub, ethernet, etc.) and just somehow "link" those to existing sources (of AOSP) and just run the build with different parameters? Or do I need to build a whole new kernel for the given device-OS combination?
Thank you for any advice or opinion!
Well this is an interesting one. There are several routes you can take here.
If you have the kernel source code, and the source code for the drivers, you could probably build the kernel from source and use it to boot Android, however, as that's unlikely, you're looking at a more regular porting process, which usually consists of pulling the vendor blobs from the existing Android system, building AOSP/Lineage with those blobs involved, and hacking together a new ramdisk that HOPEFULLY will be compatible. It's a very long and very tedious process, but it's certainly possible.
From that you'll then get in to the debugging stage of finding out what works out of the box, you'll very well need to make changes to AOSP for it to work on that SoC.
abtekk said:
Well this is an interesting one. There are several routes you can take here.
If you have the kernel source code, and the source code for the drivers, you could probably build the kernel from source and use it to boot Android, however, as that's unlikely, you're looking at a more regular porting process, which usually consists of pulling the vendor blobs from the existing Android system, building AOSP/Lineage with those blobs involved, and hacking together a new ramdisk that HOPEFULLY will be compatible. It's a very long and very tedious process, but it's certainly possible.
From that you'll then get in to the debugging stage of finding out what works out of the box, you'll very well need to make changes to AOSP for it to work on that SoC.
Click to expand...
Click to collapse
Thanks for pointing in the right (or at least some) direction! I found some guide on porting ROMs which I followed, basically like you said. So I just replaced some files in System image. Will flash later today, so maybe I will get some results!
abtekk said:
From that you'll then get in to the debugging stage of finding out what works out of the box, you'll very well need to make changes to AOSP for it to work on that SoC.
Click to expand...
Click to collapse
So I was following this tutorial, although found some irregularities, let's say: For example, none of those 2 folders contained init.d/ directory, thus I didn't update it. Also, I haven't found META-INF folder therefore haven't updated updater-script.
Basically, when I did (or at least what I think I was doing was that I took /system partition from our current ROM, that is working on that custom device and replaced stuff in there by stuff from the new system I wanted to port. My idea from what I've read was that i took kernel (and boot/recovery) from the original, working ROM and "injected" the new system onto it. Is that correct? Is that what I needed to do? Because the problem is, I cannot boot into the system (might as well be because of Kernel version, because I am trying to port Android 6 on Kernel 3.10. which was used in the current ROM running Android 5). It looks like the device is stuck in bootloader, or "somehow doesn't know what to start" (sorry, I can't put it better), displaying only my device's logo.
When I connect it to the computer via USB cable, running adb devices shows me that device, but when I try to access shell using adb shell I got error saying that /system/bin/sh wasn't found, which made me thinking that somehow the /system partition isn't "linked" properly, like I stated in the beginning.
Was I doing everything correctly? Do I need to do something above that? (maybe do you know about some tutorial). I am trying to port AOSP 6 Android.
Thank you!