Database Info

[Root][Guide] Rooting ICS 4.04 leak from the 2.3.6

FILES WERE ATTACHED. I HOPE IT IS VIRUS FREE BUT I CANNOT PROMISE AS THERE MAY BE SOME TROJANS BECAUSE I DOWNLOADED AT SOMEWHERE. You've been warned. That's why I placed the list of files originally.
0. Your system must be in version 2.3.6 or below, which can be rooted by motofail. Do double wipe before you flash.
a) Place the following files in the same folder:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
motofail
su
Superuser.apk (script default) / supersu.apk
b)(optional) Prepare the modified RSDlite which can flash any roms...
c) Prepare the Motorola driver and install it.
d) use notepad to create a script (root.bat)(provided below) and save it in the same folder with the files above.
1. Connect your phone to the computer. You'd better install the drivers for your phone first. Turn on "USB debugging" and connect it as "charging mode".
2. You CANNOT unplug your usb cable and you CANNOT close the rooting program/script in the whole process.
3. Run the root.bat.
4. it will push some files into your phone and reboot your phone.
5. You will see the caution symbol with the Android robot.
6a. Flash your rom by the stock recovery
OR
6b(i). Pull the battery out.
6b(ii). HOLD the volume-down button and put the battery back.(Power ON) It will boot into the AP mode. (If you can see the blank secreen but not showing "USB CONNECTED, FLASH OK" , release the volume button or retry)
6b(iii). run the RSDlite to flash your rom
7. The phone will reboot and update few(1-3) times.
8. The phone will be rooted after the final reboot.
9. Take out your SD card and do factory reset. (The root will be kept) (I found this may solve some problems)
Script is here :
Code:
@echo off
cls
adb kill-server
adb wait-for-device
adb.exe shell mv /data/local/12m /data/local/12m.bak
adb.exe shell ln -s /data /data/local/12m
adb.exe reboot
adb.exe wait-for-device
adb shell rm -r /data/local/tmp
adb shell mkdir /data/local/tmp
adb push motofail /data/local/tmp
adb shell chmod 755 /data/local/tmp/motofail
adb shell /data/local/tmp/motofail exploit
adb reboot
adb wait-for-device
adb remount
adb.exe shell rm /data/local/12m
adb.exe shell mv /data/local/12m.bak /data/local/12m
adb.exe shell mv /data/local.prop /data/local.prop.bak
adb.exe shell "echo 'ro.kernel.qemu=1' >> /data/local.prop"
adb.exe reboot recovery
echo The phone will boot into the recovery mode
echo please follow the tutorial for the rooting process
echo do not close this window
ping -n 8 127.1>nul
adb wait-for-device
adb remount
adb push su /system/bin
adb shell chmod 4755 /system/bin/su
adb push Superuser.apk /system/app
adb shell chmod 666 /system/app/Superuser.apk
adb shell rm -r /data/local/tmp
adb shell mkdir /data/local/tmp
echo Your phone is rooted!!!
PAUSE
The script is provided by the crc3334404 at gfan.com .Some text is modified by me.
The guide is mainly based on his guide too. (with several modification and addon etc)
Tested on ME865

attach the required files
Edit:- thanks will try

may be i am noob but when i run the bat file it say
C:\root>adb wait-for-device
* daemon not running. starting it now *
* daemon started successfully *
Click to expand...
Click to collapse
and stays there waited for 15 min but nothing happend
EDIT:- as i said i am noob, forgot to tick usb debugging

shamsud said:
may be i am noob but when i run the bat file it say
and stays there waited for 15 min but nothing happend
Click to expand...
Click to collapse
probably bad drivers or something

shamsud said:
may be i am noob but when i run the bat file it say
and stays there waited for 15 min but nothing happend
EDIT:- as i said i am noob, forgot to tick usb debugging
Click to expand...
Click to collapse
So sorry that I didn't mention originally.
Actually I can't sure whether it works in MB865. May you please tell us after trial. Thanks

