Related
I don't feel like reformatting it to make it look good. You can find my post at AllDroid.org or by following this link http://alldroid.org/Default.aspx?tabid=40&g=posts&t=554 let me know if this helped you out. If you follow it to a tee you should have no problems at all.
This is what the link that they OP posted says.
This is a walk-through of how to root your Droid X using the Birdman's method. This walk-though is based off of Rainabba's walk-though but I am going to go into a little bit more detail on some sections to make it more understandable for newer people to rooting.
Before starting this walk-through make sure you do not have any Server Applications running on your computer. This includes stuff like PDAnet's or Some Bluetooth server apps. I noticed that PDAnet will close the adb.exe so you can't do anything. It has also come to my attention that bit-torrent and U-torrent applications may interfere with this process shut those down to.
First you will need to download 3 files, just put these files onto your desktop.
Download the DroidXRoot_v2.zip file from http://alldroid.org/default.aspx?g=posts&t=493
Download the ADBDriver_v3_Google.zip from http://alldroid.org/Defa...40&g=posts&t=495
Download the correct SDK for your OS (Operating System) from http://developer.android.com/sdk/index.html
Now that you have all 3 files downloaded and put onto your desktop its time to do stuff with them.
Extract the DroidXRoot_v2.zip to drive "c:" and just name it "DroidXRoot" so it will look like "c:/DroidXRoot"
Extract the SDK folder into your "DroidXRoot" it doesn't matter what the name of this folder is I used the preset name. This should not look like "c:/DroidXRoot/android-sdk-windows"
Open the "android-sdk-windows" folder and then open the "Tools" folder. From here copy ALL of the files from this folder.
Back out of the "Tools" folder and then out of the "android-sdk-windows" folder. You should now be in "c:/DroidXRoot" Paste those files in here.
Right now Bookmark this page, doing the ADB driver install requires a reboot. This way you can find this post instantly.
Time to install the ADB drivers. For these instructions go to http://alldroid.org/Defa...40&g=posts&t=495 and follow the instructions.
Assuming that the installation went through with no problems, its time to move on.
(Where you see the "Run" at type the command in the quotes ("") but with out the quotes. You should also be able to just copy and past whats inside the quotes if your lazy)
Go to the phone it should still be plugged in from doing the ADB driver install if not plug it in now.
Go to your phone: Home, Menu Button, Settings, Applications, Development: Make sure the "USB debugging" option is enabled/checked.
Hit your Home Button and pull down the Status Bar and click on USB connection: Make sure its set to PC MODE.
Open a command prompt (On Windows 7 and Vista: Start, then type cmd, Right click the cmd and make sure you run as admin. Linix just open the terminal and make sure your running Root through it. If you don't know how to get that good terminal root.)
Ok now that you have your command prompt open Run "cd c:\DroidXRoot"
Run "adb devices" you should see your device listed with a whole bunch of numbers. If you get the message "No devices found" you didn't copy and past the files correct from the tools folder to the "DroidXRoot" folder or you didn't install the driver right from the previous post. If you get the message "adb is not recognized as an internal or external command" you may still have a server file running, make sure there all exited since you rebooted while installing the "adb" drivers. Well if you see your device your doing great keep moving.
Run "adb push Superuser.apk /sdcard/Superuser.apk"
Run "adb push su /sdcard/su"
Run "adb push busybox /sdcard/busybox"
Run "adb push exploid /sqlite_stmt_journals/exploid" If you have any problems with the pushing as in getting the "access denied" response then you did not start in an admin or root and need to restart...
Run "adb shell"
Run "cd sqlite_stmt_journals"
Run "chmod 755 exploid"
Where doing great if you didn't have any problems. From here pick up your phone, and navigate to a screen where you can turn on/off your WiFi with a widget, turn your WiFi on. You will need to turn it off then back on instantly after the following command.
Run "./exploid" turn your Wifi off then turn it back on. Now follow the directions on your command prompt. When that completes you will be back at a shell prompt.
Run "rootshell" You will be prompted for a password enter "secretlol" and press Enter. You are now root but you still have more to do. (You will know that you are in root because your prompt will be a "#" instead of "$")
Run "cp /sdcard/Superuser.apk /system/app/Superuser.apk"
Run "cp /sdcard/su /system/bin/su"
Run "cp /sdcard/busybox /system/bin/busybox"
Run "chmod 4755 /system/bin/su"
Run "chmod 4755 /system/bin/busybox"
Run "rm /system/bin/rootshell"
Run "exit" to drop from root to a non-root user, you will still be logged into the phone.
Run "exit" again to drop back from your phone to your computer command prompt, you should be at "c:\DroidXRoot"
Now you need to confirm that you have established Root:
Run "adb shell"
Run "su" you should now see the "#" sign which indicates you are root)
WATCH YOUR DROID X SCREEN SO YOU CAN ALLOW SUPERUSER ROOT ACCESS!!!
Credits
Sebastian Kramer for this blog post - http://c-skills.blogspot...07/android-trickery.html
Birdman - for editing Sebastians work for the droidx
[mbm] - for answering birdmans many questions while root was tried (and failed xD)
Rainabba - for the original post located at http://alldroid.org/default.aspx?g=posts&t=493
The blog list
Birdman - @mrweeeedbirdman - http://stevenbird.info
Rainabba - @rainabba - http://rainabba.blogspot.com
Videos
Evidence of root: http://tiny.cc/DroidXRootProof
Video tutorial for root: http://tiny.cc/How2RootDroidXVideo
As is always the case with this sort of activity, you do this completely at your own risk. AllDroid, Rainabba, Birdman, and myself take NO responsibility for the outcome.
Edited 7/27/10
Added the section about shutting down the Bit-torrent and U-torrent applications - Thanks sanzy for finding that out.
Fixed a typo in line 21 - Thanks kdkinc fo noticing that.
Alright. Thank you very much.
I'm new to the DroidX. I'm trying to root my friend's phone.
Before updating to the OTA 2. 2 does the DroidX need to be "S-Off" as we Incredible users call it?
Or does this process cover that?
Thank you again.
Sent from my ADR6300 using XDA App
ksidirt said:
Alright. Thank you very much.
I'm new to the DroidX. I'm trying to root my friend's phone.
Before updating to the OTA 2. 2 does the DroidX need to be "S-Off" as we Incredible users call it?
Or does this process cover that?
Thank you again.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Simply put... S-Off does not work for anything other than HTC phones. So your Motorola Droid X will not need S-Off because it's not an option.
As of right now.. the leaked 2.2 is rootable but I don't know if the OTA that Verizon release for the DX will block the root or not.
To be safe, if you really want froyo now... use the leak, I have no problems with it, or you can wait until the OTA is released and confirmed rootable.
Your choice...To each his own
MrDanger said:
Simply put... S-Off does not work for anything other than HTC phones. So your Motorola Droid X will not need S-Off because it's not an option.
As of right now.. the leaked 2.2 is rootable but I don't know if the OTA that Verizon release for the DX will block the root or not.
To be safe, if you really want froyo now... use the leak, I have no problems with it, or you can wait until the OTA is released and confirmed rootable.
Your choice...To each his own
Click to expand...
Click to collapse
Awesome. Thank you.
I ended up using the following:
http://alldroid.org/default.aspx?g=posts&t=553
Worked first try.
If you're going to update to 2.2, you will need to run some additional commands prior to the update via adb or Root Explorer.
I've not had any issues with 2.2 - and I upgraded the day I got my X. No complaints here.
I'm also not really concerned with getting the official OTA -- chances are it (or a version of the update that is compatible with the leaked 2.2) will be found in the wild before long.
First off, I'm fairly new to the Droid X and this is my second android phone(the first was an Eris which should be kinda obvious). I am rooted but, for whatever reason, I cannot run the adb remount command from the prompt. I can run other commands like adb shell bootanimation which runs my boot animation and when i enter in adb shell it returns a $. $ does mean rooted, correct?
Also, when i try to run the sdk manager i get the "java not found in your your path" The weird thing is that it is in the path. So i'm getting frustrated now and I know it is probably something simple that i am overlooking.
If anyone can help out, I would greatly appreciate the help.
DroidEris1981 said:
First off, I'm fairly new to the Droid X and this is my second android phone(the first was an Eris which should be kinda obvious). I am rooted but, for whatever reason, I cannot run the adb remount command from the prompt. I can run other commands like adb shell bootanimation which runs my boot animation and when i enter in adb shell it returns a $. $ does mean rooted, correct?
Also, when i try to run the sdk manager i get the "java not found in your your path" The weird thing is that it is in the path. So i'm getting frustrated now and I know it is probably something simple that i am overlooking.
If anyone can help out, I would greatly appreciate the help.
Click to expand...
Click to collapse
$ does not mean rooted. from that prompt you can enter 'su' and you should get an '#' and then you are using root.
However, by default, the ADB daemon is not running with root privileges. Thus when you try to ADB remount it gets denied.
You need to run a 'Root Elevated' adb daemon. Or you can manually remount the /system partition from adb shell.
Why does the Droid X Recovery Bootstrap start on boot?
As mentioned above, it needs to log that your phone booted successfully and recovery mode is not necessary. It also replaces your "adb daemon" with one that has root permissions, allowing for easier usage of the adb command.
Click to expand...
Click to collapse
I know that if you install/run DroidX Bootstrapper (which installs the ClockworkMod Recovery) it also sets up a root elevated ADB daemon. You will need to reboot after installing before this takes effect.
Hi guys,
could anyone explain me please how to enable usb charging with Pershoot´s Kernel (boot-cm_2636.4_ux-oc-xtra-vfpv3-d16_fp-101811)?
I rly don´t get this:
adb shell echo 1 > /sys/class/power_supply/battery/force_usb_charging
Thank you very much.
Sure bud,
The script you posted is meant to be run in a command prompt using the tablet's ADB interface. To access this you need the Android SDK (that is the tool for app development) installed on your PC. You can look up how to do this all over the interweb.
To make your life easier though, download a terminal emulator app from the Market, there are plenty of free ones. Once you've done that open it and run the script as follows
su
echo 1 > /sys/class/power_supply/battery/force_usb_charging
The "su" command gives you root access just as "adb shell" would in command prompt.
The catch is the script is not persistent after reboot. So you will need to run it again if you reboot the tab. This doesn't really bother me cause I only use it for charging in the car and it takes like 30 seconds to type in the script.
Enjoy!
Thank you very much!
Now it´s working.
FillTheVoid said:
Sure bud,
The script you posted is meant to be run in a command prompt using the tablet's ADB interface. To access this you need the Android SDK (that is the tool for app development) installed on your PC. You can look up how to do this all over the interweb.
To make your life easier though, download a terminal emulator app from the Market, there are plenty of free ones. Once you've done that open it and run the script as follows
su
echo 1 > /sys/class/power_supply/battery/force_usb_charging
The "su" command gives you root access just as "adb shell" would in command prompt.
The catch is the script is not persistent after reboot. So you will need to run it again if you reboot the tab. This doesn't really bother me cause I only use it for charging in the car and it takes like 30 seconds to type in the script.
Enjoy!
Click to expand...
Click to collapse
how do you make it stick ?
I ask this question in another forum and the result was, it´s not possible (maybe wrong).
By the way, after I enable USB charge, my notebook can´t find my Tab anymore.
Mondfahrer said:
I ask this question in another forum and the result was, it´s not possible (maybe wrong).
By the way, after I enable USB charge, my notebook can´t find my Tab anymore.
Click to expand...
Click to collapse
I found a way to very easily get it running.
download terminal emulator.
Go to system preference of terminal emulator and there is an option to enter initial command to after you start terminal emulator.
so just type in:
su - root
echo 1 > /sys/class/power_supply/battery/force_usb_charging
Whenever you start teminal emulator, it will enable usb charging
I use this app to NTSF http://forum.xda-developers.com/showpost.php?p=13337600&postcount=6
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
I have found a way to remove ads on 5.1.1, it is exactly the same way as 5.0.1 except you NEED root for it to work.
Type in the following commands in a command prompt. Be sure USB debugging is on and it is securely connected to your computer. Although you do type reboot as the last command, the tablet turns off, just press the power button . This was successful on two of my tablets.
Code:
adb shell
su
At this point grant superuser access from the tablet
Code:
pm hide com.amazon.kindle.kso
exit
reboot
In theory this should work from a terminal emulator straight on your tablet but I have not tried it out
EDIT:
I should have explained the process better as some people are getting confused.
1. Make sure you have the correct drivers and USB debugging turned on your tablet.
2. Download this one click tool to gain root access if you have not done so already. Make sure to disable OTA updates from the tool as well (not necessary for removing ads but will be useful in the future).
3. Open a command window on your computer and type the commands above. If you have root you should get a
Code:
#
symbol after typing the su command.
Hello, it's my first post here so I apologize if the question is basic - I went thru all of the steps in other fourms last night and got Google Play to install just fine and even temporarily I appear to get the lock ads to remove but at best that doesn't seem to last past a reboot. After some further reading I found that unfortunately the kindle did a OTA update to 5.1.1 and that explains the reason I've been unable to permanently get rid of those lock ads.
I read your post, but I'm unclear on what I need to do to get root access (I mean without completely rooting the thing) I ran ADB from a windows command line, but I get a "not found" command when i type in SU..here's what it looks like (I'm putting my typing in bold, and the auto generated command line stuf in regular):
========================================
c:\amazon>adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found
127:[email protected]:/ $
=====================================
Since I've only done the automated scrip that is supposed to allow google play and remove ads, I didn't really expect to have root access, but I'm hoping there's some way I can get this to work without trying to fully root the kindle. If I have to go that route I might as well get rid of the entire Kindle OS... I don't actually want to do that, as I use amazon prime so a lot of the default junk that comes with this kindle is useful.
Big-T said:
Hello, it's my first post here so I apologize if the question is basic - I went thru all of the steps in other fourms last night and got Google Play to install just fine and even temporarily I appear to get the lock ads to remove but at best that doesn't seem to last past a reboot. After some further reading I found that unfortunately the kindle did a OTA update to 5.1.1 and that explains the reason I've been unable to permanently get rid of those lock ads.
I read your post, but I'm unclear on what I need to do to get root access (I mean without completely rooting the thing) I ran ADB from a windows command line, but I get a "not found" command when i type in SU..here's what it looks like (I'm putting my typing in bold, and the auto generated command line stuf in regular):
========================================
c:\amazon>adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found
127:[email protected]:/ $
=====================================
Since I've only done the automated scrip that is supposed to allow google play and remove ads, I didn't really expect to have root access, but I'm hoping there's some way I can get this to work without trying to fully root the kindle. If I have to go that route I might as well get rid of the entire Kindle OS... I don't actually want to do that, as I use amazon prime so a lot of the
default junk that comes with this kindle is useful.
Click to expand...
Click to collapse
Yeah it could have been better explained, they meant that process works if your tablet is rooted.
You won't get root commands to work in shell like that if it isn't rooted. Like it says the su file isn't there.
A lot changed yesterday with respect to 5.1.1 and root.
So you could use the temporary root found yesterday to gain access. Should be able to disable it from there. (First two code boxes there show the temp root access and the resulting prompt, the third lets you make it permanent). Though not sure why rooting it is tantamount to removing the entire OS tbh anyway.
http://forum.xda-developers.com/amazon-fire/orig-development/root-t3272362
Pond-life said:
Yeah it could have been better explained, they meant that process works if your tablet is rooted.
You won't get root commands to work in shell like that if it isn't rooted. Like it says the su file isn't there.
A lot changed yesterday with respect to 5.1.1 and root.
So you could use the temporary root found yesterday to gain access. Should be able to disable it from there. (First two code boxes there show the temp root access and the resulting prompt, the third lets you make it permanent). Though not sure why rooting it is tantamount to removing the entire OS tbh anyway.
http://forum.xda-developers.com/amazon-fire/orig-development/root-t3272362
Click to expand...
Click to collapse
Thank you! It appears I finally got the ads cleared permanently although I had a few hiccups along the way. I'm going to try to step-by-step this for anyone else that may have problem like I did (First andriod device, first time messing with one)
1) Got my kindle yesterday and it did an automatic over the air update to 5.1.1 - Found instructions for installing the google play store and removing ads in this excellent thread http://forum.xda-developers.com/amazon-fire/general/installing-google-framework-playstore-t3216122
2) Downloaded "Amazon-Fire-5th-Gen-Install-Play-Store.zip" file from rootjunkysdl.com but had some problems getting my device to recognize correctly. I found the only drivers to work on two seperate computers were from the amazon website https://developer.amazon.com/public/resources/development-tools/ide-tools/tech-docs/05-setting-up-your-kindle-fire-tablet-for-testing#Introduction
3) After I got the drivers to install I ran the "1-Install-Play-Store.bat" file from step #1. The batch file guided me thru everything and the Google Playstore worked just fine. At first I thought I got rid of the lock screen ads as well, but after my first reboot the ads came back.
4) This thread pointed out that with the new 5.1.1 updated you had to have root access enabled. I tried to do so, but the commands weren't working. The problem was, I was missing a critical step that wasn't explicitly stated in the other threads YOU MUST INSTALL THE ROOT_FIRE.ZIP and point your command prompt window to this extracted folder...even though the zip file in step#1 has an adb.exe it's missing other files to get you root acees
http://rootjunkysdl.com/?device=Amazon%20Fire%205th%20gen
5) After unpacking and running the commands as provided, the ads are gone. I'm attaching a link to a screenshot of my command window so folks can see what they should be typing in:
https://www.dropbox.com/s/icyyzr14limkosu/Capture.JPG?dl=0
Big-T said:
Thank you! It appears I finally got the ads cleared permanently although I had a few hiccups along the way. I'm going to try to step-by-step this for anyone else that may have problem like I did (First andriod device, first time messing with one)
1) Got my kindle yesterday and it did an automatic over the air update to 5.1.1 - Found instructions for installing the google play store and removing ads in this excellent thread http://forum.xda-developers.com/amazon-fire/general/installing-google-framework-playstore-t3216122
2) Downloaded "Amazon-Fire-5th-Gen-Install-Play-Store.zip" file from rootjunkysdl.com but had some problems getting my device to recognize correctly. I found the only drivers to work on two seperate computers were from the amazon website https://developer.amazon.com/public/resources/development-tools/ide-tools/tech-docs/05-setting-up-your-kindle-fire-tablet-for-testing#Introduction
3) After I got the drivers to install I ran the "1-Install-Play-Store.bat" file from step #1. The batch file guided me thru everything and the Google Playstore worked just fine. At first I thought I got rid of the lock screen ads as well, but after my first reboot the ads came back.
4) This thread pointed out that with the new 5.1.1 updated you had to have root access enabled. I tried to do so, but the commands weren't working. The problem was, I was missing a critical step that wasn't explicitly stated in the other threads YOU MUST INSTALL THE ROOT_FIRE.ZIP and point your command prompt window to this extracted folder...even though the zip file in step#1 has an adb.exe it's missing other files to get you root acees
http://rootjunkysdl.com/?device=Amazon%20Fire%205th%20gen
5) After unpacking and running the commands as provided, the ads are gone. I'm attaching a link to a screenshot of my command window so folks can see what they should be typing in:
https://www.dropbox.com/s/icyyzr14limkosu/Capture.JPG?dl=0
Click to expand...
Click to collapse
Think it might depend when you downloaded the Amazon-Fire-5th-Gen-Install-Play-Store.zip, the zip has been around for some time and he updated it several times last night and somewhat confusingly kept the same name for it and the batch file inside.
The current zip and a few other versions last night has the root riles in the "files" directory that the batch uses them from there. Even then the order of the commands isn't ideal I don't think as the block the ads one comes in the install google play one before the root install which it relies on it.
I think if adb shell pm hide com.amazon.kindle.kso was moved to the blocking 5.1.1 OTA section and updated the same way those OTA hides were to
adb shell su -c "pm disable com.amazon.kindle.kso"
so that section would be
adb shell su -c "pm disable com.amazon.otaverifier"
adb shell su -c "pm disable com.amazon.device.software.ota"
adb shell su -c "pm disable com.amazon.settings.systemupdates"
adb shell su -c "pm disable com.amazon.kindle.kso"
5? You know everything failed in that pic right?
Pond-life said:
5? You know everything failed in that pic right?
Click to expand...
Click to collapse
Yeah, lol! [laughing with not at] It looks like the commands are failing because he's already in su! Something weird happened at the line:
adb wait-for-device && adb shell
. . . and he went into su (#), so subsequent shell and su fail, but the "pm hide" works! But then the one "exit" takes him out, as though he actually was only in shell. This is really strange.
Worked perfectly! Thanks
I was having issues with the supertool and even another manual entry way of blocking ads, but this seems to have worked.
Thank you!
If you're rooted, why not use an app instead of doing this via adb.
S6 EDGE TMO
dEris said:
If you're rooted, why not use an app instead of doing this via adb.
S6 EDGE TMO
Click to expand...
Click to collapse
Amazon lockscreen ads are not the same as google ads. The lockscreen ads don't go away with ad blockers. That was the first thing I tried after root. Of course, someone could just make an app that runs this script specifically for this device but I find this way pretty simple
phonehunter59 said:
Amazon lockscreen ads are not the same as google ads. The lockscreen ads don't go away with ad blockers. That was the first thing I tried after root. Of course, someone could just make an app that runs this script specifically for this device but I find this way pretty simple
Click to expand...
Click to collapse
You can disable apps with app freezer apps in the play store. Therefore, instead of using adb to disable apps, use an app. App app app lol
S6 EDGE TMO