Database Develop

[Q] Bionic won't activate Pageplus after JB upgrading

I'm a Pageplus user. After flashing 6.7.246 (ICS 4.0.4), I got OTA to 98.72.22 (JB 4.1.2) successfully.
But I'm stuck then when trying to activate Pageplus OTA by calling *22800:
I kept getting "Sorry, this SIM card is not recognized or registered..", no matter how many times I tried.
There's another notified error: "Unknown SIM card detected"
It's abnormal b/c it should fail only 2-3 times, then taking me to the activation screen.
The 4glteSIM card inside was activated before and used on the 6.7.246 stock build.
FYI, I also reflashed 6.7.246 one more time on top of 6.7.246 and didn't encounter the activation problem. So I'm superised to have this issue after upgraing.
Please advice me if you have any idea.
Thanks in advance.

Did you keep root? And if you did flash a rom like cm10 and then activate the rom like you did on ics. I did that and then I rebooted in stock jelly bean and it was activated. Hope that helps!
Sent from my DROID BIONIC using xda app-developers app

Thx for your reminding. I'll try this way.
Did you install the cm10 with safestrap 3? I tried to install it on the JB but failed. Does it require a rooted JB?
I tried to search but cannot find an effective way to root Bionic JB.
I'll appreciate if u can give some detail abt: A. the JB rooting method, and B. How to install cm10 (or the justed released Blurry-JB_2.4.zip) while keeping the JB stock rom.
Thanks a lot!
Wilsono1050 said:
Did you keep root? And if you did flash a rom like cm10 and then activate the rom like you did on ics. I did that and then I rebooted in stock jelly bean and it was activated. Hope that helps!
Sent from my DROID BIONIC using xda app-developers app
Click to expand...
Click to collapse

Idk if there's a jelly bean root method for the droid bionic. But I kept root after the ota. Then with safestrap 3.11 I installed cm10 and activate it. It usually retrieved the activation when the phone boots up with cm10.
Sent from my DROID BIONIC using xda app-developers app

I managed to have the JB stock rom rooted anyway (by the virtual box approach).
Then I was allowed to install safestrap 3.1, then the newest Blurry JB 2.4.
I tried to "activate" from the step 2 ("2-Getting phone ready for OTA Activation") of the old instaruction:
http://www.howardforums.com/showthr...CS-OTA-Activation-TXT-MMS-3G-ROOT-on-PagePlus
But the CDMA Workshop didn't find the port. I assume the reason is that safestrap has blocked the normal bp-tools booting way.
So I can only start from "3-OTA Activation".
After changing "Network Selection" to "CDMA Only", I rebooted and dialed *22800. Still get the same error "sim card not recognized or registered".
Can you please detail how did you "activate" it under cm10?
Many thanks.
Wilsono1050 said:
Idk if there's a jelly bean root method for the droid bionic. But I kept root after the ota. Then with safestrap 3.11 I installed cm10 and activate it. It usually retrieved the activation when the phone boots up with cm10.
Sent from my DROID BIONIC using xda app-developers app
Click to expand...
Click to collapse

Okay, if you install the jb blurry rom its going to be the same problem as stock because they're pretty much the same. What I did is 1. Kept root after the ota 2. Installed safestrap 3.11 3.) Rebooted into safestrap and created rom slot 1 and installed cm10 rc2 and gapps. When I booted up it activated by itself for me. I then booted up to stock rom and it was activated as well, but had to install the build prop. so I wouldn't get the unregistered sim error thing. Hope that helps!
Sent from my XT875 using xda app-developers app

I installed the cm10.1.0 rc2 into the slot 1 (with and without gapp), but reboot get a blank screen. Have to pull the battery to get reboot to ss.
Wilsono1050 said:
Okay, if you install the jb blurry rom its going to be the same problem as stock because they're pretty much the same. What I did is 1. Kept root after the ota 2. Installed safestrap 3.11 3.) Rebooted into safestrap and created rom slot 1 and installed cm10 rc2 and gapps. When I booted up it activated by itself for me. I then booted up to stock rom and it was activated as well, but had to install the build prop. so I wouldn't get the unregistered sim error thing. Hope that helps!
Sent from my XT875 using xda app-developers app
Click to expand...
Click to collapse

may thx. that work!
taller238 said:
I installed the cm10.1.0 rc2 into the slot 1 (with and without gapp), but reboot get a blank screen. Have to pull the battery to get reboot to ss.
Click to expand...
Click to collapse

taller238 said:
may thx. that work!
Click to expand...
Click to collapse
Did you get it to work?
Sent from my XT875 using xda app-developers app

did anyone get this to work?
Thinking of just saving myself the headache and getting a droidx2.
I'm running cm10.1 and safestrap 3.11 3. I'm going to try a dealer tomorrow to see if they can activate it on pageplus.
I haven't activated a phone on pageplus for a while. I've been using simple mobile, straight talk and h20

taller238 said:
Still get the same error "sim card not recognized or registered.
Click to expand...
Click to collapse
I had the same problem when I went from GB to ICS. I just ignored it and kept trying and trying (based on advice/steps I found elsewhere) and after a few times it worked. So I would suggest trying it about 10-12 times in a row to see if it works.
Also, here is the method I used for GB to ICS, I'd be interested to know if they help you move from ICS to JB:
Re-activating phone
1. Remove any old Motorola Droid Bionic drivers you may have on your computer and install the newest ones.
2. Turn phone off and turn back on in BPTools mode. Then plug the phone into your computer via USB.
3. Open DFS. Click "Ports" and select the COM port for your phone. Next, click the "SPC" button.
4. Click the "Programming" tab and then the "General" tab. Change the "Ruim Config" to NV_ONLY and click "Write".
5. Click the "Data" tab. Under the "Mode" section, change the "HDR SCP force AT config" option to "RevA_MFPA" and click "Write".
6. Close DFS and unplug phone from USB port.
7. Go to the dialer and dial ##7764726 (##PROGRAM). When prompted for an SPC password, enter "000000" and hit verify.
8. Go to "06 Test Mode". Hit "Next" twice. Then, change the Network mode to "CDMA Only".
9. Back out to the home screen; the phone will automatically restart.
10. After the phone has restarted, go to the dialer and dial *22800. Ignore any SIM card error messages you may see; just keep trying *22800 until you reach the activation screen.
11. Follow the instructions to activate the phone.