Results?
Sent from my Atrix II using xda premium

lilhaiti said:
Results?
Sent from my Atrix II using xda premium
Click to expand...
Click to collapse
Id really like to know as well! Haha

sorry guys am unable to flash with stock recovery it say "assert failed" i downloaded the file from below thread
http://forum.xda-developers.com/showthread.php?t=1684443
Click to expand...
Click to collapse

shamsud said:
sorry guys am unable to flash with stock recovery it say "assert failed" i downloaded the file from below thread
Click to expand...
Click to collapse
do you have a MEARET phone? are you fully stock?

fully stock but Searet rom, now loading mearet rom...
EDIT:= Finally got the rooted ics the above method works

shamsud said:
fully stock but Searet rom, now loading mearet rom...
EDIT:= Finally got the rooted ics the above method works
Click to expand...
Click to collapse
Could you upload a backup.i need it to work on getting cm9 working with data. I cant just use the ics update because its only patch files.i need the already patched files.pm me the link to the upload if u can upload it as soon as possible. I just need the system.ext3.tar
Sent from my MB865 using xda premium

rdavisct said:
Could you upload a backup.i need it to work on getting cm9 working with data. I cant just use the ics update because its only patch files.i need the already patched files.pm me the link to the upload if u can upload it as soon as possible. I just need the system.ext3.tar
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
He sent me a PM I told him to do a cwm backup and give us the system and also to dump boot with dd in case we need it for anything

I rooted failed....
It stock after RDS 4.0.4....
I plug the usb and all drivers are ok, then press anykey, then.....it stock...
My OS windows 7 64bit...

dickluo said:
I rooted failed....
It stock after RDS 4.0.4....
I plug the usb and all drivers are ok, then press anykey, then.....it stock...
My OS windows 7 64bit...
Click to expand...
Click to collapse
Questions may help:
1. did you flash it back to 2.3.6 First?
2. Did you root the 2.3.6 successfully by the batch?
3. Flashed the 4.0 after root with no Window closed?
4. Always connected with usb?
5. Usb debugging enabled?
6. No superuser.apk? May be you don't need to do factory reset after rooting. Please let us kvow.
If all yes, please tell us your 2.3.6 version too. E. G. 55.109.xxx
Sent from my ME865 ICS4.0 using XDA premium.

Double post, deleted

shamsud said:
fully stock but Searet rom, now loading mearet rom...
EDIT:= Finally got the rooted ics the above method works
Click to expand...
Click to collapse
Which cheesecake rom did you start with?
Sent from my ME865 ICS4.0 using XDA premium.

4.0.4 drains battery very fast
Two observations after testing ICS on MB865
1/ battery drains twice as fast for ICS 4.04 compared to GB 3.6.6
2/ Screen slower response

austin_boy said:
Two observations after testing ICS on MB865
1/ battery drains twice as fast for ICS 4.04 compared to GB 3.6.6
2/ Screen slower response
Click to expand...
Click to collapse
Never tried GB 3.6.6 and am afraid it doesn't exist.
My battery is ok:
{
"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"
}

xanadu said:
Never tried GB 3.6.6 and am afraid it doesn't exist.
My battery is ok:
Click to expand...
Click to collapse
Maybe because you are on T-mobile and don't use 3G

socialx said:
0. Your system must be in version 2.3.6 or below, which can be rooted by motofail. Do double wipe before you flash.
Click to expand...
Click to collapse
Can anybody help me to find 2.3.6 firmware for ME865?

Whats the deal with the "Confidential Motorola Poperty" phones?

Hello, well today i was going through the second hand market on my town for a phone and i saw this mb865, impecable but as is.. with no charger cables or anything whatsoever.. the price was cheap enough so i got it..
After getting to my home i noticed that on the back under the cover and on the display at the right side of the screen it has some engravings saying this phrase.
"Confidential Motorola property not for sale"
so whats the deal with this phone? is it a prototype? or what?
Im from Mexico and the phone has a Iusacell rom.
What do you guys think?

