Develop Bugs

[HOWTO] Install Latest WaveSecure in ROM

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)

Wow.

Hi all,
I have been a winmob user for over 5 years and i know pretty much everything about them. (see join date) Though 3 days ago i got a a8183 desire.
My god i have a lot to learn about Android. Winmob seemed so much simplier to pick apart with registry and custom roms.
Anyways i have been reading thread after thread for days yet i still have a couple of questions that i cannot get clear answers for.
I have a a8183 telstra desire running on optus. I have updated to the latest offical 2.2 ROM. (Everyone mentions OTA (over the air) though i downloaded it and installed thru windows).
So i would appreciate if someone could help me out with my questions/assumptions.
1. From what i have read you cannot r00t a froyo OS. Is that right? Though i have found an app z4root that will do it temporarily until reboot. Unrevoked doesnt seem to work.
2. To change system files you need not only root though you need the clockworkmod recovery part of the bootloader. (eg. to replace HOST file for adblocking).
3. You need permanent r00t to install the clockworkmod (so i cannot do this).
4. You cannot remove default ROM apps from your phone without the clockworkmod.
5. You need clockworkmod to install custom ROMs.
So from what i gather.. r00t is good. though really only cause it gets you the clockworkmod recovery which is where you can really hack it.
And to get this i need to downgrade to 2.1, r00t, clockwork then use a hacked rom for 2.2?
Your help is greatly appreciated.

hi sage, i too came from windows mobile so i know how you feel, lucky for me i jumped on the android bandwagon earlier with the htc hero, after i got bored with my HD1, anyway your wrong on quite a few points, so i'll point you in the right direction.
1) the latest version of unrevoked (www.unrevoked.com/recovery) is more than able to root the froyo roms, its a one click app and can root your device in minutes
2) to easly modify system files you need s-off (this is equivalent to HSPL on wm devices) after you have rooted, you need to search for alpharev, this is a linux live cd, you just burn it and boot it and it will security unlock your device.
3) when you download and run unrevoked, it will not only root your device but insatall the latest version of clockworkmod recovery. (just hold vol down and power when your device is off to access hboot, and choose recovery from the list) so unrevoked kills 2 birds with one stone
4) to remove the apps in the /system/ partition there are 2 ways, from recovery using adb, or if you flash the s-off mod, you can remove them directly from your device using a file manager.
5) yes you need clockworkmod or another custom recovery to install custom roms, but now you know how to do it, thats not a problem

Hi Sage,
If you're looking for an easier way to get rid of all the Telstra apps (more like a blob of links really ) on your phone you may want to try one of the stock HTC WWE ROMs. It's clean and you can flash it via exe, just like in WM. The latest RUU I believe is the 2.29.405.2. Also, be aware of the risks of rooting your phone.

thanks for your response guys
Ok so i am now r00ted and running Leedroid's WWE ROM! (thank you!) it was actually pretty easy.
I think unrevoked was failing cause i was using a USB HUB.
OK so now i just want to remove some more of the default apps that come with it.
So i will try alpharev to security unlock my device. (is this permanent or if i reflash my rom it will come back?)
once i have done this i can then delete anything i like thru r00t explorer?
At this stage i am trying to just make some more room for apps. As a number of them wont move to SD Card.
A couple of last questions if i may. I have an new SD Card on order. Am i able to simply copy everything from my existing SD to my new and then swap it over in my phone and it will all be ok? Or do i need 'clone' it with some tool?
Where in the system paths do i remove 'shortcuts' within all apps? (or even simply rename them.)
Much appreciate your help. Android is growing on me. I especially love adb logcat!

ok.. i am now security off'd alpharev worked a treat.
i am now using r00t explorer to try and delete items from /system/app though they come up read-only so i cannot delete them
i take when i get to remove these the phone will have more stoage space for apps yeah?
i also still cannot find where the all apps shortcuts sit! (so i can rename/remove).
and lastly now i have the alpharev bootloader so gonna google how to change that
i did use the Leedroid apps2sd ROM. though most of my apps are still going to phone memory and i cant move them across.
Is there a fix for this? i guess once i work out how to delete these read-only files ill be ok anyway.

