I've done all the searching, downloading and tried about 4 ways to get a good root on my NST. Nothing seems to work the way I've seen with other devices. I've tried Nooter, Touch Nooter, Nook Manager, and a special SD image for TopHat (an app for Soaring!). Many of the processes seem to be at least 2 years old (I know, I'm a late adopter).
So the question is: What is the generally accepted process for Rooting a Nook, in the new world?
I'd personally recommend NookManager. Used it on my 1.2.1 Glow and it worked like a freaking Charm. Plus there's a thing you can download to add into so after you root you go back a bit in the setup process and install google manager. Takes anywhere from a couple hours to a day but it'll recognize.
NookManager works fine - I'm literally rooting my 1.2.1 NST at the moment with it.
It took a few tries to find something that would write the card correctly though - using the Nook itself or my Xperia Mini as an SD writer didn't work, I've had to dig out a MicroSD>SD adapter and this has worked like a charm.
I've used NookManager + dd + Debian laptop with integrated card-reader to root a Nook Simple Touch with 1.2.1.
I'd recommend obtaining a separate small microSD card, 512MB should be enough (that said, 512MB ones seem to have low Class, and i've read that cards with low Class values have problems) - my backup was ~300MB, plus ~60MB for NookManager itself. I haven't found a way to have more than one backup with NookManager, so you'll only need these ~360MB.
If your card is larger, then NM will give that space to the backup partition. AFAIU, it backs up system partitions, not /media, so backup size will stay low (i.e. it will not back up the whole 2GB internal flash).
And i've had problems resizing the primary NookManager partition on my 32GB card (gparted failed to resize it, and after that the partition was unusable), i'm going to try to fix this by formatting the partition myself, making it bootable, and copying the partition from NookManager.img into it, but that's a long shot.
Anyway, just use a separate small microSD card for NookManager, and a big one for running NST normally (as a storage space for apps and books).
Nookmanager hands down. Especially if you're new to the whole process, it walks you through everything once you've made the SD card.
L_R_N said:
I've used NookManager + dd + Debian laptop with integrated card-reader to root a Nook Simple Touch with 1.2.1.
Click to expand...
Click to collapse
Same here, pretty much. NookManager worked perfectly for me. The only thing I had to re-do was upgrading from UK 1.2.0 to UK 1.2.1 before using NookManager. Good thing I took my backup of 1.2.0 before rooting!
I'd recommend obtaining a separate small microSD card, 512MB should be enough (that said, 512MB ones seem to have low Class, and i've read that cards with low Class values have problems) - my backup was ~300MB, plus ~60MB for NookManager itself.
Click to expand...
Click to collapse
NookManager could, conceivably, need just over 2GB for a backup - but only if the entire onboard memory is full and isn't compressible with gzip. My backups were about the same size as yours, but I'd suggest going with a minimum of a 2GB card to be on the safe side, and verifying the md5 checksum.
I haven't found a way to have more than one backup with NookManager, so you'll only need these ~360MB.
Click to expand...
Click to collapse
There's currently no code in NookManager to handle multiple backup files; a new backup will erase any pre-existing backup.
If your card is larger, then NM will give that space to the backup partition. AFAIU, it backs up system partitions, not /media, so backup size will stay low (i.e. it will not back up the whole 2GB internal flash).
Click to expand...
Click to collapse
That's incorrect; NookManager does backup the entire 2GB internal flash, but it prepares by zeroing all unallocated space so that it compresses well using gzip.
...
Anyway, just use a separate small microSD card for NookManager, and a big one for running NST normally (as a storage space for apps and books).
Click to expand...
Click to collapse
32GB Sandisk UHS-I/Class 10 cards are under £17 now, and 16GB cards are under £10, so why bother with less for your main card? Buying larger cards also makes them more likely to still be useful with future devices that you might wish to re-use them in. I went for a 32GB card and loaded all the arddict dictionaries I could find (including 11GB for the complete English Wikipedia) and Wikitravel (~700MB). I'm keeping /media for screensavers (~75MB for all the xkcd strips!)
cowbutt said:
32GB Sandisk UHS-I/Class 10 cards are under £17 now, and 16GB cards are under £10, so why bother with less for your main card? Buying larger cards also makes them more likely to still be useful with future devices that you might wish to re-use them in. I went for a 32GB card and loaded all the arddict dictionaries I could find (including 11GB for the complete English Wikipedia) and Wikitravel (~700MB). I'm keeping /media for screensavers (~75MB for all the xkcd strips!)
Click to expand...
Click to collapse
My logic here is simple: smaller card -> less time spent on backing it up. One small card for NookManager (which you would only use when rooting or making backups), one large card for data (which you'll always keep in your Nook).
By the way, i did manage to re-size first sdcard partition (where NookManager is), made it much bigger, without breaking NookManager. Now i'm also using it for data.
L_R_N said:
My logic here is simple: smaller card -> less time spent on backing it up.
Click to expand...
Click to collapse
Only if you fill it, or back it up by imaging the whole card.
To be honest, though, my SD cards are only portable copies of data that I have elsewhere anyway. On multiple devices and media if (vaguely) important or time-consuming to reconstruct.
Related
I thought this might be useful to anyone else in my situation. I had apps2sd installed on the stock 4GB card but purchased a larger class 6 card and wanted to seamlessly switch over without reinstalling all my apps and have my application data work correctly etc. I couldn't find a straightforward guide online so I gave it my best educated shot and it worked for me. If you got apps2sd working then you should be familiar with the partitioning etc.
I got it to work upgrading using the following steps:
1. Nandroid +ext backup!
2. Copied all files/folders from old (stock) card onto folder in computer using a card reader (apps2sd and linux swap partitions aren't visible but are included in the nandroid ext backup) (Put aside old/stock card with all original data and partitions just in case the rest doesn't work)
3. Inserted new card into phone and booted into 1.6.2 recovery (go Carebear!)
4. Partioned new card. (I actually changed the partition size from previous setup so it shouldn't matter as it worked fine for me. Made 32MB linux swap and 512MB ext2 and the remainder FAT32)
5. Upgraded ext2 partition to ext3. Shut down.
6. Removed new card from phone, insert into card reader and copy all files from folder backup of old card onto the FAT32 partition of the new card.
7. Insert new card back into phone. Boot to recovery again and do a Nandroid restore of your +ext backup and VOILA!! It boot looped once but after second boot it has been running flawlessly with all apps installed on ext3 partition and all original data in place etc.
Hope this helps anyone confused, as I sure was. It really was much simpler than I thought it would be.
phaelenp said:
I thought this might be useful to anyone else in my situation. I had apps2sd installed on the stock 4GB card but purchased a larger class 6 card and wanted to seamlessly switch over without reinstalling all my apps and have my application data work correctly etc. I couldn't find a straightforward guide online so I gave it my best educated shot and it worked for me. If you got apps2sd working then you should be familiar with the partitioning etc.
I got it to work upgrading using the following steps:
1. Nandroid +ext backup!
2. Copied all files/folders from old (stock) card onto folder in computer using a card reader (apps2sd and linux swap partitions aren't visible but are included in the nandroid ext backup) (Put aside old/stock card with all original data and partitions just in case the rest doesn't work)
3. Inserted new card into phone and booted into 1.6.2 recovery (go Carebear!)
4. Partioned new card. (I actually changed the partition size from previous setup so it shouldn't matter as it worked fine for me. Made 32MB linux swap and 512MB ext2 and the remainder FAT32)
5. Upgraded ext2 partition to ext3. Shut down.
6. Removed new card from phone, insert into card reader and copy all files from folder backup of old card onto the FAT32 partition of the new card.
7. Insert new card back into phone. Boot to recovery again and do a Nandroid restore of your +ext backup and VOILA!! It boot looped once but after second boot it has been running flawlessly with all apps installed on ext3 partition and all original data in place etc.
Hope this helps anyone confused, as I sure was. It really was much simpler than I thought it would be.
Click to expand...
Click to collapse
Thanks for the procedure, that will be very useful!
I'll also take this chance to ask you how were apps2sd performing with the stock 4Gb SD? this is the one thing that's keeping me from going the apps2sd way, not knowing if the stock card is too slow for it to work correctly.
danimar1 said:
Thanks for the procedure, that will be very useful!
I'll also take this chance to ask you how were apps2sd performing with the stock 4Gb SD? this is the one thing that's keeping me from going the apps2sd way, not knowing if the stock card is too slow for it to work correctly.
Click to expand...
Click to collapse
Honestly, I didn't notice ANY difference in performance once I got it set up correctly. I have a class 6 card now but really, they seemed to run perfect on the stock class 2.
phaelenp said:
Honestly, I didn't notice ANY difference in performance once I got it set up correctly. I have a class 6 card now but really, they seemed to run perfect on the stock class 2.
Click to expand...
Click to collapse
The real difference between a class2 and a class6 has to do with the swap, not so much a2sd, although the apps may load a little faster(nominal difference)... it really is all about the swap, and being able to write and read it faster.
On a G1, with 96MBs of swap, and most of a Hero ROMs RAM being on the swap partition, it was a huge difference, very noticeable, with the N1, very little will ever end up on the swap, and mostly is there to make it so that you can open a few more apps.
pjcforpres said:
The real difference between a class2 and a class6 has to do with the swap, not so much a2sd, although the apps may load a little faster(nominal difference)... it really is all about the swap, and being able to write and read it faster.
On a G1, with 96MBs of swap, and most of a Hero ROMs RAM being on the swap partition, it was a huge difference, very noticeable, with the N1, very little will ever end up on the swap, and mostly is there to make it so that you can open a few more apps.
Click to expand...
Click to collapse
What do you recommend for size with the swap partition on an N1? I just went with the default 32MBs. Will I see any increase in performance by increasing that?
phaelenp said:
What do you recommend for size with the swap partition on an N1? I just went with the default 32MBs. Will I see any increase in performance by increasing that?
Click to expand...
Click to collapse
It is all about preference... with the N1 there really is little to no need for a swap. If you use it, yes the developer recommended 32 is probably best.
But this phone has so much RAM, that swap isn't really needed at all. The whole idea behind the swap partitions was so we could boot a larger ROM than the stock phone could handle, ie a Hero ROM on a G1.
None the less, there are some small benefits gained with swap used with one of the Desire ROMs... for me, I don't use enough different apps to really see those benefits, but others that use tons of apps will see the added RAM.
pjcforpres said:
It is all about preference... with the N1 there really is little to no need for a swap. If you use it, yes the developer recommended 32 is probably best.
But this phone has so much RAM, that swap isn't really needed at all. The whole idea behind the swap partitions was so we could boot a larger ROM than the stock phone could handle, ie a Hero ROM on a G1.
None the less, there are some small benefits gained with swap used with one of the Desire ROMs... for me, I don't use enough different apps to really see those benefits, but others that use tons of apps will see the added RAM.
Click to expand...
Click to collapse
Thanks! I have a lot of apps installed but I'm rarely using a lot of them simultaneously so I guess no need to worry about it. I mean, this thing frickin' FLIES as I have it set up now!!
Well, i'm a noob to this forum, and to doing ANY rooting/flashing. There, thats out in the open XD
Heres the specs:
CM7 7.0.3 Stable
Nook Color (Blue Dot)
ADW Launcher
Onto the issue! I have searched ENDLESSLY for a solution to this, but have come up short. Nearly everytime I power off/on or reboot the Nook, all my widgets show "Problem Loading Widget". The ONLY way to get them running again is deleting and replacing them again on the screen.
Let me explain some things I have done and hopefully we can figure this out. I am assuming, that it may be due to me performing this - http://forum.xda-developers.com/showthread.php?t=1034939. Basically what that does is take the unused eMMC from the NC and tag it as the SDCard. The reason for doing that is because I don't have any ACTUAL decent sized SD cards and figured why not use the 5GB thats avail and unused on the Nook, and "simulate" it as being a 5GB SD card for apps and whatever else.
Nearly every post I have read says it has to do with having the apps for the widgets on the SD Card. Well, they're not, they're on internal memory. AND, if I do move them to my "simulated" SD Card, they don't even come up in the widget list, so that clears that option.
Also, since I had a Blue Dot Nook, I performed this - http://forum.xda-developers.com/showthread.php?t=1094371 and partitioned to the old style NC.
I have tried and tried to find out where the apps, if stored "internally", actually are. I cannot for the life of me find them, other than the default Google Apps in /system/app, as well as the ones I have downloaded on the "simulated" SD card under /mnt/asec & /mnt/sdcard/android.secure.
Also, when I plug the NC into my PC, I see whatever is on my "simulated" 5GB SD card (which is really the eMMC of the device). Is it possible to view the root of the device at all to see ALL the files/folders on it?
If someone can solve this, I will be eternally grateful, in a totally non gay way atleast. THANKS!
Hey there....
I'm new to the NookColor and rooting/flashing Android devices, too (though, I did run Linux on my Palm Tungsten T3, back in the day). I probably only partially understand your woes, but it seems to me that your problem stems from the faking microSD thing. Maybe it's not so much that Android wants to put something in the SD, as much as it's confused, when it probes for orthodoxy. I understand the want to use the internal memory, instead of buying a mSD, honestly.
Again, I'm totally new to this, but reading your post and many other posts in the last 48 hours, I think I might have a valid solution: start over. If I were you, I'd do the following, which, incidentally, is very much what I'm in the process of doing, too. I'm starting from "blue dot" scratch with two mSD's (2GB & 8GB) in-hand, though. By the way, and if it's any help to you, I bought my Class 4 SanDisk 8GB mSD at Office Depot yesterday for around $15 (on sale?).
1. Buy a microSD card.
2. Image the card with ClockworkMod.
3. Install TitaniumBackup Free.
4. Backup all of your apps/stuff to the microSD card with TitaniumBackup.
5. Save an image of your current setup with ClockworkMod (booting from mSD, backing up to mSD)
6. Repartition to the old (pre-"blue-dot") scheme, again, using the first mrm3.net link below as a guide.
7. Install the latest CM7 Nightly for "encore"...
8. Save an image of your current setup with ClockworkMod (booting from mSD, backing up to mSD)
9. Install TitaniumBackup Free.
10. Restore all of your apps to the microSD card with TitaniumBackup.
(Of course, I'm assuming a lot of things... I guess I'm just thinking aloud... Maybe some of this is of some use to you. Good luck!)
-v
p.s.... I had a few links I was going to share, but I'm not allowed to share external links until after my 8th post (and I understand why that's a rule)... lol..
There seems to be plenty of threads about these things around here. I just don't have them right now..
Thank you vulariter! It'd be great if when you finish getting everything set up, letting me know how it works out for you. I know people have been having some pretty weird things happening with the blue dot Nooks. Appreciate the info.
I"m happy to report that my internal CM7 Nightly install went well. I chose to go with a 2 GB apps / 4 GB media internal partitioning scheme. I like breathing room, on both sides..lol.. I also like doing things the difficult way, sometimes.. (just being honest)...
Minus the unnecessary convolution of my rooting the stock OS, 50+ complex character WPA2 key, static IP WIFI network, and email address fiasco, here's basically what I did. Again, I'd love to share the external links, but I don't think it will let me do so.
Oh, and always check MD5 sums on the files you download, wherever possible. Corruption in these files will surely eat your Nook alive, at least a little. lol.. Yes, be very scared of that.
Also, don't forget to backup your ClockworkMod backups to a better medium than the microSD card. I used 7zip to archive them on my laptop's internal drive. A cloud backup of them would probably be better (e.g. Dropbox). Just remember, you're putting potentially personal info out there, wherever you put these backups.
Thanks to all the people who figured this stuff out (see the links / websites below, to give them credit).
Bought a NookColor at my local B&N. (I later read about the "blue dot" thing and realized mine had the "blue dot" on the back of the box.)
SIDE NOTE: My understanding is that the "blue dot" signifies only a few important things. 1. a 5 GB apps / 1 GB media partitioning scheme... 2. U-Boot 1.2, with the "Read Forever" logo..... 3. Maybe an unlocking of a few more cylinders (about 250 MB)??? I've only read a little on this..... 4. Maybe a different chip revision or two, inside.
Bought a SanDisk Class 4 (class 6 would have been better) 8GB microSD card.
Located my microSD to SD adapter, which is a priceless item to me.
Located my USB many-in-one card reader, because my Lenovo R61's internal SD reader is unstable.
Located my 2GB class ? microSD card, which I once used in my old LG env2.
Connected my USB card reader to my laptop.
Inserted the 2GB mSD into my USB card reader.
Copied all of my old music, etc, on my 2GB microSD to a directory on my laptop for posterity.
Downloaded the latest version of Win32DiskImager. (Link 1)
Downloaded the latest version of ClockworkMod 2GB SD image. (Link 1)
Imaged my 2GB mSD with the ClockworkMod image.
Created "clockworkmod" and "clockworkmod\backup" directories, inside of the 2 GB mSD (whose disk label is now "boot").
Downloaded the "Custom: 2GB for Apps and 4GB for Media" partitioning file from mrm3.net and placed it in the root directory of my 2 GB mSD.
Downloaded the "Mandatory Data Format File" from mrm3.net and placed it in the root directory of my 2 GB mSD.
Downloaded the latest CM7 "encore" Nightly from cyanogenmod.com and placed it in the root directory of my 2 GB mSD.
Downloaded the latest "encore" Gapps from mrm3.net and placed it in the root directory of my 2 GB mSD.
Confirmed my Gmail and Youtube accounts were linked. This is also the same address which I'm using for my B&N account.
SIDE NOTE: I had to change my B&N account's non-Gmail email address to align my email addresses. I think this may have caused a problem with my obtained-at-Nook-purchase B&N Membership Card, because it no longer works... (I've contacted them about it...and their answer is unsatisfactory. Beware!)
Unboxed my NookColor and began charging it, via the wall plug.
Booted my stock NookColor, signed into my WIFI network and registered my device to my Gmail email address.
Played around with the stock OS and Nook apps, because I'll probably never ever see them again.. The Crossword game was awesome! I didn't allow myself to become attached to their reading apps, to be honest..lol.. (I would have probably been attached, had I not been proactive in my "hacking".)
Powered off my NookColor.
Inserted the 2 GB mSD into my NookColor.
Booted my NookColor into ClockworkMod.
Saved a backup of the stock system to the "backup" directory I created earlier.
Followed the instructions at mrm3.net to repartition my NookColor (rebooting, as directed).
Removed the 2 GB mSD card.
Rebooted again, allowing the Nook to recover from the repartitioning. I did not reregister the device in this step. I just waited for the woman's face to appear and shut it down.
Inserted the 2 GB mSD card.
Booted my NookColor into ClockworkMod.
Saved a backup of the NEWLY PARTITIONED stock system to the "backup" directory I created earlier.
I followed the mrm3.net CM7 Nook Nightlies instructions, but I'll paraphrase here. (Definitely seek this article out, and don't take my word for it.)
Still in ClockworkMod, I reformatted the "data", "system",and "cache"partitions.
Used "install from zip" to install "cm_encore_full-xx.zip"
Used "install from zip" to install "Nook_Color_Google_Apps.zip"
This may be a good time to obtain another backup, if you're paranoid. I did not and wasn't...
Removed the 2 GB mSD card.
Rebooted again, allowing CM7 to do its thing.
Signed into my WIFI network, using the menus.
Signed into the Google Market, selecting all of the Gapps, when prompted. (I figure I can uninstall them, if I find them totally useless.) (e.g. Facebook
app, since I quit it..lol)
Inserted my 8 GB mSD card in the NookColor for the first time and formatted it, from within CM7. I could have made a Win32DiskImage image of the 2 GB ClockworkMod mSD, wiped it out and formatted it for general use, but I like having my own data (media files / apps) separate from my "live recovery environment(s)." Point being, I could have gotten by with just a single mSD card, as tiny as 2 GB and the cheapest class, but I splurged, because I want to keep some music and things on tap, wherever I go.
Rejoiced in the open source goodness.
This would another good time to obtain another backup. I should go do that right now..
Please keep in mind that I might be taking some things for granted. My mind has been altered by being a *NIX System Administrator...
Good luck and let me know if you have any questions.
-v
Great stuff V! So this is what I have decided to do. I will keep my current system until the next stable version of CM is released. Once that happens, i'll go ahead and repartition, reformat, and of course reinstall following all of the proper procedures that i'm too lazy to write out here.
The only other issue I was having with my Nook is that it wasnt recognizing when an SD card was plugged in. I thought it may have been CM7, so I flashed back to the stock OS, and it still wouldnt recognize it plugged in. However, if I have the SD card plugged in, and reboot, it shows the SD card mounted fine. I need to do a check to make sure I can read/write to it, but i'm assuming it will be no problem if it sees it fine. If I were to remove the card, it would not say that the card is unplugged, so theres no instant feedback; it requires a reboot every time to notice if the card is plugged in or not. For me, all I need is it to be recognized and be accessible, as its not like I am going to be taking it out all the time, it will be in there pretty much for good.
I have a new-to-me Nook Color running the 1.4.2 firmware. I did a factory reset and set up my Barnes and Noble account. Yay me. However I can't FOR THE LIFE OF ME get it to boot off the SD card.
I've tried two 2GB cards (Samsung & SanDisk) and one 8GB SanDisk card. Also used three different card readers to burn the .IMG. What am I missing? I stick them in the Nook and the Nook just boots up as normal without hesitation. I've been rooting cell phones for years but this tablet has me stumped.
Is there another option I can use to flash CWM? Once I get it flashed I'm sure flashing the ROM is a breeze...
EDIT: After more and more digging, it might be an issue with writing to the wrong partition. How can I check to see if I'm installing to the write partition? I've formatted my cards multiple times. This is the stuff I see in a lot of answer posts:
of = /dev/disk# (good)
of = /dev/disk#p# (bad)
Click to expand...
Click to collapse
have you wrote an sd card that will boot (ie. Clockwork 4 gig et al). Can you read and write to it from within stock? More data please, what were you writing to what partition?
When I use the uSD card to boot and it is plugged into the computer you should hear three da-da-das.
n8nmad said:
have you wrote an sd card that will boot (ie. Clockwork 4 gig et al). Can you read and write to it from within stock? More data please, what were you writing to what partition?
When I use the uSD card to boot and it is plugged into the computer you should hear three da-da-das.
Click to expand...
Click to collapse
I have never successfully created an SD card that will boot on the Nook. Outside of the Nook, I have no way of testing to see if works or not.
You asked what partition, but I only have one partition on the card. If I open up the card in Disk Manager, there's just one allotment of space. When you burn the Image, is that supposed to create a separate partition that's visible in My Computer? If so, that's not happening because all the data is in one spot on the card (from what I can tell)
You need to flash the card. I suggest starting here:
http://forum.xda-developers.com/showthread.php?t=922870
or any of the other dev threads dealing with dual boots or whatever it is you are trying to accomplish.
Does your stock nook format sd cards to write books and such? If not that would be a big clue that it is a hardware issue
n8nmad said:
You need to flash the card. I suggest starting here:
http://forum.xda-developers.com/showthread.php?t=922870
or any of the other dev threads dealing with dual boots or whatever it is you are trying to accomplish.
Does your stock nook format sd cards to write books and such? If not that would be a big clue that it is a hardware issue
Click to expand...
Click to collapse
Yes, the stock Nook picks up the cards and formats them when installed. I've used these cards for all my smartphone rooting without any issues.
I've also formatted the cards and burned the CWM images using the windiskimager tool. It's just not bootable for some reason
The very first fundamentally step is to check whether it is a NOOKcolor or Nook Tablet.
votinh said:
The very first fundamentally step is to check whether it is a NOOKcolor or Nook Tablet.
Click to expand...
Click to collapse
Holy balls, I feel like an idiot. I had no idea the two were so similar. I am almost certain I have the Color (going by what it says on the case) but I'll look closely when I get home
It's the Nook Tablet. Wow....just...wow
On the bright side, at least my technical experience isn't the problem. My common sense on the other hand...
I believe you still can root the NT or run the pre-alpha ROM from it.
Unsure if it's able to run from uSD yet or not.
I read a number of latest threads about rooting NST 1.2.0 having trouble. I am so new to this process and would like to have a full set of proven steps to do it.
Some suggests tinynoot but I found the thread which is more for Glow. I am not sure if it is right way to go.
Does anyone know if TouchNooter 1.2.0 version is available?
npoon said:
I read a number of latest threads about rooting NST 1.2.0 having trouble. I am so new to this process and would like to have a full set of proven steps to do it.
Some suggests tinynoot but I found the thread which is more for Glow. I am not sure if it is right way to go.
Does anyone know if TouchNooter 1.2.0 version is available?
Click to expand...
Click to collapse
this
[Root] NookManager - graphical rooter for 1.2.0 and beyond
http://forum.xda-developers.com/showthread.php?t=2040351
Does anyone know if TouchNooter 1.2.0 version is available?
Click to expand...
Click to collapse
It does not exist.
Tinynoot works for glow and non glow firmware 1.2
It includes minimal apps, so you will need to know how to use adb to install apps.
The latest version of NookManager will allow installation of apps from the Amazon Appstore without using ADB. This is your best bet for rooting FW 1.2.0 right now and it is a very easy, menu driven root method. (See post 2 in this thread for the link.)
Make sure you get a good backup of your Nook first. The easiest way to do this is to write the NookManager image to a 4GB SD card, boot from the card and use the backup option of the tool.
David0226 said:
The latest version of NookManager will allow installation of apps from the Amazon Appstore without using ADB. This is your best bet for rooting FW 1.2.0 right now and it is a very easy, menu driven root method. (See post 2 in this thread for the link.)
Make sure you get a good backup of your Nook first. The easiest way to do this is to write the NookManager image to a 4GB SD card, boot from the card and use the backup option of the tool.
Click to expand...
Click to collapse
I used NookManager and made a backup before rooting, do you know where I can find the backup so I can transfer it to my PC ?.
mug2k said:
I used NookManager and made a backup before rooting, do you know where I can find the backup so I can transfer it to my PC ?.
Click to expand...
Click to collapse
it's on the microSD card you used to make the backup.
David0226 said:
Make sure you get a good backup of your Nook first. The easiest way to do this is to write the NookManager image to a 4GB SD card, boot from the card and use the backup option of the tool.
Click to expand...
Click to collapse
will a 2gb sd card do? OR a 4gb card is necessary?
2gb card should work. I rooted using nookmanager yesterday and made a backup with a 2gb sd card
Will 10gb work? Sorry if it sounds too silly. :crying:
Thanks guys, you are great.
npoon said:
Will 10gb work? Sorry if it sounds too silly. :crying:
Thanks guys, you are great.
Click to expand...
Click to collapse
It will. I used a 16 GB one lol
Sent from my SGH-T959 using Tapatalk 2
I used Win32DiskImager.exe trying to write NookManager.img to my 16gb but didn't know I had to run it as Administrator. After "Write", the SD card became unformated. I went ahead and now the SD card became 64mb.
I have Windows XP Prof and tried Disk Manager and Diskpart without success.
Anyone knows how to get my SD card fix?
XP doesn't have any tools to reformat SD cards.
Try: MiniTool Partition Wizard (Home Edition)
SD Card became 64 mb
npoon said:
I used Win32DiskImager.exe trying to write NookManager.img to my 16gb but didn't know I had to run it as Administrator. After "Write", the SD card became unformated. I went ahead and now the SD card became 64mb.
I have Windows XP Prof and tried Disk Manager and Diskpart without success.
Anyone knows how to get my SD card fix?
Click to expand...
Click to collapse
The SD card becomes 64mb because there are now two partitions on it. It is meant to be like this after installing nook manager on it. Windows will only see one though if connected directly to the PC. You need to put it in your nook and connect the nook to the pc with the usb lead. You will then see two drives, one with nook manager on it and one with a back up of your original nook image, if you did one!
To format your sd card you can use SDFormatter. Just search for it. If you do this though it will wipe off anything you have on it, especially any back you have done.
Thanks. I finally found HP USB Manager to reform it back to 16gb.
I found one weird thing is Win Imager really doesn't like my 16gb SD Card as it always does is to make it unformat and then force it becomes 68mb. Anyhow, I used NookManager backed up but can't find a file for the backup. Does anyone know where it is sitting on SD card?
npoon said:
Thanks. I finally found HP USB Manager to reform it back to 16gb.
I found one weird thing is Win Imager really doesn't like my 16gb SD Card as it always does is to make it unformat and then force it becomes 68mb. Anyhow, I used NookManager backed up but can't find a file for the backup. Does anyone know where it is sitting on SD card?
Click to expand...
Click to collapse
Win Imager is working properly. The unformat is probably just that Win Imager doesn't properly inform windows of the partition table change on the card. Once Windows manages to get the new partition table loaded (e.g. remove and reinsert the card) it then sees the 64MB partition that was written to the card. See my post on the NookManager development thread for a little more info and how to get your backup off the card.
So I finally made the leap from Lollipop to Marshmallow. Everything has been going fine for the most part, but I've hit a huge snag: moving apps to SD.
I use Titanium Backup to keep a full backup of my phone on the external SD card. I depend on this backup for two purposes:
1) it makes updating the ROM (like this time) a lot easier. I do a factory reset, get the base Android going, re-install Titanium Backup from the Play Store, point it to my backups on the external SD card, and then I'm good to restore (either full app+data if that's safe, or I first re-install the app from the Play Store then just restore the app's data using TB).
2) It saves my butt in the event of a phone hardware failure, which has happen several times over my many years as an Android user. I just buy a replacement phone, move the SD card over, and restore my apps/data in a similar manner as in #1.
I have a Galaxy S5 with 16GB of internal storage, which is certainly not enough so I depend on my 64GB external SD card greatly. Between keeping all my large media on the external SD, as well as moving what large apps to SD as I can, this has been fine. I use Bliss ROM.
So make the jump from Android 5 -> 6, and finally get to the point where I need to move some of the apps I've restored to SD... but can't find the option. I do some research, and now am in a panic. From what I can tell, you can only move apps to SD if you use the SD as adopted/internal storage, which means it gets re-formatted, encrypted, and can only be used with that phone. This eliminates the possibility of #1 & #2 above. To continue performing #1 & #2, I need to use the SD as "portable storage" (the way it is now), which apparently leaves no way to move apps to SD.
I am in a pickle now, and feel stuck. I'm hoping I'm missing another option. Help?
sremick said:
So I finally made the leap from Lollipop to Marshmallow. Everything has been going fine for the most part, but I've hit a huge snag: moving apps to SD.
I use Titanium Backup to keep a full backup of my phone on the external SD card. I depend on this backup for two purposes:
1) it makes updating the ROM (like this time) a lot easier. I do a factory reset, get the base Android going, re-install Titanium Backup from the Play Store, point it to my backups on the external SD card, and then I'm good to restore (either full app+data if that's safe, or I first re-install the app from the Play Store then just restore the app's data using TB).
2) It saves my butt in the event of a phone hardware failure, which has happen several times over my many years as an Android user. I just buy a replacement phone, move the SD card over, and restore my apps/data in a similar manner as in #1.
I have a Galaxy S5 with 16GB of internal storage, which is certainly not enough so I depend on my 64GB external SD card greatly. Between keeping all my large media on the external SD, as well as moving what large apps to SD as I can, this has been fine. I use Bliss ROM.
So make the jump from Android 5 -> 6, and finally get to the point where I need to move some of the apps I've restored to SD... but can't find the option. I do some research, and now am in a panic. From what I can tell, you can only move apps to SD if you use the SD as adopted/internal storage, which means it gets re-formatted, encrypted, and can only be used with that phone. This eliminates the possibility of #1 & #2 above. To continue performing #1 & #2, I need to use the SD as "portable storage" (the way it is now), which apparently leaves no way to move apps to SD.
I am in a pickle now, and feel stuck. I'm hoping I'm missing another option. Help?
Click to expand...
Click to collapse
From what I've read there is a method for app2sd to work with mm. I never had success with it though, and downgraded to ll.
ldeveraux said:
From what I've read there is a method for app2sd to work with mm. I never had success with it though, and downgraded to ll.
Click to expand...
Click to collapse
A method other than formatting the card as internal/adopted storage? Did the method involve setting up multiple partitions?
While I could set up a FAT32 partition just for TB, then adopt the rest, my backups aren't the only thing I've needed to access after popping out the SD card. For example, just being able to load media that way is quick and sometimes a life-saver. I've also used that as a way to get zip files on that I could then flash via recovery. I'm also not clear if you can "mount" adopted storage as USB while in recovery so it's visible to the computer as a USB mass-storage device while the phone is connected via USB cable (as you have been able to do normally up to this point).
sremick said:
A method other than formatting the card as internal/adopted storage? Did the method involve setting up multiple partitions?
While I could set up a FAT32 partition just for TB, then adopt the rest, my backups aren't the only thing I've needed to access after popping out the SD card. For example, just being able to load media that way is quick and sometimes a life-saver. I've also used that as a way to get zip files on that I could then flash via recovery. I'm also not clear if you can "mount" adopted storage as USB while in recovery so it's visible to the computer as a USB mass-storage device while the phone is connected via USB cable (as you have been able to do normally up to this point).
Click to expand...
Click to collapse
I'm not the app developer, I have no clue how/if it works. It didn't for me, but did for many others. Go to that thread and read up!
ldeveraux said:
I'm not the app developer, I have no clue how/if it works. It didn't for me, but did for many others. Go to that thread and read up!
Click to expand...
Click to collapse
Which app/thread are you referring to? Or are you talking about Bliss ROM itself? I didn't post in that thread, as this issue seems generically Marshmallow-related, and not specific to Bliss.
sremick said:
Which app/thread are you referring to? Or are you talking about Bliss ROM itself? I didn't post in that thread, as this issue seems generically Marshmallow-related, and not specific to Bliss.
Click to expand...
Click to collapse
It's a marshmallow problem, not Rom specific. In xda's app section there are threads for both link2sd (not working) and app2sd (works for some). Check those, I think that's where I saw the info.
Ok it wasn't easy but I think I've gotten my head wrapped around Apps2SD and have it working. I tried the free version, backed up my 64GB external SD, partitioned it with a 16GB f2fs partition (for moving/linking apps) and the remainder exfat (for using the way I've traditionally used it). Restored everything back to the exfat partition and fixed where BeyondPod and Titanium Backup were pointing to. Did a few test links and it seemed to be working although fumbling my way through was confusing at first as I didn't find a clear "how to". Ended up buying the Pro version of Apps2SD once I felt good that this was a workable solution.
I still get an error on boot about my SD being corrupt but I just need to search on that, I'm sure there's a simple fix somewhere.
sremick said:
Ok it wasn't easy but I think I've gotten my head wrapped around Apps2SD and have it working. I tried the free version, backed up my 64GB external SD, partitioned it with a 16GB f2fs partition (for moving/linking apps) and the remainder exfat (for using the way I've traditionally used it). Restored everything back to the exfat partition and fixed where BeyondPod and Titanium Backup were pointing to. Did a few test links and it seemed to be working although fumbling my way through was confusing at first as I didn't find a clear "how to". Ended up buying the Pro version of Apps2SD once I felt good that this was a workable solution.
I still get an error on boot about my SD being corrupt but I just need to search on that, I'm sure there's a simple fix somewhere.
Click to expand...
Click to collapse
I think the consensus was to use NotifyClean (Xposed module) to eliminate that message at boot. :good: Everything still working for you otherwise? I was thinking of upgrading now, and think this might work too:
http://blog.sam.liddicott.com/2016/02/android-6-semi-adopted-storage.html
sremick said:
Ok it wasn't easy but I think I've gotten my head wrapped around Apps2SD and have it working. I tried the free version, backed up my 64GB external SD, partitioned it with a 16GB f2fs partition (for moving/linking apps) and the remainder exfat (for using the way I've traditionally used it). Restored everything back to the exfat partition and fixed where BeyondPod and Titanium Backup were pointing to. Did a few test links and it seemed to be working although fumbling my way through was confusing at first as I didn't find a clear "how to". Ended up buying the Pro version of Apps2SD once I felt good that this was a workable solution.
I still get an error on boot about my SD being corrupt but I just need to search on that, I'm sure there's a simple fix somewhere.
Click to expand...
Click to collapse
Is f2fs and exfat supported by stock MM in Apps2SD? Got it formatted with fat32 and ext4.
ldeveraux said:
I think the consensus was to use NotifyClean (Xposed module) to eliminate that message at boot
Click to expand...
Click to collapse
Ugh. I do not want to have to use Xposed.
Everything still working for you otherwise?
Click to expand...
Click to collapse
Well it was working just great... then I rebooted. Apparently some trouble getting the 2nd partition (fsfs, where the apps are being moved to) to mount at boot. Trying to sort it out in this thread:
http://forum.xda-developers.com/android/apps-games/apps2sd-partition-sd-card-link-apps-to-t3122919
andacro said:
Is f2fs and exfat supported by stock MM in Apps2SD?
Click to expand...
Click to collapse
No idea, I never run stock.