Related
I was messing around with the ONE-click-lag-fix thingy on this thread
http://forum.xda-developers.com/showthread.php?p=8353541#post8353541
someone posted a "fix"
""you can fix the jpk issue by doing this:
after the failure, reboot the phone.
then with root explorer delete the file linux.ex2 in folder /data/ext2 this will give you back the space
open terminal emulator on phone and type:
su
busybox mount -o remount,rw /system
press home button and reapply the lagfix.
wait...
profit!"
So I went into my phone in /data and found linux.ex2 (although it wasn't in /ext2 it was just in /data) and I deleted it
and used the terminal commands etc.
I reset my phone and it books into the logo then turns black and turns off
I don't have the 3 button recovery mode enabled... I have ADB and stuff though
WHAT do I do ?
Please oh please tell me I didn't brick my phone
Please tell me how to fix this and I will give you $50 or $100 paypal right away
If it is bricked, what do I do to go about getting it replaced ?
Try: adb reboot recovery
And try a factory reset
Otherwise, you can boot into download mode by: adb reboot download and flash via Odin.
kalpik said:
Try: adb reboot recovery
And try a factory reset
Otherwise, you can boot into download mode by: adb reboot download and flash via Odin.
Click to expand...
Click to collapse
Where do I get ADB again (im at work) is there a tutorial ?
btw if this works Ill need your paypal info
You can use mke2fs to re-create linux.ex2
Ex. mke2fs /data/linux.ex2
This could get you booted up again. Then you could uninstall/reinstall the lagfix.
frankencat said:
You can use mke2fs to re-create linux.ex2
Ex. mke2fs /data/linux.ex2
This could get you booted up again. Then you could uninstall/reinstall the lagfix.
Click to expand...
Click to collapse
What do you mean? can you please explain this further?
what's mke2fs ?
Funkadelick said:
Where do I get ADB again (im at work) is there a tutorial ?
btw if this works Ill need your paypal info
Click to expand...
Click to collapse
ADB tutorial: http://forum.xda-developers.com/showpost.php?p=7239659&postcount=3
WAIT!!!!!!!: Before you do anything else!!! Look for /sdcard/linux.ex2 and see if it exists. This should be a backup that can be restored. Copy this back to data and you should be good to go. Might take a while to copy but it should work.
frankencat said:
WAIT!!!!!!!: Before you do anything else!!! Look for /sdcard/linux.ex2 and see if it exists. This should be a backup that can be restored. Copy this back to data and you should be good to go. Might take a while to copy but it should work.
Click to expand...
Click to collapse
I'm fairly new -- this is the problem
What do you mean "look" for it ? I can't even open up my phone -- it goes black on the boot screen (i shouldn't have deleted linux.ex2)
So I would assume this would be done through ADB ? I'm downloading it now
frankencat said:
WAIT!!!!!!!: Before you do anything else!!! Look for /sdcard/linux.ex2 and see if it exists. This should be a backup that can be restored. Copy this back to data and you should be good to go. Might take a while to copy but it should work.
Click to expand...
Click to collapse
I would need to know the commands to type to "restore" this file basically once I get ADB running
and if it works, please PM me your paypal info
I downloaded the android development SDK -- but when I ran it i got this: "Failed to fetch URL http://dl-ssl.google.com/android/repository/repository.xml, reason: dl-ssl.google.com"
Is this b/c I'm at work ? (firewall)
do I need to connect in order to use ADB ?
You said you have ADB so do this...hook up your phone and fire up a command window on you pc.
type in "adb shell"
this should get you into adb shell (duh).
next type "su"
Now enter the following one at a time on order. The last line will reboot your phone.
/data/lagfixtemp/busybox rm -rf /data/data;
/data/lagfixtemp/busybox rm -rf /data/system;
/data/lagfixtemp/busybox rm -rf /data/dalvik-cache;
/data/lagfixtemp/busybox rm -rf /data/app;
/data/lagfixtemp/busybox rm -rf /data/app-private;
/data/lagfixtemp/busybox mv /data/bak/data /data/;
/data/lagfixtemp/busybox mv /data/bak/system /data/;
/data/lagfixtemp/busybox mv /data/bak/dalvik-cache /data/;
/data/lagfixtemp/busybox mv /data/bak/app/app-private /data/;
/data/lagfixtemp/busybox mv /data/bak/app /data/;
/data/lagfixtemp/busybox mv /system/bin/playlogosnow /system/bin/playlogos1;
reboot
Funkadelick said:
I downloaded the android development SDK -- but when I ran it i got this: "Failed to fetch URL http://dl-ssl.google.com/android/repository/repository.xml, reason: dl-ssl.google.com"
Is this b/c I'm at work ? (firewall)
do I need to connect in order to use ADB ?
Click to expand...
Click to collapse
You don't need to run anything. Just download it and unzip the files to a directory on your computer like C:\android-sdk-windows
Then add the tools directory to you PATH setting
C:\android-sdk-windows\tools
Let me know if you don;t know how to do that and I will walk you through it.
frankencat said:
You said you have ADB so do this...hook up your phone and fire up a command window on you pc.
type in "adb shell"
this should get you into adb shell (duh).
next type "su"
Now enter the following one at a time on order. The last line will reboot your phone.
/data/lagfixtemp/busybox rm -rf /data/data;
/data/lagfixtemp/busybox rm -rf /data/system;
/data/lagfixtemp/busybox rm -rf /data/dalvik-cache;
/data/lagfixtemp/busybox rm -rf /data/app;
/data/lagfixtemp/busybox rm -rf /data/app-private;
/data/lagfixtemp/busybox mv /data/bak/data /data/;
/data/lagfixtemp/busybox mv /data/bak/system /data/;
/data/lagfixtemp/busybox mv /data/bak/dalvik-cache /data/;
/data/lagfixtemp/busybox mv /data/bak/app/app-private /data/;
/data/lagfixtemp/busybox mv /data/bak/app /data/;
/data/lagfixtemp/busybox mv /system/bin/playlogosnow /system/bin/playlogos1;
reboot
Click to expand...
Click to collapse
Jesus christ how did you know all this stuff ? gonna try it out ill let you know how it goes -- brb
frankencat said:
You don't need to run anything. Just download it and unzip the files to a directory on your computer like C:\android-sdk-windows
Then add the tools directory to you PATH setting
C:\android-sdk-windows\tools
Let me know if you don;t know how to do that and I will walk you through it.
Click to expand...
Click to collapse
I got adb up and running
but please explain (in detail) your solution you mentioned in the previous page --
"You can use mke2fs to re-create linux.ex2
Ex. mke2fs /data/linux.ex2
This could get you booted up again. Then you could uninstall/reinstall the lagfix."
Please in details explain what you mean and show commands. Thanks
frankencat said:
You said you have ADB so do this...hook up your phone and fire up a command window on you pc.
type in "adb shell"
this should get you into adb shell (duh).
next type "su"
Now enter the following one at a time on order. The last line will reboot your phone.
/data/lagfixtemp/busybox rm -rf /data/data;
/data/lagfixtemp/busybox rm -rf /data/system;
/data/lagfixtemp/busybox rm -rf /data/dalvik-cache;
/data/lagfixtemp/busybox rm -rf /data/app;
/data/lagfixtemp/busybox rm -rf /data/app-private;
/data/lagfixtemp/busybox mv /data/bak/data /data/;
/data/lagfixtemp/busybox mv /data/bak/system /data/;
/data/lagfixtemp/busybox mv /data/bak/dalvik-cache /data/;
/data/lagfixtemp/busybox mv /data/bak/app/app-private /data/;
/data/lagfixtemp/busybox mv /data/bak/app /data/;
/data/lagfixtemp/busybox mv /system/bin/playlogosnow /system/bin/playlogos1;
reboot
Click to expand...
Click to collapse
when I type adb shell I get
error: device not found
am I doing something wrong ?
I rebooted my phone (galaxy S logo / start up screen) then it goes black as usual -- then I connected the cable and ran ADB from CMD.exe and typed ADB shell and got that error
Add C:\android-sdk-windows\tools to you computer's PATH...
- Open System Properties by right-clicking on My Computer
- Click on Advanced tab
- Click on Environment Variables
- Find PATH in System Varibles (bottom window) and open it for editing by either double-clicking or selecting it and clickin Edit button
- Scroll all the way to the end of the PATH string and enter a semi-colon ; at the end
- Paste the path to the sdk tools directory right after the semi-colon (C:\android-sdk-windows\tools)
- Click OK, OK, OK all the way out.
Now type "PATH" (without the quotes) in the command window and you should see the new path in the window. If not then close the window and open a new one. The tools dir should now be in the path and you are ready to use ADB.
You probably do not have have USB debugging enabled. Do you know if you eneabled that before or not? Also, did you make an nandroid backup before you started this?
And yes, it is because of Jesus Christ that I know this stuff.
<><
frankencat said:
Add C:\android-sdk-windows\tools to you computer's PATH...
- Open System Properties by right-clicking on My Computer
- Click on Advanced tab
- Click on Environment Variables
- Find PATH in System Varibles (bottom window) and open it for editing by either double-clicking or selecting it and clickin Edit button
- Scroll all the way to the end of the PATH string and enter a semi-colon ; at the end
- Paste the path to the sdk tools directory right after the semi-colon (C:\android-sdk-windows\tools)
- Click OK, OK, OK all the way out.
Now type "PATH" (without the quotes) in the command window and you should see the new path in the window. If not then close the window and open a new one. The tools dir should now be in the path and you are ready to use ADB.
Click to expand...
Click to collapse
I did all of this - i type in PATH and I see the new path etc.
But when i type adb shell it still says "device not found"
frankencat said:
You probably do not have have USB debugging enabled. Do you know if you eneabled that before or not? Also, did you make an nandroid backup before you started this?
And yes, it is because of Jesus Christ that I know this stuff.
<><
Click to expand...
Click to collapse
I don't think I enabled it -- as this happened spontaneously -- is there any way to fix this ? or am I seriously screwed ?
Not screwed, there is always a way.
Try this, pull your battery to power down your phone and then put the battery back in but DONT power it back up.
Now you have to do this all at the same time...hold down the up and down volume buttons and press down the power button. Hold all three buttons until you see the black Vibrant screen. KEEP HOLDING the up and down volume buttons until you see the yellow diags screen and then the green recovery screen.
Using the up/down volume keys to move, select "Reinstall Packages" and press the power button to select.
Tell me what you see...
I have a brand new ATT Captive.
I have it rooted.
I am on a MAC.
I am looking for a solution to allow me to sideload no market apps.
First person to post a method that will allow me to complete this will get $50 paypal as soon as I get this completed.
I have tried every solution on this board and spent 3 days trying to do this. Nothing has worked.
I begging someone to please find and post me a solution. I guarantee that I will pay to the first solution to make this possible.
Please help me out.
Don't pay people for it, there's threads all over for how to do it. This is copied from one of those threads.
"Method 2: with Root Explorer
(courtesy of kirbo20)
This is a pretty easy process. I went in to Root Explorer - dbdata - databases - com.android.providers.settings, copied settings.db to my sd card, edited it on my pc with a db editor changed 0 to a 1 next to non market apps. Copied it back to the original directory, rebooted and installed a non market app.
(added by gotfolk)
again using FF plug in..
Click Secure on the left pane
click on install_non_market_apps
click edit
number 3 states value click there and type in 1. hit ok
(/gotfolk)
Please use caution. If you want to make sure the db save properly open it on your sd card before you copy and replace the original. It should open up as a readable table. If it opens up in a txt editor its corrupt. This permanently enables non market apps. You can not toggle it on and off.
( This is a sqlite3 database file, you can find many GUI editors that will be able to handle the editing, including a FF plugin. Search "SQLite" )"
And if you don't want to use root explorer - Use the Android SDK on your mac - it is free.
You have to do your work in the terminal, but it is easy using the ADB Shell to get the file to your SD card, move it to your mac, use Firefox and SQLite manager to change the one value, put the file back, change permissions and you are done.
Most of us are not looking for $50 - just looking for people to use search and give things a try before creating a new post.
I think you can spend $4 very well on Root explorer and enable sideloading apps. And save $46.
2) Downloaded Root Explorer and SQLite Editor. Both of these are paid apps but look like they are worth owning. For instance, you can also use Root Explorer to rename and disable the AT&T bloatware, as an alternative to this method.
3) Using Root Explorer, mount the filesystem R/W and copy /dbdata/databases/com.android.providers.settings/settings.db to /sdcard/settings.db
4) Open /sdcard/settings.db in SQLite Editor
5) Open the 'secure' table
6) Long-hold on record 6, "install_non_market_apps" and select "Edit Record"
7) Change the value from 0 to 1 and save
8) Back in Root Explorer, copy /sdcard/settings.db back to /dbdata/databases/com.android.providers.settings/settings.db
9) I don't remember if I had to reboot or not, but you may as well.
Click to expand...
Click to collapse
Edit: Couldn't find the video with these intructions. Anyways you can download SQLite manager add-on on firefox, open firefox, go to tools->sqlite manager. Have the copied settings.db on your desktop, then open it up with the firefox SQLite manager(just to save you some more money). Once you're there, open up settings.db, go to secure on the left side, and then go to "browse and search" on the menu bar. Right click and edit "install_non_market_apps" and change the value from 0 to 1 like the instruction above. Then do steps 8 and 9. And you do have to reboot.
Sorry if it was confusing lol
doesnt the android central sideloading wonder work in mac?
puttingg said:
I have a brand new ATT Captive.
I have it rooted.
I am on a MAC.
I am looking for a solution to allow me to sideload no market apps.
First person to post a method that will allow me to complete this will get $50 paypal as soon as I get this completed.
I have tried every solution on this board and spent 3 days trying to do this. Nothing has worked.
I begging someone to please find and post me a solution. I guarantee that I will pay to the first solution to make this possible.
Please help me out.
Click to expand...
Click to collapse
max_warheads said:
(additional CHOWN notes added below. If you are getting "chown: unknown user/group system:system" read them!
Ok, we do have a WHOLE other thread that was made a sticky already, but you need to read the WHOLE thing to get all the properly interesting parts. I'll make sure I keep this OP up to date.
The following methods enable side loading and installing of apps onto the captivate, without the need of a program on a computer attached via the SDK. There are multiple methods, and for the most part, these methods that have worked flawlessly for many users here on this forum. We're just collecting them all in one post for speed and clarity.
Methods that assist in loading applications, without modification to the settings (a.k.a still need a computer attached) can be found at the collective wiki, http://samsungcaptivate.wikia.com/wiki/How_to_Sideload
ALL METHODS REQUIRE ROOT & BUSYBOX:
Root your phone, see http://forum.xda-developers.com/showthread.php?t=725555
Busybox : http://www.appbrain.com/app/stericson.busybox
Please, save a clean, un-altered backup copy of this file. To be safe. Rarely does corruption occur, but if it does, it won't be good.
Method 1: From Win7x64, Samsung Drivers, Android SDK installed.
This method uses the tools you already have at hand, as part of the SDK. All instances in code blocks are run inside of the command prompt. You will need to know where you installed your SDK, and the tools directory therein.
Once rooted, go install BusyBox installer from the App Market/AppBrain etc and run it. It will download and install the latest version for you.
From my Win7x64, with USB Debugging ON. Ensure that you phone is UNLOCKED as it the SU app will ask for permission for 'UNKOWN' in the following command.
Connect to PC, and Eject/Safely Remove the SD card, and "Turn off USB Storage" on the phone.
open command prompt, follow along:
Code:
> c:
> cd \android\tools
> adb shell
$ su
# cp /dbdata/databases/com.android.providers.settings/settings.db /sdcard/settings.db
# exit
$ exit
mount the SD cards to the pc,
"USB Connected select to... ", Mount
mine mounted as H:
Code:
> copy H:\settings.db settings.db
> sqlite3 settings.db
~> update secure set value="1" where name="install_non_market_apps";
1 row updated
~> .quit
> copy settings.db H:\settings.db
Eject the drive, safely remove, etc.
"Turn off USB storage" etc, to mount it back to the phone
Code:
> adb shell
$ su
# cp /sdcard/settings.db /dbdata/databases/com.android.providers.settings/settings.db
# chmod 660 /dbdata/databases/com.android.providers.settings/settings.db
# chown system.system /dbdata/databases/com.android.providers.settings/settings.db
# exit
$ exit
> adb reboot
Bam. Done.
Method 2: with Root Explorer
(courtesy of kirbo20)
This is a pretty easy process. I went in to Root Explorer - dbdata - databases - com.android.providers.settings, copied settings.db to my sd card, edited it on my pc with a db editor changed 0 to a 1 next to non market apps. Copied it back to the original directory, rebooted and installed a non market app.
(added by gotfolk)
again using FF plug in..
Click Secure on the left pane
click on install_non_market_apps
click edit
number 3 states value click there and type in 1. hit ok
(/gotfolk)
Please use caution. If you want to make sure the db save properly open it on your sd card before you copy and replace the original. It should open up as a readable table. If it opens up in a txt editor its corrupt. This permanently enables non market apps. You can not toggle it on and off.
( This is a sqlite3 database file, you can find many GUI editors that will be able to handle the editing, including a FF plugin. Search "SQLite" )
Method 3: with Root Explorer & Sqlite Editor & Terminal Emulator
(courtesy of ice3186)
- Open Root Explorer
- Browse to /dbdata/databases/com.android.providers.settings/
- copy settings.db to the root of your sd card ( /sdcard/ )
- Click on the newly copied settings.db in /sdcard/, with SQLite Editor installed, you can open and edit it here.
- Select the "secure" table, and update the value of 'install_nonmarket_apps' from 0 to 1, and save.
- close out of SQLite editor
- copy the modified file ( /sdcard/settings.db ), and browse back to /dbdata/databases/com.android.providers.settings/ and paste
- confirm the overwrite if asked and then open again to confirm it's been changed.
- open Terminal Emulator
Code:
$ su
# chmod 660 /dbdata/databases/com.android.providers.settings/settings.db
# chown system.system /dbdata/databases/com.android.providers.settings/settings.db
# reboot
- reboot phone.
No PC, no Mac, no drivers, no SDK. Viola.
Method 4: Mac & Android SDK
You will see "[sdcard]" through this method...I don't own a Mac so I'm guessing a bit.
This method uses the tools you already have at hand, as part of the SDK. All instances in code blocks are run inside of the Terminal. You will need to know where you installed your SDK, and the tools directory therein.
Once rooted, go install BusyBox installer from the App Market/AppDroid etc and run it. It will download and install the latest version for you.
From a Max OS X, with USB Debugging ON. Ensure that you phone is UNLOCKED as it the SU app will ask for permission for 'UNKOWN' in the following command.
Connect to Mac, and Eject/Safely Remove the SD card, and "Turn off USB Storage" on the phone.
open Terminal, follow along:
Code:
> cd /android/tools
> ./adb shell
$ su
# cp /dbdata/databases/com.android.providers.settings/settings.db /sdcard/settings.db
# exit
$ exit
mount the SD cards to the Mac,
"USB Connected select to... ", Mount
mine mounted as [sdcard]
Code:
> cp [sdcard]/settings.db settings.db
> ./sqlite3 settings.db
~> update secure set value="1" where name="install_non_market_apps";
1 row updated
~> .quit
> cp settings.db [sdcard]/settings.db
Eject the drive, safely remove, etc.
"Turn off USB storage" etc, to mount it back to the phone
Code:
> ./adb shell
$ su
# cp /sdcard/settings.db /dbdata/databases/com.android.providers.settings/settings.db
# chmod 660 /dbdata/databases/com.android.providers.settings/settings.db
# chown system.system /dbdata/databases/com.android.providers.settings/settings.db
# exit
$ exit
> ./adb reboot
Method 5: Android SDK only
Of course, this also requires root and BusyBox.
From the android sdk tools folder in a command prompt:
note: all linux/mac should use './adb' in place of just 'adb', and place quotes on the echo statement between echo and |
Code:
adb shell
su
chmod 666 /dbdata/databases/com.android.providers.settings/settings.db
exit
exit
adb pull /dbdata/databases/com.android.providers.settings/settings.db settings.db
echo update secure set value = 1 where name = 'install_non_market_apps';|sqlite3 settings.db
adb push settings.db /dbdata/databases/com.android.providers.settings/settings.db
adb shell
su
chmod 660 /dbdata/databases/com.android.providers.settings/settings.db
chown system.system /dbdata/databases/com.android.providers.settings/settings.db
reboot
NOTICE
You must chown the settings.db file and reboot once it is back in its original location. If you do not, you will not be able to alter settings such as WiFi,GPS, default Ringtones, etc. It's also highly likely that you may wish to chmod to 660 (-rw-rw---), so I've tacked that in here and above.
Code:
> adb shell
$ su
# chmod 660 /dbdata/databases/com.android.providers.settings/settings.db
# chown system.system /dbdata/databases/com.android.providers.settings/settings.db
# exit
$ exit
> adb reboot
Chown Note
In the event that you are getting "chown: unknown user/group system:system" please try 1000.1000 as this has been reported to work on several of the samfirmware-released roms that fail with this message.
Absolutely do not use someone else's settings.db unless you specifially make it a point replace android_id with your android_id!
[
Sent from my AOSP Captivate
Click to expand...
Click to collapse
How to install ubuntu on the Droid 4
Note to mods: this thread is a branch off of this thread
Huge thanks to zacthespack for creating the ubuntu installer app and original boot script and to zeroktal for modifying the script to work on the D4 and helping me get it working on my device.
I decided to take my experience in setting this up and put it into a how-to so that others could enjoy the experience of having ubuntu on the Droid 4. If zackthespac or zeroktal have any problems with me making and putting this guide up, please let me know and I will remove it.
Knowledge Required:
working knowledge of command line
working knowledge of vi
OR the ability to learn how to use both
Tools Required:
A rooted Motorola Droid 4
BusyBox (Android Market)
Terminal Emulator (Android Market)
Android VNC Viewer (Android Market)
Ubuntu Installer App (Android Market)
zeroktal's ubuntud4.zip file (attached to this post and mediafire)
Vi Cheat Sheet (lagmonster.org)
Step by Step:
Install BusyBox, Terminal, and Android VNC Viewer
Install and run Ubunutu Installer App
Follow the on-screen instructions and click next
Download either the Small or Large image to your phone, (use zeroktal's ubuntud4.zip file instead of the boot script provided in the guide) after the image downloads (will take a while because the file is HUGE) click next
For this screen, the instructions differ from the app.
1. With your D4 plugged into your PC in USB Mass Storage, create a directory (folder) called ubuntu in the EXTERNAL sdcard's root*
2. Extract the image you downloaded to that directory
3. Download and extract the attached .sh (ununtud4.zip) to that directory
4. Disconnect your phone from your PC
5. Open terminal and run the following commands:
su [ENTER]
mount -o remount,rw,exec,suid /dev/block/vold/179:1 /mnt/sdcard-ext [ENTER]
cd /mnt/sdcard-ext/ubuntu [ENTER]
sh ubuntud4.sh [ENTER]
960x540 [ENTER]**If you get an error message: ubuntud4.sh: 45: syntax error: end of file unexpected (expecting "then") see troubleshooting section below.killall -TERM Xtightvnc [ENTER]
vncserver :1 -geometry 960x540 [ENTER]**6. Open androidVNC app and enter the following settings:
Nickname: Anything you want
Password: ubuntu
Address: localhost
Port: 5901
Color Format: 24-bit color (4 bpp)
7. Hit connect
8. Hit your menu soft button and then set input mode to touchpad
9. You have ubuntu on your Droid 4!
To "shut down" ubuntu:
press the menu button, select disconnect in VNC
In terminal type this command 3 times (terminal will close itself when you are done):
exit [ENTER]
To "start up" ubuntu again:
Follow steps 5-8 above
Troubleshooting:
If you get the error message: ubuntud4.sh: 45: syntax error: end of file unexpected (expecting "then") you are about to have fun with vi at the command line.
Do the following from inside terminal:
su [ENTER]
cd /mnt/sdcard-ext/ubuntu [ENTER]
vi ubuntud4.sh [ENTER]If you see ^M or ^ at the end of any line (remember to scroll all the way to the right to see the end of long lines) remove it. once you do that, everything should work just fine. (See the Vi Cheat Sheet above for help with Vi)
Note: Vol Up + E is [ESC] by default in this terminal emulator
Notes:
* It does not have to be on the external SD, but if you put it on the internal SD you will have to modify things as needed-- if you dont know what needs to be changed, just put it on the external SD.
** Screen size can be whatever you want it to be, but 960x540 is the size of the D4 screen.
*** This is a fairly involved process... especially when it comes to editing the .sh file in vi things can get very frustrating and hard, but just take your time and you will get it. As always, doing anything with root access on your phone, especially on the command line has risks. I am not responsible if anything goes wrong with your phone... proceed at your own risk!
greekchampion04 said:
Notes:
* It does not have to be on the external SD, but if you put it on the internal SD you will have to modify things as needed-- if you dont know what needs to be changed, just put it on the external SD.
** Screen size can be whatever you want it to be, but 960x540 is the size of the D4 screen.
*** This is a fairly involved process... especially when it comes to editing the .sh file in vi things can get very frustrating and hard, but just take your time and you will get it. As always, doing anything with root access on your phone, especially on the command line has risks. I am not responsible if anything goes wrong with your phone... proceed at your own risk!
Click to expand...
Click to collapse
I actually got it up and running on my internal sdcard partition. Pretty much just have to modify the Mount remount command, and a few lines in the script.
Here's the original command
Code:
mount -o remount,rw,exec,suid /dev/block/vold/179:1 /mnt/sdcard-ext
And the modified one
Code:
mount -o remount,rw,exec,suid /dev/block/vold/179:57 /mnt/sdcard
Only things you have to change are the device location(179:57) and mount location(drop the -ext after sdcard)
Now, after that you also have to modify the script a bit. Just go through it, and anywhere that you see sdcard-ext, drop the -ext off the end.
thanks for putting that up for everybody! like i said, if you know what you are doing its not a hard swap to make.
Is anyone else getting just a gray screen when they remote in? What could be causing this?
i had that same problem at first... did you use zeroktal's ubuntud4.zip file? or did you use the ubuntu.sh file included in the app?
I used the sh file included. I did however fix the problem, when mounting at the start i confused vold with void. I did not get the file system mounted properly. This method does work!! however I am currently trying to get bash on my droid to replace sh as the shell. I've checked the forums but have not found anything yet about someone installing bash on the droid 4. With no way for nandroids I feel i should wait before I kill sh.
Sent from my DROID4 using XDA App
If you mod your init.sh in your root directory to the following, your vnc will work on startup without issue. It will also shutdown vnc on exit.
#!/bin/bash
#############################################
# Asks User to screen size and saves as REZ #
#############################################
#echo "Now enter the screen size you want in pixels (e.g. 800x480), followed by [ENTER]:"
#read REZ
##############################################
# Pick which desktop environment to use, this#
# is done by having a xstartup file for each #
# desktop, then renaming the one you want to #
# use to 'xstartup' before boot #
##############################################
echo "Please select which Desktop environment you want to use, type the number to select it then press [ENTER]"
echo "1 - LXDE"
echo "2 - Gnome"
echo "Make your Selection:"
read DESKTOP
if [ $DESKTOP == 1 ]
then
mv /root/.vnc/lxstartup /root/.vnc/xstartup
fi
if [ $DESKTOP == 2 ]
then
mv /root/.vnc/gxstartup /root/.vnc/xstartup
fi
###########################################
# Tidy up previous LXDE and DBUS sessions #
###########################################
rm /tmp/.X* > /dev/null 2>&1
rm /tmp/.X11-unix/X* > /dev/null 2>&1
rm /root/.vnc/localhost* > /dev/null 2>&1
rm /var/run/dbus/pid > /dev/null 2>&1
############################################################
# enable workaround for upstart dependent installs #
# in chroot'd environment. this allows certain packages #
# that use upstart start/stop to not fail on install. #
# this means they will have to be launched manually though #
############################################################
dpkg-divert --local --rename --add /sbin/initctl > /dev/null 2>&1
ln -s /bin/true /sbin/initctl > /dev/null 2>&1
###############################################
# start vnc server with given resolution and #
# DBUS server, (and optionally an SSH server) #
###############################################
dbus-daemon --system --fork > /dev/null 2>&1
/etc/init.d/ssh start
vncserver :1 -geometry 960x540
echo
echo "If you see the message 'New 'X' Desktop is localhost:1' then you are ready to VNC into your ubuntu OS.."
echo
echo "If VNC'ing from a different machine on the same network as the android device use the 1st address below:"
##########################################
# Output IP address of android device #
##########################################
ifconfig | grep "inet addr"
echo
echo "If using androidVNC, change the 'Color Format' setting to 24-bit colour, and once you've VNC'd in, change the 'input mode' to touchpad (in settings)"
echo
echo "To shut down the VNC server and exit the ubuntu environment, just enter 'exit' at this terminal - and WAIT for all shutdown routines to finish!"
echo
###############################################################
# Spawn and interactive shell - this effectively halts script #
# execution until the spawning shell is exited (i.e. you want #
# to shut down vncserver and exit the ubuntu environment) #
###############################################################
/bin/bash -i
#########################################
# Disable upstart workaround and #
# kill VNC server (and optionally SSH) #
# Rename used xstartup to its first file#
#########################################
killall -TERM Xtightvnc
/etc/init.d/ssh stop
Also save the follow lines between ### as remount.sh on your system partition. Then chmod 755 /system/remount.sh. Now you can just run run from a terminal /system/remount.sh and voila it remounts correctly and starts ubuntu(with the above fixes). Im still working on the unmounts.
####### for the internal sd card
mount -o remount,rw,exec,suid /dev/block/vold/179:57 /mnt/sdcard
/mnt/sdcard/ubuntu/ubuntu.sh
######
OR
####### for the external sd card
mount -o remount,rw,exec,suid /dev/block/vold/179:1 /mnt/sdcard-ext
/mnt/sdcard-ext/ubuntu/ubuntu.sh
#######
great stuff!
feel free
Feel free and take, modify, repost or edit anything I touch.
QUESTION:
After I delete all the ^M and ^ what do i do next? I try to hit the command ":x" to exit and save changes but it just creates another line. Also when I press VOL UP + E to escape nothing happens.
PhanTuhC said:
QUESTION:
After I delete all the ^M and ^ what do i do next? I try to hit the command ":x" to exit and save changes but it just creates another line. Also when I press VOL UP + E to escape nothing happens.
Click to expand...
Click to collapse
In vi, the command to save and exit is :wq (probably short for write and quit).
remember, read up on the vi quick-reference guide: http://www.lagmonster.org/docs/vi.html
OK I fixed it but now its not letting me connect with androidVNC. All the settings entered is correct but when I try to connect it says:
"VNC connection failed!" localhost/127.0.0.1:5901 - Connection refused"
ok, i've gone thru this a few times (slowly and deliberately) and must be missing something...the directions seem pretty straightforward! here's what i know...
busy/terminal/vnc are all installed
small 2.5gb image is unzipped in /sdcard-ext/ubuntu directory
the attached .sh file from page 1 is in the same directory
i removed all ^M using vi
but when I try sh ubuntud4.sh i get an error...
"mkdir failed for /data/local/mnt/ubun, No such file or directory"
(plus a few other errors)
should the directory be "ubun" or "ubuntu"? am I typing something incorrectly?
copy and paste new script
Copy and paste the new scripts I posted. They will fix your problem. Remember to use the remount script from /system/ the rest will work perfectly if you are root. I'll check back later on your progress.
Ok, well I started from scratch (deleted both .img and .sh files) and it's still not working.
I have all the apps installed (and yes rooted, SU works just fine)
I used Ubuntu Installer app to download the image zip (tried both the large and small img)
I downloaded the .sh file from the first post
The /sdcard-ext/ubuntu/ folder now has two files: "ubuntu.img" and "ubuntud4.sh"
All ^M characters have been removed from .sh file
Still no joy...
Ideas? What am I missing?
In terminal, I can set SU permissions and the mount/cd commands work just fine...it's the last sh command that spits out a bunch of errors about not being able to create/find the directories.
I'm going to format the sdcard and try again...any help is appreciated.
Update: Even after re-formatting the SD and following the steps exactly, no luck!
Did you remember to remount the sdcard with exec and suid permissions?
Andbuntu will work much better than this method. It works on every single phone with modification to the "environmental variables".
http://code.google.com/p/andbuntu/
Follow the directions in the script to make the process much easier than the first post.
instructions:
generate an image with rootstock on an ubuntu computer.
put it on /sdcard/ubuntu/ubuntu.img
run the script on your phone with "sh /path/to/script"
Here is the script. http://andbuntu.googlecode.com/svn/trunk/uboot
Also, run "firstRun" to make things like terminals work properly.
Adamoutler: That didnt work for me. The permissions were incorrect on the mounted partitions.
Sent from my DROID4 using XDA App
hi i have read numerous posts and tried many tutorials on here but cant seem to get anywhere with my kindle
fire i believe its a kindle fire 2nd gen as sytem version is 10.2.6
im using win xp on my pc and in device manager i have
kindle fire - android composite ADB interface
MTP has exclamation mark by it and wont load any drivers i have windows media player 11 installed.
it doesnt show up in my computer at all which i think is where the problem may lie
can anyone point me in the right direction on turning my kindle fire into an android device
and not amazon.... thanks in advance
inflicted_1999 said:
hi i have read numerous posts and tried many tutorials on here but cant seem to get anywhere with my kindle
fire i believe its a kindle fire 2nd gen as sytem version is 10.2.6
im using win xp on my pc and in device manager i have
kindle fire - android composite ADB interface
MTP has exclamation mark by it and wont load any drivers i have windows media player 11 installed.
it doesnt show up in my computer at all which i think is where the problem may lie
can anyone point me in the right direction on turning my kindle fire into an android device
and not amazon.... thanks in advance
Click to expand...
Click to collapse
Just got my 2nd gen in the mail today, started reading up on how to root 10.2.4, was feeling good about it, ready to get started and noticed that it was in the middle of upgrading to 10.2.6. guess I'll be following this thread, hope something comes along soon...
How To: Root the Kindle Fire 7" 2 with Windows - Version 10.2.6
inflicted_1999 said:
hi i have read numerous posts and tried many tutorials on here but cant seem to get anywhere with my kindle
fire i believe its a kindle fire 2nd gen as sytem version is 10.2.6
im using win xp on my pc and in device manager i have
kindle fire - android composite ADB interface
MTP has exclamation mark by it and wont load any drivers i have windows media player 11 installed.
it doesnt show up in my computer at all which i think is where the problem may lie
can anyone point me in the right direction on turning my kindle fire into an android device
and not amazon.... thanks in advance
Click to expand...
Click to collapse
inflicted_1999,
I am sorry to hear your frustrations around Rooting the Kindle Fire 2 version 10.2.6, this can be a bugger to Root. I have an idea that may help you. When you have a yellow triangle over MTP, this is a strong sign that the driver is not functional. When you have the combination of, one Android Composite ADB Interface with the yellow triangle over MTP, you have a driver failure. Having said this, none of the utilities will work until you have a functional driver. Just FYI Windows Media Player is not needed to get the Kindle to Root. Once you have successfully installed the driver Android Composite ADB Interface will change to Android ADB Interface and the MTP will change to Portable Devices > Kindle. You will also know the driver install was successful when you get a pop-up asking what to do with the Kindle Drive - like sync it with your MP3 collection.
If you already tried Part A for the driver, here are the key points:
Note: Windows 7 and Vista users, please perform this fix before Rooting: http://forum.xda-developers.com/show...php?p=36373627
A) The first step is to get the ADB Driver installed. If you already performed this step and verified communication to the Kindle.
Please open an Administrative CMD Prompt and enter:
Code:
Code:
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
Note: We have seen quite a few cases when the driver "fails to install". This message is normally erroneous and can usually be ignored. Plug in your Kindle, then look in the Windows Device Manager to see if the main driver installed.
Our friends at RevTV Created this video which outlines How to install ADB: How to Install ADB Video
The following ADB Driver was provided by Amazon and should install on most platforms (Windows XP, Vista, 7, and 8): Kindle Fire ADB drivers
Note: Due to intermittent issues with the USB Drivers, we offer two versions. First try Kindle Fire ADB drivers.exe if this
does not open ADB Communication try the new updated KindleDrivers.exe
This worked for me
inflicted_1999 said:
hi i have read numerous posts and tried many tutorials on here but cant seem to get anywhere with my kindle
fire i believe its a kindle fire 2nd gen as sytem version is 10.2.6
im using win xp on my pc and in device manager i have
kindle fire - android composite ADB interface
MTP has exclamation mark by it and wont load any drivers i have windows media player 11 installed.
it doesnt show up in my computer at all which i think is where the problem may lie
can anyone point me in the right direction on turning my kindle fire into an android device
and not amazon.... thanks in advance
Click to expand...
Click to collapse
I’m a n00b to this, but this worked for me. I had root than lost it because I didn’t disable auto update. The only way I could get root back is like this.
1. Use Prokennexusa steps to get your comp talking to your kindle, if you run win 7 or Vista make sure you heed the warning. Next find and download “Root_with_Restore_by_Bin4ry_v18” to your desktop and make two copies of it. The name of the folder does not matter you just need two copies of the program, I’ll explain in a minute. I don’t have a download link but it’s on the forum just search for it.
2. Pick one of the two “Root_with_Restore_by_Bin4ry_v18” to modify, you need to modify it to kick the kindle in the head and allow the original to work.open the folder of the one you want to modify and right click on the “RunMe.bat” and click edit. Highlight everything in it and delete. Then copy this in its place.
Code:
@echo off
COLOR 0A
echo ======================================================================
echo = This script will root your Android phone with adb restore function =
echo = Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
echo = Idea for Tablet S from Fi01_IS01 =
echo = (18.12.2012) v17 =
echo ======================================================================
echo.
:CHOICE
set nxt=0
set ric=0
echo Device type:
echo 1) Normal
echo 2) Special (for example: Sony Tablet S, Medion Lifetab)
echo.
echo x) Unroot
echo.
set /p type=Make a choice:
if %type% == 1 GOTO TEST
if %type% == 2 GOTO TABSMENU
if %type% == x GOTO UNROOT
echo.
echo Please Enter a valid number (1 to x)
echo.
GOTO CHOICE
:TEST
echo Checking if i should run in Normal Mode or special Sony Mode
echo Please connect your device with USB-Debugging enabled now
echo Waiting for device to shop up, if nothing happens please check if Windows ADB-drivers are installed correctly!
stuff\adb.exe wait-for-device
stuff\adb.exe pull /system/app/Backup-Restore.apk . > NUL
stuff\adb.exe pull /system/bin/ric . > NUL
if EXIST ric (set ric=1) else (echo .)
if EXIST Backup-Restore.apk (GOTO XPS) else (echo .)
GOTO OTHER
:UNROOT
set /p unr=Really (y/n) ?
IF %unr% == n GOTO CHOICE
stuff\adb.exe push stuff\busybox /sdcard/Documents/busybox
stuff\adb.exe shell "chmod 755 /sdcard/Documents/busybox"
stuff\adb.exe shell "su -c '/sdcard/Documents/busybox mount -o remount,rw /system'"
stuff\adb.exe shell "su -c 'rm /system/xbin/su'"
stuff\adb.exe shell "su -c 'rm /system/app/Superuser.apk'"
GOTO FINISH
:TABSMENU
echo.
echo Special mode:
echo 1) Root
echo 2) Rollback
set /p tabtype=Make a choice:
if %tabtype% == 1 GOTO TABS
if %tabtype% == 2 GOTO TABS_RB
:TABS
echo.
echo Tablet S mode enabled!
echo.
GOTO START
:XPS
echo.
echo Found Sony Backup-Restore.apk
echo LT26,LT22 etc. mode enabled!
echo.
del Backup-Restore.apk
if %ric% == 1 (del ric) else (echo .)
set NXT=1
GOTO START
:TABS_RB
echo.
echo Tablet S Roll Back
echo.
echo Please connect device with ADB-Debugging enabled now....
stuff\adb.exe wait-for-device
FOR /F "tokens=1 delims=" %%A in ('stuff\adb.exe shell "if [ -d /data/app- ]; then echo 1 ; else echo 0 ; fi"') do SET tabs_app=%%A
if %tabs_app% == 1 GOTO TABS_RB_1
if %tabs_app% == 0 GOTO TABS_RB_2
:TABS_RB_1
stuff\adb.exe shell "rm -r /data/data/com.android.settings/a/*"
stuff\adb.exe restore stuff/tabletS.ab
echo Please look at your device and click "Restore my data"
echo.
stuff\adb.exe shell "while [ ! -d /data/data/com.android.settings/a/file99 ] ; do echo 1; done" > NUL
echo 1st RESTORE OK, hit ENTER to continue.
pause
stuff\adb.exe shell "rm -r /data/data/com.android.settings/a"
stuff\adb.exe restore stuff/tabletS.ab
echo Please look at your device and click "Restore my data"
echo.
stuff\adb.exe shell "while : ; do ln -s /data /data/data/com.android.settings/a/file99; [ -f /data/file99 ] && exit; done" > NUL
stuff\adb.exe shell "rm -r /data/file99"
echo Achieved! hit ENTER to continue.
echo.
pause
stuff\adb.exe shell "mv /data/system /data/system3"
stuff\adb.exe shell "mv /data/system- /data/system"
stuff\adb.exe shell "mv /data/app /data/app3"
stuff\adb.exe shell "mv /data/app- /data/app"
echo "Roll back compelted."
GOTO FINISH
:TABS_RB_2
echo.
echo.
echo "Roll back failed. /data/app- not found."
echo.
echo.
GOTO FINISH
:eek:THER
echo.
echo Normal Mode enabled!
if %ric% == 1 (del ric) else (echo .)
echo.
:START
stuff\adb.exe wait-for-device
IF %type% == 2 GOTO TABTRICK
echo Pushing busybox....
stuff\adb.exe push stuff/busybox /sdcard/Documents/.
echo Pushing su binary ....
stuff\adb.exe push stuff/su /sdcard/Documents/.
echo Pushing Superuser app
stuff\adb.exe push stuff/Superuser.apk /sdcard/Documents/.
echo Making busybox runable ...
stuff\adb.exe shell chmod 755 /sdcard/Documents/busybox
if %ric% == 1 (stuff\adb.exe push stuff/ric /sdcard/Documents/ric) else (echo .)
IF %nxt% == 1 GOTO XPSTRICK
stuff\adb.exe restore stuff/fakebackup.ab
echo Please look at your device and click RESTORE!
echo If all is successful i will tell you, if not this shell will run forever.
echo Running ...
stuff\adb.exe shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done" > NUL
echo Successful, going to reboot your device in 10 seconds!
ping -n 10 127.0.0.1 > NUL
stuff\adb.exe reboot
echo Waiting for device to show up again....
ping -n 10 127.0.0.1 > NUL
stuff\adb.exe wait-for-device
GOTO NORMAL
:TABTRICK
stuff\adb.exe install -s stuff/Term.apk
stuff\adb.exe push stuff/busybox /sdcard/Documents/.
stuff\adb.exe push stuff/su /sdcard/Documents/.
stuff\adb.exe push stuff/Superuser.apk /sdcard/Documents/.
stuff\adb.exe push stuff/rootkittablet.tar.gz /sdcard/Documents/rootkittablet.tar.gz
stuff\adb.exe shell "chmod 755 /sdcard/Documents/busybox"
stuff\adb.exe shell "/sdcard/Documents/busybox tar -C /data/local/tmp -x -v -f /sdcard/Documents/rootkittablet.tar.gz"
stuff\adb.exe shell "chmod 644 /sdcard/Documents/VpnFaker.apk"
stuff\adb.exe shell "touch -t 1346025600 /sdcard/Documents/VpnFaker.apk"
stuff\adb.exe shell "chmod 755 /sdcard/Documents/_su"
stuff\adb.exe shell "chmod 755 /sdcard/Documents/su"
stuff\adb.exe shell "chmod 755 /sdcard/Documents/onload.sh"
stuff\adb.exe shell "chmod 755 /sdcard/Documents/onload2.sh"
stuff\adb.exe shell "rm -r /data/data/com.android.settings/a/*"
stuff\adb.exe restore stuff/tabletS.ab
echo Please look at your device and click "Restore my data"
echo.
stuff\adb.exe shell "while [ ! -d /data/data/com.android.settings/a/file99 ] ; do echo 1; done" > NUL
ping -n 3 127.0.0.1 > NUL
echo 1st RESTORE OK, hit ENTER to continue.
pause
stuff\adb.exe shell "rm -r /data/data/com.android.settings/a"
stuff\adb.exe restore stuff/tabletS.ab
echo Please look at your device and click "Restore my data"
echo.
stuff\adb.exe shell "while : ; do ln -s /data /data/data/com.android.settings/a/file99; [ -f /data/file99 ] && exit; done" > NUL
stuff\adb.exe shell "rm -r /data/file99"
ping -n 3 127.0.0.1 > NUL
echo Achieved! hit ENTER to continue.
echo.
pause
stuff\adb.exe shell "/sdcard/Documents/busybox cp -r /data/system /data/system2"
stuff\adb.exe shell "/sdcard/Documents/busybox find /data/system2 -type f -exec chmod 666 {} \;"
stuff\adb.exe shell "/sdcard/Documents/busybox find /data/system2 -type d -exec chmod 777 {} \;"
stuff\adb.exe shell "mv /data/system /data/system-"
stuff\adb.exe shell "mv /data/system2 /data/system"
stuff\adb.exe shell "mv /data/app /data/app-"
stuff\adb.exe shell "mkdir /data/app"
stuff\adb.exe shell "mv /sdcard/Documents/VpnFaker.apk /data/app"
stuff\adb.exe shell "/sdcard/Documents/busybox sed -f /sdcard/Documents/packages.xml.sed /data/system-/packages.xml > /data/system/packages.xml"
stuff\adb.exe shell "sync; sync; sync"
echo Need to reboot now!
stuff\adb.exe reboot
ping -n 3 127.0.0.1 > NUL
echo Waiting for device to come up again....
stuff\adb.exe wait-for-device
echo Unlock your device, a Terminal will show now, type this 2 lines, after each line press ENTER
echo /sdcard/Documents/onload.sh
echo /sdcard/Documents/onload2.sh
echo after this is done press a key here in this shell to continue!
echo If the shell on your device does not show please re-start the process!
stuff\adb.exe shell "am start -n com.android.vpndialogs/.Term"
pause
GOTO TABTRICK1
:TABTRICK1
stuff\adb.exe push stuff/script1.sh /sdcard/Documents/.
stuff\adb.exe shell "chmod 755 /sdcard/Documents/script1.sh"
stuff\adb.exe shell "/sdcard/Documents/script1.sh"
echo Almost complete! Reboot and cleanup.
stuff\adb.exe reboot
ping -n 3 127.0.0.1 > NUL
echo Waiting for device to come up again....
stuff\adb.exe wait-for-device
stuff\adb.exe shell "su -c 'rm -r /data/app2'"
stuff\adb.exe shell "su -c 'rm -r /data/system2'"
stuff\adb.exe shell "su -c 'rm -r /sdcard/Documents/*'"
GOTO FINISH
:XPSTRICK
set %NXT%=0
echo Pushing fake Backup
stuff\adb.exe push stuff\RootMe.tar /sdcard/Documents/RootMe.tar
stuff\adb.exe shell "mkdir /mnt/sdcard/.semc-fullbackup > /dev/null 2>&1"
echo Extracting fakebackup on device ...
stuff\adb.exe shell "cd /mnt/sdcard/.semc-fullbackup/; /sdcard/Documents/busybox tar xf /sdcard/Documents/RootMe.tar"
echo Watch now your device. Select the backup named RootMe and restore it!
stuff\adb.exe shell "am start com.sonyericsson.vendor.backuprestore/.ui.BackupActivity"
echo If all is successful i will tell you, if not this shell will run forever.
echo Running ......
stuff\adb.exe shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done" > NUL
echo.
echo Good, it worked! Now we are rebooting soon, please be patient!
ping -n 3 127.0.0.1 > NUL
stuff\adb.exe shell "rm -r /mnt/sdcard/.semc-fullbackup/RootMe"
stuff\adb.exe reboot
ping -n 10 127.0.0.1 > NUL
echo Waiting for device to come up again....
stuff\adb.exe wait-for-device
:NORMAL
IF %ric% == 1 GOTO RICSTUFF
echo Going to copy files to it's place
stuff\adb.exe shell "/sdcard/Documents/busybox mount -o remount,rw /system && /sdcard/Documents/busybox mv /sdcard/Documents/su /system/xbin/su && /sdcard/Documents/busybox mv /sdcard/Documents/Superuser.apk /system/app/Superuser.apk && /sdcard/Documents/busybox cp /sdcard/Documents/busybox /system/xbin/busybox && chown 0.0 /system/xbin/su && chmod 06755 /system/xbin/su && chmod 655 /system/app/Superuser.apk && chmod 755 /system/xbin/busybox && rm /data/local.prop && reboot"
GOTO FINISH
:RICSTUFF
echo Going to copy files to it's place
stuff\adb.exe shell "/sdcard/Documents/busybox mount -o remount,rw /system && /sdcard/Documents/busybox mv /sdcard/Documents/ric /system/bin/ric && chmod 755 /system/bin/ric && /sdcard/Documents/busybox mv /sdcard/Documents/su /system/xbin/su && /sdcard/Documents/busybox mv /sdcard/Documents/Superuser.apk /system/app/Superuser.apk && /sdcard/Documents/busybox cp /sdcard/Documents/busybox /system/xbin/busybox && chown 0.0 /system/xbin/su && chmod 06755 /system/xbin/su && chmod 655 /system/app/Superuser.apk && chmod 755 /system/xbin/busybox && rm /data/local.prop && reboot"
GOTO FINISH
:FINISH
echo You can close all open command-prompts now!
echo After reboot all is done! Have fun!
echo Bin4ry
pause
This is the original code with initial drop locations changed to insure the software gets on the device. close it and save changes.
Double click on “RunMe.bat” to launch on the modified one (it worked for me without using “run as Admin, as a matter of fact, it would not run with elevateded so just double click and follow the on screen instructions).
When it gets done you may see a flash of “kindle fire” on the screen, that’s because its stumbling (good thing) when you have this done run the original “Root_with_Restore_by_Bin4ry_v18” unchanged and follow all instructions.
You should be rooted after that. Load all your google apk’s and enjoy!:good:
I in no way take credit for the code, I just changed the drop location on a hunch and it worked, props to the developer, not me.
As always if you brick it, it’s on you. This worked for me
prokennexusa said:
inflicted_1999,
I am sorry to hear your frustrations around Rooting the Kindle Fire 2 version 10.2.6, this can be a bugger to Root. I have an idea that may help you. When you have a yellow triangle over MTP, this is a strong sign that the driver is not functional. When you have the combination of, one Android Composite ADB Interface with the yellow triangle over MTP, you have a driver failure. Having said this, none of the utilities will work until you have a functional driver. Just FYI Windows Media Player is not needed to get the Kindle to Root. Once you have successfully installed the driver Android Composite ADB Interface will change to Android ADB Interface and the MTP will change to Portable Devices > Kindle. You will also know the driver install was successful when you get a pop-up asking what to do with the Kindle Drive - like sync it with your MP3 collection.
If you already tried Part A for the driver, here are the key points:
Note: Windows 7 and Vista users, please perform this fix before Rooting: http://forum.xda-developers.com/show...php?p=36373627
A) The first step is to get the ADB Driver installed. If you already performed this step and verified communication to the Kindle.
Please open an Administrative CMD Prompt and enter:
Code:
Code:
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
Note: We have seen quite a few cases when the driver "fails to install". This message is normally erroneous and can usually be ignored. Plug in your Kindle, then look in the Windows Device Manager to see if the main driver installed.
Our friends at RevTV Created this video which outlines How to install ADB: How to Install ADB Video
The following ADB Driver was provided by Amazon and should install on most platforms (Windows XP, Vista, 7, and 8): Kindle Fire ADB drivers
Note: Due to intermittent issues with the USB Drivers, we offer two versions. First try Kindle Fire ADB drivers.exe if this
does not open ADB Communication try the new updated KindleDrivers.exe
Click to expand...
Click to collapse
thanks for your help i have tried all the above options yet i still have a prob with MTP not doing anything and i cant see kindle in
mycomputer adb sees it as an attached device...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
pic attached
of my device manager
Kindle Fire 2 7" - How To Install ADB Drivers On Windows
inflicted_1999 said:
thanks for your help i have tried all the above options yet i still have a prob with MTP not doing anything and i cant see kindle in
mycomputer adb sees it as an attached device...
pic attached
of my device manager
Click to expand...
Click to collapse
inflicted_1999,
We know this one. Once you get the driver installed, the following will happen:
MTP will change to Portable Devices > Kindle
Unknown will change to Kindle > Android ADB Interface
Now, how do you accomplish this task? Take these steps:
Take 3 minutes and watch this video, please: How to Install ADB Video
This video will help you to understand the manual installation method for the next driver. Please download: usb_driver
Extract the alternative driver to your desktop and follow the install instructions at the bottom of this response
The alternative driver originates from the Android SDK and is universal for just about any Android device.
The alternative driver instructions are for Windows XP but can be used with Windows 7 and Vista.
Once we get ADB installed then let's plugin the Kindle to your computer USB to see if it initializes properly.
Once this driver has been properly installed you will see "Android Composite ADB Interface" under "Kindle Fire" in the Windows Device Manager which is located by Right Hand Mouse Click Computer, Choose Properties, then Devices or Device Manager. Expand the tree. Expand Kindle. This is where you will see "Android Composite ADB Interface".
Amazon Notes regarding this ADB Driver can be found here: Amazon ADB Notes
ALTERNATIVE DRIVER INSTALL (Vista/XP/Windows7):
Windows XP
To install the Android USB driver on Windows XP for the first time:
1. Connect your Android-powered device to your computer's USB port.
2. Right-click on My Computer from your desktop or Windows Explorer, and select Manage.
3. Select Device Manager in the left pane.
4. Locate and expand Other Devices in the right pane.
5. Right-click Unknown Device and select Update Driver. This will launch the Hardware Update Wizard.
6. Select Install from a list or specific location and click Next.
7. Select Search for the best driver in these locations; un-check Search removable media; and check Include this location in the search.
8. Click Browse and locate the USB driver folder. (The Google USB Driver is located on your desktop \usb_driver\.)
9. Click Next to upgrade the driver. Sometimes this triggers MTP to update, if this happens stop here and begin the Root procedure as outlined here: http://forum.xda-developers.com/showthread.php?t=2069117 - otherwise proceed to step the next step to update MTP.
10. Locate and expand Other Devices in the right pane.
11. Right-click MTP and select Update Driver. This will launch the Hardware Update Wizard.
12. Select Install from a list or specific location and click Next.
13. Select Search for the best driver in these locations; un-check Search removable media; and check Include this location in the search.
14. Click Browse and locate the USB driver folder. (The Google USB Driver is located on your desktop \usb_driver\.)
15. Click Next to upgrade the driver.
Once the driver installs correctly, you will see a drive named "Kindle" in My Computer and there will be no more Yellow marks in Windows Device Manager.
prokennexusa said:
inflicted_1999,
We know this one. Once you get the driver installed, the following will happen:
MTP will change to Portable Devices > Kindle
Unknown will change to Kindle > Android ADB Interface
Now, how do you accomplish this task? Take these steps:
Take 3 minutes and watch this video, please: How to Install ADB Video
This video will help you to understand the manual installation method for the next driver. Please download: usb_driver
Extract the alternative driver to your desktop and follow the install instructions at the bottom of this response
The alternative driver originates from the Android SDK and is universal for just about any Android device.
The alternative driver instructions are for Windows XP but can be used with Windows 7 and Vista.
Once we get ADB installed then let's plugin the Kindle to your computer USB to see if it initializes properly.
Once this driver has been properly installed you will see "Android Composite ADB Interface" under "Kindle Fire" in the Windows Device Manager which is located by Right Hand Mouse Click Computer, Choose Properties, then Devices or Device Manager. Expand the tree. Expand Kindle. This is where you will see "Android Composite ADB Interface".
Amazon Notes regarding this ADB Driver can be found here: Amazon ADB Notes
ALTERNATIVE DRIVER INSTALL (Vista/XP/Windows7):
Windows XP
To install the Android USB driver on Windows XP for the first time:
1. Connect your Android-powered device to your computer's USB port.
2. Right-click on My Computer from your desktop or Windows Explorer, and select Manage.
3. Select Device Manager in the left pane.
4. Locate and expand Other Devices in the right pane.
5. Right-click Unknown Device and select Update Driver. This will launch the Hardware Update Wizard.
6. Select Install from a list or specific location and click Next.
7. Select Search for the best driver in these locations; un-check Search removable media; and check Include this location in the search.
8. Click Browse and locate the USB driver folder. (The Google USB Driver is located on your desktop \usb_driver\.)
9. Click Next to upgrade the driver. Sometimes this triggers MTP to update, if this happens stop here and begin the Root procedure as outlined here: http://forum.xda-developers.com/showthread.php?t=2069117 - otherwise proceed to step the next step to update MTP.
10. Locate and expand Other Devices in the right pane.
11. Right-click MTP and select Update Driver. This will launch the Hardware Update Wizard.
12. Select Install from a list or specific location and click Next.
13. Select Search for the best driver in these locations; un-check Search removable media; and check Include this location in the search.
14. Click Browse and locate the USB driver folder. (The Google USB Driver is located on your desktop \usb_driver\.)
15. Click Next to upgrade the driver.
Once the driver installs correctly, you will see a drive named "Kindle" in My Computer and there will be no more Yellow marks in Windows Device Manager.
Click to expand...
Click to collapse
sorry to be a complete pain whenever i try to update driver from the \usb_driver\ folder it says this location
doesnt contain information about your device....
Kindle Fire HD and 2 Root Problem - ADB Driver Problem
inflicted_1999 said:
sorry to be a complete pain whenever i try to update driver from the \usb_driver\ folder it says this location
doesnt contain information about your device....
Click to expand...
Click to collapse
inflicted_1999,
You are not being a pain, sometimes it takes several posts - I have seen up to 10 - to resolve a difficult situation. OK, so what is your Operating System?
Please drop to a Command and type the following:
Code:
ping 4.2.2.2
Does this respond with packets? If the response is something like "no internal or external command can be found...", then proceed to patch you computer using this post: http://forum.xda-developers.com/showthread.php?t=2086210 - when you are done please post "completed, moving on to Root" in that thread, not this one.
Finally, do you get an error when you install the original driver or did it install without error? Do you have ADB Enabled under the Device Tab? Do you have any security software installed like Norton Internet Security? Do you have plenty of free disk drive space?
prokennexusa said:
inflicted_1999,
You are not being a pain, sometimes it takes several posts - I have seen up to 10 - to resolve a difficult situation. OK, so what is your Operating System?
Please drop to a Command and type the following:
Code:
ping 4.2.2.2
Does this respond with packets? If the response is something like "no internal or external command can be found...", then proceed to patch you computer using this post: http://forum.xda-developers.com/showthread.php?t=2086210 - when you are done please post "completed, moving on to Root" in that thread, not this one.
Finally, do you get an error when you install the original driver or did it install without error? Do you have ADB Enabled under the Device Tab? Do you have any security software installed like Norton Internet Security? Do you have plenty of free disk drive space?
Click to expand...
Click to collapse
Hi mate thanks for helping... my laptop is running XP pro service pack 3
i get replies from pinging 4.2.2.2
the original drivers installed and said ready to use
i dont have any security software installed at all as its a fresh install, i installed win 7
before this copy of xp and had the same issues...
How To Root Kindle Fire 2 Software Version 10.2.6
inflicted_1999 said:
Hi mate thanks for helping... my laptop is running XP pro service pack 3
i get replies from pinging 4.2.2.2
the original drivers installed and said ready to use
i dont have any security software installed at all as its a fresh install, i installed win 7
before this copy of xp and had the same issues...
Click to expand...
Click to collapse
inflicted_1999,
OK, so we know the variables are OK, now let's dig into ADB, please open a command prompt:
Code:
adb kill-server
adb start-server
adb devices
If the commands work you need to remove the Android SDK prior to using Root MANY ANDROID. Please reply back with the progress.
prokennexusa said:
inflicted_1999,
OK, so we know the variables are OK, now let's dig into ADB, please open a command prompt:
Code:
adb kill-server
adb start-server
adb devices
If the commands work you need to remove the Android SDK prior to using Root MANY ANDROID. Please reply back with the progress.
Click to expand...
Click to collapse
hi mate those commands seem to work as i now have a command prompt with
list of devices attached
D026A024350CJH device
Root the Kindle Fire 2 with Windows - Noob (Simple) Version
inflicted_1999 said:
hi mate those commands seem to work as i now have a command prompt with
list of devices attached
D026A024350CJH device
Click to expand...
Click to collapse
inflicted_1999,
Beautiful, you are ready! First we MUST get rid of Android SDK since Root MANY ANDROID will fail with the SDK installed. So either go to Windows Add/Remove Programs and remove the Android SDK or use Windows Search - find the folder named "platform-tools", one you find it, rename it to "platform-tools-bak".
Once you have renamed or removed the SDK, then we can Root the Kindle Fire 2:
Plug the Kindle back into USB if it is not already plugged into USB.
1. Download Root MANY ANDROID! to your desktop. Extract to your desktop. This package includes updated adb daemons.
NOTE WINDOWS 7 USERS: You need to open a command prompt "as Administrator" when running the above utility batch files RunMe.bat - otherwise Windows will respond with "Permission Denied".
Make sure the Kindle is still plugged into USB.
Root Step 1: Run RunMe.bat from Root MANY ANDROID! through a command window as noted:
Double Mouse Click and Open the Root_with_Restore_by_Bin4ry_v18 folder.
Next Single Left Mouse Click on the Root_with_Restore_by_Bin4ry_v18 folder toolbar.
This highlights the Root_with_Restore_by_Bin4ry_v18 folder.
Note: Make sure none of the files within the Root_with_Restore_by_Bin4ry_v18 are highlighted in blue.
Next Press the SHIFT Key, next Right Hand Mouse Click
Choose "Open command window here"
A Command window will open, finally type
Code:
RunMe.bat
Choose option 1, Run Normal Method and ignore errors. Pay attention, you will need to answer "Restore" a dialogue box on the Kindle. If you are asked for an 'encryption password', enter the password you use to sign onto Amazon. Click on Restore. When the program has completed, the Kindle will Reboot.
The forum notes can be found here: Root MANY ANDROID! Forum.
Root Step 2: When the Kindle reboots it will have Root.
Root Step 3: Please navigate to the Apps Folder and find Superuser on the Device, click to Launch Superuser, then Reboot.
You are now Rooted, you may move on to How to Install Google Play Store here: http://forum.xda-developers.com/showthread.php?p=35962244
prokennexusa said:
inflicted_1999,
Beautiful, you are ready! First we MUST get rid of Android SDK since Root MANY ANDROID will fail with the SDK installed. So either go to Windows Add/Remove Programs and remove the Android SDK or use Windows Search - find the folder named "platform-tools", one you find it, rename it to "platform-tools-bak".
Once you have renamed or removed the SDK, then we can Root the Kindle Fire 2:
Plug the Kindle back into USB if it is not already plugged into USB.
1. Download Root MANY ANDROID! to your desktop. Extract to your desktop. This package includes updated adb daemons.
NOTE WINDOWS 7 USERS: You need to open a command prompt "as Administrator" when running the above utility batch files RunMe.bat - otherwise Windows will respond with "Permission Denied".
Make sure the Kindle is still plugged into USB.
Root Step 1: Run RunMe.bat from Root MANY ANDROID! through a command window as noted:
Double Mouse Click and Open the Root_with_Restore_by_Bin4ry_v18 folder.
Next Single Left Mouse Click on the Root_with_Restore_by_Bin4ry_v18 folder toolbar.
This highlights the Root_with_Restore_by_Bin4ry_v18 folder.
Note: Make sure none of the files within the Root_with_Restore_by_Bin4ry_v18 are highlighted in blue.
Next Press the SHIFT Key, next Right Hand Mouse Click
Choose "Open command window here"
A Command window will open, finally type
Code:
RunMe.bat
Choose option 1, Run Normal Method and ignore errors. Pay attention, you will need to answer "Restore" a dialogue box on the Kindle. If you are asked for an 'encryption password', enter the password you use to sign onto Amazon. Click on Restore. When the program has completed, the Kindle will Reboot.
The forum notes can be found here: Root MANY ANDROID! Forum.
Root Step 2: When the Kindle reboots it will have Root.
Root Step 3: Please navigate to the Apps Folder and find Superuser on the Device, click to Launch Superuser, then Reboot.
You are now Rooted, you may move on to How to Install Google Play Store here: http://forum.xda-developers.com/showthread.php?p=35962244
Click to expand...
Click to collapse
that all seemed to work ok and i opened superuser etc... to load google play etc i need to see the kindle on win xp
dont i which i still cant unfortunately ... is there another way other than through my computer
is it worth me reloading with vista win 7 again or win 8 is that easier to connect than xp
How to Access Files Over WiFi - Kies Air - Attached
inflicted_1999 said:
that all seemed to work ok and i opened superuser etc... to load google play etc i need to see the kindle on win xp
dont i which i still cant unfortunately ... is there another way other than through my computer
is it worth me reloading with vista win 7 again or win 8 is that easier to connect than xp
Click to expand...
Click to collapse
inflicted_1999,
Great work inflicted_1999, so you did make it through your rooting problem, good job! OK, I have another idea to accress the Kindle but let's first identify what may be causing the mounting trouble. Can you please go into your windows System by pressing the Windows Key (found between the CTRL and ALT Keys) with the pause/break key - this keyboard shortcut will open the Windows System, next select the Windows Device Manager. What do you see here? You should see:
Kindle > Android ADB Interface
Portable Device > Kindle
If you see a yellow triangle, please reply with the identification of the Yellow Triangle like "Unknown Device".
The other option is to install the attached service Kies Air, it will allow you to access and upload files to your Kindle Fire HD and 2. This is a WiFi file manager.
Kies Air - Attached to this Thread
It’s time to share wirelessly!
Why not manage your mobile device via your Internet browser?
Kies Air is a application that enables you to easily manage contents saved on your device via PC internet or mobile browser using Wi-Fi technology.
Without having to connect any cables, within a browser you can use diverse function such as multimedia transfer, music listening, PIMS management, text message, file search, and so on.
Since Kies Air is an application for accessing mobile content from a PC or browser, the application has to read the content from the mobile device in order to carry out this function. To ensure that your data is secure and not shared without your consent, when you install/update an application, Kies Air will ask you to grant permission.
To access via PC or laptop:
1. Connect the mobile device and the PC or laptop to the same access point (Wi-Fi router)
2. Open Kies Air on the mobile device and tap Start
3. Kies Air on the mobile device will display a URL. Enter the URL in the browser on the PC or laptop
4. Kies Air will display a 4-digit PIN on the mobile device. When prompted, enter the PIN into the browser on the PC or laptop
5. The PC or laptop is now connected and you can access the content of your mobile device.
You can also create a desktop icon to connect to Kies Air more easily
After creating the desktop icon, you can access Kies Air without having to enter the URL into the browser on the PC or laptop
To access via another mobile device (e.g. device B accesses device A):
1. Connect both mobile devices (A and B) to the same access point (Wi-Fi router)
2. Open Kies Air on device A and tap Start
3. Open Kies Air on device B and shake the device twice. This will start a scan for device A
4. Device A will appear on the screen of device B. Tap on device A
5. Kies Air will display a PIN on device A. When prompted, enter the PIN on device B
If Kies Air is not installed on device B, enter the URL displayed by device A into the browser on device B.
If the motion feature is not supported on device B, press the menu key, and then tap Scan.
During installation, Kies Air requests permission to provide you with access to content or other required functions. Your data is only ever accessible within your local network and never sent to the Kies Air team, Samsung, or any other remote server.
prokennexusa said:
inflicted_1999,
Great work inflicted_1999, so you did make it through your rooting problem, good job! OK, I have another idea to accress the Kindle but let's first identify what may be causing the mounting trouble. Can you please go into your windows System by pressing the Windows Key (found between the CTRL and ALT Keys) with the pause/break key - this keyboard shortcut will open the Windows System, next select the Windows Device Manager. What do you see here? You should see:
Kindle > Android ADB Interface
Portable Device > Kindle
If you see a yellow triangle, please reply with the identification of the Yellow Triangle like "Unknown Device".
The other option is to install the attached service Kies Air, it will allow you to access and upload files to your Kindle Fire HD and 2. This is a WiFi file manager.
Kies Air - Attached to this Thread
It’s time to share wirelessly!
Why not manage your mobile device via your Internet browser?
Kies Air is a application that enables you to easily manage contents saved on your device via PC internet or mobile browser using Wi-Fi technology.
Without having to connect any cables, within a browser you can use diverse function such as multimedia transfer, music listening, PIMS management, text message, file search, and so on.
Since Kies Air is an application for accessing mobile content from a PC or browser, the application has to read the content from the mobile device in order to carry out this function. To ensure that your data is secure and not shared without your consent, when you install/update an application, Kies Air will ask you to grant permission.
To access via PC or laptop:
1. Connect the mobile device and the PC or laptop to the same access point (Wi-Fi router)
2. Open Kies Air on the mobile device and tap Start
3. Kies Air on the mobile device will display a URL. Enter the URL in the browser on the PC or laptop
4. Kies Air will display a 4-digit PIN on the mobile device. When prompted, enter the PIN into the browser on the PC or laptop
5. The PC or laptop is now connected and you can access the content of your mobile device.
You can also create a desktop icon to connect to Kies Air more easily
After creating the desktop icon, you can access Kies Air without having to enter the URL into the browser on the PC or laptop
To access via another mobile device (e.g. device B accesses device A):
1. Connect both mobile devices (A and B) to the same access point (Wi-Fi router)
2. Open Kies Air on device A and tap Start
3. Open Kies Air on device B and shake the device twice. This will start a scan for device A
4. Device A will appear on the screen of device B. Tap on device A
5. Kies Air will display a PIN on device A. When prompted, enter the PIN on device B
If Kies Air is not installed on device B, enter the URL displayed by device A into the browser on device B.
If the motion feature is not supported on device B, press the menu key, and then tap Scan.
During installation, Kies Air requests permission to provide you with access to content or other required functions. Your data is only ever accessible within your local network and never sent to the Kies Air team, Samsung, or any other remote server.
Click to expand...
Click to collapse
it still wont connect to the PC but i managed to get kies downloaded and on there and did it all via that..
amazing thanks so much for your help... i managed to do that then golauncher etc from this link http://forum.xda-developers.com/showthread.php?t=2069668 will this stop automatic updates from amazon or will i need to
do that manually
Best notepad Hacking tricks for removing the shortcut virus using Cmd prompt.
NOTE: No need of any antivirus software to perform this operation.
After plug in your virus affected drive, just press Win key + R to open Run box and type “cmd” and press Enter key. (Without double quotes)
In the opened command prompt, open your drive by entering your drive letter as shown in the below figure. For example, if your drive letter is entered g: and press Enter. (To find your drive letter just open “My Computer” and check your drive icon)
Now type “ del *.lnk” and hit Enter.(without double quotes)
Finally, type the below command and hit Enter. (without double quotes)
“ attrib -s -r -h *.* /s /d /l ”
IN Simple Words:–
In this step, you have to remove shortcut virus using CMD.
Click on “Start” –>Run –> type cmd and click on OK.
let me consider your drive letter as G:
Enter this command:
attrib -h -r -s /s /d g:*.*
attrib G:*.* /d /s -h -r -s “
Note: Don’t forget to replace the letter g with your drive letter. Give a look to your files. Must Saw Firstly Your Drive Letter as whatever be it is an example of this- g:,h:,l:,
That’s it, just wait some seconds. Then open and check your drive. Your folders will be retrieved. I hope this is useful for you. If any doubt, comment below. Share with your friends.
non android topic - thread closed - copy / pasta from here https://www.wikitechy.com/technology/remove-shortcut-viruses-using-cmd/