Database Users

Unroot the vibrant

I want to root but want to be reassured I can unroot for warranty purposes.

In theory couldn't you just restore to factory settings?
Sent from my SGH-T959 using Tapatalk

JWhipple said:
In theory couldn't you just restore to factory settings?
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
Restoring factory settings does not remove root.

Just open terminal on your computer and type
Code:
adb shell
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
That'll remove the components that rooting installs.
*obviously to use adb shell you'll need the SDK installed

mmm easy
Ahh, easiest root/unroot makes me happy

Xyber3364 said:
Ahh, easiest root/unroot makes me happy
Click to expand...
Click to collapse
Yeah, the Vibrant is ridiculously simple so far.

bahnburner said:
Just open terminal on your computer and type
Code:
adb shell
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
That'll remove the components that rooting installs.
*obviously to use adb shell you'll need the SDK installed
Click to expand...
Click to collapse
could you just use the terminal on the phone ?

Yeah, I just don't like BetterTerminal. For some reason it always gives me hell, and it's the only terminal emulator that allows for an on screen keyboard.
To do this in terminal on the phone:
Code:
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su

bahnburner said:
Yeah, I just don't like BetterTerminal. For some reason it always gives me hell, and it's the only terminal emulator that allows for an on screen keyboard.
To do this in terminal on the phone:
Code:
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
Click to expand...
Click to collapse
actually you can use any terminal and just hold the menu button to pull up the keyboard... it worked for anything i needed on the mt3g seems to still work on the vibrant but havent tested in terminal so whoever tries it out let us know

bahnburner said:
Yeah, I just don't like BetterTerminal. For some reason it always gives me hell, and it's the only terminal emulator that allows for an on screen keyboard.
To do this in terminal on the phone:
Code:
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
Click to expand...
Click to collapse
skater4690 said:
actually you can use any terminal and just hold the menu button to pull up the keyboard... it worked for anything i needed on the mt3g seems to still work on the vibrant but havent tested in terminal so whoever tries it out let us know
Click to expand...
Click to collapse
Sweet, thanks guys. Im gonna root now. Even if the terminal on the Phone dont work, atleast I can install the drivers and go the adb route.. AWESOME..

skater4690 said:
actually you can use any terminal and just hold the menu button to pull up the keyboard... it worked for anything i needed on the mt3g seems to still work on the vibrant but havent tested in terminal so whoever tries it out let us know
Click to expand...
Click to collapse
Wouldn't hard resetting put those back even after deleting?

ok my phone is having hardware issues home key and search buttons are not working so i have to return my phone problem is that im rooted. i just downloaded terminal emulator and am trying to put that code in but its not working any advice

mx4life921 said:
ok my phone is having hardware issues home key and search buttons are not working so i have to return my phone problem is that im rooted. i just downloaded terminal emulator and am trying to put that code in but its not working any advice
Click to expand...
Click to collapse
Try hard resetting to make sure?
only thing I suggest is install the drivers on your pc and the sdk and do it that way.. I'd link ya to the instructions but I'm still trying to find this instructions myself....
Anyone got a link?

where can I find the terminal On my pc?

temperbad said:
where can I find the terminal On my pc?
Click to expand...
Click to collapse
press "Control+r"
type "cmd"
press enter

bahnburner said:
Yeah, I just don't like BetterTerminal. For some reason it always gives me hell, and it's the only terminal emulator that allows for an on screen keyboard.
To do this in terminal on the phone:
Code:
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
Click to expand...
Click to collapse
Good 'ol "Terminal Emulator" has a soft keyboard toggle as well, works just fine.
My only gripe is the Swype backspace doesn't work right in any of the terminal applications including connectbot so you have to change your input method first if you have any desire to use the backspace key... Original android one works ok.

bahnburner said:
press "Control+r"
type "cmd"
press enter
Click to expand...
Click to collapse
Ok so after opening that it and when I press SU it errors, says superuser error. Do I got to get it to recognize my device first somehow? I got the drivers installed and in cmd it recognizes my device... What does the line you enter the command got to say when I enter in the commands?

Quick question. I am rooted and going to exchange under warranty. Can I do a factory data reset without causing any problems? I thought I read where someone tried when they were rooted and it wouldnt boot after. Thanks