I have been working on this for HOURS and tried just about every single thing I could. Root, CDMA workshop, DFS, MDN, MIN, SIN, Safestrap, CM10.1, CM10... what a mess! I can attest that it is possible to get working but might be very painful. I read the numerous new and old threads trying to piece together information. In the end it's hard to say what really worked but let me comment on a few things:
1) *22800 never worked on the stock ROM. Believe me, I tried it about 200 times.
2) You can program in your MDN/MIN/SID using DFS. However, doing so left me with no incoming calls/texts. Only outgoing... weird.
3) CM10.1 did nothing for me. There was a very annoying issue where I tried to activate it and it acted like it was going to but I couldn't "press 1" since the keypad was disabled during activation.
4) Hashcode's CM10 STOCK didn't boot at all. I tried it with both Safestrap 2.11 and 3.11. CM10 KEXEC booted.
5) I finally got the activation to work in CM10 KEXEC with Safestrap 3.11. After activation worked, incoming calls were fixed.
So... here's the kicker. After pulling my hair out and being frustrated for many, many hours I gave the phone to my wife. I had dialed *22800 and when it started to say "press 1" I handed the phone to her.
"See?!" I said.
"See what?" she said. She poked at the screen a bit.
"It wants me to press 1 and there's no dialpad."
"Hmmm..." she said.
Suddenly I heard the sound of ringing. "Wha...?! Hey, give me that. A different screen? 'Your phone is being activated now, please wait 15 minutes.' GAH! I mean... yay!"
I asked my wife what she did. She was like, "I dunno... I pressed Home Menu Back or something."
So... if I had to guess on a procedure I think it would be like:
1) Update phone to JB if not updated already.
2) Use easy Virtualbox method to root.
3) Go through CDMA/DFS rigamarole (NV only RevA_MFPA yadda yadda)
4) Reboot and set CDMA only. Use BuildProp Editor to set telephony.lteOnCdmaDevice=0.
4b?) At some point I used DFS to manually program MDN/MIN/SID, but I'm not sure this is necessary.
5) Install Safestrap 3.11
6) Install CM10 KEXEC with Safestrap 3.11 in slot 1.
7) Boot CM10 and *22800 away! Cross your fingers, hand the phone to whoever is next to you in despair.
8) ???
9) Profit!
I erased Safestrap slot, uninstalled recovery and uninstalled the app when I was done.

has anybody successfully activated the stock JB on the Bionic on PagePlus?
no progress on this yet since I can't find any success stories on Hofo either.
thanks
BD

BuonaDomenica said:
has anybody successfully activated the stock JB on the Bionic on PagePlus?
no progress on this yet since I can't find any success stories on Hofo either.
thanks
BD
Click to expand...
Click to collapse
they all claim this works
Droid-RAZR-MAXX-JellyBean-OTA-Activation-TXT-MMS-3G-ROOT-TETHERING-on-PagePlus
This one confirmed also
Droid-RAZR-and-RAZR-Maxx-Droid-4-Droid-Bionic-on-Pageplus-no-root-or-custom-roms
My brothers bionic activated just fine also...sometimes you just have to follow the steps Exactly as written

primetime^ said:
they all claim this works
Droid-RAZR-MAXX-JellyBean-OTA-Activation-TXT-MMS-3G-ROOT-TETHERING-on-PagePlus
This one confirmed also
Droid-RAZR-and-RAZR-Maxx-Droid-4-Droid-Bionic-on-Pageplus-no-root-or-custom-roms
My brothers bionic activated just fine also...sometimes you just have to follow the steps Exactly as written
Click to expand...
Click to collapse
well your links are not working as I want to check it out

primetime^ said:
they all claim this works
Droid-RAZR-MAXX-JellyBean-OTA-Activation-TXT-MMS-3G-ROOT-TETHERING-on-PagePlus
This one confirmed also
Droid-RAZR-and-RAZR-Maxx-Droid-4-Droid-Bionic-on-Pageplus-no-root-or-custom-roms
My brothers bionic activated just fine also...sometimes you just have to follow the steps Exactly as written
Click to expand...
Click to collapse
BuonaDomenica said:
well your links are not working as I want to check it out
Click to expand...
Click to collapse
Droid-RAZR-MAXX-JellyBean-OTA-Activation-TXT-MMS-3G-ROOT-TETHERING-on-PagePlus
http://www.howardforums.com/showthread.php/1794056-Droid-RAZR-MAXX-JellyBean-OTA-Activation-TXT-MMS-3G-ROOT-TETHERING-on-PagePlus
Droid-RAZR-and-RAZR-Maxx-Droid-4-Droid-Bionic-on-Pageplus-no-root-or-custom-roms
http://www.howardforums.com/showthread.php/1795498-Droid-RAZR-and-RAZR-Maxx-Droid-4-Droid-Bionic-on-Pageplus-no-root-or-custom-roms!
they weren't links,,, google is your friend,,, they are at howardfourms enjoy these links though...
gonna be looking them over myself
.

