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)

Cannot Mount System as r/w

I have searched the entire forum and haven't found the answer to my problem...I have even asked in the rom specific thread (where other people have had a similar problems) but my question (and theirs) just gets overlooked!!
So here it is.
I have both radio S-off and the End Hboot and have flashed three different custom roms on my HD (the Core Droid, Revolution HD and LeeDroid) all giving me the same problem.....I cannot set the system as r/w using apps such as Root Explorer and SUFBS!
I tried entering the mount command by itself in a terminal on the phone and I get:
# mount
mount: no etc/mtab
I can however mount the system from adb shell by inputting: mount -o remount,rw /dev/block/mmcblk0p25 /system
but that isn't really a solution!
I have a nandroid backup of my original stock rom which I have rooted and I can mount the system fine using root explorer and do not get this 'no etc/mtab' message when I type mount in the terminal.
I find it odd that it occurs with three different custom roms but not on my original stock rom so maybe it could be the way I flash the roms? ...I always use the Full_Wipe.zip with CWM recovery which formats the boot, system, data and cache partitions and then I apply the rom.
I've been pulling my hair out over this...and I know it must be something simple, but I've been stuck with this problem with no solution for a week!
Does anyone have any ideas?
EDIT: It turns out that some of the custom roms have limits in place that prevent editing the system and therefore were causing errors. Have tried the Cyanogen rom and have not encountered the errors/restrictions so it was definitely due to those custom roms. Not really a solution, but found the 'cause' of the problem.

Hmmm....looks like I'm the only one with this problem. Has no one else had anything similar?

your not the only one, i hbave had this too, this prevents you from removing apps doesnt it, now is it the 1.72 rom or the 1.34 rom

try to download Root Tools and go to Extras and then go to MIscellaneous and select "mount system read/write". if it does not work i guess that you have an issue with phone.

if its a 1.72 rom then you wont be able to mount it, i think HTC have decided to change the mount partition or something along that line, there isnt an issue with the phone, its just HTC have plugged up the root boothole that there was.

mariosraptor said:
try to download Root Tools and go to Extras and then go to MIscellaneous and select "mount system read/write". if it does not work i guess that you have an issue with phone.
Click to expand...
Click to collapse
Just tried that option and it does work as it succesfully mounts the system as r/w. However, if I go into root explorer it doesn't allow me to toggle the system as r/o....so the mount commands from my currently installed apps are not working. Could it be something to do with restoring the apps from my old Milestone onto the Desire HD using totanium backup? Actually restoring through titanium backup shouldn't be a problem since it works with the stock rooted rom.
fkofilee said:
if its a 1.72 rom then you wont be able to mount it, i think HTC have decided to change the mount partition or something along that line, there isnt an issue with the phone, its just HTC have plugged up the root boothole that there was.
Click to expand...
Click to collapse
I've heard about that problem too....but my current rom is based on the 1.34 rom (Core Droid V1.5), so its not that...

after doing what you have to do you can go again to Root Explorer and remount as read only.
fl4r3 said:
Just tried that option and it does work as it succesfully mounts the system as r/w. However, if I go into root explorer it doesn't allow me to toggle the system as r/o....so the mount commands from my currently installed apps are not working. Could it be something to do with restoring the apps from my old Milestone onto the Desire HD using totanium backup? Actually restoring through titanium backup shouldn't be a problem since it works with the stock rooted rom.
I've heard about that problem too....but my current rom is based on the 1.34 rom (Core Droid V1.5), so its not that...
Click to expand...
Click to collapse

mariosraptor said:
after doing what you have to do you can go again to Root Explorer and remount as read only.
Click to expand...
Click to collapse
I guess thats the best option for now...not a complete solution, but a work around that doesn't require a pc at least.
Would still be good to find the cause and fix it!