If i were you, i would go to that store again, and return it. Perhaps you'll have some bad experiences with that phone, because maybe it's not the final release and may had some changes than ours phone.

And on the other hand, it may be an engineering device with an unlocked bootloader....

snowplow said:
And on the other hand, it may be an engineering device with an unlocked bootloader....
Click to expand...
Click to collapse
im now officially praying for this.. as of right now.. i have asked for an unlock code from cellunlocker.net..
any of yoou know them? they seem reliable enough...

No idea about sim-unlocking it, I doubt that you will be able to though if it is carrier locked. Have you tried different sim cards in it?

snowplow said:
No idea about sim-unlocking it, I doubt that you will be able to though if it is carrier locked. Have you tried different sim cards in it?
Click to expand...
Click to collapse
Well i have tried my sim ( which is from another carrier) and it asks me for asubsidiary code.. so im hoping ill be able to unlock it the same way i did with my xt610 some time ago..
So far i dont see anything special in this phone, other than those words... mm well see.. tomorrow ill try to flash some roms, recoveries.. etc..
and ill be expecting my unlock code..

Sent from my iPad using Tapatalk

enable usb debugging, open command prompt, go to the folder you have adb in, and type the following post the output.
Code:
adb shell
su
cat proc/omap_dev_type
if you dont have adb, just download android terminal from google play and type in the same except 'adb shell'. of course, your phone has to be rooted.

Ravikirancg said:
enable usb debugging, open command prompt, go to the folder you have adb in, and type the following post the output.
Code:
adb shell
su
cat proc/omap_dev_type
if you dont have adb, just download android terminal from google play and type in the same except 'adb shell'. of course, your phone has to be rooted.
Click to expand...
Click to collapse
What is this Iusacell ROM he mentioned? & I hope anyone can post the root file for Gingerbread & ICS and "eetu' can use it to root as per GB or ICS he would have on his phone & for then executing the above command on android terminal .
Eetu, you need to follow above instructions and advise what output you get on screen. Your phone may be one of a kind most special and our developers need all help to unlock bootloader & they may get in touch with you based on your reply that is sought & until then preferably do not alter stock settings by flashing custom ROM's, Mod's etc. We need all help we can get. Thanks!

