Hi to everyone,
after two weeks I wrecked my Alcatel Tablet (Telekom Puls).
The Android system recovery 3e offers me among others:
apply update from ADB, sdcard or cache
Root and USB-Debugging are activated.
After starting >adb device< on my windows 7 (USB) I get a correct answer.
The copied file build.porp misses the file permissions I assume.
Any hints and suggestions are welcome.
Thanks in advance.
rfine said:
Hi to everyone,
after two weeks I wrecked my Alcatel Tablet (Telekom Puls).
The Android system recovery 3e offers me among others:
apply update from ADB, sdcard or cache
Root and USB-Debugging are activated.
After starting >adb device< on my windows 7 (USB) I get a correct answer.
The copied file build.porp misses the file permissions I assume.
Any hints and suggestions are welcome.
Thanks in advance.
Click to expand...
Click to collapse
Hello,
If there is a permission issue, You may push your build.prop and give it correct permissions according to these commands.
Code:
adb push build.prop /system/build.prop
adb shell chmod 644 /system/build.prop
adb reboot
-Vatsal
adb sideload
Thank you for your post, Vatsal.
Before I start the adb prompt on the pc the following message I get from the tablet:
Now send the package you want to apply to the device with adb sideload <filename> ...
Hi Guys,
As we all know Tom Tom does not work on the intel units.
For the MTCB devices there is a way to get it working: https://forum.xda-developers.com/an...lution-tomtom-connection-to-internet-t3368026 To get that working you need xposed installed. Since we can not install xposed we can not use that methode.
If we look at this post: https://forum.xda-developers.com/showpost.php?p=69772506&postcount=109 someone already tried to put a serial into the default.prop file but that does not work.
I found this page: http://stackoverflow.com/questions/19368712/where-is-ro-boot-serialno-and-ro-serialno-stored that does not work neither.
http://forum.odroid.com/viewtopic.php?f=94&t=12243
This page says we need to extract the boot.file and use the CarlivImageKitchen tool to extract it so we can modified the file.
I could find the boot.img in the latest update from joying: https://www.carjoying.com/Joying-blog/59.html location: 5009_20.zip.
I tried to extract the boot.img and unpack it with the Kitchen tool and found the init.rc file. Also found the on boot section and added the following lines:
Code:
# Set serial number.
setprop ro.serialno 1234567812345678
setprop ro.boot.serialno 1234567812345678
setprop ril.serialnumber 1234567812345678
Also added those lines to the default.prop file.
Repacked the file and put everything together.
We know that if we put a usb stick with the latest firmware in the usb input from the device it will automatic update and so also the new serial numbers.
The point is, i only wrote a android program a few times and i do not know much about boot files etc.
My question to your developers (because you are 100x times better then i am) would this work? What could probably go wrong if we add 3 lines in the ini.rc file?
Hoping to get some help from you guys!
According to the steps you need to do to get root i found the command to copy the boot.img to the device:
Code:
adb shell dd if=/mnt/usb_storage/USB_DISK0/udisk0/boot.img of=/dev/block/mmcblk0p9
I used the boot.img from the root steps. Added the command in the init.rc file and default.prop. Copied it back to the device and booted.
No luck with the ro.serialno and ro.boot.serialno. serialno was changed to what i have set.
The values of ro.serialno are overwritten somewhere else
Hi,
Have you been able to change the serial no. yet? I'm also waiting for a solution to install Tomtom GO on to this intel headunit
Nope still no success.
I don't have any idea what i can do to fix it.
Put here photo whit error tomtom go please and model headunit and android .
Hi all,
because there is actually no persistend root on the Huawei Mate 9 (system modifivations are discarded after reboot) i would like to run system modifications directly after booting the device.
To do that i am going to use tasker.
For example i want to delete the "camera_click.ogg" file to avoid sounds when making photos with WhatsApp.
Using root explorer i only have to tap on mount system r/w and delete the file.
So i tried the following code in the android shell (which can be run within tasker):
Code:
su
mount -o rw,remount /system
rm -f /system/media/audio/ui/camera_click.ogg
But the system is still not writeable! And mountimg via root explorer only works again after a reboot...
Once with a similar code i got an error message like "resource busy".
What can cause this Problem and how can i delete this system file?
(note: i am not so familiar with Linux, only Raspberry Pi knowledge )
Thank you for helping in advance!
It is same dm-verity problem.
You have to modify boot to turn dm-verity off.
5[Strogino] said:
It is same dm-verity problem.
You have to modify boot to turn dm-verity off.
Click to expand...
Click to collapse
Thank you for your answer!
I will try this tutorial:
https://forum.xda-developers.com/mate-9/development/root-root-mate-9-t3556590
Hope it works...
First off a big thanks to the guys at {Mod edit} for doing all the hard work, I'm just writing this post as a guide for those who don't speak Russian - like myself
Second thanks to all those on the Original Thread (https://forum.xda-developers.com/an...ying-android-8-1-intel-airmont-eight-t3897206) for helping me finally find an android head unit worth buying.
Compatible Firmware Versions:
9853i 800X480 2019.3.20
9853i 1024X600 2019.3.29
"New" 9853i 1280X480 新UI 2019.3.18
"Old" 9853i 1280X480 旧UI 2019.3.18
Legacy Support
2019.3.5
https://forum.xda-developers.com/showpost.php?p=79310679&postcount=43
Changelog:
April 10 2019:
Added new files for several units
Previous Changelogs:
April 4 2019:
Fixed typo in Developer instructions
Added "Ultra Wide" version
March 28 2019:
Simplified Installation Process
Reformatted instructions
Warnings
I am not responsible for bricked devices. Proceed through this rooting process at your own risk.
Rooting your device will void Joying's waranty. (Even though it can be uninstalled in Magisk Manager).
Prereqs
BLANK Flash drive or MicroSD card (1GB is plenty)
A copy of the "Joying Root 9853i ***.zip" appropriate to your device (attached)
Head unit running latest version of Joying firmware (https://www.joyingauto.eu/blog/post/joying-intel-airmont-sc9853i-car-stereo-latest-update/)
Rooting Your Device
Plug your Flash Drive or MicroSD into your computer. Make sure there's nothing on it.
Extract the contents of the device-appropriate archive to your flash drive. You should have 2 files: "lsec6521update" and "6521_1.zip".
Go to your head unit. Moment of truth; no turning back once you begin this next step! Plug your flash drive into the head unit. The update will be detected and the update will automatically begin.
Your head unit will reboot into recovery and install the update containg root. DO NOT POWER OFF YOUR DEVICE OR UNPLUG THE FLASH DRIVE DURING THIS PROCESS!!! If you do, you may permanantly brick your device! Once prompted by the update process, remove your Flash Drive and let it boot back up into Android.
If you would like the more in depth "developer" tutorial, attached is Developer.zip.
Inside I included "Readme.rtf" - a copy of the developer instructions with screenshots.
Senior members, after following the above proceedure, I have a Joying-signed "6521_1.zip" file containg Magisk.
Is this file specific to my unit or will others be able to flash this file to get root? If so it would make the rooting process a lot faster and noob-friendly. Thanks!
Please see attached update file.
Unzip to root of an empty flash drive and plug into head unit. Device will update automatically.
**FLASH AT YOUR OWN RISK, I AM NOT RESPONSIBLE FOR BRICKED UNITS**
I truly TRULY hope you win the lottery..........or maybe even get a raise at work!! LOL.
Thanks!
I literally ordered my HU about 20 min ago. When it gets here Ill check your file with the one I get.
prrlhkr said:
Senior members, after following the above proceedure, I have a Joying-signed "6521_1.zip" file containg Magisk.
Is this file specific to my unit or will others be able to flash this file to get root? If so it would make the rooting process a lot faster and noob-friendly. Thanks!
Please see attached update file.
Unzip to root of an empty flash drive and plug into head unit. Device will update automatically.
**FLASH AT YOUR OWN RISK, I AM NOT RESPONSIBLE FOR BRICKED UNITS**
Click to expand...
Click to collapse
Friend, you are a Lord of Joying!!
Succesful, device rooted at 2 minutes! Enough this zip file and the magisk apk! Many thanks! Now I begin hunting for radio skins and etc
prrlhkr said:
Senior members, after following the above proceedure, I have a Joying-signed "6521_1.zip" file containg Magisk.
Is this file specific to my unit or will others be able to flash this file to get root? If so it would make the rooting process a lot faster and noob-friendly. Thanks!
Please see attached update file.
Unzip to root of an empty flash drive and plug into head unit. Device will update automatically.
**FLASH AT YOUR OWN RISK, I AM NOT RESPONSIBLE FOR BRICKED UNITS**
Click to expand...
Click to collapse
Well done :good:
The magisk patched boot image you have created, is valid for all Joying SC9853i FYT machines. It is based on the firmware and not on your specific unit, and the firmware is identical for all Joyings.
So everyone on the same firmware version with an Intel Joying can use your patched boot image.
The only "but" here is that the boot image can change over firmware versions, so please specify the firmware version for which your patched boot image is, e.g. the "9853i 2019.3.5" version (I assume). It shouldn't make a difference at all whether it is for the 1024x600, 800x480, with or without 4G. All those specifics are not in the boot image.
So the release date is important for the version.
And because of the possible "but": You need to create a new boot image per new firmware version. So if Joying releases a new firmware and you flash it, you better not use your already created boot image, but create a new patched boot image.
If your lucky, nothing has changed and you can use the same.
If you are unlucky you will "soft-brick" your unit, but even in that case there is no worry. You simply take the Joying firmware again and flash it again. Flashing is done by the recovery image. So an incorrect boot image will not boot your unit, but via recovery (reset with a needle or so in the reset (RST) hole) you can simply flash your unit again.
surfer63 said:
Well done :good:
The magisk patched boot image you have created, is valid for all Joying SC9853i FYT machines. It is based on the firmware and not on your specific unit, and the firmware is identical for all Joyings.
So everyone on the same firmware version with an Intel Joying can use your patched boot image.
Click to expand...
Click to collapse
If that's the case could someone upload their signed zip file as I just can't get signing to work on my Mac. Thanks in advance.
colonel_lp said:
If that's the case could someone upload their signed zip file as I just can't get signing to work on my Mac. Thanks in advance.
Click to expand...
Click to collapse
@prrlhkr added it to the 2nd post of this thread.
Whether SC9853i receives any attention by developers like Sofia&PX5 in the future? Extra Tools apk made by Surfer is excellent and mods are enviable
CTDPeti said:
Whether SC9853i receives any attention by developers like Sofia&PX5 in the future? Extra Tools apk made by Surfer is excellent and mods are enviable
Click to expand...
Click to collapse
I will extend my JET apk.
Xposed need to be tested for install. Maybe a direct install from the Xposed installer itself. This should be feasible considered the fact that the Magisk rooting, once successful, should allow for transparent install of Xposed. This would mean that you download the Intel 8.1 version installer and try it.
If it does work, most Xposed modules, including my XFytTweaker should work. I already had a quick look at the server apk, and all functions, calls, etc. are the same. they have not changed over Sogia3G to PX5 now to Intel SC98539i.
surfer63 said:
I will extend my JET apk.
Click to expand...
Click to collapse
EDIT: Rewrite of this post.
To be able to start on this I need from someone with a rooted unit a system listing.
So from a terminal
Code:
su
ls -lR /system > /sdcard/system_list.txt
ls -lR /sys > /sdcard/sys_list.txt
And please attach both files "system_list.txt" and "sys_list.txt" to a post (you might want to zip it )
tried to do but permission denied with su, hope this is what you need, I'm a noob, sorry
CTDPeti said:
tried to do but permission denied with su, hope this is what you need, I'm a noob, sorry
Click to expand...
Click to collapse
Thanks for your attempt, but this is not what I need.
Did you do the "ls -lR"? (uppercase R? This is important on linux systems where the underlying core is of Android).
The su command is actually necessary for the "/sys" folder/file system.
You say that su permission is denied. What error did you get? Did you get a Magisk popup asking you to give root access to the application (once/next 15 minutes/always)?
See also this useful site: https://www.didgeridoohan.com/magisk/HomePage
surfer63 said:
Thanks for your attempt, but this is not what I need.
Did you do the "ls -lR"? (uppercase R? This is important on linux systems where the underlying core is of Android).
The su command is actually necessary for the "/sys" folder/file system.
You say that su permission is denied. What error did you get? Did you get a Magisk popup asking you to give root access to the application (once/next 15 minutes/always)?
See also this useful site: https://www.didgeridoohan.com/magisk/HomePage
Click to expand...
Click to collapse
Sorry for the previous mistache but now i'm in my garage and mendig my motorbike (yeah, spring beginnig in Central Europe ) with some tools and beers. Previous terminal command apk wasn't fully compatible with magisk and not to ask superuser grants. I found a new one and tried to generate other files, hope it is good enough but it is not so easily from an average garage...
CTDPeti said:
Previous terminal command apk wasn't fully compatible with magisk and not to ask superuser grants. I found a new one and tried to generate other files, hope it is good enough but it is not so easily from an average garage...
Click to expand...
Click to collapse
This is exactly what I need. Thanks.
I will start extending the JET apk
surfer63 said:
This is exactly what I need. Thanks.
I will start extending the JET apk
Click to expand...
Click to collapse
One more question. For quite some functionalities I need to mount /system "read-write". That is different per unit. From a terminal it is on the Sofia 3GR:
Code:
su
mount -o remount,rw /system
on the PX5:
Code:
su
mount -o rw,remount /system
(see that the rw and remount are reversed)
If I mix them up on both models I get the error "device or resource busy" or something like that.
So those on a rooted 9853i, please try both commands. If they both work it is nice, if both don't work we have another issue (or challenge, whatever you want to call it)
surfer63 said:
One more question. For quite some functionalities I need to mount /system "read-write". That is different per unit. From a terminal it is on the Sofia 3GR:
Code:
su
mount -o remount,rw /system
on the PX5:
Code:
su
mount -o rw,remount /system
(see that the rw and remount are reversed)
If I mix them up on both models I get the error "device or resource busy" or something like that.
So those on a rooted 9853i, please try both commands. If they both work it is nice, if both don't work we have another issue (or challenge, whatever you want to call it)
Click to expand...
Click to collapse
They both work for me no problems, is this what you're looking for?
prrlhkr said:
They both work for me no problems, is this what you're looking for?
Click to expand...
Click to collapse
Yes, it is.
That is also how it works on every linux/unix system and how it should work, but not on the Joying Android 6 and Android 8 systems.
When I was expanding my JET apk to PX5 (from Sofia) It took me quite some time to understand that the stupid Android versions on those systems were not behaving like they were supposed to.
Edit: as example on my PX5:
Code:
px5:/ $ su
px5:/ # mount -o remount,rw /system
mount: '/devblock/platform/ff0f0000.dwmmc/by-name/system'-> '/system': Device or resource busy
1|px5:/ # mount -o rw,remount /system
px5:/ #
Every unix/linux guru would consider me crazy, until they see it themselves. And on the Sofia it is the other way round.
Stupid FYT.
All,
I made the first experimetal JET apk which can be used on the FYT based Joying Intel Airmont sp9853i as well.
As that is here actually off-topic, I posted that version in the Joying Extra Tools thread.
Please continue in that thread for all JET related questions/remarks/etc. and let's keep this thread for the actual rooting questions/remarks.
surfer63 said:
All,
I made the first experimetal JET apk which can be used on the FYT based Joying Intel Airmont sp9853i as well.
As that is here actually off-topic, I posted that version in the Joying Extra Tools thread.
Please continue in that thread for all JET related questions/remarks/etc. and let's keep this thread for the actual rooting questions/remarks.
Click to expand...
Click to collapse
Surfer, mine is frozen, see attachment
CTDPeti said:
Surfer, mine is frozen, see attachment
Click to expand...
Click to collapse
Thanks. One error detected, maybe 2. Please continue this in the "Joying Extra Tools apk" thread.
With frozen I hope you mean the app, not your unit.
A frozen app can be closed via the App-manager: the rectangle top-right.
Edit: Did you get the question to give root access to the JET apk?
Okay let me start by saying I have been modifying android boxes for several years so the question that I ask is not because I've never done it before. I recently purchased the X88 Pro 10 media box. It has Android 11 as the O/S, and the firmware for the device is from Oct. 2021. I turn on the developer options and try to access the device using ADBlink via the Ip address without success. I then connect the device to my laptop via a usb cable connection and I'm able to install an APK though my ability to go in and access or modify files and folders is limited. Has anyone else had this issue and what were you able to do to overcome the issue?
I just picked one of these up to use as an Android 11 test kit. Unfortunately, the developers who built the Android disabled wireless adb debugging! Luckily, the box is rooted at the factory so I was able to add it in. Connect via USB, su to root, mount / as rw (mount -o rw,remount / ) and add this line to the end of /system/build.prop
Code:
service.adb.tcp.port = 5555
This change to build.prop is persistent after resets so you only have to do it once.
I'm using ad link 4.8, I'm connected to the device via USB to see the device, and have the ADB Shell open. however I must be typing in the commands in wrong. See attachment. Please assist.
Thank you.
ThirdStarr said:
I'm using ad link 4.8, I'm connected to the device via USB to see the device, and have the ADB Shell open. however I must be typing in the commands in wrong. See attachment. Please assist.
Thank you.
Click to expand...
Click to collapse
Looking at your screenshot, it appears that you have successfully gained root access (the # prompt). Your next steps :
mount the / partition as rw:
Code:
mount -o rw,remount /
Add code to the end of /system/build.prop
Code:
echo "service.adb.tcp.port = 5555" >> /system/build.prop
mount the / partition as ro:
Code:
mount -o ro,remount /
This worked for me. YMMV
Thank you for the assist. That allowed me access to the device via up address.
The only issue I have now is that all the Kodi folders and files are hidden when you try to use File Manager in adbLink. This device has been the biggest bear to work with.. Once again thank you for the assistance and patiences
ThirdStarr said:
Thank you for the assist. That allowed me access to the device via up address.
The only issue I have now is that all the Kodi folders and files are hidden when you try to use File Manager in adbLink. This device has been the biggest bear to work with.. Once again thank you for the assistance and patiences
Click to expand...
Click to collapse
In the device record, check the "disable root" checkbox, save the record, then disconnect the device. When you reconnect the file manager should work.
I did as you suggested and rebooted the device.
I was only able to access this far in file manager
ThirdStarr said:
I did as you suggested and rebooted the device.
I was only able to access this far in file manager
Click to expand...
Click to collapse
For Android 11, Google has implemented scoped storage which removes the ability for external applications (or the normal shell) to read/write in /sdcard/Android/data/. You can still access this area via the shell as the root user. File manager won't work as root on this device, sorry.
Ok I understand. Thank you very much
Hello i'm on android 11, how i can use the root access? Doesn't work for me
I no longer have this device. Good luck!
hi i am kumar, regarding my x88 pro 10 android 11 i am facing a issue that i can connect to other hotspot or wifi network. i can't connect to my home wife that at the below of thw wifi name (check password and try again). i change my password in router page and try back with the new password still it shows like that. may i know why?