Unfortunately removing system apps wont give you more space to install apps, they are stored under a different partition, /system and /data are not on the same disk so you can save as much space on /system as you want but it won't affect /data at all.
With running out of space you have a few choices:
Go to settings..applications..then manage and move as many apps to SD as you can. This is fro-yo apps2sd, not all data is moved and not all apps can be moved, so you will probably run out of space again anyway.
Or
Reboot into recovery and partition your sdcard to create an ext partition, when you boot your rom ALL apps will be moved to the ext partition leaving lots of free space. Backup your sdcard before you partition it, you will lose all data.

Sage said:
ok.. i am now security off'd alpharev worked a treat.
1) i am now using r00t explorer to try and delete items from /system/app though they come up read-only so i cannot delete them
2) i take when i get to remove these the phone will have more stoage space for apps yeah?
3) i also still cannot find where the all apps shortcuts sit! (so i can rename/remove).
Click to expand...
Click to collapse
1) Press on Remount as R/O, this should allow you to delete/replace system stuff & ringtones, fonts...etc.
2)No, because apps install to data/apps & not system/apps.
3)You mean like the applicatiuon menu when we used to delete shortcuts or rename them? Hahaha man that was sooooooooooooo long time ago for me. Anyway, the applications installed are displayer & you can't hide them or rearrange them like Winmo. You might want to try Launcher Pro to hide apps in the apps drawer.
If you need more info, ask freely because 2 years ago I went through the same

mr.r9 said:
1) Press on Remount as R/O, this should allow you to delete/replace system stuff & ringtones, fonts...etc. Typo..You meant R/W
2)No, because apps install to data/apps & not system/apps.
3)You mean like the applicatiuon menu when we used to delete shortcuts or rename them? Hahaha man that was sooooooooooooo long time ago for me. Anyway, the applications installed are displayer & you can't hide them or rearrange them like Winmo. You might want to try Launcher Pro to hide apps in the apps drawer.
If you need more info, ask freely because 2 years ago I went through the same
Click to expand...
Click to collapse
Hmm..actually the new MTD partition table hack should be able to free space on the /system, adjusting partitions with less for /system and /cache and more for /data/app should give enough space..Though I'm not sure if he wants to try this right now, since it's considered an advanced task and maybe he'd like to get more accustomed to Android before attempting it? His wish though..
And well, there's yet another method to remove system apps, other than the other two methods. This is to modify the zip file of the custom rom to remove the actual apks from /system and reflashing it on top of the actual flash..

droidzone said:
And well, there's yet another method to remove system apps, other than the other two methods. This is to modify the zip file of the custom rom to remove the actual apks from /system and reflashing it on top of the actual flash..
Click to expand...
Click to collapse
Ohh yes indeed. OP, you can edit the zip before installing it to your device. You can remove/replace application in system/data and fonts...etc. Just remember to change signature verification to off in your recovery.

my god. i have spent days on this baby and im only barely scratching the surface
much appreciate all your help guys!
ok.. so its time to use app2sd i hear that app2sd+ is better though? (it moves more data to SD yeah? appcache?)
i only have 2Gb microsd right now so i might wait until i my 8GB arrives before i flash a new ROM and start again (again!)
i also noticed these online kitchens. http://cookmyrom.co.cc
which look great! tho they are still a version behind the leedroid i am using tho its a good way to get rid of some default apps.
i certainly like the idea of reparitioning the default disk though not quite ready for that yet especially when app2sd+ sounds much more straight forward.
i am dumbfounded that you cant remove 'shortcuts' from the All Apps! or even rename them!! my god. i would think that was first thing available on such an open source OS.
So i have now created a folder called "Folder" to reduce the clutter.. and now i guess i cant even rename it!?? and if i create another one its called "Folder" too!
lol.. this OS is so advanced yet some basic stuff seems to be overlooked.
I did try launcher pro though it removed my HTC Sense (which i like). So i might need to keep looking for an app to help organise my All Apps and my desktop (is desktop what its called?)
And just how do i add ringtones?
love your work guys thanks again.

Create a folder called Ringtones on the root of your SD to have...ringtones.
When you open a folder, long press on the header to rename it.
As for organizing, I stopped caring & started to use search, but maybe if you want you can try an app called folder organizer.

