Related
TGA_Gunnman created a one click root that new users will want to use, said thread is a sticky in Captivate Development. If you still want to use the old method (and install ADB) please use this one.
I followed my own guide! This works perfectly if you read everything and follow the instructions.
Also: once you are rooted, be EXTREMELY careful! Half of the new threads are people who have screwed up their phones by deleting this or corrupting that. Please, for the sanity of all of the devs and Android veterans, make backups and just be all around careful. Almost all problems that anyone has had are repareable AND PREVENTABLE with a little reading and care. Just to clarify, rooting does not automatically enable sideloading. Please follow http://forum.xda-developers.com/showthread.php?t=738376 to enable sideloading.
Follow these steps exactly and there will be no risk of bricking your Captivate, the worst that may happen is the phone rejecting the update.zip.
HOWEVER:
I take no responsibility if ANYTHING at all happens to your device that you don't like. Don't come crying to me if your brand new phone breaks in any way. Your warranty is also void, but you could have figured that out for yourself.
Now that that's over with, lets get to the fun bit. If you are on Windows, you can follow this procedure, or for TGA_Gunnman's one click root program (only on Windows), you can go ahead and skip to the bottom.
1) You may need Samsung drivers if you are on a PC, which you can learn about here: ADB Drivers at the Unlockr
For 64 bit Windows, you'll need these drivers: http://zedomax.com/blog/2010/07/14/s...iver-download/
Don't proceed until your phone is fully installed on Windows with the drivers!
2) Download the attached zip (at the bottom of the post) and rename it to update or update.zip if you are on a Mac. (If you are on a Mac, DO NOT USE SAFARI to download the file, it automatically unzips any zip file. Use Google Chrome or firefox instead.) Scroll down the notification bar and click "mount" to allow your computer to read the internal memory. Put the file on the INTERNAL SD card of the Captivate, which won't be tough to figure out if you don't have an SD card in the phone.
3) EDIT--There is an easier way to get to recovery, but do this step anyway. Turn the phone off, then hold power, volume up and volume down. If you still want the android SDK (which will be very useful throughout your rooted experiences) follow the old procedure:
This step requires the Android SDK, and Android Debugging enabled. You can get the SDK here: Android SDK. Just download the zip, extract it to something like C:\Android. You won't need the Java dev pack or anything.
You can enable Android Debugging like this: From the homescreen, press Menu, then click Settings. Navigate to Applications>Development and check USB Debugging. Now, hook the phone to the computer. Next,
On a PC, click start>run>"cmd" (in the text box) or on a Mac, spotlight "Terminal". Linux users, you know what to do.
The command you will use is in the tools folder of wherever you extracted it to (IE: C:\android\tools), so be sure your working directory of command prompt is in that tools location!
Finally, type:
Code:
adb reboot recovery
Click to expand...
Click to collapse
4) Once the phone is booted into recovery, use the volume keys on the phone to scroll to "Reinstall packages." Use power to select what you have highlighted.
5) Give yourself a pat on the back. You are now rooted. You should see a Superuser application now.
MD5 Sum: 1eb65923281c113e8751a7d8a6faff43
Can we please have more detailed instructions? I don't understand the part where it says "type in the terminal"
I am very new to android as this will be my first Android phone.
Also, after rooting will we be able to install 3rd party applications? Or do we have to do anything else to bypass ATT's restrictions?
adb terminal is software you need to install on your PC , will probably need samsung drivers also , guide is indeed not noob friendly. This will help you get needed bits including ADB
Probably None of us have captivate , so writing a guide is a bit troublesome
Ditto, a guide to the adb terminal please! I will acquire this phone, this Sunday.
Actually, you'd have to install a custom ROM for that. MoDaCo should be coming out with them pretty soon, and so will XDA. It won't be too long. BTW, once you have ADB installed on your computer, you can sideload apps all you want. The command is
Code:
adb install /directory/of/app/on/computer
point me to some functioning samsung drivers and I can do this!
If you cant get it to work on windows, try a ubuntu live cd. All you need to do is go to ubuntu and burn a disc and reboot.
Are there no Windows 64 bit drivers?
Edit- I found some that work. I think. Haven't tried it (yet).
http://zedomax.com/blog/2010/07/14/...ic-4g-and-fascinate-galaxy-s-driver-download/
Edit 2- Just did the root. Seems to have worked (no errors) but how do I know if it did? How do I delete say, ATT Maps?
Thanks for this. I am new to smartphones and plan on purchasing the Samsung Galaxy-S, but don't want to mess it up. I am new to editing the OS of any smartphone, but I think if I have a tutorial I will be fine
For Mac and Linux you put a ./ in front of the adb correct? (./adb install...)
NOSintake said:
For Mac and Linux you put a ./ in front of the adb correct? (./adb install...)
Click to expand...
Click to collapse
if you are in the directory above yes. the ./ just saves you from writing out the full path
lets say adb is in "/home/user/Downloads/sdk/tools"
you could type out "/home/user/Downloads/sdk/tools/adb command" regardless of where your terminal window was focused
or if you were currently in the directory "/home/user/Downloads/sdk/tools"
you could use the shortcut "./adb command"
OP I'd change your post based on my experiences... Here's a little more detail and I've rearranged it (you need the drivers before running these commands, for example).
blackjackboy said:
Please let me know if this rooting method works as I have no Captivate to test on. I'm not taking any credit for any of these files, LeshaK made the original file to root the European Galaxy S, Justadude modified it for the T-Mobile Vibrant and chaoscentral edited the file for use on the Captivate.
Follow these steps exactly and there will be no risk of bricking your Captivate, the worst that may happen is the phone rejecting the update.zip.
HOWEVER:
I take no responsibility if ANYTHING at all happens to your device that you don't like. Don't come crying to me if your brand new phone breaks in any way.
Now that that's over with, lets get to the fun bit.
1) You may need Samsung drivers if you are on a PC, which you can learn about here: ADB Drivers at the Unlockr
For 64 bit Windows, you'll need these drivers: http://zedomax.com/blog/2010/07/14/...ic-4g-and-fascinate-galaxy-s-driver-download/
Don't proceed until your phone is fully installed on Windows with the drivers!
2) Download the attached zip (at the bottom of the post) and rename it to update or update.zip if you are on a Mac. Scroll down the notification bar and click "mount" to allow your computer to read the internal memory. Put the file on the INTERNAL SD card of the Captivate, which won't be tough to figure out if you don't have an SD card in the phone.
3) This step requires the Android SDK, and Android Debugging enabled. You can get the SDK here: Android SDK. Just download the zip, extract it to something like C:\Android. You won't need the Java dev pack or anything.
You can enable Android Debugging like this: From the homescreen, press Menu, then click Settings. Navigate to Applications>Development and check USB Debugging. Now, hook the phone to the computer. Next,
On a PC, click start>run>"cmd" (in the text box) or on a Mac, spotlight "Terminal". Linux users, you know what to do.
The command you will use is in the tools folder of wherever you extracted it to (IE: C:\android\tools), so be sure your working directory of command prompt is in that tools location!
Finally, type:
Code:
adb reboot recovery
4) Once the phone is booted into recovery, use the volume keys on the phone to scroll to "Reinstall packages." Use power to select what you have highlighted.
5) Give yourself a pat on the back. You are now rooted. You should see a Superuser application now.
Thank you to LeshaK, Justadude, and chaoscentral. Once again, I didn't discover how to root, that credit goes to LeshaK, bringing it over to the USA was Justadude's doing, and chaoscentral edited the file for use on our Captivates.
MD5 Sum: 1eb65923281c113e8751a7d8a6faff43
Click to expand...
Click to collapse
Ubuntu 10.04 - adb
Any step by step instructions just to get adb running enough on 10.04 to root and side load software? I'm getting command not found when I try to run adb, even after downloading packages.
Hi,
Did this thread worked well to Root the Captivate or anyother suggested link? I'll appreciate any help.
Thanks
rerooting captivate
This worked perfectly on my Captivate. I now have the SuperUser Permission on my application screen. Now I can REALLY screw up my Captivate!!!
Thanks for the answer & More Queston
cellgeek said:
This worked perfectly on my Captivate. I now have the SuperUser Permission on my application screen. Now I can REALLY screw up my Captivate!!!
Click to expand...
Click to collapse
Hi,
Thanks for your helpful answer. As I'm getting my Cativate tomorrow, can you please just answer yes or no to each of my questions as follow ?
After Rooting will I be able to:
1- download any 3rd party Android application?
2- install any "Samsung Galaxy S" ROM on my Captivate?
3- Recieve any "OTA" update as a "Galaxy S" phone?
Thanks again
Muhamadabdelaall said:
Hi,
Thanks for your helpful answer. As I'm getting my Cativate tomorrow, can you please just answer yes or no to each of my questions as follow ?
After Rooting will I be able to:
1- download any 3rd party Android application?
2- install any "Samsung Galaxy S" ROM on my Captivate?
3- Recieve any "OTA" update as a "Galaxy S" phone?
Thanks again
Click to expand...
Click to collapse
1. No. You will have to use adb or the database modification method (which having root access makes possible). Both are described in detail elsewhere in this forum.
2. Rooting means simply getting superuser permissions. Loading a ROM has to do with the bootloader and recovery partition. Unmodded Galaxy S ROMs probably will not work on the Captivate, but be patient.
3. Not sure what you're asking. You will still get any Captivate OTA updates as if you hadn't rooted, but you won't get, for example, the rumored Korean FroYo Galaxy S update OTA when it drops. You'd have to wait for the Captivate OTA FroYo upgrade (or there may be a ROM or patch you can flash by then).
Rooting is basically just allowing programs to run as the superuser account. Many programs like Metamorph, some screenshot apps and some wifi tethering apps require more permission than Android normally gives an app.
Thanks Drachen
Drachen said:
1. No. You will have to use adb or the database modification method (which having root access makes possible). Both are described in detail elsewhere in this forum.
2. Rooting means simply getting superuser permissions. Loading a ROM has to do with the bootloader and recovery partition. Unmodded Galaxy S ROMs probably will not work on the Captivate, but be patient.
3. Not sure what you're asking. You will still get any Captivate OTA updates as if you hadn't rooted, but you won't get, for example, the rumored Korean FroYo Galaxy S update OTA when it drops. You'd have to wait for the Captivate OTA FroYo upgrade (or there may be a ROM or patch you can flash by then).
Rooting is basically just allowing programs to run as the superuser account. Many programs like Metamorph, some screenshot apps and some wifi tethering apps require more permission than Android normally gives an app.
Click to expand...
Click to collapse
Thanks alot for taking all this time & energy to reply to me! WOW, it seems like everytime I wanna step up one, I go back 10 steps. All I need is to use my Captivate for installing a Stock Rom of "Galaxy S" & be able to get rid of any "AT&T" restrictions for anything on this phone, what should I do please?
Thanks
Muhamadabdelaall said:
Thanks alot for taking all this time & energy to reply to me! WOW, it seems like everytime I wanna step up one, I go back 10 steps. All I need is to use my Captivate for installing a Stock Rom of "Galaxy S" & be able to get rid of any "AT&T" restrictions for anything on this phone, what should I do please?
Thanks
Click to expand...
Click to collapse
The ATT stuff doesn't actually run so they aren't a big deal at this point. I also don't see Amazon MP3 background stuff like some Android devices have, so... There's really not a huge case for rooting yet.
That said, when Custom ROMs for this come out I'll still be getting one.
For those of you having a hard time installing ADB Shell, try this video. It worked for me.
http://www.youtube.com/watch?v=YeWH6Bj1DYw&feature=related
The Xperia X10 Rooting Toolkit also works flawlessy with the Samsung Galaxy Note and gives you full root access (tested by myself)
Just follow the instructions to root/unroot the device here
http://forum.xda-developers.com/showthread.php?t=1319653
Confirmed working!
Since the ice cream sandwich is not out yet, what is the advantage of rooting it now?
clubtech said:
Confirmed working!
Click to expand...
Click to collapse
You are using AT&T and have the note,from wish retailer you buy yours?
please excuse my trivial question, but rooting the Note with the instructions you provided is it possible to install any kind of apk file?
finanziere said:
please excuse my trivial question, but rooting the Note with the instructions you provided is it possible to install any kind of apk file?
Click to expand...
Click to collapse
You don't need to root to install apks.
wonsanim said:
You are using AT&T and have the note,from wish retailer you buy yours?
Click to expand...
Click to collapse
eBay...
10chars
clubtech said:
eBay...
10chars
Click to expand...
Click to collapse
Thanks
is a little expencive on ebay
schölli said:
The Xperia X10 Rooting Toolkit also works flawlessy with the Samsung Galaxy Note and gives you full root access (tested by myself)
Just follow the instructions to root/unroot the device here
http://forum.xda-developers.com/showthread.php?t=1319653
Click to expand...
Click to collapse
could somebody tell me if this root method increase the binary counter??
thanks..
kersh said:
You don't need to root to install apks.
Click to expand...
Click to collapse
thanks, but I mean the non official apps or those that are cracked.
is it possible to install these without rooting the device?
m_adnan said:
could somebody tell me if this root method increase the binary counter??
thanks..
Click to expand...
Click to collapse
It won't
Sent from my GT-N7000 using xda premium
Worked for me! It was even easier than rooting an HTC Evo 4G. This thread, or at least the thread referenced in the first post, should be stickied in the Development sub-forum.
I am a Noob and I can Root my Note!
I had experience rooting a Milestone 2 with SuperOneClick and an unbranded Android Tablet with Z4Root. (Thanks to developers of these!)
Unfortunately, both these methods did not work on the Galaxy Note so I came here and found this thread.
Unfortunately, ADB drivers was an issue with the zergRush Exploit on first run. The easiest way to get around this is to install PDANet on Windows and have it install the drivers for you. No need to complete the whole installation, just watch when it's finished installing USB drivers and then when prompted to continue, just cancel. Then re-run the zergRush Exploit and it should do its magic (Again thanks to the developers who work on these!)
While I'm able to freeze some apps with ROM Toolbox, I'm unable to change boot animation or the battery icon. Would appreciate if anyone could help with this!
Rooting hav no relation to install official/crckd version of apk.
Rooting needed for those application which are needed to access your system data e.g backup etc
when you need to install these kinds of application (weather off/unoff) you needs Root.
The optional unrooting package works also perfectly (just for info)...
i have sent back my Galaxy Note to amazon just to wait for the white version of the Note.
This method won't increase your binary counter, so root and unroot it as often as you like
Never either had any problem at all after rooting it, so this method is also stable and won't crash your device in any way or crash any applications...
Root confirmed working here, superuser.apk doesn't have permissions set properly but still works, easy to fix, updates fine from market.
Awesome - confirmed working. This needs to be stickied... other websites are promoting netchips CWN kernel method instead of this MUCH simplier way.
For you noobs with a clean system (that means me!), get the following files:
Note I run a 64 bit windows box, get the 32 bit variants if necessary.
You need:
1) Latest version of Kies
www.samsung.com/ca/kies/index.html
download file for me was: Kies_2.0.3.11082_152_4.exe
2) Java:
www.oracle.com/technetwork/java/javase/downloads/index.html
Click on jdk and download. File for me: jdk-7u1-windows-x64.exe
3) android sdk:
developer.android.com/sdk/index.html
My file was: installer_r15-windows.exe
4) zergrush root script
http://forum.xda-developers.com/showthread.php?t=1312859
grab the zip file in that page i.e.
DooMLoRD_v1_UNROOTING.zip
and unzip it to your windows box.
Install 1, 2, 3 in that order.
Find the SDK Manager program in your sdk install directory, double click it, and download/update 'Android SDK Platform Tools'.
Note you can't run the sdk manager program from the command prompt, or it'll complain that directories are being locked.
Now follow the instructions on the zergrush page, i.e. do the 'before you begin' stuff.
Go to the directory where you unzipped the doomlord zip file, run the runme script from a command prompt,and that's it.
To test, download terminal monitor, run it, and do a 'su' then 'id' and see if it says you are root or not.
Good luck!
- Frank
sir can i ask a question?
after i install the cwm and i will make a nandroid back up before rooting the phone.
if i restore the unrooted back up. Will i go back to became un root again and go back to out of the box state?
will this work with the Korean version of the Note? thanks in advance.
TF101, SL101 and TF101G on ICS firmwares anything else is untested.
Also should work on TF201 and TF300T on ICS ONLY!
For Windows, tested on windows 7 x64 bit, xp 32 bit and windows 7 32 bit.
Your data will be retained, unless you wipe in TWRP or something
UPDATE:
Added V0.41 which includes TWRP
Also V0.42 which is even newer TWRP!
apk not working sofar :[
If you have a TF201, or TF300T, this will work still, but you need to replace the included file 'recoveryblob' with a recoveryblob from a recovery from your device (download the .zip file for the recovery you want, and extract the 'blob' or 'recoveryblob' file from it and place in PERI folder, naming it recoveryblob and overwriting the otherone!)
Initiate project-PERI:
Since there's no one-clicks that I've stumbled across, and many people are asking if this-that etc.. works with .24, I've made an easy one-click (ish) that guides you through it and runs the necessary commands.
Thanks to:
Team Rouge (I used their touch recovery version)
Wolf (For his method to flash recovery!)
Roach (Bootloop fix)
Members here for testing help :] (I'm bad about typos...)
Download here (feel free to mirror):
V0.1- Platypus - 13.42MB
Version 0.1
Mirror - Thanks Alan1995
Mirror 2 - Thanks Alan1995
V0.2- Elephant - 13.39MB
Version 0.2
Mirror - Thanks Alan1995
Mirror 2 - Thanks Alan1995
Mirror 3 - Thanks Alan1995
V0.3- Raptor - 13.39MB
Version 0.3
Mirror - Thanks Alan1995
Mirror 2 - Thanks Alan1995
Mirror 3 - Thanks Alan1995
V0.4- Indri - 13.39MB
Version 0.4
Mirror - Thanks Alan1995
Mirror 2 - Thanks Alan1995
Mirror 3 - Thanks Alan1995
V0.41- TwrpyIndri - 14.29MB
Version 0.41 (TWRP 2.3.2.3)
V0.42- TwrpyIndri Cutting Edge - 14.15MB
Version 0.42 -- Recommended (TWRP 2.5.0.0)
Just unzip it to a folder anywhere and run the .bat file!
Works with or without MicroSD, just let the device totally reboot (E.G. don't let any commands run at the splash screen or in recovery.)
Fixed reboot confusion in V0.2 -Didn't fix in v0.2, Did fix in v0.3 though
If I did anything wrong, or offended any devs, killed someone's cat, or something else, Please let me know!
Post here with any questions or problems, I tested this and everything worked fine, but still consider it as final? release candidate 4.
Did it work?
This should do everything needed, and all is included in zip!
If you want to skip any steps that you've already done if you mess up, just unplug the USB and pretend that it isn't throwing 'device not found' errors, then get back to where you were.
If superuser isn't installing but you have recovery, try 'fix permissions' in recovery. -- Fixed (hopefully) in V0.2
Read the readme and run as administrator! Video-tut is here!
**Also attached to thread.**
PERI - Changelog --
Code:
[*][B]V0.42[/B]
-- Added [I]cutting edge[/I] TWRP 2.5.0.0
-- Thanks jazzruby
[B]V0.41[/B]
-- Added TWRP 2.3.2.3 recovery, finally c:
-- Fixed a couple typos.
-- Fed a llama candy.
[B]V0.4[/B]
-- Added option for ROOT users to just flash recovery.
-- Added unbrick/bootloop fix option for those that can access adb (hopefully works)
-- Bug fix, minor layout change.
-- Second-Last windows release! :D 'Last is auto APX unbrick..' Then the app.
-- Indri
[B]V0.3[/B]
-- Fixed reboot typo that causes failed reboot
-- Other layout issues and typos
-- [I]Added a Readme, read it[/I]
-- Got angry at video recorder for not working.
-- Raptor
[B]V0.2[/B]
-- Fixed a few layout issues and typos.
-- Added driver autoinstaller for Windows 7. (XP Can still use manual)
-- Updated the SU zip I was using, hopefully fixes fake error messages.
-- Fixed reboot confusion (Reordered command layout)
-- Elephant
[B]V0.1[/B]
[I]-- Initial Release[/I]
-- Helps you root and install recovery.
-- Simple mostly automated batch script.
-- Driver install guide too!
-- Reboot bug included!
-- Platypus
[/CENTER]
Tl;DR: This installs recovery and walks you through rooting your device from total stock. It includes everything you need, download is above.
It also functions as a unbrick for soft-bricks where you can access ADB or if your recovery is bootlooping and won't flash anything.
If you already have root: This tool will work on an already rooted tf to install Rouge's latest Touch Recovery (Reads from internal and external)
--if you're in a bootloop and can boot into android via-cold-boot, this will fix it! --
So if anyone who's already rooted doesn't mind doing further testing on it that would be great, the more reports the better!
If the superuser.zip isn't giving you root (For whatever reason ) try flashing the attached SuperSU I packed.
Video:
How to use PERI to root your Transformer!
**coming soon**
Unbricking/fix recovery bootloop:
I added an unbricking help/feature in V0.4 that'll help with bootloops or softbricks. PERI will help you through it.
**If you want to use the 'I'm already rooted just flash recovery' feature, you need to have given adb su access already!!!**
I bricked my tab on purpose using ROM manager to test the unbricker. Seems to work fine, let me know.
It might have bugs though and not work, in which case 'Don't taze me bro!'
I pretty much copy-pasted roach's bootloop fix.
--
If I helped, click thanks!
Thing O Doom isn't responsible for bricks, dead cats, or thermonuclear war. (Although I will help you with the first two. Seek a bomb shelter if you experience the third problem.)
The .bat is open-source, download the .zip and take a look at the .bat with notepad++, if you like.
If you're having driver issues, give USBdeview a looksee.
What does it do, exactly ? You are downgrading and then rooting with it ?
No, it doesn't need to downgrade, it just runs wolf's exploit and directly flashes recovery on your tf. All user data is safe.
If it was a downgrade, the filesize would be alot bigger as I'd have to include a stock ROM.
tried it on my transformer with the latest .24 update but it could not flash the recovery at first time, got error ..... lemme check again
Edit: got error --- "cannot stat 'recoveryblob': No such file or directory" ---
I am sure that I am using the same transformer as yours as mine was imported from USA.
About Guide
Hi all,
I think ıt should be a more detailed guide.
"Just unzip it to a folder anywhere and run the .bat file!" it seems very easy.
I do not want to offend the developers and Thing O Doom
tigerfire25;
you can try that move the blob file internal memory of asus and try again. I an now at work so I can not try the method. I am just suggesting you, do not hope too much
I tried to make with simplicity in mind, so that really is all you need to do:
1. Make folder and extract contents of .zip into it.
2. Run the .bat file, which then holds your hand through the whole process.
3. ???
4. Profit.
EDIT5: Tigerfire, please try with a MicroSD inserted. This may fix it, thanks for reporting back.
Done
Done on my TF101G B90 with .24, it worked but:
1) when it tries to reboot the device (twice during the procedure) it doesn't work, i had to do it manually
2) the installation of the Superuser gives an error like it didn't succed but after reboot it was installed
Anyway thanks
Yeah, the reboot to recovery scripts don't work, it's actually just a simple 'adb reboot' command. I couldn't get 'adb reboot recovery' to work, sorry about that, that's why I detailed the manual instructions in there.
The superuser zip might be borked, but 'fix permissions' in CWM usually removes the error, but if it installed I figure whats it matter? XD
worked for me o/
I now have revolution HD Rom on my .24 TF101
thanks for your help ^^
Hi Thing O Doom,
Nice work and thanks
Thing O Doom said:
I tried to make with simplicity in mind
Click to expand...
Click to collapse
You might be able to automate the process a little better by running the PnP Utility ('PnPutil.exe').
e.g.
Code:
pnputil -i -a %~dp0\adb-drivers\android_winusb.inf
-a - add package
-i - install package
You can skip the install command (-i) if you like (drivers will now be in the 'driver store' (-a) and installed when device is connected).
PnPUtil - TechNet
Thing O Doom said:
The superuser zip might be borked, but 'fix permissions' in CWM usually removes the error, but if it installed I figure whats it matter? XD
Click to expand...
Click to collapse
You might want to try/use the su pkg from HERE
http://goo.im/superuser/Superuser-3.0.7-efghi-signed.zip
It uses a newer 'update-binary' and cleaner/updated 'updater-script' & pkg.
-JR-
Thanks for the pointers, I'll be uploading V0.2 a bit later to fix some of those bugs and automate the process a bit better.
Added V0.2 and Changelog in OP.
Thanks jazzruby for pointers!
@ Thing of Doom
Quarkko,
1. You use the same recoveryblob (Tf101 and Tf101G are very similar, so 3rd method works on both.)
2. You don't need to do anything, as you won't get OTA updates anymore if you install CWM. You can manually flash rooted updates in CWM later if you want to update.
3. Following to the letter, almost 0. You'd have to unplug your tf DURING the flashing of the recoveryblob. (The dd if command)
4. You still can't use NvFlash, since you have a Tf101G, sorry it hasn't been cracked yet.
Clear guide- Use my PERI: one click root and recovery installer (in my sig), it walks you through it and runs the commands for you. Works on the tf101G
Click to expand...
Click to collapse
Thanks for the reply.
I tried your PERI method! But unfortunately I use XP for these jobs. Should I wait for the xp drivers. Thanks anyway.
You can still use PERI with xp, just not the Autoinstall of drivers portion of it. Hit no when it asks to install drivers, then when it gets to the section that asks if a device shows up, hit no and then it will redirect you to a manual install of the ADB drivers.
All it needs are ADB drivers, which are easy enough to install.
TF101/G ONLY! anything else is untested.
does it mean onnly the g version or only the tf101?
kind regards
gandalf
I'll clarify that in the op. It works with both the tf101 and the tf101G, the slider is untested.
Worked for me.
Asus Transformer TF101 | ICS 4.0.3 | Compilation IML74K.WW_epad-9.2.1.24-20120503
Thank You!
xxanthor said:
Done on my TF101G B90 with .24, it worked but:
1) when it tries to reboot the device (twice during the procedure) it doesn't work, i had to do it manually
2) the installation of the Superuser gives an error like it didn't succed but after reboot it was installed
Anyway thanks
Click to expand...
Click to collapse
I have a TF101 serial number starting with 0 and US version. I also have to face with reboot problem twice.
Command Screen say that;
Reboot: Operation not permitted. (both Revovery and Flashing screens)
I used a laptop with operating windows 7 32 bit. After reboot problem, this time I try to exectue the batch file as an administrator but, the laptop can not see the device.
Finally, I reboot my device twice manually. Then, I waited for the final reboot. The final reboot completed. There is no Superuser apk. I get into the recovery menu and I installed by manually.
Thing O Doom said:
I'll clarify that in the op. It works with both the tf101 and the tf101G, the slider is untested.
Click to expand...
Click to collapse
-thanks.. it did it,but no root.-and the recovery- if i trie to go to recovery after pressing vol up i only see the android layinf with a red triangel and exclamation mark.
May i try once more?
Kind regards and sorry for my englisch
By the way :funny comments
Try V0.2, it fixes reboot problems mostly. If it can't see it, then drivers need to be re/installed. Is USB debugging enabled?
So did you manage to get Rouge recovery on there and root?
Hey guys, I have good news for you all. I sat down these days and tried all kinds of exploits and one, normally for the Asus Transformer Prime really works!
Debugfs automated root from sparkym3 provided me full root access to my device. Its simple to use and does all stuff automatic
So it enables Users of the Lenovo ThinkPad Tablet to finally root their device, even if you had it updated to ICS. As you all know, this was not possible before, but after I ran through almost all exploits running anywhere for ICS, I found this one working like a charm.
Have fun!
WARNING!
If you dont know the slightest bit of Windows or Linux shell and never did more than USE the device, be warned... If you kill it, its dead!
emuandco said:
Hey guys, I have good news for you all. I sat down these days and tried all kinds of exploits and one, normally for the Asus Transformer Prime really works!
Click to expand...
Click to collapse
I confirm it works perfectly. ICS TPT _A400_03_0070_0132_US :good:
God, this is so wonderful. CWM works, Koshu's CM10 JB Firmware, too. I LOVE THE DEVICE AGAIN!
Great news! Who might have thought that a working exploit is already out there?
This is wonderful news, a friend of mine recently lost root after he had to send his TPT in for repair and got a new board already updated to ICS.
FANTASTIC - worked on UK running OTA 3.5
Booyah! Thanks Emuandco for your diligence!
Thank you. Had lost hope of root for ICS. My TPT may finally be the tablet I paid for.
22 hours and 5 badly needed factory resets were worth it ^^
Thanks a lot :good: :good: :good:
I just rooted my ThinkPad (WE version). Works like a charm.
emuandco said:
Hey guys, I have good news for you all. I sat down these days and tried all kinds of exploits and one, normally for the Asus Transformer Prime really works!
Debugfs automated root from sparkym3 provided me full root access to my device. Its simple to use and does all stuff automatic
So it enables Users of the Lenovo ThinkPad Tablet to finally root their device, even if you had it updated to ICS. As you all know, this was not possible before, but after I ran through almost all exploits running anywhere for ICS, I found this one working like a charm.
Have fun!
Click to expand...
Click to collapse
wonderful!!!
Thanks a lot!!!
Just tried and it worked!!!
after some trouble installing the adb drivers it worked fine on my WE tablet..finally, awesome, thanks
Amazing how much of a difference having root on this tablet makes.:good:
Stylus and Pressure Sensitivity
Been waiting a long time for this. I had one question that I can't seem to find the answer to. I use my TPT for sketching, allot, it's why I bought the tablet. I was wondering, if I root and then upgrade to Jelly Bean, will I lose stylus and pressure sensitivity?
Can someone post the steps to get this working starting from a clean OTA 4.0.3 rom? I just started messing with the TPT. What boot options are there? I see the hold-down-rotate-and-power boot which looks like what is needed for nvflash, but I can't seem to get any other bootloaders booting here. The debugfs script seems to want to talk to a recovery boot, yes? How do I boot into recovery mode?
Sorry for the TPT newbie questions. Is there a wiki someplace with all the boot modes and other info?
First, load this one: LINK
Its the Driver needed for the TPT to communicate with the PC over ADB protocol.
Go to your TPT Settings below inside Developer Options and check USB Debugging. Attach to your PC and hand the new unknown Device in Device manager the loaded ADB Driver. Then download and unzip everything from the Exploit into a directory; then run RootDebugfs.bat from that directory. This should do it for the rooting of the Stock Firmware. You can verify it by getting "Root Checker" from Play Store. If its green, next load this one: LINK and this one LINK. Its the ClockWorkMod aka modded Recovery Mode making it possible to flash unsigned Updates and making nice Full Backups and the JB Firmware itself.
Install this way from a windows console bein inside the folder where the adb.exe from the exploit is, Step one is making a backup of your previous Recovery Mode for future reverting if you want to do so. Step two is the actual install. You need to copy the loaded recovery.img from the CWM thread to the SD in your TPT, same goes for the JB ZIP File and maybe the 3G Patch for the 3G Card you might have.
BE SURE ALL FILES ARE COPIED ON THE SD AND ITS INSIDE THE TPT AGAIN!
Code:
adb shell
su
dd if=/dev/block/mmcblk0p1 of=/mnt/external_sd/orig_recovery.img
mount -o rw,remount /system
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.backup
dd if=/mnt/external_sd/recovery.img of=/dev/block/mmcblk0p1
exit
exit
This should be enough. Now reboot and while the Lenovo mini Logo shows up, push Vol UP rapidly. This should boot up CWM6, our modded recover Mode. Here Vol UP is upwards, Vol DOWN is downwards and ON/OFF is Enter. First thing, DO A FULL BACKUP TO EXTERNAL SD in "backup and restore", "backup" !!! Then let it do a "wipe data/factory reset", then select "install zip from sdcard" and in there "choose zip from external sdcard". Choose the CM10 JB ZIP first, then the 3G Patch for your Card.
Reboot and youre done.
i have updated to the latest ota and i am not rooted.. A400_03_0070_0132_US
when i run it and choose option 1 the window automatically closes after like 2 seconds
am i supposed to use the asus drivers or what? if anyone can please help...
Somebody buy that man a beer.!!!!!!
Yankies77 - right click on RootDebugfs.bat and choose 'Run as Administrator'
You may get a different result.
pwstein said:
Yankies77 - right click on RootDebugfs.bat and choose 'Run as Administrator'
You may get a different result.
Click to expand...
Click to collapse
I have already tried that doesn't work. when in cmd i write adb devices it shows the device is connected
i have put it to transfer files and MTP settings with unknown sources and debugging on ..when i run the .bat file
after the *demon started successfully* it suddenly closes after which nothing happens..what do you think is wrong?
Open a CMD prompt and run the bat file from there. then show us the output of the script please.
AAND be sure that theres not any adb.exe coming from the system path variable, like in system32 or syswow64. kill these
I got a uk glow worm on the 27th (2 days before release ) and one of the first things that I tried to do was to root with glownooter. Bad idea! I thought that I had bricked my device. I had to use a lot of trickery to recover from a loading screen lock-up and once I did the first thing that I did was backup my nook (Which i should have done before).
UPDATE!
Please try my new ROOT install pack HERE:
http://forum.xda-developers.com/showthread.php?p=34216660#post34216660
This can be used to root and install the most requested things of this thread in just one zip.
Here is a quick guide to most things you will need to do to get started. I will update this guide as I discover and build new modifications.
To Backup and Restore
Follow this guide. Please do this BEFORE any other tinkering!
http://blog.the-ebook-reader.com/20...-and-restore-nook-glow-and-nook-simple-touch/
Its important to check your backup before proceeding! Please listen to roustabout and dont skip this step... He knows what he's talking about
roustabout said:
I'd like to suggest an addition to the backup method that many folks are using - always test your restore, but dont test it (the first time) on your device.
Your backup file should be about 2 gig.
find a 2 gig or larger flash drive or sdcard and restore your backup image to that drive.
when you're done, there should be 8 partitions, as there were on your Nook to begin with.
If you can't get that working - you're not ready to root yet. Until you're sure you can restore, don't start making changes, please.
People turn up all the time having screwed themselves over by restoring a partial backup and not knowing it, or having restored only one partition from a complete backup and having blown out the partition table.
Click to expand...
Click to collapse
Thanks roustabout
To Root!
Make sure you use the CWM file suitable for your SD Card. I used "2gb_clockwork-rc2" because my card was 2gb+.
http://forum.xda-developers.com/showthread.php?t=1360994 (Thanks mali100)
Use WinImage with admin rights to restore CWM virtual hdd image to your SD.
Download tinynoot-1-of-2 and tinynoot-2-of-2
http://forum.xda-developers.com/showthread.php?t=1650593 (Thanks to eded333 and roustabout)
Put on CWM boot SD.
Install them in CWM back to back (I didn't bother with the restart in the middle as it should not make a difference considering the file content). After a restart you should have root access and an android launcher on your 1.2.0 Nook (among other files). If nook fails to boot one of the tinynoot files may have corrupted. Recover, Re-download and Retry!
To Add Apps
Using ADB to install apps is easy. Extract this to your C drive:
http://dl.dropbox.com/u/13673492/ADB + Fastboot + Drivers.zip
Navigate to the folder in a cmd prompt.
Drop your APK into the same folder and on your nook open the "adbwireless" app and enable ADB
That app will tell you what your nooks IP address is.
Then you can:
Code:
adb connect ip.address.of.nook:portnumber
adb install app_of_your_choice.apk
Setup ADB over USB
OK I have taken the liberty of building a quick driver mod to support your nook through USB. It works for me. First you need to have the android SDK if you don't already (sure you do but just in case ).
http://developer.android.com/sdk/index.html
Make sure you tick to install the android USB driver when the SDK is installed.
Browse to extras\google\usb_driver in your SDK folder (wherever you put it) and replace android_winusb.inf with my file:
http://dl.dropbox.com/u/13673492/android_winusb.inf
Next go to C:\Users\your_user_account\.android and replace adb_usb.ini with my file:
http://dl.dropbox.com/u/13673492/adb_usb.ini
In device manager, point google ADB driver to this and hopefully that should get you set up!
To test type
Code:
adb devices
Its working if you get something like this:
Code:
* daemon not running. starting it now on port ____ *
* daemon started successfully *
List of devices attached
[YOUR NOOK] device
And then try
Code:
adb install app_of_your_choice.apk
UPDATE
Install Multitouch Kernel With Overclocking
Install the CWM zip using your clockworkmod SD card
http://forum.xda-developers.com/showthread.php?t=1906507
:good: Thanks to johnjtaylor for discovering that this kernel works works.
Hopefully this more comprehensive guide will get others with this software to start playing around.
If this helps, be polite and say thankyou
Have you setup ADB yet? If you can connect with ADB and get a shell, you can execute a 'df' at the shell prompt to see how much free space is available in each partition. On my NST (no glowlight) apps seem to be installed in /data/app so see how much free space is there. On the NST, this appears to be the same partition that books purchased from B&N are placed in, so if you have a lot of books from B&N, you may have to archive some to install apps. Of course all this is going on the assumption that the NST Glow is similar to the NST in this regard.
David0226 said:
Have you setup ADB yet? If you can connect with ADB and get a shell, you can execute a 'df' at the shell prompt to see how much free space is available in each partition. On my NST (no glowlight) apps seem to be installed in /data/app so see how much free space is there. On the NST, this appears to be the same partition that books purchased from B&N are placed in, so if you have a lot of books from B&N, you may have to archive some to install apps. Of course all this is going on the assumption that the NST Glow is similar to the NST in this regard.
Click to expand...
Click to collapse
Thanks for replying. I'm actually working setting up ADB now. As for books I only just got my nook so all of my titles are epub format on an sd card so i wouldn't think it would be that. As soon as I get ADB set up I will post back my results incase it helps anyone else with this new software version.
Can you look in the documentation that comes with the reader for any reference to 'third party software' or 'GPL software'. They should list where to download / apply for the source code somewhere. Once we can see the source code we can compare it against the existing versions and identify any significant issues.
I set up ADB.
Plenty of space in all partitions including /data for the apps that I want. Managed to install through "adb install some_app_i_want.apk" so problem resides with the amazon app store. Not really an issue for me because I have a specific set of apps that I want and don't need to browse the app store.
I will try to work out what's wrong for others.
staylo said:
Can you look in the documentation that comes with the reader for any reference to 'third party software' or 'GPL software'. They should list where to download / apply for the source code somewhere. Once we can see the source code we can compare it against the existing versions and identify any significant issues.
Click to expand...
Click to collapse
Thanks. I'm looking for it now
No reference to GPL. Only references to third party software are to tell me that my warranty is no longer valid (no surprise there!)
Is there any other place I can find this info thats not the documentation?
loney01843 said:
No reference to GPL. Only references to third party software are to tell me that my warranty is no longer valid (no surprise there!)
Is there any other place I can find this info thats not the documentation?
Click to expand...
Click to collapse
Nothing obvious from the uk.nook.com website. On the US site the 'support' section links to terms of service which contain the links to the open source code (see http://www.barnesandnoble.com/container/nook_lnav.asp?pid=43307 and search for NOOK 1.1.5 OSS Release ), but I can't see an equivalent on the UK site. It's an oversight, but such things happen with a new product launch.
You can email them at [email protected] . The relevant paragraph from the US site is:
1. Notwithstanding anything to the contrary in this Agreement, certain components of the Software are licensed subject to the General Public License Version 2.0, a copy of which is attached as Exhibit A (the "GPL License"). You may not use these components except in compliance with the GPL License. In addition, you may have additional rights with respect to such components under the GPL License, including, without limitation, the right to obtain the source code for such components from us. You may obtain a copy of such source code by contacting us through the contact information provided on the Web Site. We will provide such source code in accordance with the GPL License.
I don't legally have the right to request the source code myself, because I don't own a UK NOOK yet. (Yeah, thinly veiled excuse for laziness!)
staylo said:
Nothing obvious from the uk.nook.com website. On the US site the 'support' section links to terms of service which contain the links to the open source code (see http://www.barnesandnoble.com/container/nook_lnav.asp?pid=43307 and search for NOOK 1.1.5 OSS Release ), but I can't see an equivalent on the UK site. It's an oversight, but such things happen with a new product launch.
You can email them at [email protected] . The relevant paragraph from the US site is:
1. Notwithstanding anything to the contrary in this Agreement, certain components of the Software are licensed subject to the General Public License Version 2.0, a copy of which is attached as Exhibit A (the "GPL License"). You may not use these components except in compliance with the GPL License. In addition, you may have additional rights with respect to such components under the GPL License, including, without limitation, the right to obtain the source code for such components from us. You may obtain a copy of such source code by contacting us through the contact information provided on the Web Site. We will provide such source code in accordance with the GPL License.
I don't legally have the right to request the source code myself, because I don't own a UK NOOK yet. (Yeah, thinly veiled excuse for laziness!)
Click to expand...
Click to collapse
You're obviously not that lazy. Thanks for looking and gathering all of the extra info I need. I'll send B&N an e-mail and see what they say. I wouldn't be surprised if they didn't want to hand it out considering you can use it for an easy root setup and install the amazon and kobo stores which could financially damage their advance into new territories! What are we to do! Can't even subscribe to a newspaper or magazine through the nook store yet!
I'll let you know when / if I get a response
There is a setting in nook touch tools that you need to "arm," to allow software from unknown sources to be installed before the Amazon appstore can install software on a tinynooted device.
The setting is a tickbox, "Allow non-Market apps"
Untick it if it is ticked by default, then re-tick it to get apps to install.
roustabout said:
There is a setting in nook touch tools that you need to "arm," to allow software from unknown sources to be installed before the Amazon appstore can install software on a tinynooted device.
The setting is a tickbox, "Allow non-Market apps"
Untick it if it is ticked by default, then re-tick it to get apps to install.
Click to expand...
Click to collapse
Thanks for the reply but I actually tried that. No joy. However perhaps it is this that is not working and not amazon app store. Im just installing through ADB instead. I wonder if I can enable unknown sources through ADB. Something to look at I guess!
UK tinynoot attempt failing
loney01843 said:
Thanks for the reply but I actually tried that. No joy. However perhaps it is this that is not working and not amazon app store. Im just installing through ADB instead. I wonder if I can enable unknown sources through ADB. Something to look at I guess!
Click to expand...
Click to collapse
I tried using the tinynoot process from roustabout's thread here http://forum.xda-developers.com/showthread.php?t=1650593 and am stuck on the final reboot with a "Your NOOK is starting up..." message. Could you let me know if you used a different tinynoot method/set of files?
smerrett said:
I tried using the tinynoot process from roustabout's thread here http://forum.xda-developers.com/showthread.php?t=1650593 and am stuck on the final reboot with a "Your NOOK is starting up..." message. Could you let me know if you used a different tinynoot method/set of files?
Click to expand...
Click to collapse
Yep thats what I used. You on 1.2.0 and did you back up?
I didn't backup first and to get out of the starting message I used this:
http://forum.xda-developers.com/showthread.php?t=1289233&highlight=restore
Then I made a backup using this:
http://blog.the-ebook-reader.com/20...-and-restore-nook-glow-and-nook-simple-touch/
I hope this helps!
loney01843 said:
Yep thats what I used. You on 1.2.0 and did you back up?
I didn't backup first and to get out of the starting message I used this:
http://forum.xda-developers.com/showthread.php?t=1289233&highlight=restore
Then I made a backup using this:
http://blog.the-ebook-reader.com/20...-and-restore-nook-glow-and-nook-simple-touch/
I hope this helps!
Click to expand...
Click to collapse
Thanks for the tip on screen freeze but the link to the images on that post don't work for me. I am on 1.2 and made a backup before attempting any rooting - have managed to reinstate my original nook so quite pleased with myself.
Is there any point in rooting until someone can find a way of getting apps onto the 1.2 NSTG?
smerrett said:
Thanks for the tip on screen freeze but the link to the images on that post don't work for me. I am on 1.2 and made a backup before attempting any rooting - have managed to reinstate my original nook so quite pleased with myself.
Is there any point in rooting until someone can find a way of getting apps onto the 1.2 NSTG?
Click to expand...
Click to collapse
Great that you got a backup. If you want custom apps you can either wait for a different root kit or push ahead (since you have a safety net).
As I said, it worked for me.
If you don't mind searching for the .apk files you want you can use this:
Code:
adb connect ip.address.of.nook:portnumber
adb install app_of_your_choice.apk
This has worked fine for me so far. Just don't try for custom kernels yet as they seem to give me troubles.
I will work more on this tomorrow including adjusting framework for gapps.
loney01843 said:
Great that you got a backup. If you want custom apps you can either wait for a different root kit or push ahead (since you have a safety net).
As I said, it worked for me.
If you don't mind searching for the .apk files you want you can use this:
Code:
adb connect ip.address.of.nook:portnumber
adb install app_of_your_choice.apk
This has worked fine for me so far. Just don't try for custom kernels yet as they seem to give me troubles.
I will work more on this tomorrow including adjusting framework for gapps.
Click to expand...
Click to collapse
Thanks also for the code but as this is my first foray into rooting I think I'll hang around and watch for a bit! Perhaps if I start learning some more I may feel confident enough to try it.
Do you have copies of the files needed for the factory reset - the links are still not working for me.
Thanks again and sorry for bothering you. Hope tomorrow is productive for you.
smerrett said:
Thanks also for the code but as this is my first foray into rooting I think I'll hang around and watch for a bit! Perhaps if I start learning some more I may feel confident enough to try it.
Do you have copies of the files needed for the factory reset - the links are still not working for me.
Thanks again and sorry for bothering you. Hope tomorrow is productive for you.
Click to expand...
Click to collapse
http://dl.dropbox.com/u/13673492/n2T-Recovery_0.2.img
This is the file needed to force factory reset. However a quality backup like you have is far more important.
For anyone who wants to give this a go, here is a quick guide for root access and app installs using windows tools until I can make something more complete:
Make sure you use the CWM file suitable for your SD Card. I used "2gb_clockwork-rc2" because my card was 2gb+.
http://forum.xda-developers.com/showthread.php?t=1360994
(Thanks mali100)
Use WinImage with admin rights to restore CWM virtual hdd image to your SD.
Download tinynoot-1-of-2 and tinynoot-2-of-2
http://forum.xda-developers.com/showthread.php?t=1650593
(Thanks to eded333 and roustabout)
Put on CWM boot SD.
Install them in CWM back to back (I didn't bother with the restart in the middle as it should not make a difference considering the file content). After a restart you should have root access and an android launcher on your 1.2.0 Nook (among other files). If nook fails to boot one of the tinynoot files may have corrupted. Recover, Re-download and Retry!
Using ADB to install apps is easy. Extract this to your C drive:
http://dl.dropbox.com/u/13673492/ADB + Fastboot + Drivers.zip
Navigate to the folder in a cmd prompt.
Drop your APK into the same folder and on your nook open the "adbwireless" app and enable ADB
That app will tell you what your nooks IP address is.
Then you can:
Code:
adb connect ip.address.of.nook:portnumber
adb install app_of_your_choice.apk
Hopefully this more comprehensive guide will get others with this software to start playing around.
Click thanks if this guides helpful.
loney01843 said:
If nook fails to boot one of the tinynoot files may have corrupted. Recover, Re-download and Retry!
Navigate to the folder in a cmd prompt.
Drop your APK into the same folder and on your nook open the "adbwireless" app and enable ADB
That app will tell you what your nooks IP address is.
Then you can:
Code:
adb connect ip.address.of.nook:portnumber
adb install app_of_your_choice.apk
Hopefully this more comprehensive guide will get others with this software to start playing around.
Click thanks if this guides helpful.
Click to expand...
Click to collapse
Great - thanks to your more detailed instructions, I have persevered and the second attempt at installing the tinynoot zips worked. Your post gave me the confidence to try installing apks for the first time and for anyone else who is unfamiliar with the processes used, I found these two pages useful for:
navigating within a command prompt (how naive): pcstats.com/articleview.cfm?articleid=1723&page=3
Pasting text into a command prompt (ditto): megaleecher.net/Copy_Paste_Text_Dos_Window
Sorry, as a newb I'm not trusted to post outside links yet. It took a couple of attempts of pasting and pressing enter to work out how to install using the adb code but it's not as hard as I expected.
I have tried installing the 1 Mobile Market which works but it is unable to install apps itself (not enough space).
Also, I have just installed NoRefreshToggle and can't seem to get it to work. Any thoughts - is 1.2 to blame? Really want this to work as Business Calendar Free is just a series of blinks at the moment!
Great! I'm glad you pushed onward and have root.
I am going through possibilities of other ways to install apps and mods.
No refresh is something that I would like as well but I think that the framework may need editing for 1.2.0. For fast mode a new kernel will need to be made or existing one modified.
Be aware that installing kernels not designed for this firmware can give you some serious problems.
Once I can setup app markets, I will work on these other modifications.
Stay tuned :good:
Take a look at the overclock kernel - it's got a lot of the norefresh features baked in, and gives you a nice ability to control both clock and kernel tuning (via the governor control.)
You're right, you can flash the two zips back to back with no ill effect, I was mistaken about what the second zip was doing.
I mistyped when I typed "nook touch tools," I meant nook color tools.
I'm very interested that the amazon store is not working in 1.2. I will see if the software's available for my device, so I can try to see what's happened.
As of now, the us bn site does not mention an os 1.2 for the glowlight.