Related
I found that [email protected]'s ROM had a good idea of adding WaveSecure to the system partition (preventing listing in the My Downloads part of market, and preventing uninstallation through normal means), but his version is slightly out of date now (latest version is 3.0.0.43)
As a result, I set about finding a means to install WaveSecure to ROM myself. Here are my findings for anyone interested in doing the same.
Install the latest version from the market (3.0.0.43 at this time). Now use adb pull to get it off the device onto your pc
Code:
adb pull /data/app/com.wsandroid.apk D:\com.wsandroid.apk
Now open Market back up from the menu, go to My Downloads, and choose Wavesecure Mobile Security Beta and uninstall it for just now (to get it off the data/A2SD location that normal apps are stored in) - thanks, my-space!
Then push the saved apk to the system partition after a remount (to make it read/write)
Code:
adb remount
Code:
adb push D:\com.wsandroid.apk /system/app/com.wsandroid.apk
Then set it all up as usual (will appear in apps list immediately)
and remount system as read only again
Code:
adb remount
And that seems to be it so far. Remember to change the D:\com.wsandroid.apk path to whatever you actually used.
Let me know if anyone finds any problems with this, but I've done it and, fingers crossed, it's worked OK for me.
Obviously, this is only for root users, and there are no guarantees for this.
Couple of questions that might need looked into -
- Do settings carry across after a wipe (as Paul claims Modaco's version does. I've never tried it so can't confirm)
- Is there any disadvantage to using this method? (I guess this is all Modaco's update.zip does, but I don't know)
you forgot to metion to uninstall wavesecure before it is pushed back into system....
my_space said:
you forgot to metion to uninstall wavesecure before it is pushed back into system....
Click to expand...
Click to collapse
Oops! Knew I'd forget something, as I always seem prone to do. Well spotted, and OP corrected.
Thanks
No worries I got a bit confused when i pushed it back onto the phone and was still in my downloads...
I've rooted my phone already but whenever i try to use the command adb remount I get "remount failed: operation not permitted". Suggestions?
I see more and more often, redundant threads.
What How-to will you post next time? How to change backlight settings?
You're pointlessly spamming the board.
I can't say i agree with the 'pointlessly spamming the board' comment, but i would have thought this would at least be better in the applications and themes subforum rather than in development.
Don't forget that an awful lot of android users (and more recently all HTC devices) are more and more 'newbs' and need stuff like this.
While this is good and provides info that people like that need (and myself cos i'm crap at adb and stuff like that so wouldn't have had a clue how to do this previously), maybe the development forum is not the best place for it....
I'm guessing one won't be notified via Market if there's an update available if you push an app to /system/app/, right?
usb0 said:
I'm guessing one won't be notified via Market if there's an update available if you push an app to /system/app/, right?
Click to expand...
Click to collapse
You won't be notified, correct
If anybody doesn't already know, WaveSecure have started hosting update.zip files. This means it's now easy to update your "baked-in" version of WaveSecure without much messing around.
https://www.wavesecure.com/installations/update.zip
Download the file, save it to your SD card, reboot into the recovery console and choose the option to apply an update.zip file.
Voila! Your version of WaveSecure will be updated to the very latest version
DJBenson said:
[...]
Click to expand...
Click to collapse
That's really awesome! Thanks for the tip!
Just a question of curiosity: If I push an app to /system/app/ and then issue the rm-command to remove its apk, won't there be lying a bunch of files associated with the program and with absolutely no function, since the app itself is removed? How do I know the name of these files and where they are located for removal?
I'm a bit confused by that question. My understanding (which may be incorrect but from what I've seen of the "guts of a ROM" appears to be the case) is that the applications reside in the apk files, they are not extracted. If you list the content of any of the app folders (/system/app, /data/app or /data/app-private) then all you get is a bunch of apk files (and some odex files). So when you 'push' an apk to the phone, that application is then "installed", when you rm/remove an application, you do so by removing the apk.
if you remove the apk you have left something in /data/dalvik-cache. wiping the dalvik-cache every now and then helps reclaiming that space, though it is not much.
the app settings and data are stored in /data/data, you could delete the files manually by checking their names (no idea if/what convention the names follow), imho not worth the trouble as it is only a few kb.
odex files aren't created if you don't do in a PITA process manually. don't worry about them, don't touch them, then you're good. odex files are only for system apps.
I bought a used phone and it had WaveSecure already installed. I couldn't find it in the applications list to uninstall, so I did a factory reset on the phone. The application was still there and it still didn't show up in the applications list.
I have the Superuser Permissions application, so someone must have rooted it.
Is there any way to uninstall this?
motomeup said:
I bought a used phone and it had WaveSecure already installed. I couldn't find it in the applications list to uninstall, so I did a factory reset on the phone. The application was still there and it still didn't show up in the applications list.
I have the Superuser Permissions application, so someone must have rooted it.
Is there any way to uninstall this?
Click to expand...
Click to collapse
""Just (re)flash a ROM................""
I just noticed that WaveSecure now points to this post for instructions to install as system application, and I am not sure that the update.zip maintained with them is up-to-date.
However, you can now select to download the .apk directly to your PC thus eliminating the first Market step in this guide.
strife242 said:
I just noticed that WaveSecure now points to this post for instructions to install as system application, and I am not sure that the update.zip maintained with them is up-to-date.
However, you can now select to download the .apk directly to your PC thus eliminating the first Market step in this guide.
Click to expand...
Click to collapse
I believe it is kept up to date, as VillainROM kitchen uses it as a source for the WaveSecure app (fetched each night to keep it up-to-date).
I've certainly never had any problems with it.
Excellent guide Pulser,... I should really reinstall Wavesecure now Im not using a MoDacO Custom ROM. Nice one bruv.
Found this to be helpful.
https://www.wavesecure.com/blog/how-to-make-wavesecure-hard-reset-proof.aspx
I just did a search in the Market fro 'wavesecure' and two things popped up WaveSecure and WaveSecure UninstallProtection Add-on which needs to be uninstalled before WaveSecure and if the add-on is uninstalled it is supposed to lock the phone. (all this is in the description I have yet to try)
I just uploaded tiny noot, a very minimal root tool for the NST glowworm. I think it would probably also work for the simple touch, but I've lent mine out and cannot test it to confirm.
I am basically a cobbler here; many thanks to GabrialD, DeanG and the folks with the minimal touch root tools, which this is based on - and of course to mali100 and the CWR team for getting that on the Touch and Glowworm. Everything below is put together with parts from those projects using what I've learned at XDA and from Dean's nook color repartitioning scripts.
They make it possible for someone like me to knock out a package that's a little more convenient to work from than booting noogie and manually copying in files.
I am using the clockwork recovery zip installation mode for copying in the minimal set of files - I'm not trying to support the google apps or the many interesting screen refresh hacks.
I am not including a modified uRamdisk - the stock uRamdisk supports ADB, and you can get root via adb wireless simply by typing su, so I chose to leave well enough alone.
GabrialD has already released a modified uRamdisk for the glowworm (to support root by default as well as the light) but since stock works for my purposes, I'm not using the modified one.
What it does include:
su and busybox
nook color tools in /system, so that nonmarket apps can be installed
adb wireless
ADW launcher
Amazon appstore, so there's at least once source of "easy" apps
Button Savior
Nook Touch Tools
Supermanager and the Busybox updater interface
The install process is three steps. Four if you decide - and you should - to make a backup of your device before you start. (that process is: make the noogie disk. boot from noogie. connect to your computer. dump the NSTG or NST using dd or another disk imaging tool, and is described in more detail with tips for lots of different operating systems at http://forum.xda-developers.com/showthread.php?t=1142983 That backup will let you restore your entire device to a known working configuration.
Download mali100's nook touch CWR disk discussed in this thread:
http://forum.xda-developers.com/showthread.php?t=1360994
the file itself is here:
http://forum.xda-developers.com/attachment.php?attachmentid=806433&d=1323121269
unzip the file and then write the .img file to an sdcard with your disk imaging tool of choice (dd in linux or win32 disk imager are two I use)
Once you've imaged the SD card, copy in these two zipfiles - leave them zipped:
http://www.mediafire.com/?ig75l5b9c24e7q6
http://www.mediafire.com/?2tfitzt97qqfaw7
Apply 1 of 2, then reboot, then
Apply 2 of 2
then remove your SD card and reboot. Although I have not gotten all the commands to run out of a single zipfile, Zydraka noticed, I think correctly, that you can run first the one and then the second without needing to reboot in between. I have done it that way successfully.
I tried putting all commands (copying the files, then setting permissions) into one file and the rooting process aborted in an ugly way. I ultimately needed to reimage the device to restore the oddly hosed /rom partition. After reimaging I was able to root successfully by running the two clockwork scripts back to back without a reboot.
A (very brief) guide to the CWR interface, for those who don't know it:
You will know your card is made correctly when you put it in your device and power on, and you see a clockwork gear nibbling at a nook N. Be patient while CWR loads; you will get to a screen with selectable menu choices.
Navigate up and down with the righthand buttons; navigate back with the lefthand upper button; choose an item or run a command using the raised n button.
Navigate down to "install zip file from sdcard" and hit N
Hit N again to "Choose Zip File from SDcard"
Navigate down to the first zip (labeled 1 of 2) and hit the n button
navigate to "yes - install"
hit the N button
once the first script is done, use the N button to navigate to and apply zip 2 of 2.
navigate back to the reboot menu using the lefthand side buttons. Once you are at the reboot menu item, you can pull the card, then reboot.
I used a 256 meg sdcard I had in the house for making the CWR disk. I find that to be a very convenient size for these disks - big enough to put a few files onto, not so big I wish I hadn't set it up as a CWR disk.
Thanks roustabout! It works great and it was super easy to do! I just got done installing a bunch of apps from Amazon.
Update: I just posted a tutorial with a video for noobs on my blog.
One thing to note, I didn't do the reboot that you mention in between the 1 and 2 packages and everything worked fine. I just installed 2 right after 1 and haven't had any problems.
Thanks for this, rooted last night everything is as it should be, the only issue I've run into is that I can't seem to install the Kindle app. It's not in the amazon market place, I tried backing up the APK from another device via EStrong and transferring the apk to the microSD, and I get a parsing file error. Any tips?
I have not been able to get Tasker to install yet, either.
One thing which sometimes works where other approaches fail (if you have the .apk file) is to ssh into your device (I use quicksshd) and log in as root, then cd to the directory the APK was copied to and issue the command
pm install blah-blah.apk
I have not yet tried that with Tasker, but it may also help with the Kindle app? I did need to do it for one of the apps I use, although I can't recall which one.
Edit: the 3.1 kindle app Zydraka points out works for me as well.
By default, the Kindle app is pretty unusable, very slow page turns. But by using the gesture-enabled screen refresh hack, it's very useable. (I found that using the no gesture version led to lots of apps just ignoring the hack's presence. I think Renate has a way around that, but I haven't read up on it.)
http://forum.xda-developers.com/showthread.php?p=22800284#post22800284
I got Tasker to install, but needed first to copy in the Maps jar and xml (to framework and permissions respectively) reboot and install via ssh - it might have worked just to reboot.
Since others may want Tasker available, putting the maps.jar and maps.xml files into the tinynooter is trivial, and I'll probably get to it soon.
I found that the older version of the Kindle app works, version 3.1.0.30. There's a donwload for it at Android Freeware. http://www.freewarelovers.com/android/app/kindle
So, after this, will the glowlight work in all apps? I need to make sure that, moon+ reader and EZpdf will glow in the dark, before I purchase the new nook.
thanks.
The glowlight seems to work in all apps. I'm not clear on how exactly it's turned on and off; it might be possible to have an app that uses a long press on the N button for something else, and that might interfere, but so far it works fine in the launcher, in the Kindle reader, in fbreader, in Newsrob (that I know I've tested.) even if you had an app that was doing something funny with that long press, you ought to be able to turn it on from the settings menu that comes up on a short press.
Once the glowlight is on, it seems to stay on until your screen goes to sleep, regardless of what applications you may also be using.
This is part of why I didn't get into the boot environment at all in this approach - I knew from manual rooting that I didn't have to change out uRamdisk so I decided to leave it all alone.
Thanks for tinynoot! It's working well for me, and glowlight behaves normally.
roustabout said:
I just uploaded tiny noot, a very minimal root tool for the NST glowworm. I think it would probably also work for the simple touch, but I've lent mine out and cannot test it to confirm.
I am basically a cobbler here; many thanks to GabrialD, DeanG and the folks with the minimal touch root tools, which this is based on - and of course to mali100 and the CWR team for getting that on the Touch and Glowworm. Everything below is put together with parts from those projects using what I've learned at XDA and from Dean's nook color repartitioning scripts.
They make it possible for someone like me to knock out a package that's a little more convenient to work from than booting noogie and manually copying in files.
I am using the clockwork recovery zip installation mode for copying in the minimal set of files - I'm not trying to support the google apps or the many interesting screen refresh hacks.
I am not including a modified uRamdisk - the stock uRamdisk supports ADB, and you can get root via adb wireless simply by typing su, so I chose to leave well enough alone.
GabrialD has already released a modified uRamdisk for the glowworm (to support root by default as well as the light) but since stock works for my purposes, I'm not using the modified one.
What it does include:
su and busybox
nook color tools in /system, so that nonmarket apps can be installed
adb wireless
ADW launcher
Amazon appstore, so there's at least once source of "easy" apps
Button Savior
Nook Touch Tools
Supermanager and the Busybox updater interface
The install process is three steps. Four if you decide - and you should - to make a backup of your device before you start. (that process is: make the noogie disk. boot from noogie. connect to your computer. dump the NSTG or NST using dd or another disk imaging tool, and is described in more detail with tips for lots of different operating systems at http://forum.xda-developers.com/showthread.php?t=1142983 That backup will let you restore your entire device to a known working configuration.
Download mali100's nook touch CWR disk discussed in this thread:
http://forum.xda-developers.com/showthread.php?t=1360994
the file itself is here:
http://forum.xda-developers.com/attachment.php?attachmentid=806433&d=1323121269
unzip the file and then write the .img file to an sdcard with your disk imaging tool of choice (dd in linux or win32 disk imager are two I use)
Once you've imaged the SD card, copy in these two zipfiles - leave them zipped:
http://www.mediafire.com/?ig75l5b9c24e7q6
http://www.mediafire.com/?2tfitzt97qqfaw7
Apply 1 of 2, then reboot, then
Apply 2 of 2
then remove your SD card and reboot. Although I have not gotten all the commands to run out of a single zipfile, Zydraka noticed, I think correctly, that you can run first the one and then the second without needing to reboot in between. I have done it that way successfully.
I tried putting all commands (copying the files, then setting permissions) into one file and the rooting process aborted in an ugly way. I ultimately needed to reimage the device to restore the oddly hosed /rom partition. After reimaging I was able to root successfully by running the two clockwork scripts back to back without a reboot.
A (very brief) guide to the CWR interface, for those who don't know it:
You will know your card is made correctly when you put it in your device and power on, and you see a clockwork gear nibbling at a nook N. Be patient while CWR loads; you will get to a screen with selectable menu choices.
Navigate up and down with the righthand buttons; navigate back with the lefthand upper button; choose an item or run a command using the raised n button.
Navigate down to "install zip file from sdcard" and hit N
Hit N again to "Choose Zip File from SDcard"
Navigate down to the first zip (labeled 1 of 2) and hit the n button
navigate to "yes - install"
hit the N button
once the first script is done, use the N button to navigate to and apply zip 2 of 2.
navigate back to the reboot menu using the lefthand side buttons. Once you are at the reboot menu item, you can pull the card, then reboot.
I used a 256 meg sdcard I had in the house for making the CWR disk. I find that to be a very convenient size for these disks - big enough to put a few files onto, not so big I wish I hadn't set it up as a CWR disk.
Click to expand...
Click to collapse
You know, it should be nice if before using the packages other people create, for your own project, you asked them for permission to use them, if not, at least create your own scripts.....
Yes I'm refering to me.... thats not cool.
Anyway, the two step process is not necessary here, thats just for preventing some Gapps database corruption, you edited that code away allready and there are no Gapps installed, so add the code to correct the permissions on the first zip, and everything should work fine, no need to rm dalvik either if you arent modifying framework.jar, etc, it should also speed the first boot time.
I apologize - this was intended to be a quick hack and largely for my own use (as I was testing stuff on both my and my girlfriend's glowworms) but I realized there were a lot of folks trying to root their gw's manually. I thought it worked well enough to share.
I didn't intend to present it as original and if I appeared to I apologize.
Say the word and I will yank the thread outright, and I would have no objection to your asking the mods to do so, either.
roustabout said:
I apologize - this was intended to be a quick hack and largely for my own use (as I was testing stuff on both my and my girlfriend's glowworms) but I realized there were a lot of folks trying to root their gw's manually. I thought it worked well enough to share.
I didn't intend to present it as original and if I appeared to I apologize.
Say the word and I will yank the thread outright, and I would have no objection to your asking the mods to do so, either.
Click to expand...
Click to collapse
Don't worry, just stating that before creating a thread with others people work, you should ask them.
Everything is fine, It didn't even pass my mind the idea of reporting it, we are a small niche community, active members must be praised, so dont worry, and I encorage you to keep deving ^^, just that before using other peoples work and starting a thread with it, ask them for permission, no one is gonna deny it and it's the kind way of doing things .
I'm planning to get my hands on a Glow tonight, so over the weekend I should be able to get together a full Nooter for it.
tiny noot - also works for older NST
Just so folks know, I've confirmed that the tinynoot rooter also works on the NST running 1.1.2 firmware.
It will probably work on earlier firmware also, since it is not replacing uRamdisk or framework files.
Are Supermanager and the Busybox Updater supposed to work? Supermanager crashes back to home, and Busybox won't install.
Did you apply both files, and is there an sd card in your device? I just tested the busybox updater and was able to get it to update the installed busybox. It requires that you have an sdcard inserted to work - I remember being puzzled by that the first time I tried using it on a device.
supermanager is crashing. I hadn't tried running it on the device before, and hadn't noticed that.
Looking at logcat, yes, supermanager's crashing in the background quite a bit. It seems to be looking for things which are not available, for instance, a dialer, and erroring out when it can't find them.
roustabout said:
[...] supermanager is crashing. I hadn't tried running it on the device before, and hadn't noticed that.
Click to expand...
Click to collapse
Supermanager has always been a problem, at least for me, using TouchNooter. I believe it's intended to provide file manager capability, particularly for installing APKs on uSD. Once I get Market (Play Store) access, reinstalling supermanager fixes the problem. At that point, I don't need it anymore.
I've always had to work around this when rooting my Touch devices. I'd suggest a basic file manager be provided instead for Day 1.
I'm rooted with tinynoot. Recently I've been experiencing excessive battery drain. I'm eliminating apps I'd installed to if that helps. Wondering if anyone has experience with apps that are problematic in that regard? Dropbox? Amazon Appstore? Facebook? 1Mobile Market? I assume nothing that was provided by default with tinynoot. Thanks.
Hi Glowco,
I'd suggest installing task management apps to get a view of what is actually running (not all processes relate to an installed app icon that you can uninstall). I use Advanced Task Manager to view running apps, and Autorun Manager to control what processes start up at boot time.
Ian
Thanks, I'll keep that in mind. In the meantime, as an experiment I uninstalled several apps including Amazon Appstore, 1Mobile Market, FB, and Wireless ADB. Good result - my battery charge hasn't decreased in an hour and a half. If I decide I miss them I can try adding them back and use your method.
That's good news!
I'd suggest that Wireless ADB is not to blame, since it does not stay resident once it's closed and in any case does nothing until you click the big red button
Of the others, I have Amazon Marketplace installed and I don't experience any battery issues (I'm Glownooted not Tinynooted but don't think that's relevant in this discussion), but I can't speak for the other two apps. If I were paranoid (and I am! ) I would point at Facebook, since it's purpose is marketing and wants to follow your every move
Ian
I am super-curious if & how anyone here is using Link2SD successfully with CM11 (on the Epic 4G, specifically).
I've tried scouring these forums, and the Internet in general, to figure out the best way to get this to work...
But everything that I've tried, it all seems to be working great, only up until the first time that the phone reboots, then it all goes to hell.
I am wondering if there are any extra steps to follow, specifically for the Epic 4G, or any particular pitfalls known to avoid?
That's why I wanted to ask here, specifically to Epic 4G users...
If you are getting Link2SD to work well with CM11, then please chime in here, and can you explain how you got it all set up and working well?
(I feel like this is the one last thing that if I could conquer it, then I could really continue to get a lot of life out of this phone... as it stands, it seems too risky to put much faith in Link2SD, because if the phone happens to spontaneously reboot while I'm out running around, then I'm screwed because so many apps just disappear, and then it's a pain to re-download, re-install, and re-setup each of them...)
Thanks in advance for any help,
AS
I am using Link2SD on my Epic 4G with CM11 with some success. I just did a reboot, and as usual lost any icons that had links created in Link2SD, so I go to the app locker & re-add them to my home screen. This is typical of what happens on a reboot for me. One thing I did notice is that it takes a minute or so for the deleted app icons to show up in the app locker again, so if you are reinstalling them, it may be a matter of waiting for them to show back up. Also on occasion(not this time), Link2SD will prompt me about a problem with the links and then prompt me to reinitiate the partition or something to that affect. Once I do that and it reboots, the app icons are still gone, so I just re-add them. Anyway, I know its not a perfect solution, but with this device its better than running out of RAM. One last thing, needless to say, I only create links for enough apps to free up enough RAM to keep my Epic working properly.
I've finally got a system going that seems to work for me, and so I thought I'd share some things.
I'm on CM11 (as of today, cm-11-20140602-NIGHTLY-epicmtd.zip) and I'm using Link2SD.
HERE'S A "GOTCHA" THAT HAD ME PULLING MY HAIR OUT FOR AT LEAST A DAY OR TWO:
Link2SD was having problems mounting the 2nd partition - it would just say "Mount script cannot be created." or something like that (not a very helpful error message), no matter how many times I rebooted and tried again. What I *finally* figured out (somehow), was that this error was being caused by /system being completely full. When I went and deleted a few things from /system (such as goofy wallpapers or that 'Apollo' app that I never use), then Link2SD was able to successfully create the script, and then I'd reboot and could use the 2nd partition successfully.
It's still a little aggravating that any reboot of the phone will cause all of my "Linked" apps to disappear - I've played with this until I am blue in the face, and have resigned myself to accepting that this is just "how it is" (?) - but I'm now using Titanium Backup as my workaround.
STEPS I TAKE WHEN THE PHONE REBOOTS:
1) Go into Link2Sd and make sure the 2nd partition is usable, otherwise recreate mount scripts (deleting wallpapers/Apollo if necessary)
2) Under Link2SD's "More" menu, perform the following:
a) Clean up the 2nd partition
b) Clean up the dalvik-cache
c) Clear all app caches
3) Restore apps from Titanium Backup
a) starting with Facebook app (the biggest hog) and then immediately go and make Facebook a "Linked" app again
b) restore a few more apps (to internal/phone), then go and shuffle those over to "Linked" apps via Link2SD
c) (repeat step 'b' until all apps are restored and "Linked" via Link2SD
^ This is the only way I've been able to get this to work for me... but now I can put about as many apps on the phone as I'll ever possibly need, and I have to say everything is running pretty smoothly now - but if anyone can see a better way, or how to improve what I'm doing, then I'm all ears... please let me (us) know.
Thanks!
Apex launcher doesn't lose the icons. I can free about 66MB of system space by swapping the launcher, deleting CM wallpapers, live wallpaper and Google keyboard.
I verified link2SD plus was not working properly but free link2SD works as advertised. For me, just installing the plus version will break the working functions of the free version. The free version scripts, links and launcher icons survive reboots. The plus version continually lost mount and wouldn't properly clean up the second partition and was not copying the lib files and placing them in the second partition.
Edit: per the developer's request, after verifying free link2SD was setup and surviving reboots, I added plus link2SD and rebooted: OK so far. Next I linked a file with plus version; OK until reboot. The application was not found except in directories. Dalvik cache cleanup finds the dex link and file in second partition as unneeded files. Had to manually delete all the files and links for the broken application and reinstall it. Also had to uninstall plus link2SD to properly link again. Sent the results back to developer.
Sent from my SPH-D700 using Tapatalk
Edit: 6/20/2014; link2SD 3.4.8 fixed the reboot issue for the link2SD Plus version for me. Sent email to developer to thank him for the fix.
See post #8.
Update on my last entry:
I emailed the link2SD developer and got a reply asking me to check the plus version again. In my reply back I linked him to this thread.
Another tip to add for nightly flashers that use link2SD and modify the zip prior to flashing: pull the mount script, 11link2SD, found at /system/etc/init.d and move it same location on zip before flashing. If retaining data, ie: dirty flashing; the mount securely retains your apps after flashing new nightly. Just checked with free version of link2SD: works.
Sent from my SPH-D700 using Tapatalk
Arson Smith said:
I am super-curious if & how anyone here is using Link2SD successfully with CM11 (on the Epic 4G, specifically).
I've tried scouring these forums, and the Internet in general, to figure out the best way to get this to work...
But everything that I've tried, it all seems to be working great, only up until the first time that the phone reboots, then it all goes to hell.
I am wondering if there are any extra steps to follow, specifically for the Epic 4G, or any particular pitfalls known to avoid?
That's why I wanted to ask here, specifically to Epic 4G users...
If you are getting Link2SD to work well with CM11, then please chime in here, and can you explain how you got it all set up and working well?
(I feel like this is the one last thing that if I could conquer it, then I could really continue to get a lot of life out of this phone... as it stands, it seems too risky to put much faith in Link2SD, because if the phone happens to spontaneously reboot while I'm out running around, then I'm screwed because so many apps just disappear, and then it's a pain to re-download, re-install, and re-setup each of them...)
Thanks in advance for any help,
AS
Click to expand...
Click to collapse
I'm using link2SD for all minus 16gb internal android device. Here is what i do in epic 4g, currently on CM11 20140523, use 20131209 gapps. I just write the part involved link2sd :
1. Buy atleast 16gb microSD and class 10 is a must, make 2nd partition (usually about 4gb - 6gb) as ext2 - ext4 (depends on the OS).
2. Device rooted, install titanium backup & root explorer 3.1.3 (make sure the root explorer working). Uninstall system apk (one of the launcher, whisper push, terminal emulator (I prefer use better terminal emulator, install as user app), CM filemanager, etc - still more that can be uninstalled for more space in system.
3. install link2SD, pick ext2 - ext4 (depends), dont restart yet. go to setting, uncheck everything then restart.
4. After back to launcher, open root explorer, go to root/data/, check app & dalvik-cache folder, press copy. Go to sdext2 folder, delete lost&found folder (usually there), and paste. So the app & dalvik-cache folder is there now (you could copy data/data folder too if you really want maximum extra space in internal, but in epic 4g i didn't copy data folder because it's enough space).
5. At the sdext2 folder, long press app folder, select "link to this folder", go to root/data/, press "create link" - "yes". Then go to sdext2 folder again, long press dalvik-cache folder, select "link to this folder", go to root/data/, press "create link" - "yes". Do the same if you copy data/data folder to sdext2 folder.
6. Reboot. Done. Then installing others app or restore with titanium backup.
I hope this is useful. Some Screenshot attached.
Hello
Thanks for that solution.
I`m searching for this solution since 1-2 weeks.
I had the same Problem on xcover 2 Link2SD.
Now it`s clear i have installt Link2SD and works perfect for just 3-4 days then i upgrade to Link2SD plus and then it happend like the Threat above.
I`m wondering that Lin2SD works perfectly on CM11 and if you go to Link2SD plus for money and this don`t work.
Free works perfectly and paid work not.
I have go back and everything its fine.
I hope the autor will fix the problem then i go back to plus.
Thank Thanks Thanks works fine!
regards marle.m
Good news! It appears the link2SD version 3.4.8 released today has a bug fix to survive reboots for linked apps when linking with link2SD plus version.
So far, I've only linked one app with plus version enabled and it survived one reboot. Then Ⓘ linked the data folder and rebooted again which also survived the reboot.
Looks like plus version is fully functional; I'll update if it fails some time later.
Sent from my SPH-D700 using Tapatalk
Finally had a chance to sit down and mess with this...
Yeah! Success! Freeing up space in /system worked.
Next question...Will I have to remove the bloat prior to flashing from now on? ie no more CyanDelta easy flashing
Anyone have any Scripting-Fu to come up with an automated method of stripping out said bloat?
thx sno
Snoshrk said:
Finally had a chance to sit down and mess with this...
Yeah! Success! Freeing up space in /system worked.
Next question...Will I have to remove the bloat prior to flashing from now on? ie no more CyanDelta easy flashing
Anyone have any Scripting-Fu to come up with an automated method of stripping out said bloat?
thx sno
Click to expand...
Click to collapse
I was thinking the gapps could be modified at the updater-script to remove some system bloat. Then remove some bloat from that as well. Most remove their own bloat choices so maybe a diy tut would be more useful?
I agree, the script would make the nightly flashing easier.
Sent from my SPH-D700 using Tapatalk
Just realized that if using Link2SD Plus to multi link all folders of an app to sdext2 after a clean install is still broken, if using intended method. Apps linked this way are missing after reboot.
Working on a safer suggested method that focuses more on removing apps from Gapps but also removing some other system apps after flashing a nightly that requires no modification of the nightly zip on a computer. Have to focus on linking only a minimum amount of apps with free Link2SD considered less risky to move, like larger stand alone apps, not needed tools.
I've got a working script and method that works but the risks to be avoided need to be detailed along with the tut to script and tool your own modified Gapps that minimizes the flash to flashing the nightly as-is and then flashing a custom Gapps that includes preferred launcher and restore methods.
Removing CMWallpapers, Apollo music and Trebuchet launcher. Substituting blacked out Google play. Replacing removed apps with Apex beta test launcher for test group, blacked out Pandora (these will be installed at /data partition where they can be easily uninstalled or updated) I use my own borrowed wallpaper.
Along with the removed bloat from Gapps, this frees a bit more than 40 MB of system space.
Sent from my SPH-D700 using Tapatalk
UPDATE: the latest version of Link2SD (3.5.2) has "fixed the bug that causes linked apps disappear on reboot when internal data is linked".
So... if you've also ponied up the buck or two for Link2SD Plus (as I have), then this finally works again like you'd always hoped it would.
I just loaded a bazillion apps back on the phone, and have been able to reboot multiple times without losing them.
The only time I "lost" them for a moment was after flashing to the latest CM11 nightly, but then doing the "Recreate mount scripts" and reboot brought them right back, with no other shenanigans necessary.
(Just wanted to let people know, because this is such a relief to me now....)
HURRAY!
OK I'm trying this again. Reboots are fine as long as I don't select quick or soft reboots; I lose mount, linked apps not installed.
Now need to try the clean install of nightly.
Snoshrk said:
Finally had a chance to sit down and mess with this...
Yeah! Success! Freeing up space in /system worked.
Next question...Will I have to remove the bloat prior to flashing from now on? ie no more CyanDelta easy flashing
Anyone have any Scripting-Fu to come up with an automated method of stripping out said bloat?
thx sno
Click to expand...
Click to collapse
One possible solution:
more scripts to limit steps
Another possible solution (click link)
Here is my issue I cannot create folders or delete anything on the internal sdcard.
Background info: I just got this gs3 its on boost mobile. I am on NJ3 I used CF-auto-root method to get root. Everything went fine updated Supersu installed a bunch of apps including Titanium Backup and made backups of all apps on the phone. Everything finished fine. I have not deleted any apps yet nor have I installed a custom record very or any ROMs its still!l stock. I have a 64gb sdcard installed which is new and empty so I wanted to put my backups on it but could not. While looking for a fix I noticed that even the default INTERNAL sdcard had a red folder on top with "cannot write to this location" . so now I cannot use TB. It gives an "insufficient storage" message and fails
I then went to ES File Explorer and tried to make a folder on the internal card and could not, also tried to delete and could not !! I have Googled this problem and come up with a number of solutions but most are very old threads. Can anyone give me some help fixing this? The phone seems to otherwise work but I fear it will only get worse with time.
edit I can install apps though even now.
Oh I left out that I did recieve an update for Security policy update. Which I understand has something to do with SElinux. I also found a fix for what appears to be my problem related to this it is;
SU
restorecon -FR /data/media/0
I decided to try it but get a message that -F is invalid
syntax is restorecon (--nRrv-- )
From what I can google the version of restorecon I have on my phone does not include that switch!!! Just my luck, can anyone help me figure out if I can change the binary to an updated one so I can use this?
Well I am disappointed 45 views and not one reply, oh well.
I eventually bit the bullet and did a factory reset from the settings menu, it cleared up the issue and I still had root!! Google reinstalled all my apps and SuperSu disabled Knox for me. I also unchecked auto update for security updates so that Samsung does not send another one to me without my knowledge. also disabled autoupdate for Samsung apps.
know everything is golden again.
I successfully rooted my Samsung Galaxy A320FL following more or less this guide (I know, it's a video and that's annoying, but it's also very clear. And there is a text version linked in description), with some modifications though.
I will write here what differs / is not specified in that guide.
I also attach all the files I used; they can also be found on the internet with some search.
Make sure to have installed on your PC Samsung USB driver for mobile phones, available on Samsung website.
I used different versions of the files needed (that guide is for Samsung 8). With the following files, everything worked well:
twrp-3.4.0-0-a3y17lte.img.tar
no-verity-opt-encrypt-6.0.zip
RMM_Bypass_v3_corsicanu.zip (learned this from another guide on this forum)
Magisk-v20.4.zip
Once TWRP is installed, the guide instructs you to install no-verity, then reboot to recovery and immediately after that reboot to system; only later, transfer and install magisk. THIS MESSED UP everything, in my case at least.
The solution was even faster: once TWRP is installed
plug USB and transfer all needed files (listed above) at once
install no-verity and reboot to recovery;
install RMM_bypass and reboot to recovery;
install magisk and reboot to recovery
reboot to system
Now you proceed following the rest of the guide.
After rooting, you may want to fix a few problems you may encounter: see next post.
HOW TO FIX FINGERPRINT AFTER ROOT
When your Galaxy A3 is rooted, unfortunately fingerprint will not work properly to log in on your apps (but it will work to unlock your phone). To fix this:
install from Google Play a file manager (like Solid Explorer)
in the left menu select ROOT folder, then rename
/system/priv-app/SamsungPass_1.3/SamsungPass_1.3.apk
to
/system/priv-app/SamsungPass_1.3/SamsungPass_1.3.apj
remove /data/app/com.samsung.android.samsungpass-1
reboot
This will remove SamsungPass. You will not be able to use SamsungPass anymore on your rooted phone, so forget the ability of saving passwords on websites and confirm them with fingerprint (you can still save passwords in browser or use google autofill; you just can't confirm them with fingerprint).
But, with the method above, at least you will be able to use fingerprint to log in those apps which natively support fingerprint login (like banking apps).
HOW TO MAKE BANKING APPS WORK ON A ROOTED PHONE
...Banking apps, though, tend to stop working when they detect a rooted phone. You can try to fix this using Magisk Hide feature.
Open Magisk and tap on the shield icon
Tap MagiskHide
Check your bank apps and any other app that want to prevent from detecting root. (According to the guides I read, hiding too many apps can be a problem: stick to what is really needed).
HOW TO MOVE WHATSAPP MEDIA FOLDER TO SD CARD
This was the main reason why I decided to root my phone: I was running out of storage. So I bought a high-quality and fast sd card (yes, it deserves your 20 €) and did the following:
Download "Apps2SD" (the original by Vicky Bonick; it's free) and follow instructions on how to create partitions.
You can create upto 3 partitions: 1st fat32/exfat/f2fs/ext4/ext3/ext2 (it's your SD card), 2nd ext2/ext3/ext4/f2fs (it is used to link the apps), 3rd swap partition (it's optional).
IMPORTANT: With Apps2SD you can LINK apps (they will end up in 2nd partition) or use FOLDER MOUNT (the chosen folder will end up in 1st partition, the one that looks like your normal SD card).
Please note that for Whatsapp media folder you will use FOLDER MOUNT method: so it will end up in the 1st partition. Create the 1st partition large enough for your whatsapp media.
Use "folder mount (app analyzer)" feature: it's like folder mount, but it's pre-set for some common apps, including Whatsapp. With this feature, you can successfully move Whatsapp media folder to SD, in one clic.
To understand what folder mount means: see FAQ.
In my case everything worked fine. When I reboot I have to re-mount folder, but it takes one second (just open Apps2SD, tap Folder Mount, slide "whatsapp other").
By the way, with App2SD you can do much more: you can move virtually any app to your SD card using the "Link apps to SD card" feature, as explained in Vicky's video.
...Hope this will save you some time!
airali said:
I successfully rooted my Samsung Galaxy A320FL following more or less this guide (I know, it's a video and that's annoying, but it's also very clear. And there is a text version linked in description), with some modifications though.
I will write here what differs / is not specified in that guide.
I also attach all the files I used; they can also be found on the internet with some search.
(...)
Click to expand...
Click to collapse
Thank you! I successfully used your compilation for a T-Mobile branded unit, all works after some tinkering. I didn't have the fingerprint problem, possibly the Samsung security thing is not the same on the carrier-modified ROM.
I had problems first making root work because of the succession of operations - basically, everything needs to be formatted in TWRP so it can mount partitions. Once I boot up the ROM, TWRP won't mount anymore → every zip you want to install, you need to do in one go before you reboot to Android.
I tried to root mine, but it didn't show up in odin, it did show up in device manager but I can't do anything with it, no transfering files via usb, etc.
The drivers are installed, I reinstalled them a couple of times, tried a different USB port, etc...
No sucess so far, I hope someone here can help me
Tap tap tap