RAD7 said:
What is this Iusacell ROM he mentioned? & I hope anyone can post the root file for Gingerbread & ICS and "eetu' can use it to root as per GB or ICS he would have on his phone & for then executing the above command on android terminal .
Click to expand...
Click to collapse
Iusacell is a service provider from México (use mostly CDMA pones), the "oficial Iusacell rom" stayed in GB not ICS (http://sbf.droid-developers.org/edison/list.php)
There is a lot of chance that will be a engineer phone, but will be the same case of the other Atrix 2 with unlocked bootloader.
Saludos

serch_mx said:
Iusacell is a service provider from México (use mostly CDMA pones), the "oficial Iusacell rom" stayed in GB not ICS (http://sbf.droid-developers.org/edison/list.php)
There is a lot of chance that will be a engineer phone, but will be the same case of the other Atrix 2 with unlocked bootloader.
Saludos
Click to expand...
Click to collapse
Noted & I guess eetu must have given reply in PM to developers!

RAD7 said:
Noted & I guess eetu must have given reply in PM to developers!
Click to expand...
Click to collapse
doubtful about that.. dosent look like he returned to this.

Ravikirancg said:
doubtful about that.. dosent look like he returned to this.
Click to expand...
Click to collapse
Gee, sucks, Eeetu, Man do revert.
When Jim said he is looking at stuff from user Amritin's phone, I was thinking prolly something more like Eetu's phone can surely add to the database.

IM HERE
Sorry guys i have had some in house problems.. but im here now..
Well blast i have probably ****ed this up now.. you see i was trying to root the phone in order to see things under the hood, but the usual superonelick, methond didnt work ( i tried other 2 thati cant remember they were mostly sripts with a runme.bat file on them)...
So with no avail.. i decided to flash the rom to a LATAM stock GB rom.. after i did.. i tried superoneclick and voila...
I havent been able to tinker with it past then.. but now im afraid of what i did.. ****..
So tell me do i try to reflash the iusacell rom( it is avaliable).. do i leave it like this.. or what?
on the meantime i have uploaded some pics of the phones messages of confidential property.. for you to see.. and im checking the ADB stuff.. getting the terminal emulator from the playstore as im typing this..
Let me know how to proceed..
{
"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"
}
Sorry for the quality.. i couldnt take better ones at the moment.. and the words on the front (on the side of the screen) are just impossible to take.. but believe me they are there..

well i downloaded the terminal from the store.. and i tried the commands with no avail.. yes i am rooted..
it looks something like this
[email protected]:/$
i type su and it says not found.. same as with the other command.. i know im doing something wrong here.. so please help.. im no linux wiz here..

eetu1923 said:
well i downloaded the terminal from the store.. and i tried the commands with no avail.. yes i am rooted..
it looks something like this
[email protected]:/$
i type su and it says not found.. same as with the other command.. i know im doing something wrong here.. so please help.. im no linux wiz here..
Click to expand...
Click to collapse
Try:
adb shell
Then, su...
Or use a root explorer and check /system/xbin and/or /system/bin for a file called "su"... And let us know..
Edit: Ahh.. You're using an app, not by usb.. Forget the first part of what I said - or try to find the adb files and do what Ravi said a few posts back with a usb from your computer..
Sent from my MB865 using xda app-developers app

alteredlikeness said:
Or use a root explorer and check /system/xbin and/or /system/bin for a file called "su"... And let us know..
or try to find the adb files and do what Ravi said a few posts back with a usb from your computer..
Click to expand...
Click to collapse
Well.. i tried using Root Exploirer and i searched both System/xbin and system/bin directories but there is no SU file in sight...
as for the other way .. where do i look for the ADB files? how do i use USB??

eetu1923 said:
Well.. i tried using Root Exploirer and i searched both System/xbin and system/bin directories but there is no SU file in sight...
as for the other way .. where do i look for the ADB files? how do i use USB??
Click to expand...
Click to collapse
Make sure its rooted properly.. open the superuser or supersu app and make sure the binary is updated..
A little more info and we can help you
What version of android are you on right now?
And what super one click did you use? I don't remember having a super one click for our phone..
Sent from my MB865 running PAC-man using Tapatalk 2

Ravikirancg said:
Make sure its rooted properly.. open the superuser or supersu app and make sure the binary is updated..
A little more info and we can help you
What version of android are you on right now?
And what super one click did you use? I don't remember having a super one click for our phone..
Click to expand...
Click to collapse
mybad it wasnt superoneclick.. damn names are the same.. i use a script called
1-click_exploit.zip
with these files inside.
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
busybox
runme.bat
su
Superuser.apk
zerg
Im on GB 2.3.6 and yes my superuser is updated.

eetu1923 said:
mybad it wasnt superoneclick.. damn names are the same.. i use a script called
1-click_exploit.zip
with these files inside.
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
busybox
runme.bat
su
Superuser.apk
zerg
Im on GB 2.3.6 and yes my superuser is updated.
Click to expand...
Click to collapse
If you have no su binary file in xbin or bin, then it's going to be difficult for things to recognize root.
You opened Superuser and tapped to check for binary updates in settings?
You could also try to install SuperSU instead..
Another thing to try: get busybox installer from Play Store and update busybox.
And about adb debugging - go to settings>developer options (or maybe security on GB?) - and enable USB debugging.
Plug in your phone to your computer by USB. Switch to each USB connection type on your phone (mass storage, mtp, camera..) and wait to let the drivers install if they haven't already.
Open a command prompt on that folder that contains adb.exe - do this by holding shift and right-click on the folder and choose open command prompt from the list (or just open the command prompt and type cd C:\Users\Desktop\1-click_exploit or whatever your path is to adb).
Type adb devices
If you get a serial number and the word "device" as output, then you should be OK to use adb
Sent from my MB865 using xda app-developers app

[Zte][warp7]Permroot[kingroot]

Will type up better guide later on gonna include my ota i pulled as well maybe help someone
btw do at ur own risk im not responsable if u mess the phone up
added batch script hope it works to automate the process and guide u. before u can use this guide or batch script make sure to enable developer settings and adb
you can download it this https://forum.xda-developers.com/attachment.php?attachmentid=4181698&stc=1&d=1497456929 extract it go into the folder find root.bat double click file.
or follow the guide below
1.need to get temp root with king root first grab that here https://kingroot.net/ grab file for android not windows version
grab this file https://forum.xda-developers.com/attachment.php?attachmentid=4180414&stc=1&d=1497364232
2.once extracted go inside folder. hold down shift key and right click inside the folder. click open command window 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"
}
unhide for root guide
3. type this "su"
then continue guide
4. type this "getprop ro.product.name"
should show output "ZTE_BEAM"
5. type this "setprop persist.sys.k ZTE_BEAM"
6. type this "getprop persist.sys.k"
output "ZTE_BEAM"
7. type this "cd /dev/block/platform/soc.0/7824900.sdhci/by-name/"
Lets backup recovery
8. type this "dd if=recovery of=/sdcard/recovery.img"
Lets write boot to recovery!
9. type this "dd if=boot of=recovery"
10. type this inside of adb shell "reboot recovery"
if u get black screen just hold power down to reboot
once booted up
make sure your still inside adb command prompt
11. type this "adb shell"
12. type this "su"
13. type this "id"
should show this output
"uid=0(root) gid=0(root) context=u:r:shell:s0"
then to set permissive
14. type this "setenforce 0"
15. type this "getenforce"
output "Permissive"
16. to test if mount system rw while still root type "mount -o remount,rw /system"
if it mounts no errors then system is writeable
reboot
if for some reason u cant write to system u can try
run this command in adb shell or terminal
reboot disemmcwp
to re-enable write protection issue this command
reboot emmcwpenab
working on replacing king with supersu til then perm root with kingroot
enjoy
and u wanna donate for my hard work click here http://paypal.me/riley60
to restore recovery back to stock u can do once u have perm root do this to restore recovery
type this inside of adb shell dd of=recovery if=/sdcard/recovery.img
hit the thanks button if my post was helpful
original guide here
thanks jcase for his guide for me to base on
https://plus.google.com/+JustinCaseA...ts/KzgyHLgVhwo
also dont forget to hit the thank you button if this post was helpful
ota file attached may help some that are bricked
to remove annoying lock screen with ads
open king root then touch the 3 dots goto settings
then touch accelerate charging turn switch it off
then that annoying part is gone if purify is installed remove it and everything should be good.

Awesome, do you know if this will work on the ZTE Warp Elite?

everyone get their phone rooted ok

Well 2 things...
1: can you lost a guide on how you did those steps?
2: if I already did a software update for my phone, would that affect my chances of getting my phone permanently rooted?

those steps are the guide if you dont know what adb is or how to use it or king root then u could look both those up for guides on the 2. after u know how to use both its pretty much gain temp root have adb open then paste commands make sure they say the same as the guide for outputs follow all steps and should be good. unless they released an update that make it android n im sure it will work. once i send in these 2 dead phones to get repaired ill make a video guide of the steps in guide. as i dont know if it will break root to try redo all the steps to show everything i did.i will see if i can automate the process with batch script. aka filename.bat

updated the guide lil for if anyone who is lil new to adb etc

I've used adb when dealing with moto phones. But this has me confused as to what to actually put in cmd prompt. Either way you're a God among us. I'm going to attempt and see if I can get it working. Thank you for your work sir. Hope to see a batch script some day.

added batch script

No errors so far. Just a little sluggish.

Stevenbew said:
No errors so far. Just a little sluggish.
Click to expand...
Click to collapse
um no errors from what and whats sluggish and for anyone who asks i used the lastest kingroot version

Just errors in general. Nothing is giving me any problems. My phone was a little sluggish after first rebooting. Almost acted like a temp root until I ran the reboot disemmcwp cmd. Then no problems.

Stevenbew said:
Just errors in general. Nothing is giving me any problems. My phone was a little sluggish after first rebooting. Almost acted like a temp root until I ran the reboot disemmcwp cmd. Then no problems.
Click to expand...
Click to collapse
did u use script or manual

madvane20 said:
did u use script or manual
Click to expand...
Click to collapse
I did it manually. Knowing exactly what to type after you edited made everything alot easier to understand.

Stevenbew said:
I did it manually. Knowing exactly what to type after you edited made everything alot easier to understand.
Click to expand...
Click to collapse
ok i only asked cause im already rooted so i couldnt really test the script but it should work and at the end it tells what commands to type in to test. looks like i may need to edit the guide lil bit later and edit my script

I read the guide over and over. While I think I may understand, I'm still afraid to attempt this since it is my only phone and I cannot replace it currently if something were to go wrong. Your typing style makes it somewhat difficult to understand but nonetheless, thank you. I'll attempt when I'm able to replace the phone if something goes wrong.

Heartseed said:
I read the guide over and over. While I think I may understand, I'm still afraid to attempt this since it is my only phone and I cannot replace it currently if something were to go wrong. Your typing style makes it somewhat difficult to understand but nonetheless, thank you. I'll attempt when I'm able to replace the phone if something goes wrong.
Click to expand...
Click to collapse
use to batch script after u get temp root it will do most of the work for you and guide u through the rest

I need help, I can not do temporary root, so neither method allows me to enter the ADB get the SU command, should the phone have any condition before trying to apply them? My phone has software version 0B09 and the options are unlocked OEM and USB debugging, which I am doing wrong, any commentary? thank you!

Pirela said:
I need help, I can not do temporary root, so neither method allows me to enter the ADB get the SU command, should the phone have any condition before trying to apply them? My phone has software version 0B09 and the options are unlocked OEM and USB debugging, which I am doing wrong, any commentary? thank you!
Click to expand...
Click to collapse
grab the newest king root then if it fails keep trying it til it goes through. if it fails uninstall king root reboot reinstall try again. also try adding this commands first if it works without root "reboot disemmcwp" without quotes then try install king root and root see if u get temp root. then if it makes it easier i have a batch script made in the minimal adb and fastboot package

madvane20 said:
grab the newest king root then if it fails keep trying it til it goes through. if it fails uninstall king root reboot reinstall try again. also try adding this commands first if it works without root "reboot disemmcwp" without quotes then try install king root and root see if u get temp root. then if it makes it easier i have a batch script made in the minimal adb and fastboot package
Click to expand...
Click to collapse
Mandvane20 Thanks for your answer and interest
It was not possible to have some temp root, I tried with king root apk and pc, also with kingo root, I went to recovery and deleted the cache, I have force stop the application, I uninstalled and reinstalled, use reboot Disemmcwp, I have made multiple attempts and none has worked, I keep reading, searching and learning, I hope to get some way

Pirela said:
Mandvane20 Thanks for your answer and interest
It was not possible to have some temp root, I tried with king root apk and pc, also with kingo root, I went to recovery and deleted the cache, I have force stop the application, I uninstalled and reinstalled, use reboot Disemmcwp, I have made multiple attempts and none has worked, I keep reading, searching and learning, I hope to get some way
Click to expand...
Click to collapse
connect to pc open adb shell run king root while its trying to root keep typing su in adb shell tell it says root. or til it doesnt give u the error saying no su then proceed with guide see if that works

[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.

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.