I've got the same issue! Are you sure the error you receive is 'no etc/mtab' and not 'no etc/fstab'?
Anyway I've been using the App 'Mount System (rw/ro)' as my solution for now and it works a treat. Still, as you can imagine it is not a permanent solution!
The only thing I feel may have contributed to the problem was my original root attempy via Visionary failed and I had to wait until the R13 before I could unroot and root again. Possibly something got borked along the way. Did you have any similar issues?
Will be keeping my eye on this thread and if I do find a solution I'll let you know.
Regards.

It’s definitely a ‘no /etc/mtab’ error.
When I rooted I used Visionary r14 and the only hiccup I had was that it didn’t permaroot on the first try so I had to redo it.
It’s odd that my nandroid backup of stock doesn’t give me the error and its only the custom roms that do! I have a feeling it might be something to do with an incorrect/incompatible Busybox installation with the custom roms...

sounds more app related as you can use another app to mount the system, but not with root explore. i know this is obverse an you probably done it ,have you uninstalled root explore and reinstalled from market as you said you used titanium backup.
you could copy /etc/mtab from stock an place on sdcard and paste it in the custom.
not a solution but more see if its just a file that's missing
the only file i could find was vold.fstab and my base rom is 1.72.405.3 and root explore works fine.

cattleprod said:
sounds more app related as you can use another app to mount the system, but not with root explore. i know this is obverse an you probably done it ,have you uninstalled root explore and reinstalled from market as you said you used titanium backup.
you could copy /etc/mtab from stock an place on sdcard and paste it in the custom.
not a solution but more see if its just a file that's missing
the only file i could find was vold.fstab and my base rom is 1.72.405.3 and root explore works fine.
Click to expand...
Click to collapse
I've tried looking for /etc/mtab in my stock rom but its not present..I don't think its a physical file thats why it can't be copied....
But I think you may be right about it being an app based problem...just tried LeeDroid V1.3 (based on 1.72 rom) out of curiosity and root explorer still wasn't working. I then wiped again but installed root explorer fresh from the market instead of titanium backup and it is now working!! YAY!!
However, SUFBS still does not work and returns 'no /etc/mtab' when I type 'mount' in its terminal and reinstalling (either from titanium backup or fresh from the market) does not make a difference. Since root explorer is now working I believe that the dev for SUFBS needs to update his app maybe?..or is there still something wrong with my system?

yes sir !!! that is where your correct !!!
the current custom roms bar... Cyanogenmodm dont allow the current installed apps to be changed due to your error message.
IF YOU ARE CONFIDENT WITH ADB COMMANDS; you can have ago at pushing and pulling and mount it that way using a PC
but be very careful as you can damage your phone by doing this

fkofilee said:
yes sir !!! that is where your correct !!!
the current custom roms bar... Cyanogenmodm dont allow the current installed apps to be changed due to your error message.
IF YOU ARE CONFIDENT WITH ADB COMMANDS; you can have ago at pushing and pulling and mount it that way using a PC
but be very careful as you can damage your phone by doing this
Click to expand...
Click to collapse
Ahhhh, if thats true then it makes sense! Thats why the custom roms were giving me trouble but not my rooted stock rom and why adb commands from a pc work. I guess its a precaution but still an inconvenience...especially when I want to make changes/do something away from the pc.
......the question is: is it true? are you 100% sure the custom roms don't allow changes?

its 100% true, well most of the new ones anyway, CM was built from open source code and is completly there creation BUT
custom roms created from stock are basically modded ROMS

Just tried Cyanogenmod rom 6.1.2 and have had no issues at all! So it seems fkofilee is right...some of the custom roms just don't allow changes to the system.
So not really a solution but atleast found the 'cause' of the problem.

I noticed you said you used the full wipe .zip has everyone else used it ??? As I did not use it the first Rom I flashed was leedroid 1.2 and then 1.3 the only thing I used was cw recovery wipe/factory reset and my root explorer never failed can toggle between the two and when I first booted all my apps synced back via market did not use titanium backup not keen on it also I've read a few posts problems with titanium not restoring apps also read somewhere the full wipe zip doesn't always work right maybe its the wipe and titanium that causing it
Just a thought
Sent from my leedroid v1.3a DhD via xda app

