Database Info

Garminfone full hard root Achieved

1: ok step one download universal and root to sd card.
2: then download a file manager such as linda file manager.
3: download chainsdd SuperUser
4: go to settings then applications put a check next to unknown sources.Then go to Development and check usb debugging and stay awake.
5: use linda file manager and browse to sd card and install universal root "DO NOT INSTALL SUPERUSERBUILT INTO IT"
6: Install chainsdd Superuser, After install open it goto settings then scroll too bottom and click su binary it may fail the first time but click it again it will say Su binaries updated.
7: I am using root explorer i bought it from market.
8: after this is installed open it and be sure to click the rw option when you open it at top of directory. Now copy /system/xbin/su to your sd card for safe keeping along with rootshell file from sqlite_stmt_journals folder.
after you back them up too sd then copy Su file too /bin let it over write theres.
Now fire off adb and type adb shell then at the $ type su and walla full root.
Anyone have ideas on how to make it read only so system cant delete those files on reboot or automated way of putting the files in right place at reboot let me know.

Good work on the first steps, next we need to flash a new recovery.img, I've been hearing that there is no easy way into the recovery at startup, what does "adb reboot recovery" result in, long story short if we can get a new recovery then we can flash unsigned roms including your su/root pre installed. Sorry I'm not more help on the legwork portion of this, I really need to get a garmin to work more on this, but p.m. me if I can help more as I don't pay enough attention to these forms

tsukisan said:
Good work on the first steps, next we need to flash a new recovery.img, I've been hearing that there is no easy way into the recovery at startup, what does "adb reboot recovery" result in, long story short if we can get a new recovery then we can flash unsigned roms including your su/root pre installed. Sorry I'm not more help on the legwork portion of this, I really need to get a garmin to work more on this, but p.m. me if I can help more as I don't pay enough attention to these forms
Click to expand...
Click to collapse
Have you tried grabbing ROM Manager from the market? It allows you to install Clockwork recovery.

LiquidSolstice said:
Have you tried grabbing ROM Manager from the market? It allows you to install Clockwork recovery.
Click to expand...
Click to collapse
Do you know if there is a compatible recovery for the garminfone? You can't flash a sholes recovery on a garminfone.

ROM Manager is useless for the Garminfone. There are no backups for it and its not a supported phone.
"adb reboot recovery" I'll have to give it a try as well, now that I am also rooted.

I did a similar process... used androot (temporary root) to get rootshell with superuser app from the market.
I downloaded su binaries separately, fired up adb shell,ran rootshell.
I manually copied su to /system/xbin then used gscript lite to script the following:
/system/xbin/su -c 'mount -o remount,rw /'
/system/xbin/su -c 'mount -o remount,rw /system'
/system/xbin/su -c 'cp /system/xbin/su /bin'
After that I added the script to my home screen and I have one click root.
The changes won't persist until the boot image is changed to and repacked.
Note that the rootshell app is useless after a cold boot or if moved. It just crashes.
The most interesting thing is looking through the startup scripts that run.
There are parts from 3 or 4 developers commented out that,!among other things, show what to set to root it permanently,and what looks like loading parts of. the os from the emmc or sdcard.
And the automated test scripts built in come complete with a Garmin test phone number that can be called as well as a full suite of functional and regression test scripts that can be used to validate all functions including the Garmin apps automatically. The daemon even loads itself on boot by default.
It looks like the build they used was a virtually unmodified developer build. Hell,the boot scripts even show what to change to make it run in the emulator. That is my next project (getting it up in emulation so I can test different modifications)... well,that and see what it will take to get the Garmin app running in the latest android. I see no point in upgrading to the latest os if I lose Garmin functionality.
Being that the devs left nice comments for damn near every line and wrote very clean and elegant scripts, i would be shocked if it took very long to get Garmin up, at least in emulation.
Fyi, since piracy is illegal, I want to make it clear that the Garmin portions of my rant refer only to regaining functionality in the latest os.

