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)

[Q] WLAN not working after Nandroid restore on another S3

Hi,
i tried to restore a Nandroid Backup into another Galaxy S3, ROM and Baseband Version is the same.
After Restore everything is fine except WLAN, i can see accesspoints and also can enter the psw but it will not propperly connect to the ap it tells me authentication failure but the psw is correct and it will also not connect to an open accesspoint, something must be messed up with the wlan.
Can anyone help? Else i will use my old way over Titanium Backup but this is more time intensive.
Greetz X23

Anyone? I have exactly the same problem after doing a nandroid restore on my replaced S3. How do I fix this without having to do a factory reset?

Fixed the "Authentication error occurred" problem
I finally solved the problem after trial and error. I found that it was a file called .cid.info in /data that I needed to delete. My WiFi now works again.

vpwrf said:
I finally solved the problem after trial and error. I found that it was a file called .cid.info in /data that I needed to delete. My WiFi now works again.
Click to expand...
Click to collapse
Hi. I just registered cause I am trying to resolve this exact issue.
My situation: Cracked my screen on my I9300 (still working and yes, not the t-mobile version but international) and got a brand new replacement phone (exact same model) so I can get my old one repaired.
Did a NANDROID restore and copied internal SD card content (external SD card was simply physically swapped). Everything seems fine, but WiFi is not connecting to any router (famous "authentication error occurred - incorrect password" message).
Flashing a newer version of my ROM (Android Revolution HD, currently on 20.0, flashing 29.0 on my new phone) works fine, WiFi working as it should. So it is not a hardware issue.
So my question really is (as I simply want to "clone" the software layer of my phone until Android Revolution HD for 4.3 is released):
What else did you modify/change/delete to get this to work? Simply deleting .cid.info after restoring from NANDROID did not resolve the issue.
Any hints are highly appreciated. Been playing around with it for a week now (on and off) but cannot resolve the WiFi issue. Checked several forums and googled like a lot, but without any success. What am I not getting?
I am fairly new to Android (6 months), sometimes missing some (to others) essential background information and vocabulary, but happy to learn and not completely retarded.
Thanks for your help!

Have you tried forgetting the networks then reconnecting? Otherwise try renaming the .rev file. Or you could try copying the .cid.info from a ROM where the WiFi works fine to the Nandroid restored data. That might fix it.

I tried forgetting the networks, without success. I do not know what you are referring to by .rev file, and I do not have another device to restore my NANDROID image to, to then copy the cid.info file. So I kept playing around and this is what worked for me:
I found a file called wpa_supplicant.conf in the following directory: etc/wifi
Opening that file revealed some (as I was assuming) device related information (such as device type, model name, serial number, etc).
I renamed that file to .bak and this resolved my issue. I even deleted that file later on.
After enabling WiFi again, the file was not recreated by the system, even after a system reboot. I am not sure what this file does and how it was created, but so far everything is working as it should.
I also found a second file with the exact same file name at a different location: /data/misc/wifi
The content of that file is different, but some of the information is identical. This file contains WiFi AP information (like AP that I connected to in the past). Deleting that file would break my WiFi and would prevent it from turning ON. So I strongly recommend not to delete that file!
Needless to say: Do not make any modifications to system files without a functional NANDROID backup!
So in the end it seems to have been what I suspected all along. Some system file that was related to my old device and that, if identical, would create issues on the new device. But all of this is pure speculation. I am not an Android/Linux expert and simply tried to apply some logic.
I hope that I will now face no more issues. In case I do, I will report back.
Thanks for your help!

So, after getting my S3 repaired and switching back to it (usual NANDROID restore process), I was facing the exact same issue.
The wpa_supplicant.conf file that I was talking about did not exist, so I tried renaming the cid.info and that worked.

skofox said:
I tried forgetting the networks, without success. I do not know what you are referring to by .rev file, and I do not have another device to restore my NANDROID image to, to then copy the cid.info file. So I kept playing around and this is what worked for me:
I found a file called wpa_supplicant.conf in the following directory: etc/wifi
Opening that file revealed some (as I was assuming) device related information (such as device type, model name, serial number, etc).
I renamed that file to .bak and this resolved my issue. I even deleted that file later on.
After enabling WiFi again, the file was not recreated by the system, even after a system reboot. I am not sure what this file does and how it was created, but so far everything is working as it should.
I also found a second file with the exact same file name at a different location: /data/misc/wifi
The content of that file is different, but some of the information is identical. This file contains WiFi AP information (like AP that I connected to in the past). Deleting that file would break my WiFi and would prevent it from turning ON. So I strongly recommend not to delete that file!
Needless to say: Do not make any modifications to system files without a functional NANDROID backup!
So in the end it seems to have been what I suspected all along. Some system file that was related to my old device and that, if identical, would create issues on the new device. But all of this is pure speculation. I am not an Android/Linux expert and simply tried to apply some logic.
I hope that I will now face no more issues. In case I do, I will report back.
Thanks for your help!
Click to expand...
Click to collapse
It did not work for me. Neither does deleting .cid.info works.