mr.r9 said:
Create a folder called Ringtones on the root of your SD to have...ringtones.
When you open a folder, long press on the header to rename it.
As for organizing, I stopped caring & started to use search, but maybe if you want you can try an app called folder organizer.
Click to expand...
Click to collapse
nice one thank you!

Sage said:
...So i have now created a folder called "Folder" to reduce the clutter.. and now i guess i cant even rename it!??...
Click to expand...
Click to collapse
Open the folder then hold where it says folder to change its name.

Ok. Now have app2sd working!
thanks to all of you. Beginning to love this android phone now. I feel sorry for all the people who use them as they come from the factory! Thank god for all the xda people who rip them to shreds and make them better

If i can have one last question. Any way to remap hardware buttons to start an app?
Like when you hold down the search button it launches Google Voice. I want it to launch a different app..
I did a search and found the hardware button remapper though it only does hardware to hardware.. not hardware to app

For Folders(Assuming you're using full HTC Sense), just open it and hold the title bar. Took me some time to figure out. You cannot easily rename the apps in "All apps", but you can remove them(Which is essentially uninstalling them) from Settings > Applications > Manage, unless they are system apps which need to be manually deleted either via S-OFF + Root explorer(OR something similar) or ADB + Custom recovery(Clockworkmod or Amon Ra).
For setting a custom ringtone, open the music app, select the music > Menu > Set as ringtone.

so no love on the hardware remap for apps?
Oh well i have done a lot of googling and it seems it cant be done (well at least not easily).
My last question is when you launch an app from a folder the folder stays open.. any way to force close or change its behaviour?

for those following this. I found the Tasker app remaps hardware buttons amongst doing amazing other things.
Still no love on closing folders though.

i ended up using tasker to create app widgets to replace the folders...

If you want app widgets, there's also "Desktop Visualizer".
In terms of killing of an app, have you tried "Settings -> apps settings -> development" then there's an option there for "stop apps via long press"?

[NTG][1.2]GlowNooter 1.12.25

This Nooter is officially supported by The Nooter Project for Nook Simple Touch​
I'm not adding certain things because I don't believe they should be available as part of a rooting kit designed to give users more control of their devices. Things such as additional readers or CPU Clocks are up to the user to install themselves and needlessly putting them in Nooter creates app bloat that a user may or may not want. You can always drop Apps you want into \nooter\data\app and they will install automatically when you root the device. This Nooter is designed with the sole purpose of opening up the possibilities of the device by giving users Root, Google Apps, and other Apps which make the device more usable as an android device than just an e-reader.
What it does:
Enables ADB via uRamdisk
Installs adbWireless
Installs Button Savior
Installs Amazon Marketplace
Installs su and Superuser.apk
Installs ADW + E-ink Friendly Theme
Installs Busybox & Busybox Installer/Uninstaller
Installs Gapps (Gmail, Market, Youtube, Others)
Installs NookColor Tools (To Enable Non-Market Installs)
System Files that get Modified:
/system/build.prop - Enabling Google Check In
packages.xml - Allows Gapps to install properly.
framework.jar - Should allow a proper Android ID to generate.
Changes:
May 26, 2012 - Initial Release
Before you begin:
You must already have a registered Nook Simple Touch Glow
You must have a Gmail/Youtube linked Account. IF you used a Gmail account for B&N Registration you should use that one for this process.
You must either have dd (Linux) or WinImage (Windows) software.
You must have an external microSDCard reader or this will not work. Using the Nook Simple Touch can result in it becoming unusable (bricked).
You must have enough intelligence to follow instructions.
Let's get started:
Download CWM from here: http://forum.xda-developers.com/attachment.php?attachmentid=806435&d=1323121399
Download TouchNooter from here: glownooter-1-12-25.zip - Uploaded
Download eded333's beta5-1XWUMFTouch-PART-2-END from here: http://nooter.googlecode.com/files/beta5-1XWUMFTouch-PART-2-END.zip
Unzip CWM and you'll find an image file you will then need to write this to an SD Card.
Linux: Unzip and use dd if=cwmimagename.img of=/dev/sdcard
Windows: Unzip and use WinImage to "Restore Virtual Hard Disk Image" to your SDcard.
Windows Alternative: https://launchpad.net/win32-image-writer/+download
Power off your Nook Simple Touch.
Insert TouchNooter SDcard into your Nook Simple Touch.
Power on your Nook Simple Touch.
User "n" to select, Left Buttons to go up in the menu, Right Buttons to go down in the menu, Power Button to go back.
Install from zip
Choose zip from sdcard
glownooter-1-5-26.zip
Click Yes and let Complete
Remove SD Card and press Power Button to go back one to main menu
Click Reboot
Upon boot unlock your screen.
At the Android Welcome Screen skip Sign In.
Enable Location Services when given the option.
Connect to Wifi and launch Youtube from ADW's App Drawer (Or the App Drawer of your Choice).
Click the Menu button (The right one in the middle of the status bar).
Select "My Channel" and Login using your Gmail Account.
Exit Youtube and Launch Gmail from ADW's App Drawer.
Sync your Gmail Account and Exit. (If it fails to sync that is fine.)
Power off your Nook Simple Touch.
Insert TouchNooter SDcard into your Nook Simple Touch.
Power on your Nook Simple Touch.
User "n" to select, Left Buttons to go up in the menu, Right Buttons to go down in the menu, Power Button to go back.
Install from zip
Choose zip from sdcard
beta5-1XWUMFTouch-PART-2-END.zip
Click Yes and let Complete
Remove SD Card and press Power Button to go back one to main menu
Click Reboot
Open up Market and Accept Terms and Service.
If you made it this far your nook should be successfully Rooted. Go Download an App to make sure.
Enable Non-Market Installs by running the NookColor Tools App.
If your Youtube fails to launch Uninstall and Reinstall Youtube from /data/app
Go to Settings > Device Info > SdCard > UnMount > Format
Thanks To:
mali100 - For porting CWM to Nook Simple Touch
eded333 - The second zip to fix Market Issues.
MrMuffin - For the original Market Hack that we're using.
If I'm using an app in TouchNooter and you would like Credit/Thanks, or to have it removed, please PM me, otherwise I might not see your requests
Currently Working On: Raspberry Pi Triple Boot System

It works!! Thank you thank you thank you thank you!

It works.
You couldn't have made me day any happier, Your hard work has given me a small tablet that I will use at work for keeping notes and recalling info. I'll be Joe cool with the info.
Thank you for all your hard work, I'll look in my couch and find something to donate.

Anyone experiencing problems accessing settings/screen to change the screesaver Folder?
Sent from my NOOK using xda premium

I have previously rooted using Roustabout's tinynoot. If I decide to do this Nooter, would I have to restore to stock first? (Haven't decided yet, pretty happy as is, but would like to know the options.)
Thanks,

