Related
I've had the SDK on my computer for months but never really got into ADB. When I go into tools and click on ADB it opens up and closes within a second. I'm trying to root my MT4G but the terminal method just isn't working for me so I'm going to try ADB. What do I have to do to get ADB setup and working with my MT4G?
Let me get home (be about 30 to 45 min) and I will try and walk you thru it.
My MyGlacier 4G MINE!!!
Arcadia310 said:
I've had the SDK on my computer for months but never really got into ADB. When I go into tools and click on ADB it opens up and closes within a second. I'm trying to root my MT4G but the terminal method just isn't working for me so I'm going to try ADB. What do I have to do to get ADB setup and working with my MT4G?
Click to expand...
Click to collapse
ADB is a tool that needs to be ran from CMD Prompt. Just a quick example to make sure your seeing your phone and assuming you have already extracted the SDK package. FYI, I moved the tools folder into the sdk folder, makes it easier to access. I would open cmd promt and type:
Note: Hit enter at the end of each line.
cd \
cd sdk/tools
adb devices (this will start deamon and then show you your device if ADB drivers are installed.
To install the drivers plug your phone in and let it auto mount your sdcard then run HTCDriver.exe. Unplug your phone and plug it back in, it should now install the driver needed for ADB. To verify everything is installed right go to your Devices and look for Android USB Devices and under that should be My HTC.
Check out this link. Its kinda a how to typed up back in the G1 days.
YOu get this working?
These are my notes and guide for rooting the Kindle with 6.2.1 firmware. If I left something out, or something is not working, please leave a comment and I'll try to update.
Credit goes to JCase for the root. Please consider making a donation to him here:
https://market.android.com/details?id=net.andirc.jcasedonate
Original procedure is here:
http://www.androidpolice.com/2011/1...on-kindle-regardless-of-its-software-version/
ADB INSTALL AND TEST - Method 1 (skip to the ROOT INSTALL section if you already have a working ADB)
NOTE: ADB = Android Debug Bridge. It is a command line interface to the android device. A working ADB is required before you can root your Kindle. ADB is installed on a PC and accesses the Kindle via USB cable.
Install Java SE Development Kit 7 on PC
The Android SDK Manager requires Java SDK
http://www.oracle.com/technetwork/java/javase/downloads/jdk-7u1-download-513651.html
Install Android SDK Manager on PC
The Android SDK has the drivers and ADB needed to perform the root procedure
http://developer.android.com/sdk/index.html
Uncheck Android 4.0
Check 2.33
Ensure Google USB Driver is checked
Install to c:\android to make typing easier later on
NOTE: The install can take a long time!
Manually update files so drivers will properly install
Open c:\users\your account name\.android\adb_usb.ini (or c:\documents and settings... if you have XP) and add the following
Code:
0x1949
Open c:\android\extras\google\usb_driver\android_winusb.inf and make additions as shown:
Code:
[Google.NTx86]
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
....
[Google.NTamd64]
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
Install drivers
Find the Kindle device in device manager and update drivers. Point to the location with android_winusb .inf
Verify ADB works
Open a command prompt
CD to c:\android\platform-tools
Code:
adb kill-server
adb devices
If it's working, ADB will return a large number, like this:
Code:
312342134231342 device
ADB INSTALL AND TEST - Method 2
NOTE: I have not tried this, but Vashypooh's app can apparently handle the driver install, and run ADB without installing the above software. If all of this works, then his app would be the best way IMO.
NOTE 2: I've seen a lot of comments suggesting the driver install in Vashypooh's app doesn't work at this point.
http://forum.xda-developers.com/showthread.php?t=1399889
ROOT INSTALL - Method 1
Install JCase's kindleroot_androidpolice.apk
JCase's app gives ADB root access. Once this is done, you still need to install the superuser app
Download kindleroot_androidpolice.apk to PC
http://www.multiupload.com/VNZ6Y41EQF
Ensure the Kindle is connected via USB, and copy file to Kindle sdcard
Using ES File Explorer on Kindle, navigate to the kindleroot_androidpolice.apk and launch
Follow prompts and click root
Install superuser app
Download superuser-2 to PC
http://www.multiupload.com/M2CX14W7Y0
Unzip to c:\download\sufiles
Use ADB to install SU app
Code:
adb root
adb remount
adb push c:\download\sufiles\su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb install c:\download\sufiles\Superuser.apk
adb reboot
ROOT INSTALL - Method 2
NOTE: I have not tried this, but Vashypooh's app can apparently handle the root process.
BurritoRoot (Temporary)
Install Permanent Root with Superuser
http://forum.xda-developers.com/showthread.php?t=1399889
A+ instructions, wish I could write my own that good lol.
jcase said:
A+ instructions, wish I could write my own that good lol.
Click to expand...
Click to collapse
Thanks to you for the root. I hope the guide will help those trying to root!
Thanks for the clear and easy steps.
Great guide Ectoplasmic!
One thing I would add though, in step 5 "Verify ADB Works", before you use the "adb devices" command, you need to type "adb kill-server". If you don't type in "adb kill-server" first, the device won't show up when you use the "adb devices" command. Or at least it didn't for me.
Otherwise, everything worked FLAWLESSLY. I verified I was rooted using Root Checker. Thank you!
zopzop25 said:
Great guide Ectoplasmic!
One thing I would add though, in step 5 "Verify ADB Works", before you use the "adb devices" command, you need to type "adb kill-server". If you don't type in "adb kill-server" first, the device won't show up when you use the "adb devices" command. Or at least it didn't for me.
Otherwise, everything worked FLAWLESSLY. I verified I was rooted using Root Checker. Thank you!
Click to expand...
Click to collapse
Thanks, I added this to the guide.
Hi I use JCase method to root my 6.2.1 KF, then I need to unroot it so my kids can still enjoy the prime video, but I cannot. I try rootkeeper but failed. I also try the "kindleroot_androidpolice.apk" and click the unroot button, but it still cannot unroot. Pls help!
Get help in irc from jcase and vashypool theyll probably be able to help u
tkcctkcc said:
Hi I use JCase method to root my 6.2.1 KF, then I need to unroot it so my kids can still enjoy the prime video, but I cannot. I try rootkeeper but failed. I also try the "kindleroot_androidpolice.apk" and click the unroot button, but it still cannot unroot. Pls help!
Click to expand...
Click to collapse
Unroot in my app (BurritoRoot) does not remove su, it just turns off adb root (which is what my app turns on) sorry for the confusion.
Will add in the future when I release burritomod
Here's the equivalent instructions for Mac
I am pretty new myself, but I'm happy to share what I've come up with so far. I am on a Mac OS X 10.6.8
Download the Android SDK for Mac (dl.google.com/android/android-sdk_r16-macosx.zip), the easiest place to put it is at the top of your user directory, from the browser download window chose your username from places on the left side, then name the zip "Android"
Next from Finder, navigate to the place where you downloaded the SDK, and double-click on it which should unzip it and create a folder of the same name e.g "Android". Open that and inside it will be a folder "tools", and inside that there will be a file "android". Double-click that to run it and the "Android SDK Manager" program window will pop up, you will also see a Terminal window in the background, don't worry about that. Uncheck all the boxes, then check "Android SDK Platform-tools" which should be the third from the top, and click install. This gets you the actual "dab" program.
Once adb is setup, to get it to recognize your kindle fire on your mac, you may need to make an entry in a config file if you haven't already.
Start Terminal Applications > Utilities > Terminal or if you are used to using spotlight, simply type in "Terminal". (here's an intro to using Terminal guides.macrumors.com/Terminal) and navigate to the directory where you have adb, e.g. if you placed it at the top of your user directory that would be
Code:
cd Android
or if you left it in the default downloads directory it would be
Code:
cd Downloads/android-sdk-macosx/
then enter the following commands
Code:
mkdir ~/.android
You may get the following error
Code:
mkdir: /Users/<username>/.android: File exists
If so, that is fine, continue to the next step
Code:
touch ~/.android/adb_usb.ini
open -e ~/.android/adb_usb.ini
TextEdit will open with that file open, you should have an entry in it on a single line that says
Code:
0x1949
if not, copy that in, then save and close it, then
Code:
./adb kill-server
Connect your kindle to the mac if it isn't already, then
Code:
./adb devices
You should see a message like
Code:
List of devices attached
2ED6000600000001 device
On your kindle, make sure you have a file navigation app, the example above ES FileExplorer is excellent and is the one I use from Amazon app store
Download Burrito Root from Android Police ( androidpolice.com/2011/12/23/exclusive-how-to-easily-root-the-amazon-kindle-regardless-of-its-software-version/)
Also download the Superuser.zip from the same page (multiupload.com/ONH28CB1GU) and unzip, then make sure you move the contents "su" and "Superuser.apk" into the same directory as adb
Through Finder copy the "kindleroot_androidpolice.apk" file you downloaded earlier to your kindle, some place like "download" so you can find it easily later
Now on the Kindle, tap disconnect on your KIndle so you can get back to the apps screen, launch the file explorer you installed earlier, navigate to folder you copied it to, e.g. "download" then install the "kindleroot_androidpolice.apk", open it, and go through the steps to launch click "Root"
Back on the Mac, in the terminal window where you had adb going, enter the commands
Code:
./adb root
./adb remount
./adb push su /system/xbin/su
./adb shell chown 0.0 /system/xbin/su
./adb shell chmod 06755 /system/xbin/su
./adb install Superuser.apk
./adb reboot
You should be rooted now, then you can follow the other instructions out there for getting Android market, etc working
TIP
here's a tip if you don't want to have to type in the period and slash ahead of adb every time. from your terminal window enter the
Code:
cd ~
touch .profile
open -e .profile
That will open text editor, and paste in the following line,
Code:
PATH=${PATH}:/Users/<username>/<sdk-directory>/platform-tools
replacing both our user name and the path to where you have sdk e.g. in my case
Code:
PATH=${PATH}:/Users/kbiz/Android/platform-tools
Then close the terminal window and reopen a new one and you should be good to go, now you'll only need to type in "adb".
Let me know if I missed something, trying to give back since this forum has been super helpful.
---------- Post added at 01:04 AM ---------- Previous post was at 12:58 AM ----------
tkcctkcc said:
Hi I use JCase method to root my 6.2.1 KF, then I need to unroot it so my kids can still enjoy the prime video, but I cannot. I try rootkeeper but failed. I also try the "kindleroot_androidpolice.apk" and click the unroot button, but it still cannot unroot. Pls help!
Click to expand...
Click to collapse
OTA Rootkeeper should work but since its not, try this (courtesy rootkindlefire.com/kindle-fire-unroot/how-to-unroot-kindle-fire/)
Code:
adb shell
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
rm /system/app/Superuser.apk
rm /system/xbin/su
reboot
after your Kindle restarts you won't have root and Amazon Video should work just fine.
Hello,
I have successfully rooted my device with the above instructions. While installing the Android market I was abusing of my root privileges and I've successfully "burned" my device. That is, the Kindle won't start up anymore (it stays forever in the initial phase showing the kindleFire logo).
I don't know where else to turn for help so I'm writing about this here. If anyone has hints of how I could recover my kindle from the void, please let me know
Cheers
http://forum.xda-developers.com/showthread.php?t=1356257
Yesssssssssss
Yesssssssssssssssssss. So nice to have root again. My Titanium Backup and SUFBS works again
I had ADB and SDK working when I had my Glacier, but since I have gotten my SGS2, and my Kindle, Android SDK Manager will not open... It just opens a command prompt, and then closes.. I have reinstalled both the SDK Manager and the Java Kit... Any ideas?
EDIT:
I must have messed with something in my system settings somewhere to corrupt a bunch of stuff... I did a system restore to the 18th of December, reinstalled, and everything works perfect now... Oh well! Haha
Hey, I used a combo of the link JCase gave me when I had questions, this guide, and the links off the rootzwiki guide and managed to get it first try. It was actually easier than I thought it was going to be. I've never rooted anything before, I didn't even have ADB or the SDK until tonight. The process (while using both guides and video tut) went smoothly without a hitch. I just finished installing the Android Market but have to wait til morning to access it, as I have no WiFi at home, and its too late for me to be driving to a hotspot. Thank you very much. You(JCase) and your comrades who put this all together f**king rule.
a really clear and easy guide ! - congratulations - you shoud try to let it pin on top !
Ectoplasmic said:
NOTE 2: I've seen a lot of comments suggesting the driver install in Vashypooh's app doesn't work at this point.
Click to expand...
Click to collapse
the reason people have problems with vashipooh's driver installation seems to be the old drivers - they don't manage to clean up the old drivers:
disconnect KF
Open an (elevated for win7) command prompt:
set devmgr_show_nonpresent_devices=1
devmgmt.msc
device manager opens - click "view" - click "show hidden devices"
now you see all devices ever connected/installed
uninstall all devices regarding "kindle" and "android (composite) adb device"
connect KF - will startup by itself
select the most recent driver (that you have installed before by install_driver.bat from KFU) manually (check date/time)
now you should be set up with a good driver installation
btw. i'm on xp - it's working for xp and 7, 32 and 64 bit
These are instructions for rooting Android devices that utilize the RK3066 chipset (Cortex A9 Dual Core, MALI Quad-Core GFX).
I have tested and verified that these instructions work for the UG007 Android-on-a-stick...they *should* work with any other devices that utilize the same USB chipset. I can almost guarantee this will work on the Imito MX1/2 as you can swap ROMS from this device.
(Basically, if you have the right ADB drivers, you should be good to go)
As per every other thread you read on this site - I TAKE NO RESPONSIBILITY FOR ANY DAMAGES YOU MAY CAUSE TO YOUR DEVICE.
This is a fairly risk-free mod, but you know...$hit happens.
Okay. Let's start.
THIS TUTORIAL ASSUMES YOU HAVE ADB AND KNOW HOW TO USE IT, and that you're in a Windows environment. There are numerous places on the web where you can find this info...and I ain't yo mamma.
1. Download all the files attached to this thread.
2. Attach your RK3066 device to your computer via it's microUSB port. You'll need to have it hooked to a display too.
3. Once booted, go to system settings. Under settings > developer options, enable USB Debugging. Under settings > USB, click "connect to computer" (This may vary depending on your ROM configuration. The point here is to have debugging enabled and your computer to recognize the stick in device manager as something other than USB storage)
4. Extract the right drivers for your system (x86/x64)
5. Go to device manager on your computer. Look for the new "unknown device". Right-click, pick "update driver software"., "browse my computer".
6. Browse to wherever you extracted the drivers in step 4. Click Next. Confirm that you want to install.
7. Open a command window in the directory where you have ADB. Type "adb devices". Still nothing, right?
8. Navigate to C:\users\MYUSERNAME\.android, where "MYUSERNAME" is your User Name. (Duh?)
9. Create a file called adb_usb.ini
10. Open it in a text editor. Add the following string and save (This tells ADB to look for our Vendor ID:
0x2207
11. You should now be able to type "adb devices" at CMD and see your device.
12. Now for the fun. Extract the stuff from "pushme" to the same directory as ADB.
13. Enter the following commands (note: The "$" and "#" symbols do not get keyed in):
Code:
adb push psneuter /data/local/tmp
adb shell
$ cd /data/local/tmp
$ chmod 777 psneuter
$ ./psneuter
14. Psneuter should run and close shell when done. Enter MOAR commands:
Code:
adb kill-server
adb devices
adb shell
15. Take a good look. Is there now a "#" sign? Good. You now have root access. You may continue. If not, then proceed to go yell at me in the comments. If yes, then proceed to enter the last batch of commands to make your newfound privileges permanent:
Code:
mount -o remount,rw -t rfs /dev/block/st19 /system
exit
adb push busybox /system/bin
adb push su /system/bin
adb install Superuser.apk
adb shell
# chmod 4755 /system/bin/busybox
# chmod 4755 /system/bin/su
# mount -o remount,ro -t rfs /dev/block/st19 /system
# exit
adb reboot
After a reboot, download a root app from Play Store to see if it worked! I find Root Checker is boffo for this sort of thing:
https://play.google.com/store/apps/...tcheck&feature=nav_result#?t=W251bGwsMSwyLDNd
THANKS/CREDITS:
Aaron Orquia @ Pocketables.com for the original "universal" root method.
AMJtech's tutorial where I found working ADB drivers and the adb_usb.ini bit to get it recognized.
The guy(s) who make Super1ClickRoot for putting all the necessary files in one easy-to-find spot.
Thanks for this tutorial.
A couple of notes:
Wow !! That's a lot of extra steps for you Windows users. Mac and Linux users start at step 11 (but if you are a Mac or Linux user, you already knew that. )
Linux: If the device still does not show up in Step 11, post, and I can help (Hint: It may not be /just/ the udev stuff.)
Is step 13 necessary? adb remount works on mine. (not sure if I had to adb root first or not) but I can have a root shell via adb without psnueter.
If adb remount succeeds, skip step 14, and continue with the 3rd line of step 15.
Linuxslate said:
Thanks for this tutorial.
A couple of notes:
Wow !! That's a lot of extra steps for you Windows users. Mac and Linux users start at step 11 (but if you are a Mac or Linux user, you already knew that. )
Linux: If the device still does not show up in Step 11, post, and I can help (Hint: It may not be /just/ the udev stuff.)
Is step 13 necessary? adb remount works on mine. (not sure if I had to adb root first or not) but I can have a root shell via adb without psnueter.
If adb remount succeeds, skip step 14, and continue with the 3rd line of step 15.
Click to expand...
Click to collapse
Thanks for the input! Yes, yes, I know windoze makes more work. It's also pretty widespread for folks.
For step 13 - I think it depends on the device. It would be nice for others to weigh in and let me know if it's needed. If not, I can totally remove it.
Also, in the other ROM thread, I made, it's even easier to root - you just grab one of the pre-rooted ROMS and drop it in SD card...the system does the rest. Mind you, this is for the UG007.
Links UG007
If you Bluetooth connection is not working properly, try to install this custom ROM: http://blog.geekbuying.com/index.php/category/android-tv-stick-tv-box/ug007/
How to install CWM-based Recovery: http://androtab.info/clockworkmod/rockchip/
Both worked for me. I was able to connect my BT Keyboard/Mouse Pad combo
./psneuter
Failed to set prot mask (Inappropriate ioctl for device) ??
nice tutorial.. while finding the best way to work my ug007 i stumbled upon this thread via armtvtech.com
currently i only knew this tutorial to root the device, but looking at yours ill give it a try first.
digitalhigh said:
Also, in the other ROM thread, I made, it's even easier to root - you just grab one of the pre-rooted ROMS and drop it in SD card...the system does the rest. Mind you, this is for the UG007.
Click to expand...
Click to collapse
you cant install custom roms without flashmode, cant do flashmode without opening device.. or did i get it wrong!? talking about the ug007
actually you can install a custom rom once you are rooted without opening the device, here
Linuxslate said:
(Hint: It may not be /just/ the udev stuff.)
Click to expand...
Click to collapse
ehm.. im still preparing to root, i guess you hint at the android sdk?
if not ill holla back at you and complain why you didnt write it out in first place
but very good to know that i skip alot by "almost" only installing ubuntu to a vm
I may be missing something, but I couldn't get this to work on my UG007
psneuter didn't work for me, gave me an error about 'invalid ioctl' or something. But the strangest thing is that "adb shell" already shows the # in the prompt.
To confirm my suspitions, I also typed "adb root", which returned "adb is already running as root".
So I proceeded with the rest of the instructions. No errors appeared, installed Superuser and I can see su and busybox in system/bin
But when I download root checker it says it wasn't properly rooted. installing terminal and type "su" says permission denied - and that's it.
Am I missing something? I'm new to this rooting thing, so please don't be angry with my noobish questions
I managed to do it - but *not* by following this tutorial.
I used this: armtvtech.com/armtvtechforum/viewtopic.php?t=28 (Cant post links yet, sorry!)
Only ran the "TPSarky-VonDroid-Root" bat, and presto! I had root on UG007.
I even fixed the changing MAC address problem with wlan.ko from armtvtech.com/armtvtechforum/viewtopic.php?f=69&t=632&start=10 (link on page 2). I just copied it to /data/local/tmp, set permissions as rwr--r-- and then used root explorer to copy it to /system/lib/modules - now I have wifi signal every time I boot the device, and don't need to mess with my router config every time
I also manage to get xbox360 wired controller working. xpad.ko on /data/local/tmp and then insmod /data/local/tmp/xpad.ko - just connect the joystick after that, and it will be recognized. Only problem is, after a reboot I have to insmod again.
I tried doing the same thing I did with wlan.ko, but nothing happens - system won't load it on boot. Am I missing something here?
The psneuter is broken
I'm on Linux, running a RK3066, and psneuter gives "Failed to set prot mask (Inappropriate ioctl for device)". Running Ice Cream Sandwich 4.1.1, kernel 3.0.8+, build RK30_anpei10w1am-r4.0.57.20121207, A10-2 cpu.
SLotman said:
I may be missing something, but I couldn't get this to work on my UG007
psneuter didn't work for me, gave me an error about 'invalid ioctl' or something. But the strangest thing is that "adb shell" already shows the # in the prompt.
To confirm my suspitions, I also typed "adb root", which returned "adb is already running as root".
So I proceeded with the rest of the instructions. No errors appeared, installed Superuser and I can see su and busybox in system/bin
But when I download root checker it says it wasn't properly rooted. installing terminal and type "su" says permission denied - and that's it.
Am I missing something? I'm new to this rooting thing, so please don't be angry with my noobish questions
Click to expand...
Click to collapse
Try renaming old "su".
Check permissions on the su and busybox you installed.
MK808, MK809 [model T002], and the MK802 III anyone?
Hi,
Thanks OP for this information.
I have a Samsung S3 [my first android device] which I rooted with no problem, but am a total noob when it comes to these android sticks.
One can say they are very similar, so I wont be completely in the dark. OK, now that we got that out of the way...
Can anyone please confirm whether they have used this with the MK808, MK809 [model T002], and the MK802 III,
I have ordered these from 1 from amazon and 2 from ebay and am expecting delivery shortly, therefore I just want to make sure before I go bricking them one by one...
I notice that they all have RK3066 Cortex A9 chips but are manufactured by different companies. The ones I see on eBay, although they all bear the same code MK8xx, they all look very different! I presume the MK8xx code is a universal model?? just like 80486 was to the PC? given the case does this method work universally?
I intend to set them up with XBMC media centres and to use with a Xbox controller. Any advice on the best way for achieving this would be nice too.
Thanks
:good:
Linuxslate said:
Thanks for this tutorial.
Linux: If the device still does not show up in Step 11, post, and I can help (Hint: It may not be /just/ the udev stuff.)
Click to expand...
Click to collapse
Linuxslate, I have an MK808 that shows up in lsusb as 2207:300a when I put it in "flash mode" but it never shows up via "adb devices".
I got mine the other day and it turned out to be rooted already?
I decided to install SuperSu and that's how I found out it was rooted.
Immediately, installed Busybox, System Tuner Pro and Titanium Backup.
Rob
Rob sent this from his SPH-D710 via Tapatalk
So would this possibly work on this - http://www.zoostorm.com/Products/357-zoostorm-sl8-3305-1030-tablet-pc.aspx
States it's a Rockchip RK3066 Cortex A9 Dual Core 1.5GHz, running 4.1.1 Jelly Bean, quite interested in getting one & root would be a bonus.
psneuter broken
Hello,
the psneuter attached to the first post doesn't do anything to my ug007. I have the same error others have posted here and haven't gotten a reply about.
To unlock, I used the script that's mentioned in a post above, TPSarky-VonDroid-Root. If you google that, you'll find a download link amongst the results.
Thank u very much...:thumbup:
................................................................................................
Linuxslate said:
Try renaming old "su".
Check permissions on the su and busybox you installed.
Click to expand...
Click to collapse
Can you elaborate a little bit what you mean by renaming "su"?
I'm having the same issue..
Both su and busybox are having the same permission -rwsr-xr-x.
Sent from my Transformer Prime TF201 using XDA Premium HD app
I configured one of these at work. Upon using the terminal app and typing in su I got the # sign. They seem to come from the factory rooted already.
Sent from my Nexus 4 using xda app-developers app
ageerer84 said:
I configured one of these at work. Upon using the terminal app and typing in su I got the # sign. They seem to come from the factory rooted already.
Click to expand...
Click to collapse
Not exactly: this particular su can be used only from adb console, or at least that how it was on my tablet. So you need to replace it with a Superuser apk's su to get all features of rooted android. You can get one e.g. from FDroid
--
blog
Not sure what u mean by on your tablet. Android devices don't typically come rooted but I was surprised to have root access via terminal emulator on this stick PC. I just took it out of the box and definitely didn't have to go through the adb interface on a computer to flash superuser or what have you. Is this just me or is this a typical experience with this particular device?
Sent from my Nexus 4 using xda app-developers app
Does anyone here have any tools or guides on how I can achieve root on my Verizon LG G2 on my mac in terminal or via a tool like this one which seems to only be windows based: http://forum.xda-developers.com/showthread.php?t=2448887
I don't have access to a windows machine at home that I can use to get root on my LG G2. I would really appreciate it if someone could make a guide (Text or Youtube even better) or a root tool like the one I linked to above. I'm not trying to be a mac snob which I'm not...I just do a lot of design work and photo editing and have used Mac's since I find that most of the studios I deal with all use them and I need to be able to exchange files that are compatible. I would really appreciate some help with regards to doing this on my MAC. Thanks for listening and I hope someone can point me in the right direction.
Thanks again.
I'm also looking for a Mac solution. I'm a long time Android user but have a Macbook. Hoping someone comes up with Mac version.
I used the method by thecubed in the development section. I unzipped it and followed the adb commands in the .bat file (right click that file, open with text editor). Don't forget the part about unplugging the USB cable and disabling and then enabling debugging.
mjdupuis said:
I used the method by thecubed in the development section. I unzipped it and followed the adb commands in the .bat file (right click that file, open with text editor). Don't forget the part about unplugging the USB cable and disabling and then enabling debugging.
Click to expand...
Click to collapse
But, did you do it on a Mac?
Thank you Devs. From my LG G2.
Yes, all through terminal.
I can post the specifics, but I'm not a developer and most likely could not help you if you or I happen to mess something up.
That would be great if you could post the specifics. Would really love to see how you did it.
WARNING! This is just what worked for me, and it's just the adb commands from thecubed's program. All credit goes to him, I didn't do any of this, just took the info from it.
Here's the thread: http://forum.xda-developers.com/showthread.php?t=2448887
Download it, unzip it, and then take a moment to go back and thank him if you didn't do that.
You are not actually using his program, just the files and commands. Everything is done using Terminal and the Finder. You must have ADB working, look elsewhere for instructions on setting that up.
The files used here are the Verizon versions of the files, which I used for my phone. They are also specific to the OTA'd Verizon software, "11A" so there are different files if you haven't installed the OTA. These commands are correct, but the files being pushed aren't all the same between different carrier models and do not work with any other carrier. All the right stuff for other carriers is contained in thecubed's program.
The bold sections are files you need to send over adb, you can manually enter the file pathway or drag the files from finder into terminal after the adb commands (and before you type the destinations).
One more warning; if this is your first time using adb or terminal, I don't recommend this as your first try. It's super easy to screw something up in terminal.
Your phone must have developer options enabled and usb debugging on. plug in your phone via usb and select "Internet" and then "Ethernet."
adb push ytiruces_1a_vzw /sdcard/ytiruces_1a
Unplug usb, disable USB debugging and then re-enable it. Plug USB back in.
adb shell "mount -o remount,rw /system"
adb push su /system/xbin/su
adb shell "chown 0.0 /system/xbin/su;chmod 06755 /system/xbin/su;sync;mount -o remount,ro /system"
adb install superuser.apk
exit
thanks for this.
I used parallels installed Windows 7 I could have drove home and grabbed my laptop but that would have been to easy lol.
But now my mom is happy to see Windows android and osx lion on a 2009 MacBook pro I was surprised how well it went I thought I was going to have driver issues or something would go wrong but it was like I was using a straight up Windows 7 laptop. If that program was available for ubuntu a lot if people would be happy campers ?
Sent from my LG-D800 using XDA Premium 4 mobile app
I thought it would be a nightmare as obviously lg doesn't provide USB drivers for Mac. Color me surprised Mac doesn't need drivers!
Although I'm still not rooted, but that's phone version related
Sent from my LG-F320L using XDA Premium 4 mobile app
back to stock
I am needing to flash this thing back to stock so I can take it to the Verizon Store for an exchange. All I really have is a Mac.... I'd really like to know how to flash it back to stock, unrooted. I have some experience, but please be very clear as I really don't want to mess up. Thanks in advance for anyone willing to help.
mjdupuis said:
WARNING! This is just what worked for me, and it's just the adb commands from thecubed's program. All credit goes to him, I didn't do any of this, just took the info from it.
Here's the thread: http://forum.xda-developers.com/showthread.php?t=2448887
Download it, unzip it, and then take a moment to go back and thank him if you didn't do that.
You are not actually using his program, just the files and commands. Everything is done using Terminal and the Finder. You must have ADB working, look elsewhere for instructions on setting that up.
The files used here are the Verizon versions of the files, which I used for my phone. They are also specific to the OTA'd Verizon software, "11A" so there are different files if you haven't installed the OTA. These commands are correct, but the files being pushed aren't all the same between different carrier models and do not work with any other carrier. All the right stuff for other carriers is contained in thecubed's program.
The bold sections are files you need to send over adb, you can manually enter the file pathway or drag the files from finder into terminal after the adb commands (and before you type the destinations).
One more warning; if this is your first time using adb or terminal, I don't recommend this as your first try. It's super easy to screw something up in terminal.
Your phone must have developer options enabled and usb debugging on. plug in your phone via usb and select "Internet" and then "Ethernet."
adb push ytiruces_1a_vzw /sdcard/ytiruces_1a
Unplug usb, disable USB debugging and then re-enable it. Plug USB back in.
adb shell "mount -o remount,rw /system"
adb push su /system/xbin/su
adb shell "chown 0.0 /system/xbin/su;chmod 06755 /system/xbin/su;sync;mount -o remount,ro /system"
adb install superuser.apk
exit
Click to expand...
Click to collapse
you wouldnt happen to know which files in there are for the tmobile g2 would you? im also trying to root on mac.
You'll have to look in the .bat file, it will show which file needs to be used for T-Mobile.
mjdupuis said:
WARNING! This is just what worked for me, and it's just the adb commands from thecubed's program. All credit goes to him, I didn't do any of this, just took the info from it.
Here's the thread: http://forum.xda-developers.com/showthread.php?t=2448887
Download it, unzip it, and then take a moment to go back and thank him if you didn't do that.
You are not actually using his program, just the files and commands. Everything is done using Terminal and the Finder. You must have ADB working, look elsewhere for instructions on setting that up.
The files used here are the Verizon versions of the files, which I used for my phone. They are also specific to the OTA'd Verizon software, "11A" so there are different files if you haven't installed the OTA. These commands are correct, but the files being pushed aren't all the same between different carrier models and do not work with any other carrier. All the right stuff for other carriers is contained in thecubed's program.
The bold sections are files you need to send over adb, you can manually enter the file pathway or drag the files from finder into terminal after the adb commands (and before you type the destinations).
One more warning; if this is your first time using adb or terminal, I don't recommend this as your first try. It's super easy to screw something up in terminal.
Your phone must have developer options enabled and usb debugging on. plug in your phone via usb and select "Internet" and then "Ethernet."
adb push ytiruces_1a_vzw /sdcard/ytiruces_1a
Unplug usb, disable USB debugging and then re-enable it. Plug USB back in.
adb shell "mount -o remount,rw /system"
adb push su /system/xbin/su
adb shell "chown 0.0 /system/xbin/su;chmod 06755 /system/xbin/su;sync;mount -o remount,ro /system"
adb install superuser.apk
exit
Click to expand...
Click to collapse
Haven't used adb before, but I'm no noob to rooting /flashing. I got adb installed and working on my computer now (running Ubuntu). After I launch adb in the terminal, then I just type these commands? (copy paste?)
You could only copy and paste if you have a Verizon g2 with the ota update, if it's any other version you'll be using different files than the ones I have used.
Yeah, I have the Verizon g2 and I guess it's got the ota... There are no pending updates right now
Two problems on mac
I'm getting two error messages. The first is a line 2 error on the g2 security. The second is 'operation not permitted' for a mount command. Anyone have any solutions?
elcapitano21 said:
I'm getting two error messages. The first is a line 2 error on the g2 security. The second is 'operation not permitted' for a mount command. Anyone have any solutions?
Click to expand...
Click to collapse
does anyone know how to fix the device offline error whenever i try in input the first command?
Bump
Sent from my VS980 4G using XDA Premium 4 mobile app
Hi all, I came across this root tutorial in a post from last year and was hoping to get some feedback on it. Risks involved? Potential for brick or boot loop? The tutorial uses supersu and I'm aware that it may now have security risks. This radio will never be online so it's not a concern. The tutorial was posted in a 8227L thread so it was supposedly done on this model but there wasn't much follow up.
According to AIDA64 my device specs are:
Model: alps 8227L demo
4x ARM Cortex A7 @ 1118mhz
32 bit ARMv7
CPU Revision: r0p3
1GB RAM
16GB ROM
Android Version: 6.0 Marshmallow
Kernel: 3.18.22
API Level 23
Android Security Patch Level: 2017-11-05
Build ID: YT9218_00002_V001
##############TUTORIAL###############
ROOT!
Root has to be done through ADB.
Attention! Incorrect actions can lead to a bootloop (endless loading) of the radio. To fix it, you will need a flashing and, as a result, a complete erase of all data; so, proceed at your own risk!
Requirements: P.C. (I prefer my laptop) and your head unit must be able to connect to the same wifi as the PC (I used my mobile phone's hotspot for wifi and connected my laptop and headunit to it)
Download adb (platform-tools-latest-windows.zip) from here
Download SuperSU apk and SuperSU zip files from here
Extract platform-tools-latest-windows.zip to C:\adb
Extract SR5-SuperSU-v2.82-SR5-20171001224502.zip.
Open the armv7 folder
Select all files in the armv7 folder and right click, Copy
Paste the files into the c:\adb directory
In the same folder, create a notepad file and paste in the following text:
Code:
service rooting /system/bin/su --daemon
class main
priority 10
user root
oneshot
seclabel ubject_r:system_file:s0
now save this file as "rooting.rc"
Open command prompt on your PC as administrator (in windows 10, in the "type here search" type "cmd")
type in "cd c:\adb"
Move over to the headunit and download "What is my IP address" from the google play store.
open up what is my ip address and write down your headunit's ip address (should be something like 192.168.3.4)
Go back to the play store and download "Terminal Emulator for Android"
open Terminal Emulator for Android
Go back to your pc and in the command prompt window, execute the following code:
(my adb worked without additional commands, immediately after opening the emulator)
(any sentences to the right of // means NOTE; so, don’t copy that part)
Code:
adb connect <IP devices>: 5555 // For example adb connect 192.168.3.4/10555
adb shell // Go to Shell
su @#zxcvbnmasdfghjklqwertyuiop1234567890,. // In the shell, we switch to superuser mode using the password
remount // Remount so that all further commands are immediately executed from the superuser
adb shell setenforce 0 // Further on the instruction manual from the articles
adb push su /system/xbin/su
adb push su /system/bin/su
adb shell chmod 06755 /system/bin/su
adb shell chmod 06755 /system/xbin/su
adb shell /system/bin/su --install
adb push rooting.rc /system/etc/init/rooting.rc
get back on you headunit,
get the SuperSU apk we downloaded from before and get it installed onto your headunit. (I put mine onto my google drive and downloaded and installed from there)
open it and look for a GRANT command.
Press GRANT to allow superuser access.
NOTE: If you get a request to update the binary file, click reject
go back to your pc. we are going to Reboot your headunit with the reset command
Code:
adb shell reboot
The radio will reboot twice, don't panic.
check with root checker
You should be ROOTED!
EDIT: here is a video:
the text file should contain:
Code:
service rooting /system/bin/su --daemon
class main
priority 10
user root
oneshot
seclabel u:object_r:system_file:s0
nismo2013 said:
the text file should contain:
Code:
service rooting /system/bin/su --daemon
class main
priority 10
user root
oneshot
seclabel u:object_r:system_file:s0
Click to expand...
Click to collapse
it works..no need to find the ip address or use a terminal emulator..you do have to add a extra line of code..
but since your at Android 6, just use KingRoot..much easier
codecxbox said:
but since your at Android 6, just use KingRoot..much easier
Click to expand...
Click to collapse
Thanks for the reply. I used kingroot on an old samsung galaxy s4 I had years ago and it made my device run like garbage. I would prefer the adb method above. In your other comment you sad no ip or terminal emulator is needed. Then you said I do need an extra line of code. Do you mean an extraline of code in order to skip the ip and terminal em? Or the tutorial above needs one more line of code as it is?
nismo2013 said:
Thanks for the reply. I used kingroot on an old samsung galaxy s4 I had years ago and it made my device run like garbage. I would prefer the adb method above. In your other comment you sad no ip or terminal emulator is needed. Then you said I do need an extra line of code. Do you mean an extraline of code in order to skip the ip and terminal em? Or the tutorial above needs one more line of code as it is?
Click to expand...
Click to collapse
you skip the ip add line and the use of the terminal emulator..
you should use these extra lines:
adb push su /vendor/bin
chmod 0677 su /vendor/bin
btw, you have to enable OEM Bootloader unlock at the usb debugging menu..press 4 times the build number and usb debugging will be enabled..after that, connect your cable to your pc, turn off and on your head unit, you should be able to adb devices with a serial number...
I recommend you to do each step copypasting at the adb prompt and pressing enter at each one..as soon you get adb superuser enabled, youre good to go...DONT UPDATE SUPERSU IF IT TELLSVYOU THAT THE BINARY NEEDS TO BE UPDATED!
your build 9816 Im never did that one, but probably you wont need to [email protected], cuz these builds 9*** already have su built in, but there not system wide..test # at adb shell before anything, and then push your su to all partitions..
codecxbox said:
you skip the ip add line and the use of the terminal emulator..
you should use these extra lines:
adb push su /vendor/bin
chmod 0677 su /vendor/bin
btw, you have to enable OEM Bootloader unlock at the usb debugging menu..press 4 times the build number and usb debugging will be enabled..after that, connect your cable to your pc, turn off and on your head unit, you should be able to adb devices with a serial number...
I recommend you to do each step copypasting at the adb prompt and pressing enter at each one..as soon you get adb superuser enabled, youre good to go...DONT UPDATE SUPERSU IF IT TELLSVYOU THAT THE BINARY NEEDS TO BE UPDATED!
Click to expand...
Click to collapse
Thanks for the additional info. I'm still a beginner when it comes to rooting and have never done adb. The reason I wanted to use the network method is the head unit is installed in my car and I only have a desktop pc. I could borrow a laptop but its not readily available. I'd also have to buy a M to M usb cable since the otg usb on the radio is full size.
One of the first things I did was enable developer options and unlock the oem bootloader. But thanks for the heads up! I also read to not undate the super su binary. Random question.. but can magisk manager be installed on top of supersu? On magiskroot.net in the install info it says it can hide supersu root.
Can you please do an edit to the lines I enter into command prompt so I'm sure I get it right? I entered the actual ip address of the head unit. Can you please correct the formatting if it's wrong?I thought I want port 5555 but in the tut above he's using /10555. My current commands are:
Code:
adb connect 192.168.0.3/5555
adb shell
su @#zxcvbnmasdfghjklqwertyuiop1234567890,.
remount
adb shell setenforce 0
adb push su /system/xbin/su
adb push su /system/bin/su
adb shell chmod 06755 /system/bin/su
adb shell chmod 06755 /system/xbin/su
adb shell /system/bin/su --install
adb push rooting.rc /system/etc/init/rooting.rc
*NEXT INSTALL SUPERSU ON HEAD UNIT AND GRANT SUPER USER ACCESS - DO NOT UPDATE BINARY - FOLLOWED BY*
adb shell reboot
First, try to get your firmware, it may be full or update, doesnt matter..just in case your hu bricks..
Second, like I told you, check if superuser is already enabled..
If you only have a desktop pc, download adb lite, and decompress it to c:/adb
Get a usb to usb cable, or cut 2 usb data cables and twist or solder green to green, white to white, red to red and black to black..
I highly reccomend you to download these apks..
busybox.apk from sterikson
CX Explorer.apk or Mixplorer.apk (these you need to obtain system modifications)
Magisk doesnt play well with HU, cuz these android builds contains su watchdogs that turn off any apps that attempt to modify system files..if your goal is to install Viper4Android, then its going to be a battle but it can be done..
I just read that you have the hu installed to your car..in that case you will have to use ADB WIFI, and process everything from your phone..there is a problem, you might need to get a wifi router, cuz these hu units dont do direct wifi..in that case, you need the real ip address of your hu and adb connect hu ip address
If your goal is to install TRWP, its almost impossible..adb fastload doesnt work, its needs access to a keyboard, and as you happen to experience, these units wont recognize a usb keyboard..the way to install TRWP is forcing it through SP Tool, but you need a very specific TRWP image, most likely you never get one..but its not necessary to obtain root, no problem
Kingroot is sounding better by the minute haha. I may just try that and then use a task kill app to stop the ram sucking crap it tries loading into the backgound processes. If kingroot fails to gain access, I hope you don't mind but I'll be back with more questions on the adb wifi process. I already have a wifi router so I'm good there. The tut above does it over wifi and desktop with the files sitting in c:/adb like you said.
A few things I have discovered about this head unit which may apply to other chinese hu.. As I'm sure you know, the bluetooth stack is missing the HID profile and while I was able to pair a gamepad, I couldn't use it. The same went for bluetooth controlled led strips. The work around for a gamepad or keyboard/mouse on these HU is, get a device that is android compatible but uses a 2.4ghz dongle. I plugged it in, drivers loaded and it started working. Check out the Rii RK707 which is an all in one. $23 on gearbest. Gamepad took getting used to but I installed retroarch and the quake 3 arena port and both worked flawlessly with a gamepad. Dead Trigger also worked perfect. I just google searched for the files and then side loaded to the HU. I also put a 3 port usb splitter on the otg and everything works fine together; storage and gamepad.
I also figured out how to gain 8GB free space. If you go to settings, then storage/internal and scroll to other, I saw mine had 8GB of files. I tapped other and then browse and saw 3 folders called amap, amap8 and amapauto or something like that. These are included chinese gps map files. I deleted the folders and my device went up to having 9GB free space and it's been running fine. I was able to install a bunch of games to verify the free space is actually there. I have seen people trying to re-partition their devices and being happy to gain 2GB free. This is the way to do it. The HU also runs less laggy with the extra space.
For external storage like a usb thumbdrive, I think these units claim to supprt 32GB. I can veryify that up to 128GB works fine. I have a 128GB verbatim store n go and keep all of my mp3 and movie files there.
Hope you find some of this helpful.
codecxbox said:
First, try to get your firmware, it may be full or update, doesnt matter..just in case your hu bricks..
Second, like I told you, check if superuser is already enabled..
If you only have a desktop pc, download adb lite, and decompress it to c:/adb
Get a usb to usb cable, or cut 2 usb data cables and twist or solder green to green, white to white, red to red and black to black..
Click to expand...
Click to collapse
Good idea! I have some phone data cables with broken micro usb plugs I can cut and solder together.
How should I check if superuser is enabled? Can I install the supersu apk and try tapping GRANT? I just assumed I didn't have it because AIDA64 came back with "no root" when I ran it.
nismo2013 said:
Kingroot is sounding better by the minute haha. I may just try that and then use a task kill app to stop the ram sucking crap it tries loading into the backgound processes. If kingroot fails to gain access, I hope you don't mind but I'll be back with more questions on the adb wifi process. I already have a wifi router so I'm good there. The tut above does it over wifi and desktop with the files sitting in c:/adb like you said.
A few things I have discovered about this head unit which may apply to other chinese hu.. As I'm sure you know, the bluetooth stack is missing the HID profile and while I was able to pair a gamepad, I couldn't use it. The same went for bluetooth controlled led strips. The work around for a gamepad or keyboard/mouse on these HU is, get a device that is android compatible but uses a 2.4ghz dongle. I plugged it in, drivers loaded and it started working. Check out the Rii RK707 which is an all in one. $23 on gearbest. Gamepad took getting used to but I installed retroarch and the quake 3 arena port and both worked flawlessly with a gamepad. Dead Trigger also worked perfect. I just google searched for the files and then side loaded to the HU. I also put a 3 port usb splitter on the otg and everything works fine together; storage and gamepad.
I also figured out how to gain 8GB free space. If you go to settings, then storage/internal and scroll to other, I saw mine had 8GB of files. I tapped other and then browse and saw 3 folders called amap, amap8 and amapauto or something like that. These are included chinese gps map files. I deleted the folders and my device went up to having 9GB free space and it's been running fine. I was able to install a bunch of games to verify the free space is actually there. I have seen people trying to re-partition their devices and being happy to gain 2GB free. This is the way to do it. The HU also runs less laggy with the extra space.
For external storage like a usb thumbdrive, I think these units claim to supprt 32GB. I can veryify that up to 128GB works fine. I have a 128GB verbatim store n go and keep all of my mp3 and movie files there.
Hope you find some of this helpful.
Click to expand...
Click to collapse
Didnt know about the 2.4 dongle, thanks for the tip! I guess the dongle should translate a usb keyboard, as its supposed to be HID compliant..give it a try!
My HU didnt contain Chinese maps, but there was a load of Baidu crap I deleted, gained some 250mb..Happy with the results!
nismo2013 said:
Good idea! I have some phone data cables with broken micro usb plugs I can cut and solder together.
How should I check if superuser is enabled? Can I install the supersu apk and try tapping GRANT? I just assumed I didn't have it because AIDA64 came back with "no root" when I ran it.
Click to expand...
Click to collapse
SuperSU from Chainfire rides upon su, so if su is not properly working, SuperSu reports that theres no root..
a quick way to know if you could be a superuser is looking at the build.prop at /system..if it says ro.xxxx.userdebug instead of ro.xxxx.user, then chances are that su is installed..but you would need to give permissions to su to modify anything, thats why the chmod command..
get to c:\adb
type adb devices you should see devices and a serial number
type adb shell you should see a $ prompt, means you dont have superuser privileges
if you see a # prompt, then you do have superuser
this is my modified routine:
adb shell
su @#zxcvbnmasdfghjklqwertyuiop1234567890,.
remount
adb shell setenforce 0
adb push su /system/xbin/su
adb push su /system/bin/su
adb push su /vendor/bin/su
adb shell chmod 06755 /system/bin/su
adb shell chmod 06755 /system/xbin/su
adb shell chmod 06755 /vendor/bin/su
adb shell /system/bin/su --install
adb push rooting.rc /system/etc/init/rooting.rc
adb shell reboot system
Reading again, you said that BT devices work, like a dongle..but at the fastboot prompt, neither HID or BT drivers get loaded, its like a safe mode boot..only way to emulate that Key Up, Key Down is opening the HU and search for a test point on the board, usually its works as a Key Down
codecxbox said:
Didnt know about the 2.4 dongle, thanks for the tip! I guess the dongle should translate a usb keyboard, as its supposed to be HID compliant..give it a try!
My HU didnt contain Chinese maps, but there was a load of Baidu crap I deleted, gained some 250mb..Happy with the results!
Click to expand...
Click to collapse
The usb keyboard and mouse also worked! I did quite a bit of research on gamepad and keyboard options once I saw 2.4ghz would work and narrowed it down to these 2. The Rii RK707 which is an all in one. It has a led keyboard and mousepad on one side, and flip it over and its a gamepad. Standard LB and RB plus incremental L and R triggers. Works well but the shape takes time to adjust to. https://www.gearbest.com/keyboards/pp_3002324601977019.html
The other which I'm still waiting to arrive is the EasySMX ESM-9110. Visually it's a copy of an xbox one controller but has nice rgby leds in the ABXY buttons. It also has programmable underside buttons like a scuf. Great reviews. https://www.aliexpress.com/item/4000574045231.html
Each are under $30 if you don't mind waiting for shipping from china. Everything else was either cheap junk or over my budget.