Related
Hi everyone!
Got this Miphone A3 yesterday, and I been searching like a fool after information about this damn phone but it ain't a easy thing to find.
But hey, what do you expect from a cloned iphone
So here's my question:
Anyone sitting on a Miphone and have you done anything with it, most imporant for everything, ROOTED?
Phone info on the phone:
Model number:
A8
Where I bought it, it said A3 on the site (mobino1), same on the battery.
But instead of the iPhone Ui it has the Android Ui pretty sweet that it didnt have the iPhone Ui.
Firmware:
1.5
Don't have Android Market app, but everything looks like Android, also works to install . apk apps tried to install apps from 1.6+ but doesn't work.
Kernel:
2.6.25
Build number:
Linkworld Project .0002_A.1_01r_100129
Been looking for that build number for a while now, don't have any info at all on that one.
Hope some1 here has some info, would be a blessing for me!
EDIT:
I found my way into what i think is the recovery mode, came up a where is said enter flash mode put in usb cable, with red background. Then when i did that, the screen turn blue saying "Enter Flash mode, Begin to flash image..."
Been reading a lot, and i never came up with that kind of "bootloader" just saying that
hope some1 could give me some tips
hi, one of the stores provided firmware from A3, I do not know how fresh. ussd queries are unsuccessful, after ussd calls to hang up. In flash mode turns pressing the upper side volume buttons and switch.
depositfilescom/files/0po3pwcu6 - miphone A3 rom
thanks for that one!
flashed my phone, worked! but it wasnt the same version. this one was with the iphone ui (using ahome)
Model number:
A3
Build number: A3 Project.0001_18r_100411
Seems like my 3G connection does not work with this version. ussd, unsuccessful on this version too, same with previous version.
I was wondering, tried to open the one.bin (flash image) but cannot extract it. Any way to extract the image and try to reconfigure the build?
the phone using "tavor platform" flashing software, anyone know anything about tavor platform?
still trying 2 modify the rom I have, no luck so far.
I do also have this phone from mobino1...
how do you try to modify the firmware you have?
Regards,
xift
miphone a3
I too am with the same problem I have software for Tavor flashing but without success for updated the firmware is in a single bin file without being able to extract and modify
if anyone knows how do to then updated
xift said:
I do also have this phone from mobino1...
how do you try to modify the firmware you have?
Regards,
xift
Click to expand...
Click to collapse
I been trying to extract the .bin file MagicIso can read the file using it "missing files" but can't read the files when extracted. Trying to find a program that could read the rom file, have you done anything to update the phone? Do you have a rom file, if so could you upload it pls?
tried to get the firmware from mobino1 but they just ignore mig those bastards.
Ernest25
miphone a3
I too am with the same problem I have software for Tavor flashing but without success for updated the firmware is in a single bin file without being able to extract and modify
if anyone knows how do to then updated
Click to expand...
Click to collapse
Do you want to flash your phone with the .bin file you already have or do you want to know how to update the phone to android 1.6+?
To flash your phone with tavor flashing software, you need to run the flash program in XP and press "volume up" and "power" on the phone to get to flash mode, then plug in the usb with the flash program open, and it automatically flash the phone.
About updating the phone to a newer version of android I have not a solution.
I been trying to, get info on the hardware so I could try to cook a own rom with at least android 2.0
Cheers
sorry i don't have the firmware as a rom file either...
and these mobino1 bastards ignore me too ^^
although they admitted they could contact the developers...
new firmware would be nice... or at least the current firmware.
I did not downgrade it yet and I think I won't do that.
Another problem could be that the bootloader only runs signed firmware image (just guessing).
I know how to flash I want is a newer room the problem these Chinese are not then updated dependent on us for a updated
(question) has a possibility to use, one firmware and change to a bin file to MiPhone a3
xift said:
sorry i don't have the firmware as a rom file either...
and these mobino1 bastards ignore me too ^^
although they admitted they could contact the developers...
new firmware would be nice... or at least the current firmware.
I did not downgrade it yet and I think I won't do that.
Another problem could be that the bootloader only runs signed firmware image (just guessing).
Click to expand...
Click to collapse
Ernest25 said:
I know how to flash I want is a newer room the problem these Chinese are not then updated dependent on us for a updated
(question) has a possibility to use, one firmware and change to a bin file to MiPhone a3
Click to expand...
Click to collapse
If they just told me straight up, we just sell the phone, we don't have any contact what so ever with the manufacture or developers I would accept it. But this just pissed me off.
I've been asking around on other sites that sells the phone, waiting on answers from them. Hopefully they are more friendly.
Don't downgrade, that was a mistake for me (the rom file azat182 nicely posted).
I tried something yesterday, made a own .bin file with android 2.1 but the flash program wouldn't start with it (parse ini error) so I tricked the flash program that it would flash the one.bin (azat182) rom file.
After it opened I replaced the .bin file with mine. Everything seems to work fine, did every step it should like, root system etc finished 100% when I tried to turn the phone on I couldn't, maybe it didn't know were the power "button" source came from.
The android source was made for an other phone, so I wasn't surprised.
Plugged the usb back in, and luckily the phone connected somehow with the computer so I flash it with the (azat182) rom and I'm back at square -1
but now I think, if I could find out the hardware/drivers on this damn phone it would work to cook a own rom using that method.
Cheers
Oh hey, someone else with one of these phones. I've been messing with mine for a while, started out with the A8 rom (from fastcardtech), and have flashed the A3 rom to the device. I've noticed that the gps works a lot better in the A3 rom than the A8, so it's not much of a downgrade, imo. Recently I've made some headway with an android 2.1 port to the device.
Anyway, this device isn't hard to root. If you adb into it, you can get root from the device by remounting /system as RW and pushing a fixed su binary to /system/bin, or wherever it goes, it's been a while
The MTD partitioning in the Miphone's rom is a big giant mess. The rom is split into 25 partitions, the kernel isn't in boot.img like it's supposed to be, neither are the kernel parameters.
The bootloader is dumb, it doesn't check for signed images. The A3 image and A8 image are both engineering builds.
wow you seem to know a lot about it...
does 3g work for you in the a3 rom? also gps doesn't work for me in a8... so a3 could be a possibility if 3g worked.
how did you adb your phone? I could not connect... the driver just didn't show a phone. although I changed the vendor ids etc...
could you write a short tutorial of some sort? would be nice!
if you are root, couldn't you make a backup of your firmware?
is there a downloadable a8 rom at fastcardtech?
regards, xift
I haven't been able to get 3g working, just edge. I don't think the 3g will work in the US, as none of the carriers will work with just wcdma2100, but I'm no expert on the subject. I've had reasonably good luck with the gps with an app called Maverick, but I don't have a data plan currently, so no agps. With gps alone, it takes about a minute or so in an open area to acquire a lock.
For ADB, there's a driver in the android sdk, but don't bother with it. Instead, the phone's going to show up as a rndis/ethernet gadget. For windows, drivers for this can be found at webos-internals.org/wiki/USBnet_networking_setup, just the .inf is all you'll need; MacOS and Linux will just see the ethernet gadget. Once that's installed, the phone will show up on the PC side as a network interface that will need an IP address; I've been using 169.254.231.10 and subnet 255.255.255.0. Once your network interface is configured, you should be able to run adb connect 169.254.231.168:5555, assuming you've got your android sdk tool set up already. From there, you can adb shell in and poke around. Once you get an adb shell, you'll have a root prompt, but to get 'rooted' so that other android apps can make use of it, you'll want to run adb remount to remount /system as RW, then copy a working version of su over to the phone. I think superuser whitelist comes with one.
I don't usually go to that much trouble, as I end up cycling between the A3 firmware and my Eclair build a lot, and the A3 rom is jacked up to where it's a pain to get a terminal emulator running on it. Adb from my desktop seems to get the most mileage.
Fastcardtech didn't have any useful information about recovery firmware that they had, a release date for an android 2.1 rom, information on the manufacturer, anything.
Wow thanks a lot... I tried with the sdk driver.
port 5555 seemed blocked there although it was obviously responding (took much longer than other ports). Thanks for your help - I'll try that one.
Could you upload your eclaire build?
I don't have much time at the moment because of my bachelor's thesis. But I'd like to see that and maybe I could help a bit. Although I do not have any experience with mobile devices etc.
You may need to mess with the usb debugging option. After flashing to the a3 rom, it's enabled. I remember it being the same between the a8 and a3 roms.
At some point, yeah, I'll my eclair build up. I'd like to at least get bluetooth, gsm and wifi going again before I do. I don't have a rom that you'd be able to flash currently; more like a big pile of build scripts, and install scripts for the android system and ramdisk.
yeah I understand that. You could open a google code project or something.
nice to know that there is somebody working on this.
usb debugging is enabled by default. I'll just have to try again.
thanks for your help so far.
file inf
I not have disk only cd and dvd when I will install the drive without the disk says no drive found I save the file as usbnet-pre.inf
if anyone can help me pls
well I also had problems installing the driver in windows ...
It always said something like "No driver found at that location".
You could try on linux though... It worked like a charm for me.
I'm root now
@nsigma is there anything I could provide you from the a8 image?
xift said:
well I also had problems installing the driver in windows ...
It always said something like "No driver found at that location".
You could try on linux though... It worked like a charm for me.
I'm root now
@nsigma is there anything I could provide you from the a8 image?
Click to expand...
Click to collapse
linux complicated for me but thank you I hope good news from you about how root this bastard mobile
I have the A3 if you're interested I can pass to you
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 everyone.
Can we please get root on this phone?
Specs are:
Operating System: KaiOS
System chip: Qualcomm Snapdragon 205 MSM8905
Processor: Dual-core, 1100 MHz, ARM Cortex-A7, 32-bit, 28 nm
Graphics processor: Adreno 304
System memory: 0.5 GB RAM
Built-in storage: 4 GB
Storage expansion: up to 64 GB
sgmarouf said:
Hello everyone.
Can we please get root on this phone?
Specs are:
Operating System: KaiOS
System chip: Qualcomm Snapdragon 205 MSM8905
Processor: Dual-core, 1100 MHz, ARM Cortex-A7, 32-bit, 28 nm
Graphics processor: Adreno 304
System memory: 0.5 GB RAM
Built-in storage: 4 GB
Storage expansion: up to 64 GB
Click to expand...
Click to collapse
Im also wondering the same thing
Yes, have been able to flash my own system and it is also possible to get ADB.
I am currently working on it, but it might take some days to get something useful out of it. As I just created a new account here, I am currently not able to post any links, but you can find my stuff linked on Twitter via @nexus511.
nexus511 said:
Yes, have been able to flash my own system and it is also possible to get ADB.
I am currently working on it, but it might take some days to get something useful out of it. As I just created a new account here, I am currently not able to post any links, but you can find my stuff linked on Twitter via @nexus511.
Click to expand...
Click to collapse
Good job! :good:
0312birdzhang said:
Good job! :good:
Click to expand...
Click to collapse
Short update:
I have been able to gain root and I have also been able to modify selinux policies on the device. Then I have been running into some strange behavior. It actually looks like the kernel is telling to be running in permissive mode but even a permissive context seems to be enforcing instead.
I will try to use something like "Magisk" instead and see, if a service can solve this issue.
For anyone interested: The kernel-config can be extracted via /proc/config.gz. The dtb is compiled into the kernel image. Maybe I try extracting the dtb and building a codeaurora kernel for the device and see, how far I get with that. This might resolve the strange selinux issues I currently see.
nexus511 said:
Short update:
I have been able to gain root and I have also been able to modify selinux policies on the device. Then I have been running into some strange behavior. It actually looks like the kernel is telling to be running in permissive mode but even a permissive context seems to be enforcing instead.
I will try to use something like "Magisk" instead and see, if a service can solve this issue.
For anyone interested: The kernel-config can be extracted via /proc/config.gz. The dtb is compiled into the kernel image. Maybe I try extracting the dtb and building a codeaurora kernel for the device and see, how far I get with that. This might resolve the strange selinux issues I currently see.
Click to expand...
Click to collapse
This is a good news! I just bought a "banana" today, waiting for your good news :fingers-crossed:
nexus511 said:
Short update:
I have been able to gain root and I have also been able to modify selinux policies on the device. Then I have been running into some strange behavior. It actually looks like the kernel is telling to be running in permissive mode but even a permissive context seems to be enforcing instead.
I will try to use something like "Magisk" instead and see, if a service can solve this issue.
For anyone interested: The kernel-config can be extracted via /proc/config.gz. The dtb is compiled into the kernel image. Maybe I try extracting the dtb and building a codeaurora kernel for the device and see, how far I get with that. This might resolve the strange selinux issues I currently see.
Click to expand...
Click to collapse
Sounds like you've made some impressive progress here, can't wait for more details!
Will you be posting a more detailed tutorial/how-to here or on your blog in the future?
Keep up the great work! :good:
Great work, would be great to uninstalled preinstalled *tty demo games.
@nexus511, any way you could please share the root procedure or point to some resources?
Or...at the very least when you get a spare second, how you did manage to unlock your bootloader knowing Nokia has publicly acknowledge disabling Device > Developer?
Muchas,
nexus511 said:
Short update:
I have been able to gain root and I have also been able to modify selinux policies on the device. Then I have been running into some strange behavior. It actually looks like the kernel is telling to be running in permissive mode but even a permissive context seems to be enforcing instead.
I will try to use something like "Magisk" instead and see, if a service can solve this issue.
For anyone interested: The kernel-config can be extracted via /proc/config.gz. The dtb is compiled into the kernel image. Maybe I try extracting the dtb and building a codeaurora kernel for the device and see, how far I get with that. This might resolve the strange selinux issues I currently see.
Click to expand...
Click to collapse
fpb4 said:
@nexus511, any way you could please share the root procedure or point to some resources?
Or...at the very least when you get a spare second, how you did manage to unlock your bootloader knowing Nokia has publicly acknowledge disabling Device > Developer?
Muchas,
Click to expand...
Click to collapse
Use OmniJB can enable "Developer Mode".
Tested on sideload mode
0312birdzhang said:
Use OmniJB can enable "Developer Mode".
Tested on sideload mode
Click to expand...
Click to collapse
Cheers mate :good: , that's a step forward (and cookie points to OmniJB's dev for the firefox 52.9 esr trick) - now WebIDE lists all runtime apps in Unrestricted DevTools privileges...which is great should I be willing to debug any of those or create my own. What I am looking for though is a way to *delete/un-install/remove* (no cigar remounting /system/b2g/webapps rw without root) some of the certified pre-installed applications (assistant to start with or the bunch of packaged Gameloft bloatware). Any idea - i've pm'ed @nexus511 for some root procedure but no answer yet?
0312birdzhang said:
Use OmniJB can enable "Developer Mode".
Tested on sideload mode
Click to expand...
Click to collapse
Is there anyway I could revert installing omniJB? I'd love to be able to install factory updates again.
hello all, just give an update on how's everything regarding nokia 8110 is going
fpb4 said:
Cheers mate :good: , that's a step forward (and cookie points to OmniJB's dev for the firefox 52.9 esr trick) - now WebIDE lists all runtime apps in Unrestricted DevTools privileges...which is great should I be willing to debug any of those or create my own. What I am looking for though is a way to *delete/un-install/remove* (no cigar remounting /system/b2g/webapps rw without root) some of the certified pre-installed applications (assistant to start with or the bunch of packaged Gameloft bloatware). Any idea - i've pm'ed @nexus511 for some root procedure but no answer yet?
Click to expand...
Click to collapse
Could you remove the pre-installed apps?
Hi!
It's possible, to get full ADB-Root by injecting a patched adbd-binary. And with real swap instead of zram, the device is more responsive (background-tasks like Launcher/Homescreen are killed less often...)
As soon, as I have build my own patched adbd, I will provide an 'update.zip' -- it seems chainfire doens't like others to use his version. (OpenSource -- anyone? )
BTW: no, I don't have 'su' -- only my own priviledged additional startscript and ADB-Root but for me this is more than enough to 'work'
(my goal is to create native apps with Ada/Gnoga - meaning native but with HTML5-GUI. First tests are working well...)
I would love to have this phone without the pre-installed social media and game garbage, would your planned update.zip allow someone reasonably competent at following instructions to do this easily or is experience required?
It should be possible to remove those apps - but for me it's hard to say how. On my device there were no preinstalled apps/games other than snake. Everything else is (un)installable normally. Could be a region-thing
(I've got the european/german version)
-- but on my device the store seems to be a 'static' bunch of zips - so it could kill the store to just remove those.
(i think I would need to adjust configs for the store if I want to clean them up)
If I remember correctly, there is a flag in the app-manifest to config if an app is removeable... my first try would be to edit this flag and check if I could uninstall it normally after this
On the other hand: there is nearly no need to uninstall - KaiOS-Apps are small and with a sdcard....
(I created an extra 1GB-Swap on /data - even then enough space left)
BTW: if You have a little experience with android-stuff, rooting is simple when You know how
Enable adb --> just type *#*#33284#*#* on keypad of your phone (the digits spell 'debug' )
-- build an update.zip - sign with AOSP-Test-Keys
--- let it create '/data/opt', '/data/opt/bin'
--- put an patched adbd (chainfire's v22 works) in /data/opt/bin
--- create /data/opt/init as a shellscript, remounting / rw, replace /sbin/adbd with patched one, remount / ro kill adbd so it restarts the patched version. (you may add commands for other stuff on boot - I disable zram, enable swapfile, start en Ada-Server....)
--- and add a call to '/data/opt/init' as last line to '/etc/init.qcom.post_boot.sh' so this 'init' will start with root-rights on startup.
This way /data/opt/init will inherit root from /etc/init.qcom.post_boot.sh, so it can replace adbd - and because the patched version won't drop it's root-rights you'll have a root shell over adb.
As You see - it's quite trivial, but at the moment I don't have a patched adbd which I'm allowed to include.
(I hadn't time to build an AOSP-tree until now)
Has anyone tried installing OmniJB from 4pda.ru website? (Sorry can't post links)
If you google "4pda 890710" it will bring it up.
Also, anyway of installing whatsapp yet?
PolePolisher said:
I would love to have this phone without the pre-installed social media and game garbage, would your planned update.zip allow someone reasonably competent at following instructions to do this easily or is experience required?
Click to expand...
Click to collapse
root or create an update to edit /data/local/webapps/webapps.json
it worked on my phone no more s*** games and google stuff
Can I not just replace the /sbin/adbd from the boot.img?
(by extracting the boot.img with a flashable zip, and then unpack/repack with kitchen)
Hello everyone !
I have an Eonon GA7156 head unit in my car (Opel Corsa D) for almost a year. At first it was great, but I wanted to improve it and fix some bugs. So I searched a way to root it and even contact the Eonon support, but I found nothing for my case (everything I tried failed) and the support told me it was impossible to root the HU. So if someone has the solution, it would be great !
As I'm a new member, I can't post a link to a picture of my HU version, so I write it here :
Processor type : QuadCore-R16
Android version : 6.0.1
MCU Version : 5.3.19-108-81-943101-170218
System version : V7.3.1_20170309.113422_KTB2
DVD version : 2.13.15-1200xh-150417
I'm new to the Android MTCx head-unit game, but from what I've read, I think you can use Kingoroot (or Kingroot) to root these older Android 6 devices... Certainly can't hurt to try. I would try Kingoroot first.
I already tried this, as well as King Root, and it didn't work. The process gets stuck and it tells that root has failed.
I have read that you sometime have to run the app mutliple times in a row before it actually works - not sure why. If you haven't tried that, it may be worth a shot.
I have an Android 8 head-unit and was able to root it pretty easily via "injecting" su via adb. I'm wondering if that same method may work for Android 6.
https://forum.xda-developers.com/showpost.php?p=76725981&postcount=740
Hopefully someone that is more familair with these radios will chime in...
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.