temperbad said:
Ok so after opening that it and when I press SU it errors, says superuser error. Do I got to get it to recognize my device first somehow? I got the drivers installed and in cmd it recognizes my device... What does the line you enter the command got to say when I enter in the commands?
Click to expand...
Click to collapse
In Windows it should look like this:
Code:
C:\Users\Bahnburner.MacbookPro>adb shell
$su
#
it may also include this, but don't worry about it if it doesn't:
Code:
* daemon not running. starting it now *
* daemon started successfully *
dashed said:
Quick question. I am rooted and going to exchange under warranty. Can I do a factory data reset without causing any problems? I thought I read where someone tried when they were rooted and it wouldnt boot after. Thanks
Click to expand...
Click to collapse
I have done a factory reset to solve a browser issue and had absolutely no problems, however, the phone will remain rooted. You will still have to manually delete Superuser.apk, su and busybox.

hopefully this will help when people want to unroot if the update won't work without unroot

help me get my vibrant to stock

I previously received my vibrant rooted and using this method on the thread http://forum.xda-developers.com/showthread.php?t=734475 and i used the unrooted file on page two. everything worked great but i still have root. I have the superuser permission show up on my app list, i also tested to see if i have root by installing a root only app, and it worked. so can anybody help get to stock?

Did you use the odin flash? That will put the phone back to 100% stock. Sounds like you used the nandroid, it might not remove extra stuff like the root files.

ttabbal said:
Did you use the odin flash? That will put the phone back to 100% stock. Sounds like you used the nandroid, it might not remove extra stuff like the root files.
Click to expand...
Click to collapse
yes i used the nandroid. can you point me to the odin flash? and is the odin more dangerous to use than nandroid? thanks for the help.

look in the vibrant development section you can't miss it for god sake search man no one is going to spoonfeed you

vdub804 said:
look in the vibrant development section you can't miss it for god sake search man no one is going to spoonfeed you
Click to expand...
Click to collapse
listen, im new to this and ive already searched the devolpment section and theres a couple similar threads. so, since i dont really know what im doing, i asked for help. all i asked was to point me to the thread that someone who is experienced in this thinks i should use. thanks for the help.

http://forum.xda-developers.com/showthread.php?t=734475
I think the complaint is that it's the same thread you would have gotten the nandroid image from. No, odin is not more dangerous, so long as you are flashing STOCK roms. Don't go flashing euro stuff with it, and you'll be fine. There are step by step directions in that thread, follow them and you'll be back to stock in no time.

ttabbal said:
http://forum.xda-developers.com/showthread.php?t=734475
I think the complaint is that it's the same thread you would have gotten the nandroid image from. No, odin is not more dangerous, so long as you are flashing STOCK roms. Don't go flashing euro stuff with it, and you'll be fine. There are step by step directions in that thread, follow them and you'll be back to stock in no time.
Click to expand...
Click to collapse
thank you for the help. i was just confused as to which one to use. hopefully, when im more experienced in this, i wont post stupid questions like this.

You dont need to flash, just remove the following with Terminal Emulator or file manager of your choice:
/system/app/Superuser.apk
/system/xbin/busybox
/system/bin/su
Reboot and you will no longer have root access.

mrxela said:
You dont need to flash, just remove the following with Terminal Emulator or file manager of your choice:
/system/app/Superuser.apk
/system/xbin/busybox
/system/bin/su
Reboot and you will no longer have root access.
Click to expand...
Click to collapse
im in Terminal Emulator and typed
/system/app/Superuser.apk
it says
/system/app/Superuser.apk: Permission denied
any ideas?

stepinmyworld said:
im in Terminal Emulator and typed
/system/app/Superuser.apk
it says
/system/app/Superuser.apk: Permission denied
any ideas?
Click to expand...
Click to collapse
did u type "su" before typing every other else?
it should be like:
# whatever you type
not $ whatever you type.

If you are using terminal then type this, each line should be entered on its own.
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su

From the sticky at the top of the page (that says to read before asking). If you want to use the links, go to the sticky.
HOW TO UN-ROOT *ie, sending your phone in for warranty work
The following code can be keyed in Terminal Emulator (could also be done in ADB or deleting the files using Root Explorer). If you do use Terminal, change the keyboard to the stock Android KB prior to opening Terminal. Apparently the backspace on swype does not work in Terminal. Each line should be entered separately. bahnburner gave the instructions in this thread, which you should review first.
Quote:
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
* Alternate Method *
TGA_Gunnman in this thread created a one click root/unroot program. Thank him for his effort.

