yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] belfastraven:
Yes in all of the CM builds( but NOT in the AOSP builds )root is found in developer settings. If it is not working there, one usually needs only to disble it (set it to "none") and then set it back to "applications" or "applications and adb", and it will work.

In AOSP, you must flash the superSU zip to get root, if you don't already have it in a previous AOSP build that you are flashing over. I believe 2.52 will work, but if you use a recent version like 2.68 or 2.70, you need to force it not to do a "systemless" install, as explained by amaces "You have to force it to normal system install by exporting SYSTEMLESS=false in recovery, or in /data/.supersu as described here: http://xdaforums.com/showpost.php?p=65177799&postcount=4868.". Once you have flashed the zip you can install the app from the playstore, if you want it.
[Nook HD, HD+ Android Development] gwisch:
And that is exactly what does not work for me. It does not matter what I set the root settings to - Aldiko Sync and Total Commander both unanimously declare that I have no root.
[Nook HD, HD+ Android Development] belfastraven:
[MENTION=3068171]gwisch[/MENTION], I haven't tried Aldiko Sync yet, but I did try Total Commander, which told me that I did not have root: But I do--other programs find it just fine (like the built in File Manager app, Solid Explorer, Flashify. I wonder if it is specifically looking for chainfire's SuperSu? See if you can go to settings in the CM File Manager app and give yourself root.. What were you running before the 3/14 cm build, and what version of Total Commander are you running?

hmmm I just opened total commander again and now I have root. Maybe try opening it a couple of times in a row? Also, I know you said that you tried all root settings, but what has specifically worked for me in the past was to disable root and then immediately enable it again...
[Nook HD, HD+ Android Development] neonleon29:
Does anyone ever wipe cache/dalvik cache in TWRP after your tablet is up and running? The reason I'm asking is because when I rebooted after wiping, the number of apps that it says is optimizing is less than when I originally installed the GApps (54 apps vs 80 apps). I originally had a problem getting Google apps on the Nook HD+ because I was wiping after installing. So I'm just wondering if this matters at all (I'm assuming the Google apps aren't being optimized) or as long as I still have the Google apps on my device, everything will be fine? I guess I'm asking if I need to do a factory rest and start over again.
[Nook HD, HD+ Android Development] mikemelbrooks:
I did I think the number of apps you have is dependent on which gapps you use. go to http://opengapps.org/ and you can choose how big the gapps file you install bigger more apps, pico not so much.
[Nook HD, HD+ Android Development] ipdev:
I wipe cache & dalvik before & after install. I normally don't have problems.
[Nook HD, HD+ Android Development] gwisch:
Thanks, belfastraven, that did indeed do it.