That sucks. It's so frustrating.
Try to play around with it, based on the info in this thread. Make sure you have a working NANDROID backup, to just state the obvious (no offense).
Can you elaborate a little further what you believe caused the issue?

Reflash ing the rom would probably fix this.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

[Q] Paranoid Android preference storage problem

Hello guys,
I've just flashed the Paranoid Android ROM by WOH (http://forum.xda-developers.com/showthread.php?t=1912187&page=111) and I really like it.
However, I'm having some kind of issue with the PA engine settings.
The problem goes like this:
1. When I set the global UI settings, I'm asked to reboot, but the settings are back to defaults after the reboot.
2. When I edit the preferences for a particular app, I'm only able to make it work by setting and applying the needed values followed by using the launch button, which finally makes the changes effective. These changes are, however, also reset after rebooting the phone.
I did some searching and found this hint (http://www.paranoid-rom.com/forum/guides-references/256-hint-pa-prefs-does-not-save-changes) which seems to deal with this problem, but haven't had any luck with it. In the terminal, when trying to run the commands, I get an error saying my file system is mounted read only. So I tried modifying the file perimissions in the ES file manager (which also didn't work on some occasions, but sometimes it did), then running the terminal commands successfully, but without any effect on the PA preferences bahaviour after rebooting.
I ended up editing those files manually and removing the backup file (which, I thought, was overwriting the preferences file, reverting the settings to defaults). The ES file manager also behaved very oddly when trying to manipulate those files, once I was not allowed to delete those files, than they disappeared on their own, same goes for renaming.
Finally, I think, the problem is being caused by the properties file being overwritten with the defaults on every boot. So far I've been unable to determine the cause of this behaviour, so I hope perhaps some of you have come across this problem and know the solution. Thanks in advance for that.

[Q] Editing MMS settings under a JB rom

First off my disclaimer -- I have searched the forums already for an answer, but can't find anything that I understand to be analogous to my problem. Also, I'm kind of a noob about this but I've been a unix/Linux sysadmin for 20 years so I have some understanding of what's going on at the Android operating system level; just not the CDMA piece yet.
So here's what I have:
I flashed my E4G over from Sprint to Boost using the Incognito method. Changed the MMSC URL through the dialer with my SPC. Voila! Everything works great.
Except that I'm on FC09 Gingerbread and it's boring.
SO... I root the easy way by flashing that pre-rooted FC09 BML image that's floating around here and install CWM recovery. Easy. Everything's cool.
Then, I wipe everything three times (no, I'm not anal retentive or obsessive-compulsive) and flash the Carbon JB rom from recovery.
Flash works perfectly and now I have TWRP for recovery, which is very convenient, though I gotta give props to the ClockworkMod team, they have knocked down a thousand walls.
BUT--- My MMS stopped working because the mm.myboostmobile.com MMSC URL was overwritten with the one that was baked into the ROM (I guess from the romdev's phone that was used to make the image). Anyway, Now that I'm on a Jelly Bean rom, I can't just use the *#*#DATA#*#* dialer code and my SPC to edit the setting back to Boost because I get that damned MODEM EXCEPTION error (which I think is related to permissions changes under ICS and JB that weren't there in FC09 Gingerbread).
I bought an APN manager off the play store and did a backup of my APNs under the working stock setup, but of COURSE, the damn thing doesn't work under ICS or JB so I wasted my money there. AND, APN Backup and Restore from the play store doesn't work properly either, although I can't rule out the possibility that the APN backup I took under working FC09 was no good.
So, my questions are these:
Is it possible to manually edit the appropriate APN settings under a Jelly Bean based ROM back to boost? I'm assuming there's some xml file somewhere that holds all this stuff that I could just vi ? I know I just need to null out the proxy and port values and switch the MMSC url back to mm.myboostmobile.com right? So where is the file and if there's an easier way to do this, can you give me a pointer?
Thanks! I really don't want to be stuck on Gingerbread just to be able to drunk-text dong shots to my boss at 2am.

SOLVED!
UPDATE: ok, a few more hours of archeology and I figured out how to get the right MMSC URL poked in there. It was an inelegant hack:
1). After moving APN Backup and Restore (play store) to my system folder with system/app/mover (also from the play store), I backed up my APNs.
2). I copied the backup XML file onto my PC and edited it with vi to change the MMSC field in each of the 15 APNs stored in the file to "mm.boostmobile.com" THIS IS PROBABLY OVERKILL and I might have broken something else I don't know yet by doing this
3). Copied the edited file back to the APNBackupRestore folder on my phone's SD card
4). I used APN Backup and Restore to delete all my APNs then entered the dialer code to view my MMSC URL, it gave a FC error --I knew it was empty now.
5). Rebooted into TWRP (CWM would work the same way) and wiped cache, Dalvik, then fixed permissions for the hell of it
6). Reboot into system, restore my edited backup APN file using APN Backup and Restore
7). Reboot again
8). Re-enter the dialer code (*#*#3282#*#*) and view my MMSC URL: Voila! "mm.myboostmobile.com" is in there now
9). texted a close-up of my big toe to my wife at her work and received a reply txt with a close-up of her left nostril: SUCCESS!
Now MMS and 3g (on rev a8) are working just fine on CarbonRom. Hope this helps someone.

