*****ROOT IS REQUIRED BEFORE PROCEEDING *****
*****FOLLOW THIS FOR ROOT, THANKS TO AYOTEDDY: http://forum.xda-developers.com/showthread.php?t=1100513
*****CREDITS GO TO SANFRANX415, SS2006, AND FROZ3N*****
The following process was originally made for the Samsung Galaxy S 4G, but works perfectly on the Sidekick 4G as well. I have tested and verified this working.
Steps:
1. Install "010 Hex Editor" you can use the trial version found here: http://www.sweetscape.com/010editor/
2. Install "Terminal Emulator" from the Market. Go to your Sidekick 4G and open the emulator.
*****FOLLOW THESE STEPS VERY CARFULLY*****
After opening a terminal emulator, type the following:
cd /dev/block <enter>
su <enter> <at this point your phone will ask for superuser, click access ALLOW it, if you already havent done so>
dd if=/dev/block/bml3 of=/sdcard/bml3.bak <enter>
*****THE PREVIOUS STEPS WILL PLACE A FILE NAMED "BML3.BAK" ONTO THE ROOT OF YOUR SD CARD*****
Go find the file on your SD Card and transfer it to your computer desktop.
3. Open 010 Hex Editor
4. In 010 Hex Editor, go to "File", "Open File", and open the "bml3.bak" file.
5. Once the file is opened, go to "View", "Linefeeds", "Fixed Custom", and ensure the number is set to "32"
6. Using your keyboard, select CRTL+F to search for a hex string, when the search window pops up select "Hex Byte" in the type field and then search for the following string below:
"FFFFFFFFFF0100000000" ALL TOGETHER, then hit the FIND ALL button to the right, some of you will get 2 results and others up to 10 results on your screen.
7. If you look at your Hex editor there are 3 window panes on the selected line
e.g 4CCC60h <-- Offset
01 01 01 01 < -- Hex Keys
yyyyyyyyy <- ASCII text (your 8 digit unlock code will be here)
8. Go through each result from the above search and you will see on the 3rd window pane (yyyyyyyyy) after the hex keys there is an 8 DIGIT CODE (write this code down), this is your unlock code NCK for your phone.
Sidenote: THIS 8 DIGIT CODE SHOULD SHOW ON AT-LEAST ONE MORE RESULT CHECK ALL YOUR RESULTS FROM THE SEARCH ABOVE IF YOU HAVE ANY DOUBTS (SOME OF YOU WILL HAVE YOUR CODE SHOWN AT-LEAST 2 TIMES AND SOME OF YOU WILL HAVE THE CODE SHOW MORE THAN 4 TIMES BUT YOU SHOULD NOT HAVE THAT MANY RESULTS)
***** TO INPUT THE UNLOCK NETWORK CODE DO THE FOLLOWING *****
9. Turn off your phone
10. Insert a foreign SIM card not attached to your current provider (e.g if you have T-Mobile, use an AT&T SIM CARD), and turn on your phone.
11. You will be prompted to enter a Network Unlock Control Key (use the code above that you wrote down and type it in your phone exactly)
12. After entering your NCK please hit "Unlock" or "GO" button and you should see a screen that says "Network Unlock Successful", and your phone should go in the main screen after your phone has been unlocked.
there is a thread in the general section with 3 or 4 different ways to do this and since u just copied an entire post in the SGS forum, u should link to that thread in ur post
I didn't just copy and paste, I change some small things that were a bit confusing, and I also gave credit to all who made the SGS4G guide at the very top of this post. The posts you say this is mentioned in, is not very noob friendly or easy to find.....this is.
Sent From My UNLOCKED Sidekick 4G
hey im trying to unlock my sidekick and im running into a problem, im good all the way up to when you search, im getting over 700 results, what am i doing wrong?
700 results ! are you 100% sure ?
what is the size of your bml3.bak file ?
do you get the same 6 digits sequence (in ASCII) after each result ?
If so that's probably the code.
I had the same problem. I was getting 700 results.when I scrolled all the way down the code was there. In results 699 and 700
Sent from my SGH-T839 using XDA App
You get a lot of results... once you get the results you look through every one of them till you find the code on the right... its 8 numbers really obvious that its the code your looking for
Any chance for a screenshot of the hexeditor on the correct string?
I ended up getting 468 results. After scrolling down the results slowly I found the unlock code. You'll know once you see it, as it stands out very clearly as a 8 digit code, it just takes time finding it if you end up getting a lot of results.
Very useful. I'm going to be unlocking a friends Sidekick 4G and didn't want him to have to pay for it. I'll give feedback when I actually try it. Thanks!
Very Nice!! simple! easy!! great post! thank you!!
Sent From My Samsung Sidekick 4G UNLOCKED
I've found the code TWICE but it never worked! any ideas?
I've reformated the SD card, rebooted the phone, and this time got the very same code 7 times, I've tried to enter it using the soft keypad and the hard one, still same result
Yay!!!
Thanks!!! Worked Fine for Me!
This will come in handy when my little cousin comes to visit.
Thanks for posting this. I followed the instructions exactly and it worked on my Sidekick 4G. There were over 120 matches to that hex string, and the unlock code was with the last two matches in the file. In case it wasn't clear, you should see 8 digits (hex values 0x30 to 0x39) right after the string you are searching for. The ASCII values (what you would actually type on the keyboard) are in the right pane of the hex editor.
ok so i followed all the instructions step by step and i opened the file in the editor 2 different ways from this forum and another, i searched for "FFFFFFFFFF0100000000" and it looked thru all 565 results and most of the results are "0.1.2.3.4.5.6.7.8.9" always in order but sometimes split up found 1 result with the correct amount of numbers but didnt work, just wondering if i went wrong somewhere?
mojo4713 said:
ok so i followed all the instructions step by step and i opened the file in the editor 2 different ways from this forum and another, i searched for ...
Click to expand...
Click to collapse
There is a much easier way which does not require complicated directions:
http://forum.xda-developers.com/showpost.php?p=15992373&postcount=7
Very useful. I have successfully unlock my SK4G without any problems. Thanks, man.
Worked perfect the first try. Thanks
Related
hi all i have been using Bell titan for long time.
I just received Telus TP2 as a gift.
guys i would like to find out its epst code.(tried MSL grabber it does not work)
can some suggest good rom to make it work on bell cdma.
as i understand tp2 supports bell cdma band.
thanks in advance
Not going to happen legally without a meid change
Try this Worked for me
From PPC Geeks
Originally Posted by AycheDub
Change the following registry entries in:
HKEY_LOCAL_MACHINE\SOFTWARE\HTC\ATDbgLog
Enable: 1
LogMode: 1
Wait a reasonable amount of time and soft-reset (I have noticed that it seems to take longer for this value to take affect, so if you reboot and the registry values are not changed, then you need to do it again and wait longer)
Check to see that the file \Temp\ATDbg0.txt has been created.
Return the values back to what they were (most likely 0) waiting the same amount of time as above.
Look in the ATDbg0.txt file and you should see a log of commands sent to the CDMA radio and there should be something like this somewhere in the file:
Code:
Tx:AT+HTC_RMSL=0\r
Rx:+HTC_RMSL: 354201\r\n0\r
Tx:AT+HTC_ROTKSL=0\r
Rx:+HTC_ROTKSL: 216112\r\n0\r
The numbers next to the Rx: +HTC_RMSL line should be your MSL. You may see a couple of different instances of this number within the text file - try one, if it doesn't work, try the next. The file ATDbg0.txt will either be in \temp or \ATDbg.
Hope this works for you.
it works
thanks it long process but it worked
arshiv said:
thanks it long process but it worked
Click to expand...
Click to collapse
You're welcome
I was one of the people that did the initial backup methods (telling you how to backup your certificate and rsa keys) or using cat which doesn't actually backup your wimax.img properly. After hours of playing around in a hex editor I finally got my 4g working again, and i'll explain how
****EDIT****
I added a hex converter you can use for your rsa key if you are too lazy to find one on google. I say to use hex instead of text replace because it's safer in regards to \n's
I was too lazy to make a gui for it but its haxt.net/evohex.php?rsa=yourrsa&cert=yourcert [obviously replace it with your 2 values]
Also, don't try to flash this image without editing it. The rsa key is invalid until you put your valid key in!
***********
Note - this won't work for anybody who actually has no idea what their RSA keys/certificate is.
So there are a few things you need first.
1. Your phones wimax mac address (take out your battery and look at the sticker)
2. Your RSA private key
3. Your Certificate
4. The wimax image file template I attached here in the zip
To simplify, use XVI32 freeware hex editor. If you search "BEGIN" you will see begin rsa key and begin certificate. You need to copy these values for later use.
Download the template file and open it in the hex editor.
Our template's mac is 00:18:41:81:8B:5C
Our templates Certificate is :
http://pastebin.com/vEnKFtS8
Our templates RSA Certificate is :
http://pastebin.com/gJbrh3ii
Convert both of these strings to hexidecimal and write them down! (it will look like a bunch of 4D 49 49 44 6B 44 43 43 41 6E 69 67 41 77 49 42 41 67 49 51 5A 4F 75 35 44 5A 4C 55 44 76 44 57 4B 57 2F 36 6D 48 66 4C 4F 54 type stuff)
If you don't know what your rsa key or certificate is, open it up in a unix friendly text editor(on windows i recommend notepad++). Search case sensitive for BEGIN. You will see the begin rsa key and begin certificate. Copy all of the text in between with no spaces or newlines! Now convert these both to hex and write them down.
Hit search -> replace on xvi32, click hex search and paste your converted hex for the templates RSA key.. and then replace with the hex value of YOUR rsa key. Do the same thing for the certificate as well.
The length of our templates rsa key might be different than yours, and your ending file size MUST be the same as your starting file size(the template is 12,582,912 bytes). There are a bunch of null characters in the template after --END KEY--- you might need to add or remove some to correct this! Just click on one and press the delete key if you have to
Now the only thing you have to do is fix your mac. In your new wimax partition file, text search for 00:18:41:81 to Replace that mac with your mac but subtract 1 from the last digit(if your mac was 00:23:76:EC:214 put 00:23:76:EC:213).
Replace the first 2 of the 3 instances with your mac -- minus 1. (If it ends on a letter, B would become A, C would become B, etc.
The last instance of your mac, put the actual mac address with nothing subtracted as it appears on the sticker under your battery.
Once you have saved the file.. name it something like wimax_fixed_resized.img and copy it to your sdcard.
Boot to fastboot and run "fastboot erase wimax"
Reboot to your recovery and adb shell in.
type "mount /sdcard" so you can run flash_image properly.
Run flash_image wimax /sdcard/wimax_fixed_resized.img
(or whatever you named it)
Profit!
One highly recommended addition to this is to use the correct ROM base version while you do this for testing if your wimax restored correctly. Quite often firmware/wimax mismatches will cause things to not auto connect, or various odd issues (true story)
Thanks for writing this up - I was planning on doing it at some point with a full guide on how to backup and restore the whole nine yards, but this will do in the meantime for people who want to restore things.
At first I thought this was for people who had lost their own RSA keys lol.
Great tutorial nonetheless.
haxt said:
I was one of the people that did the initial backup methods (telling you how to backup your certificate and rsa keys) or using cat which doesn't actually backup your wimax.img properly. After hours of playing around in a hex editor I finally got my 4g working again, and i'll explain how
****EDIT****
I added a hex converter you can use for your rsa key if you are too lazy to find one on google. I say to use hex instead of text replace because it's safer in regards to \n's
I was too lazy to make a gui for it but its haxt.net/evohex.php?rsa=yourrsa&cert=yourcert [obviously replace it with your 2 values]
***********
Note - this won't work for anybody who actually has no idea what their RSA keys/certificate is.
So there are a few things you need first.
1. Your phones wimax mac address (take out your battery and look at the sticker)
2. Your RSA private key
3. Your Certificate
4. A wimax.img from an evo that has has an intact wimax partition(borrow a friends nandroid backup).
To simplify, use XVI32 freeware hex editor. If you search "BEGIN" you will see begin rsa key and begin certificate. You need to copy these values for later use.
Next, open up the backup you got from a friend and save the certificate/rsa information between the ---BEGIN --- and ---END --- tags.
Now that you have the rsa key/certificate for both it is time to run a str_replace.
(Make sure to look at the original file size of the backup you got of someones wimax.img. Once you are done the file size needs to be the same).
Take YOUR rsa key and convert it to hexidecimal.. you can find tons of sites that will do this .. just google convert string to hex (it will be a long string of stuff like 4D 49 49 44 6B 44 43 43 41 6E 69 67 41 77 49 42 41 67 49 51).
Next, take your buddies RSA key and convert it to hex as well.
Open a copy of your buddies backup now and this will be used as the template for your new wimax partition. Hit search -> replace. For the hex to search paste your buddies RSA key you converted to hex.. and for the replace with.. put the hex of your rsa key.
Repeat these last steps for the certificate as well (convert to hex and replace your buddies certificate with your own certificate text)
REMEMBER!!!! if the length is not the same of the certificate/key you can fix this by adding or removing the blank bytes at the end of the ---END RSA or --END CERTIFICATE area.
You should be able to save the file now and the size should be exactly the same as the original backup you borrowed.
Now the only thing you have to do is fix your mac. In your new wimax partition file, search for 00: to locate the mac address of your buddies partition. You might find a few random ones first but just look at the surrounding text to know it's their mac. Replace that string with your mac but subtract 1 from the last digit(if your mac was 00:23:76:EC:214 put 00:23:76:EC:213).
Replace the first 2 of the 3 instances with your mac -- minus 1. (If it ends on a letter, B would become A, C would become B, etc.
The last instance of your mac, put the actual mac address with nothing subtracted as it appears on the sticker under your battery.
Once you have saved the file.. name it something like wimax_fixed_resized.img and copy it to your sdcard.
Boot to fastboot and run "fastboot erase wimax"
Reboot to your recovery and adb shell in.
type "mount /sdcard" so you can run flash_image properly.
Run flash_image wimax /sdcard/wimax_fixed_resized.img
(or whatever you named it)
Profit!
Click to expand...
Click to collapse
is there any way to break it down anymore? and do you have to use a buddies backup? i have my RSA keys i made a backup a while ago... cant you just use one of your old backups and replace wimax? thanks in advance and thanks for the post.
Great post, had been wondering how to actually restore the wimax keys once you had 'em.
Question for any devs that may have them: are the RSA keys generated by or linked to MAC ID somehow? Would it be possible to use backups of an one phone's keys with the another phone's baseband MAC ID?
I'll try to clean up the post to make it an easier read tomorrow but if you have an intact backup of your wimax image you can just restore it with flash_image or fastboot.. or just restore the nandroid backup. This is just for people that have the key itself but the image they have might be corrupted. If it would help everyone I can take a working wimax.img and remove the RSA keys so you can just download it as a template and put your keys in
I updated the thread.. has a template file in there too with dummy certs and keys to make it easier for you guys.
This is a big deal bro. Thanks!
Has anyone been having issues connecting to 4G? I've been having some issues where it authenticates, launches then disconnects. My keys are present but not really sure what else to do from here.
NYCHitman1 said:
Has anyone been having issues connecting to 4G? I've been having some issues where it authenticates, launches then disconnects. My keys are present but not really sure what else to do from here.
Click to expand...
Click to collapse
Does it get to the "Obtaining IP Addres..." then moves to "Disconnected"?
Caanon said:
Does it get to the "Obtaining IP Addres..." then moves to "Disconnected"?
Click to expand...
Click to collapse
That's exactly what it does.
Sent from my PC36100 using XDA App
NYCHitman1 said:
That's exactly what it does.
Click to expand...
Click to collapse
Good news and bad news...
Bad news is that I wasn't ever able to fix it. I tried flashing up and down all the radios I could find, trying all the radio/rom combos I could think of. RUU'd even, and no dice.
Good news is that it might not have actually been your fault. I ended up biting the bullet and going to the Sprint store to explain what was going wrong. The tech looked at it and said, "Let me guess, this happened after an update, right?" Apparently this is a "known issue" to Sprint, and it actually ended up happening to the tech herself about a week before it happened to mine. They ordered me a refurb no charge (I have insurance, but didn't have to use it I don't think) and got it a few days later. New one connects to 4g no problem, and 4g on CM works like a charm (thanks toast and shin!).
Caanon said:
Good news and bad news...
Bad news is that I wasn't ever able to fix it. I tried flashing up and down all the radios I could find, trying all the radio/rom combos I could think of. RUU'd even, and no dice.
Good news is that it might not have actually been your fault. I ended up biting the bullet and going to the Sprint store to explain what was going wrong. The tech looked at it and said, "Let me guess, this happened after an update, right?" Apparently this is a "known issue" to Sprint, and it actually ended up happening to the tech herself about a week before it happened to mine. They ordered me a refurb no charge (I have insurance, but didn't have to use it I don't think) and got it a few days later. New one connects to 4g no problem, and 4g on CM works like a charm (thanks toast and shin!).
Click to expand...
Click to collapse
Damn! I really don't want to go through all that trouble right now. Lol, eff it. I'll wait for the next best thing.
Sent from my PC36100 using XDA App
Question, wouldn't it be easier to just backup the existing wimax.img and restore it if/when needed using recovery? Or does this method address something that can't be done via recovery?
Sticky
Sent from my HTC EVO 4G running Frost 4.0 using XDA app.
i am confused when it come to this. is there a video or something. i know for a fact that i lost my RSA keys and i have used the "WiMAX Keys Checker" to check it and it say they are missing. but during my first initial backup i see the "img" file in there. i can't connect to 4g anymore so i am guessing for some reason it can't read it when i restore to the old version of my evo or when i change rom. i need some serious slow help
ericvbp21 said:
i am confused when it come to this. is there a video or something. i know for a fact that i lost my RSA keys and i have used the "WiMAX Keys Checker" to check it and it say they are missing. but during my first initial backup i see the "img" file in there. i can't connect to 4g anymore so i am guessing for some reason it can't read it when i restore to the old version of my evo or when i change rom. i need some serious slow help
Click to expand...
Click to collapse
Flash the WiMAX radio again and Update Profile, it will grab the keys from the carrier based on your phone's programming information
aph said:
Flash the WiMAX radio again and Update Profile, it will grab the keys from the carrier based on your phone's programming information
Click to expand...
Click to collapse
i flashed the wimax radio and updated the profile but it still does the same thing. any idea? I do have the RSA keys so i don't know why it doesn't grab 4G....
Well I thought I lost my RES keys after doing haxts back up, after I checked using Explorer and there was no res_OEM.key file. I did the back up again, still no file. I used Astro on my phone and the files where there. (res_OEM.key 4,575 KB & res_OEM.keycat 16,863 KB. Now a day later and the files show up using Explorer? I did do a winmax back up before I did anything and that is still there. Bottom line, if you think you lost you res keys after doing a backup, check it with a file manager program on your phone.
ericvbp21 said:
i am confused when it come to this. is there a video or something. i know for a fact that i lost my RSA keys and i have used the "WiMAX Keys Checker" to check it and it say they are missing. but during my first initial backup i see the "img" file in there. i can't connect to 4g anymore so i am guessing for some reason it can't read it when i restore to the old version of my evo or when i change rom. i need some serious slow help
Click to expand...
Click to collapse
I have my keys (WiMAX Keys Checker) but i can only connect when i do a restore of the orginal EVO rom from backup, but on all other roms(elite II for now) it just saids searching and never conects. Please help
edit drop and broke the phone that im talking about.. got new one thur insurance and rooted it and and 4 g works with no problme wonder what i ddi when i root the first phone
I've noticed since upgrading my Droid X to Gingerbread that many websites that were previously fooled by setting the User Agent (in Dolphin HD) to "desktop" are no longer fooled and can now detect that I'm on a mobile device. This can be quite irritating as the mobile version of many sites is horrible.
To see if this article pertains to you, if you're set for a desktop user agent string, go to http://www.bbc.co.uk and see if you get the mobile version of the page or the desktop version. If you get the mobile version despite your user agent setting, this hack may help you.
When this first happened to me I decided to find out how the sites were detecting the fact that I'm on a mobile device. Generally a website only knows what you tell it about yourself, and what you tell it about yourself is 100% in the HTTP headers your browser sends (or that get added by a proxy server if you use one). So the first logical place to look was to see what all headers the browser was sending. Note: for any who might object that it also knows things about you by your cookies, your cookies are actually sent as HTTP headers as well.
I have a CGI script on one of my web servers that I use to see what all headers my browser is passing. There are plenty such scripts/sites on the web -- here is a decent one (it's not mine) if you want to see what your browser sends. Examining the headers, one stuck out like a sore thumb:
Code:
HTTP_X_WAP_PROFILE='http://uaprof.vtext/com/mot/mb810/mb810.xml'
Geez, that's a pretty dead giveaway isn't it? I checked a phone running FroYo and it does not send that header, so that further confirms this is the header these sites use to detect me as a mobile (since they don't detect me as a mobile under FroYo and do under Gingerbread).
I then Googled HTTP_X_WAP_PROFILE and found numerous coding resources where they suggest looking to see if that header exists and/or is set to anything in order to detect mobile browsers. Bingo.
Great - so how to get rid of it? My first thought is that since the header is clearly identifying me as a Droid X (MB810), there has to be something in the phone that is providing the data. Since I observed that the header is present whether I access the net via WiFi or via 3G, that further confirmed that this is all happening in the phone and not being added by Verizon in transit.
The first sensible place to look was /system/build.prop. Turns out that the first sensible place to look was the right place to look as I found this line:
Code:
ro.mot.hw.uaprof='http://uaprof.vtext/com/mot/mb810/mb810.xml'
Well, that's about as perfect as you could ask for. Not knowing if the phone might be touchy about completely removing this setting, my first attempt was to change the line to read like this:
Code:
ro.mot.hw.uaprof=''
I found that you must reboot the phone for the setting to take effect (no real surprise there). Unfortunately, afterward, when I examined the headers being sent by the browser, they now contained this:
Code:
HTTP_X_WAP_PROFILE=''
With that setting, the various websites still detected me as a mobile browser (which you would expect). Next I tried changing the build.prop to this:
Code:
ro.mot.hw.uaprof=
* Note - there is nothing after the equal sign - not a space or anything, just a carrriage return.
This (pleasantly) resulted in the HTTP_X_WAP_PROFILE header being completely absent -- the ideal outcome. Happily, the various websites that were detecting me as a mobile no longer did. Success!
In the interest of being thorough, I tested just removing the ro.mot.hw.uaprof setting altogether (by commenting out the line). I figured that probably was not the best plan, but I wanted to see what would happen. When I did that, the following header was the result:
Code:
ro.mot.hw.uaprof='http://uaprof.motorola.com/phoneconfig/MotoMB200/profile/MotoMB200.rdf'
Interesting default value -- and of course I was again identifiable as a mobile device.
So, the fix for this is pretty simple. The exact property that needs to be modified in your build.prop would of course vary if you're not running a Motorola build, but I'd expect it to be readily identifiable. Of course you have to be rooted to do this, and of course you should make a backup copy of your build.prop before you modify it, and of course you should think about what your fallback recovery is going to be if you foul up your build.prop and end up in a boot loop or something. Can you boot into Recovery and then fix the file with ADB, etc. -- it all depends on how your phone is set up.
For those that like step-by-step, here's precisely what I did:
Open Root Explorer (or other "root aware" editor)
Navigate to /system
Mount system as R/W
Open build.prop in text editor
Find the ro.mot.hw.uaprof line
Put a # at the beginning of the existing line (to make it into a comment)
Insert a new line below the existing line that says "ro.mot.hw.uaprof=" (without the double quotes -- no characters after the equal sign)
Save and exit editor
Mount system as R/O
Reboot phone
By doing it this way I end up with a backup copy of the original string in case I want to easily put it back. Root explorer automatically saves the original build.prop as build.prop.bak, but if you're really cautious you might want to actually make a copy of the file to your SD card or something.
At this point, in Dolphin HD, with my user agent string set to Desktop, all of the web sites that had begun seeing me as a mobile device now serve the normal desktop page (as desired). If I want to see the mobile version (for some reason) I can just switch Dolphin HD back to Android mode (user agent string) and then I get the mobile version.
Hope this helps someone. Sorry it was so long -- almost everything I write up is.
P.S. If you do this successfully on a non-Motorola phone, post here and let others know.
firstly,, BIG THANKS
I am running a GB2.3.3build.596 P3D 2file root DroidX..
when i open ROOT EXPLORER in r/w mount and open the build.prop i can not type anything..and this mobile site only crap was the reason i took 2 days of forum reading at 3 forums before i went ahead and sbf'd back to froyo from a stock Verz 2.3.3GB to then root ,and then to install the 2 P3D files to have a .596 build GB rooted phone
any suggestions, maybe another editor ware? total newb
Hey all,
Ive been playing with AutoKiller since it came out, and its a fabulous way to manage memory in Android. However, recently I found a mod that not only tweaked the lowmemkiller (android memory management) but also reorganized the service\app priority for best responsiveness.
I started this thread as a forum to discuss the different settings for the SuperCharger script, AutoKiller, and anything that modifies android's memory management. Ive included the default script along w/ a few mods for the different launcher versions. I am leaving the details scarce, as I want you to look at the original thread of instructions and issues resolution.
I am personally using the "Hard-To-Kill" launcher feature tweaked to recognize ADW EX (u just change the name of the launcher in the beginning of the script to com.adw.launcher, or whatever your launcher package name is) and MegaRAM (512+) option and have had good results for the past few hours.
Install Instructions
Install Script Manager from the Android Market (Market Link)
Select the script for your launcher (Ive attached a few)
Long-press and open as a "script\executable"
Select "open as root"
Click Save
Click Run
Follow Instructions & refer to orig thread for details
Share feedback here for others (Please try a setting for at least 12-14 hours before deciding its good\bad, tweaks like this CAN cause slow down after a number of hours of use, yet be incredibly responsive initially.)
Package name for Popular Launchers
ADW EX - org.adwfreak.launcher (attached, remove txt extension)
ADW Launcher - org.adw.launcher (attached, remove txt extension)
Launcher Pro - com.fede.launcher
Go Launcher EX - com.gau.go.launcherex (Thanx richua!)
Stock Gingerbread Launcher (or CM's pre-installed ADW) - com.android.launcher
Try it out, and see how it works for you. Please visit the original thread as it is VERY informative, much more than I could be, and it contains much better instructions to get this up and running
Link: Original Thread
Help???!!! "I dont get it", "I'm getting some strange error in Scripting Manager", "WTF are you talking about?" aka Issues\Questions
There is a step-by-step walk through located here (thanks ruchua!), but this is still experimental and isnt ready for "mass consumption", hence why I was slim on details in the OP. If you REALLY want to try these tweaks but dont want to wrestle with the script, download AutoKiller, donate a few bucks so you get access to the advanced kernel tweaks, enable it on optimum or aggressive, enable all advanced tweaks, and it should have a similar effect w/o all the scripting action.
Enjoy and have fun!
Nice find.
Can't get the files to download.. via the (XDA Premium) app its saying can't open file - via desktop, download unsuccessful. I was anxious to try the files you've provided cause I noticed ADW EX on the name of the files and its not titled that in the original thread.
Sent from a Nexus X by LG
eViL D: said:
Nice find.
Click to expand...
Click to collapse
I believe I was the one to point this out to zimphismonger over in faux's thread when I seen zimphishmonger asking about a bug in AutoKiller with faux's latest Kernel. No big deal, its just I've been messing with this thing and been unsuccessful with it. At least somebody knows how to tweek it.
Sent from a Nexus X by LG
DJ "suMo* said:
Can't get the files to download.. via the (XDA Premium) app its saying can't open file - via desktop, download unsuccessful. I've been up and down the oringinal thread, the visual walk through, and cannot figure this out for nothing. I was anxious to try the files you've provided cause I noticed ADW on the name of the files and its not titled that on the original thread. I've been messing with this for the past week and can't get it to run, its just too complicated for me.
Sent from a Nexus X by LG
Click to expand...
Click to collapse
This is def an advanced tweak that requires some knowledge of Android and app development. If you can follow the walkthrough on the original page, thats great. If not, I would suggest AutoKiller Donate as it does a lot of the same things w/o the scripts.
Please share your thoughts suggestions, experience etc, as Im interested in how this will affect different "style" of users: Id classify myself as a app-heavy user with ~200 apps, while others are much less. Im interested in a memory management setting that will help both sides.
Ive been playing w/ the HTK launcher setting and the 2 "MegaRAM" settings to see how it affects general responsiveness, UI, refresh, and if any apps get kicked out of ram (especially messaging and launcher).
DJ "suMo* said:
I believe I was the one to point this out to zimphismonger over in faux's thread when I seen zimphismonger asking about a bug in Autokiller with faux's latest Kernel. No big deal, its just I've been messing with this thing and been unsuccessful with it. At least somebody knows how tweek it.
Click to expand...
Click to collapse
The original author of the thread linked in the OP started talking about this (although a little aggressively, if you ask me...but whatever), but I decided to take a peak at the code anyway. This is a cool script, but it is by no means (end)user friendly and could use some more documentation. The possible bug\glitch between AutoKiller and Faux's kernel (if it exists, I think its a generalized bug) is that enabling the advanced tweak setting for IO scheduler which tells it our phone has no spinning hard disk (all flash memory) causes an immediate reboot back to the kernel's "baked-in" LG logo (the purple one). Disabling that feature fixed that issue, but the "SuperCharger" script has a similar option that ill most likely have a similar result.
Tackling a few points at once here...
The process name for GO Launcher is com.gau.go.launcherex in case anyone else uses that.
Inside GO Launcher settings, there's an option for "system persistent" that I unchecked. There's no explanation as to what that setting does but everything is running smoothly so far. Also in GO Launcher settings as well as LauncherPro (maybe others too but those are the two I use) there's a setting to prevent FC when running out of memory. I kept that checked by default.
Per the dev's suggestion in Faux's thread, my setup is MegaRAM 1 and HTK Launcher. For the past 10 minutes I've been trying to make things lag and frankly, things just aren't lagging. This is much better than any setup I tried with Autokiller, which in its own right is also a very good app. I unchecked all settings in Autokiller so it wouldn't interfere; I will probably uninstall it soon.
The V8 beta for this SuperCharger script and Autokiller's advanced tweaks both have a setting for kernel scheduling, which as some of you may know leads to booty loops. Autokiller was updated today with a change that tries to prevent that but I have not tried it since I hate booty loops and don't even want to risk messing up the great setup I have now. The V8 beta has also been rewritten with the scheduler tweaks commented out. Hopefully this issue can get sorted out. I run the scheduler tweak on my N1 and can't say that it's helping a lot, but it certainly doesn't seem to be hurting.
Seriously, the ROI on running this script is immense. Read the linked OP carefully, follow the directions, and you'll have what feels like a new phone in a few minutes.
@zimphishmonger, I don't know if you follow Paul O'Brien of MoDaCo, but he put out a link yesterday on Twitter for an apk BetterBatteryStats for Gingerbread devices. http://www.cri.ch/sven/doku.php/computing/android/betterbatterystats Have you checked it out? I got it installed and I'm not 100% sure what its doing. I figured it was related to this post being it has to do with utilizing..
Sent from a Nexus X by LG
I got no idea what to do... the more I read the more confused I get. Links lead to other links that lead to other links. I wish someone would make a flashable or something. ;-)
Sent from my LG-P999 using XDA App
siresh said:
I got no idea what to do... the more I read the more confused I get. Links lead to other links that lead to other links. I wish someone would make a flashable or something. ;-)
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
agreed!
FWIW, the OP is crazy confusing for non-techies. Oh, the beauty of a step-by-step laundry list!
(Or a flashable...)
Here's a list of what I did to get up and running within a few minutes.
Make a nandroid.
Download Script Manager https://market.android.com/details?id=os.tools.scriptmanager
If you use ADW or ADW EX as a launcher, download the appropriate file to your SD card from the OP of this thread. Continue to step 6.
If you use LauncherPro/LauncherPro Plus or GO Launcher, download the text file from OP of the linked thread titled "V6_SuperCharger_for_Android-update8.sh.txt" either to your phone (if you have a text editor) or to your computer (if you don't). Here's the link: http://forum.xda-developers.com/attachment.php?attachmentid=661892&d=1311292674
Open the text file. If you have a "find" feature, look for where it says "com.android.launcher". If you're on your phone and/or don't have a "find" feature, scroll down (not too far from the top) to a line that starts with "launcheradj=" and that's where you'll find "com.android.launcher". Replace com.android.launcher with either com.fede.launcher if you're using LP/LPP or com.gau.go.launcherex if you're using GO Launcher. Make sure you don't delete that space between "pidof" and "com.whateverYou'reUsing", and don't delete that tick mark right after it. Save and exit. If you did this on your computer, upload this file to your phone. (Note: if you are using a launcher not described here, you'll have to find the process name yourself and enter it as instructed above)
Open Script Manager and locate where you just stored that file. Long press on it, select "Open As ...", select "Script/Executable." In the box that pops up, check "Run as root" and then hit "Run" in the top left. The script will now be run. The first prompt will be for scrolling speed. Touch the screen to bring up the soft keyboard. Type the number corresponding to which scroll speed you like and hit enter.
You are now inside the script. IF YOU DID NOT READ ANY OF THE LINKED THREAD, type 8 at the main menu prompt and hit enter on the keyboard, wait for it to do some work and automatically return to the main menu prompt, then type 11 and hit enter and wait, then hit 17 and enter and wait. 17 is the exit command so you'll now see on the top left a button that says "Close." Hit that and then back out of Script Manager, then go to step 9.
If you did read the linked thread, you'll know a little bit more about what each option is. Feel free to experiment. To select an option, type the number of the option and hit enter on the keyboard. Current recommendations are both 8 and 11. Once you are done, type 17 followed by an enter, then hit "Close" in the top left and back out of Script Manager.
Provided you followed the instructions and did not encounter any weird errors in any step, the settings you selected are now active. Nothing else is required. Enjoy your snappy new setup.
I rolled back my settings and typed this list up as I started over from scratch so this almost literally is each and every step I took to get things running. If you have download errors, I suggest not using the XDA app and downloading instead from a standard browser. Make sure you are clicking on the right file. If you didn't read the linked thread and are unsure about proceeding, you should read the linked thread. If you read the linked thread and still are unsure, download the Autokiller app and choose the "optimum" setting there.
So do we change anything in the script to match our launcher??
fcisco13 said:
So do we change anything in the script to match our launcher??
Click to expand...
Click to collapse
Check steps 3 and 4 in my post right above yours.
richua said:
Here's a list of what I did to get up and running within a few minutes.
Make a nandroid.
Download Script Manager https://market.android.com/details?id=os.tools.scriptmanager
If you use ADW or ADW EX as a launcher, download the appropriate file to your SD card from the OP of this thread. Continue to step 6.
If you use LauncherPro/LauncherPro Plus or GO Launcher, download the text file from OP of the linked thread titled "V6_SuperCharger_for_Android-update8.sh.txt" either to your phone (if you have a text editor) or to your computer (if you don't). Here's the link: http://forum.xda-developers.com/attachment.php?attachmentid=661892&d=1311292674
Open the text file. If you have a "find" feature, look for where it says "com.android.launcher". If you're on your phone and/or don't have a "find" feature, scroll down (not too far from the top) to a line that starts with "launcheradj=" and that's where you'll find "com.android.launcher". Replace com.android.launcher with either com.fede.launcher if you're using LP/LPP or com.gau.go.launcherex if you're using GO Launcher. Make sure you don't delete that space between "pidof" and "com.whateverYou'reUsing", and don't delete that tick mark right after it. Save and exit. If you did this on your computer, upload this file to your phone. (Note: if you are using a launcher not described here, you'll have to find the process name yourself and enter it as instructed above)
Open Script Manager and locate where you just stored that file. Long press on it, select "Open As ...", select "Script/Executable." In the box that pops up, check "Run as root" and then hit "Run" in the top left. The script will now be run. The first prompt will be for scrolling speed. Touch the screen to bring up the soft keyboard. Type the number corresponding to which scroll speed you like and hit enter.
You are now inside the script. IF YOU DID NOT READ ANY OF THE LINKED THREAD, type 8 at the main menu prompt and hit enter on the keyboard, wait for it to do some work and automatically return to the main menu prompt, then type 11 and hit enter and wait, then hit 17 and enter and wait. 17 is the exit command so you'll now see on the top left a button that says "Close." Hit that and then back out of Script Manager, then go to step 9.
If you did read the linked thread, you'll know a little bit more about what each option is. Feel free to experiment. To select an option, type the number of the option and hit enter on the keyboard. Current recommendations are both 8 and 11. Once you are done, type 17 followed by an enter, then hit "Close" in the top left and back out of Script Manager.
Provided you followed the instructions and did not encounter any weird errors in any step, the settings you selected are now active. Nothing else is required. Enjoy your snappy new setup.
I rolled back my settings and typed this list up as I started over from scratch so this almost literally is each and every step I took to get things running. If you have download errors, I suggest not using the XDA app and downloading instead from a standard browser. Make sure you are clicking on the right file. If you didn't read the linked thread and are unsure about proceeding, you should read the linked thread. If you read the linked thread and still are unsure, download the Autokiller app and choose the "optimum" setting there.
Click to expand...
Click to collapse
This is really good...super clear writing and easy to follow instructions! Thanks for making it so easy for us!!
So does this make a big difference on our devices? I have EB 2.3.5 with faux's kernel and at 1.1 ghz. It's already pretty fast. The before and after benchmark comparison on the OP don't seem to be different. I would like some feedback before I do this let me know! I'll do it in the morning if it's really worth it.
Shaddy-Z. said:
So does this make a big difference on our devices? I have EB 2.3.5 with faux's kernel and at 1.1 ghz. It's already pretty fast. The before and after benchmark comparison on the OP don't seem to be different. I would like some feedback before I do this let me know! I'll do it in the morning if it's really worth it.
Click to expand...
Click to collapse
Overall, it has made performance a bit better. I use the same ROM and settings as you, and I agree it's already very good...but these settings are nice. I'm not sure this process can be undone so easily, so it's a valid point you make. But, fwiw, I followed the instructions above and am noticing a difference in performance.
richua said:
Here's a list of what I did to get up and running within a few minutes.
Make a nandroid.
Download Script Manager https://market.android.com/details?id=os.tools.scriptmanager
If you use ADW or ADW EX as a launcher, download the appropriate file to your SD card from the OP of this thread. Continue to step 6.
If you use LauncherPro/LauncherPro Plus or GO Launcher, download the text file from OP of the linked thread titled "V6_SuperCharger_for_Android-update8.sh.txt" either to your phone (if you have a text editor) or to your computer (if you don't). Here's the link: http://forum.xda-developers.com/attachment.php?attachmentid=661892&d=1311292674
Open the text file. If you have a "find" feature, look for where it says "com.android.launcher". If you're on your phone and/or don't have a "find" feature, scroll down (not too far from the top) to a line that starts with "launcheradj=" and that's where you'll find "com.android.launcher". Replace com.android.launcher with either com.fede.launcher if you're using LP/LPP or com.gau.go.launcherex if you're using GO Launcher. Make sure you don't delete that space between "pidof" and "com.whateverYou'reUsing", and don't delete that tick mark right after it. Save and exit. If you did this on your computer, upload this file to your phone. (Note: if you are using a launcher not described here, you'll have to find the process name yourself and enter it as instructed above)
Open Script Manager and locate where you just stored that file. Long press on it, select "Open As ...", select "Script/Executable." In the box that pops up, check "Run as root" and then hit "Run" in the top left. The script will now be run. The first prompt will be for scrolling speed. Touch the screen to bring up the soft keyboard. Type the number corresponding to which scroll speed you like and hit enter.
You are now inside the script. IF YOU DID NOT READ ANY OF THE LINKED THREAD, type 8 at the main menu prompt and hit enter on the keyboard, wait for it to do some work and automatically return to the main menu prompt, then type 11 and hit enter and wait, then hit 17 and enter and wait. 17 is the exit command so you'll now see on the top left a button that says "Close." Hit that and then back out of Script Manager, then go to step 9.
If you did read the linked thread, you'll know a little bit more about what each option is. Feel free to experiment. To select an option, type the number of the option and hit enter on the keyboard. Current recommendations are both 8 and 11. Once you are done, type 17 followed by an enter, then hit "Close" in the top left and back out of Script Manager.
Provided you followed the instructions and did not encounter any weird errors in any step, the settings you selected are now active. Nothing else is required. Enjoy your snappy new setup.
I rolled back my settings and typed this list up as I started over from scratch so this almost literally is each and every step I took to get things running. If you have download errors, I suggest not using the XDA app and downloading instead from a standard browser. Make sure you are clicking on the right file. If you didn't read the linked thread and are unsure about proceeding, you should read the linked thread. If you read the linked thread and still are unsure, download the Autokiller app and choose the "optimum" setting there.
Click to expand...
Click to collapse
Thanx much easier to understand!!! Will this work on 2.3.3 ota rom rooted.?)
Sent from my LG-P999 using XDA App
richua said:
Here's a list of what I did to get up and running within a few minutes.
Make a nandroid.
Download Script Manager https://market.android.com/details?id=os.tools.scriptmanager
If you use ADW or ADW EX as a launcher, download the appropriate file to your SD card from the OP of this thread. Continue to step 6.
If you use LauncherPro/LauncherPro Plus or GO Launcher, download the text file from OP of the linked thread titled "V6_SuperCharger_for_Android-update8.sh.txt" either to your phone (if you have a text editor) or to your computer (if you don't). Here's the link: http://forum.xda-developers.com/attachment.php?attachmentid=661892&d=1311292674
Open the text file. If you have a "find" feature, look for where it says "com.android.launcher". If you're on your phone and/or don't have a "find" feature, scroll down (not too far from the top) to a line that starts with "launcheradj=" and that's where you'll find "com.android.launcher". Replace com.android.launcher with either com.fede.launcher if you're using LP/LPP or com.gau.go.launcherex if you're using GO Launcher. Make sure you don't delete that space between "pidof" and "com.whateverYou'reUsing", and don't delete that tick mark right after it. Save and exit. If you did this on your computer, upload this file to your phone. (Note: if you are using a launcher not described here, you'll have to find the process name yourself and enter it as instructed above)
Open Script Manager and locate where you just stored that file. Long press on it, select "Open As ...", select "Script/Executable." In the box that pops up, check "Run as root" and then hit "Run" in the top left. The script will now be run. The first prompt will be for scrolling speed. Touch the screen to bring up the soft keyboard. Type the number corresponding to which scroll speed you like and hit enter.
You are now inside the script. IF YOU DID NOT READ ANY OF THE LINKED THREAD, type 8 at the main menu prompt and hit enter on the keyboard, wait for it to do some work and automatically return to the main menu prompt, then type 11 and hit enter and wait, then hit 17 and enter and wait. 17 is the exit command so you'll now see on the top left a button that says "Close." Hit that and then back out of Script Manager, then go to step 9.
If you did read the linked thread, you'll know a little bit more about what each option is. Feel free to experiment. To select an option, type the number of the option and hit enter on the keyboard. Current recommendations are both 8 and 11. Once you are done, type 17 followed by an enter, then hit "Close" in the top left and back out of Script Manager.
Provided you followed the instructions and did not encounter any weird errors in any step, the settings you selected are now active. Nothing else is required. Enjoy your snappy new setup.
I rolled back my settings and typed this list up as I started over from scratch so this almost literally is each and every step I took to get things running. If you have download errors, I suggest not using the XDA app and downloading instead from a standard browser. Make sure you are clicking on the right file. If you didn't read the linked thread and are unsure about proceeding, you should read the linked thread. If you read the linked thread and still are unsure, download the Autokiller app and choose the "optimum" setting there.
Click to expand...
Click to collapse
Thanks for the detailed how-to. Please be sure to uninstall and\or disable autokiller to make sure they arent conflicting, as that will def screw with your test results. Also, please run this for at least 24 hours to get a real good idea how it performs after a number of hours. This is a major mod to androids memory management and Im trying to discover if there are any side effects. Thanks for your feedback and testing results. Please keep sharing.
siresh said:
I got no idea what to do... the more I read the more confused I get. Links lead to other links that lead to other links. I wish someone would make a flashable or something. ;-)
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Wanted testing from people who knew what was going on internally, as this is pretty experimental, but this is fine too. Feedback is feedback Try a few different memory settings and see how they work, both MegaRAM and multitasking settings.
Erislover said:
Overall, it has made performance a bit better. I use the same ROM and settings as you, and I agree it's already very good...but these settings are nice. I'm not sure this process can be undone so easily, so it's a valid point you make. But, fwiw, I followed the instructions above and am noticing a difference in performance.
Click to expand...
Click to collapse
This can easily be undone by running the script again, I think its option 8 to "unsupercharge". Thy options should disable all the tweaks made by the script (you did nandroid before, right??).
FEEDBACK: Tested MEGARAM Option 2 (#9 on the script) and it was too aggressive, imo. We don't need that much free ram anyways, its a waste. Testing MEGARAM 1 + HKL (#8 on script) today, and we'll see how it works.
Im using it now.... this thing is blazing.... feels like overclocking.... whats it doing really?
Sent from my Transformer TF101 using XDA Premium App
KingDavid63 said:
Im using it now.... this thing is blazing.... feels like overclocking.... whats it doing really?
Sent from my Transformer TF101 using XDA Premium App
Click to expand...
Click to collapse
The SuperCharger script completely re-arranging how Android prioritizes its apps in memory (so which ones get killed and when), and tweaks how aggressive Android's internal memory management. Essentially, it is fending off apps from hogging memory and cpu time unnecessarily, and giving important apps like phone, launcher, sms highest priority. The 98kickasskernel script (if you are using it) is optimizing a lot of kernel settings are set improperly\not optimized (almost identical to Autokillers "advances system tweaks"). Thats a very dumbed down explanation, but it gets the idea across .
I just got promoted and was given an LG C900 to use as my cell phone. The previous owner wiped it and when I received it 7.0 was on it.
I did some googling and updated it to 7.5 so it's running Mango now. I'm trying to change the theme accent color. None of them are dark enough. How would I go about making the colors darker or setting some type of custom theme up?
Derple said:
I just got promoted and was given an LG C900 to use as my cell phone. The previous owner wiped it and when I received it 7.0 was on it.
I did some googling and updated it to 7.5 so it's running Mango now. I'm trying to change the theme accent color. None of them are dark enough. How would I go about making the colors darker or setting some type of custom theme up?
Click to expand...
Click to collapse
only if you have your device interop unlocked. then you can install Advanced Configuration Tool by Schaps and change accent colors.
Since you have an LG it's easy to unlock your phone following the instructions here. You install MFG tool and modify the registry. After that you can sideload the advanced config tool with for example this.
Thank you for the information. I checked that thread and it says this: This only works on devices that already have a developer-unlock!
My device does not have a developer-unlock so I cannot apply his methods
Derple said:
Thank you for the information. I checked that thread and it says this: This only works on devices that already have a developer-unlock!
My device does not have a developer-unlock so I cannot apply his methods
Click to expand...
Click to collapse
that is incorrect, which is good for you . Read the article carefully. if you have an LG device, and ONLY an LG device, you were able to follow the steps to completely unlock your phone at any time, even on Mango. Trust me. It's a known fact that LG devices have the LG MFG tool with built-in registry editor.
dial ##634# on your phone and press call. that will install the LG MFG tool (listed under you apps).
then follow these steps (a lot of steps, but trust me, well worth it, you can sideload homebrew applications and a lot more)
1. Prepare a cup of coffee
2. Open the MFG app. The password is: appmfg#*#
3. Go to Engineer Menu -> Other Settings -> Edit Registry
4. Set your ROOT PATH to "HKEY_LOCAL_MACHINE"
5. Set your input path to "\Comm\Security\LVMod"
6. Set your input key to "DeveloperUnlockState" and set to DWORD.
7. Leave input data box empty and tap "SET".
8. The output should be 0.
9. Now enter "1" in the inputbox and tap "SET".
10. The output should be 1.
11. Set your input path to "\Software\Microsoft\DeviceReg"
12. Set your input key to "PortalUrlProd" and set to DWORD.
13. Clear the input data box and hit "SET".
14. Output result should be "0".
15. Set your input key to "PortalUrlInt" and set to DWORD.
13. Clear the input data box and hit "SET".
14. Output result should be "0".
15. Set your input path to "\Software\Microsoft\DeviceReg\Install"
16. Set your input key to "MaxUnsignedApp" and set to DWORD.
17. Clear the input data box and hit "SET".
18. The output should be 0.
19. Now enter "2147483647" in the inputbox and tap "SET".
20. Output result should be "2147483647".
Thank you. I went ahead and followed those instructions and rebooted. Still installing Windows Phone SDK 7.1 so I can run Tom XAP Installer to see about installing the tools you linked before (hope I'm doing this right).
Derple said:
Thank you. I went ahead and followed those instructions and rebooted. Still installing Windows Phone SDK 7.1 so I can run Tom XAP Installer to see about installing the tools you linked before (hope I'm doing this right).
Click to expand...
Click to collapse
cool, this one (XapDeployX) doesn't require VS I believe. Either way, it's a good program to deploy programs because you can use this to update a program without deleting it's settings.
BTW. Advanced Config Tool will install itself in the Settings menu in case you are looking for it. It will throw and error message when you start it, but it will run. I highly recommend not to play with any of the other settings in the program because you can mess up your device. Only use the accent color part.
The program is sometimes picky and doesn't want to start. My experience was to use the deployer above and it worked (compared to another one I tried).
cheers
Ok so I followed the instructions, rebooted, connected to my computer, launched zune, and ran the xap file.
Tom XAP Installer tells me the following:
-Please make sure your phone was unlocked!
-Please make sure you connected device to PC and Zune launched
EDIT: I tried the link you gave me above and that worked great Any other XAP's I should look into? So far this thing is much cooler than the iPhone 3G I had. I just wish it had Citrix, VPN, and could see wifi networks with a hidden SSID
Derple said:
Ok so I followed the instructions, rebooted, connected to my computer, launched zune, and ran the xap file.
Tom XAP Installer tells me the following:
-Please make sure your phone was unlocked!
-Please make sure you connected device to PC and Zune launched
EDIT: I tried the link you gave me above and that worked great Any other XAP's I should look into? So far this thing is much cooler than the iPhone 3G I had. I just wish it had Citrix, VPN, and could see wifi networks with a hidden SSID
Click to expand...
Click to collapse
developers are currently rewriting their homebrew tools for Mango. Needs some time. There are a few useful homebew apps in this forum, e.g. r1ng3d to get your custom ringtones. For sideloading apps I highly recommend Phone7Market. You can search the marketplace, review screenshots and deploy with the same program. You can sideload some HTC OEM apps if you like as well. You can find more 3rdMarketPlace applications via this program. If you use the same deployer above you will be able to run them fine on the LG even though they are Samsung or HTC.
derausgewanderte said:
only if you have your device interop unlocked. then you can install Advanced Configuration Tool by Schaps and change accent colors.
Since you have an LG it's easy to unlock your phone following the instructions here. You install MFG tool and modify the registry. After that you can sideload the advanced config tool with for example this.
Click to expand...
Click to collapse
you're a very helpful guy, I have my phone unlocked and tweaked thanks to you
scoobysnacks said:
you're a very helpful guy, I have my phone unlocked and tweaked thanks to you
Click to expand...
Click to collapse
woah, you seem to be extremely helpful as well looking at your statistics . 2,523 posts and 484 Thanks since July 2011. how do you do that?
that's 21 posts per day
derausgewanderte said:
woah, you seem to be extremely helpful as well looking at your statistics . 2,523 posts and 484 Thanks since July 2011. how do you do that?
that's 21 posts per day
Click to expand...
Click to collapse
hahaha boredom really...
I've been on sick leave from work so I haven't had much else to do lol