I use full wipe. Zip but I never have problems with root explorer. Been using more than 1 Rom. ( Modaco r 2, leedroid 1. 3, Hd revolution. And also I have modded them a lot to look aosp.
Sent from my LeeDroided Desire HD

[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.

cut and copied xbin files to bin resulting root corrupt

i own a device xpad x1010 manufactured by simmtronics india.it was rooted. i decided to have some fun and download dsploit.i also installed busybox for this.my device already had busy box as shown by root checker but i installed it.all my apps vanished and many data was lost and my tab was acting weird.no apps was getting installed so i googled and found some where to delete inbuilt apps and move the contents from xbin folder to bin.it worked but and all my apps and data was restored.but root was corrupted.root checker showed device not configured properly or not granted:crying:.now i want to fix this problem i dont want to reroot my device as many thing i have added to root.
not:while installing busybox it give option for backup which i have done but cant find it anywhere.
previously my root checker told my device is root access ,but superuser not installed.
i am a noob but interest on learning so please guide me.
also in my room my neighbour school wifi catches but its wpa2 protected.i want to crack password.as in india data cost is high and schooland colleges have unlimited data plans .so its not a crime just use a free stuff of others

pelvin091 said:
i own a device xpad x1010 manufactured by simmtronics india.it was rooted. i decided to have some fun and download dsploit.i also installed busybox for this.my device already had busy box as shown by root checker but i installed it.all my apps vanished and many data was lost and my tab was acting weird.no apps was getting installed so i googled and found some where to delete inbuilt apps and move the contents from xbin folder to bin.it worked but and all my apps and data was restored.but root was corrupted.root checker showed device not configured properly or not granted:crying:.now i want to fix this problem i dont want to reroot my device as many thing i have added to root.
not:while installing busybox it give option for backup which i have done but cant find it anywhere.
previously my root checker told my device is root access ,but superuser not installed.
i am a noob but interest on learning so please guide me.
also in my room my neighbour school wifi catches but its wpa2 protected.i want to crack password.as in india data cost is high and schooland colleges have unlimited data plans .so its not a crime just use a free stuff of others
Click to expand...
Click to collapse
Is your device OK???? or still you need help????

ASKS v1.2 security and new kernel issues

Well to assist with peeps installing new Samsung Kitkat firmwares released this year, I made a quick list of odd issues that will pop up with rooting.
The new kernal will not allow titanium backup to find su. I use super su, so depending on which su you use, you may be able to operate titanium backup.
My fix, custom kernel.
Smanager fails to use rw permissions in terminal, though you can set rw permissions in advanced.
I removed asks packages, as with knox packages, so as far as I can tell asks v1.2 has no effect and is a bridge to selinux and knox.
Will try using busybox pro intead of a generic busybox with smanager, but feel the issue is within the app its self.
Will end up using jack term as a work around, until smanger is updated.
Would like to see titanium backup updated as well. So I can use the stock kernel and be happy this Kitkat is the best and most secure without the vulnerability issues still being addressed with newer builds of amdroid.
Found I get a wee better speeds, not just by the kernel replacement, but possibley from fixes done and tuning of this build.
If I find anything new I will add, but xposed and its modules seems bug free with is new kitkat.

Ok, I found the issue with term usage with rw permission.
You must use the mount remount command when at a terminal session. Unless your terminal app has a command toggle or macro to perform the proper command without typing.
Remember to also do the mount remount command for ro to close the rw session.
Everything else seems good to go. The new security seems more in tune to linux with apps needing to be more careful with setting permissions through the system perameters.

Looks like Samsung is making headway with blocking Google apps... starting with Chrome browser. Using Boeffla kernel on 4.4.2 you must use a script to make selinux passive. Never had to do that with any kernel running bare without a kernel manager before.