Related
This is copied from the Droid2 section and is said to work on the X for those of us that didnt move SU b4 updating to 2.2 or those that lost root for whatever reason.
Cool How to root the Droid 2
All credit goes to Sebastian Krahmer at http://c-skills.blogspot.com/. Please see fit to donate via Paypal to [email protected]
***NOTE: Proceed at your own risk. I and the providers of this code are not responsible for anything you do to your phone!***
Setup:
- Install adb (here) and Motorola drivers for windows(32-bit or 64-bit)
- Download attached archive
- Extract to a directory, I used c:\Droid2Root
- Make sure you have USB degugging enabled
- Change connection to PC Mode
Process:
- Open command prompt
- cd c:/wherever-your-sdk-tools-folder-is
- adb devices (to verify the connection)
- cd c:/Droid2Root
- adb push Superuser.apk /sdcard/Superuser.apk
- adb push su /sdcard/su
- adb push busybox /sdcard/busybox
- adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin
- adb shell
- cd data/local/tmp
- chmod 0755 rageagainstthecage-arm5.bin
- ./rageagainstthecage-arm5.bin
- let the process run until it 'kicks' you out (may take a minute or two)
- cd c:/wherever-your-sdk-tools-folder-is
- adb devices (to verify the connection)
- adb shell (you should now have a # prompt, if not return to ./rage step above)
- mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
- cp /sdcard/Superuser.apk /system/app/Superuser.apk
- cp /sdcard/su /system/bin/su
- cp /sdcard/busybox /system/bin/busybox
- chmod 4755 /system/bin/su
- chmod 4755 /system/bin/busybox
- mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
- exit
- exit
I'm sure there are certain steps that could be streamlined or eliminated, so please feel free to make a suggestion and I'll edit the post.
Additional thanks to @rainabba and AllDroid.org for their excellent Droid X rooting tutorial, which assisted me greatly in this process.
Attached Files
File Type: rar Droid2Root.rar (954.1 KB, 733 views)
Last edited by karnovaran; Yesterday at 01:58 PM.. Reason: Clarity
Reply With Quote
Hello all...
This worked on my DX that I upgraded to 2.2 just fine. The root pw isn't given anywhere in the instructions as it is in the 2.1 manual root steps.
Any thoughts on the root pw so that I can SSH to the device after rooting?
This method worked for me after thru much trial and error I was able to update to Froyo only to discover I lost root. Did not want to roll back to 2.1 and start over. Thanks so much to everyone who came up with root process and to those who discovered it worked on the DX.
I tried intstalling the 64bit drivers (then rebooted) then hooked it up in PC mode and can't seem to get it to show up in the list of attached devices.
Tried uninstalling and reinstalling everything, the one click roots say it can't find my droid X and going through your instructions adb can't find my device ether. I kinda been having a problem with doubletwist where it doesn't recognize my device properly, could that be related?
I don't know why, but after typing ./rageagainstthecage-arm5.bin it showed the text talking about donations, etc went right back to the $ prompt, and never booted me out of shell. I waited 15 minutes at the $ prompt before Ctrl-break'ing out of shell and trying to relogin. noticed adb is repsonding sluggish. Maybe it's still working? Anyone else having this problem?
Edit: I retried the ./rageagainstthecage-arm5.bin command after rebooting the phone and it worked this time. And I'm rooted! Wireless Tether for Root app works perfectly!
Also I notice when I say PC mode the little debugger icon then doesn't show up like it does in USB mode or charge mode. could this be why the device isn't showing up?
Ok so I manage to get everything good up until the point where I should be looking for a # instead of a $ for terminal. I've done the rage and waited till it kicked me out and went back in and got the same result.
The way that I got through my problems is I set the droid x to USB charge only mode (PC mode there was no debugging and every time I plugged it in, it wouldn't take the ADB driver it wanted a MB810 or something driver)
I know I set the permissions right, and it does run (shows up a little message about donating and in a min or so kicks me out, anything else I can try?
Thanks for the help.
mavermc said:
I tried intstalling the 64bit drivers (then rebooted) then hooked it up in PC mode and can't seem to get it to show up in the list of attached devices.
Click to expand...
Click to collapse
You need to turn off USB debugging first time you connect DX to PC and let the drivers install. After the drivers install, turn on USB debugging and let the driver installation complete again. Then go in terminal (also make sure you change directory to where the adb application is) and type in "adb devices". If your device does not show up, change USB connection method to Windows Media Sync mode on DX and try again.
I hope that helps because that is the limit of my knowledge on the subject.
No reboot, battery pull, then reboot = weird!
Okay, so after I rooted my DX, I went to reboot it (powered off then back on) and it got stuck on the M screen. So I pulled the battery, reinserted it, and then powered on again. It rebooted fine. So...why the battery pull?? Anyone??
So i rooted using this method, (finally got it to work, just used it in usb charge mode on a XP machine) Now my phone seems to drop battery like crazy, all I've changed besides the root is install set cpu (and set some profiles to lower the clock with screen off and low battery and hi temp) installed battery life widget and a little white widget that shows what the current clock speed is. oh and wifi teather, any idea why my battery just sucks now? and things like battery info (to show whats using the battery) force closes on me after root, anyone else with these problems?
read-only what? help!!
is it ppossible to do this from the device?
Will this root work on ota froyo upgrade that we will have in a few days?
Sent from my DROIDX using XDA App
Like many have said it works perfectly if you disable the USB Debugging...install all drivers again and then put it in "Charge Mode"
I finally have my phone rooted...Now I know why my Deodex didnt wanna work. Thanks to all for releasing this and ending my headache
Hi all.
Give a try to my version of the instructions. This is kind of like the holy grail of rooting the Droid 2 at the moment. Much clearer! More info! Enjoy!
http://forum.xda-developers.com/showpost.php?p=7865824&postcount=164
dscottjr81 said:
- ./rageagainstthecage-arm5.bin
- let the process run until it 'kicks' you out (may take a minute or two)
- cd c:/wherever-your-sdk-tools-folder-is
- adb devices (to verify the connection)
- adb shell (you should now have a # prompt, if not return to ./rage step above)
Click to expand...
Click to collapse
One thing I found was after it ran and returned to a cursor, I closed the cmd window and relaunched it and had no issues. Before I restarted I did switch to Charge only w/ USB debug active.
It wouldn't work at all for me until I put the contents of the Droid2Root.rar in my /tools folder. The adb commands would not work as soon as I "cd c:/Droid2Root", but the adb commands would work in the /tools folder. So I just put the contents of the Droid2Root.rar in my /tools folder and it worked just fine. O yea I'm on the OTA 2.2 (2.3.15) that came out today. I also did it under "Charge Only" with debugging.
So I take it that the One-Click root will not work withfroyo 2.2 update????
i continuously get the money sign even after it kicks me out from the ./rage step and i kill-server then adb shell.
its still there even after 3 attempts at the ./rage step what should i do? it just wont (#) prompt me
Evening all,
I am getting very frustrated with my DroidX, since I cannot seem to get it rooted. I believe the crux of my problem lies in that I cannot seem to keep USB Debugging active, even though its enabled. It seems to show up once in awhile, and then just disappears. This does not allow rooters like Z4 to do its job.
I was running the Moto version 5 USB drivers, but backed down to the 4.9 USB drivers and still no luck. Has anyone run into this and can you guide me in rectifying this?
Thanks,
Steve
stevefxp said:
Evening all,
I am getting very frustrated with my DroidX, since I cannot seem to get it rooted. I believe the crux of my problem lies in that I cannot seem to keep USB Debugging active, even though its enabled. It seems to show up once in awhile, and then just disappears. This does not allow rooters like Z4 to do its job.
I was running the Moto version 5 USB drivers, but backed down to the 4.9 USB drivers and still no luck. Has anyone run into this and can you guide me in rectifying this?
Thanks,
Steve
Click to expand...
Click to collapse
what version of Android you have?
I am running VZW stock 2.2.1 but the problem seems to lie in the fact I cannot keep USB debugging on, even though it is enabled on the phone.
Has anyone seen this?
Root your phone without your computer - This would be the path someone on a Mac could take or someone without access to a computer.
This works for the DX and D2 phone, won't work for the D1
Visit the market and get the free Android Terminal Emulator installed.
Visit the market and make sure you have Astro installed.
Grab rageagainsthecage.zip with your phone http://www.droidforums.net/forum/at...s-root-them-unroot-them-rageagainsthecage.zip
Use Astro to navigate to the /sdcard/download folder
Long press on the rageagainstthecage.zip file and "extract to this directory"
The 4 files, from the zip file should now be in the /sdcard/download folder (rageagainstthecage-arm5.bin, su, superuser.apk and busybox.
What are we going to do?
Steps 1- 5: Change to the /tmp folder on your phone, copy the file to the tmp directory, change its permissions. run it, and wait.
Step 6: make sure we can proceed
Steps 7 - 14: make system read-writable, copy the superuser. su and busybox files to where they need to go, use chmode to change their permissions, then make the system folder read-only, and exit Terminal Emulator.
If you want to know more about the commands being used here: cd, cp, chmod, mount, and exit are all Linux commands you can look up on your favorite search engine.
Okay, let's do it - type the blue parts in Terminal Emulator
cd /tmp
cp /sdcard/download/rage*.bin /tmp/
chmod 777 rage*.bin
./rage*.bin
This will take some time, just wait for the $ to show up so you know it is done.
Go to Settings > Applications > Manage Applications > Terminal Emulator > and Force Stop the application
Sanity check - Go into Terminal Emulator again and make sure you have a # symbol as a prompt. If so you are ready to proceed.
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/download/Superuser.apk /system/app/Superuser.apk
cp /sdcard/download/su /system/bin/su
cp /sdcard/download/busybox /system/bin/busybox
chmod 4755 /system/bin/su
chmod 4755 /system/bin/busybox
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
exit
For USB debugging, it might be your usb connection type. Try changing it to computer, mass storage, etc, until you find what's stable. I used Z4root when I did mine. Took like 2 minutes, and no computer, no terminal commands, true one-click root. Don't have the APK anymore, since I've moved on to the Bolt, sorry. But a google search should pull it up.
Thanks to all. I am now rooted. Woo hoo!
So thecubed made a great tool to root, but the .bat file is intended for PC use. I'm on a Mac.
Could anyone extrapolate the adb commands used in that file? I'm familiar with adb and would have no issues with following the commands, I just can't seem to see exactly what the .bat file does.
tldr: what are the adb commands needed to root using his files? I can take it from there.
I'd love to know as well.
Sent from my VS980 4G using Tapatalk 4
mjdupuis said:
So thecubed made a great tool to root, but the .bat file is intended for PC use. I'm on a Mac.
Could anyone extrapolate the adb commands used in that file? I'm familiar with adb and would have no issues with following the commands, I just can't seem to see exactly what the .bat file does.
tldr: what are the adb commands needed to root using his files? I can take it from there.
Click to expand...
Click to collapse
Here, I put the whole .bat file text, you should be able to figure it out.
@echo off
echo.
echo **************************************
echo Easy root for LG G2
echo Supports ATT, TMO, VZW, and KT Variants
echo Repackaged by IOMonster
echo See http://tinyw.in/mXhw for details
echo **************************************
echo.
echo.
echo Credit to http://optimusforums.com/threads/how-to-root-the-lg-g2-f320.8846/
echo.
echo.
pause
echo Looking for device...
.\adb.exe wait-for-device
echo Determining carrier...
for /f %%i in ('.\adb.exe shell getprop ro.build.target_operator') do set RESULT=%%i
if %RESULT%==ATT GOTO ATTTMORoot
if %RESULT%==TMO GOTO ATTTMORoot
if %RESULT%==VZW GOTO VZWRoot
if %RESULT%==KT GOTO KTRoot
echo.
echo.
echo No matching phone found. Got %RESULT% from ADB.
pause
:ATTTMORoot
echo Found ATT or TMO phone!
echo Pushing g2_security...
echo.
.\adb.exe push g2_security /sdcard/g2_security
GOTO RootStep2
:VZWRoot
echo Found VZW phone!
echo Pushing VZW g2_security...
.\adb.exe push g2_security_vzw /sdcard/g2_security
GOTO RootStep2
:KTRoot
echo Found KT F320k phone!
echo Pushing ytiruces_1a ...
.\adb.exe push ytiruces_1a /sdcard/ytiruces_1a
GOTO RootStep2
:RootStep2
echo.
echo.
echo *******************************************************
echo Now, please unplug usb, go to developer options and
echo disable USB debugging and re-enable it.
echo Once you've done that, re-plug your usb...
echo *******************************************************
pause
echo Waiting for device...
.\adb.exe wait-for-device
echo Now it's time to install su and superuser.
echo.
echo Please note! This will trip LG's rootchecker!
echo.
echo This means your phone will show ROOTED in the settings menu,
echo and in the LG Download mode.
echo.
echo If you do not want to possibly invalidate your warranty
echo press CTRL-C to stop this script.
echo You will have a rooted ADB, but no apps on the phone will be able
echo to access root functions.
echo.
pause
echo.
echo.
echo Mounting system RW and pushing SU, then remounting system RO again
.\adb.exe shell "mount -o remount,rw /system"
.\adb.exe push su /system/xbin/su
.\adb.exe shell "chown 0.0 /system/xbin/su;chmod 06755 /system/xbin/su;sync;mount -o remount,ro /system"
echo Installing superuser
.\adb.exe install superuser.apk
echo.
echo.
echo ***************************************************
echo Done.
echo ***************************************************
echo.
echo Please check the above for any errors and let me know if you run into any issues.
echo Enjoy your phone!
pause
Click to expand...
Click to collapse
wargreymon89 said:
Here, I put the whole .bat file text, you should be able to figure it out.
Click to expand...
Click to collapse
If anyone can't, they don't need to root.
If you know your carrier, skip all the carrier detect crap and go straight to pushing the correct root.
Then wait and push Su and the rest.
It's a pretty simple root via adb manually.
I just want tethering to work before I run out and get one.
Thank you very much!
I'm having trouble getting debug mode on my mac. Any suggestions? SDK Tools are updated and USB Debugging is checked...
Did you select internet and then Ethernet when you connect your USB?
mjdupuis said:
Did you select internet and then Ethernet when you connect your USB?
Click to expand...
Click to collapse
Your a boss!
wargreymon89 said:
Here, I put the whole .bat file text, you should be able to figure it out.
Click to expand...
Click to collapse
By the way, this worked out just fine. I couldn't get it to work the first time around because the original method by thecubed didn't work with the ota. His update worked. Thank you, again.
A Mac root method (not automated)
I posted this in another Q&A thread, just wanted the answer to be available if someone may be following this. The two thread might need to be combined.
WARNING! This is just what worked for me, and it's just the adb commands from thecubed's program. All credit goes to him, I didn't do any of this, just took the info from it.
Here's the thread: http://forum.xda-developers.com/showthread.php?t=2448887
Download it, unzip it, and then take a moment to go back and thank him if you didn't do that.
You are not actually using his program, just the files and commands. Everything is done using Terminal and the Finder. You must have ADB working, look elsewhere for instructions on setting that up.
The files used here are the Verizon versions of the files, which I used for my phone. They are also specific to the OTA'd Verizon software, "11A" so there are different files if you haven't installed the OTA. These commands are correct, but the files being pushed aren't all the same between different carrier models and do not work with any other carrier. All the right stuff for other carriers is contained in thecubed's program.
The bold sections are files you need to send over adb, you can manually enter the file pathway or drag the files from finder into terminal after the adb commands (and before you type the destinations).
One more warning; if this is your first time using adb or terminal, I don't recommend this as your first try. It's super easy to screw something up in terminal.
Your phone must have developer options enabled and usb debugging on. Plug in your phone via usb and select "Internet" and then "Ethernet."
adb push ytiruces_1a_vzw /sdcard/ytiruces_1a
Unplug usb, disable USB debugging and then re-enable it. Plug USB back in.
adb shell "mount -o remount,rw /system"
adb push su /system/xbin/su
adb shell "chown 0.0 /system/xbin/su;chmod 06755 /system/xbin/su;sync;mount -o remount,ro /system"
adb install superuser.apk
exit
I see there are step by step videos for windows but none for Mac yet. I've rooted my last two phones but I followed videos which showed the exact process. I'm hoping someone eventually posts a Mac walk through video for the less confident users such as me.
I'm trying to follow the steps. When I run ./adb devices it lists my phone but says offline next to it. any ideas?
If you're on a Mac there's no "./" just "adb devices". You can't follow the commands in the .bat file without making those adjustments. Did you try following the commands in my post?
black05x5 said:
I'm trying to follow the steps. When I run ./adb devices it lists my phone but says offline next to it. any ideas?
Click to expand...
Click to collapse
You need to be sure USB debugging is on, that you selected Internet>Ethernet when connected to USB, and my phone asked me if I wanted to allow connections from my computer. If all these are set up correctly it should work.
I have usb debugging on. My phone did ask me to confirm connection which I did. Then when I type ./adb devices it lists my phone but still says offline next to it. Being a noob at this I'm really stumped.
mjdupis can you please clarify what you mean when you say I don't need to type ./ before the command? My understanding was I always had to do this on a Mac?
black05x5 said:
mjdupis can you please clarify what you mean when you say I don't need to type ./ before the command? My understanding was I always had to do this on a Mac?
Click to expand...
Click to collapse
The "/" is what you would use to point to a filepath. Like /Home/Library/Root or a file on the phone /System. If you look at the commands I listed there are no ./ before any adb commands, that's a windows thing.
Terminal tells me there's no such directory when I put ./ before adb commands, because it thinks I'm trying to direct it to an adb folder.
I reinstalled everything and now its finally recognizing my phone. Now I just have to figure out how to do this. Sorry to keep asking, but can someone confirm if this is right...
Now that it recognizes my phone
I type adb push then drag the file ytiruces_1a_vzw into terminal and then type /sdcard/ytiruces_1a and hit enter.
Then unplug the cord from phone, turn of debugging and back on then plug the cord back in. then select internet ethernet to activate debugging.
Then type adb shell and hit enter.
Then type mount -o remount,rw /system and hit enter.
Is this correct so far??
thanks for your help!!
---------- Post added at 10:54 PM ---------- Previous post was at 10:15 PM ----------
Actually, looks like I figured it out. Got phone rooted... Thanks again for the help!
Could use your help again! Got my phone rooted and installed TWRP. Everything was working great. Running stock rom. Only mod I had done was the black notification bar. I installed an app from the market called LCD Density. Tried changing my phone from 320 to 300. It then reboots the phone for it to take affect. My phone is now stuck in a bootloop on the LG logo screen with the LED flashing. I can get into TWRP but the problem is I never made a back up or downloaded a rom onto the phone as I hadn't planned to flash any roms. Is there any way I can get a rom onto my phone so I can then flash it in TWRP? I have a Mac.. Thanks for any help...
Got it fixed! Was finally able to connect to my Mac. Then put a rom on the phone using ADB and flashed the rom.
Does anyone here have any tools or guides on how I can achieve root on my Verizon LG G2 on my mac in terminal or via a tool like this one which seems to only be windows based: http://forum.xda-developers.com/showthread.php?t=2448887
I don't have access to a windows machine at home that I can use to get root on my LG G2. I would really appreciate it if someone could make a guide (Text or Youtube even better) or a root tool like the one I linked to above. I'm not trying to be a mac snob which I'm not...I just do a lot of design work and photo editing and have used Mac's since I find that most of the studios I deal with all use them and I need to be able to exchange files that are compatible. I would really appreciate some help with regards to doing this on my MAC. Thanks for listening and I hope someone can point me in the right direction.
Thanks again.
I'm also looking for a Mac solution. I'm a long time Android user but have a Macbook. Hoping someone comes up with Mac version.
I used the method by thecubed in the development section. I unzipped it and followed the adb commands in the .bat file (right click that file, open with text editor). Don't forget the part about unplugging the USB cable and disabling and then enabling debugging.
mjdupuis said:
I used the method by thecubed in the development section. I unzipped it and followed the adb commands in the .bat file (right click that file, open with text editor). Don't forget the part about unplugging the USB cable and disabling and then enabling debugging.
Click to expand...
Click to collapse
But, did you do it on a Mac?
Thank you Devs. From my LG G2.
Yes, all through terminal.
I can post the specifics, but I'm not a developer and most likely could not help you if you or I happen to mess something up.
That would be great if you could post the specifics. Would really love to see how you did it.
WARNING! This is just what worked for me, and it's just the adb commands from thecubed's program. All credit goes to him, I didn't do any of this, just took the info from it.
Here's the thread: http://forum.xda-developers.com/showthread.php?t=2448887
Download it, unzip it, and then take a moment to go back and thank him if you didn't do that.
You are not actually using his program, just the files and commands. Everything is done using Terminal and the Finder. You must have ADB working, look elsewhere for instructions on setting that up.
The files used here are the Verizon versions of the files, which I used for my phone. They are also specific to the OTA'd Verizon software, "11A" so there are different files if you haven't installed the OTA. These commands are correct, but the files being pushed aren't all the same between different carrier models and do not work with any other carrier. All the right stuff for other carriers is contained in thecubed's program.
The bold sections are files you need to send over adb, you can manually enter the file pathway or drag the files from finder into terminal after the adb commands (and before you type the destinations).
One more warning; if this is your first time using adb or terminal, I don't recommend this as your first try. It's super easy to screw something up in terminal.
Your phone must have developer options enabled and usb debugging on. plug in your phone via usb and select "Internet" and then "Ethernet."
adb push ytiruces_1a_vzw /sdcard/ytiruces_1a
Unplug usb, disable USB debugging and then re-enable it. Plug USB back in.
adb shell "mount -o remount,rw /system"
adb push su /system/xbin/su
adb shell "chown 0.0 /system/xbin/su;chmod 06755 /system/xbin/su;sync;mount -o remount,ro /system"
adb install superuser.apk
exit
thanks for this.
I used parallels installed Windows 7 I could have drove home and grabbed my laptop but that would have been to easy lol.
But now my mom is happy to see Windows android and osx lion on a 2009 MacBook pro I was surprised how well it went I thought I was going to have driver issues or something would go wrong but it was like I was using a straight up Windows 7 laptop. If that program was available for ubuntu a lot if people would be happy campers ?
Sent from my LG-D800 using XDA Premium 4 mobile app
I thought it would be a nightmare as obviously lg doesn't provide USB drivers for Mac. Color me surprised Mac doesn't need drivers!
Although I'm still not rooted, but that's phone version related
Sent from my LG-F320L using XDA Premium 4 mobile app
back to stock
I am needing to flash this thing back to stock so I can take it to the Verizon Store for an exchange. All I really have is a Mac.... I'd really like to know how to flash it back to stock, unrooted. I have some experience, but please be very clear as I really don't want to mess up. Thanks in advance for anyone willing to help.
mjdupuis said:
WARNING! This is just what worked for me, and it's just the adb commands from thecubed's program. All credit goes to him, I didn't do any of this, just took the info from it.
Here's the thread: http://forum.xda-developers.com/showthread.php?t=2448887
Download it, unzip it, and then take a moment to go back and thank him if you didn't do that.
You are not actually using his program, just the files and commands. Everything is done using Terminal and the Finder. You must have ADB working, look elsewhere for instructions on setting that up.
The files used here are the Verizon versions of the files, which I used for my phone. They are also specific to the OTA'd Verizon software, "11A" so there are different files if you haven't installed the OTA. These commands are correct, but the files being pushed aren't all the same between different carrier models and do not work with any other carrier. All the right stuff for other carriers is contained in thecubed's program.
The bold sections are files you need to send over adb, you can manually enter the file pathway or drag the files from finder into terminal after the adb commands (and before you type the destinations).
One more warning; if this is your first time using adb or terminal, I don't recommend this as your first try. It's super easy to screw something up in terminal.
Your phone must have developer options enabled and usb debugging on. plug in your phone via usb and select "Internet" and then "Ethernet."
adb push ytiruces_1a_vzw /sdcard/ytiruces_1a
Unplug usb, disable USB debugging and then re-enable it. Plug USB back in.
adb shell "mount -o remount,rw /system"
adb push su /system/xbin/su
adb shell "chown 0.0 /system/xbin/su;chmod 06755 /system/xbin/su;sync;mount -o remount,ro /system"
adb install superuser.apk
exit
Click to expand...
Click to collapse
you wouldnt happen to know which files in there are for the tmobile g2 would you? im also trying to root on mac.
You'll have to look in the .bat file, it will show which file needs to be used for T-Mobile.
mjdupuis said:
WARNING! This is just what worked for me, and it's just the adb commands from thecubed's program. All credit goes to him, I didn't do any of this, just took the info from it.
Here's the thread: http://forum.xda-developers.com/showthread.php?t=2448887
Download it, unzip it, and then take a moment to go back and thank him if you didn't do that.
You are not actually using his program, just the files and commands. Everything is done using Terminal and the Finder. You must have ADB working, look elsewhere for instructions on setting that up.
The files used here are the Verizon versions of the files, which I used for my phone. They are also specific to the OTA'd Verizon software, "11A" so there are different files if you haven't installed the OTA. These commands are correct, but the files being pushed aren't all the same between different carrier models and do not work with any other carrier. All the right stuff for other carriers is contained in thecubed's program.
The bold sections are files you need to send over adb, you can manually enter the file pathway or drag the files from finder into terminal after the adb commands (and before you type the destinations).
One more warning; if this is your first time using adb or terminal, I don't recommend this as your first try. It's super easy to screw something up in terminal.
Your phone must have developer options enabled and usb debugging on. plug in your phone via usb and select "Internet" and then "Ethernet."
adb push ytiruces_1a_vzw /sdcard/ytiruces_1a
Unplug usb, disable USB debugging and then re-enable it. Plug USB back in.
adb shell "mount -o remount,rw /system"
adb push su /system/xbin/su
adb shell "chown 0.0 /system/xbin/su;chmod 06755 /system/xbin/su;sync;mount -o remount,ro /system"
adb install superuser.apk
exit
Click to expand...
Click to collapse
Haven't used adb before, but I'm no noob to rooting /flashing. I got adb installed and working on my computer now (running Ubuntu). After I launch adb in the terminal, then I just type these commands? (copy paste?)
You could only copy and paste if you have a Verizon g2 with the ota update, if it's any other version you'll be using different files than the ones I have used.
Yeah, I have the Verizon g2 and I guess it's got the ota... There are no pending updates right now
Two problems on mac
I'm getting two error messages. The first is a line 2 error on the g2 security. The second is 'operation not permitted' for a mount command. Anyone have any solutions?
elcapitano21 said:
I'm getting two error messages. The first is a line 2 error on the g2 security. The second is 'operation not permitted' for a mount command. Anyone have any solutions?
Click to expand...
Click to collapse
does anyone know how to fix the device offline error whenever i try in input the first command?
Bump
Sent from my VS980 4G using XDA Premium 4 mobile app
It took some doing, but after following the instructions in this link:
http://forum.xda-developers.com/showthread.php?t=2559915
I was finally able to root my Nook Glowlight. The instructions are kind of sprawled out and extremely unclear so I will sum up.
As always, you will need the ADB. In order to install the ADB, you need the Java Development Kit and the Android Studio (formerly known as the Android SDK)
http://www.oracle.com/technetwork/java/javase/downloads/index.html
http://developer.android.com/sdk/installing/studio.html
How to obtain root via ADB: The ONLY way you can root is using Windows. I was successful on Windows 7 32 bit, but it may be possible on other versions.
step 1) install bootloader driver.
You need to grab the drivers from here (bnusbdrivers.zip):
http://forum.xda-developers.com/showpost.php?p=49665945&postcount=279&nocache=1&z=184593200683593
then, open the Device Manager (on Windows). Be ready to right click on the new device 'omap3660' that shows.
With the nook turned completely off, plug in a USB cable. you will have less than 3 seconds to right click the new omap3660 device that shows up in the system profiler.
If you were successful and you right clicked on it in time, manually install the Barnes & Noble USB driver (there are entries added to the generic Google drivers for both the TI Omap 3660 bootloader and the ADB device after you modify the uRamdisk later on)
***NOTE***
If you WEREN'T successful on your first try (took me THREE times to get to it in time), you aren't going to get another chance to install the drivers. At least not easily anyway, because after Windows tries to automatically install the drivers for the bootloader and fails, it will disregard the device any time it shows up after that. So, you are going to need to delete the registry entries that it created, which in my experience was easier said than done. Even admin access was not sufficient to make the necessary changes to the registry.
You will need to launch regedit.exe using another tool called psexec which is available here:
http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx
after you download the pstools package, copy those .exe files to C:\Windows\System32\ (in order to add them to $PATH in cmd.exe)
Then, once you've installed the pstools commands to C:\Windows\System32\, run cmd.exe as admin (right click it and select 'run as administrator') and then open regedit.exe with the following command
Code:
psexec -s -i -d regedit.exe
Then, once regedit is open you need to find the keys created by the Nook bootloader and delete them. The Nook bootloader's device ID is 0451:d00e
You are going to be looking in HKEY_LOCAL_MACHINE\Current Control Set\enum\usb\ for the keys with the bootloader's device IDs. There may also be keys generated in control set 001 and 002 as well. Delete all of those keys and then reboot your computer. Then with the nook power off completely, repeat the process from the first step. eventually you will be successful installing the bootloader driver.
Step 2) temporarily boot with uRamdisk-noogie
you need to download omaplink.exe from here:
http://www.temblast.com/android.htm
and you also need to download the four files which allow you to temporarily mount the boot partition; omap3_aboot.bin, u-boot-ng2-exp-v03.bin, uImage-ng2-130-stk and uRamdisk-noogie.
They are available here:
http://forum.xda-developers.com/showpost.php?p=49779966&postcount=285
download usbboot-ng2-images-noogie-v1.zip
The next part is easy.
Extract the .zip file and then fire up cmd.exe. cd into the directory of the newly extracted .zip
in the new working directory, enter the command
Code:
omaplink omap3_aboot.bin u-boot-ng2-exp-v03.bin uImage-ng2-130-stk uRamdisk-noogie
Then, with the Nook powered all the way off and omaplink running, plug it in and a few seconds later, after the device boots up all the way, you will be looking at the contents of the boot partition instead of the internal storage like normal.
Step 3) Edit uRamdisk
you will need to download bootutil.exe from here
http://www.temblast.com/android.htm
copy bootutil.exe to C:\Windows\System32
with the boot partition mounted, copy uRamdisk to your computer and extract the files init.rc and default.prop, eg;
Code:
bootutil /x /v uRamdisk init.rc default.prop
then using notepad++ (available here: http://notepad-plus-plus.org/) edit the files as follows
default.prop
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
and
init.rc
comment out lines 375 and 392-399
(do this by adding a # to the beginning of the line)
uncomment line 215
(do this by deleting the # at the beginning of the line)
save both files and then repack them into uRamdisk
Code:
bootutil /r /v uRamdisk init.rc default.prop
copy uRamdisk back onto the Nook, eject the disk and power off the device. Reboot and you should be able to connect to ADB via WiFi
eg;
Code:
adb connect 192.168.0.10
replacing '10' with whatever IP your Nook is grabbing from your router.
Step 4) Full Root
at this point, you have root access via ADB only. You will not have root access in any apps like Root Explorer, Terminal, TiBackup, etc.
In order to finish PROPERLY rooting your Nook, you need to install 'su' to /system/bin/ and install the superuser.apk
Code:
adb connect 192.168.0.10
adb shell mount -o remount, rw /system
adb push su /system/bin/
adb shell chmod 6755 /system/bin/su
adb install superuser.apk
reboot your device one more time and then you will be fully rooted.
*** Note ***
this devices firmware seems to be a strange hybrid between donut and eclair, although it purports itself to be Android 2.1. The Superuser.apk and su binary came from an old Cyanogenmod 4.6 build in case anyone was wondering (Android Donut). The ones from Cyanogenmod 5 (Android Eclair) do not work. you will get the 'install failed older sdk' error.
installing busybox
I tired installing busybox by using the stericson busybox pro.apk. It would always freeze at 6.47%.
I figured out that if I grabbed an older version of the busybox binary and pushed it to /system/xbin manually and then chmodded it to the proper permissions, auto updates and proper symlinking work using the busybox app
Code:
adb shell mount -o remount, rw /system
adb shell mkdir -p /system/xbin
adb push busybox /system/xbin
adb shell chmod 6755 /system/xbin/busybox
adb install busybox.apk
Then reboot, and run the busybox app to update and create symlinks.
enjoy!
installing nano and bash
Code:
adb connect 192.168.0.10
adb shell
mount -o remount, rw /system
adb push nano /system/xbin/
chmod 6755 /system/xbin/nano
adb push bash /system/xbin/
chmod 6755 /system/xbin/bash
bash
mv /system/bin/sh /system/bin/sh.bak
ln -s /system/xbin/bash /system/bin/sh
chmod 6755 /system/bin/sh
adb push profile /system/etc/
adb push terminfo /system/etc/
and then in terminal emulator under 'Preferences' change the initial command to
Code:
export TERMINFO=/system/etc/terminfo;export TERM=linux;export HOME=/sdcard;
and finally
Code:
adb push bashrc /sdcard
adb shell
mv /sdcard/bashrc /sdcard/.bashrc
exit
nano works just fine via ADB, but because of lack of 'ctrl' key (and physical buttons to assign it to) you won't be able to write files (ctrl+o) using the terminal on your nook. But between having full proper root access, busybox, a proper bash terminal emulator and nano for editing config files, this should REALLY extend the usefulness of your Nook Glowlight. It should work just fine on other versions of Nook too.
Hi N00b-un-2,
Many thanks for your summary!
There is one important edit that I think you missed,
in init.rc you also need to:
Line #375, comment out "disabled" with a # at the start of the line.
(see http://forum.xda-developers.com/showthread.php?p=49070213#post49070213)
without this I couldn't get adb to connect.
And since you already made it very noob friendly, might I suggested you clarify:
Line #215 remove # to enable adb over wifi
(rather than search for 5555)
Also, I'm not expert, but I believe the commands to get superuser on the device are (at least it worked for me):
adb connect 192.168.x.x
adb shell mount -o remount, rw /system
adb push su /system/bin/
adb shell chmod 6755 /system/bin/su
adb install superuser.apk
Finally, I'm not sure if this is important, but maybe remount system as read only again:
adb shell mount -o remount, ro /system
Thanks again, nice work!
---------- Post added at 01:48 PM ---------- Previous post was at 01:10 PM ----------
Hi again,
had similar issues with installing busybox, here's what worked for me (note needed to run su to create dir):
adb shell mount -o remount, rw /system
adb shell /system/bin/su
adb shell mkdir -p /system/xbin
adb push busybox /system/xbin
adb shell chmod 6755 /system/xbin/busybox
adb install busybox.apk
cheers.
As far as remounting /system as ro, I would HIGHLY recommend just rebooting at this point, otherwise your nook might be stuck in a weird pseudo-rooted state. Probably won't cause any problems, but why risk it?
Thanks for clarifying the line number. I will make the appropriate edits to my instructions. I was working off the top of my head and couldn't remember what exact line the ADB over TCP config was, as I just used ctrl+w '5555' to find it myself.
There are several pre-edited uRamdisk images floating around the forum with various features enabled which would be easier for noobs than extracting the config files and manually editing and then repacking them. In the future I'll probably throw those on here as well.
darz said:
Hi N00b-un-2,
Many thanks for your summary!
There is one important edit that I think you missed,
in init.rc you also need to:
Line #375, comment out "disabled" with a # at the start of the line.
(see http://forum.xda-developers.com/showthread.php?p=49070213#post49070213)
without this I couldn't get adb to connect.
And since you already made it very noob friendly, might I suggested you clarify:
Line #215 remove # to enable adb over wifi
(rather than search for 5555)
Also, I'm not expert, but I believe the commands to get superuser on the device are (at least it worked for me):
adb connect 192.168.x.x
adb shell mount -o remount, rw /system
adb push su /system/bin/
adb shell chmod 6755 /system/bin/su
adb install superuser.apk
Finally, I'm not sure if this is important, but maybe remount system as read only again:
adb shell mount -o remount, ro /system
Thanks again, nice work!
---------- Post added at 01:48 PM ---------- Previous post was at 01:10 PM ----------
Hi again,
had similar issues with installing busybox, here's what worked for me (note needed to run su to create dir):
adb shell mount -o remount, rw /system
adb shell /system/bin/su
adb shell mkdir -p /system/xbin
adb push busybox /system/xbin
adb shell chmod 6755 /system/xbin/busybox
adb install busybox.apk
cheers.
Click to expand...
Click to collapse
N00b-un-2 said:
There are several pre-edited uRamdisk images floating around the forum with various features enabled which would be easier for noobs than extracting the config files and manually editing and then repacking them. In the future I'll probably throw those on here as well.
Click to expand...
Click to collapse
Would have been good if I could have easily found a pre-edited image, but your instructions were a great alternative, thanks again
darz said:
Would have been good if I could have easily found a pre-edited image, but your instructions were a great alternative, thanks again
Click to expand...
Click to collapse
Sorry for the really noob question, I have rooted, wifi adb running and installed apps as per your instructions, but I can't seem to access any of it on the nook. How can I get access to the launcher I installed?
You mentioned pre-edited images, do any of those come with the apps I need to get access to a custom launcher?
Cheers,
Dariusz
==============
Updated: All sorted
==============
For some reason had some issues with ADW launcher, Launcher pro worked fine.
ps I think I made a mistake with the su step I suggested, if you run a one line shell command I don't think it keeps su privileges, so I believe you need to run commands within the shell as per below:
adb shell
mount -o remount, rw /system
/system/bin/su
mkdir -p /system/xbin
exit
adb push busybox /system/xbin
adb shell chmod 6755 /system/xbin/busybox
adb install busybox.apk
Noob
Hey guys any instructions noob friendly or a video in youtube,i stick up at dab connect 192.168.0.10.I dos't have a Windows PC and using Mac whit Parallels Desktop.Is it possible instructions for Mac?
The above instructions from N00b-un-2 should work fine running a vm with parallels on your Mac.
OB
Sent from my SPH-D710VMUB using Tapatalk 2
valentin1985 said:
Hey guys any instructions noob friendly or a video in youtube,i stick up at dab connect 192.168.0.10.I dos't have a Windows PC and using Mac whit Parallels Desktop.Is it possible instructions for Mac?
Click to expand...
Click to collapse
Before you perform the adb connect step you need to find out what your IP address is:
On your nook, click on the settings icon in the top right corner and then select "Change"
Under Wireless Networks, select the wifi name that you are already connected to (where it says "Connected to the internet")
This will display your connection details, remember that IP address
Now go back to your pc and type:
adb connect [IP address]
darz said:
Before you perform the adb connect step you need to find out what your IP address is:
On your nook, click on the settings icon in the top right corner and then select "Change"
Under Wireless Networks, select the wifi name that you are already connected to (where it says "Connected to the internet")
This will display your connection details, remember that IP address
Now go back to your pc and type:
adb connect [IP address]
Click to expand...
Click to collapse
BIG HINT! If you're using Powershell ISE, you have to type .\adb.exe connect [IP address] or else it won't recognize "adb" as an executable!
Don't ask why, because I don't know. :?
thenookieforlife3 said:
BIG HINT! If you're using Powershell ISE, you have to type .\adb.exe connect [IP address] or else it won't recognize "adb" as an executable!
Don't ask why, because I don't know. :?
Click to expand...
Click to collapse
So far so good,but now what?
valentin1985 said:
So far so good,but now what?
Click to expand...
Click to collapse
I just gave a little tip on Powershell ISE. I do not know much about the Nook GlowLight rooting process, as I have a NSTG, not a NG. Ask someone else.
thenookieforlife3 said:
I just gave a little tip on Powershell ISE. I do not know much about the Nook GlowLight rooting process, as I have a NSTG, not a NG. Ask someone else.
Click to expand...
Click to collapse
Yes,i try whit dis command .\adb.exe connect 192.168.0.9 but result is the same.
valentin1985 said:
Yes,i try whit dis command .\adb.exe connect 192.168.0.9 but result is the same.
Click to expand...
Click to collapse
But that's okay! What I said was, if you are using the command program Powershell ISE, do it that way instead. But you are just using cmd.exe, not Powershell ISE!
In cmd.exe, which is what you are using, it is not neccessary to type .\adb.exe. Just type adb.
From there, ask someone else in this thread.
thenookieforlife3 said:
But that's okay! What I said was, if you are using the command program Powershell ISE, do it that way instead. But you are just using cmd.exe, not Powershell ISE!
In cmd.exe, which is what you are using, it is not neccessary to type .\adb.exe. Just type adb.
From there, ask someone else in this thread.
Click to expand...
Click to collapse
I prefer to use ConEmu or Console2 when I am forced to use Windows. Not a big fan of CMD.EXE or Powershell/PowershellISE. there are plenty of other CLI alternatives out there
N00b-un-2 said:
I prefer to use ConEmu or Console2 when I am forced to use Windows. Not a big fan of CMD.EXE or Powershell/PowershellISE. there are plenty of other CLI alternatives out there
Click to expand...
Click to collapse
Well, as I ONLY use Windows and Powershell ISE has a nice-enough layout for my purposes, I use it. That's why I gave a tip on it.
Actually on a lot of installs just typing adb in the command console won't work either unless it's got the path variable set up correctly, I find it easiest to just right click and choose run as administrator, no need for the path to be setup.
OB
Sent from my SPH-D710VMUB using Tapatalk 2
FW 1.2.1
Hi guys,
thanks for creating this thread. I was wondering if this rooting procedure was tested with the firmware 1.2.1 ?
real-6 said:
Hi guys,
thanks for creating this thread. I was wondering if this rooting procedure was tested with the firmware 1.2.1 ?
Click to expand...
Click to collapse
This rooting procedure is for the new Nook GlowLight with firmware 1.3.1. Your device is a Nook Simple Touch with GlowLight, which can be rooted very easily using the rooting package here.