Ok... to permanently root your phone...
Use the method in the first post. Then, in Root Explorer go to /system/bin and click r/w (if it isn't already). Scroll down to governor.sh, long press and choose open in text editor. Add the following to the end:
mount -o remount,rw /
mount -o remount,rw /system
cp /system/xbin/su /bin
Save it. Now at every boot you will have rw filesystems and the su file will copy over. I am working on making a modified recovery.img to flash.
I don't know why people say the Garminfone is more locked down or unflashable than any other phone. It comes with a flash_image program on the phone that lets you specify a destination partition and an image file, it will flash /system/recovery.img on boot and all the boot scripts are commented for how to do things like boot off the emmc. The developers left a bunch of services in the boot scripts but disabled to do various functions.

Tim2246 said:
1: ok step one download universal and root to sd card.
2: then download a file manager such as linda file manager.
3: download chainsdd SuperUser
4: go to settings then applications put a check next to unknown sources.Then go to Development and check usb debugging and stay awake.
5: use linda file manager and browse to sd card and install universal root "DO NOT INSTALL SUPERUSERBUILT INTO IT"
6: Install chainsdd Superuser, After install open it goto settings then scroll too bottom and click su binary it may fail the first time but click it again it will say Su binaries updated.
7: I am using root explorer i bought it from market.
8: after this is installed open it and be sure to click the rw option when you open it at top of directory. Now copy /system/xbin/su to your sd card for safe keeping along with rootshell file from sqlite_stmt_journals folder.
after you back them up too sd then copy Su file too /bin let it over write theres.
Now fire off adb and type adb shell then at the $ type su and walla full root.
Anyone have ideas on how to make it read only so system cant delete those files on reboot or automated way of putting the files in right place at reboot let me know.
Click to expand...
Click to collapse
So I ran into a little speed bump here, I'll post what I've done thus far and maybe someone has some feedback...
1) Open the applications settings menu for Android OS and Check off the option "Uknown Sources" and then click on "Development" and make sure options "USB debugging" and "Stay Awake" are checked.
2) Download and install the "Universal Androot" apk. application installer using the web browser on your android phone.
3) Launch "Universal Androot" and use the drop down menu on the main screen and select the option that states, "Do not install Superuser" and then click the "Root " button, the application will run a few scripts and then confirm success.
4) Go the Android Market, and download and install the following application, "SuperUser" written by android software developer, chainsdd.
5) Once "SuperUser" is installed on your phone, launch the application and click, "Settings" on the top right hand corner of the application, it will bring you to a list of options, scroll to the bottom, and click on, "Su binary v original", this will download a zip file containing any updates. (You may have to click this several times if it fails, it will eventually download)
6) Go to the Android Market, and download, "Root Explorer (File Manager)" and install it, you may also download this package elsewhere...
7) Open "Root Explorer" and make sure you are in the / "root directory" of the unit and then click the "Mount R/W" button at the top.
8) Browse to /system/xbin/ and copy file "su" to /sdcard
This is where I have a problem, I can not locate /system/xbin/su
Here is some additional information that may be relevant
Garmin
Hardware R1.7
Software 4.0.12
Android
Firmware 1.6
Kernel version 2.6.29

hey all!
I've tried following the directions like 10 times and i keep coming up short..i can't seem to get root.. It's odd. Would anyone be kind enough to post a video, or clarify the directions needed in a step-by-step fashion?
Thanks in advance!

Does anyone in the know have a timeframe for when we might know how to get rid of the t-mobile animation that plays when the phone boots up? I'd like to replace all the bootscreens with some wicked cool custom stuff, but gotta knock that pink crap outta the way first.