mrxela said:
You dont need to flash, just remove the following with Terminal Emulator or file manager of your choice:
/system/app/Superuser.apk
/system/xbin/busybox
/system/bin/su
Reboot and you will no longer have root access.
Click to expand...
Click to collapse
mrxela said:
If you are using terminal then type this, each line should be entered on its own.
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
Click to expand...
Click to collapse
this worked! Thank you. This should go into the thread as a sticky or named terminal commands for un-rooting. so hopefully i will receive OTA updates corrects?

It is in the sticky.

JEEBUS (10....)

mrxela said:
It is in the sticky.
Click to expand...
Click to collapse
aww shux. smh
thanks

I used root explorer and deleted those files, so that means I'm on stock and I can get warranty service? Thanks a lot guys, you have saved a noob

stepinmyworld said:
this worked! Thank you. This should go into the thread as a sticky or named terminal commands for un-rooting. so hopefully i will receive OTA updates corrects?
Click to expand...
Click to collapse
Haha rooting won't keep you from getting OTA updates.

how do i root now that i have gingerbread?

I have a Verizon tab that was rooted. I updated to gingerbread which removed root. Is there a way to root now that I have gingerbread?
Thanks!

you may try SuperOneClick 2.2 with ZergRush...

Thanks. I'll give it a shot.

Soundchasr said:
Thanks. I'll give it a shot.
Click to expand...
Click to collapse
Did it work?

Haven't had a chance yet.

I tried it hangs on Step 7.. Does not root.
Sent from my SCH-I800 using xda premium

receptr said:
I tried it hangs on Step 7.. Does not root.
Sent from my SCH-I800 using xda premium
Click to expand...
Click to collapse
I've had the same problem. I can't seem to find a method that works; this Tab isn't getting much attention at all anymore.

Telling me, I have gingerbread on mine and it does nothing but forceclose crap all over the place

Lakilaulea said:
I've had the same problem. I can't seem to find a method that works; this Tab isn't getting much attention at all anymore.
Click to expand...
Click to collapse
I was able to get mine rooted by using the kernel from Galaxy Cubed 3 ROM. Downloaded the whole ROM and flashed only the kernel in heimdall. Then I used adb to push the correct files to the system and fixed permissions and rebooted. Worked great.
UPDATE:
If people want to know the adb commands I used, here they are:
adb push busybox /data/local/tmp/.
adb shell "chmod 755 /data/local/tmp/busybox"
adb shell "/data/local/tmp/busybox mount -o remount,rw /system"
adb shell "dd if=/data/local/tmp/busybox of=/system/xbin/busybox"
adb shell "chown root.shell /system/xbin/busybox"
adb shell "chmod 04755 /system/xbin/busybox"
adb shell "/system/xbin/busybox --install -s /system/xbin"
adb shell "rm -r /data/local/tmp/busybox"
adb push su /system/bin/su
adb shell "chown root.shell /system/bin/su"
adb shell "chmod 06755 /system/bin/su"
adb shell "rm /system/xbin/su"
adb shell "ln -s /system/bin/su /system/xbin/su"
adb push Superuser.apk /system/app/.
adb shell "cd /data/local/tmp/; rm *"
You can copy and paste these commands to a bat file and run it in a command prompt window. These were taken from a script used to root devices.
Here are links for the files you need. They are:
su
superuser.apk
busybox
They need to be placed in the same directory that you run the adb commands from.
SECOND UPDATE:
Rather than go through all this, go here:
http://forum.xda-developers.com/showthread.php?p=19678785
This is dsb9938's plain stock EI04 VZW ROM that is pre-rooted. Just flash in Heimdall and you are good to go. As long as you only wipe cache and dalvik, all your apps should stay intact.

Gingerbreak.apk should do the trick. Worked on my P1010

chris_toshiba said:
Gingerbreak.apk should do the trick. Worked on my P1010
Click to expand...
Click to collapse
It did not work on my VZW Tab. Someone said it is because it only works on 2.3.3 and older gingerbread and we have 2.3.5.
BTW, look at my earlier post (second update) to get a really easy way to have rooted stock 2.3.5 VZW Tab.

Unlocking and rooting from WW .29

It costed me more than a day but finally it is done and my TF300T is unlocked and rooted. The biggest problem was finding and placing the steps in the right order. It turned out that the Asus tool for unlocking the bootloader on .29 does not work. So, these are the steps (and most easy), to unlock and root a TF300T on WW .29
1 Downgrade to .17 with the DE blob found here and the instructions. Follow step 2.
2 Download the Asus unlock tool from the Asus website (support.asus.com)
3 Download also the .29 file
4 Install the unlock apk and unlock your device
5 After rebooting you will see the message that your device is unlocked. Now the fastboot protocol is available. You need it to perform step 7
6 After unlocking install .29 the same way as you downgraded your device
7 Install CWM by following the instructions found here
8 On the bottom of the same treat there is explained how to root the device (just run a simple apk)
9 It could be the you have to install busybox from the market, but I'm not sure.
The main advantage of this method is that you have CWM installed also.
Suc6!

