Database Info

[DUMP]Transformer Android 2.2 System Dump

[Background]
A few users have gotten Transformers with Android 2.2 installed with diagnostic tools included. So far there have been 3 confirmed users who have gotten these units.
These units are shipped rooted from Asus
Unfortunately, t0dbld has confirmed that the sbk is locked on these devices
[Photos]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[System Dump]
System Archive:
http://db.tt/p3p14Ez
MD5 for Archive:
http://db.tt/DWpL8U7
Or
85c584c6f425fbd6ab111b9f73251fe0
[Reference Thread]
http://forum.xda-developers.com/showthread.php?t=1054120
[Credits]
mmsson - Took time to provide system dump
t0dbld - Helping with users with 2.2 TF and confirming sbk is locked
Welshiren - Currently taking his time to provide more details on his 2.2 TF
*I did not create the system dump or the photographs, and i take no credit for it

Placeholder For Later Or For Important Temporary Information

The MD5 link might be broken.
FYI it should be:
85c584c6f425fbd6ab111b9f73251fe0

Roach2010 said:
The MD5 link points to the system dump.
FYI it should be:
85c584c6f425fbd6ab111b9f73251fe0
Click to expand...
Click to collapse
Yup just realized that lol, corrected the link, thanks

Just some findings i found that i thought where interesting
in \system\lib\hw\wlan\ there are specific broadcom files
bcm4329.ko
fw_bcm4329.bin
fw_bcm4329_apsta.bin
fw_bcm4329_mfg.bin
The Broadcom 4329 supports FM according to specs
http://www.broadcom.com/products/Blu...utions/BCM4329
and look what i found in the app folder
FMTesttool.apk
Interesting...
The FMTesttool.apk wont run for me
I dont know if it is a honeycomb issue or a issue with it being disable in the Broadcom bin files
One user told me when he ran it it displayed radio frequencies but everything was in Chinese, and there was no audio output or any type of RF noise coming from the TF

Do any of these users have root access, a system dump is nice but we could use alot more than that.. we need to see if there partitions are hidden etc we need to see if they have an available partition map or at least a blkid command, next we should dd these partitions etc, the best we could gain from this is to see if the partitions still match up the same as in hc builds and than know where to look to unlock our devices

t0dbld said:
Do any of these users have root access, a system dump is nice but we could use alot more than that.. we need to see if there partitions are hidden etc we need to see if they have an available partition map or at least a blkid command, next we should dd these partitions etc, the best we could gain from this is to see if the partitions still match up the same as in hc builds and than know where to look to unlock our devices
Click to expand...
Click to collapse
I am unsure since the 3 known users who have gotten these units seem to be regular end users, the dump that was acquired was done through a walkthrough by another member on xda from what i was told
If you want to contact welshiron and walk him through the steps in doing a dd image of the partitions and go over any other things you want to know about the device
(dont know if he is familiar with linux, maybe have him do it through a live CD if he is up to it, or maybe use Cygwin to run DD if it even supports it)
Im still an Android noob so i cant really help him too much
If he is the trusting type he might let someone remote in via teamviewer, logmein, etc. lol
Anyways, my theory is these are shipping mistakes because of the limited supply, and once supply increases we may never see any of these test units again

You Dont need linux for a DD, we need root and that is all, also if they are on 2.2 and linux kernel .32 than super one click should work for a quick root and unroot when done. after than we need to get them to open an adb shell,
C:\ adb shell
$ su
# blkid
this will get us some output that we can go on from there also there maybe be a partition map on the tab... i wont get mine till tuesday so i can only guess on where it is . either way we would want to start dd the partitions he has or tha came up for example from the same adb shell with su
C:\ adb shell
$ su
# dd if=/dev/block/mmcblk0p1 of=/sdcard/mmcblk0p1.img

t0dbld said:
You Dont need linux for a DD, we need root and that is all, also if they are on 2.2 and linux kernel .32 than super one click should work for a quick root and unroot when done. after than we need to get them to open an adb shell,
C:\ adb shell
$ su
# blkid
this will get us some output that we can go on from there also there maybe be a partition map on the tab... i wont get mine till tuesday so i can only guess on where it is . either way we would want to start dd the partitions he has or tha came up for example from the same adb shell with su
C:\ adb shell
$ su
# dd if=/dev/block/mmcblk0p1 of=/sdcard/mmcblk0p1.img
Click to expand...
Click to collapse
Didnt know dd was built into android shell, thats cool
Can you contact him and walk him through it, i contacted asking him if he ever used ADB before, haven't gotten a response yet

SlimDan22 said:
Just some findings i found that i thought where interesting
in \system\lib\hw\wlan\ there are specific broadcom files
bcm4329.ko
fw_bcm4329.bin
fw_bcm4329_apsta.bin
fw_bcm4329_mfg.bin
The Broadcom 4329 supports FM according to specs
http://www.broadcom.com/products/Blu...utions/BCM4329
and look what i found in the app folder
FMTesttool.apk
Interesting...
The FMTesttool.apk wont run for me
I dont know if it is a honeycomb issue or a issue with it being disable in the Broadcom bin files
One user told me when he ran it it displayed radio frequencies but everything was in Chinese, and there was no audio output or any type of RF noise coming from the TF
Click to expand...
Click to collapse
new roms have the same bcm4329 files, look in /system/vendor in any rom (prime for example).
and lol i'm stupid, dd is the obvious answer for the boot.img.
We could theoretically make a cool testing rom with that.

also, if a wipe/factory reset got rid of testing apps, that means they were in /data, so we need a dump of that too, almost for sure. you see, i've never had a factory reset that so much as TOUCHED system partition, so if the apps disappeared after a reset, they were in data, not /system.

Hi!
Sorry if it has been posted already .
There is another guy who has received a 2.2 TF, and he cannot post in this thread.
I beg any master please go to this link (look in the pages 19 and 20) and help this man before he returns his TF tomorrow. Maybe there is still time to get something useful.
http://forum.xda-developers.com/showthread.php?t=1054120&page=20
Regards.

