Related
If anyone can post a link to a detailed Ubuntu guide for newbies to root the Hero and remove stock apps, I would appreciate it. The guide posted doesn't go into too much detail in Ubuntu since the OP said that he could not get it to work in Ubuntu. Thanks.
killabee44 said:
If anyone can post a link to a detailed Ubuntu guide for newbies to root the Hero and remove stock apps, I would appreciate it. The guide posted doesn't go into too much detail in Ubuntu since the OP said that he could not get it to work in Ubuntu. Thanks.
Click to expand...
Click to collapse
Wouldnt the Mac version work since they are both *nix?
I was able to root my Sprint HTC hero just fine running Jaunty. I followed the instructions in the guide you mentioned, for Ubuntu. One thing I noticed is before adb recognized my phone, I had to start "HTC Sync" from the phone's notifications. Just ignore the error about it not finding HTC Sync on your PC. Obviously it never will since HTC Sync is a Windows app
Here's the step by step that worked for me: http://romeosidvicious.com/2009/11/09/rooting-the-htc-hero-with-ubuntu-karmic/
I typed it so I could find it easily if necessary and figured why not share it....
romeosidvicious,
Thanks for all your hard work. I and others really appreciate it.
Stevious said:
I was able to root my Sprint HTC hero just fine running Jaunty. I followed the instructions in the guide you mentioned, for Ubuntu. One thing I noticed is before adb recognized my phone, I had to start "HTC Sync" from the phone's notifications. Just ignore the error about it not finding HTC Sync on your PC. Obviously it never will since HTC Sync is a Windows app
Click to expand...
Click to collapse
Yep, that is something I had to do in windows XP as well. It will help many others as well. Thanks.
Stevious said:
I was able to root my Sprint HTC hero just fine running Jaunty. I followed the instructions in the guide you mentioned, for Ubuntu. One thing I noticed is before adb recognized my phone, I had to start "HTC Sync" from the phone's notifications. Just ignore the error about it not finding HTC Sync on your PC. Obviously it never will since HTC Sync is a Windows app
Click to expand...
Click to collapse
Great, now my Ubuntu Jaunty machine won't detect the phone. I did the above but it still won't work. Im gonna reboot and retry...
Edit:
Nope, no love for my Ubuntu. It's not seeing the Hero. I will have to research this one.. If anyone has suggestions, please chime in.
Ok, found a solution:
http://forum.xda-developers.com/showthread.php?t=537508
----------------------------------------------------------------
Here is the part that solved it for me:
Setting up UDEV to recognize HTC Device -
1. Type the following into a terminal (Applications > Accessories > Terminal):
Code:
gksudo gedit /etc/udev/rules.d/51-android.rules
2. Now add the following line to the blank file:
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
3. Click save and close.
4. To restart udev, open up a terminal and enter:
Code:
sudo /etc/init.d/udev restart
---------------------------------------------------------------------
Thanks to Wddglr for all the useful info. It looks like I will be using other things he posted about. Hopefully that info will help someone else.
Just curious, which version of Ubuntu are you running? I didn't have to make any UDEV changes in Jaunty.
romeosidvicious said:
Here's the step by step that worked for me: http://romeosidvicious.com/2009/11/09/rooting-the-htc-hero-with-ubuntu-karmic/
I typed it so I could find it easily if necessary and figured why not share it....
Click to expand...
Click to collapse
I want to follow through with this...
I was following this
http://www.youtube.com/watch?v=ArMO5IHS2eI
until the step came to plug it in and then he suggested typing "adb devices" which told me this.
"~/android-sdk-linux/tools$ adb devices
bash: adb: command not found"
So I came here and I want to follow the links tutorial.. two questions
Is it safe to proceed even though i've been told adb: Command not found
will i be able to proceed although ive been told this command is not found?
Onompoly2 said:
"~/android-sdk-linux/tools$ adb devices
bash: adb: command not found"
So I came here and I want to follow the links tutorial.. two questions
Is it safe to proceed even though i've been told adb: Command not found
will i be able to proceed although ive been told this command is not found?
Click to expand...
Click to collapse
Try:
sudo ./adb devices
From the same directory. Or, you can specify the full path:
sudo ~/android-sdk-linux/tools/adb devices
To answer your other questions, it won't work if it says the command is not found.
Okay
It worked but I must have turned into an idiot when i decided my operating system was good enough.
This isn't working, and I am not even upgraded to the operating system the tutorial is written for...
194 updates due... running 8.04 with a bunch of double half installed broken applications.. maybe I should reformat.
I'll let you guys know how things go which ever way it goes.
back again. fresh 9.10 install fully updated.
Following this
http://romeosidvicious.com/2009/11/09/rooting-the-htc-hero-with-ubuntu-karmic/
I get this far
[email protected]:~# sudo su
[email protected]:~# cd ~/android-sdk-linux/tools
[email protected]:~/android-sdk-linux/tools#
[email protected]:~/android-sdk-linux/tools#
[email protected]:~/android-sdk-linux/tools# ./adb push ../asroot2 /data/local/
711 KB/s (74512 bytes in 0.102s)
[email protected]:~/android-sdk-linux/tools# ./adb shell chmod 0755 /data/local/asroot2
[email protected]:~/android-sdk-linux/tools# /data/local/asroot2 /system/bin/sh
bash: /data/local/asroot2: No such file or directory
[email protected]:~/android-sdk-linux/tools# ./adb shell /data/local/asroot2 /system/bin/sh
[+] Using newer pipe_inode_info layout
Opening: /proc/559/fd/3
SUCCESS: Enjoy the shell.
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4755 su
reboot
Click to expand...
Click to collapse
It seems as though after it says "SUCCESS" that my terminal just stops responding to code...
Tried reading the link to where he made the tutorial from, but its a mixture of ubuntu and windows with 30 pages of posts.
Any thoughts/help?
Thanks
[Continuing]
So just pretending that everything is going as planned I reboot the phone and it actually turns my computer off as well..
So I continue with the steps.
[email protected]:~# cd ~/android-sdk-linux/tools
[email protected]:~/android-sdk-linux/tools# ./adb push ../recovery-RA-heroc-v1.2.3.img /sdcard/
* daemon not running. starting it now *
* daemon started successfully *
1199 KB/s (3352576 bytes in 2.730s)
[email protected]:~/android-sdk-linux/tools# ./adb shell
$ su
su: permission denied
Click to expand...
Click to collapse
But Get permission denied.
I'm going to go ahead and start over but skip the first line that i input that said SUCCESS and stopped the terminal.
(really don't know what i'm doing but I think I need to get these two lines in
cat sh > su
chmod 4755 su)
EDIT: on second thought perhaps this has something to do with me being logged in as root on my computer from the get go, i'll try that.
A dummy and his cell phone perhaps soon part.
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4755 su
reboot
Click to expand...
Click to collapse
It looks like you copy/pasted this whole section as a block. I think you need to execute the commands one at a time, and wait for a new "#" prompt between each one. The reason the terminal stops responding is that as one long string, it's not a meaningful command.
buck2202 said:
It looks like you copy/pasted this whole section as a block. I think you need to execute the commands one at a time, and wait for a new "#" prompt between each one. The reason the terminal stops responding is that as one long string, it's not a meaningful command.
Click to expand...
Click to collapse
I didn't, although i did try that as well
after I would do the mount commands i would no longer get a $ or a # sign, it was just a bunch of nothingness...
I ended up booting up my girlfriends vista and then spent quite a while figuring out how to get the driver for adb, I had to follow two different windows guides for rooting for some reason as well... so if that says anything.. just imagine how long it took me to realize how to get the driver hahah
buck2202 said:
It looks like you copy/pasted this whole section as a block. I think you need to execute the commands one at a time, and wait for a new "#" prompt between each one. The reason the terminal stops responding is that as one long string, it's not a meaningful command.
Click to expand...
Click to collapse
no, I'm having the same problem. After the "mount" command it gives me nothing.
Edit: doing this in karmic
Odd. I've had no problems following the generic procedure from theunlockr on ubuntu. My only suggestion would be to turn
Code:
./adb shell /data/local/asroot2 /system/bin/sh
into
Code:
./adb shell
/data/local/asroot2 /system/bin/sh
I'm not sure why it should make a difference, but on my computer "./adb shell <command>" exits the shell when it finishes. From what you've pasted, it doesn't look like that's happening to you, but that's my only guess right now.
If you run "./adb devices" do you see your serial number?
And out of curiosity, why are you running as root on your computer? (sudo su) Have you tried just starting the adb server as root, and running the rest of the commands normally? Does this work?
Code:
./adb kill-server
sudo ./adb start-server
./adb devices
im on to the command prompt thingy and im a little confused......
do i put the whole command in? because when i do it says faild bla bla?
do i type it in just how it shows? cuz i wont work for me, but if i put in
JUST..."abd shell mount" it show alot of writing like it worked but im not putting in the WHOLE command???
can anyone tell me what it is supposed to say after each command??????????
omg i just want it to work. i got a new phone from verizon because i downloaded the leak, when all i wanted was a custom rom for wireless tether
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery.img
you might want to hit up in the irc chat, you can get real time help there. irc.wastate.net i believe or irc.zifnab06.net chat room either erisroothelp or droideris
where is that? those links diddnt work
those werent links, they were the servers for the irc chats. you need a irc chat client to get on there. if you want to use a web based chat client, the direct link to there is chat.andirc.net
whooohoooo!
you dont remember how the command prompt works? im just wondering if you put the whole command in or just the first part....sorry if im coming off a little stupid and pushy
how about posting the error?
ok i get in to my tools directory(this is what i see)
*C:\AndroidSDK\AndroidSDK\tools>
i put in (adb shell mount -o rw,remount /dev/block/mtdblock3 /system)
this is what it says "mount: Operation not permitted"
Why not use this:
http://forum.xda-developers.com/showthread.php?t=661413
what does that do? is it an app to get around the command prompt?
Does your phone have root access? (did you flash the rooted PB00IMG.zip?)
yes i did all the steps leading up to this now im stuck on the command prompt
do i type in all of the command? when i do it says "mount: Operation not permitted" on the first command
*Sigh*
- Open up command prompt (either type in cmd in the windows search bar or dig deep into your computer to find that sexy thang.
- Direct it to the folder of your choosing. In this case, the tools subfolder of android sdk. There are several ways to do this, the easiest would be as follows:
Say you're trying to get to C:\AndroidSDK\tools
Type:
cd C:\AndroidSDK\tools
or
cd C:\
cd AndroidSDK
cd tools
- From here, you shouldn't have a problem with adb. Make sure your device is plugged in and type:
adb devices
and you should see your device. Copy and paste the commands and you should be good to go.
ok so i put in adb devices (wasnt in the walkthrough)
and it showed
"list of devices attached"
HT9CTHG01052 device
im assuming that this is my device! yay.....or so i thought
i copied and pasted the command...and i also tried to type it out
it said the same thing!?
"mount: operation not permitted"
im sure its something im doing wrong...i just need someone to take a couple minutes to help a brutha
i typed in "cmd" in front of each command and it showed
microsoft windows [version bla bla]
copyright bla bla
untill i got to the last command..... it said 'ecovery.img' is not recognized as an internal or external command, operable program or bach file (yes it did say " 'ecovery.img' ") i looked all over a i found no file mis labled as "ecovery.img"
when it says all that stuff about windows does that mean that it took the command?
Why are you typing in "cmd" infront of everything?
IDK im just trying to figure it all out? am i wrong?
thanks for helping btw
i wish someone knew what it is supposed to say after each command....or even a video showing someone doing these commands so you can see them typing them
Open up a command prompt and go to your tools directory, and execute these commands:
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery.img
you type the adb commands in exactly like they are shown. you dont type anything in front of adb.
Hi, I'm pretty geeky for a non IT person, but I have had a Blackberry up until now, so I am totally new to this Android set up. I have the Epic on Sprint; am frustrated with battery life, and would like to try and root the phone for 2.2 froyo. however most of the tutorials blow through the lingo (adb, huh?) in a way that is not explanatory for people who are new to this. Is their either a visual step-by-step guide for people or a more basic explanation of what is what and what to do somewhere? And, so far all I've seen is for Windows people. I have a Mac running snow leopard?
Help!
tromano said:
Hi, I'm pretty geeky for a non IT person, but I have had a Blackberry up until now, so I am totally new to this Android set up. I have the Epic on Sprint; am frustrated with battery life, and would like to try and root the phone for 2.2 froyo. however most of the tutorials blow through the lingo (adb, huh?) in a way that is not explanatory for people who are new to this. Is their either a visual step-by-step guide for people or a more basic explanation of what is what and what to do somewhere? And, so far all I've seen is for Windows people. I have a Mac running snow leopard?
Help!
Click to expand...
Click to collapse
I'm thinking of writing a script for Mac users, i don't have an epic but my xo-worker does and i rooted his today on my Mac, not as simple as the one click root but is doable.
that would be awesome; i guess the main things are 1. if you root it, can you upgrade to 2.2? 2. if you root it and upgrade, can you undo everything to factory?
Id be interested in this also
Sent from my SPH-D700 using Tapatalk
tromano said:
that would be awesome; i guess the main things are 1. if you root it, can you upgrade to 2.2? 2. if you root it and upgrade, can you undo everything to factory?
Click to expand...
Click to collapse
1. Rooting doesn't instantly make you 2.2 Upgradeable. 2.2 Froyo comes in different flavors for different manufactures. They lock the phone down with their systems so they phone cannot be unlocked, etc. Right now we are a bit far behind in getting 2.2 on the Epic. I think Sprint might even get it faster.
2. If you root you can ALWAYS go back to stock. They is a guide right here for returning to stock 2.1 and undo everything to factory.
It's kind of crude, but I wrote this for someone over at SDX-Developers to try. I think they were successful.
I don't use Macs much, but here's Joey's Permanent Root Method process I used to get it working under linux. The same method can be done through a Mac's Terminal if you're not intimidated by using command line.
First download Android-SDK for OSX.
http://developer.android.com/sdk/index.html
Once downloaded extract it and save to the root of your Mac's hard drive. Then rename the folder "android-sdk"
Next download the following files and save them to the /android-sdk/tools folder.
http://www.joeyconway.com/epic/root/joeykrim-root.sh
http://www.joeyconway.com/epic/root/jk-su
http://www.joeyconway.com/epic/root/rageagainstthecage-arm5.bin
http://www.joeyconway.com/epic/root/playlogo
Next open a terminal window. (command key + space then type terminal)
At the prompt, type "cd /android-sdk/tools"
If you save the files where I told you to, you shoud be able to copy and paste the commands into your terminal window. Do one line at a time and press enter after each pasting.
./adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin
./adb push joeykrim-root.sh /sdcard/joeykrim-root.sh
./adb push jk-su /sdcard/jk-su
./adb push playlogo /sdcard/playlogo
./adb shell
chmod 755 /data/local/tmp/rageagainstthecage-arm5.bin
cd /data/local/tmp
rageagainstthecage-arm5.bin
exit
./adb shell
mount -t rfs -o remount,rw /dev/block/stl9 /system
cat /sdcard/joeykrim-root.sh > /system/bin/joeykrim-root.sh
cat /sdcard/jk-su > /system/bin/jk-su
mv /system/bin/playlogo /system/bin/playlogo-orig
cat /sdcard/playlogo > /system/bin/playlogo
chmod 755 /system/bin/playlogo
chmod 755 /system/bin/joeykrim-root.sh
exit
Click to expand...
Click to collapse
Issue for operation not permitted
I got all the way to the last paragraph of ./adb shell but cannot get the mount line to work....it says operatino not permitted. I put everything in the mac's root section just inside mac hd.
HELP!! I put hte phone in debug mode....did I need ot install any drivers from samsung....help!!!
-J
jayhover85 said:
I got all the way to the last paragraph of ./adb shell but cannot get the mount line to work....it says operatino not permitted. I put everything in the mac's root section just inside mac hd.
HELP!! I put hte phone in debug mode....did I need ot install any drivers from samsung....help!!!
-J
Click to expand...
Click to collapse
Were you able to get this working?
Root
No, I was not.
Check out this snippet of the instructions (I'll number them for ease):
<snip>
1.) cd /data/local/tmp
2.) rageagainstthecage-arm5.bin
3.) exit
4.) ./adb shell
5.) mount -t rfs -o remount,rw /dev/block/stl9 /system
</snip>
When you ran step 2, what happened? You may have to run the command this way with a dot and slash in front instead:
./rageagainstthecage-arm5.bin
When you ran step 4, did you get a $ or a #? If you got a #, step 5 should work properly. If you got a $, you'll need to do re-run the ./rageagainstthecage-arm5.bin step again. Re-running this step doesn't hurt anything. Good luck.
ss4rob said:
Check out this snippet of the instructions (I'll number them for ease):
<snip>
1.) cd /data/local/tmp
2.) rageagainstthecage-arm5.bin
3.) exit
4.) ./adb shell
5.) mount -t rfs -o remount,rw /dev/block/stl9 /system
</snip>
When you ran step 2, what happened? You may have to run the command this way with a dot and slash in front instead:
./rageagainstthecage-arm5.bin
When you ran step 4, did you get a $ or a #? If you got a #, step 5 should work properly. If you got a $, you'll need to do re-run the ./rageagainstthecage-arm5.bin step again. Re-running this step doesn't hurt anything. Good luck.
Click to expand...
Click to collapse
i'm stuck. i just got my epic and i'm trying to root it. i get to step 2 (using "./" before rage...cage) and terminal looks like it's running something. i type in "exit" when it finishes and it's as if my terminal logs me out. i can't reach step 4 and the screen on my epic has gone black by now. frozen up. i need to remove the battery to reboot and unfreeze my device. what am i doing wrong? am i missing a step somewhere? also, the "playlogo" file saves as ".sh" at the end, so in the terminal i manually enter that at the end of the file name just so that it can be read. "playlogo" without the ".sh" at the end cannot be found. is this what's causing it? any help would be greatly appreciated. i'm trying not to brick my phone!
I'm pleased to tell everyone Bluetooth finally works!!! I can't take any credit other than putting together the instructions to get it working and digging all over the interwebs so have a look below!!!!!!!:
Also note, this may work on other Linux setups using the Transformer and possibly other devices using similar instructions and files.
OP for Tubutnu by x3maniac
1. Go to this site and download the gz file. This contains a few missing files we need and it's compile for ARMHF. http://forum.xda-developers.com/showthread.php?t=1476835
2. Extract the contents of the gz to /usr/sbin
3. Go to this site. Copy the code in the box and make a new file called bsp-tf101. Save the file to /etc/init.d. http://forum.xda-developers.com/showpost.php?p=21388706&postcount=1456
4. In Android (or mount the Android file system if it isn't already) copy the file /data/misc/bluetooth/bcm4329.hcd to /lib/firmware. If the file with CAPITAL letters exists like this already in /lib/firmware: BCM4329.hcd you are to delete it or CUT it from that directory (many XDA posts say to get rid of that file. We want to use the lower case file.
5. In Android (or mount the Android file system if it isn't already) copy the file /data/misc/bluetooth/mac.txt to /lib/firmware/brcm.
6. Now, edit /etc/init.d/bsp-tf101. Go to the line that starts with /usr/sbin/brcm_patchram_plus and REMOVE --bd_addr and whatever MAC address is in the file. We are doing this because when you run the service, the MAC will be read from /lib/firmware/brcm/mac.txt.
7. In terminal type "service bsp-tf101 start" NO QUOTES.
8. After the terminal says Done Setting Line Discipline, open your Bluetooth Manager application from Preferences in Lubuntu.
9. Happy scanning and pairing! I successfully connected my GS3 and saw other devices nearby.
Addendum for Bluetooth in Raring
1. Create a file called "tfbatch" or whatever name you want, it does not matter. Save it in your home directory for the moment. Edit your file with nano /home/username/tfbatch with the following lines in it below.
#! /bin/shrfkill unblock 0/usr/sbin/brcm_patchram_plus --enable_hci --baudrate 3000000 --patchram /lib/firmware/bcm4329.hcd /dev/ttyHS2chmod /dev/nv* /dev/tegra_*exit
2. Now copy "tfbatch" or whatever you named it to /usr/bin. You can do (without quotes) "cp /home/username/tfbatch /usr/bin"
3. sudo nano /etc/rc.local
4. Type tfbatch in this file before the line that says exit 0. I'm not sure if you need a space in between tfbatch and exit 0 but put one there just in case.
5. If you haven't done so already, from terminal do the following for these files:
sudo chmod 777 /usr/bin/tfbatchsudo chmod 777 /lib/firmware/bcm4329.hcdsudo chmod 777 /usr/sbin/brcm_patchram_plussudo chmod 777 /usr/sbin/brcm_patchram_plus.c
6. Please note, I understand the security risks of 777 for these files but if you are worried then you must choose something different. Maybe 644 but I don't know for sure. We are doing 777 for some files becacuse of permission denied errors. If you find a better method I'll update my post.
7. Reboot and Profit. (I was perfectly able to use PAN for Bluetooth tethering without installing anything extra using Raring and GNOME-CORE. However, I did not get Bluetooth headsets to work yet so if someone else wants to help out then that's great too.
Hi!
First of all thank you, that worked perfectly for me.
I just had to chmod bcm4329.hcd and brcm_patchram_plus's files.
For those who have the same "problem" just type this once you placed all the files in good folders.
Code:
sudo chmod 777 /lib/firmware/bcm4329.hcd
Code:
sudo chmod 777 /etc/init.d/bsp-tf101
And do the same for all files you extracted from brcm.tar.gz
Not sure if chmod all of these files is useful but that's what I've done and it worked.
Hope it'll help.
147keul said:
Hi!
First of all thank you, that worked perfectly for me.
I just had to chmod bcm4329.hcd and brcm_patchram_plus's files.
For those who have the same "problem" just type this once you placed all the files in good folders.
Code:
sudo chmod 777 /lib/firmware/bcm4329.hcd
Code:
sudo chmod 777 /etc/init.d/bsp-tf101
And do the same for all files you extracted from brcm.tar.gz
Not sure if chmod all of these files is useful but that's what I've done and it worked.
Hope it'll help.
Click to expand...
Click to collapse
I have been problems getting this to work on Raring 13.04 build from X3. Are you using Raring by chance or one of the other versions by X3?
I've not been using yet Raring method, I used the one click method with 2.6.36 kernel.
Gonna take a look in a few with raring, I'll tell you if I manage to make it work.
147keul said:
I've not been using yet Raring method, I used the one click method with 2.6.36 kernel.
Gonna take a look in a few with raring, I'll tell you if I manage to make it work.
Click to expand...
Click to collapse
I got it to work a little bit ago and tethering for Bluetooth internet. Good call with chmod it worked like a champ. Thanks!
When using your Bluetooth tethering, you can also use Conky to display the IP address. You can edit the file by sudo nano /etc/conky/conky.conf. Go to the line that is displaying ${addr wlan0}. Copy that whole line below and replace wlan0 with bnep0. Bnep0 is the adapter interface that has the BT tether IP address.
Has anyone seen this? Ubuntu Developer Preview for Galaxy Nexus, Nexus 4 Arrives Feb. 21
"Our platform supports a wide range of screen sizes and resolutions. Developers who have experience bringing up phone environments will find it relatively easy to port Ubuntu to current handsets"
"For developers, contributors and partners, there is now a coherent experience that warrants attention. The cleanest, most stylish mobile interface around."
Click to expand...
Click to collapse
I don't have the files starting from step 4 (folder is empty). I'm guessing it's because I installed another ROM (EOS JB MR1 4.2 from http://forum.xda-developers.com/showthread.php?t=2063406). Would anyone happen to know where else I can obtain the files needed starting from step 4? Thanks!
Treizy said:
I don't have the files starting from step 4 (folder is empty). I'm guessing it's because I installed another ROM (EOS JB MR1 4.2 from http://forum.xda-developers.com/showthread.php?t=2063406). Would anyone happen to know where else I can obtain the files needed starting from step 4? Thanks!
Click to expand...
Click to collapse
Search android from terminal:
Find / | grep bcm4329.hcd
If you get nothing I'll try to upload later.
TomTcom said:
Search android from terminal:
Find / | grep bcm4329.hcd
If you get nothing I'll try to upload later.
Click to expand...
Click to collapse
Thanks! Found that file in /system/etc/firmware.
I wasn't able to find the mac.txt file but I know my bluetooth mac address. Is that the only thing that I need to include in that file?
Treizy said:
Thanks! Found that file in /system/etc/firmware.
I wasn't able to find the mac.txt file but I know my bluetooth mac address. Is that the only thing that I need to include in that file?
Click to expand...
Click to collapse
Yes, that's the only thing you need to put in. Strange you can't find needed files in right places, have you tried with a "root explorer"? Try to download it, and normally you should find mac.txt.
Trying this again with the raring build and still running into problems.
When I try to start the service, i get the following error:
Code:
$ sudo service bsp-tf101 start
* Starting Bluetooth Support Deamon...
* Setting correct permissions on nvtegra device nodes...
/etc/init.d/bsp-tf101: 23: /etc/init.d/bsp-tf101: /usr/sbin/brcm_patchram_plus: Permission denied
I did run the following commands before hand:
sudo apt-get install rfkill (I didn't have this installed before and it was giving an error)
sudo chmod 777 /lib/firmware/bcm4329.hcd
sudo chmod 777 /etc/init.d/bsp-tf101
sudo chmod -R 777 /usr/sbin/brcm_patchram_plus
Any idea why it still says permission denied?
Thanks!
Treizy said:
Trying this again with the raring build and still running into problems.
When I try to start the service, i get the following error:
Code:
$ sudo service bsp-tf101 start
* Starting Bluetooth Support Deamon...
* Setting correct permissions on nvtegra device nodes...
/etc/init.d/bsp-tf101: 23: /etc/init.d/bsp-tf101: /usr/sbin/brcm_patchram_plus: Permission denied
I did run the following commands before hand:
sudo apt-get install rfkill (I didn't have this installed before and it was giving an error)
sudo chmod 777 /lib/firmware/bcm4329.hcd
sudo chmod 777 /etc/init.d/bsp-tf101
sudo chmod -R 777 /usr/sbin/brcm_patchram_plus
Any idea why it still says permission denied?
Thanks!
Click to expand...
Click to collapse
Try also chmod 777 the brcm_patchram_plus.c file as well.
Also, I need to update my guide. I don't run it as a service but rather a batch file launched from rc.local so everything is executed as root. I'll have to update the guide to include Raring. So that could be part of the problem as well.
TomTcom said:
Try also chmod 777 the brcm_patchram_plus.c file as well.
Also, I need to update my guide. I don't run it as a service but rather a batch file launched from rc.local so everything is executed as root. I'll have to update the guide to include Raring. So that could be part of the problem as well.
Click to expand...
Click to collapse
So if I add these commands to the rc.local file in /etc it should work?
Code:
sudo chmod 777 /lib/firmware/bcm4329.hcd
sudo chmod 777 /etc/init.d/bsp-tf101
sudo chmod -R 777 /usr/sbin/brcm_patchram_plus
sudo service bsp-tf101 start
Or do I need to do something else?
Treizy said:
So if I add these commands to the rc.local file in /etc it should work?
Code:
sudo chmod 777 /lib/firmware/bcm4329.hcd
sudo chmod 777 /etc/init.d/bsp-tf101
sudo chmod -R 777 /usr/sbin/brcm_patchram_plus
sudo service bsp-tf101 start
Or do I need to do something else?
Click to expand...
Click to collapse
No don't do that. I'll try and post what you need to do later tonight.
Treizy said:
So if I add these commands to the rc.local file in /etc it should work?
Code:
sudo chmod 777 /lib/firmware/bcm4329.hcd
sudo chmod 777 /etc/init.d/bsp-tf101
sudo chmod -R 777 /usr/sbin/brcm_patchram_plus
sudo service bsp-tf101 start
Or do I need to do something else?
Click to expand...
Click to collapse
I have updated my guide. See the OP for the Addendum for Raring installation. The file you create will be ran before the GUI loads with root permissions from rc.local.
Let me know if this worked.
TomTcom said:
I have updated my guide. See the OP for the Addendum for Raring installation. The file you create will be ran before the GUI loads with root permissions from rc.local.
Let me know if this worked.
Click to expand...
Click to collapse
Nope
When I try to turn bluetooth on, nothing happens. It will switch back to off when i close the settings popup.
Treizy said:
Nope
When I try to turn bluetooth on, nothing happens. It will switch back to off when i close the settings popup.
Click to expand...
Click to collapse
Hmmm...if you followed the guide you shouldn't have to turn it on. The batch is executed on boot from RC.local. Try and give me some more details.
TomTcom said:
Hmmm...if you followed the guide you shouldn't have to turn it on. The batch is executed on boot from RC.local. Try and give me some more details.
Click to expand...
Click to collapse
Maybe I messed up. For step 1, the files you are asking us to download are the ones in post #10 correct (brcm.tar.gz)? Also, I don't have this mac.txt file anywhere so I created my own and just put my mac address in it (hopefully the correct one). Lastly, i dont have this file for this step:
sudo chmod 777 /usr/sbin/brcm_patchram_plus.c
but instead i have it in this location:
/usr/sbin/brcm_patchram_plus/brcm_patchram_plus.c
Treizy said:
Maybe I messed up. For step 1, the files you are asking us to download are the ones in post #10 correct (brcm.tar.gz)? Also, I don't have this mac.txt file anywhere so I created my own and just put my mac address in it (hopefully the correct one). Lastly, i dont have this file for this step:
sudo chmod 777 /usr/sbin/brcm_patchram_plus.c
but instead i have it in this location:
/usr/sbin/brcm_patchram_plus/brcm_patchram_plus.c
Click to expand...
Click to collapse
I think you might have files in the wrong location, there should be no brcm_patchram_plus directory. Try to extract the zip again and make sure they are all in /usr/sbin only.
If you didn't have mac.txt from Android, you can just make it like you did and make sure it is in /lib/firmware/brcm.
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.