Related
********Please Mods remove thread if possible!! New Tatuyama fix (ext4) has been incorporated into SuperRooter by DesignGears ********
LINK: http://forum.xda-developers.com/showthread.php?t=751934
DISCLAIMER
DO IT ON YOUR OWN RISK.
ME OR ANYONE ELSE ON THIS FORUM IS NOT RESPONSIBLE FOR BRICKED/DEAD DEVICES AND/OR DEAD SD CARDS.
YOU SHOULD UNDERSTAND EVERY STEP IN THIS HOW-TO BEFORE ATTEMPTING TO FOLLOW.
**********EDIT LOG*******************
8/10/2010: Added Startup Issue Reversion
8/11/2010: Added Alternate Manual Method that might work better than AUTO
8/11/2010: Added Possible Method of Backing EXT2 Partition
Here everyone... I have been trying lag fixes all over the place and I always seem to have issues partitioning the external sd for the apps... so after so many attempts, this was BY FAR the best lag fix out there.... It doesn't rely on the externalsd for functionality.
Easy and nothing special needed.
The steps below are pretty good, but I did things a little different.
Copied the update.zip to my external sdcard.
Then used Root Explorer to copy the update.zip to my internal sd card.
(******Here is the updated filed: http://forum.xda-developers.com/attachment.php?attachmentid=376882&d=1281390347******)
Then I used ROM Manager (Reboot into Recovery) to boot into the Linux Loader
Then I said update using update.zip (not install update.zip)
Then Reboot
For some reason it didn't install busybox 1.17.1 so install it manually
(located: http://forum.xda-developers.com/showpost.php?p=7574130&postcount=229)
Make sure after you install busybox.apk that you go into busybox and check to MAKE SURE you are running 1.17.1 ONLY. You might have an older version or newer version but it must be 1.17.1; if different just click install.
After that follow the MCR Scripts below. (Took about 6 minutes to do everything)
*** If MCR Scripts DOES NOT show up, its probably because you don't have the non market install hack on your phone. In the update.zip you can find the apk and install via ADB, but I didn't do it this way. ******
(Original Thread! Alternate method on OP in link below! Some people say it worked better for them.)
http://forum.xda-developers.com/showpost.php?p=7587405&postcount=417
@Tayutama
I ran the Tayutama update.zip using the up+power+menu button method, it installed in seconds and I restarted the phone. I ran the benchmark but still got 8xx scores. I'm an Noob, so needed more thorough instructions. These are now given below. NOTE: THIS METHOD IS MUCH MORE NOOB FRIENDLY AND DOES NOT REQUIRE A PC OR USB DEBUGGING MODE.
EDIT I had realised I needed to launch the newly installed MCR app after restart and choose a lagfix file to run. I ran the file and 'all complete'. This worked a treat. Ran Quadrant and now have a top score of 2114 running on JM2. System is much snappier. This mod of RyanZA fix by Tayutama is the most noob friendly also. Full instructions as follows:
EDIT Requirements: Make sure your phone has 'superuser' app installed by checking your app list. If it isn't installed, you can use a newer beta version of Tayutama's update.zip
available at; http://forum.xda-developers.com/atta...4&d=1281437129
Full instructions:
1. The update.zip installs all the files needed. It is attached here; http://forum.xda-developers.com/atta...2&d=1281390347
2. Place it on your internal sdcard
3. Turn off your phone.
4. Hold down Up+powerbutton+Menubutton for a couple of seconds until u see the galaxy logo .
5. Use the up and down buttons to get to update.zip.
6. Press menu button on update.zip to select it
7. It installs root, correct busybox (1.17.1) as well as all the scripts needed for the fix and the 'MCR Scripts' app to run the scripts. (NOTE: This version does not install superuser.app which is needed, although the beta update.zip does, so read 'requirements' above if needed)
8. After install, the phone restarts.
9. Go to the newly installed 'MCR Scripts' application from the app list, open it and choose from 3 scripts. For example, Lagfix10024 is the 1gb ex2 version.
10. The script should run and take a few minutes.
11. You should see an 'all complete' prompt, and this means you can close the application.
12. Run quadrant to test if the fix was applied.
Originally Posted by Tayutama
Don't know if you mind me posting this here RyanZA, but i made a update.zip out of your script. NOTE THIS ONLY WORKS ON 2.1
What this update.zip file does is that it copies a few files to your internal sdcard and installs ASE which can be used to run .sh files without the need to use a terminal.
There are 3 scripts included:
LagFix1024.sh - Makes a 1GB file on /data
LagFix512.sh - Makes a 512MB file on /data
RemoveFix.sh - Removes the lagfix
This also includes BusyBox 1.17.1 so no need to install that first.
Testet this on JM1
Click to expand...
Click to collapse
********Alternate Method that might even work better!! ****************
All the files are located in the update.zip file that you need to download.
1. Connect phone to PC, make sure adb can see it:
adb devices
2. adb kill-server
3. adb push createlagfix.txt /sdcard/createlagfix.sh
4. adb push playlogos1 /sdcard/playlogos1
5. adb push userinit.sh /sdcard/userinit.sh
6. adb shell su -c "/system/bin/sh /sdcard/createlagfix.sh"
7. adb kill-server
8. adb reboot
************ Reverting back if there are boot up and black screen issues ****************
If you have black screen and doesn't boot into the desktop, this is the fix to return back to normal state:
To fix that problem:
1. Boot into Recovery Mode (Vol Up + Vol Down + Power) Let go of Power after you see AT&T.
2. Delete User Cache
3. Delete All User Data
4. Then see if your phone boots up
5. If your phone does boot up then navigate to Settings -> Security -> Factory Reset
6. After factory reset your phone should be useable again.
DO NOT INSTALL THIS UPDATE IF YOU DO NOT KNOW WHAT YOU ARE DOING.
**********Possible method of Backing up Your EXT2 Partition **********
BTW I would also perform a NANDROID Backup as well which can be done by using ROM Manager to boot into the Android Loader....
Nandroid does NOT back up the apps off your SD card.
AppsToSD (I'm speaking re MoDaCo's rom here) uses the ext2 partition on your SD card for the /data/app and /data/app-private folders, where your actual downloaded application files are kept. Nandroid does NOT back this up, and simply mounting your SD card and copying the files off also does not back this up.
The only way to back up these critical folders is to directly copy them to somewhere else. You can use command line or Droid Explorer.
If you want to use command line, do this from an ADB shell or terminal:
mkdir /sdcard/backup/
mkdir /sdcard/backup/app
mkdir /sdcard/backup/app-private
cp -r /data/app/* /sdcard/backup/app/
cp -r /data/app-private/* /sdcard/backup/app-private/
This will create two folders on your SD card: app and app-private, both in a folder called Backup. It will then copy the entire contents of your /data/app and /data/app-private folders to your SD card.
After you do this, back up the entire contents of your SD card as normal.
To restore the files after replacing/partitioning your SD card, head to this thread:
http://forum.xda-developers.com/showthread.php?t=585349
Click to expand...
Click to collapse
Quadrant score was 917 and was on stock roms.....
Now Quad score is 2193 and still on stock roms.....
Tested on 2.1 Update 1 Captivate
Baseband: I897UCJF6
slider2828 said:
Quadrant score was 917 and was on stock roms.....
Now Quad score is 2193 and still on stock roms.....
Tested on 2.1 Update 1 Captivate
Baseband: I897UCJF6
Click to expand...
Click to collapse
Does it show strong real world improvements?
good job explaining nothing. troll harder
So....
This is a ""one step"" that isn't one step... ?.. ?
Oh, and for anyone wondering....
This appears to be the ext2 fix.
This IS the same fix from the otger thread, just packaged in update.zip format. Id be a bit more cautious using this one as it hasnt had as much testing among the I9000 crowd much less Captivate users.
Zilch25 said:
This IS the same fix from the otger thread, just packaged in update.zip format. Id be a bit more cautious using this one as it hasnt had as much testing among the I9000 crowd much less Captivate users.
Click to expand...
Click to collapse
Thanks for confirming this. I am seeing strong real world improvements, too. Dolphin Browser HD is very snappy and everything seems a lot faster (I am on stock captivate, btw, couldn't get this to work on I9000 for some reason).
Only thing is you should back up frequently because it can be corrupted a lot more easily since it is on ext2.
hm... i applied the update in clockwork mod recovery, i have super user and the correct busybox version installed and rebooted the system. i went to the app list and could not find the "MCR SCRIPT" you mentioned i should be seeing... am i doing something wrong?
THat is weird I saw mine in the apps list.... its just called MCR with a green dog bowl and light bulb....
Woops sorry for the truncation in the quote.... I have attached the update.zip file that you need to download.... The update.zip file you used is probably a ROM Manager Update.zip, so just rename it and copy the new update.zip file to the internal sd....
Sorry.....
solufein said:
good job explaining nothing. troll harder
Click to expand...
Click to collapse
What the hell does that mean.... You saying it doesn't work? Why not try it and it is an EXT2 fix.
max_warheads said:
So....
This is a ""one step"" that isn't one step... ?.. ?
Oh, and for anyone wondering....
This appears to be the ext2 fix.
Click to expand...
Click to collapse
This isn't one step because I don't have the USB cable with me. I just had a USB adapter for the microsd and I can't boot into the linux loader correctly without the cable, so I used ROM Manager. It would have been easier if I did.
Zilch25 said:
This IS the same fix from the otger thread, just packaged in update.zip format. Id be a bit more cautious using this one as it hasnt had as much testing among the I9000 crowd much less Captivate users.
Click to expand...
Click to collapse
Yup it is but on the internal card. Are you sure its the same? Look at the OG thread, a LOT of people have tried it with great success....
darth_vato said:
Thanks for confirming this. I am seeing strong real world improvements, too. Dolphin Browser HD is very snappy and everything seems a lot faster (I am on stock captivate, btw, couldn't get this to work on I9000 for some reason).
Only thing is you should back up frequently because it can be corrupted a lot more easily since it is on ext2.
Click to expand...
Click to collapse
How do you back it up?
i updated the zip and rebooted used busy box and i dont have that MCR app
Bionicboto said:
i updated the zip and rebooted used busy box and i dont have that MCR app
Click to expand...
Click to collapse
Same instructions before, did you download the update.zip? I just added that instruction. Can you try again after that?
slider2828 said:
THat is weird I saw mine in the apps list.... its just called MCR with a green dog bowl and light bulb....
Woops sorry for the truncation in the quote.... I have attached the update.zip file that you need to download.... The update.zip file you used is probably a ROM Manager Update.zip, so just rename it and copy the new update.zip file to the internal sd....
Sorry.....
Click to expand...
Click to collapse
when you say put the update.zip into the phone... do i put it in the internal sd card root? or do i put it in the ROM MANAGER folder? when i choose apply update, it only gives me one option to update from: /sdcard/update.zip. i choose that it installs properly and i reboot. i still don't the app, lol.
i also have removed the the recovery-update.zip or renamed it and tried to reboot into recovery mode via ROM MANAGER but it doesn't let me do it because it can't find the zip. then i tried to put the update into the the ROM MANAGER folder and it says it can't the find update.
its still the same cant find the app i reboot to recovery apply sd card update.zip go to yes and it says installed reboot and its not there
arsinic said:
when you say put the update.zip into the phone... do i put it in the internal sd card root? or do i put it in the ROM MANAGER folder? when i choose apply update, it only gives me one option to update from: /sdcard/update.zip. i choose that it installs properly and i reboot. i still don't the app, lol.
i also have removed the the recovery-update.zip or renamed it and tried to reboot into recovery mode via ROM MANAGER but it doesn't let me do it because it can't find the zip. then i tried to put the update into the the ROM MANAGER folder and it says it can't the find update.
Click to expand...
Click to collapse
Sorry for the bad reply.
Rename the update.zip that is already on the internal sd cards root because that is ROM Managers using ROOT Explorer
Then copy the update.zip that you downloaded to the external SD card.
Then copy update.zip from the external sd card to the internal sd cards root.
Then use ROM Manager to reboot into the linux loader.
Hope that helps?
-Ken
slider2828 said:
Sorry for the bad reply.
The update.zip that you use download, copy it the the internal sd card's root... (Basically where ROM Manager update.zip was. Like you did Rename the update.zip that is already there, because that is ROM Managers).
Hope that helps?
Click to expand...
Click to collapse
hm... the only update.zip i have is in the Recovery Mod folder named: recovery-update.zip. the only update.zip i have in the sdcard root is the update.zip i downloaded from the your url and have been applying that as the update. i seem to be having the same problem as Bionicboto.
should i have the rom manager's update.zip in there also or it doesn't matter? and i also have no external sd card. is that something i need in order to get this update working properly?
Did you ever perform a backup with the ROM Manager? That usually creates a update.zip.....
Basically when I log into root explorer and click on SDCARD.... you should see the update.zip in that folder along with Android folder, busybox folder, clockworkmod folder, DCIM folder, downloads folder, etc etc....
slider2828 said:
Did you ever perform a backup with the ROM Manager? That usually creates a update.zip.....
Click to expand...
Click to collapse
i preformed a backup right before i did all this. i did notice the update.zip in there. i took it out and put in the update.zip you uploaded. do i need both in there?
thanks for the quick replies btw.
Nope... Try this... with ROM Manager,
Choose Flash ClockWorkMod Recovery and that will recreate the boot files for ROM Manager.... and also backup your current ROM again.
Then try the steps again.
OMG Dude I noticed you in oakland, I am in hayward/san leandro.... We can try after I get off work which is in 30 minutes. and then take 30 minutes to get back to SL....
You wanna meet at the starbux on marina?
Flashed and installed perfectly. Bumped my quadrant up to 2117. Good post, thanks.
Hi,
like I said I cannot get Google apps on my nook color. I've tried everything. I originally had cm7.0.3 but that wouldn't work so I tried 7.1.0 rc and it still won't work. I tried booting in recovery mode numerous times, I've tried using ROM manger to install from SD but again doesn't work. Someone please help!
chad11 said:
Hi,
like I said I cannot get Google apps on my nook color. I've tried everything. I originally had cm7.0.3 but that wouldn't work so I tried 7.1.0 rc and it still won't work. I tried booting in recovery mode numerous times, I've tried using ROM manger to install from SD but again doesn't work. Someone please help!
Click to expand...
Click to collapse
settings > accounts and sync > add account > log in
that should help. That's how i fixed it when i had the same problem.
thanks but in the first post I forgot to mention I also can't add my Google account. I get as far as it is checking the server connection bu then it say it can't connect
chad11 said:
thanks but in the first post I forgot to mention I also can't add my Google account. I get as far as it is checking the server connection bu then it say it can't connect
Click to expand...
Click to collapse
can you connect to the internet at all?
re-do everything. Do "adb pull /data/app/ app/" and "adb pull /data/data/ data/" and go into the app folder. Delete anything that has to do with Google (market, googleservices, etc.) Download cm7 and gapps from the links at the end of this post Put em on your sd card. Boot into recovery. Mounts & Storage, wipe data, system, and cache. Now flash cm7 first, then gapps. Now flash anything else you use (dal's OC kernel, etc) and reboot. Re-setup your Nookie. Now push puth the app/ and data/ folders to your sd card. Download File Expert and Root Explorer. Using file expert, navigate to the sd card. Select the app/ folder you pushed, and press and hold. Now hit install all apk packages. Keep installing. If you get an error, Setting>Applications>Allow Non-Market installs. Now use root explorer to merge the data/ folder on your sd with the /data/data/ folder on the emmc. Done. Hope that wasn't to complicated.
ikingblack said:
re-do everything. Do 1) "adb pull /data/app/ app/" and "adb pull /data/data/ data/" and go into the app folder. Delete anything that has to do with Google (market, googleservices, etc.) 2) Download cm7 and gapps from the links at the end of this post Put em on your sd card. Boot into recovery. Mounts & Storage, wipe data, system, and cache. Now flash cm7 first, then gapps. Now flash anything else you use (dal's OC kernel, etc) and reboot. Re-setup your Nookie. Now push puth the app/ and data/ folders to your sd card. Download File Expert and Root Explorer. Using file expert, navigate to the sd card. Select the app/ folder you pushed, and press and hold. Now hit install all apk packages. Keep installing. If you get an error, Setting>Applications>Allow Non-Market installs. Now use root explorer to merge the data/ folder on your sd with the /data/data/ folder on the emmc. Done. Hope that wasn't to complicated.
Click to expand...
Click to collapse
You are aware that when you do #3 you will take care of #1. wiping the /data wipes everything in it.
And if you want go about it that way you could even just do a
Code:
c:\<target folder> adb install [package name]
and it will install the app for you. so you can pull it, wipe it then reinstall everything.
adb pull backs it up. and whoops, here are links:
CM7: http://download.cyanogenmod.com/get/cm_encore_full-123.zip
Gapps: http://goo-inside.me/gapps/gapps-gb-20110613-signed.zip
ikingblack said:
adb pull backs it up. and whoops, here are links:
Click to expand...
Click to collapse
Then why are you having the [OP] reflash the gapps if they are just going to manually install them?
the problem the [OP] is having is the device [Nook Color] will not connect to google's servers. It has nothing to do with the g/apps not showing up on the device.
No, we are backing up all the apps, because one time I had this problem and a fresh slate caused it. And as for the adb install commands, It would take forever, because you would have to type in the APK's name. For my method, all you have todo is hit Install. Just keep stabbing the right lower corner of the screen.
ikingblack said:
No, we are backing up all the apps, because one time I had this problem and a fresh slate caused it. And as for the adb install commands, It would take forever, because you would have to type in the APK's name. For my method, all you have todo is hit Install. Just keep stabbing the right lower corner of the screen.
Click to expand...
Click to collapse
So because you reinstalled the applications it's magically reconnected to Google's servers?
Nope. There was something corrupt in my /data/ folder. Wiping and re-installing all apps was what I had to do.
OK your first post was a little complicated for me. this is the first time I've rooted somethiing. could you please put in simpler terms. by the way I don't have any apps on my device or any other data i care about so I don't need to back anything up if that would make it easier
also yes (neidlinger) I did have a internet connection, and I also can't install a new build through recovery
Alright, if you don't have anything to back up, do this:
Download CM7, gapps, and other stuff you want (overclock kernel) and put it on the sd card.
Now boot into recovery, CWM.
Go into Mounts + Storage. Wipe system, data, and cache. Go into advanced (on the first menu) and wipe dalvik cache.
Hit "install zip from sd card" and then "choose zip from sd card".
Now select CM7. Wait for it to flash
Choose zip again, but choose gapps, then flash an OC kernel if you wanted. Note the NC doesn't have back and menu buttons, so download a Hard Key editor to make Volume+ to menu and volume- back.
Now reboot device. Now set it up. After typing in your google account, it will *attempt* to connect to Google Servers. It will fail. It will then show a button to connect to wifi. Hit it and connect to the wifi. Then continue set up steps. Enjoy CM7 with a smaller guide. Much smaller.
ikingblack said:
Alright, if you don't have anything to back up, do this:
Download CM7, gapps, and other stuff you want (overclock kernel) and put it on the sd card.
Now boot into recovery, CWM.
Go into Mounts + Storage. Wipe system, data, and cache. Go into advanced (on the first menu) and wipe dalvik cache.
Hit "install zip from sd card" and then "choose zip from sd card".
Now select CM7. Wait for it to flash
Choose zip again, but choose gapps, then flash an OC kernel if you wanted. Note the NC doesn't have back and menu buttons, so download a Hard Key editor to make Volume+ to menu and volume- back.
Now reboot device. Now set it up. After typing in your google account, it will *attempt* to connect to Google Servers. It will fail. It will then show a button to connect to wifi. Hit it and connect to the wifi. Then continue set up steps. Enjoy CM7 with a smaller guide. Much smaller.
Click to expand...
Click to collapse
Please Take TIME to read the entire post before firing off solutions that will not help the [OP]
chad11 said:
also yes (neidlinger) I did have a internet connection, and I also can't install a new build through recovery
Click to expand...
Click to collapse
To the OP. Do me a favor. And i under stand this is your first time messing with a rooted device.
I need you to either get your SDK up and running, and do the patch for it to pick up your Nook Color. Once you do that you need to go into the adb command prompt and type
Code:
adb kill-server
adb start-server
that will kill and start the the bridge to connect your phone to the computer
then type
Code:
adb devices
it should show your serial number
once that is done type
Code:
ls /data/app
That will show you all of your applications that are store in the /data folder on your device.
should see a bunch of com.android.[package_name]
They'll look like this
Code:
com.google.android.apps.books-2.apk
com.google.android.apps.docs-2.apk
com.google.android.apps.googlevoice-2.apk
com.google.android.apps.maps-2.apk
com.google.android.apps.plus-1.apk
com.google.android.apps.reader-1.apk
com.google.android.gm-1.apk
com.google.android.music-2.apk
com.google.android.street-1.apk
com.google.android.voicesearch-1.apk
com.google.android.youtube-1.apk
If you see those then you know your Google Apps were installed when you flashed the package from the get go.
you can also do a
Code:
ls /system/app
and look for MarketUpdater.apk GoogleServicesFramework.apk. If you see those then you know are good to go.
The only reason i'm not suggesting it's a bad flash is i had the SAME problem when i went from Rooted Stock to CM7. Once i logged into my device all of the G/Apps showed up. It was almost like they do appear until you are logged in.
what is SDK and adb
chad11 said:
what is SDK and adb
Click to expand...
Click to collapse
SDK is Software Development Kit. It enables one to create ROMs, Themes, Applications and what not. (http://developer.android.com/sdk/index.html)
the ADB is the Android Debug Bridge it is what enables your phone to talk to your computer. via the CMD prompt. (http://developer.android.com/guide/developing/tools/adb.html)
The very basics of it you will need the ADB drivers. Which i have a link to in my signature. However some extra steps must be taken to make the computer pick up the Nook Color.
I mtried to get them both but when I tried to install SDK It said I had to install a java SE thing but i don't know which windows to install: 84, 64, or ititium. I don't know if I spelled it right but they wouldn't work
@neidlinger in your post it said "ls /data/app". Well, actually it should be "adb shell ls /data/app"
Heads up.
hey, I just figured something out. when I boot into clockworkmod recovery it deosn't show up. then when I take the sd card out and power it back on it shows up. what does this mean
Hey all!
I am new to the NC community, but have quite a bit of experience working with my Samsung Fascinate. I have some minor themeing experience.
Just ordered a NC from ebay for 119 and was curious what sort of setup (ROM, KERNEL) etc are stable and working well?
What OC is stable?
Is Honeycomb worked out as fully functional?
I have done some sticky reading, and I would like to just make a bootable sdcard, and leave the Emmc alone for now.
What are the recommendations?
Thanks!
CM7 is definitely the best for this. Honeycomb did not have access to the sources and so was more of a demo.
We hope that ICS may make it onto the NC one day but for now CM7 gives a really good stable experience.
You can choose to use the latest stable CM 7.1 or choose to use one of the late nightly builds. There has been an issue with what is called SOD (Sleep of death) where the device occasionally doesn't wake up from sleep and needs a reboot. This was an issue even with 7.1 on some devices. It now appears to have been solved but requires an extra patch which should make it into a nightly soon.
Installing onto a boot SD or emmc is both easy tasks and there are plenty of guide material on this. If you are going to boot from SD make sure you use a Sandisk card (e.g. a class 4 16 or 32GB). These give much better performance when used in this role over other brands.
If you end up primarily using CM7 and not reverting to stock then I would say it is worth going full emmc. It is easy to revert to stock if you ever need to. Running from emmc gives more overall memory and makes management and back up more straightforward.
Most Nooks OC fine up to 1300 and remain stable. The boost in performance is fairly dramatic. For some reason some graphics benchmarks peak at 1200MHz and get worse if the OC is pushed higher. I guess the GPU may end up clocking lower if the main clock is pushed too far.
Thanks BOB!
I had used CM7.1 on my fascinate, but it was a short stay as it wouldn't play nice with wifi at my house. Hopefully that's not the case with the NC.
How is MIUI on the NC? From what I see it has done pretty good. Do you have any particular experience with it?
As far as kernels, what are the stable ones by name?
I have plenty of experience of writing ROMS to the internal memory with CWM so I shouldn't be too far off if I need to do that, or choose to go that route.
If you use cm7 can you still use the stock Nook Reader? or what is the reader of choice?
I believe you can only use the Stock reader in the Stock ROM. There is a standard Nook App for Android but it is not the same. Works OK for your standard reading etc but not as nice as the stock reader.
If you want to use the Stock Reader and CM& then I think your choices are ...
1) Run CM7 on the SD card and boot into Stock whenever you want to use the Stock reader.
2) Make a Stock ROM set up on a SD card, Install CM7 on emmc and reverse the procedure of 1.
3) Install a dual boot Stock and CM7 off the emmc. At start up you then choose whether to boot into Stock or CM7 and the SD card remains fully usable as data.
I did use method 3 for a while when I first started with Nook but I so rarely went into stock and I don't really need to access the stock reader that I gave up and redid the emmc as full CM7.
I did try MIUI out but I ended up reverting to standard CM7 really just to keep compatibility with other CM7s I use.
Advantages of Internal Dual boot over SDcard boot?
Been running CM7 off an SDcard for almost a year...
Considering moving too a dual boot internal setup stock 1.4.2 + CM7.2...
But not really sure of the advantages/disadvantages of dual internal vs. emmc stock + CM7 on the sdcard.
The only thing I can think of is that dual internal would allow bot stock and CM7 to use my new 32GB SD card...though I haven't decided if that's an advantage or disadvantage
I do want to keep stock around for the kids books, read in store...plus at least with the old version of CM7 I was using the Nook app didn't do well with my magazines.
Appreciate any guidance!
Charles
charles_w said:
Been running CM7 off an SDcard for almost a year...
Considering moving too a dual boot internal setup stock 1.4.2 + CM7.2...
But not really sure of the advantages/disadvantages of dual internal vs. emmc stock + CM7 on the sdcard.
The only thing I can think of is that dual internal would allow bot stock and CM7 to use my new 32GB SD card...though I haven't decided if that's an advantage or disadvantage
I do want to keep stock around for the kids books, read in store...plus at least with the old version of CM7 I was using the Nook app didn't do well with my magazines.
Appreciate any guidance!
Charles
Click to expand...
Click to collapse
I personally would stay away from dual booting on emmc. It plays with your internal partitions which is not a good idea. I would keep stock on emmc and the newly released 7.2-RC1 on SD. By making one simple change to stock you can have both systems share the 32GB card and not have to take the card out ever. The boot menu of CM7 makes it very easy to boot between the two.
Sent from my Nook Color running ICS and Tapatalk
Thanks for the reply.
leapinlar said:
By making one simple change to stock you can have both systems share the 32GB card
Click to expand...
Click to collapse
Don't suppose you happen to have a link to a post that describes that one simple change do you?
Hope to hear from some others...as it seems many use the dual boot internal...so there must be some advantages for certain scenarios.
Charles
charles_w said:
Thanks for the reply.
Don't suppose you happen to have a link to a post that describes that one simple change do you?
Hope to hear from some others...as it seems many use the dual boot internal...so there must be some advantages for certain scenarios.
Charles
Click to expand...
Click to collapse
It does have advantages, you don't have to worry about SD card switches, etc. I was just saying it is non-standard and risky to your partitions. One of the partitions, (2) is vital to your system (it has your serial #, etc in it) and since you have to write to the partition table to accomplish dual boot, you risk the possibility of corrupting it as you are setting up dual boot. But a lot of people have done it with no problem.
I don't have a link on how to make the change. It is a very simple change to one file. There is a text file in /system/etc named vold.fstab. In it there is a line that contains 'sdcard auto' in it. Change that to 'sdcard 4'. (without the quotes.) Now the hard part. You have to be rooted on emmc to have access to the file. But there are plenty of rooting threads that tell you how. You can even unroot after you have fixed the file if you want. The other way is to change the file on your PC using adb. Both methods take a little extra effort, but it is worth it to not have to swap SD cards all the time. Both systems then share the SD card storage area. By making this change, I know of no advantage to dual boot and it is much safer (and you already have the SD set up).
And you use the boot menu to select which operating system you want to boot to. That comes with CM7. (But you know that having run CM7 for a year).
Sent from my Nook Color running ICS and Tapatalk
found the link for sharing sdcard
leapinlar said:
I don't have a link on how to make the change. It is a very simple change to one file. There is a text file in /system/etc named vold.fstab. In it there is a line that contains 'sdcard auto' in it. Change that to 'sdcard 4'. (without the quotes.) Now the hard part. You have to be rooted on emmc to have access to the file.
Click to expand...
Click to collapse
Found it, http://forum.xda-developers.com/showpost.php?p=13668471&postcount=529
and it doesn't even require emmc to be rooted.
Charles
charles_w said:
Found it, http://forum.xda-developers.com/showpost.php?p=13668471&postcount=529
and it doesn't even require emmx to be rooted.
Charles
Click to expand...
Click to collapse
good job!
Sent from my Nook Color running ICS and Tapatalk
charles_w said:
Found it, http://forum.xda-developers.com/showpost.php?p=13668471&postcount=529
and it doesn't even require emmc to be rooted.
Charles
Click to expand...
Click to collapse
Seems the File Expert feature to mount system as read write is no longer included in the free version. Is there a terminal command for that?
Sent from my NookColor using Tapatalk 2 Beta-2
Sherip said:
Seems the File Expert feature to mount system as read write is no longer included in the free version. Is there a terminal command for that?
Sent from my NookColor using Tapatalk 2 Beta-2
Click to expand...
Click to collapse
The free version of ES Explorer allows mounting system as r/w.
Little update....
I have found that the best setup I have found so far is CM 7.2 RC1 (03042012) with V6 (Update 9 RC6.9) supercharger set to option 9 (super 1000HP) supercharge (link for the V6 is on Mr666's page). The ICS transitions included in RC1 are swift and with the supercharger everything is super smooth. I can say I have noticed a small increase in my battery life as well. I toyed around with the UV/OC settings and returned to the sleep of death's I was getting on 7.1. So I re-flashed and just have left everything set to default in the peformance settings that comes with 7.2. So far, no SOD"s and I have a very capable tablet.
leapinlar said:
The free version of ES Explorer allows mounting system as r/w.
Click to expand...
Click to collapse
When I set the option in ES Explorer, I get an error message that it failed to mount r/w. Possibly this is not possible without rooting emmc. In terminal I can't make the Nooksys folder.
Sent from my NookColor using Tapatalk 2 Beta-2
Sherip said:
When I set the option in ES Explorer, I get an error message that it failed to mount r/w. Possibly this is not possible without rooting emmc. In terminal I can't make the Nooksys folder.
Sent from my NookColor using Tapatalk 2 Beta-2
Click to expand...
Click to collapse
You don't need to mount it where racks said. You can mount it in /data, which you should be able to make r/w. Where it says /mnt/nooksys, substitute /data/nooksys. First go to /data with es explorer and manually create the nooksys folder (you need to set your home directory to / in es explorer before you can see /data). Then follow his steps except don't do the mkdir command since you did it manually. And wherever it says /mnt substitute /data.
Edit: you need to modify the mount command, it now needs to have appended to the end, -t ext4. - Scratch that. It's only necessary if you are trying to do it from CM9. CM7 works OK as written.
I created nooksys in data with ES. In terminal I tried:
$su
# mount -o /dev/block/mmcblk0p5 /data/nooksys
and it returns
mount: not found
Any idea how to fix?
I have cm7.2 RC-1 on SD (verygreen but boot partition was resized) and stock 1.42 on emmc (untouched except by b&n)
Sent from my NookColor using Tapatalk 2 Beta-2
Sherip said:
I created nooksys in data with ES. In terminal I tried:
$su
# mount -o /dev/block/mmcblk0p5 /data/nooksys
and it returns
mount: not found
Any idea how to fix?
I have cm7.2 RC-1 on SD (verygreen but boot partition was resized) and stock 1.42 on emmc (untouched except by b&n)
Sent from my NookColor using Tapatalk 2 Beta-2
Click to expand...
Click to collapse
What is the -o in the line for? And you manually created the folder first? And you did check the root button in settings?
All the options for Root Settings in ES File Explorer are checked. I have / set as the home directory. I created a folder named nooksys manually inside /data using ES. I closed ES and started terminal. I'm not sure what the -o is for, I found it in some other posts and I guess I was just trying to fix it myself, but the error message
mount: not found
is the same with and without the -o
Edit: also the version of ES File Explorer is the latest version per "Check Now"
Sherip said:
All the options for Root Settings in ES File Explorer are checked. I have / set as the home directory. I created a folder named nooksys manually inside /data using ES. I closed ES and started terminal. I'm not sure what the -o is for, I found it in some other posts and I guess I was just trying to fix it myself, but the error message
mount: not found
is the same with and without the -o
Edit: also the version of ES File Explorer is the latest version per "Check Now"
Click to expand...
Click to collapse
After you created the folder, did you check it. By that I mean open it? It should be an empty folder. Exit out of the folder, but leave Es explorer open. Use the home key to get back to home screen so you can open terminal. I don't know much about es, maybe it has to stay open to keep root access.
Edit: the :not found error is saying it cannot understand the mount command. Are you using all lower case? Very important. Terminal does not like upper case.
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?