Dude, nice job! Now to go buy a glowlight.

Hi,
Hmm, awesome =), just installed this on my Nook STR Glow.
Two questions
1. What's the best way to get Market searching enabled?
I've heard of installing SearchMarket - however, how do you do that? Do you just find the APK and install it manually?
2. Is it possible to install the Multitouch and NoRefresh patch from here?
http://forum.xda-developers.com/showthread.php?t=1568560
Or is the Glowlight version different enough that these won't work?
Cheers,
Victor

Anybody have trouble with getting the Opera Mini that comes with this to work? It doesn't even open for me. I installed Dolphin Mini and it seems to work ok but I'd like to get Opera working.

Multi-language root
This is great!
Is there a way to add menus and/or keyboard with another language?

xanadu1979 said:
Anybody have trouble with getting the Opera Mini that comes with this to work? It doesn't even open for me. I installed Dolphin Mini and it seems to work ok but I'd like to get Opera working.
Click to expand...
Click to collapse
Try opera mobile, not mini.

@glowco: I'm looking at GD's scripts and the tinynoot scripts right now.
It looks as if I used the same binary (despite the different name) for the
/system/app/Superuser piece (the file sizes and mod dates are identical.)
I used a different release of busybox, though. So the busybox my script installed would be overwritten by the glownoot busybox.
My advice is that if you want to get the google apps working, restore from a nonrooted backup and use this tool. I'm very likely to ignore my advice on my own device and see what happens, but today's not likely the day that's going to happen.
The line in glownooter that does the copy-in is:
package_extract_dir("system/xbin/", "/system/xbin/");
Unless the package_extract_dir command wipes a directory before copying in the file, you'd overwrite busybox at that step but leave the links to it. The links would probably continue to work but if there's an important difference between the two busyboxes, you might find it made trouble in a weird, random way long after you'd forgotten that you'd overlaid one root with another.
The busybox updater/manager might alleviate that issue - not sure what Ed's or GD's take on overlaying one root with another is.

