Related
So, anyone come up with a way to block the NC from receiving its firmware updates from B&N? I can see Barnes releasing a update and it just installs itself and wipes out the root we have. I'm sure they cant be happy about all the stuff we are now doing on the nook, but I'm sure they are especially not happy about us being able to install the Kindle app! In my mind, its the best of both worlds, but I'm sure B&N wouldnt see it that way. They could (for all practical purposes), put out a 1.0.1 update that blocked that app and kills our root.
The "default way" of disabling OTA updates on Android might work (make sure your device is not currently updating or something):
Code:
mount -o remount,rw /dev/block/mmcblk0p5 /system
cd /etc/security
mv otacerts.zip otacerts.zip_DISABLED_OTA_UPDATES
Although the key contained in that ZIP file does not look like it's really used (its name is testkey.x509.pem).
Edit: Please disregard my mindless ramblings below (I feel like the noob I am, now). I took a closer look at the code once my mind had emerged from whatever haze had been blocking my deeper thought processes and realized what needed to be done to get it to work (I learned a little more about ADB, which helps). And what's more, I think I did it the right way. *grin* Now, if we knew for sure this would block updates, we'd be set. I suppose we'll find out soon enough.
Thanks for posting the code, Weichel.
weichel said:
The "default way" of disabling OTA updates on Android might work (make sure your device is not currently updating or something):
Code:
mount -o remount,rw /dev/block/mmcblk0p5 /system
cd /etc/security
mv otacerts.zip otacerts.zip_DISABLED_OTA_UPDATES
Although the key contained in that ZIP file does not look like it's really used (its name is testkey.x509.pem).
Click to expand...
Click to collapse
Just to make sure I'm on the right track (noob here), I'd want to do an "adb shell" then run the script above? Also, read-write access for the NC system partition is probably necessary, yes? I haven't enabled rw access yet, didn't want to take any chances of accidentally bricking my NC.
I tried the code above (without going through to proceedure to enable read-write access to the system partition), but it didn't return any messages confirming success or failure.
just looked in that /etc folder and I see install-recovery.sh I wonder what that does.
xboxexpert said:
just looked in that /etc folder and I see install-recovery.sh I wonder what that does.
Click to expand...
Click to collapse
Overwrites corrupted/custom recovery with stock one on boot. At least, that's what it did on the OG Droid.
disregard. wrong post
big.t_03 said:
Edit: Please disregard my mindless ramblings below (I feel like the noob I am, now). I took a closer look at the code once my mind had emerged from whatever haze had been blocking my deeper thought processes and realized what needed to be done to get it to work (I learned a little more about ADB, which helps). And what's more, I think I did it the right way. *grin* Now, if we knew for sure this would block updates, we'd be set. I suppose we'll find out soon enough.
Thanks for posting the code, Weichel.
Just to make sure I'm on the right track (noob here), I'd want to do an "adb shell" then run the script above? Also, read-write access for the NC system partition is probably necessary, yes? I haven't enabled rw access yet, didn't want to take any chances of accidentally bricking my NC.
I tried the code above (without going through to proceedure to enable read-write access to the system partition), but it didn't return any messages confirming success or failure.
Click to expand...
Click to collapse
I don't understand the confusion here. You have a rooted Color Nook. Install Root Explorer and go to /system/etc and click the Mount R/W button and then long press the ocacerts.zip file and rename it. It's that easy.
I have sucessfully rooted my nook and I can load apks from dropbox, installers or via adb so I am a happy camper, all is good....
But I got greedy. The ComicViewer doesn't work well without menu keys so I decided to install softkeys.apk and that is where the trouble started, something is amiss.
I am not an expert here, just a novice, so forgive my patchwork explanation.
Here's what I know and what I did, maybe someone can spot my error?
I can fully access adb.
I remember installing SuperUser and SU using the commands:
# adb shell
# cd /system/bin
# mount -o remount,rw /dev/block/mmcblk0p5 /system
# cat /data/local/su > su
# chmod 6755 su
# ls -l su
And all was fine, SuperUser shows up in the drawer. Then I tried installing SoftKeys and it never showed up or worked.
So I figured I fubared the SuperUser install somehow or have an old version of SU or SuperUser. So I downloaded the most recent versions and went to uninstall the original with uninstall utilities and it's not listed in any of them, so I tried using adb (adb shell ls /data/app) and it's still not in the list.
I even reset the Nook to factory and rooted again with nooter and when I tried to install SuperUser again (downloaded the latest version here on the forum) it said "Install Failed already exists!"
So I cannot uninstall the SuperUser or overwrite it with a newer version, and a factory reset doesn't fix it??
I cannot use any root utilities like SuperUser or z4root, SuperUser has all blank screens and I cannot update it and 4zroot just doesn't seem to do anything but reboot the nook.
Titanium Backup says I don't have root access and other utilities say the same thing,
I can mount system partition as read-write
> adb shell
# mount -o remount rw /system
# exit
That works...
So I tried the commands again to install SuperUser and SU and when I try to install SU
# cd /system/bin
# mount -o remount,rw /dev/block/mmcblk0p5 /system
are OK but when I do:
# cat /data/local/su > su
I get:
Cannot create su: remote access failed
I have also tried a few other things that seem to be available to root users and all come back with write or access errors.
What could I be doing wrong?
Note: I also tried to do a full wipe by using that Power and Volume Down and nothing happens...
Power the nook on and off immediately 8 times until it does a full factory reset. When I've done the Power+VolUp+Nook button reset it doesn't always seem to do a FULL reset. When the nook fails to boot 8 times it does a different reset that takes a good deal longer and (at least in my experience) seems to be the real deal.
z4root will work and install superuser for you.
mhoepfin said:
z4root will work and install superuser for you.
Click to expand...
Click to collapse
I have already mentioned that that did not work, but thanks for the suggestion anyway.
Ok, something VERY weird is going on.
I have reset it to factory twice
Each time I did it by powering on and off 8 times in a row
The first time after it indicated it was updating th software, it went into a stuck at NookColor Logo boot loop again.
The second time I left in the nooter microSD card and it booted properly.
But it booted to a "clean" system with all my programs.
All my settings and data was gone, but all my apks were still installed.
So what exactly did it reset? Just data?
I tried to get it to flash both ways, the quick (power/home/volume) and now twice with the 8 power cycles. Neither reset the Nook entirely.
Am I screwed?
I want to go back to factory to fix this thing
EDIT:
Looks like I am locked out of the system entirely, none of my apps work, some of them come back and say no write access.
I cannot do an app listing like:
adb shell ls /data/app
I get:
opendir failed, Permission denied
I can't do a simple mount
mount -o remount rw /system
I get:
mount: operation not permitted
This should help you with what type of reset you want to do. I think you should do another 8 power on/off reset followed by a power-up-home reset to get it fully reset.
axe2 said:
This should help you with what type of reset you want to do. I think you should do another 8 power on/off reset followed by a power-up-home reset to get it fully reset.
Click to expand...
Click to collapse
I tried that...
Now it's completely dead.
Won't power up at all.
It had plenty of battery life left and plugging it in will not boot it either...
gormly said:
I tried that...
Now it's completely dead.
Won't power up at all.
It had plenty of battery life left and plugging it in will not boot it either...
Click to expand...
Click to collapse
Well that's a bummer! Maybe something went wrong in one of the resets. Did they seem to complete? If it's not a hardware problem you should still be able to revive it via nooter. I would suggest PMing pokey9000 and see if he can walk you through a recovery. You might be the first near brick that requires running some of the recovery commands by hand. I think Pokey9000 knows the most about that.
axe2 said:
Well that's a bummer! Maybe something went wrong in one of the resets. Did they seem to complete? If it's not a hardware problem you should still be able to revive it via nooter. .
Click to expand...
Click to collapse
Yea, but it won't respond to anything, it won't boot meaning no power at all.
It's just completely black screen.
Nothing I do does anything.
gormly said:
Yea, but it won't respond to anything, it won't boot meaning no power at all.
It's just completely black screen.
Nothing I do does anything.
Click to expand...
Click to collapse
Whatever you do make sure the battery is getting charged somehow.. Try to leave it plugged into the wall or in a usb. Does the computer see the device when plugged in? HAve you tried to remove the SD card from the NC while powering up?
norkoastal said:
Whatever you do make sure the battery is getting charged somehow.. Try to leave it plugged into the wall or in a usb. Does the computer see the device when plugged in? HAve you tried to remove the SD card from the NC while powering up?
Click to expand...
Click to collapse
Yep tried all those things...very frustrating afternoon so far
However...I did get it to boot.. here is how:
Press and hold the power button while inserting the USB charger connected to a computer, continue to hold (I think it was 10 seconds or so).
I remember doing this to reset a device a long time ago, not sure what.
But it worked, not only that but I was able to do a pwer/up/home rest and this time it completely wiped the nook. It looks like I am back to factory!
YES!!
Thanks for alll the help and suggestions guys. Hopefully this struggle will help someone else in the future.
gormly said:
But it worked, not only that but I was able to do a pwer/up/home rest and this time it completely wiped the nook. It looks like I am back to factory!
YES!!
Thanks for alll the help and suggestions guys. Hopefully this struggle will help someone else in the future.
Click to expand...
Click to collapse
OK. This time around, do this:
(1) nooter
(2) use ADB to enable Non-Market Apps
(3) use ADB to enable multitouch
(4) Use ADB to push z4root over to the NC
(5) Run z4root and do a full-root (whatever is NOT the "temp" option)
(6) Use ADB to install Astro
(7) Use ADB or Astro to install a market
(8) Install the rest of your apps however you choose.
johnopsec said:
OK. This time around, do this:
(1) nooter
(2) use ADB to enable Non-Market Apps
(3) use ADB to enable multitouch
(4) Use ADB to push z4root over to the NC
(5) Run z4root and do a full-root (whatever is NOT the "temp" option)
(6) Use ADB to install Astro
(7) Use ADB or Astro to install a market
(8) Install the rest of your apps however you choose.
Click to expand...
Click to collapse
I did 1,2,3,6,7,8 and in place of 4/5 I used the most recent version of SU and SuperUser and all is good on my Nook! Not sure what happened before but it must have been a bad version of su or superuser. In any case, all seems fine, only Titanium doesn't work, all the rest of the root requesting apps work fine.
Thanks!
I want to get this hack for my status bar...I attempted with the 2gb Nookie install, and realized that the 8gb was better for my 16gb card (since there's no 16gb version available as of now). The 2gb hack had the status bar buttons, the 8gb one does not.
The version of the hack currently is for versions of Nookie that are flashed to the eMMC (which I have no idea how to do). Brian said something about copying the files, but I can't seem to figure out what to do here...can someone offer some input please? Thanks!
anybody? please help.
no one can help?
piercenkc said:
no one can help?
Click to expand...
Click to collapse
Do you have adb installed? I don't have the adb command now. It is I'm my home computer.
Google nookie froyo. You can install adb. I can post the instruction when I am home.
It seems to be the easiest way for me.
I just got adb installed. Let me know what the command is whenever you get home - I appreciate your help! Thanks!
I have my adb install in c:\tools. Please replace it with whatever your directory is.
Backup your sdcard first - make sure you do this....
Extract the new zip file to a directory. My dir is c:\tools\temp\
adb shell mount -o remount,rw /dev/block/mmcblk1p2 /system
adb push c:\tools\temp\system system/
adb shell mount -o remount,rw /dev/block/mmcblk1p2 /data
adb push c:\tools\temp\data data/
Start Rom Manager->Fix Permissions
Reboot
It works for me. I am sure there are better ways, but this is what I did.
If anyone who know adb commands. Please feel free to provide another suggestion.
awesome, that definitely worked!
i think i liked the bar better up top though...will i have to do that whole process again with a different version of the hack?
I know there are fixes in each update. I would not used the older one unless I know what was changed.
I loaded the 3/22 last night and still had the FCs with stock browser. The 3/23 update works great. Now, just waiting for the reverse colors...
http://forum.xda-developers.com/showthread.php?t=999214
I will check out the new buttons tonight.
I'm sure I have done something stupid and if I can't get this fixed it's not the end of the world. My moboot defaulted to CM7 until I used recovery to flash CM9 nightly. Since then it has defaulted to WebOS. CyanogenMod shows up as the second option in moboot. I have tried the following directions to change the default to CM9 with no luck;
Cyboot to change to "android" - Still defaults to WebOS
Internalz pro on webOS to change moboot.default to "CyanogenMod" (with no quotes, case sensitive, which matches the Ulmage.CyanogenMod). I did this in developer mode on WebOS and saved it- Still defaults to WebOS. I confirmed in root explorer that the moboot.default is changed to "CyanogenMod" no quotes.
Used Terminal in android (can't find the link but followed directions exactly, same idea, changing moboot.default)- Nothing
Wiped everything and flashed CalssicNerd, changed the moboot.default accordingly - No luck.
Wiped everything again, flashed CM9 nightly, again tried cyboot, internalz pro, terminal, root explorer, still no luck. The moboot.default file is definitely changed to "CyanogenMod" no quotes.
Any ideas???????
Wipe clean with webOS doctor and then clean install of CM9
Sent from my cm_tenderloin using Tapatalk 2
That is not the answer I wanted but I thought it was probably going to be necessary
One more noob question, once I have wiped and reinstalled CM9, using Titanium to "restore all apps and system data" shouldn't cause the problem again should it? I'm assuming titanium doesn't mess with the boot folder? Are there things in "system data" that could be causing the problem? I guess either way I will find out shortly!
Thanks
Hey Use adb shell then:
mount -o rw,remount /
mkdir /boot
mount /dev/block/mmcblk0p13 /boot
echo Cyanogenmod > /boot/moboot.default
Should work if it doesn't you'r going to have to clean install i think its mainly because you flashed CM9 over CM7 without Wiping the TouchPad.
No luck with ADB. when I run the mkdir /boot I get "mkdir failed for /boot, File exists"
After running the rest of the commands it makes the new moboot.default file but puts it on the SD card main directory, not in the boot folder overriding the current moboot.default. (which is already CyanogenMod anyway)
Anyway, I'm just going to wipe and do a clean install. Thanks for the suggestions.
Edit: Wiped everything, started from scratch with eyeballers unofficial nightly cm9. It was still going to WebOS so I checked and there was no moboot.default. Created one with root explorer and I'm good to go. Plus I love this rom!!
Thanks again to all the people that help noobs like myself.
Glad that you resolved your problem if u need any help just ask
I wish I'd caught this before you wiped everything. Try adding a blank enter at the end of the moboot.default file - it's what I found fixed the error for me.
The other thing you could've done was booted into WebOS, installed PreWare from your PC, and then installed CyBoot and modified all your boot settings that way - you could set it to default to android, set the timeout to less or more than the default 5 seconds, etc.
ve6ay said:
I wish I'd caught this before you wiped everything. Try adding a blank enter at the end of the moboot.default file - it's what I found fixed the error for me.
The other thing you could've done was booted into WebOS, installed PreWare from your PC, and then installed CyBoot and modified all your boot settings that way - you could set it to default to android, set the timeout to less or more than the default 5 seconds, etc.
Click to expand...
Click to collapse
I think he clearly states that he tried that on his first post
Whoops. Now I see where he said he tried the Cyboot method. My bad. But the blank enter at the end, I'm not sure he said he did or not. And for some reason, it needs that blank CR/LF at the end of the line, else it sometimes (for some people) doesn't work.
It's all good, It was a good excuse to play around with new ROMs and learn some new stuff. Truth is when everything on the touchpad is running just how I want it, I get bored. I like tweaking it more than I like using it
If I ever run into the same problem, or find someone that does, I will pass on your advice of the blank enter. Thanks
I bought a tab S2 about a month ago to replace my HP touchpad i've had/been using since the firesale about 4 yrs ago. At the time of purchase, I discovered really quickly that lack of custom roms on the S2 at that time was to much of an issue, and I returned it.
I am however seeing an alpha of CyanogenMod for the tab S2 that's looking pretty close to usable. Given that the tab is also on sale this week, i'm very much inclined to repurchase it, however, question: Does cifs/smb mounting remote filesystems work with the tab s2 rom that was posted?
You can do that on the stock S2 with many different apps in the Play Store. ie. ES File Explorer, Solid Explorer, AndSMB
nrage23 said:
You can do that on the stock S2 with many different apps in the Play Store. ie. ES File Explorer, Solid Explorer, AndSMB
Click to expand...
Click to collapse
Correct me please if i'm wrong, but those applications just allow me to browse remote filesystems from the application itself. They don't smb mount them. It's the cifs.ko file i'm missing (which i'm assuming is included with cm12?)
The cifs.ko file would have to be done via a kernel module based on what I seen from other devices. I do not know if it is included in CM kernels or not.
Did you or anyone get cifs working?
I understand it may be possible to compile a cifs.ko and insmod it.
I don't know how possible that is but whilst I'm googling how to compile I thought I'd see if anyone had done it.
Cheers, Guy
I got CIFS mount working on my 710 by installing Neked_Nook_MM-710-V1 and my fork of @engine95 mm kernel which has the cifs module enabled.
Hi thanks for the reply
I don't suppose you have any tips or suggested posts/ guides I could use to recreate your setup?
I guess I could figure out how to get neked nook flashed based on the guides but the fork of the engine95 Kernel that includes cifs..? I can see a post about the permissive kernel by engine95..
Is your device fully functional and stable now?
Thanks a lot,
Guy
Neked nook is very stable. My tab s2 has not crashed so far with that rom, and my custom kernel. I have attached my boot image. This is a fork of engine95 kernel with just cifs module added. This kernel only works on MM.
Extract boot.zip and flash boot.img via twrp(boot image) or fastboot.
You can use the attached cifs manager to mount your smb/cifs drives on android as a directory.
I am only able to mount it to /mnt/drive. I could not get it to mount to /sdcard.
Awesome thanks
I use cifsmanager on a Chuwi hi12 that i've rooted, it already has the cifs modules and permissive kernel so I am able to mount the shares almost wherever I like - and I use cifsmanager to poke 1TB of satellite images into the map folder of my mapping app on the SD card. But I don't know if cifs was in the kernel (chuwi is on lollipop) already or part of the rooting process, would love to recreate the setup on my samsung as its a far superior device.
I'll give it a go this weekend, really appreciate you taking the time to upload the files you used.
Cheers,
Guy
Hi Currowth,
I know life is too short to help each noob, but can I trouble you for another pointer?
I used the full image of Neked Nook MM v1, and the boot image you provided, and the tablet is working great, and if I cat /proc/filesystems I can now see cifs listed....but..
I can't mount any cifs shares - to anywhere, including /mnt/drive. I get the mount failed Mount: I/O error.
(I think my process was along the lines of: ODIN to cf-autoroot (i'd actually done this a while before starting this thread so including in case its relevant, as i dont know if there is an issue with a /system or systemless root?) then I ODIN'd TWRP on, took a full backup with TWRP and then wiped data,cache, system etc and flashed Neked Nook on, booted into NNook, then went back to twrp and put the boot image you provided on.
Any help greatly appreciated.
If it means anything I'm not trying to watch Batman in bed, I'm trying to put together a repeatable solution for me and my overland traveller friends so we can take huge amounts of map and satellite image tiles completely offline when we're driving our landrovers, toyotas etc across deserts where sat navs or road maps are useless.
thanks again,
Guy
*Edited to add i've been googling the crap out of the mount i/o error, tried a patched version of cifsmanager, tried copying the apk to the system/apps folder and changing its permissions before reinstalling.. no joy
Looks like it can be a root issue. This is what i flashed to get root. "BETA-SuperSU-v2.74-2-20160519174328"
try to install busybox also and try again.
If that does not work:
Can you try to run this in adb shell as root?
mount -t cifs -o username="username",password="password" //smbpath/dir mnt/cifs/dir
replace "username,"password", and smbpath/dir
Guy009 said:
Hi Currowth,
I know life is too short to help each noob, but can I trouble you for another pointer?
I used the full image of Neked Nook MM v1, and the boot image you provided, and the tablet is working great, and if I cat /proc/filesystems I can now see cifs listed....but..
I can't mount any cifs shares - to anywhere, including /mnt/drive. I get the mount failed Mount: I/O error.
(I think my process was along the lines of: ODIN to cf-autoroot (i'd actually done this a while before starting this thread so including in case its relevant, as i dont know if there is an issue with a /system or systemless root?) then I ODIN'd TWRP on, took a full backup with TWRP and then wiped data,cache, system etc and flashed Neked Nook on, booted into NNook, then went back to twrp and put the boot image you provided on.
Any help greatly appreciated.
If it means anything I'm not trying to watch Batman in bed, I'm trying to put together a repeatable solution for me and my overland traveller friends so we can take huge amounts of map and satellite image tiles completely offline when we're driving our landrovers, toyotas etc across deserts where sat navs or road maps are useless.
thanks again,
Guy
*Edited to add i've been googling the crap out of the mount i/o error, tried a patched version of cifsmanager, tried copying the apk to the system/apps folder and changing its permissions before reinstalling.. no joy
Click to expand...
Click to collapse
Thanks for coming back Currowth,
Ok my SuperSU from the original cf-autoroot was 2.46. I assumed I needed to remove that so I ran the unroot function and then used twrp to flash the version you linked to, after reboot SuperSu is at 2.74.
Unfortunately i have the same I/O error.
I also ran adb root from my win10 machine and tried the manual mount command as you suggested - it returns I/O error also. Initially it said 'no such file or directory' so I manually created the dir, with the name the same as the share dir, in /mnt/cifs.
command output
255|[email protected]:/ # mount -t cifs -o username=admin,password=admin //10.10.10.254/Public1 /mnt/cifs/Public1
mount: No such file or directory
255|[email protected]:/ # cd /mnt/cifs
[email protected]:/mnt/cifs # mkdir Public1
255|[email protected]:/ # mount -t cifs -o username=admin,password=admin //10.10.10.254/Public1 /mnt/cifs/Public1
mount: I/O error
One other thing, in the NNook image thread, i see it says make sure you 'ODIN M' first. I'm embarrassed to say i don't know what that means!
update in mean time: i started again, based on doing all the flashing whilst rooted with the older supersu. So i've unrooted, rooted with your beta_xx linked above, wiped system, cache, data and dalvik, flashed the Neked Nook full MM V1 ROM, booted into that, then back to twrp to flash the boot.img you linked above, installed busybox, the linked cifsmanager, tried to mount, then updated supersu as recommended in NNook thread, rebooted and tried mount again but no joy, always getting i/o error.
just for further info, the shared folder does work on my chuwi with cifsmanager, so hopefully that is not the issue. Before I re-did the ROM and the boot image, i installed paragon ntfs and was able to successfully mount an NTFS formatted SD card into the /mnt/cifs/public1 directory.
interestingly cifsmanager couldn't create the directories under /mnt, but i was able to create them manually and then get an IO error. I changed permissions on the /mnt/cifs folder and now it can create the directory when attempting to mount but still gets IO error.
i'm beyond my depth, guess it feels like cifsmanager is either not working or not got permission - or something i've done prior to the NN and kernel flashes has caused an issue.
Its starting to feel like a lost cause. You know better than me - if this is the end of the easy flash-type fixes to try, perhaps I should just throw in the towel.
Thanks again for your help Currowth, you're a gent
I just did a clean install to replicate you issue, but was not able to reproduce it. 'ODIN M' means that install a marshmallow rom first via ODIN. If you already came from a marshmallow ROM, you can ignore it.
The steps i took to ensure that i am was able to get cifs were the following:
First i installed "Neked_Nook_MM-710-V1.zip"
Next I installed "BETA-SuperSU-v2.74-2-20160519174328.zip"
Last i installed "boot.img"
I did this all through twrp.
Reboot, dont setup knox if it asks you to.
Try to do a wipe, then reinstall the following and try again.
Guy009 said:
Thanks for coming back Currowth,
Ok my SuperSU from the original cf-autoroot was 2.46. I assumed I needed to remove that so I ran the unroot function and then used twrp to flash the version you linked to, after reboot SuperSu is at 2.74.
Unfortunately i have the same I/O error.
I also ran adb root from my win10 machine and tried the manual mount command as you suggested - it returns I/O error also. Initially it said 'no such file or directory' so I manually created the dir, with the name the same as the share dir, in /mnt/cifs.
command output
255|[email protected]:/ # mount -t cifs -o username=admin,password=admin //10.10.10.254/Public1 /mnt/cifs/Public1
mount: No such file or directory
255|[email protected]:/ # cd /mnt/cifs
[email protected]:/mnt/cifs # mkdir Public1
255|[email protected]:/ # mount -t cifs -o username=admin,password=admin //10.10.10.254/Public1 /mnt/cifs/Public1
mount: I/O error
One other thing, in the NNook image thread, i see it says make sure you 'ODIN M' first. I'm embarrassed to say i don't know what that means!
update in mean time: i started again, based on doing all the flashing whilst rooted with the older supersu. So i've unrooted, rooted with your beta_xx linked above, wiped system, cache, data and dalvik, flashed the Neked Nook full MM V1 ROM, booted into that, then back to twrp to flash the boot.img you linked above, installed busybox, the linked cifsmanager, tried to mount, then updated supersu as recommended in NNook thread, rebooted and tried mount again but no joy, always getting i/o error.
just for further info, the shared folder does work on my chuwi with cifsmanager, so hopefully that is not the issue. Before I re-did the ROM and the boot image, i installed paragon ntfs and was able to successfully mount an NTFS formatted SD card into the /mnt/cifs/public1 directory.
interestingly cifsmanager couldn't create the directories under /mnt, but i was able to create them manually and then get an IO error. I changed permissions on the /mnt/cifs folder and now it can create the directory when attempting to mount but still gets IO error.
i'm beyond my depth, guess it feels like cifsmanager is either not working or not got permission - or something i've done prior to the NN and kernel flashes has caused an issue.
Its starting to feel like a lost cause. You know better than me - if this is the end of the easy flash-type fixes to try, perhaps I should just throw in the towel.
Thanks again for your help Currowth, you're a gent
Click to expand...
Click to collapse
Thanks Currowth I will try and give it a go tomorrow
Just a thought, are you booting into Android after each step, or doing all the flashing in one twrp session then doing first boot once all items are flashed?
I flashed them in one session without rebooting.
Hi Currowth, I've had a breakthrough!
I re did the NNook/root/boot image in the order you advised.
I have been using a patriot node WiFi disk enclosure, that works with cifs manager on my other tablet. Today I was working away from the WiFi disk so I made do with a windows pc to provide a shared folder. After setting cifs manager up I was able to mount the share under /mnt, but not to any other location. I got back to my WiFi disk, and that continued to give an io error!? So windows worked but the patriot didn't. Weird. I'd ruled the patriot out as it works on my 5.1 lollipop tab.
So I continued to mess around... I had stumbled across another app called mount manager by Ryan conrad (I don't have the link but I have the apk) which has more noob-friendly options and found if I used the ntlmv2 option I could mount the patriot into /mnt !
I did try to get it to mount to other locations and although it succeeded in the app, the mounted folder was empty.
As my app - Osmand+ has the option to manually specify it data folders I created a 777 permission folder for it under /mnt, and then mounted the patriot containing my satellite images into the appropriate empty tile folder.
Working solution!!! If a little messy.
Thanks so much for your help, the Samsung s2 is about 400% faster and more practical than the other tablet so really happy
I don't know why android devices are so limited by manufacturers when the OS is capable of so much, but that's a different conversation haha
A follow up on this in case it is useful to others...
Using /mnt was a bad idea. /mnt is mounted / built on a system partition as a mount point for other file systems or devices (how I have explained it to myself). So anything you add here as a folder gets destroyed when you reboot.
So, I installed my osmand app to /data/osmand and then used a root terminal to run "chmod -R 777 /data/osmand/" to set permissions to 777 on that folder and all subfolders.
After doing this I was able to get mount manager to mount my cifs share into an empty subfolder in the apps folder tree.
I initially tried changing permissions on /data in case it was needed for folders further down the tree, but it was not needed - which is just as well because again, /data is mounted at boot with 771 permissions, so changes 777 back to 771 after reboot. To change that would involve unpacking the boot image in order to edit the init.rc file and then repacking. I didn't bother it was not required.
If anyone wants mount manager, Google 'ryan conrad mount manager' and take your chance with the apk sites, can't remember whigh site I used!