Kralik said:
I have been working on this for HOURS and tried just about every single thing I could. Root, CDMA workshop, DFS, MDN, MIN, SIN, Safestrap, CM10.1, CM10... what a mess! I can attest that it is possible to get working but might be very painful. I read the numerous new and old threads trying to piece together information. In the end it's hard to say what really worked but let me comment on a few things:
1) *22800 never worked on the stock ROM. Believe me, I tried it about 200 times.
2) You can program in your MDN/MIN/SID using DFS. However, doing so left me with no incoming calls/texts. Only outgoing... weird.
3) CM10.1 did nothing for me. There was a very annoying issue where I tried to activate it and it acted like it was going to but I couldn't "press 1" since the keypad was disabled during activation.
4) Hashcode's CM10 STOCK didn't boot at all. I tried it with both Safestrap 2.11 and 3.11. CM10 KEXEC booted.
5) I finally got the activation to work in CM10 KEXEC with Safestrap 3.11. After activation worked, incoming calls were fixed.
So... here's the kicker. After pulling my hair out and being frustrated for many, many hours I gave the phone to my wife. I had dialed *22800 and when it started to say "press 1" I handed the phone to her.
"See?!" I said.
"See what?" she said. She poked at the screen a bit.
"It wants me to press 1 and there's no dialpad."
"Hmmm..." she said.
Suddenly I heard the sound of ringing. "Wha...?! Hey, give me that. A different screen? 'Your phone is being activated now, please wait 15 minutes.' GAH! I mean... yay!"
I asked my wife what she did. She was like, "I dunno... I pressed Home Menu Back or something."
So... if I had to guess on a procedure I think it would be like:
1) Update phone to JB if not updated already.
2) Use easy Virtualbox method to root.
3) Go through CDMA/DFS rigamarole[/URL] (NV only RevA_MFPA yadda yadda)
4) Reboot and set CDMA only. Use BuildProp Editor to set telephony.lteOnCdmaDevice=0.
4b?) At some point I used DFS to manually program MDN/MIN/SID, but I'm not sure this is necessary.
5) Install Safestrap 3.11
6) Install CM10 KEXEC with Safestrap 3.11 in slot 1.
7) Boot CM10 and *22800 away! Cross your fingers, hand the phone to whoever is next to you in despair.
8) ???
9) Profit!
I erased Safestrap slot, uninstalled recovery and uninstalled the app when I was done.
Click to expand...
Click to collapse
THANK YOU so much for making this post! I was finally able to activate my bionic after a week of reading the internet. lol. To update this post, yes, you need to do 4b. That step was what got me over the hump.

Anyone know the reason why no 3G? 1x works just fine. When toggle cdma/evdo, it still shows 1x.

I found some useful information about this about a month ago and some more details recently.
The system app com.motorola.setupwizard.phoneservice (VzwPhoneService.apk) actually intercepts attempts to call the activation numbers. The manifest file hinted at it with the names of the permissions and intents it has in there, and recently looking at decompiled source code confirmed it. The app is also responsible for SIM-based activation for Verizon 4G.
This app seems safe to disable for those on Verizon MVNOs; it is also on lists online of apps that people have safely disabled. When disabled, you can freely call up the activation screen with *228 or its variants.
Note that if you disable that app with a method that is permanent, like changing file extension, moving, or deleting, you should also disable com.motorola.setupwizard.controller (VzwController.apk) by one of those methods. If you ever wipe data, this will prevent it from getting stuck after the welcome screen if you tap start instead of doing the 4-corner bypass. (VzwController gets stuck waiting forever for the disabled VzwPhoneService) A side effect of disabling the additional app is that you no longer need to do the 4-corner bypass on first boot after wiping data when the phone isn't activated.

ShadyDreamer said:
I found some useful information about this about a month ago and some more details recently.
The system app com.motorola.setupwizard.phoneservice (VzwPhoneService.apk) actually intercepts attempts to call the activation numbers. The manifest file hinted at it with the names of the permissions and intents it has in there, and recently looking at decompiled source code confirmed it. The app is also responsible for SIM-based activation for Verizon 4G.
This app seems safe to disable for those on Verizon MVNOs; it is also on lists online of apps that people have safely disabled. When disabled, you can freely call up the activation screen with *228 or its variants.
Note that if you disable that app with a method that is permanent, like changing file extension, moving, or deleting, you should also disable com.motorola.setupwizard.controller (VzwController.apk) by one of those methods. If you ever wipe data, this will prevent it from getting stuck after the welcome screen if you tap start instead of doing the 4-corner bypass. (VzwController gets stuck waiting forever for the disabled VzwPhoneService) A side effect of disabling the additional app is that you no longer need to do the 4-corner bypass on first boot after wiping data when the phone isn't activated.
Click to expand...
Click to collapse
THIS! This so much! I had given up on flashing custom rom's after successfully switching my XT912 to page plus (3g/MMS working) and from there had just given up on custom roms after such a large headache. That was a year ago when the phone was coming from ICS to Jellybean (that was a rookies worst nightmare when google is your only quick resource: wrong versions, wrong tools, old information and didn't know a damn bit better. Ugh) anyways, I recently came back to try it out but found out yet again I was trying to use old information when getting through the activation process. This solved it though. I used Titanium Backup (trial version) to delete the system app/process and activation screen popped up on first try! If anyone else has the same issue that I had, where US Cellular answered my activation call, don't fret. I imagine it has to do with the SID (CDMA Network ID) but then I had let the phone sit for a minute and noticed at the bottom "a special number needs to be called to activate this phone" hit that button then the Verizon activation system answers and its good to go from there.
I'll now install safestrap and hopefully get a version of CM11 to run properly which caused this whole re-flashing process. I had a "working" stock rom that would constantly try to activate on phone startup, but 3g would work after skipping all those annoying screens, however when booting to CM11 it was not working with 3g.
Thank you again for that information, I can confirm com.motorola.setupwizard.phoneservice is the culprit to OTA activation problems when switching to PagePlus network.

[HELP] OTA KitKat update error on rooted D950

I have a (previously) rooted D950, and I can't get the OTA At&t update to install. I've completely removed root, and double checked through root checker that it's gone, and the update errors out every time with a message about having been rooted.
I read another thread where some people report being able to retain root after receiving the update THEN downgrading and rooting 4.2.2., then installing the OTA again, but it seems that I jumped the gun and rooted first, which is now causing the install to error out.
Has anyone else experienced this? Found a workaround? Ideas? Totally frustrating.
Sent from my LG-D950 using xda premium

