Hello. I recently got a Hisense A9, running Android 11 / Hisense's Ink OS with Snapdragon 662. It's a Chinese phone so doesn't have Google Services, and since it's pretty new / not very popular nobody has rooted it yet, and I can't find stock recovery or boot images.
I've been trying to extract the stock recovery.img so I can build a TWRP tree, and then hopefully extract the stock boot.img from a Nandroid backup, but I can't find a way to extract recovery.img from the device (without root access). Is there a way to do this?
I also looked into using MicroG to replace Google Services, but the ROM needs to support signature spoofing, which this device's doesn't. Apart from the 2Accounts workaround for Chinese phones, is there a way to get Google Apps / Services working on this phone?
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.
Hi everyone,
Thank you for reading this thread question.
I have an Android 2.3.3 Mediatek MTK 6573 Phone. I am trying to learn how to make a custom rom. I like to know what tools we need to use in order to develop on this phone and in general. I have a few questions about the process to setup and make a custom ROM.
I rooted my phone using SuperOneClickv2.3.3-ShortFuse. I'm trying to perform backup of the rom before I flash the ROM. I'm atta
1. Backup
http://forum.xda-developers.com/showthread.php?t=1683883
The backup shell script uses mkyaffs2img, but it appears to be missing on my phone. Is there a correct site to get the right binary for mkyaffs2img to execute on the phone?
Currently when I try to backup the last part of the sh file this binary was missing
cat /sdcard/Install/BackUp/yaffs_back_2.3/gen/mkyaffs2image > /system/bin/mkyaffs2image
I tried to get a copy from code.google (http://code.google.com/p/fatplus/downloads/detail?name=yaffs2-source.tar&can=2&q=)
I get the error /system/bin/mkyaffs2image: 1: Syntax "(" unexpected
I tried using Nandroid, but I don't see the system.img or ramdisk.img file that represents the ROM system.
2. Flash ROM
http://bm-smartphone-reviews.blogspot.com/2011/10/mt65x3-flashing-tutorial.html
From the same thread there is mention about SP Flash Tool. What is the scatter.txt file? Do we need to find it some where?
3. Android source
Can we use the android source (http://source.android.com/) to make our own custom ROM? If so how do we include the drivers that are specific to the phone? I can build my own custom system.img and ramdisk.img with the android source and load it on the emulator, but I don't know if I can use those img and flash it onto a real android phone. I'm aware of the idea of android fragmentation, but looking at android source code, it seems we need the specific vendor drivers to be included in the source build. Is this the difficult part in flashing roms for specific phone hardware?
Thanks for you help and explanatins .
I think I'm trying to over complicate things, but this is my first time flashing ROM in android, rather than windows mobile >_<
Best,
SoLi26200
after looking at numerous threads and advice, it seems quite complicated to install a simple fn app, which by definition, is supposed to be easy,
why firefox doesn't have it, considering that most stuff is only available on itunes or google store these days, is beyound me.
Even more so that i thought that the dual core would a) let me run ffos or android ie via easy restart mode,
and b) android would have the google store app.
so. how do i get this on. some ppl seem to be able, and there explanation is: its complicated.
fair enough. i hope you will help me and others to work through this. An explanation for dummies.
this is the best post i'v seen so far.
http://forum.xda-developers.com/firefox-os/general/zte-c-roms-cw-recovery-50-t2806173/page3
along with these links:
http://developer.android.com/tools/help/adb.html
https://developer.mozilla.org/en-US/Firefox_OS/Firefox_OS_build_prerequisites
https://drive.google.com/folderview?id=0B_6NtXCtTLkHeGgzcDVwWnZWR2c&usp=sharing
http://forum.xda-developers.com/firefox-os/general/zte-c-roms-cw-recovery-50-t2806173/page3
so i can change my os from ffos to android and back. no problem:
https://www.youtube.com/watch?v=axOYIfo7y2s
http://down.comebuy.com/Open_c_root_Android4.4.rar
but i get stuck with "adb reboot bootloader"
that won't work, so advice for dummies, from that point forward would be much appreciated. Thanks
ok, so tried installing two other adb programs, http://www.rockchipfirmware.com/sites/tntfiles/PDAnet-64bit.zip
and while neither where completely successful, they did manage to allow adb to access phone,
and for the commands to have determined affects, so have moved on to Upgrade tool, which does not recognize device, thoughts? help?
Hi darth lotus,
To install google play store, you need to be able to write to the system file system, to do this you would either need to root and push google apps (gapps) via adb, or replace the stock recovery with a custom recovery which will allow you flash .zips that are not signed by ZTE.
Installing clockworkmod recovery, for example would allow you to do this,
There are examples of clockwork recovery here http://forum.xda-developers.com/firefox-os/general/zte-c-roms-cw-recovery-50-t2806173 and here http://www.modaco.com/topic/373213-recovery-clockworkmod-6050-for-zte-open-c-kis-3/
And TWRP recovery here http://www.modaco.com/topic/373288-recovery-twrp-2710-for-zte-open-c-kis-3/
The second clockwork and the twrp recovery are by a developer named Konstat who has uploaded all his sources to github https://github.com/KonstaT/android_device_zte_kis3
Konstat has also started work on getting a stable version of Cyanogenmod 11 on the ZTE Open C, please see here http://www.modaco.com/topic/373214-devrom149-cyanogenmod-11-android-444-for-zte-open-c-kis-3/
I apologise for linking to a different website but until we can ask xda to create a zte open c forum, I do not really have an option :crying:
I have a very challenging ROM dump to preform and was hoping for a bit of guidence.
I bought a Chinese table. Why you ask? Well because it has an Intel Core M with 4gigs of Ram and a retina display. Of course with a Chinese tablet comes nonexistent customer service and poor firmware development. What makes working with this tablet even tougher is the fact that the manufacturer of the tablet has disabled the usb port. You can still use the port for hardware but not for OTG. This means no Adb or Fastboot. The stock recovery is very basic with no extra features. Even if there was a custom recovery I couldnt flash it anyway.
The supplied Android firmware was in Chinese and loaded with bloatware Since it was meant for the Chinese market there was no Gapps with Playstore. Plus the OS wasnt rooted.
I managed to discover a rooted copy of the firmware on a Chinese forum site.... and no I don't speak Chinese. I was able to switch it all to English, de bloated, install playstore and fix a few problems. Now I am ready to make a backup for myself and other owners of this tablet. But with no custom recovery, no Adb or Fastboot I am not sure how to do this.
The firmware was originally distributed on a .img file that could create a bootable USB. You boot to the USB and a script would launch that would install all the .img files, (system.img, userdata.img, etc. ) My plan is to create the new system image files and replace them on the original USB. So I would have a bootable restore did with the modified firmware.
My problem is that I am not sure how to create these system .img files. I would prefer not to have the image creation tool as part the the new modified firmware.
Any direction would be appreciated.
I have an android device running Android 5.1.1 but on a proprietary build that doesnt include GApps.
What i want to do is root the device, but in order to do so with Magisk, I need the Stock ROM boot.img file which I cant find anywhere because they arent open source like Samsung ect. There is also no TWRP build for it, official or ortherwise.
The device is a Rand McNally OverDryve 8 Pro.
Anyone have any ideas on how to get the boot.img file without having exising root or TWRP? Maybe with adb without root though, unless some way to gain root shell without root device.
Or can anyone point me to a DETAILED, uptodate guide on how to compile TWRP myself, inculding setting up the build envirment and which version of Ubuntu I should use. I have tried previously with some older guides using Ubuntu 12.01 or somthing but lots of sync and repo issues and such and i gave up as im jist learning on the fly and not capable of deep troubleshooting.