THIS was posted on May 23rd, and hidden in the CWM Recovery + Root thread with NO thanks given to it:
http://forum.xda-developers.com/showthread.php?p=26478502#post26478502
And THIS was my comment to it just a few minutes ago:
http://forum.xda-developers.com/showpost.php?p=26929082&postcount=176

The unlocked worked on my US .29
Sent from my VS910 4G using xda premium

If it's really true that the ASUS unlock does not work with .29 then ASUS is a bonehead.
"Use this to unlock .. and oh jeah, you have no warranty"
[unlocking]
"Uhh, what do you mean it does not work? Well good luck then at XDA since you messed up the warranty. No it's not our fault, you want to unlock..."
Tnx for pointing this out. Also tnx for providing a step to step overview.

Unlocked my .29 with no problem

keynith said:
The unlocked worked on my US .29
Sent from my VS910 4G using xda premium
Click to expand...
Click to collapse
Same here. I had the modded build.prop so.....
I set the original build.prop back in place and then did a factory reset. Once I did that, the unlock tool worked fine.

Ok so quick question...
My bootloader is unlocked and im on .17
I have the update .zip for .29, but every time I try to flash in recovery (teamwin) nothing happens. Just says "installing update" for well over 15 min. Any suggestions? Btw: tried flashing both zips... the 2nd inside the first and still nothing :/
Sent from my ASUS Transformer Pad TF300T using xda premium

Redownload the update and try again. Could be bad update. Or get CWM and flash a ROM
Sent from my Transformer Prime TF300T using XDA Premium HD app

keynith said:
Redownload the update and try again. Could be bad update. Or get CWM and flash a ROM
Sent from my Transformer Prime TF300T using XDA Premium HD app
Click to expand...
Click to collapse
Didn't work :/
Plus I don't think I can get CWM flashed over teamwin. I think I read, that will brick it and have been too busy lately to check info on that. You see how long it took me to reply to this. Ugh! Sucks being busy all day. I'll keep looking around when I can. Thanks though. For sure
Sent from my ASUS Transformer Pad TF300T using xda premium

