Related
Ultimately... All I'm trying to do is put my custom ringtone on the internal memory so that it still plays correctly when the sd card is connected to my computer. (Though I certainly wouldn't mind removing the obnoxious "boot_att.ogg" file as well.) But I keep getting thwarted. First by the discovery that there's no /home directory (which kind of weirds me out, but that's a whole 'nother story).
Anyway, my phone is rooted with z4root, and I'm trying to do this by two different methods. [Correction: It would be better to say that I've tried this using two different programs] I've tried using "adb shell," and I've tried using "Android Terminal Emulator". I can successfully use su in both of them (but if I can't rewrite anything, then I don't see what the difference is). Then I go to the directory on my sd card where the cell ring is and I type
cp cell\ ring.mp3 /system/media/audio/ringtones/
And it replies
cp: /system/media/audio/ringtones/cell ring.mp3: Read-only file system
So, I found these instructions that say to use "mount -o rw,remount -t yaffs2 /dev/block/mtdblock3" (though I think it needs to be "mtdblock7" for mine) or "mount -o rw,remount -t rootfs /" But when I do either of those, it returns
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Which I take to mean that the "mount" command isn't being used correctly (and my experience with the mount command on desktop bash is limited, so I don't have any clue how to correct it).
It's worth noting that I have the exact same results in both adb shell and Android Terminal Emulator.
So, I found another thread (I think one on XDA) that said that I need to be in recovery mode to write to /system, which kind of makes sense. But I have no clue how to do that. And Google is not helping. The only instructions I could find said to turn the phone off and hold down the camera and volume up button. Which did nothing. And it's a good thing nobody was watching because I'm sure I looked like an idiot.
So... I guess I'll have to ask, how do I get into recovery mode? But at this point, I keep coming across so many absurd things keeping me from this that I wouldn't be surprised if next I get an error.
Therefore, my question is this: Is there a way to get into recovery mode, or, alternatively, is there a way to keep my ringtone working even while my sd card is connected to my computer?
Do you have busybox installed?
Have you tried Root Explorer? It has a button to toggle read-write and read only in a folder.
I do have busybox installed. I have no idea what it does, but I installed it in an attempt to enable sideloading (which I have yet to successfully do; apparently the file isn't in the same place on the Flipside as the Captivate and I was going by a Captivate guide).
I have not yet tried Root Explorer. I know this sounds stupid since it's just four dollars, but I tend to shy away from mobile programs that cost money. (Don't know why, I've been that way since my black and white palm pilot.) But, that's just something that's weird about me, lol. I'll get Root Explorer tomorrow and come back.
Busybox is a set of command line utilities. More Info. The link in my previous post is to an installer for Busybox. Busybox provides a set of commands that can be used and many of the tutorials on modifying an android phone use them. Some don't clearly state Busybox is required.
If you are using this thread as a guide to enabling installation from unknown sources be sure to read the whole thread. In particular this post.
Mission accomplished: Root explorer worked perfectly. I saw it in the marketplace before, but I didn't know it can change read/write privileges. (I didn't get it because I thought it was going to have the same effect as Android Terminal Emulator, just without the GUI. Obviously, I am pleasantly corrected.)
And I have a correction: I did not have BusyBox installed; I had the installer installed. But it is installed now.
Thanks also for the links; sideloading is on my to-do list, after removing AT&T bloatware.
And I have one quick question: Do you (or anybody reading) happen to know if it'll be ok if I remove that boot_att.ogg file in /system/media/audio? I don't know if AT&T designed it so that the phone will crash without it, so I thought I'd ask before removing it.
adanedhel728 said:
. . . .
And I have one quick question: Do you (or anybody reading) happen to know if it'll be ok if I remove that boot_att.ogg file in /system/media/audio? I don't know if AT&T designed it so that the phone will crash without it, so I thought I'd ask before removing it.
Click to expand...
Click to collapse
I have not tried any mods of the boot sound. I would suggest that you replace the file with one that is the same name but just silence if removing it does not work.
Mounting file system as Read/Write
I too can affirm that the "Root explorer" app works perfectly for toggling the Read Only File System to Read Write.
I have a Samsung Captivate from AT&T that I upgraded to Froyo (2.2) using the official release from Samsung via the Kies Mini interface. First, I can say that was very worth it. Love 2.2 much better than stock 2.1
I rooted the phone with SuperOnceClick1.7 (had to have a Windoze OS to run that though) that I got from XDA developers and it worked like a charm. I then removed all the bloatware that AT&T likes to inflict upon its users by using "Titanium Backup." Finally, I added "Terminal Emulator" and verified that the su command was working and then "cd" to the "/etc" folder where the "PowerOn.wav" file is for the annoyingly loud startup sound is to delete it. When I issued the "rm" command to delete the file, got the dreaded "can't delete dueo the Read-only file system" or something very similar. Tried using the Android SDK via adb and that gave exact same results.
What to do?...Found this thread that gave great advice that "Root explorer" does work to toggle the R/O to R/W so the file could be deleted.
Thank you marvin02 for the great lead!!!
I have removed the "boot_att.ogg" file without any problems and went as far as swapping out the "bootanimation.zip" also without any problems. Now using CyanogenMod 5 boot animation but... haven't had any luck replacing the .ogg file for a custom startup sound. Tried encoding audio to the same specs as the original but keep getting this strange noise at boot time instead. Just thought I'd throw that in.
Quick question...
I just downloaded the free explorer from Speed which makes Root Explorer.
don't see any button to change read only to read/write. Is that a feature only in the paid Root Explorer?
Thanks from a Noob.
Edit: Just so if there are any other noobs asking... Yes, need to get the paid version to be able to write in system folders.
The free version is not able.
How can I activate God Mode on a rooted XOOM? I want to nullify some stock apps, but Root Explorer is saying they are read only.
Thanks.
[edit] Changed the thread question.
LOL. I didn't know we were playing Quake.
What do you mean by god mode. You already have root. That's all you should need.
Sent from my Nexus One using XDA App
lol.
That might not be the correct term, and it may require a custom rom. Not sure, but on Project Elite for the OG Droid, there's an option under General>System called God Mode that gives you full access to files on the system. That may just be what Actngrezy calls it in PE.
I just want to rename some of the apps that were included on the XOOM. Specifically, I want to nullify the Quick Office apk so I can install the NI Adam version. When I navigate to the apk in Root Explorer, I get an error telling me it's a read only file. I never got that error with the Droid. I can change whatever I want to on that device.
Did you click on mount r/w in root explorer
arrtoodeetoo said:
How can I activate God Mode on a rooted XOOM? I want to nullify some stock apps, but Root Explorer is saying they are read only.
Thanks.
Click to expand...
Click to collapse
Did you install superuser? if so make sure you have allowed root explorer in it. Then on the top left hand side in root explorer hit mount r/w
arrtoodeetoo said:
lol.
That might not be the correct term, and it may require a custom rom. Not sure, but on Project Elite for the OG Droid, there's an option under General>System called God Mode that gives you full access to files on the system. That may just be what Actngrezy calls it in PE.
I just want to rename some of the apps that were included on the XOOM. Specifically, I want to nullify the Quick Office apk so I can install the NI Adam version. When I navigate to the apk in Root Explorer, I get an error telling me it's a read only file. I never got that error with the Droid. I can change whatever I want to on that device.
Click to expand...
Click to collapse
Im just visiting the forum to steal a few files to compare with atrix , how ever if i read your cleverly phrased question correctly and you are trying to remove/freeze some apps that came on the Xoom and you are getting read only error its because to modify anything in the /system dir you need to
1. back up anything you might remove via adb pull or via adb shell cp
2. adb shell
3.su
4. mount -o rw,remount (what ever the path to zoom block is i dont know cause i dont have one ) exp /dev/block/mmcblk0p12 /system
from there you can remove what ever you want out of system dir
5. exp. rm /system/app/quickoffice.apk
Thanks! I never noticed that button before. lol.
you can also get a system uninstaller in the market that will do it for you just the same, I usually use that in case there is more included than just the apk file
PaulG1488 said:
Did you click on mount r/w in root explorer
Click to expand...
Click to collapse
x 2
Sent from my Xoom using XDA Premium App
I thought about the uninstaller thing, but I'd rather not uninstall anything that came on the XOOM just in case. I just add an extra .null at the end of the apk (and associated files, which are easy to find) in case I need to restore them.
For instance, the NI Quick Office app force closes when you just breathe on the freaking tablet, so I had to restore the default one.
Hi All,
I set out to flash my tablet back to stock with the goal of copying some of the awesome asus-specific widgets and applications and installing them back on my tablet after I re-rooted/modded it. I accomplished part of this goal by finding some of the .apk's I wanted, like the Asus weather & battery widgets, the Supernote.apk, anda few others (I still wasn't able to find the Swype Keyboard.apk file)
Anywho, I tried to install the .apk's on my tablet after re-installing cm9 and rooting it but it just says "Application not installed". Anyone have any ideas? And can anyone elaborate on how to copy that swype keyboard APK that I desperately want? I found the other .apk's in the /system/app folder but swype wasn't there.
My other questions relate to CM9:
1) is there any way to decrease the boot time for CM9, or at least customize the boot screen?
2) I'm currently running an older version of cm9 (rc0 unofficial) and I have the stable rc1 of cm9 but when i tried to flash it, it didn't work (i can get the exact error message if needed). Did I do something wrong in updating or is RC1 not compatible with the device? Should I just wait till CM10 comes out?
3) When I initially rooted/flashed cm9, I was able to connect my tablet to my computer and the root of the / directory, but after flashing stock and trying again, I don't have the same luck. Is there some step I missed?
I appreciate any responses, thanks.
- Opethfan89
3 days, 300 views, no responses. BUMP anyone?
opethfan89 said:
Hi All,
I set out to flash my tablet back to stock with the goal of copying some of the awesome asus-specific widgets and applications and installing them back on my tablet after I re-rooted/modded it. I accomplished part of this goal by finding some of the .apk's I wanted, like the Asus weather & battery widgets, the Supernote.apk, anda few others (I still wasn't able to find the Swype Keyboard.apk file)
Anywho, I tried to install the .apk's on my tablet after re-installing cm9 and rooting it but it just says "Application not installed". Anyone have any ideas? And can anyone elaborate on how to copy that swype keyboard APK that I desperately want? I found the other .apk's in the /system/app folder but swype wasn't there.
My other questions relate to CM9:
1) is there any way to decrease the boot time for CM9, or at least customize the boot screen?
2) I'm currently running an older version of cm9 (rc0 unofficial) and I have the stable rc1 of cm9 but when i tried to flash it, it didn't work (i can get the exact error message if needed). Did I do something wrong in updating or is RC1 not compatible with the device? Should I just wait till CM10 comes out?
3) When I initially rooted/flashed cm9, I was able to connect my tablet to my computer and the root of the / directory, but after flashing stock and trying again, I don't have the same luck. Is there some step I missed?
I appreciate any responses, thanks.
- Opethfan89
Click to expand...
Click to collapse
I haven't tried this, but it may work. If you have ADB on your computer, try doing an adb push [name of file].apk /system/app/
If you can't do that, try copy/pasting them there using a root explorer on your device itself. Make sure the permissions are set properly (I don't remember what they are off the top of my head).
After doing that, reboot. See if it works.
As for your CM Questions:
1) I'm not sure if you can reduce the time. For customizing the animation, look at something like Rom Toolbox Pro (which also includes a root explorer like I mentioned above).
2) All CM9 TF300T downloads are located here: http://get.cm/?device=tf300t RC1 is listed there so I'm assuming you did something wrong (what's the error you get?)
3) Did you re-root? I'm not sure I understand.
Link9228 said:
I haven't tried this, but it may work. If you have ADB on your computer, try doing an adb push [name of file].apk /system/app/
If you can't do that, try copy/pasting them there using a root explorer on your device itself. Make sure the permissions are set properly (I don't remember what they are off the top of my head).
After doing that, reboot. See if it works.
As for your CM Questions:
1) I'm not sure if you can reduce the time. For customizing the animation, look at something like Rom Toolbox Pro (which also includes a root explorer like I mentioned above).
2) All CM9 TF300T downloads are located here: http://get.cm/?device=tf300t RC1 is listed there so I'm assuming you did something wrong (what's the error you get?)
3) Did you re-root? I'm not sure I understand.
Click to expand...
Click to collapse
I apologize for the vagueness of my original post. I made this thread in anticipation of flashing everything back to stock, trying to copy over those Asus-specific .apk's (which I managed to do), and then re-rooting/re-flashing CM9.
I flashed the .30 firmware to get back to stock and found the Asus widgets & apk's I was looking for in the /system/app directory. After some bootloops and other fun, I was able to flash back to CM9 and when I tried to install the .apk's I immediately get the message "The Application was not installed"
Of the asus items I wanted, Supernote and Polaris Office were my top two picks, and I was able to acquire Supernote through 3-rd party means and install it. So I'm stoked to have Supernote on a CM9-flashed tablet. I wasn't able to find Polaris Office so I hope to at least be able to find a work-around to install that.
In response to #3 - yes I re-rooted my tablet (lost root with the .30 firmware) and previously I was able to browse the root directory of my tablet while it was connected to my computer. Now, I can only browse the SD card. I still haven't figured out a solution to this, but I just transfer files to my memory card and then to my tablet from there. I'm looking into how to do OTA file transfers via bluetooth or wi-fi, if at all possible.
opethfan89 said:
I apologize for the vagueness of my original post. I made this thread in anticipation of flashing everything back to stock, trying to copy over those Asus-specific .apk's (which I managed to do), and then re-rooting/re-flashing CM9.
I flashed the .30 firmware to get back to stock and found the Asus widgets & apk's I was looking for in the /system/app directory. After some bootloops and other fun, I was able to flash back to CM9 and when I tried to install the .apk's I immediately get the message "The Application was not installed"
Of the asus items I wanted, Supernote and Polaris Office were my top two picks, and I was able to acquire Supernote through 3-rd party means and install it. So I'm stoked to have Supernote on a CM9-flashed tablet. I wasn't able to find Polaris Office so I hope to at least be able to find a work-around to install that.
In response to #3 - yes I re-rooted my tablet (lost root with the .30 firmware) and previously I was able to browse the root directory of my tablet while it was connected to my computer. Now, I can only browse the SD card. I still haven't figured out a solution to this, but I just transfer files to my memory card and then to my tablet from there. I'm looking into how to do OTA file transfers via bluetooth or wi-fi, if at all possible.
Click to expand...
Click to collapse
So did you try what I suggested in my post (pushing the files to /system/app on your tablet, rather than trying to install them through File Browser or whatever)?
I'm not sure if they rely on any custom Asus framework stuffs, like with many other OEMs. I personally doubt it because Asus barely changes anything. I think it *should* work, but can't guarantee it.
The easiest way to get the files to /system/app (if you're not very ADB or tech. savvy) is to download a root explorer (like Rom Toolbox Pro has, for example) and copy all the .apks that you want from your sdcard to /system/app.
Link9228 said:
So did you try what I suggested in my post (pushing the files to /system/app on your tablet, rather than trying to install them through File Browser or whatever)?
I'm not sure if they rely on any custom Asus framework stuffs, like with many other OEMs. I personally doubt it because Asus barely changes anything. I think it *should* work, but can't guarantee it.
The easiest way to get the files to /system/app (if you're not very ADB or tech. savvy) is to download a root explorer (like Rom Toolbox Pro has, for example) and copy all the .apks that you want from your sdcard to /system/app.
Click to expand...
Click to collapse
I haven't tried pushing the files via ADB yet. I just wiped out my computer so I need to re-install the drivers to get the tablet recognized and/or the the Android SDK.
In the 3rd point of your point, do you mean my external SD card or the internal memory?
the Transformer Pad has a good portion of internal memory partitioned as an sdcard and mounts it at /sdcard/. I haven't used an external SD card with my tablet yet. Either one should work.
I also found out that Polaris Office has some library files that you probably should grab as well. You can find them at:
/system/lib/libpolarisoffice_tablet.so
/system/lib/libpolarisofficedump.so
/system/lib/libtfapps-polaris.so
/system/lib/libtflua-polaris.so
Click to expand...
Click to collapse
There might be some library files for the other apps. You might want to look around in the /system/lib folder for other libraries as well.
Link9228 said:
the Transformer Pad has a good portion of internal memory partitioned as an sdcard and mounts it at /sdcard/. I haven't used an external SD card with my tablet yet. Either one should work.
I also found out that Polaris Office has some library files that you probably should grab as well. You can find them at:
There might be some library files for the other apps. You might want to look around in the /system/lib folder for other libraries as well.
Click to expand...
Click to collapse
That's awesome, thanks. If I'm able to get this working I will post a guide for others to follow. I ended up just signing up for the swype beta (which I think is stupid since I paid for that app when I bought my tablet, shouldn't have to get a reduced version)
I was able to find a working supernote.apk app on a 3rd-party website and it installed and worked perfectly.
My other issue I'm having is I try to push the files with ADB and it tells me my tablet is read-only? it gives that same message no matter which directory I try to push to. I have the superuser app and have root, but superusers' log shows the 'adb shell' is consistently being denied root permission (if i try to do su or something similar). Any thoughts?
opethfan89 said:
That's awesome, thanks. If I'm able to get this working I will post a guide for others to follow. I ended up just signing up for the swype beta (which I think is stupid since I paid for that app when I bought my tablet, shouldn't have to get a reduced version)
I was able to find a working supernote.apk app on a 3rd-party website and it installed and worked perfectly.
My other issue I'm having is I try to push the files with ADB and it tells me my tablet is read-only? it gives that same message no matter which directory I try to push to. I have the superuser app and have root, but superusers' log shows the 'adb shell' is consistently being denied root permission (if i try to do su or something similar). Any thoughts?
Click to expand...
Click to collapse
You need to remount your system as read-write. Trying doing an adb remount. If that doesn't work, try typing the following into a terminal emulator:
su
busybox mount -o remount,rw /system
Click to expand...
Click to collapse
Try ADB pushing again after that.
if you are able to install the apps by adb push. then maybe a .zip file can be created and use CWM to install all the stock apps.
Link9228 said:
You need to remount your system as read-write. Trying doing an adb remount. If that doesn't work, try typing the following into a terminal emulator:
Try ADB pushing again after that.
Click to expand...
Click to collapse
Well part of the issue is that I can't "su" while in adb shell. It says permission denied. When I type ADB devices normally, it'll list my device. But when I'm in "adb shell" it doesn't show anything. "adb remount" gives me the message "error: device not found".
Any other suggestions?
opethfan89 said:
Well part of the issue is that I can't "su" while in adb shell. It says permission denied. When I type ADB devices normally, it'll list my device. But when I'm in "adb shell" it doesn't show anything. "adb remount" gives me the message "error: device not found".
Any other suggestions?
Click to expand...
Click to collapse
That's weird. I've never seen that before. Are you certain that your adb drivers are installed properly? You can always use a terminal emulator on your device itself to remount the system as read/write and then use adb afterwards.
Link9228 said:
That's weird. I've never seen that before. Are you certain that your adb drivers are installed properly? You can always use a terminal emulator on your device itself to remount the system as read/write and then use adb afterwards.
Click to expand...
Click to collapse
I'm pretty sure my drivers are installed correctly. Everything shows up in device manager, "adb devices" lists my device, fastboot flashes files just fine, so yea.
And yea I have the terminal emulator on my tablet and I've used it before for some stuff (installing Ubuntu) so I will try the steps you guys have mentioned. I'm in the process of trying out some other ROM's right now (Hydro atm, and then probably CleanROM) so once I go back to stock and have access to the appropriate files I'll try these steps.
THIS METHOD IS NO LONGER WORKS as of update version 2.0.5 and higher.
Please visit this thread instead for the current rooting method.
Posting in this thread will get you nowhere, let it RIP.
ANNOUNCEMENT:
If you have a new Nook HD/HD+ and want to root and get the GAPPS running, you should follow the guide at the All-in-One thread instead. That said, I won't copy all the information here to there, so you should continue to read on.
Let me start by saying that I didn't come up with the working root method. The original root instruction came from verygreen in this thread. And I am not a developer, I merely have a few linux background and even less so in the Android. I worked on this on my spare time by myself.
I merely take what was working, but unusable to make it usable. I found something that he is missed. This may actually be working on Nook HD (non-plus) also, but since I don't own one I can't say that it will.
Disclaimer:
If something gone wrong, it's all your fault. I take ZERO responsibility for what happen to your device, your life, your wife/husband, your kids, your unborn child and etc. You get the idea.
Background:
When I found out the root doesn't actually work past a reboot, I start looking what actually cause the Nook to be pissed and factory reset itself. Well, it seem that the /system and anything in there is basically coming from a /dev/block/mmcblk0p8 And if something got change, Nook get pissed and do a FULL FACTORY RESET(I'll explain in a moment). Well, at least I start investigated under that idea.
What I found:
What I found, or at least what I think I found is that, probably just adding file, or increase in the size(maybe there is a threshold for this), will cause it to do a full factory reset. What I also found is that there is a $PATH for /system/sbin but not pointing to anywhere. So I come up with the idea of making another ext4 file system in a file and loop mount it to /system/sbin I guess that work(very well). What I also found is that, there are two kind of factory resets. The one that you perform yourself, which is actually not a full factory reset and the one that Nook get pissed and do the full one.
A factory reset that you perform yourself, whether from the GUI or button combination will basically clean the partition /data while a full blown one will basically restore other partition such as /system
What is included:
basically a zip file, inside that zip file are 6 files.
boot_complete_hook.sh.bak this is basically a modified version of verygreen's
busybox & su are basically from his thread
superuser.apk well I found this one floating around and seem like a good idea to stick it in there (not even sure if it gonna work w/ Nook)
makeroot.bat this is basically what do most of the work. It's base on verygreen original rooting instruction.
sbin_mount This is basically an ext4 file system which have su and another version of busybox all setup nice and tidy for you all. This version of busybox is 1.20.2r2 which I grabbed from here.
Prerequisite:
ADB, it's your responsibility to have adb up and running, meaning not just have it install, but it can see your nook also.
leapinlar wrote a post to help you getting ADB to work here.
Now to get root:
all you have to do is unzip it and run makeroot.bat (obviously you run this in windows command prompt). Yub that's all. The batch file will do the rest, including reboot the nook and wait for it to reboot and stuff. Won't make a coffee for you though.
The manual and hard way:
well, I will only explain this in a summarize way. Basically this start with verygreen rooting method. It basically take advantage of the exploit and run /data/boot_complete_hook.sh which you adb push yourself(with correct permission) with root privilege. What you can run in there is basically up to your creativity. So obviously in this case, you mount the sbin_mount as an ext4 filesystem in the /system/sbin You can make this file yourself if you want to, in linux using dd and mkfs command. Basically using dd to create a file volume to the size you want and mkfs to format it to ext4. Mount it and start uploading stuff you want in there. You will have to correct all the file permission as well. Since all of this will be mounted to /system/sbin you should be aware what you gonna put in there. I guess I could make this thing 100MB, but for this specific purpose 10MB is enough. I my case, just the su and busybox and the symbolic links for the busybox. I'm doing this for the long term. I'm too lazy to point to busybox everytime I wanna do something.
What to do afterward:
Now that you have root, you can Enable Unknown Source to allow you to install app from within the device and install GAPPS. Follow the two guides below if you interested.
Enable Unknown Source: Again, I make an easy little tool for you here.
GAPPS: here.
Did I missed something:
Well, as I said I'm no coder so if I didn't do a clean job, you can refine it. If I didn't document or give proper credit, then I guess I missed that. Sorry about that, again I'm no coder and never done this. And finally:
If this thing work for you, feel free to hit that "THANKS" button. I spent many hours trying to come up with this solution.
FAQ:
Q: My so and so application when attempting to have root access get freeze up, or superuser doesn't work?
A: Well, I'm not sure if this is dued to how the Nook side-loading work or not, but it seem for some reason superuser won't start by itself. So you have to start it manually the first time.
Q: I type in "adb root" and I can't get in as root, it doesn't work?
A: yes it does, it's just not working with adb root. You can get in via "adb shell" once you get in, type in "su" and you can see that you now should have root access.
Thank you so much! This works perfectly. Survives reboot.
here's the Linux version.
Thanks someone0 for getting this started.
Haven't fully tested the linux version, but it loads and starts up, so should work.
extract, and open up terminal and navigate to the dir you extracted to, and type
./makeroot.sh and then enter.
This sounds like a good idea initially.
It is true that the B&N does not just check for /system/xbin/su directly like they did in the past.
This time they check for something else and I just had no time to look into it more deeply to find out what is it they are actually checking for. I plan to figure this out on Friday when I am back home.
Also wanted to tell you that having Linux background is a great thing when tinkering with Android (at a low level, anyway). I don't have much Android background to speak of as well.
This works really well, and thanks to Someone (and mad props too) for getting persistent root working on this.
I may be being very naive, but my suspicion on the reboot is around the manifest file that's present at root.
It seems to be generated by the boot process and it might provide a quick and dirty list of what's permitted on the device to check. With persistent root, lots of investigation becomes a lot less painful. I expect that by end of day we'll have install unsigned running.
Early in my experimenting with the HD+, I noted:
- some versions of the Google Services Framework can be installed via adb
- when I launched the native calendar app after installing gsf, it wanted to sync to a google account, and was able to add the google account
- one version of the Play store installed and launched as far as throwing the 'you must accept the terms of service' before crashing
What BN most likely does is calculating the hash value (or digest, if you prefer) of certain system files that they think shouldn't be tampered with, then during reboot, the values of these files must match, or they will do a factory reset.
The key point is to find out where they do these checks and fool the check.
This sound simple but it depends on how they implement it. If they use binary decisions (like if the hash_value == calculated), then it is easy to get around. If not (e.g. using white box algorithm to hide keys), then it get more complicated.
excellent and very elegant solution. Kudos!
I'm heading out to work, and if you think your theory is right, try poking around with it. Now that your have root, you can try to dd those bootloading partitions out to user area and upload them out to PC and inspect them.
looking at the vold.fstab
Code:
xloader -> /dev/block/mmcblk0p1
bootloader -> /dev/block/mmcblk0p2
recovery -> /dev/block/mmcblk0p3
boot -> /dev/block/mmcblk0p4
rom -> /dev/block/mmcblk0p5
bootdata -> /dev/block/mmcblk0p6
factory -> /dev/block/mmcblk0p7
system -> /dev/block/mmcblk0p8
cache -> /dev/block/mmcblk0p9
userdata -> /dev/block/mmcblk0p10
Be extra careful when touching those partition if you not sure, don't touch them. But making a block copy of them and taking them out should be relatively easy and safe. Obviously you gonna need a Linux box to do this. I setup a VM on one of my PC last night because I need to get a ext4 partition and put all the goodies in there.
krylon360 said:
here's the Linux version.
Thanks someone0 for getting this started.
Haven't fully tested the linux version, but it loads and starts up, so should work.
extract, and open up terminal and navigate to the dir you extracted to, and type
./makeroot.sh and then enter.
Click to expand...
Click to collapse
Just wonder why do use a zip file for the linux version? Wouldn't this kinda messup the permission when compress/uncompress? meaning, makeroot.sh may not have the proper permission when unzip. Please double check.
someone0 said:
Just wonder why do use a zip file for the linux version? Wouldn't this kinda messup the permission when compress/uncompress? meaning, makeroot.sh may not have the proper permission when unzip. Please double check.
Click to expand...
Click to collapse
works just fine.
I chmod a+x'd the script before putting it into the zip.
heh, yeah, it works. Forgot I had my touchpad pluged in and it rebooted it....
whoops.
thanks for posting the location of the /recovery partition. I want to put a copy of htat on ice to prevent BN from undoing any of my work in a future update - I may want some of the fixes they have, but I want to be able to roll them back if needed.
Someone0 are you around can you pm me, Your root works, I installed nook color tools ver .02 in system/app folder and was able to see it in my sideloaded launcher, was able to uncheck/check install non market apps which sets the setting for US to be able to install .apk files from the nook itself, ONLY ISSUE is since I put that file in the system/app folder and the nook didnt like it I got stuck in a bootloop and get to start this process all over again! (nook resetted to ground zero)
maybe we temporary can leave it there get us the permission to install non market apps then remove the file and we will be ok or maybe stuck in another bootloop.
---------- Post added at 09:20 PM ---------- Previous post was at 08:52 PM ----------
GOT IT WORKING NOW:
1. Once rooted, get a file manager with root support and enable read/write permission to /system
2. temporary copy nook tools ver .02 .apk to the system/app folder
3. have a sideloaded launcher and check the app drawer youll see nook tools, run it, first screen uncheck and check the install non market apps box couple of times make sure its checked afterwards
4. have a test .apk to run the BN installer on and see you can now install .apks from the NOOK HD and HD+
5. remove the nook tools.apk file from the system/app folder and quit your file explorer which should reset everything for the system folder back to the way it orginally is!
6. reboot, if you reboot successfully with no boot loop 8 times, your GOLDEN FOR NOW! once again load up a file manager go select an .apk file and see you can now install it! Next step is trying to get amazon market working! then google somehow, but for google you need files in system/app folder permanently!
7. YOU CAN NOW SUCCESSFULLY DOWNLOAD .APK FILES through web, email, any other app and install through the NOOK HD or HD+ BN installer for .apk files. Watch what you install, if it gets put into /system or /system/app folder DREADED BOOT LOOP which resets everything! AMAZON MARKET WORKS!!!! and apps from there install fine to the BUILT IN MEMORY.
** Hopefully amazon market dont install stuff to the system/app folder and if it does hopefully you do not get the dreaded boot loops where you got to start this whole process over again so be forwarned!!! you will loose all data on NOOK HD and HD+ if u get stuck in the bootloops! BACKUP STUFF before messing with root and this kind of thing! DEVELOPMENT!
Aside from moving the actual apk to /system/app/ temporary (since you only do it once), putting a symbolic link there may work also without creating a reset loop. But can't you just side load the apk and run it in other folder?
someone0 said:
Aside from moving the actual apk to /system/app/ temporary (since you only do it once), putting a symbolic link there may work also without creating a reset loop. But can't you just side load the apk and run it in other folder?
Click to expand...
Click to collapse
when you sidelaod it OR install or have it installed to another folder or ran from another folder it cant modify the setting to allow non market apps to install!!
has to be in the /system/app folder THEN RAN from app drawer then you can set the setting uncheck and check box quit program and for now YOU HAVE to remove the .apk from the system/app folder and then you can reboot and the setting sticks! I GOT AMAZON MARKET INSTALLED right now installing apps! NOW WE GOT A KINDLE ladys and gentleman!
Amazon apk installs in internal memory. Apps downloaded from Amazon get installed in internal memory. You can then move them to SD card or leave them in internal memory. System apps are provided in the ROMs by the developers or vendors. ALWAYS back up before making system changes.. Now rooted - use Titanium Backup. System/app should be static throughout ROM lifecycle unless modified by user.
skyhawk21 said:
7. YOU CAN NOW SUCCESSFULLY DOWNLOAD .APK FILES through web, email, any other app and install through the NOOK HD or HD+ BN installer for .apk files. Watch what you install, if it gets put into /system or /system/app folder DREADED BOOT LOOP which resets everything! AMAZON MARKET WORKS!!!! and apps from there install fine to the BUILT IN MEMORY.
** Hopefully amazon market dont install stuff to the system/app folder and if it does hopefully you do not get the dreaded boot loops where you got to start this whole process over again so be forwarned!!! you will loose all data on NOOK HD and HD+ if u get stuck in the bootloops! BACKUP STUFF before messing with root and this kind of thing! DEVELOPMENT!
Click to expand...
Click to collapse
This is why I put the /system back to ro, at least that is what I think I did.
Amazon Store working on ROOTED Nook HD
Proof of Concept:
http://youtu.be/wCyd730L74Y
skyhawk21 said:
Proof of Concept:
http://youtu.be/wCyd730L74Y
Click to expand...
Click to collapse
LOL, your internet is slow. Could have cut the video time by 1/2 if not 2/3 if you switch to faster ISP.
skyhawk21 said:
Someone0 are you around can you pm me, Your root works, I installed nook color tools ver .02 in system/app folder
Click to expand...
Click to collapse
What exactly did you install? I cannot find "nook color tools" in Google Play or on APKTOP. Thanks for your hard work!
NEVERMIND! I found the thread that has the link for the app: http://forum.xda-developers.com/showthread.php?t=868366 Thanks again.
does this root method work on Nook HD+2.0.2?
if not how I can downgrade to 2.0.0?
ANNOUNCEMENT:
If you have a new Nook HD/HD+ and want to root and get the GAPPS running, you should follow the guide at the All-in-One thread instead. That said, I won't copy all the information here to there, so you should continue to read on.
Proof:
https://www.youtube.com/watch?v=MssQ25bnZnk
Okay this one is more interesting than the root I created. I don't think there will be a simple batch file for this one. I barely get this working and I'm going to try to write instruction for the people. I guess let me start off with the same disclaimer.
Disclaimer:
If something gone wrong, it's all your fault. I take ZERO responsibility for what happen to your device, your life, your wife/husband, your kids, your unborn child and etc. You get the idea.
Background:
I basically taking the installation process from the Kindle Fire HD and apply it it here. The original instruction which I "borrow" from is here. For the most part, the process is the same, but we have to be extra careful for writing into /system partition or we are toast.
What I found:
Well, since we didn't have "UNKNOWN SOURCE" option, we have to adapt and fix that first. You can thanks skyhawk21 for coming up with that idea. Since then, there have been other way to enable Unknown Source. LeapinLar have wrote an excellent here. And I have make it even simpler here. Also, I have found that trying to install Google Play store after some other stuff already installed is kinda pain and brought some error. So I would strongly start this fresh. I mean factory reset and apply root. If you don't know how to gain root on the Nook HD+, I wrote an excellent piece for it here.
Hugh big caution
I did all my stuff based off my root method. I also noticed that verygreen updated his root. While there are some similarlity in our methods, THERE ARE SOME DIFFERENCE ALSO. For example his root doesn't have a working superuser or he have busybox installed and symbolicly linked for all sub command. This mean the instruction I have may not work if you used his method to root.
Addendum 1: 11/19/[email protected]:50PM Pacific
I have been told that the first set of instruction is no longer necessary by leapinlar. This mean that if you only want the ability to install app via Google Play, you can do the first set of instruction and be done with it. But this means you won't be able to utilize the rest of Google's services. On the other hand, you can skip the first instruction and purely do 2nd instruction and get most of the stuff working. Well I say most because it doesn't include Google Maps and Chrome.
Addendum 2: 11/19/[email protected] Pacific
I have added Google Map below so you can download separately But Chrome Browser is like 20MB and over the filesize limit of the xda forum. Since most people don't use it, and there are many good alternative browser already, I won't bother. You can also look up both apk online if you want. they both should work on Nook. You don't have to make symbolic link on these two, but you can't have it on /system either. Either try install it via "adb install" command or open it using your favorite file browser. I forgot which method I use, probably the first.
Addendum 3: 11/30/[email protected]:25AM Pacific
I rewrite and hide unnecessary stuff and streamline the guide.
Addendum 4: 12/01/[email protected]:25PM Pacific
Adding gapps-ics-inst.sh.img which should be compatible for both my and verygreen root method.
Addendum 5: 12/02/[email protected] Pacific
Adding troubleshooting tips
Addendum 6: 12/04/[email protected]:45PM Pacific
Update with brand new easy to follow instruction.
Addendum 7: 12/07/[email protected] Pacific
The Google Map will no longer install as part of the script. I think Maps may not function properly if google framework weren't installed correctly first.
So, you will just have to install it manually after the Google Play updated.
EXTREMELY OUTDATED NOT FULLY WORKING Instruction is hidden since it's no longer necessary.
Instruction:
Optional, factory reset it. Seriously I cannot say this will work unless you start from scratch. If you already have rooted earlier, then install something like titanium backup and backup your porn(I mean data).
Gain root access. Follow this guide.
Follow my instruction here to enable "UNKNOWN SOURCE".
Upload 3 files to /data/su/ using "adb push" command
GoogleServicesFramework.apk - mediafire.com/?zaumfwhraxcifqf
Vending.apk - mediafire.com/?31bn3e258jjpj8d
Play.apk - mediafire.com/?wwcqrlfwt8o1gnv
If you have problem downloading this Play.apk I suggest try using this Vending_v3.9.17.apk instead. Be sure not to confuse with the earlier Vending.apk file, or better yet, rename it to something like Play3917.apk
adb install $your_choice_of_file_manager(must support root), I prefer ES File manager
using your file manager and browse to /data/su and install GoogleServicesFramework.apk (I'm not sure if you can just do adb install GoogleServicesFramework.apk from your PC, but since I didn't do it that way and this is a known result, so I recommend doing it this way)
adb shell
su
mount -o remount,rw /system
mv /data/su/Vending.apk /system/app/Vending.apk
chmod 644 /system/app/Vending.apk
chown 0.0 /system/app/Vending.apk
mount -o remount,ro /system (not sure if this is necessary, but I better safe than sorry)
using your file manager and navigate to /system/app and install Vending.apk
mount -o remount,rw /system (only if you did step 11)
rm /system/app/Vending.apk
mount -o remount,ro /system
using your file manager and go to /data/su and install Play.apk or Play3917.apk depending on what you download
now you can delete both GoogleServiceFramework.apk and Play.apk in the /data/su folder.
That's all, your Google Play Store should now be working.
Login and have fun. I manage to install some stuff through that.
Click the "THANKS" button below.
OK, now to get a more complete gapps. The below steps are to be only after you have Google Play Store, meaning all the above steps are done. The instruction below will let your other app sync and use google account. Meaning stuff like RSS reader sync with google reader or Youtube app access your personal account. Well, atleast those are the two I have tried and seem to be working.
OUTDATED Instruction:
Instructions:
Download these two files. gapps-ics-inst.sh.img and gapps-ics-system.zip (if you use verygreen root method use this gapps-ics-inst.sh.img , the one embedded on this post instead. This one should work universally but untested. I re-wrote it to adapt for verygreen root method also. If it works I'll rewrite this part of instruction again to use the new version of the shell script.)
adb push gapps-ics-inst.sh.img /data/su/gapps-ics-inst.sh
adb push gapps-ics-system.zip /data/su/
This step might take some time
adb shell
su
cd /data/su
chmod 755 gapps-ics-inst.sh
./gapps-ics-inst.sh
This step could take some time too, once it return to shell, then go to next step
(optional delete installation file to save space) rm gapps-ics-system.zip
(optional delete installation file to save space) rm gapps-ics-inst.sh
exit
exit
(you should be back to your OS by now, if not keep exiting until you are out of adb)
adb reboot
once your nook is rebooted, the screen may say updating some files, this is normal.
enjoy, everything should work now.
If you didn't hit that "THANKS" button, you better do now. If you did, do it again?
Thanks leapinlar for catching the typo, I have reupload the shell script file now. And thanks to him for hosting the gapps-system.zip
There have been some errors on my initial instruction. Certain things have been point out. I have updated the instruction accordingly. leapinlar have also fixed gapps files and the shell script for that in post #34. So big kudo to him. I haven't have much time to toy with this lately, but since people report that his script work. So here are the new instruction.
If you were using verygreen version of root, try running this first.
Code:
adb shell su -c "/data/su/busybox chown shell.shell /data/su"
FAQ:
Q: I don't see the Google Play Market on the list of apps.
A: If you use the "Skip OOBE" aka Test mode, then (reboot first or go into shell and kill the app launcher and then) you have to hold down the Vol-Up key and tap the word Apps on the top to see them. After that I recommend installing other launcher, then they can see all the apps.
Q: Some people are saying after they install an adblock app, after reboot it get into bootloop and wipe everything.
A: The way most adblock apps work is that they modify the hosts file which usually located at /system/etc/hosts Well, as we have discussed before this is not a good idea to make change directly to /system folder(directory). The only adblock I know of that work is AdAway with a specific setting.
When installed, first you have to go to menu > preferences > target hosts file > /data/data/hosts, it will then ask to create symbolic link, say yes and then you can reboot.
Troubleshooting Tips:
I had a little problem today, unrelated to the GAPPS install mod here. But the problem involved Google Play not working correctly. I kept getting Google Play error pop up. So, I use Titanium Backup ROOT to wipe the data and then uninstall all the apps which names start with Google. I'm not sure if this is enough, it might but I didn't want to take any chance. This maybe unnecessary but I did it anyway; I delete all the files that I created in the /data/su/system that have anything to do with google. Basically anything that was unzip there. Rebooted, then re-apply the same google mod here. And problem solved. I did have to re-login again, but yes I clear up that Google Play error.
Pre-Requisite:
ADB + ROOT + Enable Unknown Source.
1. ADB: leapinlar wrote a post to help you getting ADB to work here.
2. ROOT: I wrote a guide on how to get root the easy way here.
3. Enable Unknown Source: Again, I make an easy little tool for you here.
Brand New and Improve Instructions:
Download these three files. New.zip GoogleMaps.apk and gapps-ics-system.zip
Unzip New.zip (don't unzip gapps-ics-system.zip)
run install.bat
PS: Now I know how hard it's to write a guide in xda. Prop to all those dev that have been there b4 and after, especially the one I have use their works.
That's it, I'm going out to buy one ASAP. Thanks for your hard work!
thanks for you Howto
after that is it possible to use Youtube and Google Maps apps?
Youtube can be install from Play Store but you have to sideload the Google Maps since it's not available for download in Play Store. GMail works, but the authentication through google account on other apps still aren't working. I guess this problem may be beyond my current level of tinkering knowledge.
great job on getting google market somewhat working!!!! We need the manual nooter developer or author to make what we need for the Nook HD AND HD+. Anyhow I belwive you need more framework files to get google authentication working and unfortunately they need to be installed within root folders like the /system folders and sub folders... Also Barness and noble included frameworks for google authentication, probably just not working with google apps installed manually.... gotta figure it out...
---------- Post added at 05:49 PM ---------- Previous post was at 05:47 PM ----------
By the way youtube app works installed older version from my Motorola Droid 3 manually through es file explorer and it works and does HD fine
I have been thinking about that and wonder if we can put those lib files on diff folder and sym link them? I still afraid it might reset the thing.
someone0 said:
Instruction:
[*]Optional, factory reset it. Seriously I cannot say this will work unless you start from scratch. If you already have rooted earlier, then install something like titanium backup and backup your porn(I mean data).
Click to expand...
Click to collapse
I was able to do this with root explorer after rooting with no problem.
Thanks for this (and your rooting zip - both are super!)
issue was fixed, removed obnoxiously long quote
smatticus said:
still have the issue where i can't get the nookcolortools to run properly from /system/app. it just crashes. i googled this and it says that i need to reboot the nook to apply the system/app move BUT that supposedly creates the bootloop. i REALLY don't want to do that so can someone help me out here?
Click to expand...
Click to collapse
You probably shouldn't quote anything that big unless you very need to. As far as getting nook color tool to run, did you set the file to have proper permission, eg: chmod and chown the file? Your other option is factory reset and start from scratch. Sometime getting a clean slate to start with make things easiler to follow.
Thank you for the Google Play Store. It works great for me. I want to install Google Voice. Before I installed your framework apk, I was not able to get the credentials to come up. Now since installing that, it comes up with my Google credentials and tries to authenticate them. But immediately Android System force closes and the sign in screen just sits there. Any ideas on this one? This is the last thing I need to make this my everyday device.
Sent from my Nook HD+ using Tapatalk
someone0 said:
As far as getting nook color tool to run, did you set the file to have proper permission, eg: chmod and chown the file? Your other option is factory reset and start from scratch. Sometime getting a clean slate to start with make things easiler to follow.
Click to expand...
Click to collapse
turns out i wasn't supposed to install the app via adb. my fault for not following instructions. thanks for your hard work
Nice, I think I am getting the Nook HD+.. Hope there is custom ROM soon.. thanks man
leapinlar said:
Thank you for the Google Play Store. It works great for me. I want to install Google Voice. Before I installed your framework apk, I was not able to get the credentials to come up. Now since installing that, it comes up with my Google credentials and tries to authenticate them. But immediately Android System force closes and the sign in screen just sits there. Any ideas on this one? This is the last thing I need to make this my everyday device.
Sent from my Nook HD+ using Tapatalk
Click to expand...
Click to collapse
I'm thinking about that right now but as I suggested, putting the google lib in other place and make symbolic link in the appropriate /system sub. I won't be able to test that theory of mine until I get home later tonight. I will have to research where all the files suppose to go and their permission. Unless you want to do it, you are welcome to.
I agree, getting authentication would be tha last missing link to make this device fully enjoyable as day-to-day usage. And the we can wait for custom ROM from real developers. That is definitely out of my knowledge.
works without full reset
figured i'd put it out there that i DID NOT do a full factory reset (partly to be a guinea pig, partly because i'm lazy) and this method DOES WORK without it. It took 2 tries (it loaded up the first time, then crashed a few minutes later.) the second time it worked like a charm. One note: the chown command gave me an "operation not permitted" notice, but the market IS working, i grabbed a TON of apps and thankfully got updates to the ones i purchased through the nook shop that hadn't seen an update since they first launched (i'm looking at you, machinarium).
Thanks!
Thanks so much for your work on this! I can access the Google Play Store along with the Amazon App Store now and have loaded up my new Nook with my favorite apps. My only disappointment is that I still can't get Amazon Instant Video or Google Play Movies to work...once these work I'll be in heaven!
leapinlar said:
Thank you for the Google Play Store. It works great for me. I want to install Google Voice. Before I installed your framework apk, I was not able to get the credentials to come up. Now since installing that, it comes up with my Google credentials and tries to authenticate them. But immediately Android System force closes and the sign in screen just sits there. Any ideas on this one? This is the last thing I need to make this my everyday device.
Sent from my Nook HD+ using Tapatalk
Click to expand...
Click to collapse
BTW, I got that working now, my theory works. Now only if I have a place to store 60+MB file. Then I can update this guide to include that. I was able to use Youtube app to access my account and so is my RSS reader to sync with google reader.
Access Denied
I'm getting an error when I try to execute ./gapps-inst.sh. It's saying cannot execute - Permission denied. I've rooted and followed the instructions to install Google Play and all worked fine...I'm on this last step and it won't work! Advice is much appreciated!! I also keep having permission denied issues with the adb push command...I can paste the files manually via ES File Explorer and rename to remove the .bin but I still can't install from adb shell.
I've also tried chmod 777 on the gapps-inst.sh prior to doing ./gapps-inst.sh but that produces a giant string of errors.
I'm at a loss!
someone0:
I just rehosted your files on my MediaFire account.
Removed links. New links on OP.
Alright, so I have no idea what Nook HD/HD+ thread to put this is in... so here i go.
1. Will these steps get the play store on the Nook HD as well?
2. Will the apps show up in the Nook app section, or do we still need a launcher. I have sideloaded all my apps, but have to use a launcher to get at them.
Thanks!
someone0:
There is are a couple of typos in your gapps-inst.sh file -
Code:
ln -s /data/su/system/usr/srec/en-US/google_hotword_clg /system/usr/en-US/google_hotword_clg
ln -s /data/su/system/usr/srec/en-US/google_hotword_logistic /system/usr/en-US/google_hotword_logistic
are missing the /srec in the second /system link.
Also it seems the real /system has these files so the symlinks fail.
Code:
ln -s /data/su/system/etc/permissions/com.google.widevine.software.drm.xml /system/etc/permissions/com.google.widevine.software.drm.xml
ln -s /data/su/system/framework/com.google.widevine.software.drm.jar /system/framework/com.google.widevine.software.drm.jar
ln -s /data/su/system/usr/srec/en-US/acoustic_model /system/usr/srec/en-US/acoustic_model