So I wrote this guide a while ago for personal use and today I stumbled across a post on here from a couple of years ago about people trying to figure out how to change the APN settings on the Brigadier. I originally did this process to get the Brigadier running on the AT&T network, and sure enough it worked, but this can also be used to just change the APN settings for Verizon. So hopefully this can help some people.
Before you begin:
• Make sure phone has adequate battery life
• Have an SD Card with the apns.sh file and edited apns-conf.xml ready
• In the phone, go to Settings > Security and check the box that says “Unknown Sources” to allow the phone to install apps that are not from the Play Store. (This is for Kingroot)
apns-conf.xml
I originally found the apns-conf.xml in the /etc/ folder after I rooted the phone and used Droid Explorer. I just copied this to my desktop and made the changes for AT&T apn settings. I do not have the original apns-conf.xml file but I will attach my edited one.
This website has a nice list of a bunch of different networks APN settings: https://gist.github.com/imnuts/4319762
apns.sh
Now this part is optional, I just made the script so I didn't have to type out all the commands over and over when I was testing this process. If you choose not use the script, just enter the commands as they are below one by one. If you do choose to use this just open up notepad, paste it in, and save as "apns.sh"
Code:
mount -o remount,rw /system
cp /storage/sdcard1/apns-conf.xml /system/etc/
chmod 0644 /system/etc/apns-conf.xml
cat /system/etc/apns-conf.xml
ls -l /system/etc/apns-conf.xml
The Process
1. Download and install the Kingroot App (Download: http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461)
2. Once installed, run the App and root the phone. (No restart necessary)
3. Once rooted, go to the Play Store and download the following apps:
a. BusyBox (Author: Stephen (Stericson))
b. Terminal Emulator for Android (Author: Jack Palevich)4. Once installed, go back to the Kingroot App > Root Authorization and give both Apps root permissions
5. Launch the BusyBox App and click the “Install” button. It will install in a couple seconds
6. Insert the SD Card if you have not already done so
7. Launch the Terminal Emulator App and type the following in order exactly as displayed:
a. “su” – this gives you root permissions in the App
b. “sh /storage/sdcard1/apns.sh” –this executes a script to over write the APN file. (If you chose not to use the script, now is when you enter the commands one by one)
c. If done correctly, and no errors arise, the output should be the contents of the XML file (The ATT configuration should be seen at top of file contents), as well as the permissions “-rw-r--r—“8. Restart the phone
9. IF CHANGING CARRIERS: Before powering back on insert ATT/other carrier sim card and power on
10. Congrats! The phones APN settings are now changed. These changes will survive a factory reset too.
Warnings:
If you are changing the APN settings to be compatible with a different carrier, be warned I do not know if this will cause any issues down the line. I did not do too much intensive testing on it. I just saw it connected to the network, was able to load web pages, send texts and place calls. I did not use the phone for an extended period of time, but while testing it it seemed to work fine. The only annoying thing about switching carriers is that you will have an icon on your notification bar that says "Unknown Sim" or something along those lines. If you disable the Setup Wizard app, the pop up that shows up when you power the phone on will go away, but the little icon in your notification bar will remain there.
Anyway, I know the phone is getting kinda old now and people might not be using it too much, but I figured it's good to get the information out there anyway. I hope you enjoyed!
Related
Hey guys, so I noticed a DISTINCT LACK of an actual guide on how to get wireless tethering set up on the Droid DNA. This guide has been created here in order to help with this problem.
1. First, you MUST have root access.
2. Second, download and install the Wireless Tether APK below.
3. Next, open the app and press menu and then click settings.
4. From this screen, touch Device-Profile and then select Generic ICS/JB (wlan0).
5. After this, you'll want to make sure that Setup-Method is set to Auto.
6. From this point, make sure the check-boxes on the following are CHECKED(if not, check them obviously):
Wi-Fi-driver reload
MSS clamping
Routing fix
**i recommend not messing with other settings unless you know what they do**
7. At this point, you should now be able to go back to the main screen of the app and start the hotspot by touching the wifi symbol. (allow any prompts for superuser access)
8. If this does not work, then it probably means that you've either rooted your phone with a different root method than moonshine OR youve installed a different SU binary file OR updated your EXISTING SU binary file. You need to do some additional steps. They are pretty simple and are as follows:
1. You will need a file explorer with root access and the ability to remount as r/w (ive included one below)
2. Download the wireless tether tools.zip file
3. Extract the files to your sdcard.
4. Copy Superuser.apk to /system/app/ (if it prompts to remount and/or overwrite an existing file, press yes on both)
5. Copy SU to /system/xbin/ (again, if it prompts to remount and/or overwrite an existing file, press yes on both)
6. RESTART the phone. (not shutdown and turn back on but ACTUALLY press RESTART)
7. Once the device powers back on, go ahead and try and activate the wireless tether app (allow any prompts for superuser access)
I hope you guys have found this very helpful, LET ME KNOW IF THIS WORKS FOR YOU, please.
If you have any additional questions or need more help, please ask.
First Off to the Community thank you for the great work!!!
OTHER INFO:
1: How I got recovery.img with CLM (Clockwork Mod Recovery) to work with Android KitKat 4.4.2 update. I used the download links from pctech101 dump of SCH-R960 Android 4.2.2 from
http://teamuscellular.com/Forum/topic/5435-samsung-galaxy-mega/page-3#entry89801
I convert the recovery.img using Caboomi's_Recovery_img2tar_odin_maker so I could flash it using Odin 3.09. This will cause Knox counter.
OR DOWNLOAD IT FROM THIS THREAD for i9200
Galaxy Mega i9200 (melius3gxx)
http://forum.xda-developers.com/showthread.php?t=2588661
If we could get the drivers for the digitizer loaded for CWM Recovery would be awesome.
2. Then I could install the UPDATE-SuperSU-v2.02.zip from the external SD Card using CLM recovery to root Android from here:
http://download.chainfire.eu/452/SuperSU/
When you go to use SuperSU for the first time from your apps you might have to extract Superuser.apk from the zip file and reinstall it again from the SD Card and then go back to CLW recovery and reinstall the UPDATE-SuperSU-v2.02.zip.
To get into CLW recovery remember you have to hold the Power Button, Volume UP button and Home Button
3. Trying to setup SCH-R960 to be used with T-Mobile using the following instructions modifying the file build.prop file in the system folder using this tutorial (I know it states for Verizon Phones) :
http://www.internauta37.altervista.org/how-and-patch-fully-enable-gsm-verizon-cdma-phones-android
Still trying to get around the SCH-R960 not wanting to see the T-Mobile LTE SIM Card inserted. One thing if you change telephony.lteOnCdmaDevice from 1 to 0 your menu in for selecting Network Mode will disappear.
I added these settings to my build.prop
# To enabled hidden menu number 4636
ril.sales_code=LOL
ro.csc.sales_code=LOL
sys.hiddenmenu.enable=1
# GSM Setting for T-Mobile
ro.telephony.default_network=9
ro.ril.def.preferred.network=9
telephony.rilV7NeedCDMALTEPhone=false
telephony.lteOnGsmDevice=1
ro.cdma.home.operator.alpha=T-Mobile
ro.cdma.home.operator.numeric=310260
ro.gsm.sim.operator.alpha=T-Mobile
ro.gsm.operator.alpha=T-Mobile
ro.gsm.sim.operator.numeric=310260
ro.gsm.operator.numeric=310260
ro.gsm.sim.operator.iso-country=us
ro.gsm.operator.iso-country=us
4. I tried tinkering around unlocking the phone using DFS CDMA Tool v14.8.0.0 demo. I used SPC of 000000 and US Cellular PWD for the phone 2010031619780721 which worked stating unlocked but never could get the LTE T-Mobile SIM card to work.
For changing the PRL:
#Select Tabs
Programming ==> NAM ==> PRL:
#Under PRL select load (I loaded 3040 MetroPCS):
Select Load to load your PRL file
Then click the Write button to write the PRL to the phone.
#The PRL can be located here:
http://androidforums.com/metro-pcs/...ease-post-new-ones-here-when-available-3.html
#Or from here
http://forum.xda-developers.com/showthread.php?t=1880781
#Or from here
http://forum.xda-developers.com/misc.php?do=showattachments&t=1880781/
For data settings I changed:
#Select Tabs
Programming ==> Data ==> MODE:
#Under Mode Change:
HDR SCP force AT config: from RevA_MFPA to RevA_EHRDP
Hybrid preferred mode: from Disabled to Factory
Then click the Write button to update the settings
Here is a list of other Samsung 16 digit passwords:
http://www.howardforums.com/showthread.php/1664024-Samsung-16-digit-passwords
5. Trying to enter the hidden menus does not work with the dialer on this phone because it's disabled and you have to enable it by editing the file in the folder \efs\carrier\HiddenMenu opening it up and changing OFF to ON or using the app ShortCut Master and it will list all secret codes.
Using ShortCut Master
From the menu select: Secret Code Explorer
--Codes--
4636 = Hidden Menu
638 = Tethering Always on
0808 = Change USB Settings
7284 = Change USB Settings
27663368378 = Change Phone Settings
#Using 27663368378
[1] UMTS > DEBUG SCREEN > PHONE CONTROL > NETWORK CONTROL > BAND SELECTION to set Automatic
[2] CDMA > COMMON > NEXT PAGE > NEXT PAGE > PREF MODE SET to select GSM/WCDMA ONLY
[3] CDMA > CONTROL > CDMA BAND SELECT to select Automatic
When setting this it will enable in your Settings Connections Tab and then More Networks ==> Mobile Networks and if you select Network mode you will now see a lot of different Prefered network modes to choose from.
Access Point Names will also be accessible now so you can set up your APN. There is also another Network mode item which has four settings to choose from and Network operators is now accessible item to choose from.
After you reboot from doing the three settings above it might show that there is no network symbol. You will need to do option [1] again and the network bars should pop back on once you do this. And then your new settings for More Network Options should appear now.
I am not sure if this is in conjunction with updating your PRL too and it enabling these menu items. I first added a Sprint PRL and it added a roaming menu item under Settings Connections Tab and then More Networks. So if this is the case can we mod PRL files to enable different menu features???
FYI: If you have Xposed Framework app installed on your phone I noticed for some reason it will block the above changes to occur (Android v4.2.2). (Maybe the devs here can fix this issue and make a menu app module add on for Xposed Framework that can enable the above menu features)
6. Removing Knox software from Android 4.4.2 go to Google Play store and download Titanium Backup and follow this tutorial:
http://pakdroid.com/2014/01/07/tutorial-remove-knox-from-your-samsung-devices-running-android-4-3/
7. Android KitKat 4.4.2 stock ROM for the SCH-R960 download and flash it using Odin 3.09:
http://www.mrcrab.net/androidfirmware/SCH-R960/Samsung-Galaxy-Mega-SCH--R960.html
8. Getting to how I hard bricked my phone I used the app GalaxSimUnlock on and of course it didn't unlock the phone but I was able to make a backup of my efs image and directory using this app. While tinkering around with the hidden menu settings for the network type I reset the the phone which in turn deleted the EFS folder from my phone. So I tried restoring it with GalaxSimUnlock which of course would not restore the back up. So I tried using the tutorial of:
su -c "busybox umount -l /efs"
su -c "busybox mke2fs /dev/block/mmcblk0p3"
su -c "busybox dd if=/sdcard/efs.img of=/dev/block/mmcblk0p3 bs=4096"
su -c "busybox mount -w -t ext4 /dev/block/mmcblk0p3 /efs"
Trying to restore the image which I could never get it to write the backup back to the phone. So somewhere along the way I messed up my boot loader and hard bricked the phone. I tried using the USB Jig to get it to boot into download mode but that didn't work either.
I did install the drivers for Windows 7 64bit for Qualcomm HS-USB QDloader 9008 which is CPU download mode. I can get QPST Configuration software to see the phone and go to the menu Start Clients and select Software download but you have to have Phone Image or Boot Image in HEX. I could not find anybody on the web that talked about debricking the phone this way. But might be a viable way to mod the boot loader or downgrade.
CPU INFO:
Qualcomm Krait 300
MSM8230AB
Snapdragon 400
2 cores
They talk a little bit about debricking here using this method and download the drivers from the following link:
forum dot cyanogenmod dot org/topic/71825-hard-brick-to-hell-and-back-guide-to-recovery/page__st__40
WHERE I NEED HELP
So my next step would be using the SD Card debrick method if some kind person could create a debrick.img for the SCH-R960 running Android KitKat 4.4.2. The following commands will create different sizes of the debrick.img but the first one should be fine for my situation.
How to Create Boot Loader Debrick Image
Created from Terminal Emulator APK:
su (enter)
busybox dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1M count=128 (enter)
su (enter)
busybox dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1M count=256 (enter)
su (enter)
busybox dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1M count=512 (enter)
Thanks ahead of time for your help!!!
Bought another SCH-R960 to try
OK, I bought another used SCH-R960 off of eBay. I still need to buy a class 10, 16GB SD Card to create the debrick boot loader SD Card. However, the phone came with Android v4.2.2 running on it. I am kind of dragging my heals upgrading to v4.4.2. If somebody could give me a really good reason to upgrade to v4.4.2 besides me needing the debrick.img. I really don't want the Knox crap built into the boot loader. Unless, somebody knows of a way to remove Knox from the boot loader before I upgrade the phone.
Thanks again for all your support to the community!!!
How to remove Knox boot loader from firmware update
Ok, I just found this guy's tutorial on removing the Knox boot loader over on youtube. I think I will try this or do you think the debrick.img may not work since this will still be an older boot loader left on the phone when creating the image?
#How to remove KNOX Bootloader on Samsung Galaxy S4 Mini firmware (with Linux)
www dot youtube dot com/watch?v=75DKAGNstbM
Put together a 4.4.2 Firmware flash
Ok, I put together a new tar.md5 file without the Knox boot loader and loaded it via Odin 3.09. However, having issues with booting into power charging mode only and also reboots systematically once you get booted into the phone interface. You will have a random crash of different apps and then the phone will reboot. I cleared the all the cache in recovery mode set it back to factory. Still same issue.
I also went in and uninstalled all the Knox realted apps with Titianum.
I left out the files he suggested in the video tutorial of aboot.mbn, sbl1.mbn, sbl2.mbn, sbl3.mbn. I also replaced the recovery.img with the updated CLW recovery.img. Everything flashed just fine.
I read here in the comments of the following link that it could be an issue with the modem and need to extract the modem from 4.4.2:
www dot s4miniarchive dot com/2013/12/how-to-remove-knox-bootloader-from-new.html
Also read it could be the battery driver. Seeing it will not go into charge mode when powered off and charger plugged in.
So I guess next need to figure out how to get the modem.bin to flash from the stock firmware.
Made another ROM
So, I went back and added sbl1.mbn, sbl2.mbn, sbl3.mbn to the tar.md5 file. And it didn't show any Knox warranty in system info or Knox gripe when booting into CWM recovery.img. However, it still does the reboot after a few min after the phone boots and still will not boot into battery charge mode when powered down and charger plugged in. It just shows the gray battery icon for a few seconds then boots up the phone.
I did do a little experiment with the firmware. I loaded Liquid ROM for Mega 6.3 v3.2 nightly build. I knew it would probably not boot but worth a shot. But, it did boot into charge mode when the phone was powered off and charger plugged in. I tried copying all the files from the /system/lib/modules from the stock rom drivers over to Liquid ROM using ADB while in recovery mode using shell. Still would not boot. SO, my only last option is to either load the full stock firmware v4.4.2. I have tried looking at the log files too to see if it would throw an error to while it fails and reboots. Must be something in the kernel looking for something from aboot.mdn bootloader????? Any ideas on this?
Added aboot to ROM
OK, bit the bullet and added aboot.mdn too the ROM and flashed it. The phone boots fine now into Battery Charge mode and full boot up of the phone without any issues. But now I have the wonderful Knox warranty bit set for the CWM Recovery. Oh well not worried about warranty anyway.
Next, I went to Walmart and purchased a SanDisk Ultra Plus 16GB SD Card. I created a recovery image from the current flash using the 128mb debrick.img and used Win32DiskImager to create the boot SD Card. I was able to reboot into Flash mode and flashed the ROM I put together with STOCK ROM and CWM Recovery.img.
I have two versions of the debrick.img now for the phone one for Android v4.2.2. and v4.4.2.
http://d-h.st/MP6
http://d-h.st/ONp
joecowboy said:
First Off to the Community thank you for the great work!!!
OTHER INFO:
1: How I got recovery.img with CLM (Clockwork Mod Recovery) to work with Android KitKat 4.4.2 update. I used the download links from pctech101 dump of SCH-R960 Android 4.2.2 from
http://teamuscellular.com/Forum/topic/5435-samsung-galaxy-mega/page-3#entry89801
I convert the recovery.img using Caboomi's_Recovery_img2tar_odin_maker so I could flash it using Odin 3.09. This will cause Knox counter.
OR DOWNLOAD IT FROM THIS THREAD for i9200
Galaxy Mega i9200 (melius3gxx)
http://forum.xda-developers.com/showthread.php?t=2588661
If we could get the drivers for the digitizer loaded for CWM Recovery would be awesome.
2. Then I could install the UPDATE-SuperSU-v2.02.zip from the external SD Card using CLM recovery to root Android from here:
http://download.chainfire.eu/452/SuperSU/
When you go to use SuperSU for the first time from your apps you might have to extract Superuser.apk from the zip file and reinstall it again from the SD Card and then go back to CLW recovery and reinstall the UPDATE-SuperSU-v2.02.zip.
To get into CLW recovery remember you have to hold the Power Button, Volume UP button and Home Button
3. Trying to setup SCH-R960 to be used with T-Mobile using the following instructions modifying the file build.prop file in the system folder using this tutorial (I know it states for Verizon Phones) :
http://www.internauta37.altervista.org/how-and-patch-fully-enable-gsm-verizon-cdma-phones-android
Still trying to get around the SCH-R960 not wanting to see the T-Mobile LTE SIM Card inserted. One thing if you change telephony.lteOnCdmaDevice from 1 to 0 your menu in for selecting Network Mode will disappear.
I added these settings to my build.prop
# To enabled hidden menu number 4636
ril.sales_code=LOL
ro.csc.sales_code=LOL
sys.hiddenmenu.enable=1
# GSM Setting for T-Mobile
ro.telephony.default_network=9
ro.ril.def.preferred.network=9
telephony.rilV7NeedCDMALTEPhone=false
telephony.lteOnGsmDevice=1
ro.cdma.home.operator.alpha=T-Mobile
ro.cdma.home.operator.numeric=310260
ro.gsm.sim.operator.alpha=T-Mobile
ro.gsm.operator.alpha=T-Mobile
ro.gsm.sim.operator.numeric=310260
ro.gsm.operator.numeric=310260
ro.gsm.sim.operator.iso-country=us
ro.gsm.operator.iso-country=us
4. I tried tinkering around unlocking the phone using DFS CDMA Tool v14.8.0.0 demo. I used SPC of 000000 and US Cellular PWD for the phone 2010031619780721 which worked stating unlocked but never could get the LTE T-Mobile SIM card to work.
For changing the PRL:
#Select Tabs
Programming ==> NAM ==> PRL:
#Under PRL select load (I loaded 3040 MetroPCS):
Select Load to load your PRL file
Then click the Write button to write the PRL to the phone.
#The PRL can be located here:
http://androidforums.com/metro-pcs/...ease-post-new-ones-here-when-available-3.html
#Or from here
http://forum.xda-developers.com/showthread.php?t=1880781
#Or from here
http://forum.xda-developers.com/misc.php?do=showattachments&t=1880781/
For data settings I changed:
#Select Tabs
Programming ==> Data ==> MODE:
#Under Mode Change:
HDR SCP force AT config: from RevA_MFPA to RevA_EHRDP
Hybrid preferred mode: from Disabled to Factory
Then click the Write button to update the settings
Here is a list of other Samsung 16 digit passwords:
http://www.howardforums.com/showthread.php/1664024-Samsung-16-digit-passwords
5. Trying to enter the hidden menus does not work with the dialer on this phone because it's disabled and you have to enable it by editing the file in the folder \efs\carrier\HiddenMenu opening it up and changing OFF to ON or using the app ShortCut Master and it will list all secret codes.
Using ShortCut Master
From the menu select: Secret Code Explorer
--Codes--
4636 = Hidden Menu
638 = Tethering Always on
0808 = Change USB Settings
7284 = Change USB Settings
27663368378 = Change Phone Settings
#Using 27663368378
[1] UMTS > DEBUG SCREEN > PHONE CONTROL > NETWORK CONTROL > BAND SELECTION to set Automatic
[2] CDMA > COMMON > NEXT PAGE > NEXT PAGE > PREF MODE SET to select GSM/WCDMA ONLY
[3] CDMA > CONTROL > CDMA BAND SELECT to select Automatic
When setting this it will enable in your Settings Connections Tab and then More Networks ==> Mobile Networks and if you select Network mode you will now see a lot of different Prefered network modes to choose from.
Access Point Names will also be accessible now so you can set up your APN. There is also another Network mode item which has four settings to choose from and Network operators is now accessible item to choose from.
After you reboot from doing the three settings above it might show that there is no network symbol. You will need to do option [1] again and the network bars should pop back on once you do this. And then your new settings for More Network Options should appear now.
I am not sure if this is in conjunction with updating your PRL too and it enabling these menu items. I first added a Sprint PRL and it added a roaming menu item under Settings Connections Tab and then More Networks. So if this is the case can we mod PRL files to enable different menu features???
FYI: If you have Xposed Framework app installed on your phone I noticed for some reason it will block the above changes to occur (Android v4.2.2). (Maybe the devs here can fix this issue and make a menu app module add on for Xposed Framework that can enable the above menu features)
6. Removing Knox software from Android 4.4.2 go to Google Play store and download Titanium Backup and follow this tutorial:
http://pakdroid.com/2014/01/07/tutorial-remove-knox-from-your-samsung-devices-running-android-4-3/
7. Android KitKat 4.4.2 stock ROM for the SCH-R960 download and flash it using Odin 3.09:
http://www.mrcrab.net/androidfirmware/SCH-R960/Samsung-Galaxy-Mega-SCH--R960.html
8. Getting to how I hard bricked my phone I used the app GalaxSimUnlock on and of course it didn't unlock the phone but I was able to make a backup of my efs image and directory using this app. While tinkering around with the hidden menu settings for the network type I reset the the phone which in turn deleted the EFS folder from my phone. So I tried restoring it with GalaxSimUnlock which of course would not restore the back up. So I tried using the tutorial of:
su -c "busybox umount -l /efs"
su -c "busybox mke2fs /dev/block/mmcblk0p3"
su -c "busybox dd if=/sdcard/efs.img of=/dev/block/mmcblk0p3 bs=4096"
su -c "busybox mount -w -t ext4 /dev/block/mmcblk0p3 /efs"
Trying to restore the image which I could never get it to write the backup back to the phone. So somewhere along the way I messed up my boot loader and hard bricked the phone. I tried using the USB Jig to get it to boot into download mode but that didn't work either.
I did install the drivers for Windows 7 64bit for Qualcomm HS-USB QDloader 9008 which is CPU download mode. I can get QPST Configuration software to see the phone and go to the menu Start Clients and select Software download but you have to have Phone Image or Boot Image in HEX. I could not find anybody on the web that talked about debricking the phone this way. But might be a viable way to mod the boot loader or downgrade.
CPU INFO:
Qualcomm Krait 300
MSM8230AB
Snapdragon 400
2 cores
They talk a little bit about debricking here using this method and download the drivers from the following link:
forum dot cyanogenmod dot org/topic/71825-hard-brick-to-hell-and-back-guide-to-recovery/page__st__40
WHERE I NEED HELP
So my next step would be using the SD Card debrick method if some kind person could create a debrick.img for the SCH-R960 running Android KitKat 4.4.2. The following commands will create different sizes of the debrick.img but the first one should be fine for my situation.
How to Create Boot Loader Debrick Image
Created from Terminal Emulator APK:
su (enter)
busybox dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1M count=128 (enter)
su (enter)
busybox dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1M count=256 (enter)
su (enter)
busybox dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1M count=512 (enter)
Thanks ahead of time for your help!!!
Click to expand...
Click to collapse
Us Cellular pwd can you explain what that is. Been trying for days to unlock sim.
Unlocking Sim Card
jr.mayo73 said:
Us Cellular pwd can you explain what that is. Been trying for days to unlock sim.
Click to expand...
Click to collapse
Us Cellular pwd is a 16 digit password used for modifying settings on the phone.
I have tried unlocking my sim card also. However, still haven't figure it out. I just purchased a this off of eBay:
New 1Pc No Cut Universal Cell Phone Mobilephone Sim Unlock Card
http://www.ebay.com/itm/301109522131?ssPageName=STRK:MEWNX:IT&_trksid=p3984.m1497.l2649
I have not received it yet but I was going to see if this will trick the sim into thinking it's a US Cellular sim. I have not received it yet in the mail for testing.
Using ShortCut Master you will also see the following unlock options which I can't seem to get to work either
From the menu select: Secret Code Explorer (These are the only codes I could see listed on this phone, such as sim lock is missing)
-- Codes --
7465625 -- Personaliztion Status (Show lock status: Network Lock, Network Subnet Lock, SP Lock, CP Lock)
7465625*27* -- Lock/Unlock Code -- CP Lock - Enter CP Lock Control Key
7465625*638* -- Lock/Unlock Code -- Network Lock
7465625*77* -- Lock/Unlock Code -- SP Lock
7465625*782* -- Lock/Unlock Code -- Network Subnet Lock
Ok thanks. Only QPST asks me for the 16 Digit password. DFS CDMA tool and CDMA workshop don't ask me for it. Im trying to use an AT&T sim card in my SCH R960. With no luck. I was gonna try your way to see if I get a different result with the sim but I didn't understand your instruction because I was trying it on CDMA workshop. DFS CDMA tool tells me there is no unlock when I click Unlock Sim. I did download shortcut master. And a S4 phone utilities Because my dialer codes wouldn't work. You might find the sim dialer code with that. I got 2 unlock screens. It might be the same ones you posted previously. If you could tell me step by step directions on get the unlock successful message I'll let you know if it works on my mega. If you have the time. I'm a noob but not really been doing this for awhile but for this phone you are the only person giving useful info for this particular phone.
Still trying to figure this out myself
I am still trying to figure out a way to unlock the SIM Card myself. I need to play around with QPST more myself and I know CDMA Tools does use the 16 digit password in the PWD field. But, not real sure what exactly it helps with you with since you can use 000000 for the SPC field.
I am going to try that Cell Phone Mobilephone Sim Unlock Card when I get it in the mail. I will post some if it works or not with this phone when I get it.
Keep posting your ideas on trying to unlock the Sim card on this phone.
joecowboy said:
I am still trying to figure out a way to unlock the SIM Card myself. I need to play around with QPST more myself and I know CDMA Tools does use the 16 digit password in the PWD field. But, not real sure what exactly it helps with you with since you can use 000000 for the SPC field.
I am going to try that Cell Phone Mobilephone Sim Unlock Card when I get it in the mail. I will post some if it works or not with this phone when I get it.
Keep posting your ideas on trying to unlock the Sim card on this phone.
Click to expand...
Click to collapse
Ok I will. My internet has been out for a few days. So its kinda hard to do research. But it should be fixed by mon so I can continue on
jr.mayo73 said:
Ok I will. My internet has been out for a few days. So its kinda hard to do research. But it should be fixed by mon so I can continue on
Click to expand...
Click to collapse
I am still waiting on the SIM Card unlocker to come in the mail. Slow boat from China. Hopefully be here in the next few days.
Three SIM card adapter
Ok, I had to purchased a three SIM card adapter to use with the Universal Turbo SIM Unlock Card. However, when I install the adapter with my US Cellular SIM card in the SIM card slot on the phone it gives me no SIM card installed icon symbol. And, so the Android OS never installs the Three SIM Card software.
I watched this tutorial on YouTube with two other Samsung phones using the exact three SIM card adapter with their phone.
https://www.youtube.com/watch?v=pQ4I6M5usRg
So I have been unable to test the SIM Unlock card which is suppose to tell the phone that the SIM cards are engineering SIM cards is why it suppose to bypass the check the SIM lock. Any ideas to how to get this to see the SIM cards with the adapters?
I am having the same problem but I have went a different route. I made a verizon s3 work with a att sim card a few years ago. So figured it might be possible with us cellular as well. So I rooted my mega with odin installed philz/cwrm recovery for the i9205 I beleive it is. Tried a custom rom for same version. On the sch-r960 and had no touch. So put it back stock and left it alone for awhile. Well the other day I got it back out cause I love the mega and want to use it on straighttalk. I have a galaxy s3 and had a bunch of roms for it on my sd card. So was like oh well and flashed wicked custom rom for the att galaxy s3. I figured I would for sure brick the mega. And what would ya know it booted up and ran just fine. Kinda crazy I was able to get it to reconize verizon some how then it went into roaming mode. I still have not figured out how to get it to detect the sim card for ST. So will be following this post I really wanna use my mega lol
Sent from my SCH-R960 using XDA Free mobile app
Hello,
I have a Samsung SCH-r960 and I want to use it for AT&T or other. Has anyone been able to unlock it or used it for other companies?
Thanks
Regards
We should do a post or thread to solve the problem of unlocking Samsung Galaxy Mega SCH-R960.
I am making this tutorial as I have had multiple versions of the LG LTE Leon and have used many firmware versions. I have created a stable method that has the least issues as I have had trouble with the latest firmware (MS34510f) disabling my root privileges. I have created a MEGA account specifically for all of the files necessary to complete this operation and have your device run smoothly. So, please follow my instructions exactly as stated and you should not have any issues. THIS PROCESS WILL REMOVE ALL DATA NOT SYNCED, DO READ BELOW NOTES IT IS VERY BENEFICIAL
Important Notes:
+This process will wipe all data that is not synced, it is important to ensure that no newer LG process are still on the device. Some might argue to leave data, to that I say good luck keeping your root and tethering without the device becoming suspiciously unstable.
+ I am not GUARANTEEING this will work on every model, but I have had an extremely high success rate with all Leon versions.
+ In this tutorial the process in which I remove Kingroot and replace it with SuperSu is for system stability. I find that most root functions I use seem to not work properly. (Wifi Tether Router and many others). So, I do recommend doing so.
+After the new OS is installed a MetroPCS splash screen will appear even if you do have T-Mobile. DO NOT BE ALARMED this firmware will not limit any functionality you had before, it will even help with tethering functionality.
Tutorial:
Let's Begin.
1. Download the link posted to obtain required files for this tutorial
Link: https://mega.nz/#F!PM4CQRqb!92kgIOnD0ZBY-8HVbtTwGQ
2. Open up LGFlashTool2014.exe
Begin by copying settings posted below, then click "normal flash"
3. Next click the "START" button
4. At this time, I recommend you verify all sync settings are to your liking and that all personal info needed is backed up
a. You have the option to throw all of your personal documents/pictures onto your SD card and removing it appropriately
(Go to: Settings - Storage - [scroll down to] Unmount SD card)
b. Next, navigate to Settings -Backup & reset [leave options default; both checked off] - Factory data reset - reset phone
c. Once reset it will most likely reboot, wipe, and then back to a OS. Now, you will Power Off entirely (make sure it is not plugged in so it will not go to charging mode)
d. Here is where we will hold down the Volume Up button with the phone unplugged from your PC. Then you must plug the USB into your phone.
e. A black screen with white text should post onto your screen, here we will continue to step 6
note: If this screen does not appear please power off and retry step d.
6. Next, follow the posted settings. Make sure to click the "Clear phone Software update Registry" button Then click "OK"
7. A new screen will arrive, and should begin the firmware download process. At this time it will take a few minute to load and should reboot to a fresh OS.
8. With the new OS in place, you can either follow the setup tutorial now or skip through for a later setup.
note: you can now insert your SD card
9. In the tools folder of the folder you downloaded copy the "mrw" folder to the Main Storage folder of your phone
10. Now copy the Kingroot apk to your downloads folder located on the main storage.
11. Go to Settings - About Phone - Software Info
At this time click the build number box a few times until it says you are a developer
12. Hit back until you are at the Setting menu, click on Developer options and check off "Stay Awake" and "Enable OEM Unlock" as well as "USB Debugging"
13. You may now run Kingroot, if it does not install root the first time it should flawlessly install the next.
14. After root is obtained, please go to your home screen and click the "Google Search" widget. Press Update Google Services and let it run. After that has been updated search for terminal emulator and install.
note: If the Play Store is acting fishy and force closing while typing in the search bar do not fret it will be fixed after reboot in further instruction
as an allternative use the jackpal.androidterm-1.0.70-71-minAPI4.apk provided in the "tools" folder
15. Open terminal and in a new window type: Su
16. Allow root usage and at this time type: sh /storage/emulated/0/mrw/root.sh
17. It will run with a few failed messages do not worry it should open SuperSu momentarily
18. Once SuperSu opens up allow it to update binaries using the "NORMAL" option but DO NOT REBOOT YET
19. At this time either download TWRP Manager from the play store or alternatively use the com.jmz.soft.twrpmanager-7.5.1.3-82-minAPI11.apk provided in the tools folder
20. Install and open TWRP Manager. Once opened click on device name and scroll until you see "LG Leon LTE (c50)"
a. Click on Recovery Version to Install and select "twrp-2.8.7.0-c50.img"
b. next click "Install Recovery" and if prompted for verification of install path and for install version select "YES" & "NORMAL"
21. After the TWRP setup is complete it may prompt you to reboot, if not click the arrow in the top left of the TWRP Manager screen and scroll down to "Reboot" and select "Reboot device"
22. After Reboot click TWRP Manager and verify a SuperSu prompt comes up if it hasn't already before the boot
At this point the device should be running smoothly. From here I prefer to do the following steps.
My Personal Setup after new install:
+Personally I like to install use a Root Uninstaller (I use 3C Toolbox Pro) and Uninstall and Backup all MetroPCS BloatWare including the Metro Browser.
+I also access the Hidden Menu by using the Dialer and Dial "2776348*#*"
- I scroll down to ApnUnlock and click to "Unlock APN"
- Then I navigate to Settings -Tethering & networks - Mobile Networks (I check off roaming data) - Access point names
--I then select the top APN and edit APN Type to: default,supl,mms,dun
---I click save from the top right selection, then turn on and off airplane mode
+If you are and Xposed user download "xposed-v79-sdk22-arm.zip","xposed-uninstaller-20150831-arm.zip", and "XposedInstaller_3.0_alpha4.apk" from: http://forum.xda-developers.com/showthread.php?t=3034811
-install the Xposed Installer, then Go to TWRP Manager, use reboot to recovery and from there click install and navigate to the "xposed-v79-sdk22-arm.zip" and install and reboot, it will reboot with a installing screen before your home screen, takes 5 minutes.
+I also use this AMAZING app "Wifi Tether Router", it is the only tethering app I use that works consistently (if you have an unlimited data plan). I get 30mbps up and down, playing many multiplayer games off my PC and PS4 averaging ping as low as 30 ! Setting I use for our device are in a post I created here: http://forum.xda-developers.com/leon/help/unlimited-metropcs-t-mobile-tether-t3290180
---------------------------------------------------------------------------------------------------------------------------------------------------------------
Special Thanks to:
MrW0lf from www.W0lfdroid.com for the Kingroot to SuperSU scrip
Numerous users on the XDA forums I pieced all of this information with
Fabio Grasso for making the amazing Wifi Tether Router
Team Win for being creating an awesome utility that has saved me from numerous bricks creating a stable method
Xposed and the creators of awesome additions such as Lolistat, Lucky Patcher, Max Lock, and SNAPPREFS
Any feedback? Did I do Okay? Questions? Let me know!
Worked for me on T-mobile H345
Worked for me on T-mobile H345 any way to install a H340 firmware on it? I GeT a Binary not authorised when trying to flash.
kodacy said:
Worked for me on T-mobile H345 any way to install a H340 firmware on it? I GeT a Binary not authorised when trying to flash.
Click to expand...
Click to collapse
Apologies for the late response, I never received a notification of your posting. I would not recommend that as I believe the H340 has a different "radio" driver or cellular chip, If I'm not mistaken the H340 isn't even LTE, the H345 is. In that case it may be possible. One thing I suggest doing before wasting your time in using any other ROM is googling H345 vs Ms345, typically the phonemore.com results will provide you with an abundance of hardware specs and let you know if they're different! Just be weary of the newest MS34510f_00.KDZ firmware I believe it has an active unroot process I've had some stability issues. I am using MS34510D_00.KDZ for months and have had no issues whatsoever! Again, I'm sorry I got back to you so late, let me know how everything goes!
brad2192 said:
Apologies for the late response, I never received a notification of your posting. I would not recommend that as I believe the H340 has a different "radio" driver or cellular chip, If I'm not mistaken the H340 isn't even LTE, the H345 is. In that case it may be possible. One thing I suggest doing before wasting your time in using any other ROM is googling H345 vs Ms345, typically the phonemore.com results will provide you with an abundance of hardware specs and let you know if they're different! Just be weary of the newest MS34510f_00.KDZ firmware I believe it has an active unroot process I've had some stability issues. I am using MS34510D_00.KDZ for months and have had no issues whatsoever! Again, I'm sorry I got back to you so late, let me know how everything goes!
Click to expand...
Click to collapse
No problem thank you for your help!
will i still have metro service?
Port(usb or serial) not found! tried on, off, update mode, changing ports and unplugging every other port. any thoughts?
kap10nuka said:
Port(usb or serial) not found! tried on, off, update mode, changing ports and unplugging every other port. any thoughts?
Click to expand...
Click to collapse
Same here (firmware update) usb not detected when using the S/W update tool
After going all the way through this guide with a T-Mobile Leon, I do indeed have a Metro PCS ROM and root, which is great! Unfortunately, it also refuses to acknowledge my T-Mobile SIM. In fairness, I did not even insert a SIM for the first time (just got the phone) until the end of the process, but it shows as carrier locked which is significantly less than useful. I'll flash back to a TMO rom and put the SIM in to double check, but it's quite a bummer. Great job on the guide otherwise, though! It definitely did what it says on the tin; I have root and apart from the SIM lock which may be my fault somehow it works great.
Hey bud those links are no longer valid know where i can get them?
my method here will give you a permanent rooted shell and will give you read-only system root which is useful for using root apps to backup data or freeze system apps--works just like real root without being able to delete system contents--freezing apps however works like a charm and should reduce the need for rw root anyway
FOLLOW DIRECTIONS EXACTLY--I WILL NOT RESPOND TO STUPID QUESTIONS--PROBABLY WON'T RESPOND TO ANY QUESTIONS BECAUSE MY DIRECTIONS ARE PERFECT, WORK PERFECTLY WHEN FOLLOWED, AND ARE EASY TO READ. FOLLOW ALL STEPS EXACTLY. IF IT DIDN'T WORK, IT IS BECAUSE OF YOUR ERROR
This works best from a factory reset device, but will work from a already used device but all other root apps and superuser apps must have their data deleted and be uninstalled first
1) make sure device is at least 50% charged--doesn't matter most of the time; better safe than sorry
install latest superuser apk
http://www.mediafire.com/file/dx854fsys5pvxjh/SuperSU.apk
install dirty cow root apk (croowt) [comes from this post https://forum.xda-developers.com/android/software-hacking/root-tool-dirtycow-apk-adb-t3525120
http://www.mediafire.com/file/1hbey829hc7676a/CRooWt.apk
make sure usb debugging is activated in developer settings and make sure you have accepted the debugging access prompt on the phone for the computer you will use
make sure you have an external sdcard installed--the smaller the better for this first time
2) open dirty cow root apk
choose "get root"
choose "method 1"
hit "ok"
choose "ok"
app will direct you to unmount and remount sdcard, choose "ok" and it will take you to storage settings
unmount sdcard
remount sdcard
when finished proceed to step 3
3) open superuser
do not update su binary
go to settings and make the default action "grant"
remove any and all apps from superuser log including the croowt app
3) THIS MUST BE DONE FROM A REAL TERMINAL ON A PC--TERMINAL EMULATORS WILL NOT WORK FOR THIS STEP
from a working pc with adb setup, preferrably linux, input commands exactly as listed
adb shell
su
setprop persist.sys.k P816A06
reboot
5) once rebooted, open dirty cow root apk again
choose get root
choose "method 2"
hit "ok"
choose "ok"
if app asks you to open with a browser, choose one, and choose "always"
screen will go black, systemui will crash and then reboot
6) once systemui is back up and running
you now have read-only root
you can now freeze system apps or backup your data using apps that require root
Your shell will be permanently rooted when accessed from a computer using adb--this will last forever unless you undo the setprop
Your system however will only be temp, read-only rooted until the phone is rebooted.
If you wish to have your temp, read-only root reactivated, all you have to do is repeat step 5 and that is it.
You can do this over and over again.
GIVE STAYBOOGY SOME PROPS FOR MAKING YOUR LIFE WITH THIS PHONE BETTER
Does this only work to back up or freeze applications?
poseidon207 said:
Does this only work to back up or freeze applications?
Click to expand...
Click to collapse
ACTUALLY READ the first sentence of OP
I don't see how freezing system apps would negate the need for a real root method? Is this "Read-Only" root method working with lucky patcher or Kernel Auditor?
Can this be used to bypass the subscription check for tethering? I assume not since system isn't writeable.
Does this method work in the ZTE Maven 3 (Z835)?
I'm doing it wrong, probably
First of all, thank you so much for doing this. I've been following that other thread since it was new, and you've put far more effort into this than the phone or most of us deserve.
I've gotten stuck trying to run Dirty Cow. I have USB Debugging enabled, adb installed on my Linux computer which recognizes my Maven (i.e. I've allowed access on the phone), etc. It eventually goes from "Checking vulnerability" to "Your device is not vulnerable" and I'm unable to proceed to the "Get root" step. What am I doing wrong? Might be some recent system update? Probably less effort to just buy a Galaxy.
Please be gentle. I know I'm a noob.
z812 root
I previously rooted my maven with kingroot and the dirtycow exploit.sh file and today I was overwhelming the device by running multible windows and apps and the phone rebooted and root was still intact....haven't rebooted it again yet but I shall.
Following the instructions from this post (except don't rebook at the end) https://forum.xda-developers.com/showpost.php?p=61736387&postcount=15 I was able to successfully tether on the LG G6 h871. The data flows from phone to whatever wifi device smoothly.
The thing I'm still working on is that the changes don't persist if the phone turns off. The settings reset when the phone is restarted. Anyone know how to make the changes stick?
Thanks!
Here's a brief update.
You can actually make these settings from within your phone, instead of through the ADB command, which is useful in case you suffer an inadvertant reboot while in the field. Still haven't been able to make the settings persist through reboot however.
Taken from here https://forum.xda-developers.com/att-lg-v10/help/activate-hotspot-unlocked-lg-v10-t3585697
You use the Settings Database Editor and find these entries in there (you have to find the one in both the System and Global tables).
The setting in Global table "tether_dun_required 0" is protected and won't let you edit it.
You can change this using ADB, and fortunately granting these permissions is a one time process that does persist through normal reboots. https://forum.xda-developers.com/tm...settings-database-editor-tweaks-t3609876/amp/
"adb shell"
"pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS" (check this command against the text the app pops up when you try to change the protected setting)
"reboot"
Now you are able to go into the Settings Database Editor app and modify these two settings
Global table "tether_dun_required 0"
System table "tether_entitlement_check_state 0"
And viola you will have a working wifi hotspot on your unrooted stock phone. Hopefully I can figure out a way to make these changes stick through reboots though, because it is a bit of a hassle to click through the app anytime it reboots, but at least it works, and it's certainly better than the popping out your sim card trick and trying to time shoving it back in just at the right moment during the wifi hotspot creation trick.
I used to use this trick but tried the other day and while I was able to connect to the hotspot I could not get internet on any device. Anyone else notice this.
Is this issue specific to the h871 / AT&T? On h870 (carrier free) you can just enable it in settings...
Worked very well for me, thanks! Did you get around these settings stick after reboot?