Here is the link to a detailed guide . Dev hyelton's page includes links to AT&T ROMs.
If you need help with LG Flash Tool:
- Connect your phone with usb to laptop/computer and open device manager
- seek for Ports: COM & LPT, right click onto Android LTE usb port connection, click "properties", click "Advanced", then change port number to number 41, click "OK"
- DOWNLOAD LG Flash Tool and install .exe
- DOWNLOAD MegaLock.zip (3kb), unzipped (7kb)
- Exchange MegaLock.dll in your system folder "LG" with the unzipped MegaLock.dll file that you have downloaded
- Open LG Flash Tool, input .dll file of downloaded stock rom.zip folder and input .tot file of this folder
- Click onto USB instead of LAN, then click "OK"
- Left arrow at the window top should be enlightened now
- Click onto this arrow
- Wait for all popup windows telling milky way download and connections to fail
- Wait then for the check of CRC and .dll files
- One or all ports should be opened, "READY" enlightened
- Disconnect your phone from computer
- Connect again and watch the immediate start of the flashing process
- After completion you must install most of the app updates, update your LG and/or AT&T profile before installing kitkat update.zip
If you'll stick in updating stock rom to kitkat, watch my video on YouTube (it's about LS995 Sprint, but AT&T LG Flex will proof the same installation process):
Visit my blog at http://www.myreviewsofreviews.for the detailed description how to avoid bootloop during the installation of LG Kitkat update.zip via ADB sideload

Thanks, but this is not a fix. Unfortunately, that guide is of no use since his links are still down. Further, I was hoping for feedback from others who have experienced this issue, and found a resolution. I have read that this is also happening on devices that have not been rooted.
I am not looking to flash a rom through FlashTool. I'm looking to fix the OTA error. All I want to do is install the OTA update.

lorawithano said:
Thanks, but this is not a fix. Unfortunately, that guide is of no use since his links are still down. Further, I was hoping for feedback from others who have experienced this issue, and found a resolution. I have read that this is also happening on devices that have not been rooted.
I am not looking to flash a rom through FlashTool. I'm looking to fix the OTA error. All I want to do is install the OTA update.
Click to expand...
Click to collapse
Not sure what you were hoping for but the guide is correct process for your problem. You need to flash back to 4.2, don't touch anything in the way of modifying system files or deleting bloatware, sign into your main Google account, update all your apps...then root the phone and when it reboots look for the ota. I would give it a couple min to setup after flashing back to 4.2 so that it successfully finds the update rather than telling you you're on the most current software. I had your exact problem too, I was one of the first AT&T users on here to take the update I tried everything to
A: retain root with supersu features and some root cloaker programs etcetera
B: factory reset, call AT&T, to get them to push the update again because I just could not get it to successfully flash without detecting suspicion of root.
Flashing back to 4.2 to retain root worked for me over 4 times now on 3 different flex phones (I had some hardware and then software issues on my replacement model)
Sent from my LG-D950 using XDA Premium 4 mobile app

brittoking said:
Not sure what you were hoping for but the guide is correct process for your problem. You need to flash back to 4.2, don't touch anything in the way of modifying system files or deleting bloatware, sign into your main Google account, update all your apps...then root the phone and when it reboots look for the ota. I would give it a couple min to setup after flashing back to 4.2 so that it successfully finds the update rather than telling you you're on the most current software. I had your exact problem too, I was one of the first AT&T users on here to take the update I tried everything to
A: retain root with supersu features and some root cloaker programs etcetera
B: factory reset, call AT&T, to get them to push the update again because I just could not get it to successfully flash without detecting suspicion of root.
Flashing back to 4.2 to retain root worked for me over 4 times now on 3 different flex phones (I had some hardware and then software issues on my replacement model)
Sent from my LG-D950 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You say flash back to 4.2, but I am already on 4.2. Never left 4.2. That's the issue. The device is defective. They're sending me a new one.

lorawithano said:
You say flash back to 4.2, but I am already on 4.2. Never left 4.2. That's the issue. The device is defective. They're sending me a new one.
Click to expand...
Click to collapse
You didn't understand my post at all it seems, I gave you the instructions to flash back to STOCK which would have fixed your problem. I did accidentally word my post incorrectly saying "flash BACK to 4.2" obviously I knew you were on 4.2, so clearly I meant use the aforementioned guide to flash back to stock then take the update. Looks like you went another route, congrats
Sent from my LG-D950 using XDA Premium 4 mobile app

Huh? Wut
Not sure where things went wrong here.....
Me thinks some thread cleaning is in order...
Stand-by....
Cleaning finished.
Come on folks, let's relax and take a breath. Sometimes things just don't work and there's little to be done about it. If common known procedures don't work, then hopefully something else will, and just move along to something else.
Or in this case, the device is being returned which of course solves all.
No need for anybody to get all bent out of shape, what started out as being helpful, just took a bad turn somewhere for unknown reasons.
Relax, be cool....
MD

KitKat update on ATT G FLEX running on Tmobile.
This might be a stupid question . I have my ATT G FLEX D950 running on Tmobile. It is on Jellybean . I am unable to pull the Kitkat update and it says "Phone is not registered on network". I am assuming I need to get my phone on ATT network to pull the update. Am I right? is there any other way out ?

santy83 said:
This might be a stupid question . I have my ATT G FLEX D950 running on Tmobile. It is on Jellybean . I am unable to pull the Kitkat update and it says "Phone is not registered on network". I am assuming I need to get my phone on ATT network to pull the update. Am I right? is there any other way out ?
Click to expand...
Click to collapse
Kinda, yes.
I had the same problem. My phone was never activated on the ATT network so it would not recognize it. You have 2 options:
Get a prepaid sim from ATT, use it once and than put your Tmobile sim back in there or ask a friend that has ATT to use the sim for a few minutes. A text or a phone call is all you need.
Worked great for me.