merwin said:
Ok... to permanently root your phone...
Use the method in the first post. Then, in Root Explorer go to /system/bin and click r/w (if it isn't already). Scroll down to governor.sh, long press and choose open in text editor. Add the following to the end:
mount -o remount,rw /
mount -o remount,rw /system
cp /system/xbin/su /bin
Save it. Now at every boot you will have rw filesystems and the su file will copy over. I am working on making a modified recovery.img to flash.
Click to expand...
Click to collapse
Sorry, but it didn't work for me. Rooting mine by manually pasting SU into the /bin folder works fine.
I copied/pasted your code over to the end of the file as described above.

Spazmogen said:
Sorry, but it didn't work for me. Rooting mine by manually pasting SU into the /bin folder works fine.
I copied/pasted your code over to the end of the file as described above.
Click to expand...
Click to collapse
Are you sure the version of su in /system/xbin is the one that comes with superuser? You can check by using either a terminal app or adb,going into the xbin folder, and type ./su
You should get a superuser request. If not, then something was not done correctly.

Thanks for the reply.
but since 2.1 Eclair was installed today, it's a moot point:
{
"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"
}
There is no SU in either /bin or in /system/xbin.
SuperUser by ChainsDD won't install the SU file, it keeps failing. Tried it 30x today.
Root Explorer only allows folders to be r/o now. So I am waiting on an update for that one.

How exactly did you get 2.1 on a Garminfone?

I have a Garminfone with 2.1 and all i did was download z4root from the market place and ran it and it seems to have given me a perminant root and i have no problems hopefully this helps you guys out it is a simple one click root unroot app.

Root is persistant. It survived a few battery pulls.
I have been able to get it into ADB REBOOT RECOVERY. A green droid guy with a yellow warning triangle appears.
One of the fellows in the Tmo forums claims to have gotten it into FASTBOOT menu options. If that is true, it would appear the boot loader is unlocked...

Garminfone 2.1 easily rooted...
I easily rooted my Garminfone 2.1 Eclair with z4root. It was one click and done with the options to temp or permanently root the phone it is also reversible.
Problem I am having is that I created an ext2 partition on my sd card but the phone doesn't recognize it. It was partitioned with "ubuntu livecd" with "gparted" partition manager. It also shows up in windows with "Mini Tool Partition Wizard 5" when the sd card is in a card reader attached to the pc.
Whats the next step? I want to move apps to the sd card. I have link2sd installed for this but can't figure out how to enable ext2 mount.
Also another good pc app to have if you trashed your sd card partitions is "Active Partition Recovery for Windows" works for all drives.

Issues - Rooting with Z4Root
Hello,
I have a Garminfone that came with 2.1 version. I have downloaded Z4Root and tried both options Temp and permanent. But no Joy.
I made sure, USB Debugging is off. Can someone let me know what step am I missing ??
Much appreciate your time.

z4root
Perseus71 said:
Hello,
I have a Garminfone that came with 2.1 version. I have downloaded Z4Root and tried both options Temp and permanent. But no Joy.
I made sure, USB Debugging is off. Can someone let me know what step am I missing ??
Much appreciate your time.
Click to expand...
Click to collapse
What exactly are you trying to do by rooting? Did you install SuperUser by ChainsDD? What app/file manager are you using? If you dont have this you won't be able to do anything. The apps you use for app/file management need to have root permissions or they will do nothing.
Mine rooted with z4root no problem and was able to remove all the fluff apps it shipped with that I didn't want. But this was only half of what I wanted to achieve. I haven't been able to move apps to sd, but I can't get ext2 to mount, not a problem because of the root I don't think.
What I have on my Garminfone 2.1
z4root
busybox (installed with z4root)
superuser
my backup root
uninstaller for root
super manager
Hope this helps.

Ok First off. Thank you very much for your time. It is greatly appreciated.
Well, Here's what I have done so far.
1. Downloaded and installed Z4Root from the Market.
2. Download and Install SuperUser by ChainsDD from the Market.
3. Ran Z4Root and first tried Temporary Root. That seemed to go fine until it was stuck after displaying the message ReBooting.
4. Next Tried Permanent Root Option after a Battery Pull. That asked me to turn on USB Debug. Did so and it seemed to go smoothly until that too was stuck with Rebooting message.
5. I tried the same Permanent Option after another Battery Pull. This time, it worked and the phone rebooted & came back. So I installed BusyBox from Market.
6. At this time I downloaded Titanium Backup. It complained not having root access. 7. So I started SuperUser and that showed an empty list under application tab. Went under Settings and hit the update. It failed but saved the Zip on my SD card.
8. I installed the Binary from Step 7 using Apps Manager. Tried SuperUser again. Still empty list for applications.
So there I am. I suspect I probably missed something somewhere. Possibly before doing Step 6 I should have done something. Can't seem to figure out.
Also earlier in this thread there was a mention that you will need to manually copy the binaris for SuperUser to certain specfic directory. Since it got installed successfully, do I still need to do it ?

[GUIDE][SCRIPT] How to root Android x86 4.3

As we all know, Android 4.3 brought with it some extra security features which caused some small issues with root. These have been solved by the likes of Chainfire and other developers, meaning we have root once more. This is their work, I've just botched it together to work on the Android x86 4.3 system, which works slightly differently
You will need:
A device with Android x86 4.3 on it
Optionals:
Another Linux based OS - this can be an OS on another partition on the device or a live disk/USB
Root permissions in that second OS and access to the terminal
Knowledge of which partition Android x86 is installed onto and which is its root folder (if you didn't mess with that, it tells you in the script)
Instructions:
On Android x86:
Download the attached zip and extract it using a file manager
Press Alt+F1 and use "cd" to change directory to where you extracted the zip
You should go as far in as the "README" and "install.sh" files
Run:
Code:
sh install.sh
Follow the instructions on-screen. It tells you the rest.
On a linux boot:
Download the attached zip and extract it to somewhere memorable
Open your terminal and use "cd" to change directory to where you extracted the zip. You should go as far in as the "README" and "install.sh" files
Run:
Code:
sh install.sh
Follow the instructions on-screen. It tells you the rest.
Reboot back into Android x86, it should have root now
Changelog:
v2:
Included version for Android x86 boot, through the Alt+F1 terminal
Made it a bit simpler
Screenshots
{
"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"
}
Credits
@Chainfire for SuperSU and all the files included that the script installs
The SuperSU thread, don't forget to thank on there
The Android x86 project for the OS itself and the init.sh file, which is patched as the install-recovery file is

Hello..
I try to run the install.sh but it said
"This script needs root. Enter your password to continue:
sh: 0: Can't open .install.sh"
I ran it with sudo permission. My Ubuntu is on sdb6 and and android is on sdb7.
Please assist.
Just wondering? Can I just copy the the system folder and let it overwrite (merge) the system folder in the android partition. Also what permission do I need to change for what folder if I were to do this manually.
Thanks minhgi

It hasn't extracted properly, the .install.sh file is in the zip with the install.sh
Just in case, for the next release (in testing now, can be run from the Android x86 boot itself), I made it ./.install.sh, which should work

Here comes version 2:
Changelog:
Included version for Android x86 boot, through the Alt+F1 terminal
Made it a bit simpler

Thanks Quinny,
It is working. Somehow when I downloaded the attachment the first time, the script folder was not there. So there was not script to run. Anyway, I did it through the Ubuntu terminal it is working for me.
---------- Post added at 02:49 PM ---------- Previous post was at 02:29 PM ----------
Opps..I said it to soo. I using an android build 4.3 from www.tabletx86.org and it use chainfire SU. It also seem like your rooting method use chainfire su. When I try to use root explorer to enable r/w permission, the app just force close. Also I try to launch chain su, it also force close. I am not sure if there is an incompatibiltiy issue there. I use the rom build from tabletx86 b/c it have broadcom wifi working for my laptop.
The android 4.3 from android-x86.org does not. Can you test the build from www.tabletx86.org? it was compile on 08-02-2013.
Thanks again.

minhgi said:
Thanks Quinny,
It is working. Somehow when I downloaded the attachment the first time, the script folder was not there. So there was not script to run. Anyway, I did it through the Ubuntu terminal it is working for me.
---------- Post added at 02:49 PM ---------- Previous post was at 02:29 PM ----------
Opps..I said it to soo. I using an android build 4.3 from www.tabletx86.org and it use chainfire SU. It also seem like your rooting method use chainfire su. When I try to use root explorer to enable r/w permission, the app just force close. Also I try to launch chain su, it also force close. I am not sure if there is an incompatibiltiy issue there. I use the rom build from tabletx86 b/c it have broadcom wifi working for my laptop.
The android 4.3 from android-x86.org does not. Can you test the build from www.tabletx86.org? it was compile on 08-02-2013.
Thanks again.
Click to expand...
Click to collapse
I'll have a go at some point, I'm on a slow connection currently so it might be a while

Quinny899 said:
I'll have a go at some point, I'm on a slow connection currently so it might be a while
Click to expand...
Click to collapse
not a problem. Please take you time. these builts are are preview version anyway.

minhgi said:
not a problem. Please take you time. these builts are are preview version anyway.
Click to expand...
Click to collapse
I looked this morning and it can't be run from the boot as it's got a broken superuser installed which means I can't mount the system. Don't see why it would force close though

So I tried doing the script via alt+f1 and it says its in root, then when the script runs it shows that it cant mount permission denied and it fails to remove old files and fails to chmod also. Any help would be appreciated. Thanks

wolfballz said:
So I tried doing the script via alt+f1 and it says its in root, then when the script runs it shows that it cant mount permission denied and it fails to remove old files and fails to chmod also. Any help would be appreciated. Thanks
Click to expand...
Click to collapse
If you're using TabletsX86's build, that's why, also, if you didn't allow /system to be mounted during install, then you're out of luck

Quinny899 said:
If you're using TabletsX86's build, that's why, also, if you didn't allow /system to be mounted during install, then you're out of luck
Click to expand...
Click to collapse
using latest build from android-x86.org and I didn't recall seeing anything about being able to mount /system during install.

wolfballz said:
using latest build from android-x86.org and I didn't recall seeing anything about being able to mount /system during install.
Click to expand...
Click to collapse
There is, right before you install.
Like so:
(Not my image)

Must have breezed right by it. Since i have it with windows how can i remove my current android install and start over? I ran the install again and i dont get that /system question at all.
So i tried installing on a virtual machine and i get the /system option now. Thanks for the help
Sent from my SCH-I535 using Xparent Blue Tapatalk 2

After installing on a virtual machine and mounting /system thw script ran without error. Rebooted but didnt see a superuser app so i installed supersu. Installed and opened root explorer and when trying to mount anything RW it hangs and then root explorer says not responding. Anything else i can try?
Sent from my SCH-I535 using Xparent Blue Tapatalk 2

Hello! I installed this, then a custom font. When I rebooted, I get stuck in a terminal. Any help?

Yoyodude1124 said:
Hello! I installed this, then a custom font. When I rebooted, I get stuck in a terminal. Any help?
Click to expand...
Click to collapse
Most likely the font. Did you set its permissions correctly?
Sent from my Galaxy Nexus using Tapatalk 4

Works perfect. I've used it twice now. Thanks.
If you get stuck in terminal you can type "start" to boot android.
Sent from my Lenovo Thinkpad Edge using Tapatalk 4

Unlockable bootloader/custom roms?
Is there any way to get custom recoveries on this, so we could install custom ROMs?

Yoyodude1124 said:
Is there any way to get custom recoveries on this, so we could install custom ROMs?
Click to expand...
Click to collapse
Nope. And there won't be ROMs like CM or the like, x86 is completely different to ARM and they're highly unlikely to make it compatible

I also only get the question whether to install /system as r/w with builds before 4.3. Using the boot image of 4.2 of course results in a mess but it takes me to the screen where I can choose to use system as r/w or read only.
Tried with a freshly fixed mbr and clean install.

[script]replace kingroot's kinguser with supersu

Remove KingRoot’s KingUser with SuperSU using Terminal [Requires Intermediate skills]
This method works for almost all the android devices and works the best, However, it requires some decent skills to follow the instructions and copy the commands listed below into the Terminal app.
The link of the script which is shared below works without a computer system/PC, Hence the steps I’m listing below won’t require a computer PC. So are you ready?
Downloads
This download section has the download links to the files or apps you will require to complete the below listed steps. Ready to shift from KingUser to SuperSU? What are you waiting for?
lets begin.
1.Download & Install Terminal Emulator App
2.Download SuperSu script from here http://www.mediafire.com/file/mxzbt42xypvn2ts/Replace_Kinguser_with_SuperSU-v2.4.zip and unzip it!
Steps to Replace KingUser with SuperSU?
Step 1: Extract the Replace_Kinguser_with_SuperSU ZIP File & Transfer the extracted version to Internal storage of device.
Install the Terminal app for Android and extract the Replace_Kinguser_with_SuperSU file and after extracting the Replace_Kinguser_with_supersu file transfer the “Extracted Folder – MRW” to outermost directory in the internal storage.
Step 2: Open Terminal Android App & Write the Following commands in the Android Terminal.
Open the terminal android app type the command “su” in the terminal, after writing the SU in terminal, you will be prompted with the message box asking you to deny/grant the functions. Granting permission will help you remove the kinguser on your smartphone.
After granting permissions you will have to type one single line of code, The other command will be: sh /sdcard/mrw/root.sh
After writing the above command, it might show some error, but ignore that error, it will automatically launch SuperSU, in case it doesn’t manually open SuperSU.
Once done, Restart your smartphone and you will see that SuperSU works flawlessly on your Smartphone. That’s all, you’ve successfully replaced KingRoot’s KingUser with Chainfire’s SuperSU.
Huge thanks to the Dev of the script
Source and Download link credits goes to Droidmen.com
Thread link of Droidmen: https://www.droidmen.com/remove-kingroot-kinguser-with-supersu/
I shared this guide from droidmen if you found this guide useful PLEASE HIT THANKS BUTTON!​

RESERVED

Good
Sent from my Redmi Note 3 using Tapatalk

can anyone confirm it in above 4.4 ?

sohamsen said:
can anyone confirm it in above 4.4 ?
Click to expand...
Click to collapse
Well it works on 4.4.2 but you need you manually uninstall kinguser in system after.

Arkonite said:
Well it works on 4.4.2 but you need you manually uninstall kinguser in system after.
Click to expand...
Click to collapse
mine uninstalled automatically

Replace kingroot with supersu
Here you can get the most effective way to replace kingroot with supersu;
How to replace kingroot with supersu

King roots

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.

What does "the su binary is out of date " actually mean? Is there a way to manually fix this?

Quick background: I want to start fresh with my Nook Tablet and leave out GApps this time, opting for microG instead. I'm familiar with all that entails and have done it on other devices.
The problem, in a nutshell: After wiping and reflashing the custom AOSP 7.0 ROM, I flash a small zip which contains and places the su binary (as far as I understand). Then I reboot and install a Superuser control app. I get "the su binary is out of date" message and do not have root.
I am following my own instructions from here when I first flashed the ROM with GApps. But now they don't work! Later in that thread a few people express problems with the same thing.
So...what does this "out of date" business actually mean? Is there a "use by" date on the su or something? That seems unlikely. I've tried all kinds of orders of operation with this thing but keep coming up with the same result. Searching around on line I can't seem to find any sort of explanation, just a lot of schemes, many dubious.
I've looked at SuperSU zip packages, but every one I try seems to be wanting system-less root and there is no way I know to unlock the bootloader.
I know that Magisk exists, but have never gotten into using it. I'd rather not, if possibe. I just don't see why something that worked a few years ago does not work now. It's not like it needs to contact a remote source for information.
As a last resort I could return to a backup and try to manually remove GApps but I'd really rather start with a clean ROM install and go from there. I need root to do what I want or I wouldn't bother with any of this.
Suggestions, explanations?

Uninstall / delete SuperSU app.
FYI:
The SU binary is a Android shell command typically incorporated in Toybox, the Linux commands suite merged with Android since its version 6, but left off by almost all OEMs - for good reasons.
The SU binary is available as standalone cmdlet at various locations in Internet. It also comes with Magisk.

every rooting solution's su binary is different from traditional linux su.
it simply means the su binary does not fit the Superuser app. according to support thread you still can grant root and just update su binary straight from within the app (won't work with foreign su)
https://forum.xda-developers.com/t/...linux-capable-superuser.3216394/post-64823952

aIecxs said:
every rooting solution's su binary is different from traditional linux su.
it simply means the su binary does not fit the Superuser app. according to support thread you still can grant root and just update su binary straight from within the app (won't work with foreign su)
https://forum.xda-developers.com/t/...linux-capable-superuser.3216394/post-64823952
Click to expand...
Click to collapse
Yeah, but it (the apk) doesn't do anything. And the links in the thread you reference to updated zips, etc., all give 403 errors.
I "understand" the concept of matching the su binary with the superuser controller app, but I can't see how a combination that once worked now does not. That's what is frustrating. Like it's magic.

most likely there is a foreign leftover su (chainfire's SuperSU or something else?) which is not granting access to phhusson's Superuser.

aIecxs said:
most likely there is a foreign leftover su (chainfire's SuperSU or something else?) which is not granting access to phhusson's Superuser.
Click to expand...
Click to collapse
Could be. A TWRP examination of /system/bin shows no sign of su (no wonder it needs "updating"). Meanwhile, /system/superuser is chock full of SuperSU stuff and the phh stuff, including a copy of su. So clear all that out and start again.
I guess I need to check if su is actually placed in /system/bin after flashing the zip package. Otherwise...maybe just put it there myself?

afaik all custom binaries belong to /system/xbin which is also in path. what's wrong with systemless-root in boot?
latest official SR3-SuperSU-v2.79-SR3-20170114223742.zip by Chainfire is capable of.

aIecxs said:
afaik all custom binaries belong to /system/xbin which is also in path. what's wrong with systemless-root in boot?
latest official SR3-SuperSU-v2.79-SR3-20170114223742.zip by Chainfire is capable of.
Click to expand...
Click to collapse
Before flashing the su zip there is an su already present in /system/xbin. After flashing, there is also an su present in /system/bin. And yes, I wiped thoroughly (twice).
I was surprised at the su already in /system/xbin. Out of curiosity I booted up another tablet running CM 13. It, too contains su in both locations, but the dates on the files are very different. The one in /system/bin is today's date, while the one in /system/xbin is sometime back in 2009 (like when the ROM was perhaps cooked up). Turns out even my ancient Nook Simple Touch (which is rooted) has an su in both locations.
Anyway, I see there is clearly an su newly placed in /system/bin now that I've flashed the su zip package. So it should work when the controller app is installed...
None of the Chainfire zips I have tried will work. They all seem to want the bootloader unlocked and so each one fails.

you can flash modified system on locked bootloader? Now you have root and TWRP, I guess bootloader is unlockable. I bet @AdamOutler can. at least, another guy managed it obviously...
https://forum.xda-developers.com/t/barnes-noble-nook-tablet-10-1-bntv650-working.3873476

aIecxs said:
every rooting solution's su binary is different from traditional linux su.
Click to expand...
Click to collapse
Wrong, as so often:
1. The su ( read: Substitute User ) shell command allows users to become other users. This command is thought to escalate privileges by becoming a privileged user; therefore, the default user is the root if no user-id is specified.
2. This is true for su shell command as it comes with Linux and/or Android ( where su since Android version 6 is included in Toybox command suite - and su might also be integral part of 3rd-party Linux commands suite named BusyBox )
3. All 3 mentioned su shell commands equally allows users to become other users. With no arguments passed, USER is root. Only difference is the way and order arguments get passed to su.

@jwoegerbauer you have no clue what you're talking about. I have already tried to explain you here, furthermore I have proofed you wrong there (your linked binaries were not even build with -fPIE)
I get the feeling you don't even know what a Superuser app actually is.

To my knowledge SuperUser app is predecessor of Magisk Manager app.

yes, Magisk app also includes Superuser app (second tab on bottom). how is that related to my question? Did you finally read about what su daemon is, and how the Superuser app grants requesting apps to hook up to daemon?
or do you still insist every Superuser app can just work with every su, or root access can be achieved by just toybox su (like linux su)? if so, please link the toybox used for, so I can test it myself.

I'm surprised that you're not able to find Toybox on the Internet, but you expect a link from me.
I'm also surprised that you obviously take pleasure in disparaging others here if they don't think or act as you do.
BTW:
When I'm mentioning SU at XDA threads, then I really mean the SU binary itself - as it's well known from Linux - and NOT the supersu daemon, what grant root to apps, as you do. Why exactly do one need an app to have root permissions? To enter protected user-space?

I have asked clear question, please tell us which toybox or su binary will work for getting root shell.
where shoud I place it? what permissions should I set, and how?
Spoiler
official toybox
{
"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"
}
BTW:
wasn't it you the one who called me an idiot two times when confronted with your false claims?

You have used the NON-ROOT version of Toybox.
The full version of Toybox you find here:
Index of /toybox/downloads/binaries
It's on you to replace the mangled Toybox version with the full version: shouldn't be too difficult for an Android guru as you are.

First, this toybox is missing important applets without android smartphone wouldn't work properly anymore. That's why one must not replace toybox.
second, you still haven't answered the question which location and permissions one must set.