I haven't seen a guide on this, so I will make one for you guys. I'm sure many of you have noticed that if you copy a file from your PC to the SD card while in Android, then use the file browser, the file doesn't show up unless you reboot. This is an annoyance when installing apps, so I present to you this guide.
1. Download and extract the Android SDK.
2. In the "android-sdk-windows" open up SDK Setup, and install the USB driver package. [thanks memin1857]
3. Open up the "android-sdk-windows/tools" folder, this is the folder you will be putting your files into, in order to copy them to the SD card.
4. Open a command prompt, and cd into the directory containing the folder in Step 3 (IE: If you extracted the folder to C:\ in step 1, you would do
Code:
cd C:\android-sdk-windows\tools
5. Type ADB Shell
6. Type su to get root access
7. Type mount -o remount rw /sdcard to mount the sdcard
8. Type exit to exit the shell
9. Type adb push nameoffile.apk /sdcard replace nameoffile.apk with the filename of whatever you want to copy
10. Success!
You can also copy folders this way, simply type the folder name instead of the file name, in place of nameoffile.apk. Just tested this with several files, and it works perfectly
YAY!!! Waited for a while allready! Thanks!
good job brother!
wow...this is so complicated...can i suggest another way?which is use an app from market called websharing file/media....this is fastest way for me to transfer files...just connect bot your pc and device to the same connection(wifi).Then you can just transfer files from your pc internet browser...there is no need to install any desktop server client...just direct transfer...speedy too...1 mp3 song just about 5or 6 seconds...if you want download this app in full version and free...i think you can find it on www.4shared.com
Easy version
Droid Explorer works from adb too.
http://de.codeplex.com/
It uses the same mechanism (adb) with Android SDK but has a visual interface.
BTW if you will use android sdk only, you don't need to install all sdk packages (takes huge amount of time), you only need usb drivers.
(Droid Explorer has drivers included)
Or u can jus add the files thru USB connection n use Dev Tools's media scanner.
Sent from my HTC HD2 running DarkStone HD2Froyo v1
Good
Nice, iiNFAMOUS CHRiS
What is the difference between this and Auto Mount which is on the Android Market?
nzxtneo said:
What is the difference between this and Auto Mount which is on the Android Market?
Click to expand...
Click to collapse
When you use Auto Mount, it mounts the USB drive so you can drag/drop files onto the SD card, but if you do that method, when you try to find the file on your phone, Android won't see it unless you restart your phone.
iiNFAMOUS CHRiS said:
When you use Auto Mount, it mounts the USB drive so you can drag/drop files onto the SD card, but if you do that method, when you try to find the file on your phone, Android won't see it unless you restart your phone.
Click to expand...
Click to collapse
Weird, maybe it depends on the build but I have never had to restart the device after I move files over with Auto Mount.
I just remove the usb cable from the HD2 and I got a notification on the top left that says "preparing SD card" and after that I am good to go.
Tried to manually deodex my phone today....after getting an error and having to install java se i thought everything was good...then i got a different error on step 4....
Starting framework.odex
* Deodexing...
* Redexing...
out\com\skyhookwireless\wps\IXpsService$Stub.smali [0,0] null
*Processing...
The system cannot find the file specified.
Press any key to continue...
ive searched lots of forums and havent seen anyone with this error...does anyone know what it means or what i can do to fix it....what the hell is skyhook wireless..i dont want to use the easy deodex method from 928DROID i would rather do it manually and i do not want the black glass theme..i would really appreciate any info that can help me get this resolved..thanks
I didn't have your problem exactly. I got through steps 1-3 ok. On step 4 it got to #30 and then it said there was an error with the core.apk and could not proceed.
I tried a couple of times and got the same thing. So- since I was running stock ota- I just dl'ed the two folders I needed from here (xda) and installed them with ADB. Worked like a charm. I would rather have done the manual way. But oh well. If it won't work what are you going to do?
Well that's actually what happened to me at first with step 4.. I think I changed the connection mode...I ended up getting it to work im just confused about exactly which connection mode it.should be in....I had it in pc mode for steps 1-3 I think...then had to put it in media sync to get through step 4...then usb mass storage to adb the folders onto the sd card...and then pc mode again to adb shell and move the folders to /system....I wish the directions listed exactly what mode u need for each...cause all the forums I read people always have problems and have to.switch to different connection modes throughout the process but no one can seem to agree on exactly which modes u need for the different steps
Sent from my DROIDX using Tapatalk
aholeinthewor1d said:
Well that's actually what happened to me at first with step 4.. I think I changed the connection mode...I ended up getting it to work im just confused about exactly which connection mode it.should be in....I had it in pc mode for steps 1-3 I think...then had to put it in media sync to get through step 4...then usb mass storage to adb the folders onto the sd card...and then pc mode again to adb shell and move the folders to /system....I wish the directions listed exactly what mode u need for each...cause all the forums I read people always have problems and have to.switch to different connection modes throughout the process but no one can seem to agree on exactly which modes u need for the different steps
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
* place phone into pc mode.
1. Unzip xUltimate v2.2, and launch "Main.exe".
2. If everything goes well xUlt should recognize the phone and make a connection. You now should see a list of options.
3. Run option 1. After option 1 is done, run option 2.
4. Now these well take a while. Run option 3.
5. IMPORTANT: After you have run option 3, you MUST navigate to the xUltimate folder and find "origi_frame" folder, and delete "guava.odex". It's a bad file, and interferes with deodexing process.
6. Now run option 4, and wait.
7. Exit xUltimate, and put the phone in USB mass storage.
8. Go back into the xUltimate folder and copy "done_frame", and "done_app", and move them to the root of the sdcard.
* place phone back into pc mode.
9. Open a command prompt, and do the following:
Code:
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
exit
exit
adb reboot
It may fail a few times. Just keep trying.
Hi,
im using gauner1986's HD-FI 0.3.
And i want to change the lockscreen, but as i tryed i failed.
I cant really remount /system as rw (but it is shown as rw in mount)
As i read i just need to move or delete htclockscreen.apk from /system/app to enable to android default lockscreen.
So i tried to move the file to htclockscreen.bak with adb, Linda Manager and Es File Explorer.
But in every case rename/move failed.
On Es File Explorer i checked the option to mount system as rw without any effect!
For adb i try'd to expand permissions using 'su' command without any effects as far as i'm able to assess it.
As i read i may need to set phone into recovery mode to remount disk using adb, but i was unable to findout how i can get my htc hd2 into this mode.
May anyone can help me with my problem?
Great Thanks
olvidar
olvidar said:
Hi,
im using gauner1986's HD-FI 0.3.
And i want to change the lockscreen, but as i tryed i failed.
I cant really remount /system as rw (but it is shown as rw in mount)
As i read i just need to move or delete htclockscreen.apk from /system/app to enable to android default lockscreen.
So i tried to move the file to htclockscreen.bak with adb, Linda Manager and Es File Explorer.
But in every case rename/move failed.
On Es File Explorer i checked the option to mount system as rw without any effect!
For adb i try'd to expand permissions using 'su' command without any effects as far as i'm able to assess it.
As i read i may need to set phone into recovery mode to remount disk using adb, but i was unable to findout how i can get my htc hd2 into this mode.
May anyone can help me with my problem?
Great Thanks
olvidar
Click to expand...
Click to collapse
Method 1) To go to recovery mode with NAND builds, just reboot phone(or when phone is off) and hold the power button until MAGLDR boots and shows the menus. Don't let go till you see the options, otherwise it goes straight to Android. From there use the vol up/down hard keys to scroll and the green phone button to select.
Method 2) If you hold the vol down key and power key when phone is off it will go straight to recovery screen with the colorful bars.
Having said all that, I'm not sure if we can change those files with out a de-odexed rom. But imilkas does have a de-odexed NAND build.
http://forum.xda-developers.com/showthread.php?t=898708
Sorry for edit but I forgot to mention that Root Explorer works better for moving/renaming system files. Go!Go!Go!
Hi!
I've just rooted NST with NookManager.
I'm a total noob in android world (as I don't have any smartphone) and I'm searching for basics about rooted android devices since two days but I didn't come to a solution to my problems.
Simply I want to uninstall some apk as described in this thread http://forum.xda-developers.com/showthread.php?t=1933615
I don't have titanium pro or root explorer.
How to install/uninstall apps and how to take full control about entire nook file system?
Thanks
yell! said:
Hi!
I've just rooted NST with NookManager.
I'm a total noob in android world (as I don't have any smartphone) and I'm searching for basics about rooted android devices since two days but I didn't come to a solution to my problems.
Simply I want to uninstall some apk as described in this thread http://forum.xda-developers.com/showthread.php?t=1933615
I don't have titanium pro or root explorer.
How to install/uninstall apps and how to take full control about entire nook file system?
Thanks
Click to expand...
Click to collapse
It depends on the Launcher you are using.
By default you should have "ReLaunch" installed.
To uninstall an apk, just select it in the app list and hold for a little bit longer. A dialog containing "uninstall" option the should pop up.
The other way is to use "NookColorTools".
http://forum.xda-developers.com/showthread.php?t=868366
Install it , run it, select "manage applications", select certain apk, uninstall it.
edit : you should probably place 'NookColorTools' in /system/app/ using ADB
######################################
Installing apk's
1 way - put 'some_app.apk' on mSD card and select it using any file manager.[/COLOR]
2 way - configure ADB, connect your nook and type 'adb install /your_apk_location_on_harddrive
3 way - install Google Play using 'NTGAppsAttack', install "searchmarket.apk" (i uploaded it somewhere, check my posts), search for apk in google play and install it.
#############################
To uninstall a system apk
Read the forum before deleting any system apk's.
Most of them are necessary for the system to work.
1 way - get any file manager that can mount root partition (Rhytm file manager ; ES file explorer) , select "root explorer" in options, navigate to '/system/app/', Move/delete any apk that you desire.
2 way - configure ADB, connect nook, type 'adb shell', 'mount -o rw,remount /dev/block/mmcblk0p5 /system', 'cd system', 'cd app', 'ls' (to see apk list), 'rm apk_name.apk'.
#############################
To install a system apk.
configure ADB, connect nook, type 'adb shell', 'mount -o rw,remount /dev/block/mmcblk0p5 /system'
exit ADB, from your system type 'adb push /your_apk_location /system/app'
#############################
If you encounter problems with installing from mSDcard search for "howto allow install non market applications on android'.
Remember that only Apk's for Android 2.1 will install. 2.2+ versions will give you an error.
That works great except for MetroUI and Apple 4S. Neither of which seem to want to uninstall from the play store and there's no app entry to hold down on to force deletion.
Plus ESfilemanager isn't letting me go to the system menue else I'd delete the apk there and while ReLaunch /will/ for some reason let me go to /system/apps since it won't let me move the library.apk back to the app folder from backup I'm not sure I trust it to not somehow fubar a delete.
Plus my sister deleted my nook backup image.
Any ideas how to safely clear these thins for someone that's clueless on how to use ADB from ubuntu 12.04? A link to an idiot's guide would be nice if nothing else.
Goggles2114 said:
That works great except for MetroUI and Apple 4S. Neither of which seem to want to uninstall from the play store and there's no app entry to hold down on to force deletion.
Plus ESfilemanager isn't letting me go to the system menue else I'd delete the apk there and while ReLaunch /will/ for some reason let me go to /system/apps since it won't let me move the library.apk back to the app folder from backup I'm not sure I trust it to not somehow fubar a delete.
Plus my sister deleted my nook backup image.
Any ideas how to safely clear these thins for someone that's clueless on how to use ADB from ubuntu 12.04? A link to an idiot's guide would be nice if nothing else.
Click to expand...
Click to collapse
>TUTORIAL - EVERYTHING ABOUT ADB - Fully Illustrated
http://forum.xda-developers.com/showthread.php?t=1241935
-use ADB to install NookColorTools
-go to 'manage applications' (in NCT)
-delete what needs to be deleted
Deleting files is needed only when you want to get rid of a system app.
Don't forget to mount system partition with write permissions. Otherwise you will not be able to copy NCT to /system/app/
You are a lifesaver (and is this thing pinned? I don't recall seeing it pinned. Hell best way of hiding a thread is put it at the very top with a sticky and making it red blinky bold letters.)
OK derp. That guide's windows. Need something linux-centric. I've a feeling after the initial setup it's similar
On command line 'adb devices' gets me nothing even with nook in usb mode.
Edit again: http://rootzwiki.com/topic/20770-gu...-adb-and-fastboot-in-linux-ubuntu-and-mint12/
Using that guide. Will edit/respond with results.
Edit the Third: Odd. Didn't have ot use ADB. ReLaunch let me install. Now to figure out wtf about mountingaccessing internal storage as root.
Thank you for your replies!
I prefer the ADB method via USB, I do not like to modify things by touch screen.
I installed ADB, server is running and nook is connected by usb cable, but no devices are found
Google does not help me (or I am failing with keywords) and I do not want to use a wireless connection.
yell! said:
Thank you for your replies!
I prefer the ADB method via USB, I do not like to modify things by touch screen.
I installed ADB, server is running and nook is connected by usb cable, but no devices are found
Google does not help me (or I am failing with keywords) and I do not want to use a wireless connection.
Click to expand...
Click to collapse
Make sure you have the driver installed properly. See the wiki article on installing the ADB driver for the Nook Simple Touch.
yell! said:
Thank you for your replies!
I prefer the ADB method via USB, I do not like to modify things by touch screen.
I installed ADB, server is running and nook is connected by usb cable, but no devices are found
Google does not help me (or I am failing with keywords) and I do not want to use a wireless connection.
Click to expand...
Click to collapse
Use "ADB konnekt" to connect with your pc via wifi.
If you want to connect via USB you have to turn on "USB DEBUGGING" (manually of using NookColorTools)
and add correct udev rules (http://ubuntuforums.org/showthread.php?t=1918512) on linux.
There are some differences in adding udev rules in different versions of Ubuntu/Debian/Mint. I have no idea on how to do that on Fedora,Gentoo etc.
Don't know how to do that on windows. This info can be found using a search engine x]. Look for ("android device adb setup windows")
I got tired of having to jump between a bunch of threads when setting up my Glowlight 3. So I'm consolidating directions into one post in the hopes that it'll save others time and trouble. Credit for instructions should go to the people who actually wrote them: arnchav of mobileread; RyogoNA, Silent eInk, cazar and Renate NST here on xda; and everyone who figured out the root exploit, sideloading, the devs behind Relaunch, RelaunchX and F-Droid. Material lifted from their original posts (linked at the bottom).
Now, this is going to walk you through doing a few things:
A) Setting up a progam called ADB on your computer so that it can talk to your NG3
B) Adding a "Launcher" app to your nook so that you can access other apps you sideload later
C) Root theNook so that you can do more stuff with the settings, including the ability to...
D) Fix a bug that, after installing a launcher, causes the NG3 to get stuck on the loading screen after rebooting
Before you start, you need to set up ADB on your computer. Follow the instructions linked here. The rest of this post will assume you're using Windows, but won't be hugely different from other OSs.
Here we go:
To set up ADB on your nook:
1. On your Nook, go to Settings>About. You should see the serial number, app version, etc. At the top of that page, there is a nook icon. Tap that icon rapidly until the developer menu opens.
2. Tap "Android Development Settings" and check the box for "USB debugging".
3. At the Developer options screen you are on (where you checked the box), hit the back arrow at the top-left of the screen to go back. But do not exit the developer menu.
4. On your computer, open a command prompt and navigate to the folder where you put adb (in my case I typed in "cd adb/platform-tools")
5. Plug the USB in to the nook. When the nook prompts you to turn on USB mode, do so. At the adb command prompt, type adb devices. ADB should recognize the nook, but say that it is unauthorized.
6. From windows, eject the nook to disconnect nook's file sharing. Once the nook's USB file sharing screen goes away, you should be able to see the developer menu again. Tap "Allow Debugging" one time! There will be no confirmation, just do it one time.
6. Unplug the USB, plug it back in, turn on USB mode when prompted. Back in the command prompt, type adb devices again. This time it should see the device and simply say "device" where it used to say "unauthorized". Congratulations! You can now install a launcher.
To install a launcher, like RelaunchX
1. Download your launcher apk of choice. If you don't know what to pick, try RelaunchX, and download the latest version from plusz's thread here: https://www.mobileread.com/forums/showthread.php?t=284418 (n.b. To make things easy, ignore his suggestion to get it through F-Droid as you'll need a new launcher to use F-Droid in the first place. Just download the apk).
2. In Command prompt, type adb install <filelocation>, where filelocation is the complete address of the apk. If you have file explorer open, you can just type adb install then a space, then drag the file in to the terminal and it will copy the location for you. (Make sure again that there is a space between "install" and the path or it won't work).
3. ADB should do it's thing and you will get a "success" message in Terminal.
4. Eject the nook from the PC. Shortly after the connection is cut, a window should open on the nook allowing you to select either the nook launcher or your new launcher. If you use RelaunchX, you may get a warning that it wasn't built with this device in mind. You can ignore it, it works great on this device.
This is all great, except there's a bug in how B&N set up the device that only shows up if you install a new launcher. If you reboot the device, you'll be stuck on the boot animation until you do weird things like hold down the power button for a long time to pull up the reboot/power off options (only seems to sometimes work). To fix that, we actually have to disable, remove, or replace the boot animation file itself.
To root:
1. Download the modified Glowlight Plus script attached here ("rootGL3.zip" - almost identical to cazar's rooGLP-3 script package, but with one line changing the model number from 510 to 520)
1. Enable USB debugging in Developer options
2. Connect USB cable and make sure your nook is showing up in 'adb devices'
3. Extract rootGLP.zip and run rootnook.cmd (or rootnook.sh on linux)
To fix (read: disable) the buggy boot animation:
1. Connect your nook to the computer again
2. (windows) open a command prompt and and navigate to the folder that adb is in.
3. Enter the following commands, in order:
Code:
adb shell
su
mount -o remount, rw /system
mv /system/bin/bootanimation /system/bin/bootanimation.bak
reboot
OPTIONAL: To restore a working boot animation (steps above will replace broken boot animation with a black screen that goes away after a few seconds)
1. Download the attached zip
2. If it's not still connected, connect the Nook to the computer again and tap the button on the nook to turn on USB mode when prompted,
3. On your computer, open up the Nook in Explorer(/Finder/your file manager of choice). Open up the NOOK Folder if you see one.
4. Copy the file inside the zip (bootanimation) to that folder on the Nook.
5. Eject the nook (as in, in windows, click the option to safely remove it as a device) but keep it physically connected
6. Open a command prompt(/terminal/whatever you use for adb) and navigate to the folder that adb is in.
7. Enter the following commands:
Code:
adb shell
su
mount -o rw,remount -t ext4 /dev/block/mmcblk0p5 /system
cp /storage/spsd/NOOK/bootanimation /system/bin/bootanimation
cd /system/bin
chmod 755 bootanimation
reboot
You now have a rooted Nook Glowlight 3 that'll boot into a launcher of your choice! You can now sideload apks of your choice using adb the same way you installed RelaunchX.
Have fun!
Sources for these instructions:
https://www.mobileread.com/forums/showpost.php?p=3632665&postcount=118 (how to sideload onto nook 3)
https://forum.xda-developers.com/showpost.php?p=75717722&postcount=113 (same as above, diff user)
https://www.mobileread.com/forums/showthread.php?p=3632665#post3632665 (to get RelaunchX)
https://forum.xda-developers.com/showpost.php?p=64191791 (for nook GLP rooting script)
https://forum.xda-developers.com/showpost.php?p=76042888&postcount=127 (to fix boot animation loop)
HELP! I DID THIS A LONG TIME AGO AND NOW MY NOOK GLOWLIGHT 3 IS STUCK ON THE LOADING SCREEN!
Don't worry, this is fixable. What's happened is that Barnes and Noble pushed out a system update that undid almost everything except that part that breaks the boot animation thing (specifically it overwrites the directory with everything that gives you root access and a working boot animation, but left your custom launcher in place).
All you have to do is re-do most of the steps above. Start from the "to root" step - even if the device is stuck on a boot animation, you should still be able to use adb. After redoing the steps, your GL3 should work normally again.
Unfortunately it looks like this is going to happen every time B&N pushes a system update, but that's not that often.
If someone knows a step-by-step way to replace the stock bootanimation with the 4.6 bootanimation file (zipped up and attached here, thanks to RyogoNA), let me know and I'll update the OP. I tried used adb shell to copy it to /system/bin/bootanimation, but I still just get a black screen on startup in its place.
jptiger said:
I still just get a black screen...
Click to expand...
Click to collapse
Mmm, did the copy of bootanimation work?
Did you:
Code:
/system/bin # chmod 755 bootanimation
Tried that, but I got an error about a Read-only file system, even after using su. What's the basic thing I'm missing?
jptiger said:
Tried that, but I got an error about a Read-only file system, even after using su. What's the basic thing I'm missing?
Click to expand...
Click to collapse
Got a private message pointing me to the command I was missing, apparently from a how-to page in Russian. For anyone else trying to do this, try:
Code:
mount -o rw,remount -t ext4 /dev/block/mmcblk0p5 /system
cd /system/bin
chmod 755 bootanimation
Can't get adb devices to give autorhized access to ng3 w 4.9.2.24 os
First off thank you for doing this work, and I am excited to root my ng3!
In trying to follow your directions on rooting, I am hitting a snag. The os is not operating in the anticipated manner. When I do the usb unplug and replug and hit the usb debugging checkbox I can not get authorization.
Please help!
Thanks in advance!
Trouble with root
Hi,
Thanks for putting this all together. However, I'm having trouble with the root step.
You'll have to put the link together because as a new poster I can't post links.
Any help would be appreciated!
imgur . com
/a
/ckm0jRq
xelcho said:
First off thank you for doing this work, and I am excited to root my ng3!
In trying to follow your directions on rooting, I am hitting a snag. The os is not operating in the anticipated manner. When I do the usb unplug and replug and hit the usb debugging checkbox I can not get authorization.
Please help!
Thanks in advance!
Click to expand...
Click to collapse
Hmm. Did you get authorization after following the directions under "To Set up ADB on your Nook"?
L3R0k2b2 said:
Hi,
Thanks for putting this all together. However, I'm having trouble with the root step.
You'll have to put the link together because as a new poster I can't post links.
Any help would be appreciated!
imgur . com
/a
/ckm0jRq
Click to expand...
Click to collapse
Ooh, that's exotic. I've never seen that before. Just going off the error text, you might need to find a newer version of adb somewhere online. Try that or try a different computer?
Adb is super stable for many years now, although it can fail to connect to your device properly for many reasons.
Can you reach developer menu navigating with nooks keys? I sometimes enable /disable /enable usb Debug, followed or preceded by revoking all PC's permissions. These are all standard options in android phones s system. menus. Rebooting nook may help too, and numerous times I've seen bad cables get in my way. Tip, just because a cable works with one device is not a guarantee it's working everywhere.
RE: STEP 6. "From windows, eject the nook to disconnect nook's file sharing."
Note:
1. The location of the eject menu is where you typically see "Safely remove hardware and eject media" in the windows taskbar.
2. After attempting to eject your Nook GLP, you may get a window that pops up that says "Windows can't stop [your device]" because a process is using it -- and you may not be able to track down which process is using it (for me, closing all windows and apps didn't help). If this is the case, hit "WINDOWS+X >> Shut down or Sign Out >> Sign out" -- then log back in. This *should* stop all processes and allow you to proceed to the next step (it did for me).
*My Nook GLP recently updated and I lost root. This also caused the startup animation to continue non-stop (but holding the power button and then selecting cancel from the options allowed me to select which launcher I wanted to use).
** Additionally, I had one other issue. My (windows) laptop wouldn't recognize my nook at all. Turns out it was the USB cable. So if you have that issue, try using a different USB cable -- preferably the one that came with your nook.
Missing epubs
So I followed the instructions, everything comes up great. I can sideload apps, I have a new launcher etc. But if I copy a file (epub or otherwise) into the NOOK folder on my PC and then browse to the NOOK folder using the file manager on the Nook reader, its empty. At first I thought it was an issue with the file manager, so I installed another one. Same thing.
When I load epubs into the NOOK folder and open the B&N launcher, it sees the books and adds them to my library. But for whatever reason I can not find where the epubs are using a file manager. I even tried using grep to search for the file I copied in adb shell but it doesn't come up with anything. Anyone know whats going on and how to fix it?
Never mind its under /storage/spsd/
mount: Operation not permitted
I get this error after typing in the mount -o ... command.
Any help apprecidated!
root file missing
Hey, @jptiger In the setup instructions the rootgl3.zip file is missing a link now... Does anyone have an active link to this file, or another working root process? I couldnt find one by searching online..
Misssing files
I rebooted my nook recently and it comes back up but when I got /storage/spsd/ its empty. When I attach my nook to my pc, I can see all my books. So I did the following:
Code:
adb shell
su
busybox find / -name "*.epub"
The only files that it shows are the sample epubs that come with the Nook. I am kind of stumped as to how the files show up when I browse the nook as a usb drive. But will not show up when browsing for them via the nook itself or adb. Any thoughts?
Heretic09 said:
I rebooted my nook recently and it comes back up but when I got /storage/spsd/ its empty. When I attach my nook to my pc, I can see all my books. So I did the following:
Code:
adb shell
su
busybox find / -name "*.epub"
The only files that it shows are the sample epubs that come with the Nook. I am kind of stumped as to how the files show up when I browse the nook as a usb drive. But will not show up when browsing for them via the nook itself or adb. Any thoughts?
Click to expand...
Click to collapse
It looks like the flash memory on the Nook maybe going bad. There was a bunch of .chk files in the hidden LOST folder. Reformatting it and copying the books back to the nook seems to have fixed the problem for now. I may have to invest in the Kobo Clara HD in the future.
andjosgra said:
Hey, @jptiger In the setup instructions the rootgl3.zip file is missing a link now... Does anyone have an active link to this file, or another working root process? I couldnt find one by searching online..
Click to expand...
Click to collapse
That's weird. I don't know why they took down the original attachment. I can't find it, but I've gotten the on from the NGP+ and modified it the way they did with the originals. It's attached to this post, give it a shot.
EDIT: I uploaded the version attached here to the OP, but with the original name. The two zips have the same contents.
Heretic09 said:
So I followed the instructions, everything comes up great. I can sideload apps, I have a new launcher etc. But if I copy a file (epub or otherwise) into the NOOK folder on my PC and then browse to the NOOK folder using the file manager on the Nook reader, its empty. At first I thought it was an issue with the file manager, so I installed another one. Same thing.
When I load epubs into the NOOK folder and open the B&N launcher, it sees the books and adds them to my library. But for whatever reason I can not find where the epubs are using a file manager. I even tried using grep to search for the file I copied in adb shell but it doesn't come up with anything. Anyone know whats going on and how to fix it?
Click to expand...
Click to collapse
adb can't access NOOK storage when it's still connected to PC. Eject the device under BNRV520 (should say "NOOK: (F" or similar), but do not disconnect. Then you can find files in both adb and later NOOK's file manager when you disconnect. (should be under /storage/spsd/)
Guide is great though. Thank you all so much! Fast and easy! (unlike making a B&N account)
btw, I had to run "adb shell su" instead of 'adb shell' -> 'su' to get su priviledge, so maybe try that.
what is the adb command to manually launch relaunchx? the launcher option stopped working, and i can't get it to run at all.
Happy to report that the excellent instructions work great on the new 7.8" Glowlight Plus that got released yesterday. Change the model number to BNRV700 in the rootnook.cmd file and you're good to go!