[Q] ATT GS5 + Tmobile Rom + Tmobile SIM + Wifi calling !!! Anyone?!

Hello,
Is there any one using the ATT GS5 on Tmobile network (obviously Tmobile SIM) with wifi calling working ? (Please..please.. I know ATT does not have wifi calling, But if you use a Tmobile Rom with Tmobile sim, you expect to have it working) !!
If yes, would you please share which ROM you are using ? Also if there is a trick to make it wok please share it?
Thanks

no luck so far
This is not a solution, I just wanted to report what I have tried so far.
I have a G900A with a t-mobile SIM card. I called TMO to make sure wifi calling was enabled on my line. I used towelroot + safestrap to install the t-mobile Alliance rom (B4), as well as the latest stock TMO rom. So far, wifi calling does not work. It is always stuck on "Enabling" in the calling options menu. VoLTE doesn't work either, but I wasn't expecting it to. My guess is that there is something in the TMO baseband that makes these things work and that ATT phones don't have.
Any hints and ideas would me much appreciated!

No solution yet...
Guillaume2x said:
This is not a solution, I just wanted to report what I have tried so far.
Any hints and ideas would me much appreciated!
Click to expand...
Click to collapse
JJ here,
I tried this ROM - [ROM] G900TUVU1BNH5 ported from TMobile, rooted, deodexed, no knox, Download Booster
... everything works, nice and smooth, but the Wifi Calling is stuck "Enabling"...
Same boat.

My att s5 is unlocked and on the tmobile network. Your telling me i can flash the tmobile stock rom? And everything will be working properly, except wifi calling?

chronichemp said:
My att s5 is unlocked and on the tmobile network. Your telling me i can flash the tmobile stock rom? And everything will be working properly, except wifi calling?
Click to expand...
Click to collapse
Yes. In particular, Mobile Hotspot will work.

Guillaume2x said:
Yes. In particular, Mobile Hotspot will work.
Click to expand...
Click to collapse
Will everything else work properly? I mainly need the t mobile stock rom to enable mobile hotspot, I have an ATT phone and do not wish to trip efuse. Thanks

does anyone know if the same issue will happen with the international version?

On a similar topic, my dad has a AT&T Samsung Galaxy S5 which was sold in Malaysia. And I found out that his phone was not able to hotspot. I have downloaded the official firmware of Samsung Galaxy S5 for Malaysia and was going to use Odin to flash the firmware into his phone. Does that work and not brick the phone? The phone seems to be unlocked as it can be used here except the firmware and the phone is AT&T barnded. Any advise? Thanks
Sent from my iPad using Tapatalk

It all works!
Guys, I have some great news. Both wifi calling AND VoLTE now work on my SM-G900A on the T-mobile network. Here is what I did:
I installed the latest ATT firmware (OA1), released earlier this February. OTA update did not work, so I had to flash the original firmware (ANCE) via Odin, and then flash the two subsequent updates using update.zip on the SD Card. This will remove safestrap and root, but fear not.
Once my phone had AO1 installed, I used this tutorial to root the phone again. It invonves temporarily flashing an earlier (ND3) kernel, using TowelRoot, and then reflashing the OA1 kernel
With my OA1 rooted, I installed safestrap. Make sure you install busybox first.
With safestrap, I installed the T-mobile Alliance Rom (build B4).
Seconds after booting, both Wifi Calling and Voice over LTE work!
Enjoy!
Guillaume

Hi Guillaume,
Have you tried just installing the stock T-mobile 5.0 firmware on a Att GS5 ?
I have my GS5 in ND3 rooted and I'm on Tmobile, but the procedure you have seems really long...
I really need wifi calling as I'm travelling a lot and it allows to call my wife when I'm back in France.
Thanks

Guillaume2x said:
Guys, I have some great news. Both wifi calling AND VoLTE now work on my SM-G900A on the T-mobile network. Here is what I did:
I installed the latest ATT firmware (OA1), released earlier this February. OTA update did not work, so I had to flash the original firmware (ANCE) via Odin, and then flash the two subsequent updates using update.zip on the SD Card. This will remove safestrap and root, but fear not.
Once my phone had AO1 installed, I used this tutorial to root the phone again. It invonves temporarily flashing an earlier (ND3) kernel, using TowelRoot, and then reflashing the OA1 kernel
With my OA1 rooted, I installed safestrap. Make sure you install busybox first.
With safestrap, I installed the T-mobile Alliance Rom (build B4).
Seconds after booting, both Wifi Calling and Voice over LTE work!
Enjoy!
Guillaume
Click to expand...
Click to collapse
Thanks as this is great news for us G900A users on TMO! Question though: After 0A1 installed/backedup and Alliance installed, did you use safestrap [TWRP] to restore your data from 0A1 install?

Geek007W said:
Thanks as this is great news for us G900A users on TMO! Question though: After 0A1 installed/backedup and Alliance installed, did you use safestrap [TWRP] to restore your data from 0A1 install?
Click to expand...
Click to collapse
Actually no; I had been using the t-mo alliance rom using safestrap for a long time (just with the old ATT modem and kernel), so I just restored the data associated with that.
Some more info after a day of tests:
You can also install the 5th build of Alliance Rom, it works too
The camera sometimes glitches a bit; toggling HDR on/off fixes it
Except for the camera glitch I'm pretty happy with it!
Jojososo said:
Hi Guillaume,
Have you tried just installing the stock T-mobile 5.0 firmware on a Att GS5 ?
I have my GS5 in ND3 rooted and I'm on Tmobile, but the procedure you have seems really long...
I really need wifi calling as I'm travelling a lot and it allows to call my wife when I'm back in France.
Thanks
Click to expand...
Click to collapse
I might to try to create a flashable zip from the latest t-mobile lollipop release, keeping only the /system files, and see how that goes. This is really a shot in the dark, hoping that the 4.4.4 modem and kernel from ATT somehow work well enough with the t-mobile lollipop rom. Damn you locked bootloader!