Removing T-Mobile CRAPPS from Huawei U8730

Hello fellow XDAers,
My wife replaced her Samsung Gravity Smart with the T-Mobile MyTouch Q, AKA the Huawei U8730 (not the older LG C800 model w/ the same name). She gave me the task of cleaning the junk APKs off of it to de-clutter it.
Rooting the phone was the first task. This method worked perfectly for me without any fuss (the app will return error 64, but after installing Superuser and rebooting, I had root access). I was able to use Titanium to remove much of the crap ware, but the most annoying bits gave the error "cannot find APK." Weird.
After digging around, I took an inventory of the apps in /data and /system.
The T-Mobile junk wasn't there.
I threw busybox on the phone and used the 'find' command, and I found where the apps were hiding: /cust/t-mobile/us/apps, which is a loopback-mounted ext3 partition. I tried to remount it read/write, but got 'permission denied' error. I figured something had the filesystem locked, so I ended all the apps that were running and tried again, but no luck.
However, I was able to remount the volume that held the ext3 image file read/write. It mounts to the /.cust_backup directory.
IMPORTANT NOTE: For those who will be following these steps themselves, at this point you will want to make sure to go into the Applications manager and uninstall any updates downloaded for the crapware you are going to remove. I will explain why below. It's not absolutely critical, but it will save you some head-scratching.
I remounted the partition read/write, grabbed the image file (located in /.cust_backup/image/cust.img), and uploaded the image file to a linux server.
On the linux server, I mounted the image, nuked the unwanted APKs, and unmounted the filesystem.
I created a backup of the original cust.img file, then overwrote the one in /.cust_backup/image
Last step was to reboot the phone, and most of the junkware was gone.
Here's where the head-scratching came in. A couple of the apps were still there, and I didn't know why. I double-checked the phone, and the APKs were in fact deleted. Then I realized: the app had received an update and I was seeing the update. When I uninstalled the update, the uninstall "failed" but the icon still disappeared. However, I had to reboot the phone again to fully remove it.
So, here's the process in a nutshell:
1. Uninstall all app updates for the crapware you plan to remove
2. Root the phone using This method .
3. copy down /.cust_backup/images/cust.img
4. Using a linux system, mount cust.img as a loopback device, then delete the unwanted APKs (they will be in t-mobile/us/apps)
5. Unmount the image (this writes your changes back into the cust.img you mounted in step #3)
6. On the phone, remount /.cust_backup r/w
7. overwrite /.cust_backup/images/cust.img with the modified version
8. Reboot the phone
That's it! Enjoy your uncluttered phone!

I know it's been a while since the original post, but I was wondering if OP has had any problems with the phone since then, or if anyone else has tried this with the Huawei u8730 and had success. My wife also wants all this crap removed from her phone, but she would probably murder me if I bricked it in the process.
Thanks!

Just on a side note here as I'm still using this device. How did you get around the non-working tethering on this device? Both the USB and Wifi hotspot won't work unless you've subscribed to the T-Mobile Smartphone Mobile HotSpot app option on your account? Mine is unlocked and being used with another carrier, but only recently wanted to tether to it so I can't figure out how to correct this one. Also still looking around for any working custom ROM for this. Thx.