After I gave myself root in the CM File Manager (even though I still don't understand why this should be required on top of activating root in the developer settings) I had root everywhere and none of the aforementioned apps complained anymore.

Not sure what the deal with Aldiko Sync is - after all it should run on any rooted phone, so to just go looking whether SuperSU is installed or not would be pretty shortsighted and I am higly sceptical that the developer used this method.

Still, I uphold that the root method, the way we currently see it in the CM13 nightlies, could be improved.

:angel:
[Nook HD, HD+ Android Development] neonleon29:
Thanks for the replies mikemelbrooks & ipdev. When I originally installed AOSP Marshmallow, I had trouble getting the Google Apps because I was wiping cache/dalvik cache before rebooting. When open GApps nano was installed, I'm pretty sure it said optimizing 80 apps. At a later time, I wiped cache/dalvik cache and rebooted. During reboot, it said it optimized 54 apps. I'm assuming it isn't optimizing the Google apps because of the problem I had previously. But since the tablet seems to be working fine, I'm not going to worry about.
[Nook HD, HD+ Android Development] ST Dog:
It should just be "enable in developer options". Nothing more.

Not sure what you want different.

It's worked fine like that in previous versions.

Now, if it's not working correctly, it should be fixed, but workarounds will do til it is.

Unfortunately, some apps are poorly written and look for signs of SuperSU or other app to determine if root is available.
[Nook HD, HD+ Android Development] graysooner:
I also wonder about file manager root. And password protected? I am just using FX file Manger and not the pre installed one.
[Nook HD, HD+ Android Development] pvaldeben:
For anyone installing AOSP version and wants root, flash SuperSU: SuperSU-v2.52.zip.

https://download.chainfire.eu/743/SuperSU/BETA-SuperSU-v2.52.zip

found it in "[ROM[BETA][P1][6.0.1][UNOFFICIAL]OmniROM 6.0.1"

http://xdaforums.com/galaxy-tab/development/rombeta-omnirom-6-0-1-t3338383

Hope this helps anyone trying to get root.
[Nook HD, HD+ Android Development] ST Dog:
My experience with file managers is they don't ask for root permission by default. You purposely select that if you want it and I recommend only when you need it (like all things root).

I have root disabled in the filemanager until I need root access, turn it on, do what I need, then turn it off.

Just like in *nix where you become root for specific tasks then go back to normal user level.
[Nook HD, HD+ Android Development] gwisch:
...and that is exactly what I would like to work like this again.
[Nook HD, HD+ Android Development] ST Dog:
Ok. It sounded like you wanted something else v/s fixing current bugs.

Other than toggling the option, I don't recall others claiming issues in general, just specific apps that appear to be looking for a 3rd party tool like SuperSU.
[Nook HD, HD+ Android Development] mikemelbrooks:
"For anyone installing AOSP version and wants root," flash SuperSU: SuperSU-v2.52.zip.

https://download.chainfire.eu/743/Su...erSU-v2.52.zip

found it in "[ROM[BETA][P1][6.0.1][UNOFFICIAL]OmniROM 6.0.1"

http://xdaforums.com/gala...6-0-1-t3338383

Hope this helps anyone trying to get root.

why this version?
[Nook HD, HD+ Android Development] graysooner:
Ah. Forgot about that.
[Nook HD, HD+ Android Development] Subgro:
Hi, I am getting issues with installing on my Nook HD in which Gapps keeps throwing up the error "System Setup has stop working". I've tried a number of things including flashing AOSP first then wiping in between each step to install cm 13 and gapps 6.0 nano and pico. Do you guys have any advice?
[Nook HD, HD+ Android Development] pvaldeben:
Saw another post that not all version of SuperSU work on AOSP. And I verified that. Then found v2.52 and it worked for me. As to why other versions did not work , I don't know.

This was the last change to root before flashing CM but it worked so I'm staying in AOSP.
[Nook HD, HD+ Android Development] mikemelbrooks:
if it helps I have tried 10 or more times this weekend, and have had the same problem, I also have tried wiping the data folder with twrp but when I reboot all the files are still there? could some one please check their partitions and let me know what the size and format are?

I have re flashed cm12.1. with no problems ?
[Nook HD, HD+ Android Development] belfastraven:
[MENTION=5471439]mikemelbrooks[/MENTION] [MENTION=7371763]Subgro[/MENTION]-- Have you tried this: From TWRP 3.0.0-0, do a factory reset. flash the cm13 rom, flash opengapps (nano or pico should work fine), reboot. DON"T wipe anything in between the flashes or after. Make sure you are running the correct opengapps. for arm, android 6. watch the messages you get from recovery.

If you had actually wiped data successfully, btw, for sure none of your personal files or applications would have been there after you rebooted, but it'a hard to know where the problem is without seeing what happened.

You can also wipe system to do a "clean" install, just remember that without some rom installed, the system won't boot. (I believe the opengapps people are now suggesting that if you have problems)
[Nook HD, HD+ Android Development] ipdev:
Never had troubles with ovation before. I did a clean wipe with twrp 3 & tried to duplicate problems everyone seems to be having. I was very successful ! I found more issues than questions asked. I even broke it enough were I couldn't restore a cwm backup from a boot sd card. The fix to that lead me to my fix with installing in twrp. Onece I was back in twrp 3, I factory reset (after format data - reboot into recovery) Installed asop 314 build rebooted back into recovery. (Wish that was an option under reboot.) then installed opengapps pico 317. Then Wipe - Factory Reset - Reboot system. No Force Closes. - Now I am trying different installs of SuperSU. (wish me luck ?)

Edit.

So my failsafe su 2.56 installed the apk but not the binaries. After a few more attempts, I gave up. Since the apk was installed, I just ran the 2.68 beta from twrp. (With the help of terminal under advanced, I entered before the install.)

echo SYSTEMLESS=false>>/data/.supersu

Now running su 2.68.
[Nook HD, HD+ Android Development] simon-edwards:
I've come to CM13 from the last official cm12 overnights. Wiped fully, formatted to f2fs, then installed 0222 because I couldn't get WiFi working on 0314. I now know why, but didn't know at the time.

This CM build is so much more stable, smooth and generally more pleasant to use than CM11. A big Thank You to Amaces and everyone who has worked with you on this project.

After 2 weeks of tweaking I still have two main gripes...

The WiFi has been dropping out every time I closed my case. Requiring a visit to settings to re-connect it. I seem to have solved this by turning WiFi on all the time. I can't think this will be good for battery life, but time will tell.

The second is more serious for my usage: it will now only read 64GB or lower exfat cards. My pair of 128GB cards are now useless unless I format them as Fat32, which will render them useless for some files as they are too large. These worked fine on cm11.

Some questions then...

Does anyone have a solution to installing full exfat support up to at least 128GB?

Can I dirty flash, say 0315 or later, over the top of this ROM?

If not what is a good backup procedure to use to batch reinstall all the apps after updating the ROM? BTW I have had mixed success with Titanium Backup Pro in the past.
[Nook HD, HD+ Android Development] belfastraven:
Once you have successfully flashed a CM13 rom, you can dirty flash over it. Same with an AOSP rom, i.e. AOSP over AOSP, or CM13 over CM13. I'm pretty sure that you cannot dirty flash an AOSP over CM or vice versa.

Re the SD Card size problem, are you saying that the card is not seen at all? What happens if you create two 64G exfat partitions on the card? Sorry--I don't have a 128G card to try this with. Does TWRP 3.0.0-0 see the card?If it does, you can try partitioning from it.

For backup, you can backup inidividual partitions (system, boot,data, etc) using TWRP.
[Nook HD, HD+ Android Development] ST Dog:
FWIW, I've seen wi-fi drop outs reported with CM13 on other platforms. Something to do with renegotiating a key for WPA2.
[Nook HD, HD+ Android Development] sepehr@teh:
I have a Nook HD+ , want to change OS . I'm want to have more flexible OS and use more apps , but my main concern is to have a good book reader , with advanced dictionary.

Any advice , idea ?
[Nook HD, HD+ Android Development] jerry.tk:
I was trying to update my device this weekend and I was having the exact same problem. Managed to solve it by flashing older version of Open Gapps. I used file open_gapps-arm-6.0-pico-20160222.zip as somebody else suggested a few pages back in this thread.

Also didn't succeed flashing gapps nano version as it was too large for remaining system space after flashing CM.
[Nook HD, HD+ Android Development] mikemelbrooks:
Thank you Jerry I can confirm that using this older version of Gapps worked for me.
[Nook HD, HD+ Android Development] rholm:
I use Moon Reader+ with color dict. Works well.

Cheers,

Rich
[Nook HD, HD+ Android Development] ipdev:
I use the nook app & kindle app.
[Nook HD, HD+ Android Development] simon-edwards:
Thanks, I'll have a hunt around for those.

Using WiFi during sleep only seems to cost 8% battery per day though. So it is not as serious as I first thought it would be.

---------- Post added at 03:11 PM ---------- Previous post was at 02:29 PM ----------

The card, partitioned as shipped from the factory was then formatted by Windows as ExFat. It is seen by the system, but when I attempt to set it as portable storage it insists upon re-formatting it as Fat32. ExFat is not an option,indeed there don't appear to be any options at that stage.

Your suggestion to split the card lead me to experiment.

If split, then only the first partition is seen. The second is invisible.

I can safely use ExFat on these smaller partitions. I start upwards from 64gb but didn't find the non-working boundary size because...

I noticed that, as supplied, the initial partition map had a tiny 7.24mb unused area before the single 128gb partition.

I took this unused space out and created one large partition that started at the very start of the disk. There is a tiny amount of unused space at the other end now.

I used Partition Table Doctor Free for this job.

PROBLEM SOLVED!!!

Without a leading unused partition the system will now see the Windows formatted ExFat partition, and will enable it for use as portable storage without any attempt to re-format it.

This lack of ExFat formatting of portable storage has to be a bug. But at least we now have a workaround.

As soon as I got it working I started to use the card in earnest. It is working just fine.

I haven't had time to play with my backup card and see if cm13 will now format it to ExFat. I won't get a chance to try this until next week,

BTW twrp doesn't seem to have an ExFat formatting option. Only ext3 & ext4 of the modern formats. Luckily I don't need to use it now. I may have missed an option setting pane somewhere in twrp.
[Nook HD, HD+ Android Development] belfastraven:
Thanks for the update. I have successfully backed up[ and restored with TWRP 3.0.0-0 using an exfat card, so the read and write support is there, but the formatting seems to be missing right now. You get ext3 or ext4 (as you mentioned) or swap. I have gotten the aparted app to make an exfat sdcard--but that feature is noted as still experimental . It seems like cm13, itself, in my nook HD always formats sd cards for external use (as opposed to "adopted" storage) as fat32.

I'm curious--what brand of card came with that "extra" initial partition. I'd like to see if they explain what it is for. Did they by any chance say that it was for use in windows and macs?
[Nook HD, HD+ Android Development] pchc_lx:
I've been pretty stuck here... have an OVATION that previously was on a CM11 build with CWM recovery.

Flashing the TWRP 3.0 or 2.8.7.5 both give Error 7 and abort- something about CWM getting the device wrong? Won't let me flash the correct recovery...

Anyways, I am able to flash CM MM ROM with this old CWM recovery. Few things are wrong- OpenGAPPS Nano won't fit in /system- weird, it's supposed to. Oh well, Pico fits. But then MM boots (looks great and feels smooth!) but there are issues. Setup halts on selecting a WiFi network- and indeed, if skipped thru, the tablet is unable to 'Turn On' the Wifi. I read this is a kernel problem and assume all these issues are because I wasn't able to install the correct recovery.

But again, CWM won't flash it. And the SD-card based installation methods (both the larger IMG files and the separated MLO-first method) are not working- the tablet won't boot with these SD cards inserted, at all (I read this is a known issue, and it seems I need to buy a new SD card to get this working...)

Any bright ideas how to get out of this? I was able to flash an even-older CWM, and I was then able to flash the stock recovery. But now I'm stuck needing the SD card method, aren't I? ....

edit: I can get ROM Manager running on the tablet by transferring the .apk over USB. weirdly, it shows both CWM and TWRP recoveries- but it does not seem that either are now installed- as I get the Nook Install Error screen when rebooting into recovery.
[Nook HD, HD+ Android Development] belfastraven:
If your rom is running, but you don't have wifi, you can try this fix : there was a bug that hit people coming from an older rom: from [MENTION=4473900]amaces[/MENTION] response to a bug report "copy https://github.com/airend/android_device_bn_common/raw/mm-13/prebuilt/bin/toybox to /system/bin/toybox (making /system rw/adb remount needed)" You will find the bug report and response if you check the bug reports. I have attached a zip of the file here for you in case you have trouble finding it. You need to unzip it before you copy it, and would need to reboot, I think, for it to take affect.

Are you sure that you originally tried to install the proper twrp recovery? 3.0.0-0 is fine for marshmallow. Did you make sure that you got the Ovation version? If you are comfortable using adb you can go to the OP in this thread and get the instructions for copying a recovery.img to your nook. installing the zip is safer since it checks to make sure that you are putting the correct version (hummingbird or ovation) on the device. The .img files are in the zip files.

If you need to use the sd card recoveries, I would suggest reformatting an sd card, fat32 and marking it 'bootable". the copying the MLO and other files including the internal recovery (again I suggest TWRP 3.0.0-0) that you want to install. Try to make sure that the nook is powers off all the way. I often have to do so by holding the power button in for a while, as opposed to shutting it down with the "shutdown" command. Then insert the sd card and power it on. That may help you boot without using a different sd card.
[Nook HD, HD+ Android Development] pchc_lx:
I will give this a shot, thanks so much for the link. Would still need to fix my recovery eventually but this would be pretty great.

Yep I definitely tried 3.0.0 and definitely OVATION. In fact the error says something like "This .zip is for device: OVATION this device is " with nothing following there.

Does flashing with ADB bypass the types of errors thrown by flashing .zips in recovery? I'm not 100% sure if I can get into the necessary mode to allow ADB running- tho I do have Easy ADB & Fastboot, I've never been able to get anything to show after Fastboot Devices

Thanks, I did make sure to wipe, format to fat32, copy the MLO first etc. With full powre off. Tried a few times, from what I'm reading here, some Nooks just get finnicky about what cards they'll boot from.

Really appreciate taking the time to respond here, thank you.
[Nook HD, HD+ Android Development] ipdev:
SanDisk 32GB Mobile MicroSDHC Class 4 Flash Memory Card (SDSDQM-032G-B35A)

Is the card I've been using to boot nook ovation (s) for the last 2 - 3 years. I would have to find the instructions I used. I think I got them from the cm device page. I killed a few sd cards before I found out these seem to be very durable.
[Nook HD, HD+ Android Development] neonleon29:
Are you still able to get to your CM 11.0 ROM? If so, I was able to flash the AOSP Marshmallow ROM by first downloading Flashify. After installing Flashify, I downloaded TWRP 2.8.7.5 zip file and unzipped it using 7-Zip. Then you would flash the recovery.img file in Flashify by selecting flash "recovery image". TWRP should now be installed on your device. Then boot into TWRP. Once in TWRP, go to wipe and perform a factory reset. Then go to install and install your ROM and GApps. Do not wipe anything after installing these two files. Reboot your tablet and hopefully you will be running your new ROM.
[Nook HD, HD+ Android Development] ieatabiscuit:
Could not have said it better myself.
[Nook HD, HD+ Android Development] belfastraven:
You might not want to build today! (April 1)

The April 1 joke is kind of obnoxious this year--It puts "MOD" before every text string --I haven't yet found a way to disable this "feature". Probably, you should wait until the April 2 nightlies are available.
[Nook HD, HD+ Android Development] pchc_lx:
man, I wish I had thought of this earlier. i think this would totally sort me out.. unfortunately now Flashify is telling me I don't have root / superuser access. root is turned on for apps + adb in the MM settings, but it must have been lost when playing around with recoveries? I transferred SuperSU over and it can't do it either.

seems like I'm stuck with rooting & installing recovery from scratch w an SD card, yeah? i bought a few older 8GB cards from amazon to try out... hopefully that works. seem to have made this mess myself so now gotta get my way out of it...
[Nook HD, HD+ Android Development] Zippy Dufus:
What's this?

So I've built 04/01 and see this! :laugh:
[Nook HD, HD+ Android Development] neonleon29:
Did you happen to make a nandroid backup of your old CM 11 ROM? If you could go back to CM 11 with root, that is where you should install Flashify and flash the TWRP recovery image.
[Nook HD, HD+ Android Development] belfastraven:
In dev settings, turn root access off, then turn back on. That usually solves the cm root problem.

---------- Post added at 05:27 PM ---------- Previous post was at 05:24 PM ----------

I tried to warn you :) (post 747). If it had just stopped at the optimization, it wouldn't have been so annoying.. :).
[Nook HD, HD+ Android Development] Uldiniad:
Lost WiFi since last build

I want to report that I have lost wifi on my tablet since making a build yesterday night. MAC is 02:00:00:00 (or something like that).

Hoping I'm not the only one and that this will be fixed soon.
[Nook HD, HD+ Android Development] belfastraven:
Hm I built hummingbird this morning and had no problem:

can you try this again? It has always worked for me.

From [MENTION=4473900]amaces[/MENTION] answer when we first reported bug

copy https://github.com/airend/android_device_bn_common/raw/mm-13/prebuilt/bin/toybox to /system/bin/toybox

I found that that exact URL may be off a bit, but I think you can easily find toybox in the mm-13 branch of his android_device_bn_common..
[Nook HD, HD+ Android Development] Uldiniad:
ok thanks [MENTION=5672278]belfastraven[/MENTION]

I'll try doing what you suggest and report back later

---------- Post added at 03:24 PM ---------- Previous post was at 03:07 PM ----------

[MENTION=5672278]belfastraven[/MENTION] when you say copy that to /system/bin/toybox what do you mean? The files don't have a type, should I copy what it downloads anyways?

Nevermind, after installing TWRP 3.0.1 and repo syncing (a bunch of wifi files force updated) I made another build and it solved the issue.

Thanks for the help
[Nook HD, HD+ Android Development] belfastraven:
New CM builds in box device folders & 3.0.1-0 TWRP

Works well on Hummingbird.
[Nook HD, HD+ Android Development] sepehr@teh:
I want to install this ASOP on ovation , which folders file I have to use ?

BR

PS : Any suggestions?