CalvinH said:
Hi!
Sorry if it has been posted already .
There is another guy who has received a 2.2 TF, and he cannot post in this thread.
I beg any master please go to this link (look in the pages 19 and 20) and help this man before he returns his TF tomorrow. Maybe there is still time to get something useful.
http://forum.xda-developers.com/showthread.php?t=1054120&page=20
Regards.
Click to expand...
Click to collapse
Are you talking about mmsson, if so he already returned it, he is the one who provided the partial system dump
But if you are talking about welshiron then i am in contact with him, it seems that no one has contacted him yet which is disappointing, i am trying my best to help him but i am not as experienced as other users in the community
Im working on showing how how to check for root

Yes I was talking about welshiron.
Thank you for your efforts. I would like to be able to do something by myself, but can't do much (well, apart from annoy you really expert guys by posting here and there).
Good luck.
Regards.

what exactly are the advantages of a 2.2 dump? will you be able to make older apps work?

I wonder if they have a different bootloader.. Is the partition layout the same? Thats a different tegrastats than my gtab.. Has anyone confirmed that this rom is not already rooted.. certainly seems like it would be. I really hope I get one of these treats.

Update:
The dev units do have root access!, welshiron has confirmed it and was able to run the su command to enable root privileges via adb
i need help from other experienced members here, i am going to have him run the blkid command, but after that i am unable to reliably walk him through and dumps through dd, due to lack of experience

I seem to have permission to post here now, how do I run the blkid command and what will that tell us?
Just a reminder, Android and Linux are alien to me so I will need help with the syntax

welshiron said:
I seem to have permission to post here now, how do I run the blkid command and what will that tell us?
Just a reminder, Android and Linux are alien to me so I will need help with the syntax
Click to expand...
Click to collapse
Im not sure either, i cant run it on my rooted phone with cyanogen
Im really surprised there is not a lot of activity or help, maybe its a slow day lol

I'm no expert but on my Desire I do this...
Download Mini ADB.
Have mine if ya need Link!
Run the Runme.Bat file
In the pop-up box type: adb shell
when it gets a console type: blkid
EDIT: Just in case it wasn't obvious, connect your Transformer to PC with USB and enable USB Debugging.
EDIT2: I think it's possible you will need to push Busybox to your device.

[GUIDE] How to ROOT your “Bird v1277” MTK 6577 Dual SIM mobile phone

Found this on the Internet not my work, I now have a ROOTED fully working mobile running Ice Cream Sandwich, all credit goes to "TPSparky" for the development of the software.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
First of all, go to the settings - Developer options and check "USB debugging"
Your phone NEEDS to be recognized as an "ADB Device" in "Device Manager" on your pc, or else this won't work!
Download this file:
https://rapidshare.com/files/1767087805/4.0root.rar
Unpack the RAR.
Double click the TPSparkyRoot.bat
TAKE YOUR TIME!!! Your phone will re-boot several times, be patient!!! The procedure should look something like this:
Once it's successful, your phone should now have a "Superuser" app installed and it should be rooted
YOU ARE DOING THIS AT YOUR OWN RISK!!!!

Will that not stop the Dual Sim Function on hte mobile phone I presume we are on about the same product.
Is this the same product as yours.
http://www.freeyourmobile.com/produ...SIM-Phone-with-4.3inch-touch-screen-M306.html

Can you upload pics somewhere else? Imageshack links are dead.

freeyourmobile said:
Will that not stop the Dual Sim Function on hte mobile phone I presume we are on about the same product.
Is this the same product as yours.
http://www.freeyourmobile.com/produ...SIM-Phone-with-4.3inch-touch-screen-M306.html
Click to expand...
Click to collapse
IcedFlame said:
Can you upload pics somewhere else? Imageshack links are dead.
Click to expand...
Click to collapse
Hi freeyourmobile, Yes it looks the same as my BIRD V1277 mobile.
Hi IcedFlame, no problem, but can you tell me where I should re-upload the pictures to?
RESPECT...

freeyourmobile said:
Will that not stop the Dual Sim Function on hte mobile phone I presume we are on about the same product.
Is this the same product as yours.
http://www.freeyourmobile.com/produ...SIM-Phone-with-4.3inch-touch-screen-M306.html
Click to expand...
Click to collapse
Hi freeyourmobile, dual sims work just fine.

chunky2 said:
Hi IcedFlame, no problem, but can you tell me where I should re-upload the pictures to?
RESPECT...
Click to expand...
Click to collapse
imgur (.com)
tinypic (.com),
photobucket (.com)
postimage (.org)
Thanks :good:

Hi All, Re-uploaded images, this time from photobucket.
RESPECT....

Hello chunky2,
I've searched everywhere on the internet, but I did'nt find an answer.
Does this Phone have a built in compass?

weissgold said:
Hello chunky2,
I've searched everywhere on the internet, but I did'nt find an answer.
Does this Phone have a built in compass?
Click to expand...
Click to collapse
Hi, Not sure at the moment as I did a factory reset to clear out some old data and now its lock in recovery mode and I dont know how to get out of it.

Oh - I feel sorry for that.

Thanks Enelna from Hungary

V12 / v1277
I Think we should call this type of phone by its model which is V1277 and V12 respectively.
V12 looks perfectly the same as V1277 but it has MT6575 cpu which on the otherhand;
V1277 has MT6575 version 2 which they code named MT6577.
I think if we all agree with this we could identify/classify right away which phone was it whether its brand is either star, ulefone, bird or what not. Right?
By the way, Is anyone here got to try flashing a custom rom for this kind of phone like the MIUI? :fingers-crossed:

Rooting failed
I desperately need your help because i know that you are my life saver.
Model number: I9100
CPU: MTK6573
Android version: 4.0.9
Baseband version: I9100XXK13
Kernel version: 2.6.35.7-I9100
Build number: GT_I9100_01
Custom build version: 1341280728
After the first rebooting the output text is : cannot create /data/local.prop: permission denied.
I have tried it 3 times but with the same problems. Is your rooting program dedicated only for MTK 6577 because mine is MTK 6573. Do you have some clues on how to fix this. Thanks for your time in helping me out. :fingers-crossed:

