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
Related
This all started out as an experiment to get my nandroid system.img file running in the adb emulator. Well sadly I haven't been able to do that (yet) but I have found something useful. I've Seen several people all over asking how to get a working marketplace app in 2.2 on the adb emulator. After a lot of researching (and trial and error) I've managed to get one. Here are the steps I've taken. (Steps 5 and 6 optional, you can just use the included build.prop if you prefer)
1) Create an avd running 2.2 (froyo,plenty of places explain how to do this so I won't)
2) Download the file (attached below, root files included)
3) Unzip to a location that's easy to remember and find.
4) Load your emulated phone (allow it to load fully)
5) enter this command in a command prompt/terminal window (make sure you "cd" to the directory where you extracted the files)
Code:
adb pull /system/build.prop
6) Remove or comment "ro.config.nocheckin=yes" (no quotes, might be able to just change it to "no" but I haven't tried it that way)
7) enter these commands
Winblows (I mean windows)
Code:
adb remount
adb push build.prop /system/build.prop
adb install GoogleServicesFramework.apk
adb install Vending.apk
adb install Gmail.apk (optional but sometimes signing in here lets the market sign in)
adb shell rm /system/app/SdkSetup.apk
Linux
Code:
adb remount
adb push ./build.prop /system/build.prop
adb install ./GoogleServicesFramework.apk
adb install ./Vending.apk
adb install ./Gmail.apk
adb shell rm /system/app/SdkSetup.apk
8) Sign in. If it works you're done if not reboot and try again, sometimes it takes 3 or 4 reboots to set. If your emulated phone has a data signal from your computer (you'll see a 3G and network icon in the notification area) just wait for it to sign in. The cancel button should grey out within a minute. If it says it can't connect restart the emulator and try again, be patient.
There is a known bug that not all apps show up in the marketplace. I'm not sure why so if someone here knows how to fix that by all means leave a post and let me know. If I see it I'll add it to the first post (provided it works of course )
Edit: Working on getting root on the emulator (just for the hell of it). So far I have su in the xbin directory and superuser.apk installed. Not 100% sure what else I need to do to get the su requests to go through though, I'll probably PM a more experienced member and post back when I have more. Got root? I do (got it working.) Here are the steps you need to take.
Rooting the standard android image on the emulator
1) Open a command prompt (cd to the directoy where you extracted the files)
2) enter these commands
Code:
adb shell mount -o rw,remount -t yaffs2 /dev/block/mtdblock03 /system
adb push su /system/xbin/su
adb shell chmod 06755 /system
adb shell chmod 06755 /system/xbin/su
adb install superuser.apk
That's it! You now have a rooted, market-enabled android emulator.
New! N00b-friendly method
1) create your avd
2) download the emulator files archive attached to this post
3) extract somewhere easy to find
4) open command prompt/terminal and cd to the extracted location
5) start your avd
6) Run your script (windows.bat or linux.sh)
7) sign into market and enjoy root!
Note:
You may have to chmod su again upon restarting the emulator.
To get root back simply run the re-root script for your OS (bat for windows,sh for linux)
To install busybox simply run the re-root script, it will automatically install if you're using the script to install on a new avd.
Post 2
[reserved for updates, explanations, pictures, present/future tweaks in progress, etc]
Pictures:
Superuser list,Marketplace (I like solitaire><), Terminal with su permissions, and re-rooted Terminal
{
"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"
}
Tweaks:
1: root (done!)
2: busybox (done!)
Wow nice....
Thank you the root resets after reboot, working on making it stick but its not hard to do it again, just start with the "-wipe-data" command and redo the root, market works after reboot though. Still working on getting a dumped system.img to boot, ill post that in its own thread when i get it. Glad you like this.
Sent from my ROOTED T-Mobile myTouch 3G Slide using XDA App
Edit: see first post on how to get root back,no data-wipe!
so cool!! Good job man!
Thanks ^_^ let me know if you find any problems that I haven't already mentioned and I'll see if I can fix them or if they're just an emulator quirk.
Sorry for the double post but I wanted to let you all know busybox is now included! Installation can be performed through scripts (included in the "Emulator Files.rar" archive) or manually. If you wish to do it manually simply open the script in a text editor to see what's going on and enter the commands in a command prompt/terminal window.
I'm not able to make this work, not with a toolkit downloaded yesterday anyway.
Pulling of build.prop works, but pushing fails with a directory related error.
"adb shell" followed by "cd /system" and "ls -l" gives a list of files that does not include build.prop, neither as a file nor as a directory.
"ls -l build.prop" works though, and lists a file with 0644 permissions.
Install of all apks different from Gmail fails, with an error that says that those apks are already installed. Uninstalling them through adb doesn't work, netting instead a simple generic error.
Does anyone know whether I'm doing something wrong or Google has modified the emulator images so to render the Market workaround unusable? If so, where could I download an earlier version of the 2.2 system image?
Many thanks
Rocco
I actually had this issue as well. Try re-making the avd, worked for me. You could also try running the scripts to install, might work. If it doesnt post back and ill post the system.img from my sdk.
Sent from my ROOTED T-Mobile myTouch 3G Slide using XDA App
I have the same problem as ropi. Remade the avd several times with different properties, still no go.
I would really appreciate it if someone could upload a fully set-up avd somewhere.
I'll try again late this afternoon (I'm on CEST). Hope it works. If not, I'd be happy too if some kind soul would upload a link to a working avd
Thanks for the kind help
Rocco
I have no idea why people are having so many problems :/. I had the problem and once I remade the avd it went away. Try starting with the -partition-size 96 option and see if that helps. If not here are the files, just extract to your avd directory, it has the ini and img files you need and it's already setup. Just run re-root to get root back and sign into market and you're good to go.
http://hotfile.com/dl/79959332/3efbade/froyo-avd.rar.html
Edit: I just downloaded the latest revision and everything seems to be working fine :/ As I've said before try starting with -partition-size 96 and also try using the scripts I've provided. That should fix the issues, but if it doesn't there's always the hotfile link I've provided (or if you're just lazy lol)
Edit 2: also,just thought of this, make sure before you push the build.prop you adb remount. Pulling will work fine without doing that but pushing won't. No one said if they had done this and still received the errors so I'm trying to cover all bases. If remount fails try the adb shell mount command posted on the first page.
Thanks dbzfanatic, that avd worked great.
Glad it worked for ya. Let us know how everything works.
Sent from my ROOTED T-Mobile myTouch 3G Slide using XDA App
A lot of apps can not be found in the Market ... I cannot find Lookout....
Yeah, I've mentioned that,firs post. It's a known bug. Nothing I can do to fix it at the moment. You could download the apk on your phone then pull it then install it in the emulator. Bit of a roundabout way of doing things but it's all we can do on the emulator for the time being, at least from what I know.
Ok after a bit of poking around (sorry it took so long) I found out a bit about the market. It seems it's not just your region that it uses to show apps but things like your carrier, presence/absence of a SIM card, Android version, etc. It uses the filters to choose which apps to show and which to exclude (not showing an American user Japanese apps, not showing someone on Verizon T-Mobile apps, etc) so this explains part of the problem. I also found out that the SIM card and IMEI numbers were(are?) hard-coded into the emulator binary, changing these may allow us to see a few more apps. I looked through the binary file a bit and didn't find anything but I'll look more closely in a bit (new job, yay <- read as "groan"). I don't know how to emulate or spoof a carrier so that will still cut us back on some of the apps being seen. If anyone knows how to do this please post here and let us know! It would also be beneficial if a user who has already modified their IMEI and SIM numbers in the emulator to compare the apps list to the one you see in the standard, non-modded emulator binary and let us know if there is a difference or not. The more apps we can see in the marketplace the better!
Just wanted to confirm that I've tried Market Enabler a few days ago and it doesn't seem to work.
Alright thanks for the feedback. Ill keep working on it.
Sent from my ROOTED T-Mobile myTouch 3G Slide using XDA App
Despite several tries, I've so far been unsuccessful in using this method to install the marketplace on a 2.2 avd. Many thanks for having provided ready-made avds, then!
I've been able to install marketplace on the Galaxy Tab images provided by Samsung, though!
Keep up the good work
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
Here's how I got my zte maven 2 (ATT) rooted.
Disclaimer: This method worked for me but may not work for others, I am not responsible if your device is bricked as a result of this. Also, this method does seem to be a bit finicky and inconsistent.
I rooted this phone twice, and it took about 15-20 tries each time for it to finally work. This is not a root you can do in 5 minutes (unless you are extremely lucky) Plan to set aside an hour or two, and a lot of patience, if you want this to work.
Credit to @madvane20 his post here helped me get root for this phone. He also got his phone rooted before I did, be sure to give him thanks.
Credit to @ZTE Girl for finding a way to remove ads from King root and keeping perm root.
With KingRoot you can get perm root, but personally I hate KingRoot, so at the end there is a method to replace KingRoot with SuperSu. Unfortunately SuperSu root resets on reboot, but a quick, 10 second adb command will reroot your phone with SuperSu
Edit: @ZTE Girl found that using lucky patcher to remove ads from King root worked for her and kept permroot.
Step 1: Enable USB debugging on your phone, and download adb and ZTE drivers to your PC.
2: Download KingRoot from KingRoot.net (download the apk for android)
3: Connect your phone to ADB, and run this command in terminal adb shell make sure you get no errors and accept any USB debugging requests.
4: Now type reboot disemmcwp This will reboot your phone without write protection.
5: When your phone reboots, run adb shell again, and install the kingroot APK. Google will give you a warning about this app being unsafe, install it anyways.
6: Now, here's the finicky part, sometimes KingRoot works, sometimes it doesn't, you just have to keep trying. Make sure your phone is still connected to the computer through adb shell, and then click try root in KingRoot. While KingRoot is attempting to get root: in adb shell keep typing su and pressing enter. Just spam this, It will keep giving errors, but eventually it (should) work. Make sure to accept any prompts on your device while you do this.
7: When you are able to successfully get into su, wait a bit, just to make sure your device doesn't restart
8: Now type getprop ro.product.name, the response should be Z831
9: Now type setprop persist.sys.k Z831, then type getprop persist.sys.k It should say Z831
10: Now type cd /dev/block/platform/soc.0/7824900.sdhci/by-name/
11: Then type dd if=recovery of=/sdcard/recovery.img This will backup your recovery, I highly recommend that you copy the backup to your computer in case something goes wrong.
12: Now type dd if=boot of=recovery, this will write boot to recovery. This part can be risky, it worked for me, but if it bricks your device, you can't say I didn't warn you with that said, don't let that scare you away from finally rooting this device and getting all the advantages that come with it
13: Now type this reboot recovery Your device my blackscreen and not boot after this, personally mine did, and I fixed it by removing the battery, and after puttting it back in, it booted normally.
14: When your phone boots up, type adb shell again, and then type su
15: Type id response should be "uid=0(root) gid=0(root) context=u:r:shell:s0" Note: I don't think my uid showed when I did this, if yours doesn't show, don't worry, it should work fine.
16: Now type setenforce 0
17: After that, type getenforce, it should respond back with "permissive"
18: To test if system is writable, type mount -o remount,rw /system, if you get no errors, everything is working , if you get an error, type reboot disemmcwp, and then try to mount system RW again.
19: I would recommend removing the update service now, so an update doesn't come and screw up your root.
20: Read this: Now you should have permroot with kingroot, however, as you will soon find, kingroot has a ton of ads, and can get very annoying. So, if you want SuperSu and no kingroot, keep reading. If you want to keep KingRoot, then you are done, have fun with your rooted Maven 2
Edit: @ZTE Girl found that you can use lucky patcher to remove ads from Kingroot while still keeping permroot.
21: Download the KingToSuperSu zip in attachments, I have modified it slightly from the original zip so it works better. You will see a folder inside the zip named "mrw" copy this folder to the root of your /sdcard (must be copied to the root of /sdcard)
22: Now go into adb shell again, and then type su
23: Type mount -o remount,rw /system
24: If you get no errors, simply type sh /sdcard/mrw/root.sh, you will see a lot of errors in the script, no need to worry, now you should have SuperSu. Note: sometimes you get a notification saying "com.eu.chainfireSuperSu has stopped" or something like that, run the command again, and it should work.
25: SuperSu will say binary needs to be updated, but the update always fails, however you can click no thanks, and it will work fine.
26: SuperSu root will go away after you reboot, however, to get root back, simply type adb shell (while connected to your computer of course) then su and then sh /sdcard/mrw/root.sh and just like that, you're rooted again. Note: I couldn't get this to work in a terminal emulator, and it would only work in adb shell for me.
Edit: If you want stock recovery back, run this command in adb shell with su dd of=recovery if=/sdcard/recovery.img. I haven't tested this, and it might unroot/brick your device. This is at your own risk.
This guide was long and complicated, sorry for that, if you need any help, just ask me and I will try to help the best I can.
If this guide helped, please clicks thanks, it means a lot to me
Proof: http://imgur.com/a/zecyU
btw easy way to get rid of ads diasbale the charging thing in king settings and adaway its what i did on the warp 7
carrier iq
this phone has carrier iq, i was able to get temp root without write using kingroot, so i was able to delete, disable apps, and also, remove carrier iq with the quide you can find on the: androidexplained website. i could not actually delete the files in the last two steps but it seemed to work anyway. this is my first post so i can't put links.
Question1: i don't like typing cause i make stupid mistakes, but im assuming i could put all your command in individual batch files ending with a pause on each, and prefixing all you commands with "adb.exe shell su". that way i could stop and see what happened and then continue.
Question2:
dd if=recovery of=/sdcard/recovery.img
seems to mean copy the boot partion to an image file on the internal sd card. am i correct?
and
dd if=boot of=recovery
seems to mean overwrite the boot partition with an image- (file)?
if so what image file?
sorry, im new to all this, i guess i probably don't have enough confidence to do this, my z831 works very well without all the bloat anyway. and yes i understand the risks if i do decide to proceed, anyway. i have 3 $10 and $20 phones that are not bricked but i forgot to reenable the system apps before i removed root and reset, so they might as well be bricked cause they cant do anything after they boot.
btw, you mentioned in one step to wait, to see if it reboots, to see if it is stable before continuing:
for me i remember that either having too many apps running or stopping too many system apps, seemed to make this z831 unstable and reboot, while it had temp root.
Question last: do i need to start the process as you said while kingroot is in the process of rooting, or can i wait till it is finished getting it's root?
duane2064 said:
this phone has carrier iq, i was able to get temp root without write using kingroot, so i was able to delete, disable apps, and also, remove carrier iq with the quide you can find on the: androidexplained website. i could not actually delete the files in the last two steps but it seemed to work anyway. this is my first post so i can't put links.
Question1: i don't like typing cause i make stupid mistakes, but im assuming i could put all your command in individual batch files ending with a pause on each, and prefixing all you commands with "adb.exe shell su". that way i could stop and see what happened and then continue.
Question2:
dd if=recovery of=/sdcard/recovery.img
seems to mean copy the boot partion to an image file on the internal sd card. am i correct?
and
dd if=boot of=recovery
seems to mean overwrite the boot partition with an image- (file)?
if so what image file?
sorry, im new to all this, i guess i probably don't have enough confidence to do this, my z831 works very well without all the bloat anyway. and yes i understand the risks if i do decide to proceed, anyway. i have 3 $10 and $20 phones that are not bricked but i forgot to reenable the system apps before i removed root and reset, so they might as well be bricked cause they cant do anything after they boot.
btw, you mentioned in one step to wait, to see if it reboots, to see if it is stable before continuing:
for me i remember that either having too many apps running or stopping too many system apps, seemed to make this z831 unstable and reboot, while it had temp root.
Question last: do i need to start the process as you said while kingroot is in the process of rooting, or can i wait till it is finished getting it's root?
Click to expand...
Click to collapse
i have a batch script i made for the warp 7 that i think will work for this phone but i never posted any of it cause he released the guide first so i told him to keep it and no the boot to recovery overwrites recovery with boot image from boot then after everything has perm root u can flash the recovery back to recovery. do we need a batch script no do we need to mess with other files risking a brick no kingroot is fine til we can find a way to get access to bootloader for fastboot as well as get a twrp built for the phone. theres ways to make kingroot not as annoying ad blocker disable notifications from kingroot and disable fastcharging lock screen. but u more than welcome to tamper just be aware u brick ur phone in the process theres no fix. as well if it makes it easier for people i will write a batch script that walks them through the process with the pauses shows them what it does so they can learn for future purpose but i m0ean the guides pretty simple
---------- Post added at 01:55 PM ---------- Previous post was at 01:51 PM ----------
wait is this thread maven or maven 2?
step 9 is different than yours, why?
Question for madvane20
XCnathan32's step 9: "Now type
setprop persist.sys.k Z831
BUT in your bat file:
adb.exe shell su
setprop ro.product.name Z831
of course swaping out ZTE_BEAM for Z831
is one better than the other or should they both be done?
yea i think i need to maybe fix the bat but im working on stuff atm got rl stuff im busy with but once im done i will finish a bat for the warp 7 and one for this phone. but yes u swap the name of the phone out for what phone u have.
---------- Post added at 03:26 PM ---------- Previous post was at 03:25 PM ----------
the warp 7 has different name etc so yea the warp 7 post is different im trying to work on everything as well keep working on my huawei ascend xt as well real life stuff
Question for madvane20, im sorry, i meant persist.sys.k OR setprop ro.product.name, this is the discrepancy in the two instructions.
did u read the guide for the zte maven 2 and also look at the guide for the warp 7 u will see the difference it just takes u to read them then u shouldnt have any questions
is this syntax correct, before i try it?
batch.txt:
https://dl.xda-developers.com/4/2/2/0/4/0/3/batchfiles.txt?key=NgPk58hMrJO5QXnvDcnCPw&ts=1500762566
if anyone wants to ask me questions just pm me or get ahole of me on hangouts im listed as dav ril or madvane20
I have used Wugfresh's NRT with my previous Nexus devices with stellar results and I downloaded ADB to try your guys method with a Z831 however, I need ti know if this guide is Android version specific? I recently went from 5.1.1 to 7.1.1 in like 3 OTA AT&T updates, so this device is running Nougat. Also, is PIE something new to 7.0 ? I read somewhere this affects the root process. Why do they have "Unlock bootloader" option in Dev settings ? Can I just run an ADB command to enable Write permission to delete 40-50 #/System/App .apk's?
Yo OP, I genuinely appreciate you sharing this. I found that everything has worked perfectly. I managed to get perm root and I just tried to install SU, gonna see if it worked. Thanks bro
Sent from my N9519 using Tapatalk
So, is it working? please let me know because i also want to root it.
---------- Post added at 04:36 AM ---------- Previous post was at 04:27 AM ----------
How to install adb and Zte drivers on your computer? please reply
379068 said:
So, is it working? please let me know because i also want to root it.
---------- Post added at 04:36 AM ---------- Previous post was at 04:27 AM ----------
How to install adb and Zte drivers on your computer? please reply
Click to expand...
Click to collapse
The ZTE drivers should be on your phone. One of the mount options, when you plug in your phone is to install drivers.
This method really works. You can copy your recovery back after, you do not loose root. You are also able to re-root and make it permanent again after a factory reset, it is just takes many more exploit attempts. You can also install Xposed through Xposed Installer.
Anybody bought and tried Super-Sume Pro with this phone yet?
can thsi be done on other mavens?
Can you do this on a Maven 3 running nougat?
Is the root method working with ZTE Maven 3?
Anyone tried this on ZTE Maven 3? Got 2 from Bestbuy, would like to have them rooted.
Thanks.
Logos Ascetic said:
Can you do this on a Maven 3 running nougat?
Click to expand...
Click to collapse
I recently dissected the partition index and firmware structure of the ZTE Maven 3, in hopes of discovering a viable root exploit. Because it ships with stock Android Nougat, systemless root via patched boot image would be preferable. But, because the bootloader does not appear to be unlockable by any known method or exploit, systemless root is not currently an option. Accordingly, I focused on the less desirable method of system-mode rooting, which injects the SU daemon and corresponding root binaries to the Android OS by way of the /system partition directly. Again, an obstacle ensued: the stock kernel of the ZTE Maven 3 is secured by AVB 2.0/dm-verity (device mapping), which checks the /system partition for any modifications whatsoever prior to allowing the OS to boot. So, if /system is modified in any way, or so much as mounted r/w, a perpetual boot loop will commence via dm-verity.
So, in short, due to the locked bootloader state and verified boot/device mapping, safely & effectively rooting the stock Android Nougat OS of the ZTE Maven 3 doesn't presently appear to be feasible.
Note: I realize that the OP designated this as a ZTE Maven 2 thread, and I apologize to the OP if I'm off topic. I only addressed the Maven 3 because of the number of questions in the thread.
I have the z831 through at&t. I'm pretty sure I unlocked the bootloader in developer options as nothing would root the phone until I turned it on. Everything worked, but is there a custom recovery or rom?
kingroot.net even if you choose english gives you a chinese app
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.
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.