Related
trying to install the DSPmanager apk i got here.
i've tried in ADB, and it gives an invalid install location error, tried in OI file manager and it gives me a big, happy green arrow and says "application not installed"
running GinSense 0.9
any help would be appreciated.
(sorry if this is the wrong thread)
(and i did search and will continue to do so until/unless i hear back)
EDIT to say - also tried app installer - same happy arrow and not installed as OI manager.
Most likely on your default install location there is no more space left to install the application. You can try to modify that by
Code:
adb shell pm setInstallLocation 2
from your PC having connected your phone in debugging mode.
The different locations are described in more details in this post.
i managed to get it installed with
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cp /sdcard/DSPManager.apk /system/app
i don't understand why neither of my app installers were doing this, but i'm new to this, so maybe i'm missing something. that link looks like some useful info, though. thanks!
Ok, in that way you installed DSPManager on your /system partition. Generally this is read only and there is no space left. Applications normally will be installed on /data, /sdcard or (if supported by to ROM) on /sd-ext.
AndDiSa said:
Ok, in that way you installed DSPManager on your /system partition. Generally this is read only and there is no space left. Applications normally will be installed on /data, /sdcard or (if supported by to ROM) on /sd-ext.
Click to expand...
Click to collapse
i'm running ginsense with S2E, so i assume normally would be on sd-ext.
i tried both using the install feature and just manually placing the .apk in /sd-ext to no avail. i also tried placing it in /data with no luck.
what are the practical differences with putting it in /system? FWIW, it's running fine with it there (both the rom and the app)
i don't know if it makes a difference, but the app is DSP manager
i removed it from /system/app then used ADB shell. i *think* i figured out what i was doing wrong, the command line wanted me to specify an install location, which i wasn't doing. is this a "cleaner" install method?
Code:
adb shell
install /sdcard/DSPManager.apk /sd-ext/app
app shows up in the launcher again.
Typically just doing an
adb install /locationofapkonyourcomputer
Click to expand...
Click to collapse
will do the trick. You don't need to copy the .apk onto your phone just to install it.
As mentioned previously, it may be that your default install location is NOT set to /sd-ext/app and that /data is full.
Hello guys, please help me out with this problem! I've been working on all day but my phone is still bad...
When I rooted my device BusyBox was supposedly installed by the toolkit I used to root (mskip's).
Then I installed BusyBox installer market app (Stericson's) and it said "BusyBox location could not be found". I thought it wasn't installed so I used the "smart install" with the default values, so it was installed to /system/bin and all the applets were listed as symlinked to /system/bin/busybox
After a while I realized that it was installed both in /system/xbin (by the root toolkit) and in /system/bin (by busybox installer). I used the uninstall option from the busybox installer app to remove it from /system/bin again and leave just one installation to avoid conflicts. This was not a good idea it seems. After uninstalling and rebooting, the phone started to work incorrectly, wifi doesn't work.. and most importantly, USB connection is dead with Android fully booted. the battery charges but the PC doesn't detect it. (It works on Recovery mode though).
I have an idea of what may be wrong. I think the "BusyBox installer" changed all the symlinks to system/bin/busybox, so when it was uninstalled, the phone was left without any of the applets of busybox even though the file /system/xbin/busybox is still present.
Or maybe I'm not really rooted anymore? However, the su binary is still present in /system/xbin/su but I still can't get to work commands like "mount".
How can I fix this problem? I will greatly appreciate any suggestions.
I think it might be fixed by installing busybox to /system/bin or even just copying the /system/xbin/busybox file to /system/xbin/busybox but because the phone is not working correctly I haven't been able to do that...
Here's the information I've gathered so far for you guys to PLEASE help me out with this:
SuperSU is installed and seems to works fine.
"BusyBox Free" installer app doesn't work. If I open it, it shows only black with the three buttons in the bottom but they can't be "clicked. It has been granted root permissions.
"ES File Explorer" gets root permissions but is unable to mount /system as writable (to copy the file).
In a terminal emulator application (Jack Palevich's), this is what I get:
Code:
$ which busybox
/system/xbin/busybox
$ ls
ls: not found
$ busybox ls
(works, outputs the directory content correctly)
$ mount -o remount,rw /system
mount: not found
$ busybox mount -o remount,rw /system
mount: permission denied (are you root?)
$ su
(the terminal emulator app has root permission, but when issuing "su" command, the cursor stays inactive for several minutes and when it finally responds, the following operations are still not succesful. The "su" doesn't seem to work.
$ busybox mount -o remount,rw /system
mount: permission denied (are you root?)
$ /system/bin/busybox --install -s /system/bin
busybox: /system/bin/zcat: Read-only file system
busybox: /system/bin/mountpoint: Read-only file system
busybox: /system/bin/nohup: Read-only file system
My plan is to make the USB work so I can use the toolkit again to restore a stock firmware and clean this mess. Oh, I have stock recovery and stock boot image if that's of any help to know it.
How can I issue the commands I need? or fix this problem?
I have basic linux experience so if you need the output of any command please let me know.
Any help is appreciated. Thank you!
... i think that flashing cwm recovery(.tar.md5) with odin and flashing a root+busybox.zip with cwm recovery should be the fastes way to fix this .... only thing is that it erease your "costum binary count" but with the "Triangel Away" app you can reset that counter ...
Thank you for the hint, enox. I'm will try to install the custom recovery now.
Thanks again enox for pointing me in the right direction. The phone is working again. I'm sharing what I did in case it helps someone in the future:
1) Installed the custom recovery 'twrp', provided by the toolkit (program_folder/recovery/recovery-twrp-2.4.3.0-GTI8190.tar) using odin with the phone in download mode.
2) Flashed this busybox uninstaller using twrp recovery. The phone wasn't working fine yet, so I continued to the following step.
3) Flashed a root+busybox.zip provided by the toolkit (program_folder/root/SuperSU-1.25-Busybox-RenameRecoveryRestore.zip) using twrp recovery.
At this point, the phone was working fine but to be sure that all symlinks were correct, I ran an additional cleaning script which you can find at the end of this post, along with my comments talking to myself while I was troubleshooting the problem.
I'll go to sleep now. Thank you.
Got a PM and I thought it would be better if I reply to it in the forum so others can benefit as well:
andr0id_n00b said:
hey i saw your problem here http://forum.xda-developers.com/showthread.php?t=2233942 and iam glad u solved your problem
can you please tell me what toolkit do you use ??
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
mskip's toolkit for Samsung Galaxy S3 Mini:
http://forum.xda-developers.com/showthread.php?t=2185700
Big thanks to him too, for providing that noob friendly yet full-featured toolkit
same with xperia mti27i
ive exactlly made the same but with my xperia mt27i android4.0 ics i dont i know what to do i dont have exp. with android so please help
Hi all,
I have SuperSU Pro 2.46 installed on a lifetab P8912.
Everything worked and I got checked with rootchecker that everything works fine.
Xmodgames also starts with the message that it has root permissions granted.
The ClashofClans mod has a problem: "Mod start fails. Please confirm XModgames is authorized with root permission".
What can I do ? Does anybody else encounter the same problem or fixed that already ?
THANKS a lot for your help,
Alecz
alecz2012 said:
The ClashofClans mod has a problem: "Mod start fails. Please confirm XModgames is authorized with root permission".
Click to expand...
Click to collapse
This should be brought to the attention of the developer of "ClashofClans" -- it might be looking for 'su' at a hard-coded path. You could test for this (and perhaps even fix the problem for you) by copying or linking '/system/xbin/su' to other common paths -- such as '/system/bin/su'.
At a terminal enter:
which su
It should reply '/system/xbin/su'.
Frank
hmm, thanks , but perhaps I didn't find the right shell to work with:
I do not have write access to that folder /system/bin
Shall I chmod 777 to that folder, at least temporary ?
Sorry for not having worked since a long time on linux..
alecz2012 said:
I do not have write access to that folder /system/bin
Click to expand...
Click to collapse
That partition is normally mounted for reading only, not for writing. Remount it as writable, copy the file, then remount as read-only again:
mount -o remount,rw /system
cp /system/xbin/su /system/bin
mount -o remount,ro /system
The SuperSU installation script will delete that copy when you flash the update again so it isn't permanent, and there is only a small chance that this is the problem.
Frank
Hi Frank,
your mount description worked fine, but still I get the error when starting the mod from xmodgames.....
Perhaps you got another tip or trick .....
THX
Alex
Frank Westlake said:
That partition is normally mounted for reading only, not for writing. Remount it as writable, copy the file, then remount as read-only again:
mount -o remount,rw /system
cp /system/xbin/su /system/bin
mount -o remount,ro /system
The SuperSU installation script will delete that copy when you flash the update again so it isn't permanent, and there is only a small chance that this is the problem.
Frank
Click to expand...
Click to collapse
alecz2012 said:
Perhaps you got another tip or trick .
Click to expand...
Click to collapse
In a terminal, run
logcat -c
Then run the application which is failing to get root; then immediately after it fails run
logcat -d > /sdcard/dump.txt
Then examine '/sdcard/dump.txt' to see if it contains an error message which might help.
Frank
Hi Frank,
done, but in the txt file it is a bunch of - at least for me - magic !
I can find lotz of krsdk stuff, looks like a former try of kingroot is still existant and might prevent something there, or perhaps that's because xmodgames is checking for kingroot ...
Really do not know .....
Anyway,
I think I am getting closer , but still the last mile to take
Frank Westlake said:
In a terminal, run
logcat -c
Then run the application which is failing to get root; then immediately after it fails run
logcat -d > /sdcard/dump.txt
Then examine '/sdcard/dump.txt' to see if it contains an error message which might help.
Frank
Click to expand...
Click to collapse
alecz2012 said:
...looks like a former try of kingroot is still existant and might prevent something there, or perhaps that's because xmodgames is checking for kingroot ...
Click to expand...
Click to collapse
That's a very reasonable guess. I assume that you rooted with Kingo Root then replaced that with SuperSU. Maybe Kingo Root is still active on your device. Maybe SuperSU did not install and the root checker found Kingo's 'su'. Take a good look at both installations and try to figure out what is there. Does the SuperSU Android application run? See if 'su' will tell you whose it is by running
su --version
Frank
Kingroot didn't work when I tried it, therefore I went through the SuperSU installation.
su --version gives me
"2.45:SUPERSU"
Best regards,
Alex
Frank Westlake said:
That's a very reasonable guess. I assume that you rooted with Kingo Root then replaced that with SuperSU. Maybe Kingo Root is still active on your device. Maybe SuperSU did not install and the root checker found Kingo's 'su'. Take a good look at both installations and try to figure out what is there. Does the SuperSU Android application run? See if 'su' will tell you whose it is by running
su --version
Frank
Click to expand...
Click to collapse
I can't see what's happening from here but the cause could very well be the incomplete KingRoot attempt. It might be that your solution is to revert to stock to remove that Kingo stuff then root again using the procedure that succeeded.
Frank
i have same problem as OP, i have moto e stock 5.0.2 rooted with supersu can anyone help me
demoakka said:
i have same problem as OP, i have moto e stock 5.0.2 rooted with supersu can anyone help me
Click to expand...
Click to collapse
Same problem with me also i really need the mod working, few other apps like freedom is working but gltools arent working
The ClashofClans mod has a problem: "Mod start fails. Please confirm XModgames is authorized with root permission".
same problem with me also..
xmodgames needs to be updated, not SuperSU.
Some problem for me with Xmod for Boom Beach. Before i updated to Android 5.0.1 it was working.
Edit: Had an old Xmod version which i installed from titanium backup. New Xmod Version fixed the problem for me.
i have this problems but i have runned root please help me
~
i have Samsung Tab 10.5 (SN-T805) .. and it has the same issue
me and one of my expert friends analyzed the application to see what is the problem, we found out that XMODGAMES doesn't check the root properly
So, if there was an expert person that can reverse engineer the application and fix this issue, that would be great
PS: we don't have time to do it, because of our final college exams, we might do it in the summer.
~
alecz2012 said:
Hi all,
I have SuperSU Pro 2.46 installed on a lifetab P8912.
Everything worked and I got checked with rootchecker that everything works fine.
Xmodgames also starts with the message that it has root permissions granted.
The ClashofClans mod has a problem: "Mod start fails. Please confirm XModgames is authorized with root permission".
What can I do ? Does anybody else encounter the same problem or fixed that already ?
THANKS a lot for your help,
Alecz
Click to expand...
Click to collapse
make ur device language tu english
My xmodgames can't work either?have you found a way to fix it?
Here is the solution How to run Xmod games in android lollipop
Hey all
I'm having some trouble getting r/w access back on system on my 5803 on .726 firmware.
I have root and working recovery, just no r/w on system. Every time I check system access in terminal it sits at "ro" and not "rw"
I had full access in Kitkat, but when I flashed Lollipop I seemed to have lost r/w access. I have tried updating my recovery, RICDefeat, and byeselinux, all to no avail.
I feel like I'm busy missing something completely obvious, but I can't for the life of me figure out where I'm going wrong. Can any of you fine souls help?
Can you enable r/w acces using adb?
Open command line window, type adb shell (with device connected in debugging mode), then su, then mount -o remount,rw /system.
Don't know if this works for Lollipop, but I do see other users struggling to get full r/w permissions with the latest LP firmware.
Cheers.
chris5s said:
Can you enable r/w acces using adb?
Open command line window, type adb shell (with device connected in debugging mode), then su, then mount -o remount,rw /system.
Don't know if this works for Lollipop, but I do see other users struggling to get full r/w permissions with the latest LP firmware.
Cheers.
Click to expand...
Click to collapse
It seems that I can enable that way, but it doesn't persist after a reboot. And mounting system in recovery doesn't seem to do anything either. If I try run certain things in recovery it seems like they don't really work. I can change recoveries and ROM, but things like debloating scripts don't seem to work. It's quite strange.
Can you use Script Manager from Play Store to run a script at boot to enable root access? Not the best solution but may work?
Peace
chris5s said:
Can you use Script Manager from Play Store to run a script at boot to enable root access? Not the best solution but may work?
Peace
Click to expand...
Click to collapse
I suppose I could, but that's not gonna solve my problem with flashing things in recovery
Still struggling with this :/
Download this file, run .bat and ready. No need to restart.
https://mega.co.nz/#!tcEDFD4I!hrpQZxmq2Af8BFUS-ciCYBGVpEJ1LvVn_nLb2SYqAWc
pedro5148 said:
Download this file, run .bat and ready. No need to restart.
https://mega.co.nz/#!tcEDFD4I!hrpQZxmq2Af8BFUS-ciCYBGVpEJ1LvVn_nLb2SYqAWc
Click to expand...
Click to collapse
Thanks for the suggestion, but it doesn't work.
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!