possible solution
shaamt said:
I desperately need your help because i know that you are my life saver.
Model number: I9100
CPU: MTK6573
Android version: 4.0.9
Baseband version: I9100XXK13
Kernel version: 2.6.35.7-I9100
Build number: GT_I9100_01
Custom build version: 1341280728
After the first rebooting the output text is : cannot create /data/local.prop: permission denied.
I have tried it 3 times but with the same problems. Is your rooting program dedicated only for MTK 6577 because mine is MTK 6573. Do you have some clues on how to fix this. Thanks for your time in helping me out. :fingers-crossed:
Click to expand...
Click to collapse
I had a similar problem when trying to root my bird v1277 with Android 4.0.4
I ended up having to do the first steps of the script manually combining the phone's engineer menu and the adb shell.
The objective is to put the local.prop file, with ro.kernel.qemu=1 in it, in the /data directory so that the phone will run in emulater mode and give adb a root shell.
For this I created the local.prop file on my computer and pushed it to /data/local/tmp. Then I entered the engineer mode on my phone and searched around and found a place where you can type shell comands as the system user and copied the local.prop file to /data with busybox.
Hope this helps you
Instructions:
[email protected]$ adb push local.prop /data/local/tmp/local.prop
from PC: adb push busybox /data/local/tmp/busybox
from PC: adb shell chmod 0777 /data/local/tmp/busybox
Enter engineer mode by typing on the dialpad *#15963#* (this may vary from phone to phone so search around if this code doesn't work).
Goto CDS Information / Network Utility. Then run: /data/local/tmp/busybox cp /data/local/tmp/ocal.prop /data/local.prop
You can run: ls /data to confirm local.prop is there.
Reboot.
From here on you can either manually do the rest of the script or copy the rest of it to a new script and run it.
EDIT: amended to make it actually work (originally tred to use mv instead co pushing busybox and using cp.
EDIT2: amended adb chmod to adb shell chmod

Engineer Mode Help for MTK Device
For the last few days i've being trying to get the engineer mode code for my phone but failed until i hit "mtk engineer mode" through googling. There is an application called "Mobileuncle MTK Tools" that could excess the engineer mode of my mtk phone.
Mobileuncle MTK Tools is able to list down the menu in engineer mode but there are no CDS Information / Network Utility in the list. The menu listed are as follows:
Battery Log
TouchScreen
GPRS
Audio
Camera
WiFi
Bluetooth
NetworkInfo
AutoAnswer
YGPS
AGPS
EPO
VideoTelephony
Display
Memory
IO
Power
BaseBand
FM Receiver
SIMMeLock
SystemLog
De-Sense
CPU Freq Test
BandMode
I'm hoping that you may have some clues on the next step of solving this problems of mine. Thanks for your time in helping me and i appreciate it very much.

FrankVM said:
I had a similar problem when trying to root my bird v1277 with Android 4.0.4
I ended up having to do the first steps of the script manually combining the phone's engineer menu and the adb shell.
The objective is to put the local.prop file, with ro.kernel.qemu=1 in it, in the /data directory so that the phone will run in emulater mode and give adb a root shell.
For this I created the local.prop file on my computer and pushed it to /data/local/tmp. Then I entered the engineer mode on my phone and searched around and found a place where you can type shell comands as the system user and moved the local.prop file to /data
Hope this helps you
Instructions:
[email protected]$ adb push local.prop /data/local/tmp/local.prop
Enter engineer mode by typing on the dialpad *#15963#* (this may vary from phone to phone so search around if this code doesn't work).
Goto CDS Information / Network Utility. Then run: mv /data/local/tmp/local.prop /data/local.prop
You can run: ls /data to confirm local.prop is there.
Reboot.
From here on you can either manually do the rest of the script or copy the rest of it to a new script and run it.
Click to expand...
Click to collapse
Hello
I do have a V1277 as well, but I'm not that up to date on android manipulations. Thing is, that I went into the engineer mode, got to CDS info/network utility. Ran ls /data and saw the local.prop. (I'm not sure if I did it before the " Then run: mv /data/local/tmp/local.prop /data/local.prop" or not...sorry...I'm noob). And also I ran the
Anyways. Everything still gives me error messages telling me that access is denied. In fact the mv command as well.
I guess I may be missing the first line of your instructions. If you have time can you please explain it a bit more deeply? (I got the TPSparkyRoot thing, with adb.exe in it, tried running the command adb push from total commander and also adb terminal)
Thanks in advance

Hi everyone.
I recently bougth a micro d-hdmi to hdmi for my v1277 so that I could use it to connect to my lcd tv.
I connected it and it works. The only thing that bothers me is that it won't go on full screen on the tv. The picture is always on portrait and centered at the lcd which kind a disgusted me. I cannot find any options on the hdmi menu to turn it to fullscreen or have it default to landscape mode just to use the whole screen real state.
Does anybody knows howntp do it? Is there an app to solve this that is available on google play.
Help.
Sent from my V1277 using xda app-developers app

shaamt said:
For the last few days i've being trying to get the engineer mode code for my phone but failed until i hit "mtk engineer mode" through googling. There is an application called "Mobileuncle MTK Tools" that could excess the engineer mode of my mtk phone.
.
Click to expand...
Click to collapse
Try these ones *#*#3646633#*#* or *#3646633#
You can also check if SystemLog / NetLog has an operational shell command box
---------- Post added at 01:47 AM ---------- Previous post was at 01:27 AM ----------
Nekem8 said:
Hello
I do have a V1277 as well, but I'm not that up to date on android manipulations. Thing is, that I went into the engineer mode, got to CDS info/network utility. Ran ls /data and saw the local.prop. (I'm not sure if I did it before the " Then run: mv /data/local/tmp/local.prop /data/local.prop" or not...sorry...I'm noob). And also I ran the
Anyways. Everything still gives me error messages telling me that access is denied. In fact the mv command as well.
I guess I may be missing the first line of your instructions. If you have time can you please explain it a bit more deeply? (I got the TPSparkyRoot thing, with adb.exe in it, tried running the command adb push from total commander and also adb terminal)
Thanks in advance
Click to expand...
Click to collapse
ok run these commands and tell me what they say and I'll try and figure out what is going on:
id
ls -ld /data
cat /data/local.prop

All,
I have sucessfully rooted my v1277 using the same procedures on how to root lenovo p700.
[Guide] how to root lenovo p700http://forum.xda-developers.com/showthread.php?t=1774567
You can try it also and please READ, understand, follow and execute the procedures carefully then you will succeed.
Sent from my V1277 using xda app-developers app

Engineer Mode Help for MTK Device
FrankVM said:
Try these ones *#*#3646633#*#* or *#3646633#
You can also check if SystemLog / NetLog has an operational shell command box
---------- Post added at 01:47 AM ---------- Previous post was at 01:27 AM ----------
Click to expand...
Click to collapse
I think i've tried all the engineer code listed on forums/web but anyway i tried again the one given by you and the result are still the same.
SystemLog / NetLog has no operational shell command box. But anyway i've installed "Terminal Emulator" from google play.
From the shell command in the device are there any way for me to check any directory that allowed system user running in emulator mode and give adb a root shell.

[Q] How to root xtrons on oreo (android 8.0) device

Hi, is there any solution to root an Xtrons Android 8.0 Device?
Kingoroot plus SuperSu was a perfect solution in past, but did not work longer.
Kingoroot keep crashing on startup on oreo.
Need help

Me too. I need a sollution for rooting. And second... I need to know if I can use others theme. I want a black theme. Not gray.

I don't think its out yet. KingoRoot, Kingroot, and *#hct#root# don't work. I'm gonna try to do KingoRoot or unlock the bootloader with adb from a computer. If that doesn't work, I'll try downgrading the firmware and try all the appropriate root procedures. Outside of all that, I'm at a loss of what else to try. I have an GS MTCD/E.

jdisco1 said:
I don't think its out yet. KingoRoot, Kingroot, and *#hct#root# don't work. I'm gonna try to do KingoRoot or unlock the bootloader with adb from a computer. If that doesn't work, I'll try downgrading the firmware and try all the appropriate root procedures. Outside of all that, I'm at a loss of what else to try. I have an GS MTCD/E.
Click to expand...
Click to collapse
You have succeeded in making root on Oreo?

One is to flash the Magisk patch created by kumarai.
https://forum.xda-developers.com/showpost.php?p=75741195&postcount=519
Some people said this mod worked, but it was unstable and unusable for my GS unit.
Another is to install Malaysk ROM.
https://forum.xda-developers.com/an...-malaysk-roms-px5-2-4-gb-8-0-android-t3762724
This worked for my GS, but the cold startup time doubled, the overheating problem also got worse.
But I want you to remember. Our Chinese android unit was originally backdoor open.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Using the terminal emulator, enter the following command...
PHP:
setprop persist.adb.tcp.port 5555
setprop sys.rkadb.root 1
Once restarted, you can delete, add, or change system files via wi-fi adb.
So I returned to stock ROM, deleted bloatware via adb, modified the build.prop add custom apk and used it.

warata said:
But I want you to remember. Our Chinese android unit was originally backdoor open.
Using the terminal emulator, enter the following command...
PHP:
setprop persist.adb.tcp.port 5555
setprop sys.rkadb.root 1
Once restarted, you can delete, add, or change system files via wi-fi adb.
So I returned to stock ROM, deleted bloatware via adb, modified the build.prop add custom apk and used it.
Click to expand...
Click to collapse
Great news, thanks!
Where can I find a tutorial about that? All the instructions tell them that we need to connect usb to the computer, but our units do not have a usb port.
Thanks!

adioperator said:
Great news, thanks!
Where can I find a tutorial about that? All the instructions tell them that we need to connect usb to the computer, but our units do not have a usb port.
Thanks!
Click to expand...
Click to collapse
No, only Wi-Fi adb can be used. I do not know how to USB debug.
By inputting the command with the terminal emulator and restarting it, you can make adb connection via wi-fi from the PC on the same network.
However, it may need to enable USB debugging for developer options.
If people need an instructions I will make it in a few days.

warata said:
No, only Wi-Fi adb can be used. I do not know how to USB debug.
By inputting the command with the terminal emulator and restarting it, you can make adb connection via wi-fi from the PC on the same network.
However, it may need to enable USB debugging for developer options.
If people need an instructions I will make it in a few days.
Click to expand...
Click to collapse
It would be great if you make an tutorial about how to push an app to system over wifi, without root. I would like to replace canbus.apk from system app.
Thanks!

ADB via Wi-Fi You can edit system files with stock ROM
PHP:
setprop persist.adb.tcp.port 5555
setprop sys.rkadb.root 1
Enter the above command with the terminal emulator. I learned this content at 4pda(Thanks to booroondooks).
But you may not be able to use virtual keyboard(AOSP) to enter the command.If so, please use another keyboard or connect a USB keyboard.
Restart and check the HU's IP address.
(Settings, Networks, Wi-Fi, and tap the connected network)
PHP:
adb kill-server
adb connect ##.##.##.##
Open a command prompt as an administrator on a PC connected to the same network and enter the above command.(##.##.##.## is your HU's IP address)
If you see the message"connected to ##.##.##.##:5555", you are connected successfully.
If not, restart PC and HU and try again.
"ADB ROOT"
This command is necessary to run adb with administrator privileges.
PHP:
adb root
"ADB REMOUNT"
This command is needed first to manipulate system files.
PHP:
adb remount
"PULL"
You can download any files with this command.
PHP:
adb pull
"PUSH"
You can upload any files with this command.
PHP:
adb push
"CD"
Please change the directory before downloading the file. Android files should not be downloaded to the Windows system folder.
PHP:
cd
"ADB SHELL"
You can operate the terminal emulator from the PC.
PHP:
adb shell
"chmod"(emulator command)
This command can change the permissions of the system file.
PHP:
chmod
***Very important***
The system file uploaded from the PC needs to give correct authority.
Most system apks require 644 privileges and will not work if they are missing.
Aiso build.prop needs 644. If you forget this, the system will be a brick.
"rm -rf "(emulator command)
You can delete system files with this command.
However, some system files may not work properly when deleted.
PHP:
rm -rf
I am not an English speaker and I am not familiar with the unix commands. So from an advanced level I may be doing something useless or dangerous.But I tried all the contents introduced here with my own HU.I attached an example of command use as an image, so I want you to compensate for the missing explanation. Good luck!

Thanks it work, i use my Archlinux Laptop to use adb wifi (android-tools), and I could change my boot logo (alfa 1024x600 for me) :
https://forum.xda-developers.com/an...evelopment/mod-boot-animation-toyota-t3351617

mum1989 said:
Thanks it work, i use my Archlinux Laptop to use adb wifi (android-tools), and I could change my boot logo (alfa 1024x600 for me) :
https://forum.xda-developers.com/an...evelopment/mod-boot-animation-toyota-t3351617
Click to expand...
Click to collapse
Did you try adding a custom boot logo in factory settings?

You Can only choose a static picture,
I want boot animation.

mum1989 said:
You Can only choose a static picture,
I want boot animation.
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=com.jrummy.apps.boot.animations&hl=en
Try this. You can add a few custom animations with this. It works, and it works with Oreo, but it might not work with your radio. YMMV.

I would say I can't change to an boot animation in the setting
so manualy I add news boot_animation_droid file. (with root)

mum1989 said:
I would say I can't change to an boot animation in the setting
so manually I add news boot_animation_droid file. (with root)
Click to expand...
Click to collapse
Mostly that is correct, there is a an option in the "factory settings" menu of the radio to change the boot animation to be one of any number of car manufacturer logos, or a static picture, as you said, but perhaps not a custom animation like you suggest.
Custom boot logos are touchy things, they have to be the proper size, proper resolution and cannot take up too much space. They have to be written to the system in the proper fashion, and if you overwrite into another part of the system you brick your unit and must recover.
You've heard of Project Treble, right?
https://www.xda-developers.com/project-treble-custom-rom-development/
https://www.xda-developers.com/how-project-treble-revolutionizes-custom-roms-android-oreo/
TWRP-type recovery with Project Treble currently allow you to flash a custom boot animation. Sadly, we don't have TWRP or Treble for these px5 units. Some people have gotten close, but no cigar, as we say.
Even with TWRP, I've heard of people bricking their phones after a custom bootanimation.zip flash, then they have to recover and re-flash the ROM. I had to restore one of these units after a failed root flashing attempt in Oreo and it took hours (sitting in a hot car, on a hot 38°C day) unit we were fully restored and back to where I wanted the OS to be. It can be done but if you screw up, or the animation isn't exactly perfect, you're in trouble.
So the short answer is, use the boot animations from that app or a similar app and be satisfied with that.
---------- Post added at 12:35 PM ---------- Previous post was at 12:26 PM ----------
warata said:
...
"chmod"(emulator command)
This command can change the permissions of the system file.
PHP:
chmod
***Very important***
The system file uploaded from the PC needs to give correct authority.
Most system apks require 644 privileges and will not work if they are missing.
Aiso build.prop needs 644. If you forget this, the system will be a brick.
"rm -rf "(emulator command)
You can delete system files with this command.
However, some system files may not work properly when deleted.
PHP:
rm -rf
Click to expand...
Click to collapse
This is excellent, thank you for sharing.
As a general note, if you are rooted, you can use Titanium Backup app to rapidly freeze or uninstall unneeded system apps, like the Easter Egg, printing services, gMail, etc. It can be done with the terminal but you can do it much faster with Titanium.

I've tried installing the LineageOS terminal, from https://www.apkmirror.com/?post_type=app_release&searchtype=apk&s=terminal but although it claims to have installed, its not not appearing as an icon on any of the screens, and when I tried to launch it from the APK launcher App (that comes built into the Xtrons Oreo unit), it doesnt seem to start
Any ideas ???

Ignore my last post.
I found an terminal emulator that worked.

Finally got this working with my Xtrons unit
ro.build.id=OPR5.170623.007
ro.build.display.id=px5-userdebug 8.0.0 OPR5.170623.007 eng.hct.20180504.142413 test-keys
ro.build.version.incremental=eng.hct.20180504.142413
ro.build.version.sdk=26
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=8.0.0
ro.build.version.security_patch=2017-10-05
ro.build.version.base_os=
ro.build.date=Fri May 4 14:24:13 CST 2018
ro.build.date.utc=1525415053
I initially miss-typed the setprop persis command, but now I got that right, I've been able to pull virtually everything off the unit, (albeit surprisingly slowly, considering the HU is sitting right next to my WiFi router)
Edit.
BTW. Is there any way to push SuperSU etc onto the device to root it using this method ?

I don't seem to be allowed to post a link to it but, here is the path to the topic about rooting the xtrons unit
android-auto/mtcd-discussion-questions-development/how-to-root-ctrons-oreo-android-8-0-t3747975
Note the processed described in the post isn't actually how to root the device, but how to use ADB to make changes when its given root privilages
There is also a replacement ROM, which is pre-rooted, but the installation process carries risks, and I've seen some people report they have gone back to the stock ROM because of issues with the replacement ROM

Hello friends, i was just wondering if it would be possible to use adb from a laptop to send just a line of command to the Head unit via a male to male usb cable since my xtrons unit has 3usb out.
I'm really fed up of using here maps, Google maps, YouTube and shuttle+ (my music player) with the notification bar always showing up and the system ui tuner app allows to remove it in a per app basis without root.
Many thanks in advance.

[CLOSED][SCRIPT][LINUX] Mount System as read write (Android 10+)

This Linux-only version is pretty much deprecated at this point. Please use the BRAND NEW UNIVERSAL VERSION instead! Thank you.
Ladies and gentlemen. Let me present to you my very first release here at the XDA forums:
Welcome to:
makeSystemRW v1.04
automated bash script by lebigmac for Android 10 and above​Creation date: February 2021
Updated: March 2021
Requirements:​
LINUX ONLY!
Android 10 or newer
This version only supports devices with super image.
Check if you have super by running ls -Alg /dev/block/by-name
phone must be rooted + bootloader unlocked + 10 GB free space on phone
at least 20 GB free space on computer for dumping data
adb and fastboot commands should be in your $PATH environment variable
I'm not 100% sure if this is a necessary requirement but I also disabled dm-verity and verification on my device just in case by simply booting into TWRP and then executing these 2 commands:
Code:
adb disable-verity
adb shell avbctl disable-verification
Description: A script for all Android power users that wish to make their read-only Android 10+ system read-write-able again to remove bloatware and make more thorough customizations to their device.
In a nutshell this is what the script is doing:
dumps your existing super image to your pc
extracts the embedded read-only partitions (system, vendor, product, etc...)
makes these partitions read-write-able
joins everything back together to new flashable super.img
flashes it to device
User data is not affected.
Usage: Simply call the script from the shell.
Optional arguments (replace x with your custom value) :
in=x : With this flag you can specify an existing super.img and skip the entire dumping of the super image process. Here you can use the super_original.img which you dumped earlier with makesysrw or the official super.img from your downloaded firmware. You probably have to unsparse the official super.img first using the included simg2img tool for superunpack to recognize it properly. If omitted, makesysrw will dump super image from phone to ./super_original.img
out=x : With this argument you can specify the output path. If omitted, default output value is ./super_fixed.img
size=x : With this parameter you can specify the extra free space (in megabytes) that will be added to each partition. If omitted, default extra size is 0 (shrink to minimum)
Examples:
Code:
# Run this command if you're first time user:
# Specify the extra free space in megabytes for each partition:
./makesysrw.sh size=100
# Plug an existing raw super image into the script like this:
./makesysrw.sh in=./super_original_raw.img size=100
# Specify both the input file as well as the output destination:
./makesysrw.sh in=./super_original_raw.img out=./super_fixed.img size=100
# For unsparsing the (sparse) super.img from your phone manufacturer's firmware you can do:
./tools/bin/simg2img ./super_sparse.img ./super_raw.img
NOTE: I did not come up with all this by myself. After searching for a solution for countless days without success, going even as far as learning hex editing - I coincidentally came across a couple of very interesting threads burried deep inside the new forum interface where this technique has been described and discussed by various enthousiasts (links can be found below in the credits section). So I take absolutely no credit for the underlying core mechanisms of the script. I'm only the amateur who put it all together into a compact script so that everybody can enjoy an Android system that's read-write-able again. Just like it used to be in Android 9 or earlier. Before this annoying 'shared_blocks feature' was implemented.
Credits: Big thanks to @munjeni for allowing me to use his amazing superunpack tool instead of the default lpunpack. Source code can be found here.
Also big thanks to @Brepro1 without your awesome tutorial guiding me I couldn't have created this script.
Thanks @AndyYan your interesting thread also helped me a lot for automating the script especially the lpdump part.
More thanks @gabrielfrias for his helpful comment
Thanks @YOisuPU and of course @topjohnwu for discovering the 'shared_blocks feature'
Thanks @bynarie for making available his otatools package! A part of it is now bundled with the archive
Disclaimer: This is open source software and is provided as is without any kind of warranty or support whatsoever. By using and viewing this software you agree to the following terms:
Under no circumstances shall the author be held responsible for any damages or negative consequences that may arrise from the (inappropriate) use of this software.
All responsibility and liability lies with the end-user. You hereby agree not to abuse this software for illegal purposes. Use this software at your own risk!
Please feel free to improve this script as you see fit (as long as you don't add anything malicious)
and make sure to post your feedback, suggestions and improvements in the official thread right here.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Mod Edit: Download link removed
Please click my like button below if you like it! Thanks​

It would be very helpful if you guys could please give me some feedback if the script works for you.
Which device are you using?
Your Android version?
Did you disable dm-verity and verification before running the script?
Your suggestions to enhance the script. Remember this is only version 1.0
Thanks!
@thor_1979

Great work! Your donation to the developers community is awesome.
The script works perfectly.
Consider keeping going.

Are you serious it actually works on your device? lmao
Congratulations. You are the first person to try it
The script pretty much does the same thing as your awesome tutorial describes.
Without your tutorial this script would not exist so thank you very much for making it available!

How do I use it? I'm really wanting to make my system rw again and this is perfect but how do I use it? It's a tar and Xz?

Simply extract the downloaded archive and open a terminal shell in the extracted folder by right clicking inside it and select Open in Terminal
Then run this command if you're running it for the first time
Code:
./makesysrw.sh size=100
or this command if you already have your raw super.img file
Code:
./makesysrw.sh in=./existing_super_image.img size=100
If you can't launch the script file make sure it is executable on your computer.

I really don't understand how this works why do you need the storage space is it making a system img that you than flash? I thought it just makes the current system read writable so you can install and uninstall system apps.

lebigmac said:
Simply extract the downloaded archive and open a terminal shell in the extracted folder by right clicking inside it and select Open in Terminal
Then run this command if you're running it for the first time
Code:
./makesysrw.sh
or this command if you already have your super.img file
Code:
./makesysrw.sh existing_super_image.img
If you can't launch the script file make sure it is executable on your computer.
Click to expand...
Click to collapse
Thanks I'm supposed to run the shell from my pc terminal or on the android device?

Sorry I see its for linux users. Ok now im getting it I have ubuntu 14 on my hard drive but I need to reinstall the grub menu because I deleted it or something. I have a s10 lite and tab S6 I would love to make the writable on the system so does this make a backup or dump of your system and than you flash it? Do you guys think thatll work on one ui 2.5 and im on lineage 18.1 on my s10 lite

Well in a nutshell this is what the script is doing:
dumps your existing super image to your pc
extracts the embedded read-only partitions (system, vendor, product, etc...)
makes these partitions read-write-able
joins everything back together to new flashable super.img
flashes it to device
User data is not affected.
The script is telling you exactly what's happening under the hood. You can also check out the source code if you have any doubts.
Yes this version of the script is supposed to be run on a Linux computer.
Please report back if it works for you or not.
Lineage OS? Doesn't that have a read-write-able system by default? In that case the script will likely fail.
Please keep in mind this script has been developed on Android 10 (Xiaomi X3 NFC) with a system that's read-only.

lebigmac said:
Well in a nutshell the script dumps your existing super image to your pc.
And then modifies the files to make everything read write able and then flashes back to the device. User data is not affected.
The script is telling you exactly what's happening under the hood. You can also check out the source code if you have any doubts.
Yes the script is supposed to be run on the computer
Please report back if it works for you or not.
Lineage OS? Doesn't that already come with read-write-able system by default? In that case the script will likely fail.
Please keep in mind this script has been developped on Android 10 MIUI 12 (Xiaomi X3 NFC) with a system that's read-only and embedded in a super image.
Click to expand...
Click to collapse
Honestly Im not a 100 percent sure anymore. I know it's a super img and it's really different in twrp there's a ton of new partitions and you have to wipe it off completely to flash a new system. I really haven't dug to deep into everything because I know that S6 oneui isn't writable and actually upset me because it's not like having full root access anymore.

For Windows users with TWRP.
(This is more like a reference)
From adb shell inside twrp.
X = Partition. To find out what block partition is mounted at, mount it in twrp then run 'df -h'.
e2fsck -f /dev/block/dm-x
resize2fs /dev/block/dm-x 3G
e2fsck -E unshare_blocks /dev/block/dm-x
Now reboot to fastbootd and execute:
fastboot resize-logical-partition <partition_slot> $((3*1024*1024*1024))

Thank you for the script.
When I read that I could use it with the super.img I guessed the usage was like
./makesysrw.sh image.img super_edited.img
I have a linux partition, but on a remote server and I was hoping to use it on the file and get my edited file from the server without putting the phone in the server..
Let me knowif you add something like that(-i and -o flags will be useful)
Best

Lossyx said:
For Windows users with TWRP.
(This is more like a reference)
From adb shell inside twrp.
X = Partition. To find out what block partition is mounted at, mount it in twrp then run 'df -h'.
e2fsck -f /dev/block/dm-x
resize2fs /dev/block/dm-x 3G
e2fsck -E unshare_blocks /dev/block/dm-x
Now reboot to fastbootd and execute:
fastboot resize-logical-partition <partition_slot> $((3*1024*1024*1024))
Click to expand...
Click to collapse
As much as I wish for a solution to be available to our fellow Windows users,
unfortunately your suggestion doesn't work here on my device see screenshot below.

lebigmac said:
As much as I wish for a solution to be available to our fellow Windows users,
unfortunately your suggestion doesn't work here on my device see screenshow below.
View attachment 5236719
Click to expand...
Click to collapse
Yeah. These dynamic partitions are weird, because for some reason I only managed to do this on slot A. And only did it on the vendor partition.
Also, this is the reference i was going by;
https://twitter.com/i/web/status/1260577424418488324

lebigmac said:
As much as I wish for a solution to be available to our fellow Windows users,
unfortunately your suggestion doesn't work here on my device see screenshow below.
View attachment 5236719
Click to expand...
Click to collapse
I think the problem is that you are requesting too large amount of memory try to replace 3G with smaller amount of memory

If anybody is good with creating flashable zips contact me! Need help working on universal version right now which will also be compatible with Windows and Mac users!
I am only amateur so need a real pro to give me some assistance here. Thank you.

Redmi note 9 pro. EU 12.0.2 rom. Android 10. It works. I installed WMware Workstation on a virtual machine in Windows. Thanks.(Google translate, sorry)

I can confirm that it works pềctly on my Pixel 4 XL Android 11 (coral-rq2a.210305.006) and Android 10 (coral-qq3a.200805.001), thank you for your awesome hard work!

Tried it on my Oneplus 7T Pro with Android 10. It extracted the superimage but failed at writing it back. It returned this error:
Code:
error: file_write: write: No space left on device
lpmake E 03-02 21:41:55 76867 76867 images.cpp:468] [liblp]sparse_file_write failed with code: -1
lpmake E 03-02 21:41:55 76867 76867 images.cpp:326] [liblp]Could not open image for partition: product_a
makesysrw: Error! failed to create super_fixed.img file./makesysrw.sh super_image.img 14.21s user 37.28s system 51% cpu 1:40.46 total
Any ideas? Thank you for your great work!

I need help rooting my zte quest 5

Ok so i got a zte quest 5 (z3351s) though qlink. Not the phone i wanted but it was one i could afford. And it works very well just can't run amazon music and other apps at the same time.
But the bloatware is unreal. Used to in my galaxy s3&s4 days i could root and delete all apps i didn't need. I know i can disable them but i want them gone completely.
Majisk didnt work
Kingoroot same even used pc.
I am hoping someone knows of a way i can root this phone or at least delete all the un needed apps for example i have Google maps go (came stock) i put the org google maps which is better plus offers sat view.
Edit i did some math and converting and the useless apps 11 out of 58 come out to 349.72mb which is a lot if your phone only has 16gb of space. Also note i don't have hardly anything.
Worst case i can Hotspot to my note10+ for multitasking but not sure of data limit.

@TexasPride
a phone's Android can get considered "rooted" as soon as in Android the SU-binary is present. Hence you at any time at your own can install the appropriate SU-binary onto your phone's Android by means of ADB.

I heard about adb methods but i haven't messed with it in forever since apk/ios apps came out

jwoegerbauer said:
@TexasPride
a phone's Android can get considered "rooted" as soon as in Android the SU-binary is present. Hence you at any time at your own can install the appropriate SU-binary onto your phone's Android by means of ADB.
Click to expand...
Click to collapse
Are you sure it will always work?
I tried this method of installing supersu: https://github.com/spff/install-supersu-via-adb
As a result, I got my phone eternally showing the boot logo and not booting.
Not a problem to re-flash stock ROM but it is an example that there in no universal way to install SU (or SuperSU) via adb.
If you could give a link to some other method how SU could be installed, I'll give it a try of course.

vp1117 said:
Are you sure it will always work?
I tried this method of installing supersu: https://github.com/spff/install-supersu-via-adb
As a result, I got my phone eternally showing the boot logo and not booting.
Not a problem to re-flash stock ROM but it is an example that there in no universal way to install SU (or SuperSU) via adb.
If you could give a link to some other method how SU could be installed, I'll give it a try of course.
Click to expand...
Click to collapse
I spoke of SU-binary and NOT of SuperSU installer package
Example:
Code:
adb devices
adb push <location-of-matching-su-binary-on-computer> /sdcard/Downloads/ 2>nul
adb shell "chmod 0777 /sdcard/Downloads/su"
Of course you can install SuperSU package by means of ADB and this even when device is booted into Stock Recovery: but this requires to make some mods to SuperSU zip.

TexasPride, sorry I stepped in your thread.​
jwoegerbauer said:
I spoke of SU-binary and NOT of SuperSU installer package
Click to expand...
Click to collapse
I see. It is often mixed in numerous materials one can find in the net. Subject is SU-binary update, but the ultimate goal is to install supersu.
jwoegerbauer said:
Example:
Code:
adb devices
adb push <location-of-matching-su-binary-on-computer> /sdcard/Downloads/ 2>nul
adb shell "chmod 0777 /sdcard/Downloads/su"
Click to expand...
Click to collapse
What should be result of running this code? SU-binary located in Downloads with 777 permission? What is the practical sense/use of it?
What software/application would use SU in that location?
Sorry for my questions. I'm not arguing. I try to understand the idea.
jwoegerbauer said:
Of course you can install SuperSU package by means of ADB and this even when device is booted into Stock Recovery: but this requires to make some mods to SuperSU zip.
Click to expand...
Click to collapse
Somehow, with my almost zero knowledge of edify and linux command line I got the same conclusion: SuperSU zip has to be modified in order to install it via adb on devices that do not have TWRP for sideload. I failed to find any examples of SuperSU modding...

@vp1117
Answering your questions from last to first:
Installing SuperSU.zip via ADB
The SuperSU.zip doesn't come with an EDIFY coded script, but with an Android SHELL script - everyone who has knowledge of LINUX scripting can read / modify it.
Android comes with TAR-binary, but not ZIP-binary. Hence the SuperSu.zip must get repacked into SuperSU.tar thus it can get extracted on Phone. The contents of such a TAR-file would look as shown here
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Making use of SU-binary
The SU-binary ( ~110KB ) is nothing else then the root user, as known from LINUX.
Running in Android via ADB a command that requires super-user ( root ) rights is done as follows
Example:
Code:
adb devices
adb shell "/sdard/Downloads/su -c '<ommand-that-requires-root-here>'"

jwoegerbauer said:
Answering your questions from last to first:
Installing SuperSU.zip via ADB
The SuperSU.zip doesn't come with an EDIFY coded script, but with an Android SHELL script - everyone who has knowledge of LINUX scripting can read / modify it.
Android comes with TAR-binary, but not ZIP-binary. Hence the SuperSu.zip must get repacked into SuperSU.tar thus it can get extracted on Phone. The contents of such a TAR-file would look as shown here
Click to expand...
Click to collapse
OK. I guess, I can repack zip to tar.
Sorry for my silly question but why should I need to keep superSU as an archive? Could not I just upload all folders + update-binary.sh to the phone? I'm sure I can do it.
Am I right my next step would be running update-binary.sh (~60 KB) from <adb shell> command line?
jwoegerbauer said:
Making use of SU-binary
The SU-binary ( ~110KB ) is nothing else then the root user, as known from LINUX.
Running in Android via ADB a command that requires super-user ( root ) rights is done as follows
Example:
Code:
adb devices
adb shell "/sdard/Downloads/su -c '<ommand-that-requires-root-here>'"
Click to expand...
Click to collapse
Interestingly, I can execute all commands I need without having su-binary (~100 KB) uploaded to my phone. It is strange but I see #-prompt after I ran <adb shell>. This happens on my UNrooted phone, running stock ROM. I guess, it's a specifics of my phone, no need to try explain it.

I done failed trying to read i dont really understand linux all that well. But if anyone has any links so i can download it and try it

vp1117 said:
Sorry for my silly question but why should I need to keep superSU as an archive? Could not I just upload all folders + update-binary.sh to the phone? I'm sure I can do it.
Am I right my next step would be running update-binary.sh (~60 KB) from <adb shell> command line?
Click to expand...
Click to collapse
Of course it's your decision how you transfer the SuperSU package onto phone: many ways lead to Rome.
My decision was to push SuperSU package repacked as TAR-file onto phone, extract it there, and finally run the modified update-binary.sh when phone is booted into recovery mode:
Code:
adb shell "$(cat < %supersu_dir%/update-binary.sh); echo $?"

So I rebooted to stock recovery and then uploaded following from UPDATE-SuperSU-v2.82-20170528234214.zip package to my phone's folder /tmp:
/arm64
/common
/META-INF
update-binary.sh
Here is what I got:
Z:\android\adb>adb shell "$(cat < /tmp/update-binary.sh); echo $?"
127
/system/bin/sh: #!/sbin/sh: not found
And here's what I got running same command from # command line:
# $(cat < /tmp/update-binary.sh); echo $?
/system/bin/sh: #!/sbin/sh: not found
127
In response to # ls -al /sbin I get lots of lines one of them is as follows:
lrwxrwxrwx 1 root root 7 1970-01-01 00:00 sh -> busybox
I feel that I'm doing something wrong, but what exactly?
In attached txt-file I put some more details I got in command line.

jwoegerbauer said:
... and finally run the modified update-binary.sh when phone is booted into recovery mode:
Click to expand...
Click to collapse
Am I right the only modification needed is to rename update-binary to update-binary.sh ?

@vp1117
NO.
When I said modified then I didn't mean simply rename it: The contents of original update-binary file must be rewritten / deleted in some parts. Also, believe me, it makes sense to repack original SuperSU.zip to SuperSu.tar as I demonstrated above. Take also note that, if device's Android isn't rooted yet, the location for unpacked SuperSU mandatory must be /data/local/tmp.
BTW:
I can see BusyBox is installed on your device's Android. Take note that BusyBox by default comes with the SU-binary. Hence your device's Android is rooted! Wondering why you waste your time with trying to completely install SuperSU from scratch?

jwoegerbauer said:
Wondering why you waste your time with trying to completely install SuperSU from scratch?
Click to expand...
Click to collapse
Good question.
Probably, because I see this when phone restarts from recovery to normal android:

jwoegerbauer said:
Also, believe me, it makes sense to repack original SuperSU.zip to SuperSu.tar as I demonstrated above.
Click to expand...
Click to collapse
OK, no problem, I can re-pack zip into tar.
However, what you demonstrated above was a screenshot showing update-binary.sh being inside the tar. At the same time you don't tell how update-binary.sh must be amended. Is it OK?

TexasPride​
I'm very sorry I put so much spam in your thread. Please forgive me. If I knew how to delete my posts here I would deleted them.

vp1117 said:
TexasPride​
I'm very sorry I put so much spam in your thread. Please forgive me. If I knew how to delete my posts here I would deleted them.
Click to expand...
Click to collapse
Its ok, i dont mind at all.

@TexasPride
FYI: I no longer participate this hijacked thread.