Related
HI Guys,
Maybe somewhat can help me out here, in my attempt to update my Acer A500, I may have in a kind of way bricked my phone. I attempted to replace wpa_supplicant file as per some of the instructions, needless to say the update failed and me in my pure genius figure I would simply factory reset and reboot. Which I ended up doing, the problem now is that the WIFI does not turn on and my tab has been unrooted, I no longer have any file explorer app on the phone and I can't download anything. Does anybody know how I can gain access to the root files so that I may revert back the old file, or somehow install an apk file from the mini sdcard or even get access to the internet via bluetooth or USB. Anything would be helpful.
FYI - I am trying to gain access to my root files using Android SDK, but I've always had problems getting any of my pc to find any of the android stuff when plugged in.
Ph0tin0 said:
HI Guys,
Maybe somewhat can help me out here, in my attempt to update my Acer A500, I may have in a kind of way bricked my phone. I attempted to replace wpa_supplicant file as per some of the instructions, needless to say the update failed and me in my pure genius figure I would simply factory reset and reboot. Which I ended up doing, the problem now is that the WIFI does not turn on and my tab has been unrooted, I no longer have any file explorer app on the phone and I can't download anything. Does anybody know how I can gain access to the root files so that I may revert back the old file, or somehow install an apk file from the mini sdcard or even get access to the internet via bluetooth or USB. Anything would be helpful.
FYI - I am trying to gain access to my root files using Android SDK, but I've always had problems getting any of my pc to find any of the android stuff when plugged in.
Click to expand...
Click to collapse
I was in this court just yesterday, swearing up and down for some reason.
You'll need the root explorer apk, gingerbreak apk and the original wpa_supplicant file posted all over XDA.
Download and install Android SDK. It will also make you download the Java SDK too before you install the Android one. Start installing the Android SDK. It will seem like it's going to take forever, but you really only need what's in the folders 2 minutes in.
Go into the program files folder where the SDK stuff is and rip the 3 ADB files out and place them in their own folder. Mine were in: c:\program files\android\android-sdk\platform-tools\
I took the 3 files out and placed them in c:\and\
Place the apks in the c:\and\ folder
Make sure the driver files are installed from the Acer website.
Make sure USB bugging and apps from outside sources are enabled in settings on the tab.
Plug the tab into the PC via USB.
Open up the command prompt and go to the c:\and\ folder
then type
adb install c:\and\rootexplorer.apk
ENTER
then
adb install c:\and\gingerbreak-v1.20.apk
ENTER
The apps should be now installed on the tab.
Then just transfer the wpa_supplicant file over and you're right where you need to be.
Make sure you change the permissions on the wpa_supplicant file like you did the first time (enable everything read/write/etc etc) by holding on the wpa_supplicant file that you paste.
rorytmeadows said:
Open up the command prompt and go to the c:\and\ folder
then type
adb install c:\and\rootexplorer.apk
ENTER
then
adb install c:\and\gingerbreak-v1.20.apk
ENTER
The apps should be now installed on the tab.
Then just transfer the wpa_supplicant file over and you're right where you need to be.
Make sure you change the permissions on the wpa_supplicant file like you did the first time (enable everything read/write/etc etc) by holding on the wpa_supplicant file that you paste.
Click to expand...
Click to collapse
You are my new hero, all this time I've been trying to get Android ADK to recognize my tablet, but to no success. All I had to do was run ADB, which Ironically I had done, but only to see if it recognizes my unit. I was not aware I can install apps with it.
I'm not worthy... I'm not worthy
A million thank you's, now to try and get 3.1 installed and hopefully Googel/android was smart enough to put in a stock file explorer.
Not working wifi hardware
Somewhat similar to what happened to this guy. But to be specific, I am using an acer a500 originally on a rooted ics 4.0.3, i remember using lucky patcher and using the custom patch on adobe flash player then i saw an update regarding busybox and superSU...i was able to install the busybox updater but not the superSU since i remembered i already had superuser. I opened superuser and then it updated...from then on...I lost my wifi...at start it was still there but it can't connect. also, i lost my root because i no longer am able to use titanium backup. double checking it, i downloaded a root checker and it displayed not properly rooted. seeing this, i thought it's been a long time since i've updated my rom so i might as well upgrade everything...my bootloader, kernel, rom. So i first degraded it by flashing to the full package stock HC 3.1 ROM (it had an old HC 3.1 bootloader). Then i noticed i can no longer turn on my wifi and use my old apps...I flashed it back to a NON-rooted stock ics 4.0.3 thinking it might fix it...but it did not. HELP please...
If this is the wrong thread I'm sorry and mods please move it.
My nook is currently rooted...
I have tried all the 3rd party e-readers different launchers.
I'm really over the idea of being rooted with the exception of "Current book cover screensaver + custom shutdown image" hack and possibly resizing my partitions.
Is it possible to replace the Uramdisk with one that had adb enabled and then just manually push over the modded files?
or am i going to need to install busybox, su, and superuser.apk?
I would like to keep it as close to original firmware as possible...
Can anyone shed some light on this?
Ok so i'm guessing busybox is required to be able to run the Current Book Cover Screensaver.
1st i turned on adb wireless.. installed the files per the instructions over ADB
rebooted and I was stuck in a boot loop
2nd restored to a fresh firmware.
Installed adb wireless, superuser, su, and busybox.
Then installed the files per the instructions over ADB
rebooted and everything works great.
Now i just wonder if i can uninstall Superuser or busybox...
persichini said:
Ok so i'm guessing busybox is required to be able to run the Current Book Cover Screensaver.
1st i turned on adb wireless.. installed the files per the instructions over ADB
rebooted and I was stuck in a boot loop
2nd restored to a fresh firmware.
Installed adb wireless, superuser, su, and busybox.
Then installed the files per the instructions over ADB
rebooted and everything works great.
Now i just wonder if i can uninstall Superuser or busybox...
Click to expand...
Click to collapse
hi,
while i'm not totally sure, i suppose you can definitely uninstall both superuser and busybox.
In any case, the modified ramdisk with ADB enabled (either WiFi or USB) is enough to allow you to push/pull files to Nook, and to open a shell (as root).
Busybox is just convenient if you plan to use shell sessions since it includes commands like cp to copy files, and others, but you can live without it (using ADB push to copy files, or using command dd, for instance).
Superuser, if you refer to android application (APK) it's just used by all other applications requiring root privileges (like RootExplorer, for instance), but if you don't plan to use them, then it's not needed.
In any case, you have practically my same configuration (as close as possible as stock firmware): after all, i use Nook just to read books, so don't need custom launcher and google apps! I would just mention XorZone modification that is really useful for me, since it's can act as a sort of launcher, and can deal with useful features like button remapping. The only other application i have installed is this PDF reader, since the stock one is really poor, while this one has a better zoom management, and also has specific features for e-ink devices and expecially for the Nook (like partial refresh).
Of course, to install the applications, i just use ADB.
traycold said:
In any case, you have practically my same configuration (as close as possible as stock firmware): after all, i use Nook just to read books, so don't need custom launcher and google apps!
Of course, to install the applications, i just use ADB.
Click to expand...
Click to collapse
Ok so something must have gone wrong when I installed your screen saver mod if i was stuck in a boot loop. Because I assuming you have it installed on yours with out superuser, and busybox... i just i can just install them now and then it should still work.
I also just use the nook to read EPUB book, i have a very nice android tablet that i use for anything and everything else. I would much rather have a high battery life on the nook then bells and whistles i don't ever use.
If you're running linux or have access to a linux box, you could just grab noogie and it should show all partitions. With this you could make the changes without ever having to touch the uRamdisk or ADB or needlessly installing anything to actually root the device.
As it is if you were to try this your way you'd have to first root it using like Minimal Nooter or TouchNooter then remove everything you don't want afterwards (su/superuser/busybox/gapps/etc).
Personally what I did was I installed touchnooter and because I like my devices to appear stock I left all the buttons unmodified while leaving a very faint button savior icon on one side that'll allow me access to android launcher the app drawer etc. This way I can use it like a proper android device without having it appear as anything more than a basic reader.
GabrialDestruir said:
If you're running linux or have access to a linux box, you could just grab noogie and it should show all partitions. With this you could make the changes without ever having to touch the uRamdisk or ADB or needlessly installing anything to actually root the device.
As it is if you were to try this your way you'd have to first root it using like Minimal Nooter or TouchNooter then remove everything you don't want afterwards (su/superuser/busybox/gapps/etc).
Personally what I did was I installed touchnooter and because I like my devices to appear stock I left all the buttons unmodified while leaving a very faint button savior icon on one side that'll allow me access to android launcher the app drawer etc. This way I can use it like a proper android device without having it appear as anything more than a basic reader.
Click to expand...
Click to collapse
Hmm interesting...
What i did was i restored to stock... so my nook was completely unrooted...
Switched the uRamdisk using noogie then ADB the following files over and set the permission...
android.policy.jar [needed only for "current book cover screensaver"];
services.jar [needed only for "current book cover screensaver"];
Settings.apk [needed only for "current book cover screensaver"];
framework.jar [needed only for "custom shutdown image"];
What your saying is just use noogie and linux to replace the files and set the permissions.
I plan on Dual Booting my G-Tablet with linux so i can resize the partitions on the nook, I'm going to try your suggestion and see how it goes..
A) Before using the Kindle Fire Utility to install TWRP, I DO need to uninstall BurritoRoot on my Kindle, correct?
B) Since I'm going to lose all my apps anyway, should I delete the ones that are not necessary for the process?
C and D) I do actually use my Fire to read PDF books, will Adobe Reader still work as it should? Where do I put the files when I transfer them from my computer to my Kindle?
I've got everything downloaded and ready to roll. I'm going to bed and plan on flashing in the morning, just need these questions answered before I do. Thanks.
A) I rooted before I even knew what TWRP was, so no.
B) You could if you want to.
C) I don't know, but I could test it.
D) The update.zip and gapps? You could put them on the root of your "sdcard," or you could create a folder for them.
UPDATE: I tested Adobe Reader and it seems to work fine.
Sent from my Kindle Fire using XDA Premium.
Another Question or two
il Stalk3r li said:
A) I rooted before I even knew what TWRP was, so no.
B) You could if you want to.
C) I don't know, but I could test it.
D) The update.zip and gapps? You could put them on the root of your "sdcard," or you could create a folder for them.
UPDATE: I tested Adobe Reader and it seems to work fine.
Sent from my Kindle Fire using XDA Premium.
Click to expand...
Click to collapse
I rooted with BurritoRoot, and yes, I found out that I do need to uninstall it before I use the Kindle Utility to install TWRP(v. 0.9).
Is there anything else I need to do before I do this?
Not the gapps, the PDFs I want to read in Adobe reader, where would I place those is transferring from my computer?
Sorry for all the questions I just want to be thorough and make sure I have every single thing right.
Thanks
Did you install the drivers that came with the Kindle Fire Utility? Do you have 0x18D1 at the end of the adb_usb.ini file? Those steps helped me most when my first install of TWRP2 wasn't done correctly. An extra step I took was downloading techerrata.com/file/twrp2/twrp-blaze-2.0.0RC0.img and adding it to the recovery folder of the KFU. Then I renamed it to twrp.img and the other to twrp.img.bak. I don't know if that helped, but after all of that was covered my second install was successful.
You could put your PDFs in a folder on your kindle. It doesn't matter really, as long as it is some place you can find them. Hopefully this helps you and if you have anymore questions I'll be glad to answer them if I can.
- il Stalk3r li
You would place your PDF files on the SD card (the file system you can access from your computer when you connect via USB) either in the root or a folder such as books.
You would then install PDF reader or Kindle reader from the market in order to read the files.
Finally, install a good file manager (or if you are installing an alternate rom such as CM7 it comes with one) such as ES file explorer (free) or Root Explorer (paid). Navigate to your files and click on the one you want to open. A popup may ask you to choose your reader if you have both the above installed. Adobe will keep a list of recently opened files so you will not have to go through the file manager again for any previously accessed docs.
il Stalk3r li said:
Did you install the drivers that came with the Kindle Fire Utility? Do you have 0x18D1 at the end of the adb_usb.ini file? Those steps helped me most when my first install of TWRP2 wasn't done correctly. An extra step I took was downloading techerrata.com/file/twrp2/twrp-blaze-2.0.0RC0.img and adding it to the recovery folder of the KFU. Then I renamed it to twrp.img and the other to twrp.img.bak. I don't know if that helped, but after all of that was covered my second install was successful.
You could put your PDFs in a folder on your kindle. It doesn't matter really, as long as it is some place you can find them. Hopefully this helps you and if you have anymore questions I'll be glad to answer them if I can.
- il Stalk3r li
Click to expand...
Click to collapse
Do I need to install the Kindle Fire Utility drivers while my Kindle is hooked up, or does it matter?
I don't think it matters.
Sent from my Kindle Fire using XDA Premium.
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?