Rooting *without* downgrading (from .29)
Hello,
Since this is my first post on this forum I couldn't post it in the dev thread, so I post it here.
I just managed to root my TF300T without downgrading the firmware.
First, I decline all responsibility if you brick your device. Use the method and the binaries with extreme caution, although all should be ok if you follow step by step the following instructions.
Before starting, you should download the two binaries (debugfs and su) that are linked at the end of this post. And please read the instructions till the end before going into.
Here it is:
Rooting the Asus Transformer TF300T
===================================
: first, use known method to get write access to the /system partition
adb push debugfs /data/local/
adb push su /data/local/
adb shell
$ cd /data/local/
$ mv tmp tmp.back
$ ln -s /dev/block/mmcblk0p1 tmp
$ exit
adb reboot
adb shell
: some cleanup first
$ cd /data/local
$ rm /data/local/tmp
$ mv /data/local/tmp.back /data/local/tmp
: and now, let's do the dirty work
$ chmod 755 /data/local/debugfs
$ /data/local/debugfs -w /dev/block/mmcblk0p1
cd xbin
write /data/local/su su
set_inode_field su mode 0104755
set_inode_field su uid 0
set_inode_field su gid 0
quit
: done, let's reboot and get root !
adb reboot
adb shell
$ /system/xbin/su
# id
id=0(root) gid=0(root) ....
# exit
: cleanup remaining files
$ rm /data/local/su
$ rm /data/local/debugfs
Now here is the link to my dropbox containing the binaries and the source file for su. debugfs is part of e2fsprogs, and I didn't touch anything (I just struggled 24h to get it compiled for android, that's why I give it away ^^).
(link removed) (Well I have a link, but this forum won't let me post it...)
Regards,
milo
[edit] added the chmod 755 on debugfs

miloj said:
Hello,
Since this is my first post on this forum I couldn't post it in the dev thread, so I post it here.
I just managed to root my TF300T without downgrading the firmware.
First, I decline all responsibility if you brick your device. Use the method and the binaries with extreme caution, although all should be ok if you follow step by step the following instructions.
Before starting, you should download the two binaries (debugfs and su) that are linked at the end of this post. And please read the instructions till the end before going into.
Here it is:
Rooting the Asus Transformer TF300T
===================================
: first, use known method to get write access to the /system partition
adb push debugfs /data/local/
adb push su /data/local/
adb shell
$ cd /data/local/
$ mv tmp tmp.back
$ ln -s /dev/block/mmcblk0p1 tmp
$ exit
adb reboot
adb shell
: some cleanup first
$ cd /data/local
$ rm /data/local/tmp
$ mv /data/local/tmp.back /data/local/tmp
: and now, let's do the dirty work
$ /data/local/debugfs -w /dev/block/mmcblk0p1
cd xbin
write /data/local/su su
set_inode_field su mode 0104755
set_inode_field su uid 0
set_inode_field su gid 0
quit
: done, let's reboot and get root !
adb reboot
adb shell
$ /system/xbin/su
# id
id=0(root) gid=0(root) ....
# exit
: cleanup remaining files
$ rm /data/local/su
$ rm /data/local/debugfs
Now here is the link to my dropbox containing the binaries and the source file for su. debugfs is part of e2fsprogs, and I didn't touch anything (I just struggled 24h to get it compiled for android, that's why I give it away ^^).
(link removed) (Well I have a link, but this forum won't let me post it...)
Regards,
milo
Click to expand...
Click to collapse
Milo,
I want to give it a try, so can you pm me the dropbox link?
Thanks
Marco
Sent from my GT-I9000 using Tapatalk 2

First, thanks for your work. Why not just "edit" the URL if you can't post one yet. PEx w w w xyz. com. That would work Cheers
...via Tapatalk

Because I'm usually not a cheater ahah!
Here it is:
http : // db. tt/FBUNeVmo
Sent from my Desire HD using XDA

Hi!
$ /data/local/debugfs -w /dev/block/mmcblk0p1 -> cannot execute - Permission denied
cd xbin -> cd /system/xbin?
write /data/local/su su -> write: not found
What to do?

Sorry, I may have missed a chmod 755 debugfs.
A line preceded with $ is meant to be executed inside debugfs shell.
Tell me how it goes, I'll update the doc.
milo
Sent from my Desire HD using XDA

miloj said:
A line preceded with $ is meant to be executed inside debugfs shell.
Click to expand...
Click to collapse
Actually it is the other way round, sorry.
Everything following a $ is executed from the Android shell, and all non-prefixed line is executed in debugfs.
milo
Sent from my Desire HD using XDA

Here is Miloj's link for the necessary files: http://db.tt/FBUNeVmo
Miloj: Excellent work! Will you edit the OP with the correct code sequence, let's save us some bricks.
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app

/data/local/debugfs -w /dev/block/mmcblk0p1 -> Segmentation fault

cdma77 said:
/data/local/debugfs -w /dev/block/mmcblk0p1 -> Segmentation fault
Click to expand...
Click to collapse
OK it happened to me as well, and while trying to debug it, it then started to work without any change from me but some printf()...
I'll try to see if I can catch the exception and repost the binary.
Sent from my ASUS Transformer Pad TF300T using XDA

Frenchies are good, in'it ?
Miloj, anytime you want to help noobs like me to get root easier than what you explain, I'm interested. Maybe something compiled for linux challenged people...
Anyway, congrats to you !
miloj said:
OK it happened to me as well, and while trying to debug it, it then started to work without any change from me but some printf()...
I'll try to see if I can catch the exception and repost the binary.
Sent from my ASUS Transformer Pad TF300T using XDA
Click to expand...
Click to collapse

[GUIDE] Here is how to ROOT the Kindle Fire HD 7" running Kindle OS 7.4.3,

To make the ADB Binary work on Ubuntu 13.04 64Bit I had to run "sudo apt-get install ia32-libs". Sorry for the inconvenience. It's not under my control
Hi Everyone today I would like to show you how to Root the Kindle Fire HD this has been tested on the Kindle Fire HD 7” running Kindle OS 7.4.3. This is actually designed for the Ubuntu Linux users as Windows users are always getting the latest tools and I’d like to share this information with you. First I would like to thank r3pwn on XDA Developers. For the hours of being remoted into my computer (while the kernel and encryption were breaking down) and helping me figure out how to Root the Kindle he stayed and watched we almost gave up be he ended up thinking of something and I’d like to share this information with you. Please note for this to best work you will need Ubuntu Linux but if you have ADB for Windows the script is simple enough to rewrite the commands one by one and just use ADB.EXE which you can easily get by downloading the Android SDK. First you need to download this zip file (it's called adt-bundle but it also contains some files such as the su binary, superuser app, and busybox (which is critical to the script working). You need to extract it to a folder. Login as the root user or use “sudo -i” (emulates root by automatically making a virtual root session and just uses the sudo to run the commands but no typing sudo every time). After that switch to the folder with the extracted files. Then run these commands you will need 2 terminal windows both logged in as Root,
In terminal 1 type this command (now this will keep running please don’t close it as it’s very important.)-
“./adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done" > NUL”
Now in terminal 2 there are many commands you will need to type so run these commands-
“./adb backup backup.ab com.android.settings”
“./adb restore fakebackup.ab”
“./adb reboot”
“adb wait-for-device”
“./adb push busybox /data/local/tmp/busybox”
“./adb push ric /data/local/tmp/ric”
“./adb push su /data/local/tmp/su”
“./adb push Superuser.apk /data/local/tmp/Superuser.apk”
“./adb shell "/data/local/tmp/busybox mount -o remount,rw /system && /data/local/tmp/busybox mv /data/local/tmp/ric /system/bin/ric && chmod 755 /system/bin/ric && /data/local/tmp/busybox mv /data/local/tmp/su /system/xbin/su && /data/local/tmp/busybox mv /data/local/tmp/Superuser.apk /system/app/Superuser.apk && /data/local/tmp/busybox cp /data/local/tmp/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"
After that just look for the Superuser App and it should work fine. Also please note an OTA update will mess up your Root so disable them or better yet flash a custom Rom not based on Amazon’s Software. I will not be providing a guide on flashing the second bootloader and twrp 2.6.0 but I recommend using FireFlash along with this Guide. I take no responsibility if it messes up your device and you have to buy a “factory (fastboot) cable” to fix it however I’ll be very sorry. I hope this guide helps you a lot. If you need any help just PM me and we can IRC chat and I can also remote into your computer (if you run a special file).
Also a big thanks to r3pwn on XDA Developers again he has told me to just thank the Bin4ry method but he is the one who got this thing running. Thank You r3pwn

This belongs in the general thread and the thread is a duplicate. Your help is very appreciated but it's like no one is caring about the rules of things.
Sent from my One X using xda app-developers app

OK well this is actually for the newest version
Sent from my Amazon Kindle Fire HD using Tapatalk 4 Beta

Will this work on any other Linux OS? Like Vector Linux?
Sent from my JellyBeer Fire HD

nathansuchy said:
OK well this is actually for the newest version
Sent from my Amazon Kindle Fire HD using Tapatalk 4 Beta
Click to expand...
Click to collapse
Misterowl is correct... This is another duplicate thread. There has been posts already on how to root 7.4.3..
Here's one showing how to use the tool(KFFirstAide): http://forum.xda-developers.com/showthread.php?t=2355788

xWolf13 said:
Misterowl is correct... This is another duplicate thread. There has been posts already on how to root 7.4.3..
Here's one showing how to use the tool(KFFirstAide): http://forum.xda-developers.com/showthread.php?t=2355788
Click to expand...
Click to collapse
Perhaps better to practice using adb ,than running a script in my opinion

xxxo said:
Perhaps better to practice using adb ,than running a script in my opinion
Click to expand...
Click to collapse
Thanks. I like to know what the script does and it is automatmatically cross platform as long as you have adb and the other files.
Sent from my Amazon Kindle Fire HD using Tapatalk 4 Beta

Krsmqn said:
Will this work on any other Linux OS? Like Vector Linux?
Sent from my JellyBeer Fire HD
Click to expand...
Click to collapse
Yes as long as you can get the adb running. You may need to manually install adb though. Also please stop talking about how the thread is in the wrong place it has been moved so please let this thread be for questions...
Sent from my Amazon Kindle Fire HD using Tapatalk 4 Beta

Hey, nathansuchy, can you please make changes to your post to reflect my new username? Thanks.
Sent from my Amazon Kindle Fire HD using xda app-developers app

Sure will do that ASAP
Please check your PM.

xWolf13:
The thread you mentioned requires that you use a script that won't work for everyone. My method uses the same idea but is written simple enough for a smart linux user to rewrite the script to work for him/her self. It is not a script but a guide on rooting. It is different in how you approach it and the other guides did not work easy for me.