Guillaume2x said:
Actually no; I had been using the t-mo alliance rom using safestrap for a long time (just with the old ATT modem and kernel), so I just restored the data associated with that.
Some more info after a day of tests:
You can also install the 5th build of Alliance Rom, it works too
The camera sometimes glitches a bit; toggling HDR on/off fixes it
Except for the camera glitch I'm pretty happy with it!
I might to try to create a flashable zip from the latest t-mobile lollipop release, keeping only the /system files, and see how that goes. This is really a shot in the dark, hoping that the 4.4.4 modem and kernel from ATT somehow work well enough with the t-mobile lollipop rom. Damn you locked bootloader!
Click to expand...
Click to collapse
Agree with the last expletive.
I did install in alliance B4 in slot 1 of Safestrap and both wi-fi tether and calling worked well. However, my G900A would not reboot or shutdown (dark screen) without a battery pull. After power up...worked?!?!
Did you install as "Stock" or in a slot?
Also have a G870A (Active). Do you know of anyone attempting the 0A1 method and Alliance Rom with the s5 Active?

I might to try to create a flashable zip from the latest t-mobile lollipop release, keeping only the /system files, and see how that goes. This is really a shot in the dark, hoping that the 4.4.4 modem and kernel from ATT somehow work well enough with the t-mobile lollipop rom. Damn you locked bootloader!
Click to expand...
Click to collapse
What would happen if I odin a Stock T-mobile firmware and let T-mobile update it ?
Will it update the Baseband etc ?

Geek007W said:
Did you install as "Stock" or in a slot?
Click to expand...
Click to collapse
I only use the stock slot.
B4 seems a bit more than stable than B5 for some reason. I get some signal issues with B5, and the fingerprint scanner sometimes fails. (It works when I first install B4, use it for a while, and then upgrade to B5. But if I do a /data wipe on B5, these issues appear. I have no idea why).
---------- Post added at 06:15 PM ---------- Previous post was at 06:11 PM ----------
Jojososo said:
What would happen if I odin a Stock T-mobile firmware and let T-mobile update it ?
Will it update the Baseband etc ?
Click to expand...
Click to collapse
You can't do that, the bootloader is locked.

Guillaume2x said:
You can't do that, the bootloader is locked.
Click to expand...
Click to collapse
Okay thanks,
So I started the steps, I've Odin the original firmware and factory reset on but my baseband stayed ND3...
Tried the OTA update hoping that it would work, but as expected it did not.
So I guess I'm at step 1 of your step one.
Then you said you pushed the update via sd card, where did you find the updates ?
Then I'll do the other steps!
Baby steps by baby steps, F... it's been a long time since I rooted my ipod 1st gen to crack my ps3!

Jojososo said:
Okay thanks,
Then you said you pushed the update via sd card, where did you find the updates ?
!
Click to expand...
Click to collapse
They are in the post that I linked to, under the troubleshooting section. If you want to keep your user data, use adb sideload instead of recovery

Guillaume2x said:
I only use the stock slot.
B4 seems a bit more than stable than B5 for some reason. I get some signal issues with B5, and the fingerprint scanner sometimes fails. (It works when I first install B4, use it for a while, and then upgrade to B5. But if I do a /data wipe on B5, these issues appear. I have no idea why).
Click to expand...
Click to collapse
OK. Installed in stock slot but ROM behaved much differently.
1. Wifi sms/mms work both send/receive but erratically.
2. Outgoing calls connect then immediately drop with local "cancelled" within a few milli-secs with a partial ring at the far end.
3. Can't receive calls at all. TMO network thinks I'm offline even though can receive a text.
3. Phone App GUI stutters when making a call.
4. Camera is basically not usable.
Where there any special steps you took to get this working installed in the stock slot? Has your install remained stable? Thanks in advance.

Geek007W said:
OK. Installed in stock slot but ROM behaved much differently.
1. Wifi sms/mms work both send/receive but erratically.
2. Outgoing calls connect then immediately drop with local "cancelled" within a few milli-secs with a partial ring at the far end.
3. Can't receive calls at all. TMO network thinks I'm offline even though can receive a text.
3. Phone App GUI stutters when making a call.
4. Camera is basically not usable.
Where there any special steps you took to get this working installed in the stock slot? Has your install remained stable? Thanks in advance.
Click to expand...
Click to collapse
My phone is still working flawlessly. What your are describing is what happened to me during the short period I reverted to the NG3 kernel in order to use Towelroot. Did you make sure to reflash the OA1 kernel once you were rooted? (before installing safestrap and, within safestrap, installing the Alliance Rom). I have found Alliance B4 to be more stable, so you could try that. Finally, a factory reset (wipe option in safestrap). Beyond that, you could try the whole thing again: flash the "downgrade to NCE" rom, which will remove safestrap and clean everything up; and take the tutorial from there.

Guillaume2x said:
My phone is still working flawlessly. What your are describing is what happened to me during the short period I reverted to the NG3 kernel in order to use Towelroot. Did you make sure to reflash the OA1 kernel once you were rooted? (before installing safestrap and, within safestrap, installing the Alliance Rom). I have found Alliance B4 to be more stable, so you could try that. Finally, a factory reset (wipe option in safestrap). Beyond that, you could try the whole thing again: flash the "downgrade to NCE" rom, which will remove safestrap and clean everything up; and take the tutorial from there.
Click to expand...
Click to collapse
Thanks again Guillaume,
Was running OA1 prior to Alliance B3, so just wiped Dalvik and Cache again, rebooted and left phone for the night. By next morning all was well except for the camera HDR issue. Once toggled it is OK until closed and reopened. Haven't had the time to look into whether there are Alliance B4 options which may affect this.
Have run it a few days and have had zero issues with Wi-Fi calling or tethering or apps: a very smooth experience.
Thanks again for your contribution. Also muniz_ri will find a bottle of wine on the doorstep soon. :highfive:

[Q] First Time Rooter, Gs6 SM-G920T, need help intresting problem cant find fix.

#1-"com.tmobile.pr.adapt (10001) has been granted superuser permissions for an interactive shell" pops up on my screen every 30 seconds on the bottom of my screen in a grey box.
#2- i also noticed that i can accept and recieve calls but i can not hear, nor can the other person hear me. if i use hangouts video call, skype, etc it works fine.
#3-i also tried to get rom manager to make a recovery and it says it needs to get CWD recovery to install a new software, the first thing we need to do is install a up to date version, we will begin that process now... etc.. then it says to get started you must first sset up a custom recovery, it gives two options a samsung galaxy s3 on metro pcs or a samsung previal 2 on boost mobile, or device not listed, when i click that it says "SM-G920T does not have an officially supported CWDR yet. Have you installed a CWD based recovery manually?" so im not sure what to do from there, or if i even need that. i have been a iphone user since day one went to android after reading up a lot on it, although rooting is quite different than jailbreaking it seems, i am incredibly excited to get started if i can get past these little problems and get started and figure everything out. ANY advice, or anwsers to these problems would be Greatly appreciated! thanks!
Also i went to dev options in settings and noticed the "OEM unlocking- allow the bootloader to be unlocker" was turned off, i dont know if this is necessary to root if i did something wrong by not turning it on or what, or if it may fix any problems above if i turn it on now. thanks!
I have a samsung Galaxy S6 (SM_G920T) . i Rooted and did not trip Knox, Although i did just remember that my fingerprint sensor is not working either.
Thank you guys so much this si a incredible forum i have spent hours and hours reading and researching before making this post i appreciate it so much!

#1 Freeze that ****. Use some root tool to freeze that T-mobile apk, seems u gave it root permissions at some point. I believe there are a lot of apps that you will want to do the same.
#2 ? No idea. Stock rom/kernel?
#3 What is this I don't even. Don't do that. Go to TWRP's official web, get your zeroflte (SM-GT920T) twrp and flash it via ODIN, or else get the recovery.img and use flashify. All that assuming you want a custom recovery.
You will need to unlock the bootloader if you are on 5.1.1. I believe locked will prevent changes or wiping anything on the OS partitions, even recovery (can someone confirm?)
I believe jailbraking and rooting should be pretty much similar, if not the same, as both target to grant the user root access to do whatever he pleases on the OS.
Welcome to android btw.

How did you root? Sounds like you used the modified sboot which causes no sounds in calls and nonfunctional fingerprint scanner. If so, flash back to stock and use a different rooting method. The rest, pretty much what the above poster stated

Root
I rooted using the version that I found the only one that works it seemed like, went to Odin put my phone In download mode and then put the boot loader download in BL and the. Put a something unikernel.sbin I believe, whatever the guide said also then it was done. I thought you couldn't use the twrp or custom recovery etc on tmobile one yet but I just read a thing about xtrestolite odex pure v2 which says it's for 5.1.1 and my model of phone but in the guide it says to root using CF auto root and a link there to it but the link doesn't have my phone on the list that the guide that clearly is my phone says to use I don't know if I'm missing something but I want to use it I understand most of it but I don't know if I need to unropt first and re root then use Odin and flash twrp that's supported on my phone then use that to recover the rom. Etc. The kernel that says is used in the guide is the same one I downloaded so do I need to remove it all then let it do that or?
Sorry if this didn't make sense I'm halfway there between confused and understood I have spent the last 10 hours reading and trying to figure this out though lol. Thanks guys!

Also
Sorry for adding more but also how do I flash back to stock? Search for the download to the stock image of my phone? Also I could only find one way of rooting everything else said it wasn't working yet or am I missing a big portion of something here?

Just flash the 5.1.1 firmware to return to stock. To root, flash unikernel with Odin. The other method you used was to not trip knox, but as you experienced has side effects. I had to Odin back to 5.1.1 myself. Can't have those issues

thanks!
so how do i flash back to 5.1.1? find the ling to completely stock 5.1.1 and flash through odin in the same spot and same way i flashed the kernel to root? also.. i rooted with " s6_UniKernel_v2-0003-ODIN.tar" is that not the one you were talking about?

CjetOKC said:
so how do i flash back to 5.1.1? find the ling to completely stock 5.1.1 and flash through odin in the same spot and same way i flashed the kernel to root? also.. i rooted with " s6_UniKernel_v2-0003-ODIN.tar" is that not the one you were talking about?
Click to expand...
Click to collapse
Yes, flashing to 5.1.1 works exactly like that. You need to get the version for your model (very important on this one) and then simply place that file in the AP field of ODIN while the device is in recovery mode. It is normal for ODIN to freeze for 2 minutes while verifying. Make sure to use a MD5 checker tool on the firmware before flashing.

Rooting has historically required more technical savvy and balls than jailbreaking, but PingPong made rooting the S6 brain-dead simple. CF-Auto root is still pretty painless, but you must make sure you have the right zip for your device.
Anyhoo, the quickest & easiest way to restore phone calls & fingerprint scan is to use Odin to get back to bone stock.
Next, use PingPong to root. After rooting, "com.tmobile.pr.adapt" will ask for root access. That is T-Mobile's "phone home" app and sends info about your device (probably including root status). Deny it root access and make sure you check "Remember my choice", and it won't bother you again. You will not lose any functionality by denying it root, so terminate that crap.
Don't bother with rom manager. CWM is archaic. If you want a custom recovery, use TWRP. You can install TWRP either using Odin or TWRP Manager app (it's free).
Good luck and have fun with your S6

