Related
the subject says it all. I've been trying to push apps to my encrypted xoom all afternoon without any luck...
I'll go ahead and admit upfront that I am a noob when it comes to using the sdk... so that could also be a major factor.
adb install (insert exact location+ filename.apk for the app you want to install)
I just tested it out
for example
adb install C:/abc.apk
What command are you using? What error message are you getting? Did you do a adb remount to make sure that the /system/app path is writable?
You can always do an adb install [package name].apk as well.
scsa20 said:
What command are you using? What error message are you getting? Did you do a adb remount to make sure that the /system/app path is writable?
You can always do an adb install [package name].apk as well.
Click to expand...
Click to collapse
I just tried to execute adb remount (I had not until you mentioned it), but I get a "remount failed: operation not permitted".
Code:
Hannibal:platform-tools dmoore$ ./adb install /Users/dmoore/Documents/android-sdk/platform-tools/AsusReader.apk
1259 KB/s (7747001 bytes in 6.007s)
pkg: /data/local/tmp/AsusReader.apk
Failure [INSTALL_FAILED_DEXOPT]
Additional information: I am on a MacBook Pro using the latest version of the SDK (downloaded it yesterday).
try typing "adb devices" if it does not list your xoom try installing or re-installing the motorola usb drivers
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
just noticed the macbook part
http://www.samsung-tablets.com/motorola-xoom-usb-driver-for-pc-and-mac-download.html/
Ok... back to me being a complete when it comes to the SDK (and the Xoom in particular)...
My Xoom is completely stock... it has not been rooted or otherwise modified.
With that being said, is there some trick to getting the file system to mount as r/w? Do I need to reboot in to recovery before adb remount will work?
Sic123 said:
just noticed the macbook part
http://www.samsung-tablets.com/motorola-xoom-usb-driver-for-pc-and-mac-download.html/
Click to expand...
Click to collapse
I've already installed the Android File Transfer app... it only allows me to browse the SD card - not the root fs... unless there's something I'm missing...
dmoore44 said:
Ok... back to me being a complete when it comes to the SDK (and the Xoom in particular)...
My Xoom is completely stock... it has not been rooted or otherwise modified.
With that being said, is there some trick to getting the file system to mount as r/w? Do I need to reboot in to recovery before adb remount will work?
Click to expand...
Click to collapse
you dont have to be in recovery (recovery wont do any good unless you install clockwork recovery) for adb remount to work but if your not rooted you cant push files into the system folder thats the whole point of rooting is to unlock the system files also if your pushing it into /system/app the rom is odexed so you will need the apk plus the odex file
Sic123 said:
you dont have to be in recovery (recovery wont do any good unless you install clockwork recovery) for adb remount to work but if your not rooted you cant push files into the system folder thats the whole point of rooting is to unlock the system files also if your pushing it into /system/app the rom is odexed so you will need the apk plus the odex file
Click to expand...
Click to collapse
I have the odex file, so i'm not terribly worried about that.
My major question would be this though... Do I need to go full blown root, or can I just unlock the device?
Houston, we've got a problem:
I did root on my kindle fire device. Everything worked well by now. Then I tried to copy android.vending_v3.4.4.apk (new market) to /system/app and it did not work even with root permissions, I changed permissions to whole directory /system/app to 777 and then I changed back the permissions for the directory /system/app and set permissions for com.android.vending_v3.4.4.apk to rw-r--r-- a clicked on the file and I got an error, which I didnt record for myself. I turned off and on my Kindle and from this moment it is not possible to start up the device. I stil have Kindle logo flashing. Could you please help me to solve this problem? Is it possible to make any flash? If yes, how?
I would use adb to fix permissions for /system/app, you can find good instructions a couple of pages into stickied thread on unbricking.
problem
I'm doing something wrong. I can not change the permissions from Read-only to Read-write. Can you please write what procedure should I do?
adb devices
List of devices attached
700E002600000001 device
adb remount
remount failed: Operation not permitted
adb -d shell chmod 777 /system/app
Unable to chmod /system/app: Read-only file system
My bugreport: motus[dot]sk[slash]bugreport.txt - its too long to attachment.
Try su
Sent from my SPH-D710 using xda premium
grebec said:
I'm doing something wrong. I can not change the permissions from Read-only to Read-write. Can you please write what procedure should I do?
adb devices
List of devices attached
700E002600000001 device
adb remount
remount failed: Operation not permitted
adb -d shell chmod 777 /system/app
Unable to chmod /system/app: Read-only file system
My bugreport: motus[dot]sk[slash]bugreport.txt - its too long to attachment.
Click to expand...
Click to collapse
You obviously didn't read the thread the above poster is talking about. I give clear instructions on the main post of said thread to fix your problem. If you would read it first you might not be having these issues. If you do continue to have problems please direct them to the appropriate thread (again, the unbricking/restore KF thread).
unbricking/restore KF thread
I have read "[HOW TO] Unbricking/Restoring your Kindle Fire". I did as instructed and I ended phrase "fastboot -i 0x1949 reboot" Kindle fire wrote "Your kindle has detected a problem and must clear app storage". After restart stopped working completely. Kindle logo before unbrick always flashing, but now, only light.
If I kindle fire connect to an ADB report is:
db shell
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
I need to be there again complete image. How do I do? I do not know connect Kindle fire with computer.
These are my notes and guide for rooting the Kindle with 6.2.1 firmware. If I left something out, or something is not working, please leave a comment and I'll try to update.
Credit goes to JCase for the root. Please consider making a donation to him here:
https://market.android.com/details?id=net.andirc.jcasedonate
Original procedure is here:
http://www.androidpolice.com/2011/1...on-kindle-regardless-of-its-software-version/
ADB INSTALL AND TEST - Method 1 (skip to the ROOT INSTALL section if you already have a working ADB)
NOTE: ADB = Android Debug Bridge. It is a command line interface to the android device. A working ADB is required before you can root your Kindle. ADB is installed on a PC and accesses the Kindle via USB cable.
Install Java SE Development Kit 7 on PC
The Android SDK Manager requires Java SDK
http://www.oracle.com/technetwork/java/javase/downloads/jdk-7u1-download-513651.html
Install Android SDK Manager on PC
The Android SDK has the drivers and ADB needed to perform the root procedure
http://developer.android.com/sdk/index.html
Uncheck Android 4.0
Check 2.33
Ensure Google USB Driver is checked
Install to c:\android to make typing easier later on
NOTE: The install can take a long time!
Manually update files so drivers will properly install
Open c:\users\your account name\.android\adb_usb.ini (or c:\documents and settings... if you have XP) and add the following
Code:
0x1949
Open c:\android\extras\google\usb_driver\android_winusb.inf and make additions as shown:
Code:
[Google.NTx86]
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
....
[Google.NTamd64]
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
Install drivers
Find the Kindle device in device manager and update drivers. Point to the location with android_winusb .inf
Verify ADB works
Open a command prompt
CD to c:\android\platform-tools
Code:
adb kill-server
adb devices
If it's working, ADB will return a large number, like this:
Code:
312342134231342 device
ADB INSTALL AND TEST - Method 2
NOTE: I have not tried this, but Vashypooh's app can apparently handle the driver install, and run ADB without installing the above software. If all of this works, then his app would be the best way IMO.
NOTE 2: I've seen a lot of comments suggesting the driver install in Vashypooh's app doesn't work at this point.
http://forum.xda-developers.com/showthread.php?t=1399889
ROOT INSTALL - Method 1
Install JCase's kindleroot_androidpolice.apk
JCase's app gives ADB root access. Once this is done, you still need to install the superuser app
Download kindleroot_androidpolice.apk to PC
http://www.multiupload.com/VNZ6Y41EQF
Ensure the Kindle is connected via USB, and copy file to Kindle sdcard
Using ES File Explorer on Kindle, navigate to the kindleroot_androidpolice.apk and launch
Follow prompts and click root
Install superuser app
Download superuser-2 to PC
http://www.multiupload.com/M2CX14W7Y0
Unzip to c:\download\sufiles
Use ADB to install SU app
Code:
adb root
adb remount
adb push c:\download\sufiles\su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb install c:\download\sufiles\Superuser.apk
adb reboot
ROOT INSTALL - Method 2
NOTE: I have not tried this, but Vashypooh's app can apparently handle the root process.
BurritoRoot (Temporary)
Install Permanent Root with Superuser
http://forum.xda-developers.com/showthread.php?t=1399889
A+ instructions, wish I could write my own that good lol.
jcase said:
A+ instructions, wish I could write my own that good lol.
Click to expand...
Click to collapse
Thanks to you for the root. I hope the guide will help those trying to root!
Thanks for the clear and easy steps.
Great guide Ectoplasmic!
One thing I would add though, in step 5 "Verify ADB Works", before you use the "adb devices" command, you need to type "adb kill-server". If you don't type in "adb kill-server" first, the device won't show up when you use the "adb devices" command. Or at least it didn't for me.
Otherwise, everything worked FLAWLESSLY. I verified I was rooted using Root Checker. Thank you!
zopzop25 said:
Great guide Ectoplasmic!
One thing I would add though, in step 5 "Verify ADB Works", before you use the "adb devices" command, you need to type "adb kill-server". If you don't type in "adb kill-server" first, the device won't show up when you use the "adb devices" command. Or at least it didn't for me.
Otherwise, everything worked FLAWLESSLY. I verified I was rooted using Root Checker. Thank you!
Click to expand...
Click to collapse
Thanks, I added this to the guide.
Hi I use JCase method to root my 6.2.1 KF, then I need to unroot it so my kids can still enjoy the prime video, but I cannot. I try rootkeeper but failed. I also try the "kindleroot_androidpolice.apk" and click the unroot button, but it still cannot unroot. Pls help!
Get help in irc from jcase and vashypool theyll probably be able to help u
tkcctkcc said:
Hi I use JCase method to root my 6.2.1 KF, then I need to unroot it so my kids can still enjoy the prime video, but I cannot. I try rootkeeper but failed. I also try the "kindleroot_androidpolice.apk" and click the unroot button, but it still cannot unroot. Pls help!
Click to expand...
Click to collapse
Unroot in my app (BurritoRoot) does not remove su, it just turns off adb root (which is what my app turns on) sorry for the confusion.
Will add in the future when I release burritomod
Here's the equivalent instructions for Mac
I am pretty new myself, but I'm happy to share what I've come up with so far. I am on a Mac OS X 10.6.8
Download the Android SDK for Mac (dl.google.com/android/android-sdk_r16-macosx.zip), the easiest place to put it is at the top of your user directory, from the browser download window chose your username from places on the left side, then name the zip "Android"
Next from Finder, navigate to the place where you downloaded the SDK, and double-click on it which should unzip it and create a folder of the same name e.g "Android". Open that and inside it will be a folder "tools", and inside that there will be a file "android". Double-click that to run it and the "Android SDK Manager" program window will pop up, you will also see a Terminal window in the background, don't worry about that. Uncheck all the boxes, then check "Android SDK Platform-tools" which should be the third from the top, and click install. This gets you the actual "dab" program.
Once adb is setup, to get it to recognize your kindle fire on your mac, you may need to make an entry in a config file if you haven't already.
Start Terminal Applications > Utilities > Terminal or if you are used to using spotlight, simply type in "Terminal". (here's an intro to using Terminal guides.macrumors.com/Terminal) and navigate to the directory where you have adb, e.g. if you placed it at the top of your user directory that would be
Code:
cd Android
or if you left it in the default downloads directory it would be
Code:
cd Downloads/android-sdk-macosx/
then enter the following commands
Code:
mkdir ~/.android
You may get the following error
Code:
mkdir: /Users/<username>/.android: File exists
If so, that is fine, continue to the next step
Code:
touch ~/.android/adb_usb.ini
open -e ~/.android/adb_usb.ini
TextEdit will open with that file open, you should have an entry in it on a single line that says
Code:
0x1949
if not, copy that in, then save and close it, then
Code:
./adb kill-server
Connect your kindle to the mac if it isn't already, then
Code:
./adb devices
You should see a message like
Code:
List of devices attached
2ED6000600000001 device
On your kindle, make sure you have a file navigation app, the example above ES FileExplorer is excellent and is the one I use from Amazon app store
Download Burrito Root from Android Police ( androidpolice.com/2011/12/23/exclusive-how-to-easily-root-the-amazon-kindle-regardless-of-its-software-version/)
Also download the Superuser.zip from the same page (multiupload.com/ONH28CB1GU) and unzip, then make sure you move the contents "su" and "Superuser.apk" into the same directory as adb
Through Finder copy the "kindleroot_androidpolice.apk" file you downloaded earlier to your kindle, some place like "download" so you can find it easily later
Now on the Kindle, tap disconnect on your KIndle so you can get back to the apps screen, launch the file explorer you installed earlier, navigate to folder you copied it to, e.g. "download" then install the "kindleroot_androidpolice.apk", open it, and go through the steps to launch click "Root"
Back on the Mac, in the terminal window where you had adb going, enter the commands
Code:
./adb root
./adb remount
./adb push su /system/xbin/su
./adb shell chown 0.0 /system/xbin/su
./adb shell chmod 06755 /system/xbin/su
./adb install Superuser.apk
./adb reboot
You should be rooted now, then you can follow the other instructions out there for getting Android market, etc working
TIP
here's a tip if you don't want to have to type in the period and slash ahead of adb every time. from your terminal window enter the
Code:
cd ~
touch .profile
open -e .profile
That will open text editor, and paste in the following line,
Code:
PATH=${PATH}:/Users/<username>/<sdk-directory>/platform-tools
replacing both our user name and the path to where you have sdk e.g. in my case
Code:
PATH=${PATH}:/Users/kbiz/Android/platform-tools
Then close the terminal window and reopen a new one and you should be good to go, now you'll only need to type in "adb".
Let me know if I missed something, trying to give back since this forum has been super helpful.
---------- Post added at 01:04 AM ---------- Previous post was at 12:58 AM ----------
tkcctkcc said:
Hi I use JCase method to root my 6.2.1 KF, then I need to unroot it so my kids can still enjoy the prime video, but I cannot. I try rootkeeper but failed. I also try the "kindleroot_androidpolice.apk" and click the unroot button, but it still cannot unroot. Pls help!
Click to expand...
Click to collapse
OTA Rootkeeper should work but since its not, try this (courtesy rootkindlefire.com/kindle-fire-unroot/how-to-unroot-kindle-fire/)
Code:
adb shell
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
rm /system/app/Superuser.apk
rm /system/xbin/su
reboot
after your Kindle restarts you won't have root and Amazon Video should work just fine.
Hello,
I have successfully rooted my device with the above instructions. While installing the Android market I was abusing of my root privileges and I've successfully "burned" my device. That is, the Kindle won't start up anymore (it stays forever in the initial phase showing the kindleFire logo).
I don't know where else to turn for help so I'm writing about this here. If anyone has hints of how I could recover my kindle from the void, please let me know
Cheers
http://forum.xda-developers.com/showthread.php?t=1356257
Yesssssssssss
Yesssssssssssssssssss. So nice to have root again. My Titanium Backup and SUFBS works again
I had ADB and SDK working when I had my Glacier, but since I have gotten my SGS2, and my Kindle, Android SDK Manager will not open... It just opens a command prompt, and then closes.. I have reinstalled both the SDK Manager and the Java Kit... Any ideas?
EDIT:
I must have messed with something in my system settings somewhere to corrupt a bunch of stuff... I did a system restore to the 18th of December, reinstalled, and everything works perfect now... Oh well! Haha
Hey, I used a combo of the link JCase gave me when I had questions, this guide, and the links off the rootzwiki guide and managed to get it first try. It was actually easier than I thought it was going to be. I've never rooted anything before, I didn't even have ADB or the SDK until tonight. The process (while using both guides and video tut) went smoothly without a hitch. I just finished installing the Android Market but have to wait til morning to access it, as I have no WiFi at home, and its too late for me to be driving to a hotspot. Thank you very much. You(JCase) and your comrades who put this all together f**king rule.
a really clear and easy guide ! - congratulations - you shoud try to let it pin on top !
Ectoplasmic said:
NOTE 2: I've seen a lot of comments suggesting the driver install in Vashypooh's app doesn't work at this point.
Click to expand...
Click to collapse
the reason people have problems with vashipooh's driver installation seems to be the old drivers - they don't manage to clean up the old drivers:
disconnect KF
Open an (elevated for win7) command prompt:
set devmgr_show_nonpresent_devices=1
devmgmt.msc
device manager opens - click "view" - click "show hidden devices"
now you see all devices ever connected/installed
uninstall all devices regarding "kindle" and "android (composite) adb device"
connect KF - will startup by itself
select the most recent driver (that you have installed before by install_driver.bat from KFU) manually (check date/time)
now you should be set up with a good driver installation
btw. i'm on xp - it's working for xp and 7, 32 and 64 bit
As you may know, some Android games especially most Gameloft games are not compatible with the Kindle Fire. So in efforts to find a way to make certain Gameloft games to work such as Modern Combat 2 and Shrek Kart and others, I resorted to editing my build.prop in the systems folder to make my device compatible with the apps. So I copied the original build.prop file, renamed it, and saved it to my SD Card folder. I took the copy I made and I then replaced it with the build.prop from HTC Glacier. (I never knew what could possibly happen) So then to apply those settings you have to reboot the device. I rebooted the Kindle and now it won't boot up. It get's to the Kindle Fire screen when booting up but after several seconds it just shows a black screen. No physical damage has been incurred to it but I feel like my stupid mistake of modding the build.prop resulted in the Kindle Fire unable to boot up correctly. It also isn't recognized by the PC when I hook it up to a USB cable. So far I've found nothing that could help to solve this. I've seen a Factory Default Settings Cable which is a special cable to reverts the device to its factory default settings but I'm not too sure if that would work. I'm in desperate need of help as in I use my Kindle Fire for everyday work and play. Thanks.
EDIT: I've tried adb push and renaming and moving the build.prop into the /system/ but returns that it is a Read-File System Only. Also adb shell and su doesn't work as in it ends up with segmentation fault. I've tried to zergRush root it and permanently root it using KFU but it ends up with 'Cannot Access Package Manager. Is System running?' Also the mount -o rw,remount.....command doesn't work either as it says Permission Denied. All of this would be easy to accomplish if only it ADB allowed me to write onto the /system file.
EDIT**: The biggest issue I'm faced with is the permission settings that prevent my from editing anything. You cannot simply change it from RO to RW because apparently the ADB is not rooted. And I also can't root it because problems exist when accessing either Package Manager or Activity Manager. What I need is a way to access the /system files without a root (non-rooted). Either that or enable fastboot because I cannot access that either. On a reply on the second page is the resulting lines when changing bootmodes on the KFU.
Don't know how to fix your problem, but just wondering, did you just completely replace the kindle fire build.prop with the HTC glacier? Because you can't do that, it will, as you have learned, mess up your device.. Your supposed to edit the build.prop and just change a few things. Next time read up on the subject before deciding to mod the device you use everyday...
the cable you'r talking about is a "factory cable" it forces the kf to fastboot mode - it don't restore any settings !
you need fastboot mode to install fff (firefirefire - custom bootloader) and twrp (recovery)
do you allready have installed fff & twrp (or cwm) ?
if you have twrp installed and booted into then you have adb command available and can copy back the original build.prop
Did you remember to restore the read/write permissions to build.prop? It should be set to 644.
As already stated, your not supposed to replace the whole file, build.prop tells android which device you have, so now Android thought and configured itself to different hardware config. which is not available to it. Adb seems like the only option.
I should have really looked more into it before modifying the build.prop. I replaced the ENTIRE build prop with the build.prop of HTC Glacer. (I know, i know I was stupid) And referring to the factory cable, I don't think I'll resort to that: too time consuming. In regards to the last person that posted before me who said that my only option was ADB could you elaborate? Thanks for all your feedback.
gococogo321 said:
I should have really looked more into it before modifying the build.prop. I replaced the ENTIRE build prop with the build.prop of HTC Glacer. (I know, i know I was stupid) And referring to the factory cable, I don't think I'll resort to that: too time consuming. In regards to the last person that posted before me who said that my only option was ADB could you elaborate? Thanks for all your feedback.
Click to expand...
Click to collapse
Your going to have to use adb to basically remove the HTC Glacier build.prop and replace it with the original build.prop.
For example:
Adb remount <- allows you to mount system as rw
Adb pull /path-to-original/build.prop
Adb push build.prop /system
Adb shell chmod 644 /system/build.prop <- sets permissions to rwrr
Adb reboot
Sent from my Kindle Fire using xda premium
You dont have access to recovery? Either TWRP or CWM?
daggy1985 said:
Your going to have to use adb to basically remove the HTC Glacier build.prop and replace it with the original build.prop.
For example:
Adb remount <- allows you to mount system as rw
Adb pull /path-to-original/build.prop
Adb push build.prop /system
Adb shell chmod 644 /system/build.prop <- sets permissions to rwrr
Adb reboot
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
I tried doing that but it says something like Access Denied or Read-Only File System when i try to push the build.prop into it.
gococogo321 said:
I tried doing that but it says something like Access Denied or Read-Only File System when i try to push the build.prop into it.
Click to expand...
Click to collapse
Did you use the 'adb remount' command? Sometimes, when attempting to push a file to the system, I get the 'read-only file system' and I have to issue adb reboot followed by adb remount and then push the file again. It seems after a time the mount system as read write automatically goes back to read-only.
Sent from my ADR6400L using xda premium
Have you got TWRP or ClockworkMod?
Because you could flash a new rom then.
abd - root mode
Perhaps, running adb in root mode will
allow you to push the original build.prop
back. Then execute "adb remount / rw" to mount the
root directory as read/write. Hopefully you will be able to push
it then follow daggy1985's instructions.
* In Win 7, type "cmd " at the 'SEARCH/RUN' and hold
shift + ctrl while hitting 'Enter' to put yourself
in Admin mode which apparently makes adb work in root mode when you launch it.
* Xda-dev is the coolest site for Android that I have seen. Kudo's to everyone participating.
sum1nil said:
Perhaps, running adb in root mode will
allow you to push the original build.prop
back. Then execute "adb remount / rw" to mount the
root directory as read/write. Hopefully you will be able to push
it then follow daggy1985's instructions.
* In Win 7, type "cmd " at the 'SEARCH/RUN' and hold
shift + ctrl while hitting 'Enter' to put yourself
in Admin mode which apparently makes adb work in root mode when you launch it.
* Xda-dev is the coolest site for Android that I have seen. Kudo's to everyone participating.
Click to expand...
Click to collapse
Thanks but I have actually been running it from Administrator from the very beginning. I've used Kindle Fire Utility KFU and it says that ADB Server is Online and my Bootmode is 4000 but it says ADB root: No. And whenever I choose any bootmode whether it be Normal, Fastboot, or Recovery, it always shows this:
***********************************************
* Activating Normal (4000) *
***********************************************
Installing BurritoRoot, Courtesy of Jcase of TeamAndIRC!
1393 KB/s (1164225 bytes in 0.816s)
Error: Could not access the Package Manager. Is the system running?
Activating BurritoRoot...
Error type 2
android.util.AndroidException: Can't connect to activity manager; is the system
running?
Elevating the Shell...
* daemon not running. starting it now *
* daemon started successfully *
/data/local/tmp/BurritoRoot3.bin: permission denied
mount: Operation not permitted
mount: Operation not permitted
failed to copy 'files\rbfb' to '/system//rbfb': Read-only file system
Unable to chmod /system/rbfb: No such file or directory
Unable to chmod /system/rbfb: No such file or directory
mount: Operation not permitted
mount: Operation not permitted
***********************************************
* Root Activated *
***********************************************
The kindle is successfully running in root mode.
<idme> Invalid permission
reboot: Operation not permitted
Same goes for the Temp Burrito Root and installing FFF and TWRP. It always shows something about cannot access Package manager. I have no clue what the Package Manager even does but apparently I cannot find a solution to that.
I think you need to get a factory programming cable like we talked about on gtalk. I'm confident that will fix this.
Sent from my DROIDX using Tapatalk
I used android commander for windows, mounted system in TWRP and used android commander to copy a new working build.prop to the right place.
With a cable from my htc desire.
would make a little test:
issue "adb shell"
if you get a error message your up to a factory cable because the system shell is messed up and you have no possibility to get to fastboot mode to install fff & twrp
if you get a $ or # prompt you can resume and try "mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system" to mount system in read/write mode
daggy1985 said:
Your going to have to use adb to basically remove the HTC Glacier build.prop and replace it with the original build.prop.
For example:
Adb remount <- allows you to mount system as rw
Adb pull /path-to-original/build.prop
Adb push build.prop /system
Adb shell chmod 644 /system/build.prop <- sets permissions to rwrr
Adb reboot
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
hey, I've tried to remount my rooted galaxy y, fall in for same problem.but there show this message; "remount failed: Operation not permitted"
my device's usb debugging mode was off in last entire.
what I have to do now?
how did u edit build.prop in the first place if u don't have root and this might help
http://yaseminavcular.blogspot.com/2012/01/how-to-get-bricked-kindle-fire-back-to.html?m=1
Sent from my R800i using Tapatalk
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!