Roustabout, thanks for your reply. I'm not rushing into anything, so if you do decide to try installing this over yours, let us know the results. (I tend to like the easier approach if it works okay.)

Maybe I should take this opportunity to ask an additional question: what will this root let me do that tinynoot didn't, other than run the Market? What additional apps would it allow me to run that would actually run well?
One app I have partially working on tinynoot is Jabiru, a jabber chat client. The basic chat connection works, but the Conference function crashes the session. I doubt this other root would make a difference in something like that?
Thanks.

I just did this and it works great. The only problem I have noticed is that when I am in gtalk and trying to chat I only see the top two rows of keys. Is anyone else getting this or know how to fix it?

Hi,
before to try rooting the nstglowlight, is it possible to make backup with noogie like the normal NST ?

Yes, you can and should boot from a noogie disk and make a whole-device backup before changing things up, just like with the NST.

Assuming that tinynoot used MinimalNooter as a basis for it's design (as is evident by the forum convo) then GlowNooter will run perfectly fine without any issues, however keep in mind that because the package names for files in GlowNooter in /data/app are likely to be different than those in tinynoot you'll end up with multiple copies of things like Amazon market, which doesn't actually affect performance, but can take up more space. So you have two options, the first is to do a fresh install onto a fresh NTG, or you can install this on top of tinynoot and go in and remove the excess files using Super Manager.

Aurtach said:
I just did this and it works great. The only problem I have noticed is that when I am in gtalk and trying to chat I only see the top two rows of keys. Is anyone else getting this or know how to fix it?
Click to expand...
Click to collapse
Using an alternative keyboard could fix it, the major issue is finding an alternative keyboard that is e-ink friendly. This tends to be broken in the app itself, because I have noticed the Google Voice app will do the same exact thing on nook devices.

glowco said:
Maybe I should take this opportunity to ask an additional question: what will this root let me do that tinynoot didn't, other than run the Market? What additional apps would it allow me to run that would actually run well?
One app I have partially working on tinynoot is Jabiru, a jabber chat client. The basic chat connection works, but the Conference function crashes the session. I doubt this other root would make a difference in something like that?
Thanks.
Click to expand...
Click to collapse
The difference between this and tinynoot IS the fact it has Market on it, you can actually go to google.com/play now and install apps to the device. Other than that there is no major difference.

Yeah, folks should understand what tinynoot grew out of: I wanted the smallest set of changes I could make to have a rooted NST usable by me. I almost didn't include the Amazon appstore, but then realized there were things I wanted from it and that it'd be more helpful to others if there was at least something
That's very bare-bones, because I don't use the NST for too much other than reading - I want an rss reader, a non-BN book reader and my contacts (via b-folders, rather than a google account,) and at that point I'm pretty much done. I often install what I want to a fresh device just using adb or pm from a commandline
Gabrial's trying to get the Google market working because so many folks really want it.
Also, I tested tinynoot against an NST last night and was able to root that using it, which is helpful to me.
That said, here are the files tinynoot copies in; it sounds as if the two rooting tools are compatible, which is helpful.
in system:
/system/xbin/busybox
/system/bin/su
/system/app/NookColorTools.apk
/system/app/com.noshufou.android.su.apk
and in /data/app:
ADW.Launcher_v1.3.6_Standalone.apk
Amazon_Appstore-2.1.0.apk
BusyBox_v7.3.apk
Button_Savior_v1.3.1.apk
NookTouchTools_v1.0-beta2.apk
Super_Manager_v2.6.0.apk
adbWireless_v1.4.1.apk
and that's that.

Link2SD & CM11: Optimal Strategies

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)

How to root Samsung A3 (2017) - Guide

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