CjetOKC said:
Sorry for adding more but also how do I flash back to stock? Search for the download to the stock image of my phone? Also I could only find one way of rooting everything else said it wasn't working yet or am I missing a big portion of something here?
Click to expand...
Click to collapse
Are you still rooted? If so, and if you are experiencing the call audio issue, go flash AOU's kernel. He has made a kernel for the tmo s6. that should eliminate your call audio issue. The finger print scanner is the only issue with flashing his kernel. Also, I rooted with the modded sboot, his TWRP and kernel, and I didn't trip knox
http://forum.xda-developers.com/tmo...recovery-twrp2-8-6-0-g925t-5-1-1-of6-t3143002

[EXPERIMENTAL][STOCK ROM]ZV9 Flashable zip (NEED TESTERS!!)

Hey guys,
Code:
DISCLAIMER
I AM NOT RESPONSIBLE IF YOU BRICK YOUR DEVICE. I AM NOT FORCING YOU TOO OR ANYONE ELSE TO FLASH AND BRICK THERE PHONE. ANYONE WHO WANTS TO RISK IT CAN/
So i made a flashable zv9 zip file HOWEVER i dont have the device with me at the moment to test it. Im NOT FORCING ANYONE to try it for me but if they wanna voulenteer to test it for me, it would be a pleasure. I have made this rom via dsxdia android kitchen and i got the system files from the original update.zip because the one from the tot wont open up after i merge them for some reason.
This will flash the system and boot.img files. I need someone to test it for me or risk thier device for a brick if they can. Yeah i know i should wait till get mines back from repair but im eager to get root on this thing. So it would be nice if someone that has an extra g4 laying around wanna helpout its development.
Requirements
-Rooted ZV6
-Flashfire
1. Root your phone http://forum.xda-developers.com/sprint-g4/development/stock-sytem-image-files-zv5-zv6-t3205640
2. Install FlashFire https://play.google.com/apps/testing/eu.chainfire.flash
3. Flash rom by tapping the + in flashfire and tap on flash zip.
4. Wait till its done flashing
5. If it bricks or something, try getting back into download mode and reflash zv6 tot file or zv9 using lgup or lgflashtool
Download:
http://www.mediafire.com/download/z7gc6dia923eyj0/LGG4_EXPERMIENTAL.zip
Mirror
https://www.androidfilehost.com/?fid=24391638059057798

Updated with steps and stuff

Is this rooted? If so, I'll give it a go!

ironbesterer said:
Is this rooted? If so, I'll give it a go!
Click to expand...
Click to collapse
Well its just stock right now didnt add root to it yet because i dont know if this is flashable via flashfire yet

Awesomeslayerg said:
Well its just stock right now didnt add root to it yet because i dont know if this is flashable via flashfire yet
Click to expand...
Click to collapse
I want to help you, but I'm planning on selling my phone soon to go to Verizon, so I don't want to mess anything up.

Chances are it will not boot due to not matching signature, I've tried different mixes when it first came out, and you will also need modem partition.
I have tried kernel, modem and system from MM over LP, resulting in a security error...
Good luck, hope you get your version working somehow.

ironbesterer said:
I want to help you, but I'm planning on selling my phone soon to go to Verizon, so I don't want to mess anything up.
Click to expand...
Click to collapse
Then why did you say you'd give it a go?
Anyways its alright.. oh I'm pretty sure you can use this on Verizon as I can use this on t mobile

Agimax said:
Chances are it will not boot due to not matching signature, I've tried different mixes when it first came out, and you will also need modem partition.
I have tried kernel, modem and system from MM over LP, resulting in a security error...
Good luck, hope you get your version working somehow.
Click to expand...
Click to collapse
Have you tried it with flashfire?

Updated it with mirror

Awesomeslayerg said:
Then why did you say you'd give it a go?
Anyways its alright.. oh I'm pretty sure you can use this on Verizon as I can use this on t mobile
Click to expand...
Click to collapse
You cannot use this phone on Verizon. I looked into it. T-Mobile is a whole other deal and even on T-Mobile you probably won't get all their bands.

mswlogo said:
You cannot use this phone on Verizon. I looked into it. T-Mobile is a whole other deal and even on T-Mobile you probably won't get all their bands.
Click to expand...
Click to collapse
Sprint LG G4 contains Bands 2, 4, and 12 which are all the bands T-Mobile uses.

Hi, have anyone tried to find out whether this method works?
my LG G4 sprint is stuck with ZV6 (customised, international) and also secure boot error 1006, unable to boot into download mode. I seriously need a solution.

Everything you need here thanks to Mayrer to get your Sprint to running with T-Mobile.
http://forum.xda-developers.com/spri...nlock-t3229801
Bands 2, 4, 12 are for bands T-Mobile.
Download PropEditor and edit these settings....Don't forget this step first!!
ro.build.target_operator=SPR => TMO
ro.build.target_country=US
ro.telephony.default_network => 9
telephony.lteOnCdmaDevice => 0 ....don't forget to save and reboot.
Along with Hidden Menu 5689#*991# to change your APN settings properly and set
Field Test => Modem Settings =>
PDP Setting => [5] APN Setting ...... now you have to select the bottom one then go into menu [ ] press until you see delete APN
you must do this because a bug I am seeing only allows the bottom APN setting to be used, I usually delete all until the APN I use is on the very bottom selection. no go back
Network Mode = Automatic => go back => RAT Selection = GSM/WCDMA/LTE auto
LTE Band Selection doesn't work proplerly so installing the modded Shortcut Master (Lite) from the link above be sure to go to
lotHiddenMenuMain (witout root) => LTE setting=> LTE Data Roam Config....and enable
Bar Roam Forced
Bar Roam Enabled
Roam Guard Forced
Roam Guard Enabled
Band 2
Band 4
Band 12 go back
Band 25 should be disabled unless you can use it. You cannot really set APN here.
I sometimes install the CDMA to GSM patch for global phones but I then have to re-do the PropEditor settings again, but it may be able to configure anything else that is missing, you can try to Adb Sideload the zip or use FlashGordon app to try to install, honestly I don't know if either worked for me for the patch.
This is what I configure to get my phone to working with T-Mobile.