THIS IS THE ALL THINGS GALAXY S4 (GS4) MODEL SPH-L720T THREAD
Note: This thread is primarily for the SPH-L720T not the SPH-L720. "T" is for Tri-band.
Please post any success and lessons learned (as it relates to the SPRINT SPH-L720T) on this thread. This thread is meant to be a centralized repository and discussion forum for all of us SPRINT SPH-L720T users. I believe that drawing all SPH-L720T users and resources together in one forum greatly benefits us all. This Operating Post (Post 1) is intended to be a summary of all that has been learned on this 720T thread. In reality, the OP can't contain everything, but it should be a huge jump start for everyone.
Nothing in this op is meant to condone or encourage you to mod your phone or to do something that may or may not be against your contract.
I will always try to give credit where credit is due...so if you see I have missed giving you credit for something on this post, please let me know. I will make the correction.
******SPRINT SPH-L720T BASICS ******
Version list is in release order from top to bottom. Tap on this version list for more info:
MK5 = 4.3 < Oldest
NAF = 4.4.1
NC6 = 4.4.2
NG5 = 4.4.2
NK1 = 4.4.2 (never became official)
OA3 = 4.4.2
OD2 = 5.0.1
OF1 = 5.0.1
OH1 = 5.0.1
OK3 = 5.0.1
PL1 = 5.0.1 < Newest (only listed on sammobile)
NOTE: Baseband = modem version
-----------------------------------------------------------
[COLOR=#00800]ROOTING[/COLOR]
Security policy updates are never ending and can potentially prevent any of the root methods below from working at any time. As always, try at your own risk.
K1MU SAFEROOT METHOD
k1mu's Saferoot method is confirmed to work on Sprint MK5. 4.3 and only trips the custom flag. It does not trip the Knox flag. I tried it on my MK5 and it worked perfectly. Saferoot will not work on KIT KAT 4.4.x (MK5) and above (NC6, NG5, etc.)
GEOHOT TOWELROOT METHOD
geohot's Towelroot v3 method with mod string "1337 0 1 7380 4 0" is confirmed to work on Sprint NC6 4.4.2 and only trips the custom flag. It does not trip the Knox flag(It will not work on NG5 or above). I tried it on my NC6 and it worked perfectly.
To find out more about mod strings, read the first post of the towelroot thread . In short, install towelroot apk, run the app, tap the title "Welcome to towelroot v3" three times and put in 1337 0 1 7380 4 0, then tap "make it ra1n" to root.
Towelroot does not install supersu for you. You will have to download supersu from the playstore and install it yourself.
If you recieve a device not supported message it DOES NOT necessarily mean that towelroot will not work on your device.
If I tap make it ra1n with the default mod string, I get this device is not supported message, but if I put the Samsung mod string in (1337 0 1 7380 4 0), it works and says your device is rooted.
CF-AUTO-ROOT METHOD
Note: All CF-ROOT methods will trip Knox flag.
CF-AUTO-ROOT for the regular 720 model is confirmed to work on 720T MK5 4.3, NAF 4.4, and NC6 4.4 (by Frukyyy post 340, judgeduck post 367, and daniel4653 post 415). JerryGNYC in post 964, pasted confirmation from mitch10102000 on another thread that CF-ROOT also works on NG5. JG96EVO on post 1854 confirmed this works on OA3. japush on post 2854 confirmed this works on OH1. Kjricker. post 3174, tha*noobster 3194, and SilverZero post 3223 confirmed this works on OK3. You can also odin the beta 720T CF-ROOT file on this link which is confirmed to work on NG5 by dward3662 in post 1177, or you can odin this 720T file which appears to be a little newer version confirmed to work on NG5 by droidzer1 in post 1349. This method will likely work on OF1, but no confirmations yet.
For OD2, jayshocka in post 2294 applied bilgerryan idea in post 2289 and confirmed turning off reactivation lock in the security screen and then using odin 3.07 with cf autoroot. jayshocka also successfully flashed twrp with flashify. Apparently, he could not use ODIN and successfully root his device until he turned off reactivation lock in settings.... more.... security. See pic post 2289. This method will likely work on OK3, but no confirmations yet.
1) Download and unzip the CF-Auto-Root-....zip
2) If you end up with a recovery.img and cache.img file, you've extracted twice. You need to end up with a .tar.md5 file - don't extract that one
3) (USB ) Disconnect your phone from your computer
4) Start Odin3-vX.X.exe
5) Click the AP or PDA button, and select CF-Auto-Root-....tar.md5
6) Put your phone in download mode (turn off phone, then hold VolDown+Home+Power to boot - if it asks you to press a up to continue, press the up volume button on the side of your phone
7) (USB ) Connect the phone to your computer
8 ) Make sure Repartition is NOT checked
9) Click the Start button
10) Wait for Android to boot
11) Done
TWRP SUPERSU METHOD
lost_ in post 1181 confirms this method for stock NG5. JG96EVO on post 2854 confirmed this works on OA3. , and this method will trip the Knox warranty flag.
This TWRP method is confirmed working on OD2 by fuzzybuffalo in post 2611 as long as you ensure reacativation lock is off in the security screen inside the new knox app first as described in the cf-auto root section above. Confirmed to work on OH1 by Pioneer post 2845. Confirmed on PL1 by bgmg
1) Get TWRP tar for jfltespr
2) Download supersu zip installer to either internal storage or ext SD
3) With the phone in download mode and Odin set to NOT auto-reboot, all other options UNchecked, flash TWRP into PDA slot (or AP slot if you are using a newer version of ODIN that doesn't have a PDA slot). When done, remove battery and USB
4) Power up into recovery. If it's still stock recovery instead of TWRP, just redo step 3
5) Flash supersu.zip
Done. The phone is now rooted. After rebooting system, open SuperSu and if you want to fully disable Knox, say yes to the prompt.
KINGROOT METHOD
Clipless in post 3720 confirms this method works on PL1
That's all the confirmed root methods so make your choice, and PLEASE post any significant findings on this thread.
ROOT METHODS NOT YET CONFIRMED ON 720T
NOTE: These methods are not yet confirmed on 720T but may work. If you try one of these methods on a 720T please confirm on this thread.
Sunderwear's method is another root method confirmed to work on KK 4.4 on another model GS4 phone (NOT 720T). This will likely trip Knox.
Framaroot is another apk root method, and apparently it auto installs supersu. Framaroot has not yet been confirmed on 720T. Not sure if this will trip Knox.
[COLOR=#00800]CUSTOM FLAG RESETS[/COLOR]
As far as the best reset for the custom flag on Sprint MK5 in case you ever want/need to get back to official:
Several methods have been noted, and they are listed in post 16 of this thread. I used Wanam with Xposed Framework to fake my custom flag back to official. Why? I have no idea, because on my Sprint MK5 the phone still boots up normal even when the flag says custom unlike the ATT GS4 which shows a big unlock picture with the word custom during boot in place of the Samsung Galaxy logo. Basically I faked the flag back to official just to satisfy my OCD.
[COLOR=#00800]XPOSED[/COLOR]
OH1 AND OK3
triiuzii in post #3429 confirms this method will allow Xposed to work on OH1 and OK3.
Download xposed installer from this thread; http://forum.xda-developers.com/showthread.php?t=3034811
or just click this link; http://forum.xda-developers.com/attachment.php?attachmentid=3383776&d=1435601440
Then you also have to download the zip file from this thread; http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-5-0-x-t3455992
or just click here; http://forum.xda-developers.com/attachment.php?attachmentid=3868339&d=1473312864
Install xposed and then reboot into recovery and flash the zip file. Your phone will take a while to update, but after it's done, xposed will be installed.
If you happen to run into a problem, also download this zip file; http://forum.xda-developers.com/attachment.php?attachmentid=3868338&d=1473312864 . It will uninstall what you tried to do.
V6 SNAPDRAGON VERSION
Bilgerryan in post 3454 confirms this version works on the "v6 Snapdragon" version here- http://forum.xda-developers.com/showthread.php?p=60857320
[COLOR=#00800]HOTSPOT[/COLOR]
WIFI TETHER APP
youngnex in post #144 and #156 confirms Wifi Tether Router to work on 720T (the app requires root permission and is now available in the play store again. This has been confirmed working on MK5, NAF, NC6 (judgeduck post 367), NG5 (dward3662 post 1132), OA3 (curtwest1 post 2248 ), OD2 (post 2747), and OH1 (guho post 2987) with the following settings (This will likely work on OF1 and OK3 also, but it's currently unconfirmed). :
WiFi Channel: 1 or 6Interface: wlan0Method: 3-HostApdNo Firmware Reload: UnCheckedDrivers: nl80211Wifi Mode: WiFi - NPrevents Standby: CheckedMTU Adjust: UnCheckedHostApd Patch: UnCheckedPower Transmit Mgmt: CheckedLTE Tether Patch: UnCheckedNo Disable Wifi: UnCheckedUnder "Advanced Wif Settings" uncheck the "Always allow scanning"If you are having problems losing connection try changing the WIFI Channel from 1 to 6 or from 6 to 1. Originally, I had to change the channel to 6 to eliminate disconnects. Worked great for months. Installed a recent Wifi Tether Router update (5/3/14) and had to change back to channel 1 to eliminate the disconnects.
NATIVE HOTSPOT SQLITE TELEPHONY.DB METHOD
A working stable solution has been put together from a few posts on this thread. They include muddogknls in post 798, jdonmc1948 in post 818, and then finally stabalized by Cooljb in post 1140. This has been confirmed on at least NC6 and NG5; however, it will likely work on all 720T versions and it requires root on at least NG5 (may not need root on NC6 and older). This will likely work on OF1, OH1, and OK3 also, but it's currently unconfirmed.
Instructions:
1) Download sqlite editor app from the app store.
2) Open the app and give it root permissions. It should populate a list.
3) Navigate to "/data/data/com.android.providers.telephony/databases/" and tap on the "telephony.db" file.
4) Tap "carriers".
5) Add dun parameter to "type" column of the last two entries (APN2 LTE internet and APN2 EHRPD internet), Do not allow a space between the comma and dun (i.e. default,mms,dun), and make sure "current" column is 1 for last 4 entries (see picture examples in post 1209). Finally, reboot and you will be good to go!
Note: If you perform an "Update Profile" or a factory reset in the future after doing this mod, it will overwrite/modify your telephony.db file, your native hotspot will likely become unstable after the next reboot, and you will have to perform these steps all over again to enable and/or stabalize your native hotspot.
APN METHOD
oberon567 post 3275 confirms a third method of adding dun to your APN type (if your APN section is unlocked) so that it reads "default,supl,mms,dun". May need to reboot to take affect. oberon567 indicates that it is limited to connecting to only a single device at a time (at least for his carrier).
[COLOR=#00800]CUSTOM RECOVERY[/COLOR]
Successful Custom Recovery tools posted so far include:
1) philz 6.1.3.1 by bthorne79 post 41
2) philz 6.30.2 by al4d post 413
3) TWRP 2.7.0.1 by mogul420 post 459.
[COLOR=#00800]ROMS[/COLOR]
Note: When flashing ROMs that are not fully compatible with the 720T. In some cases you go directly to Digital Roaming, but in others you might brick the device.
It has been reported that currently you will lose WiFi calling capability if you flash asop ROMs. So far, I have seen no confirmations of WiFi calling working on asop ROMS
In post #470, glassman326 has confirmed with photo evidence that while the startup spark graphic is lost when flashing a regular 720 rom, spark still works and is not actually lost (at least with the SlimKat NC6 ROM; however, this probably holds true for all 720 ROMs); however, you may be able to restore the spark graphic or actual spark (if it's really gone) by following the instructions in the MISC section below.
bthorne79 in post 3348 also confirms "Spark does work on aosp ROMs..." and "Octos has a spark tester and he gets his spark speeds also"
In post 3075, TheHumansAreDead confirms Blisspop v4.0.3 Official 20151112 jfltespr (Lollipop 5.1.1) runs as smooth as butter on our sph-l720t with 3G and LTE service on Ring+.
He had to edit the APN settings for Ring+ to get the data working and posted that info here.
Tap this for Official BlissPop thread
In post 1853 bthorne79 confirms every rom for aosp now with TW works on SPH-L720T.
In post #158, frukyyy confirms Sacs 4.3
daniel4653 in post 439 confirms most touch wiz Roms work with triband model.
bilgerryan in post 2261 and 2636 confirms this Wicked X ROM works on 720T.
FlashFire ROM for 720T credit muniz_ri post 2503.
Liquidsmooth Confirmed by captkang post 2764.
Tap here to download Stock Rooted Deodx ROMs credit bthorne79 post 1433.
antibiotic1 in post 1436 has figured out how to get C-ROM to work.
If you decide to use the cm12 rom you will want to go to post 2293 by tyxavier13 and download the fix he posted.
Per shadowcliffs post 1934 , the tw lollipop rom S4 Echoe Rom v42 works well on our l720t with the AEL kernel. You can even flash the ported Note 4 camera.
As working-non working status or issues should be modem specific shadowcliffs offers this on NG5 :
1) ROMs working well:
1.1) Stock NG5, OA3:
1.2) [UNOFFICIAL][5.0.2][CM-12.0] CyanogenMod 12 for jfltespr (2015-01-26 / FINAL: Working
1.3) [LXR22G][5.0.2] Team OctOs Oct-L: Working
1.4) [OFFICIAL] CyanogenMod Nightly Builds for jfltespr
Followings are reported working by others in this thread:
1.5) C-Rom 7.1 (#78 ) : some issues where it says digital roaming sometimes. It didn't seem to be as good a connection for LTE as stock rom and it dropped to 3G more often.
1.6) SuperS4 (#80): the newest SuperS4 does have the spark icon.
1.7) BeanStalk ROM (4.4.4) : It's completely stable and has just about every possible customization baked right into the ROM including xposed installer.
1.8 ) SlimKat ROM (4.4.4): keeps the ROM stock,only customize a little, always a rock solid ROM with exceptional support and almost perfect code.
1.9) PacMan ROM (4.4.4)：
1.10) Mahdi ROM (says digital roaming instead of Sprint but works perfectly)
2) Roms Not working so well:
2.1) Sacs_Custom_Rom_V3_NG2_9_24_14 : Wifi not working. ktoonez kernel fixes WiFi but with lag. The issue might be modem specific.
2.2) [ROM] [ jfltespr ][ Feb 10 ] AICP - 8.0 - LP 5.0.2_r1 | OFFICIAL NIGHTLIES: Phone runs warm / battery drain
2.3) 【5.0.1】Google Play Edition 【JFLTE-GPE】, 2-23-2015 build: Phone runs warm / battery drain
（Below are reported by others）
2.4) Triforce + ktoonez kernel to get the WiFi working: FC from time to time though.
Click to expand...
Click to collapse
STOCK ROOTED ROMS
From bthorne79: These are STOCK ROOTED BUILDS
DOWNLOADS
https://www.androidfilehost.com/?w=files&flid=20593
The roms must be be flashed in custom recovey.
How to flash rom
1: Reboot phone to recovery
2: Make a back up of current rom
3: Wipe clean
4:Flash rom
5:Reboot and wait about 4-5 for boot to finish
How to flash modem
Use Odin v3.09
1: Untick Autoreboot
2: Flash modem in the phone slot (CP)
3: Reboot once again into Download Mode using (Vol Down plus Home button combi)
4: Flash Modem once more
5: Once done,unplug then reboot device manually.
If this doesn't work, try repeating the flash process again while rebooting manually and with auto-reboot option turned off.
If you have a issue with wifi connetion make sure you are on the correct baseband.
modems will be in the extra folder named with the firmware build along with stock boot.img, recovery and the NON_HLOS.bin(wifi fix)
Tap on these links below for some more great SPH-L720T rom threads:
Shaddowcliffs testing results of Roms for SPH-L720T thread
bthorne79 SPH-L720T stock roots roms thread
[COLOR=#00800]UNLOCKING FOR USE ON OTHER CARRIERS[/COLOR]
The following unlock for overseas solution has been brought forward by kmani.k78 post 1355 and mkardash in post 1363.
Tap here to go to the unlock solution thread and follow the directions on post one.
aalyatim in post 1392 offers a unlocking solution for domestic use which apparently requires the user to downgrade the modem to MK5 first. MK5 modem can be found in the downloads section at the bottom of this OP. Also check out instructions from broad_st_bully post 1626.
You can also use Galaxy tools to perform a sim unlock.
In regards to galaxy tools, idone provided this wisdom: To use GSM outside the US it is as simple as pressing the unlock sim button in galaxy tools. If you want to use it in the US: only S4, Note 3, and Mega's(Mega's that haven't been updated to 4.4.x) can, but you also need to downgrade baseband (modem) to MK5 first, then navigate to UE SETTING & INFO>SETTING>PROTOCOL>GCF>[1] and reboot. For more information on How to get galaxy tools, go to the "NATIVE HOTSPOT GALAXY TOOLS APK METHOD" area in the HOTSPOT section of this op.
UNLOCKING YOUR APN's
Use Galaxy Tools to change the sales code to XAS. This will unlock your APNs
[COLOR=#00800]TOGGLES[/COLOR]
Including: MobileData & WiFiHotspot toggles.
klabit87 in post 822 posted this as a working solution: .
http://forum.xda-developers.com/showthread.php?p=43042030
See post 822 for more info.
Note: Brightness toggle doesn't work on 720T and SmartPause toggle is already present on 720T stock.
...Or use Galaxy tools to turn the toggles on for you (requires root). For more information on How to get galaxy tools, go to the "NATIVE HOTSPOT GALAXY TOOLS APK METHOD" area in the HOTSPOT section of this op.
SURFING WHILE TALKING
It is the sim/network that determines whether the phone is capable of simultaneous surf and talk. ATT sim which will switch you to the ATT network, will allow the phone to surf and talk. Same with a Verizon sim/network. The sprint sim/network does not support this.
Once you have a sprint sim installed and activated, you can only surf and talk when connected to wifi. The device will use your wifi for surfing and your cellular for phone call (if your WiFi calling is off). If you do not have a wifi connection, you cannot use cellular for simultaneous phone call and surfing on sprint sim/network.
Sprint representative advised me that Sprint is rolling out simultaneous cellular Talk and Surf capability sometime this month (September 2018). He said they are using VOIP technology to add this dual simultaneous cellular capability to their subscribers, and that it is a different method than what is used by AT&T and Verizon.
It is called Sprint Plus and its only available to android initially, and in select areas. My understanding is this software fix/enhancement is being pushed only to Galaxy S8 and newer devices initially.
Read this Sprint Plus web page:
https://www.sprint.com/en/support/solutions/services/faqs-about-calling-plus.html
[COLOR=#00800]MISC[/COLOR]
HOW TO REPROVISION YOUR PHONE
From your dial pad type ##72786#
LOST SPARK GRAPHIC AND SOME OTHER SPRINT SETTINGS
When I upgraded to stock KitKat I lost my boot spark graphic. shadowswittness 506 and frukyyy in post 621 provided the location of an AOSP tool on the play store called customization refresh. Some sprint settings including spark can often be restored via this tool.
I downloaded and ran step one. It went through a series of boots, and (for whatever it's worth) it restored my spark boot graphic on the last reboot. I did not lose anything by running step one. I have no idea what happens on step two.
Not sure if this will work on flashed roms to restore the spark boot graphic.
BLOAT WARE LIST
Here is one I found: "Safe to Remove Applications" for our Sprint GS4's List!
HOW TO HIDE YOUR UPGRADE NOTIFICATIONS
If you want to stay on your current version and don't want see the upgrade notification until you are ready and toy are on kit Kat or lower, I recommend robtheslob's solution post #118 which uses the NotifyClean module with Xposed Framework to hide the notification. Here are the instructions:
1. Download and Install NotifyClean and turn it on in the Xposed Framework.2. Inside CleanNotify, tap "Google Services Framework" or "Google Play Services" depending on what version OS you are running.3. Tap "System Update Downloaded". It should now be highlighted in red. If you don't see this choice, it means that you did not have NotifyClean installed prior to the upgrade notification firing/appearing. A notification has to fire once for NotifyClean to capture it. If you installed NotifyClean after receiving the update notification, reboot your phone a couple of times. This should cause the notification to re-fire and NotifyClean to capture it. At this point, you should now be able to go back into the module and see the System Update Downloaded under Google Play Services. Don't forget to tap it and turn it red. When it is in red, it is turned off.4. Press the back button to back out of module and reboot.NOTE: You can go back into NotifyClean at any time in the future, unhide the upgrade notification, reboot, and upgrade to NG5 when you are ready.HOW TO GET TO SERVICE MODE MENU
(from kskh post 862)
*#0011#
Menu > Back
Menu > keyInput "Q"
Menu > keyInput "0000"
Wait for few seconds
There is a beta xposed framework for lollipop that may allow notify clean to work on lollipop. We have no confirmations though.
Here is another solution. It's called Disable notifications credit frukyyy post 2784. Note: This solution may hide other Google Play service notifications for other apps or all your apps, but is should work on all android versions.
OTHER CODES
##3282# resets data > fuzzybuffalo post 2242
##72786# resets network, but might prompt for MSL code > fuzzybuffalo post 2242
MOBILE ODIN
From shadowcliffs post 2183, here is how to get mobile odin to work.
Just set ro.product.model to SPH-L720 in build.prop. It looks like:
ro.product.model=SPH-L720
Save, reboot, then mobile odin will recognize the device and start downloading what it needs.
[COLOR=#00800]ODIN BASICS[/COLOR]
BL = Bootloader
AP = PDA/Firmware
CP = Phone/Modem/Baseband
[COLOR=#00800]DOWNLOADS [/COLOR]
Samsung Odin Tutorial credit bthorne79 post 1508
XDA Odin Guide
Samsung Odin credit to fuzzybuffalo #2668.
Stock no-root OD2 tar for those who don't want to wait for a long Sam-mobile download credit MexPwrEng post 2749
USB Drivers credit to daisflaque post 689
Samsung Kies
All Stock Firmwares
Firmware Faster Downloads by bthorne79 post 2701
Stock rooted busybox deodx MK5 zip from bthorne credit bthorne79 post 1663. Use a custom recovery to flash.
Chainfires new SuperSu forum credit bigsamda1st
NC6>NG5 OTA credit Jshugzda post 928. Use stock recovery to flash.
OA3>OD2 OTA credit FivePiece post 2507
Deodexed OH1 credit emkeene post 3100
FULL OH1 Firmware credit Kjricker post 2847
Xposed Framework Installer
Stock NC6 Kernel credit 2WhiteWolves post 1126
NC6 MODEM credit bthorne79 post 1340. Modems go in CP/phone slot in ODIN.
MK5 MODEM .bin file post credit BradGrenz and broad_st_bully post 1623
NG5 & NC6 Odin modems and the Stock Rooted Deodx ROMs credit bthorne79 post 1433. Modems go in phone slot in ODIN. Use a custom recovery to flash ROMs.
Stock Odin recovery for ng5 credit bthorne79 post 2056
OA3 stock root and all other files(modem recovery and few others) credit bthorne79
[COLOR=#00800]THANKS[/COLOR]
Let me end by saying thank you to all you developers and senior members for all your hard work. We can not appreciate you enough.
Any feed back is always appreciated.
[COLOR=#00800]CONCLUSION[/COLOR]
Though I am a certified techy with many years of experience in the computer and network world, this is my first Android phone, and I had everything to learn about Android and my Samsung phone. As I began to read and try to learn everything about something I knew nothing about, I realized that I never completely understood what I was reading, because things were never fully explained, often assumed a prior knowledge, and were spread out all over the net in different threads and different forms. If I was gonna catch up fast and learn what I needed to learn about my 720T, I determined that I needed to draw every SPRINT 720T user to one place (as much as is possible), and that gave birth to the XDA "EVERYTHING SPRINT Galaxy S4 Model SPH-L720T" thread and the concept of this OP. I figured this would really help me and others, and for me, it has been a real success.
Wouldn't it be great if there was a thread like this for all phone models? If you use another phone and are just stopping by, feel free to copy the OP layout and start a thread like this for your phone.
If you like having an "All Things SPH-L720T" thread, please click thanks.
Great thread.
Sent from my SPH-L720 using Tapatalk
daniel4653 said:
Rule number one, search before you post. Something I have a feeling that you did not do since the rooting method has already been answered.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
------------------------------------------
With utmost respect, your feelings are incorrect. I did search for hours. I did not find any confirmation of rooting the MK5...I only found older models such as the MK2. That being said, I am as human as the next guy. If I missed it, and you know where it is, Please advise.
Thanks,
bgmg
Cf auto root is confirmed to root the mk5
Sent from my SPH-L720 using Tapatalk
SPRINT Galaxy S4 Baseband = L720TVPUAMK5 Model = SPH-L720T
daniel4653 said:
Cf auto root is confirmed to root the mk5
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
-------------------
Daniel,
Thank you very much. Not sure where you found that but I take your experienced word for it. I searched off and on for days, read for hours, and didn't see it...so I really appreciate your confirmation and instantly gave you a like.
About three weeks ago, I owned a brand new ATT I337 model, used saferoot on it, and it tripped the custom flag. I had to use ted77usa ATT unbrick method to get the custom flag turned off so that I could return the phone.
Now that you have confirmed that CF will root the MK5, I'll do some more re-reading to try and confirm that CF method will not trip any flags (such as custom and knox warranty).
Any more guidance would always be appreciated.
bgmg
I'm interested in your outcome as well. I purchased this model when sprint put it on their site. I've been following a couple threads here but never saw a definitive answer on it working.
Sent from my SPH-L720T using Tapatalk
bgmg said:
-------------------
Daniel,
Thank you very much. Not sure where you found that but I take your experienced word for it. I searched off and on for days, read for hours, and didn't see it...so I really appreciate your confirmation and instantly gave you a like.
About three weeks ago, I owned a brand new ATT I337 model, used saferoot on it, and it tripped the custom flag. I had to use ted77usa ATT unbrick method to get the custom flag turned off so that I could return the phone.
Now that you have confirmed that CF will root the MK5, I'll do some more re-reading to try and confirm that CF method will not trip any flags (such as custom and knox warranty).
Any more guidance would always be appreciated.
bgmg
Click to expand...
Click to collapse
You're welcome. And I found it in the same thread as I found that a member successfully rooted their MK5 triband with this method.
https://www.youtube.com/watch?v=s_hXUJ-u-cw&feature=youtube_gdata_player
Sent from my SPH-L720 using Tapatalk
SPRINT Galaxy S4 Baseband = L720TVPUAMK5 Model = SPH-L720T
wlc108 said:
I'm interested in your outcome as well. I purchased this model when sprint put it on their site. I've been following a couple threads here but never saw a definitive answer on it working.
Sent from my SPH-L720T using Tapatalk
Click to expand...
Click to collapse
-----------------------------------
Thanks WLC108. I'm not sure when I'm going to try it yet. May be a week or so. I want to do more reading and hopefully get some more feedback on the MK5.
A few weeks ago, I bought a brand new ATT model S4. I tried a few methods of rooting it that failed, and I think CF was one of them. In the end, I used the saferoot method posted by ted77usa for the att model and it worked perfectly. It tripped only the custom flag.
Resetting the custom flag was difficult but I was able to do it with ted's expert help. This allowed me to return the ATT phone, because I wanted to switch to Sprint. Of course that does not mean that CF won't work on my new MK5 Sprint model. Daniel is a senior member and confirms that the CF method will work on the MK5...so that should be reliable.
I really like the saferoot method best. Ted indicates it will work on the Sprint model but since he is more of an ATT guy, I'm not sure I should try it. For now, I need to do more reading on the CF method again to refresh my memory.
I've said all this only to say, I'm not completely new at this, I have a good idea what to look for and ask about before trying to root and prevent getting stuck.
ted77usa was simply awesome at assisting me (a real noob at the time). I hope to find someone else on the sprint side that will help me like ted did.
Currently, I'm trying to confirm whether CF will trip any flags, and if so, can the flags be undone later if needed.
Feel free to follow the thread and hit the "Thanks" button if you like.
Note that CF will flag Knox.
Sent from my SPH-L720 using Tapatalk
bummer.....then I don't want to use CF this early in my contract because it trips the knox flag.
Is there a method for resetting the knox flag later?
bgmg said:
bummer.....then I don't want to use CF this early in my contract because it trips teh knos flag.
Is there a method for resetting the knox flag later?
Click to expand...
Click to collapse
At the moment there isn't. You may be able to use the Kingo app. I know it works on the regular sprint gs4 without tripping Knox. It should work on the triband version.
Sent from my SPH-L720 using Tapatalk
Sprint galaxy s4 users
__
daniel4653 said:
At the moment there isn't. You may be able to use the Kingo app. I know it works on the regular sprint gs4 without tripping Knox. It should work on the triband version.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
----------------------------------
daniel4653,
k1mu's saferoot method is confirmed to work on Sprint MK5 and only trips the custom flag. It does not trip the Knox flag. I haven't tried it on my MK5 yet, but will soon (trying to decide if I want to wait for kit kat. I did try it on My ATT GS4 4.3 android with knox a few weeks ago, and it worked perfectly.
Check it out at http://forum.xda-developers.com/showthread.php?t=2565758 post 1
At the bottom of post 1, you will see the reported success on Sprint MK5
If this is helpful, please add a Thanks.
bgmg said:
----------------------------------
daniel4653,
k1mu's saferoot method is confirmed to work on Sprint MK5 and only trips the custom flag. It does not trip the Knox flag. I haven't tried it on my MK5 yet, but will soon (trying to decide if I want to wait for kit kat. I did try it on My ATT GS4 4.3 android with knox a few weeks ago, and it worked perfectly.
Check it out at http://forum.xda-developers.com/showthread.php?t=2565758 post 1
At the bottom of post 1, you will see the reported success on Sprint MK5
If this is helpful, please add a Thanks.
Click to expand...
Click to collapse
Hmm I'm surprised the Op never added the regular SPH-L720. I confirmed it on the thread that it worked.
Sent from my SPH-L720 using Tapatalk
k1mu's method worked nicely on my mk5. Now to wait for a hotspot mod for this ver
Sent from my SM-T210R using Tapatalk
Thanks wlc108
Here is some more news.
According to k1mu The "Custom" flag is set by a scanner that looks at the content of your phone, searching for anything that's modified or unexpected.
To clear the custom flag, un-do any changes you've made to the phone (like "de-bloat"), remove busybox, unroot, then reboot. Wait an hour and reboot again. You should no longer have any changes from stock, so you'll no longer be custom. It's easier, if you're planing to return your phone, to just flash a full-wipe factory stock ROM. (Not a "Stock" ROM, but factory stock from Samsung unmodified.)
I have not confirmed this works on MK5....and when I rooted my ATT GS4 a few weeks ago with k1mu saferoot, I never added anything else to it that requires root (such as nobloat, appquarantine, busybox or anything else). I did a full unroot and never saw the custom flag change back to official. I did several reboot attempts over the next few days and it never returned to official. It always said custom. It was not until I did ted77usa's unbrick method that it switched back to official. I then returned that ATT GS4 and switched to Sprint MK5. I'm pretty certain that ted77usa unbrick method for ATT GS4 would not work on the Sprint GS4.
I've also been told:
If custom doesn't go away do a full wipe either via odin, or k1mu's preferred method using the carrier-utility or kies.
or use Triangle Away. Gets rid of custom when you reboot
or use wanam exposed to fake the system status and it will allow you to be samsung official, 0x0 with root
I've not tested any of these yet, but hope to soon
Please click thanks if you are finding these postings helpful to read.
bgmg said:
Thanks wlc108
Here is some more news.
According to k1mu The "Custom" flag is set by a scanner that looks at the content of your phone, searching for anything that's modified or unexpected.
To clear the custom flag, un-do any changes you've made to the phone (like "de-bloat"), remove busybox, unroot, then reboot. Wait an hour and reboot again. You should no longer have any changes from stock, so you'll no longer be custom. It's easier, if you're planing to return your phone, to just flash a full-wipe factory stock ROM. (Not a "Stock" ROM, but factory stock from Samsung unmodified.)
I have not confirmed this works on MK5....and when I rooted my ATT GS4 a few weeks ago with k1mu saferoot, I never added anything else to it that requires root (such as nobloat, appquarantine, busybox or anything else). I did a full unroot and never saw the custom flag change back to official. I did several reboot attempts over the next few days and it never returned to official. It always said custom. It was not until I did ted77usa's unbrick method that it switched back to official. I then returned that ATT GS4 and switched to Sprint MK5. I'm pretty certain that ted77usa unbrick method for ATT GS4 would not work on the Sprint GS4.
I'm still looking for confirmation on returning the custom flag back to Official on MK5 after using k1mu saferoot.
Please click thanks if you are finding these postings helpful to read.
Click to expand...
Click to collapse
If you're talking.about the custom/official that is shown on download mode you could Odin MK5 once you are unroofed and that will reset everything to official. It did for me on MK2 after using safe root .
Sent from my SPH-L720 using Tapatalk
daniel4653 said:
If you're talking.about the custom/official that is shown on download mode you could Odin MK5 once you are unroofed and that will reset everything to official. It did for me on MK2 after using safe root .
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
I'm looking for a custom recovery and i don't mind tripping the Knox any help.
Custom Recovery
bthorne79 said:
I'm looking for a custom recovery and i don't mind tripping the Knox any help.
Click to expand...
Click to collapse
Greetings. I see you are a senior member, which means you understand more of this terminology then I do, so forgive me if I misunderstand your question.
If by custom recovery you mean change the "SYSTEM STATUS = Custom" flag back to "SYSTEM STATUS = Official" try one of these methods:
According to k1mu the saferoot developer, "the 'Custom' flag is set by a scanner that looks at the content of your phone, searching for anything that's modified or unexpected.
To clear the custom flag, un-do any changes you've made to the phone (like 'de-bloat'), remove busybox, unroot, then reboot. Wait an hour and reboot again. You should no longer have any changes from stock, so you'll no longer be custom. It's easier, if you're planing to return your phone, to just flash a full-wipe factory stock ROM. (Not a 'Stock' ROM, but factory stock from Samsung unmodified.)"
I've also been told:
If custom doesn't go away do a full wipe either via odin, or k1mu's preferred method using the carrier-utility or kies.
or use Triangle Away. Gets rid of custom when you reboot
or use wanam exposed to fake the system status and it will allow you to be samsung official, 0x0 with root
I've not tested any of these yet, but they seem safe enough.
When I had a AT&T GS4 and did the safe root, I was changed to "SYSTEM STATUS = Custom" and the boot screen when I turn on the phone would show a big "CUSTOM" instead of "SAMSUNG GALAXY S4". On my new Sprint MK5 GS4 after saferoot, my flag is still "SYSTEM STATUS = Custom" but my boot screen still shows "SAMSUNG GALAXY S4". since I don't see big annoying "CUSTOM" message on my sprint GS4 screen during boot, I'm not really worried about trying to reset the flag at this time.
In any case, I hope you find this helpful.
Please click thanks if you are finding these postings helpful to read.
bgmg said:
Greetings. I see you are a senior member, which means you understand more of this terminology then I do, so forgive me if I misunderstand your question.
If by custom recovery you mean change the "SYSTEM STATUS = Custom" flag back to "SYSTEM STATUS = Official" try one of these methods:
According to k1mu the saferoot developer, "the 'Custom' flag is set by a scanner that looks at the content of your phone, searching for anything that's modified or unexpected.
To clear the custom flag, un-do any changes you've made to the phone (like 'de-bloat'), remove busybox, unroot, then reboot. Wait an hour and reboot again. You should no longer have any changes from stock, so you'll no longer be custom. It's easier, if you're planing to return your phone, to just flash a full-wipe factory stock ROM. (Not a 'Stock' ROM, but factory stock from Samsung unmodified.)"
I've also been told:
If custom doesn't go away do a full wipe either via odin, or k1mu's preferred method using the carrier-utility or kies.
or use Triangle Away. Gets rid of custom when you reboot
or use wanam exposed to fake the system status and it will allow you to be samsung official, 0x0 with root
I've not tested any of these yet, but they seem safe enough.
When I had a AT&T GS4 and did the safe root, I was changed to "SYSTEM STATUS = Custom" and the boot screen when I turn on the phone would show a big "CUSTOM" instead of "SAMSUNG GALAXY S4". On my new Sprint MK5 GS4 after saferoot, my flag is still "SYSTEM STATUS = Custom" but my boot screen still shows "SAMSUNG GALAXY S4". since I don't see big annoying "CUSTOM" message on my sprint GS4 screen during boot, I'm not really worried about trying to reset the flag at this time.
In any case, I hope you find this helpful.
Please click thanks if you are finding these postings helpful to read.
Click to expand...
Click to collapse
No a custom recovery as in CWM TWRP or PHILZ I tried twrp now I don't have a recovery at all I've done a lot of roots and phone flashes but this is my first Knox and it being a different variant from the SPH-L720 with different software also
Sent from my SPH-L720T using xda app-developers app
Related
Hello everyone, i'm a new member. I apologize if my english is not good enough.
After been driven insane by one pre-installed app from my Operator (Claro Peru) i decided that it was time to root my device to get rid from that pest. I'm a noob, so i started to investigate about the safest methods to not damage my phone. My Device's model is SGH I337m.
The plan was to update the FW from JB 4.3 that came with my phone to 4.4.2 and then proceed to root. I downloaded the Canadian 4.4.2 FW with build version I337MVLUFNC1 and installed manually with Odin. After the phone rebooted, my S4 was upgraded with 4.4.2 but Samsumg keyboard was going insane, so i went to the apps and solved that cleaning the cache/data. Then i noticed that the Wifi wasn't connected, i tried to turn it on, but then a message with a shield appeared saying that my device security stopped the operation. Beliving it was only a problem with KNOX, i installed autoroot (CF-Auto-Root-jfltecan-jfltevl-sghi337m) with Odin, open SuperSU and stopped it from working, but the Wifi still wouldn't connect.
So the first thing that crossed my mind was to unroot and do a factory reset, didn't work. The FW still was 4.4.2, so i´ve been searching solutions with this FW because i've read some cases of devices that stopped working completely after trying to do a downgrade. so i don't want to go to that route for now.
After a couple hours of search, some solutions i found on the forum were:
- Install Faux123 Kernel (Found on Youtube, this would be the thread i think http://forum.xda-developers.com/showthread.php?t=2273437http://forum.xda-developers.com/showthread.php?t=2273437
- Flash a modem for i337m
- Safestrap recovery and bypasslkm.zip
- Downgrade
I haven't tried any of this methods because i dont want to get into a deeper trouble. In the first solution i'm not sure what to do because this is the files the author recommends for canadian models (i337m), but when i enter here http://faux.romhost.me/jflteatt/jb42/http://faux.romhost.me/jflteatt/jb42/ only jflteatt appears, and that would be i337 model, isn't it? I thought that installing it may cause more troubles, so i didn't do it.
For the flashing modem method, i'm not really sure if installing a modem from another country would get me in trouble, so again i didn't proceed.
I found the Safestrap and recovery method on a downgrade thread for the i337, so again, didn't do it.
So, is there a way to get one of this methods working on i337m to get wifi working again, or is there any other better method to get back wifi.
I would really appreciate any help you can give me guys.
Copellius said:
... My Device's model is SGH I337m.
The plan was to update the FW from JB 4.3 that came with my phone to 4.4.2 and then proceed to root. I downloaded the Canadian 4.4.2 FW with build version I337MVLUFNC1 and installed manually with Odin. After the phone rebooted, my S4 was upgraded with 4.4.2 but Samsumg keyboard was going insane, so i went to the apps and solved that cleaning the cache/data. Then i noticed that the Wifi wasn't connected, i tried to turn it on, but then a message with a shield appeared saying that my device security stopped the operation. Beliving it was only a problem with KNOX, i installed autoroot (CF-Auto-Root-jfltecan-jfltevl-sghi337m) with Odin, open SuperSU and stopped it from working, but the Wifi still wouldn't connect.
So the first thing that crossed my mind was to unroot and do a factory reset, didn't work. The FW still was 4.4.2, so i´ve been searching solutions with this FW because i've read some cases of devices that stopped working completely after trying to do a downgrade. so i don't want to go to that route for now.
After a couple hours of search, some solutions i found on the forum were:
- Install Faux123 Kernel (Found on Youtube, this would be the thread i think http://forum.xda-developers.com/showthread.php?t=2273437http://forum.xda-developers.com/showthread.php?t=2273437
- Flash a modem for i337m
- Safestrap recovery and bypasslkm.zip
- Downgrade
I haven't tried any of this methods because i dont want to get into a deeper trouble. In the first solution i'm not sure what to do because this is the files the author recommends for canadian models (i337m), but when i enter here http://faux.romhost.me/jflteatt/jb42/http://faux.romhost.me/jflteatt/jb42/ only jflteatt appears, and that would be i337 model, isn't it? I thought that installing it may cause more troubles, so i didn't do it.
For the flashing modem method, i'm not really sure if installing a modem from another country would get me in trouble, so again i didn't proceed.
I found the Safestrap and recovery method on a downgrade thread for the i337, so again, didn't do it.
So, is there a way to get one of this methods working on i337m to get wifi working again, or is there any other better method to get back wifi.
I would really appreciate any help you can give me guys.
Click to expand...
Click to collapse
ok so you have the i337m canadian version... making anything related to safestrap and the att i337 irrelevant, completely different methods so don't get them confused lol
you were updating from stock 4.3 right? your best bet is to factiry reset and reflash stock fw for 4.4.2 before you brick your device... kitkat is very different from 4.3, maybe read up on it a bit too...
for ex, the "message with a shield appeared saying that my device security stopped the operation" isn't related to needing to root, it's an option under security settings.
to enable superuser on kitkat you need to enable developer options, then enable superuser. I prefer supersu so manually install that from play store afterwards. I recommend checking and/or enabling this as soon as the phone completes booting up after flashing.
also I think there's a known issue w/ 4.4.2 and wifi not turning on until after 2nd boot completed if I rememebr correctly, been using 4.4.4 for awhile now though so could be wrong...
good luck and check out the help section :angel:
Please post here ALL of what you learned/thoughts/ideas. My goal is to get the Sprint based phone "G900P.04" Virgin Mobile users up and going.
I am not responsible for ANYTHING!!! Try doodling with your phone at your own risk!
THIS IS WHAT I GOT SO FAR:
APN SETTINGS:
Virgin Mobile Samsung Galaxy s5 as all the capabilities of flashing any Sprint based G900P.04 ROM/Tweak. However, once flashed, you will have Sprint based network APN settings/not virgin mobile network APN settings. APN settings is what allows you to call/text/LTE/send receive text/pictures. Currently the Virgin Mobile stock ROM doesn't have the option to manually set APN settings though settings/network connections/more networks. However, once flashed to a Sprint ROM, this option "should" now be available to edit. If ballzy enough to try flashing a Sprint ROM and obtain data capability PLEASE POST YOUR FINDINGS. Virgin Moible APN settings can be found at this address:
Virgin Mobile USA APN Settings
I called Virgin Mobile and told them that my send recieve text doesn't work and ask if i can access APN settings manually to check if there correct. He gave no option to view them manually. He advised to dial ##72786# which he said redoes the hands free activation process and "?may?" fix the APN issue.
Apps like the APN backup & restore is another option "if exhausting all other available options" a thread I found HERE It appears that if you know what your doing, the app will work but nevertheless, people has reported it not restoring APN settings.
ROOTING Virgin Mobile Galaxy s5 Obtain warranty without tripping knox counter:
The CF autoroot though odin I seen threads that it trips the knox counter but the "towelroot" method doesnt trip the knox counter and was easy for me.
How to:
1. Go to settings/system/security/allow 3rd party apps. As long as you know what you download I disabled "verify apps" while I'm their.
2. With your phone, Download towelroot HERE and click the red logo to start download
3. Download a file explore application from Google Play "my favorite is FX File Explorer/has secondary Playstore download for accessing root files" and install the tr-1 .apk you downloaded.
4. Read and click the option to root phone.
5. When it says remove knox I clicked "yes."
6. As mine did also, a lot of users report that the phone didn't complete/auto reset device but hung on the "removing knox process." Personally I waited 5min---pressed the home button---manually reset phone.
7. Go to Play store and download/install SuperSU---update binary's---reset phone
8.Your phone is rooted/complete.
Return to Factory Stock
Reflash the phone with the factory stock ROM with Odin can see instructions HERE
Note: Virgin Mobile users only has the option of the Sprint ROM so im curious if this will bork up APN settings...putting them on Sprint/not Virgin Mobile settings. The hand free activation by dialing ##72786# may/may not work.
Custom Recovery:
All Sprint based recoveries I'm positive will work. Custom Recovery opens up any theme/tweak/ROM capability. However, im reluctant to do so because you will not have the ability to update the OS when it arrives because it requires the stock recovery....where you have to do the Return to Factory Stock option just posted.
I've always used Philz Touch Recovery and was always happy with it. Insturctions HERE
There is a TWRP recovery but even people on the TWRP thread say that they hear good things about Philz Recovery.
Installing a ROM:
As mentioned, only Sprint Based ROMs work because it's a Sprint phone. However, if flashing a Sprint ROM through your custom recovery it should error. This is because the developer Puts a script in the ROM that only allows Sprint not Virgin mobile phones to flash the ROM. To fix this, it requires editing the ROM with NotePad++ and deleting the first few lines of code. Good thread to read how to do this is HERE
Apps/Tweaks:
Im still using stock ROM up until somebody with experience can guarantee I can start flashing ROMs without any mishapps.
..Adaway is working great.
Link HERE Couldn't beileve the amount of ad's is on the Internet...even on XDA. Just open/install with a file explorer like FX File Explorer...make sure under settings/security you check "Unknown sources" so you can install apps outside of play store
Wanam Xposed is amazing
Verified working on my Virgin Mobile Stock ROM. Install Wanam from Playstore and install frame work from HERE Now got my phone all theme'd blacked-out like how I like it. 4-way boot menu working too. NOTE: Wanam website states S-Health conflicts with it...so recommend uninstalling it.
Native Hotspot Enabled:
Install this App HERE GalaxyTools.apk. Click Enable Native Hotspot and reboot phone. "Mine rebooted automatically once enabled." Now I access my Hotspot using a playstore hotspot widget "my perfered is called Elixir 2 from the playstore. " on my home screen.
Debloat Stock ROM:
App Master is small and can go to system files and debloat all dumb apps Samsung/Virgin Mobile put on there. A thread HERE shows what Apps are safe to remove.
PLEASE POST ALL YOUR FINDINGS/THOUGHTS/IDEAS
Rather than restoring a Virgin Mobile phone to a Sprint stock firmware we can use these firmwares instead
G900PVPU1ANE5 STOCK VIRGIN MOBILE
G900PVPU1ANK4 STOCK VIRGIN MOBILE
G900PVPU1BOA6 STOCK VIRGIN MOBILE
G900PVPU2BOD3 STOCK VIRGIN MOBILE
G900PVPU3BOF6 STOCK VIRGIN MOBILE
G900PVPU3BOG1 STOCK VIRGIN MOBILE
Notice the Product Code is VMU, which is for VIRGIN MOBILE!
I'll try to keep this post updated with Virgin Mobile Firmwares in case more are added, for convenience and reference
Here is where I got them from
FIRMWARES | SAMMOBILE | VMU
VM's stock ROMs are on sammobile.
Working are CF auto-root, and Philz recovery (via ODIN).
The latest Sprint NK4 ROM (4.4.4) can be ODIN flashed on top of the VM stuff, and everything keeps working as VM. (Towelroot does not work on 4.4.4.)
I don't believe the VM APN settings posted above are accurate for this phone. But if you do the above (CF auto-root, Philz, Sprint ROM), you should be able to get to them on your own phone.
Presumably there will be a stock VM 4.4.4 ROM released soon regardless.
I don't know that there's a need to do much VM-specific stuff separate from what's done for Sprint.
I've been having two flashable zips that I use when switching to a new AOSP based rom (like CM, PAC, whatever), so rather than doing it manually, for you lazy folk like me, you can boot into Recovery, after having checked that you properly flashed your ROM, and flash these VMU APNs. This is for KK ROMs only! If you flash the file named AOSP_MMS_FIX.zip on lollipop you will get a Bootloop.
I got them a while ago so I forgot where or who made them, if you are reading this however, let me know so that I can give cred
By the way, does anybody know how to get MMS working on lollipop? With lollipop roms I can flash the file Universal_vmu_ApnFix-v.R2.zip to get texting and calls working but it doesnt fix picture messages.
EDIT: The Universal_vmuApnFix-v.R2.zip DOES work on AOSP lollipop roms. Just do not flash the other file.
The Sprint Lollipop 5.0 OA6 stock tar posted at the following does also appear to work for VM. Somehow it does know it's on a VM phone -- VM boot logo and everything:
http://forum.xda-developers.com/showpost.php?p=58662929&postcount=1
No problems with the latest CF Auto-root in that thread. Philz 6.57.8 appears to still work after renewed flashing, too.
boost mobile send the update same day Sprint relesed
Sent from my SM-G900P using XDA Free mobile app
d99x, no APN fix was needed when you flashed that Sprint OA6 onto the VM S5?
TheBritton said:
d99x, no APN fix was needed when you flashed that Sprint OA6 onto the VM S5?
Click to expand...
Click to collapse
Correct. And though APN settings are no longer accessible via "More networks," an S-Finder search for "Access Point Names" still turns up the settings. Confirmed to be VM. Everything's hunky dory automatically. :good:
For what it's worth, I backed everything up via Kies in advance. After all apps re-downloaded from the Play store, a Kies restore did get back most if not all of my settings. It just can't restore apps themselves to the new build.
Anyone know the best way to root with the lollipop update installed?
TheChiZ said:
Anyone know the best way to root with the lollipop update installed?
Click to expand...
Click to collapse
The CF Auto-Root linked in the first post of this thread works, but trips Knox:
http://forum.xda-developers.com/showthread.php?t=2729617
And for what it's worth, the official VM firmware is now up at SamMobile:
http://www.sammobile.com/firmwares/database/SM-G900P/VMU/
d99x said:
The CF Auto-Root linked in the first post of this thread works, but trips Knox:
http://forum.xda-developers.com/showthread.php?t=2729617
And for what it's worth, the official VM firmware is now up at SamMobile:
http://www.sammobile.com/firmwares/database/SM-G900P/VMU/
Click to expand...
Click to collapse
Yeah im on the stock update
TheChiZ said:
Yeah im on the stock update
Click to expand...
Click to collapse
Whats Knox like on this phone coming from the s3, if i trip knox once while rooting, how does that affect me when I want to flash a custom rom?
i just got my virgin mobile galaxy s5. i have yet to root and want to understand this fully before i do what i would like to do as ive had experience with bricked devices and dont want a repeat of the feeling. i want a to make a list of what i think i should do and i would love it if i could get corrections on anything thats wron with my process. i and on the sm-g900p model for VM. baseband: g900pvpuboa6 and android version 5.0 lollipop.
1. (while in download mode) connect s5 to computer
2. open odin 3.9 or 3.7
3. select pda/ap and place CF Auto Root into the slot and let it run until the bar turn bluor green or whatever color means that its good to go.
4. apply a custom recovery (i personaly like PhilZ touch recovery)(i am not sure exactly how to do this. on my s3 i was able to apply the recovery via the stock recovery but i dont know if that is possible with knox and all)
5. go into custom recovery on phone and apply the latest version of supersu
6. in custom recovery apply and deknoxify and debloat zips
7. boot up phone and update supersu and run a root checker
8. do whatever with your new rooted s5
i would love it if someone could tell me if this is a tested method or if i am missing something or doing something wrong. any help would be much appreciated as i really dont want anything to go wrong. i also would love it if someone had a link to philz touch recovery that is properly compatible with my version of s5 (sm-g900p VM)
It's not critical, but the latest ODIN is 3.10.6:
http://forum.xda-developers.com/showthread.php?t=2711451
PhilZ is at the following. You can flash the latest 6.57.8 tar.md5 the same way in ODIN. Remember he's no longer developing or supporting this, but it works for now.
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/klte/
You do not need to flash SuperSU via a custom recovery if you don't want to. You can add/update it just fine via the Play store.
You do not need to apply the de-knoxify and debloat zips if you don't want to. If you want, there are other file manager programs out there that you can also use to "freeze" Knox (if it makes you feel better for some reason), and to debloat manually yourself.
If you mess up badly, you can use ODIN to flash the full restore TAR from the following (extract it first). Though it's in a "Sprint" folder there, it recognizes it's on the VM variant of the Sprint phone just fine.
http://rwilco12.com/downloads.php?d...print) (SM-G900P)/Stock ROMs/OA6/Full Restore
thank you. the philz recovery i was using was too outdated and caused me some problems. and cf auto didnt seem to want to work. however the recovery you gave the link to worked flawlessly and allowed me to flash the supersu update and gain root.
my next question is weather or not it is safe to flash a sprint stock android L rom and keep my calling, text and mms, and 4g data seeing as i am on VM and not sprint (i do know they are the same phone internally but coming from a VM s3 i needed to flash a APN fix everytime i flashed a new rom to keep things working)
revins95 said:
thank you. the philz recovery i was using was too outdated and caused me some problems. and cf auto didnt seem to want to work. however the recovery you gave the link to worked flawlessly and allowed me to flash the supersu update and gain root.
my next question is weather or not it is safe to flash a sprint stock android L rom and keep my calling, text and mms, and 4g data seeing as i am on VM and not sprint (i do know they are the same phone internally but coming from a VM s3 i needed to flash a APN fix everytime i flashed a new rom to keep things working)
Click to expand...
Click to collapse
I read somwhere that this may be the case this time around aswell, dont know 100% though
The Sprint stock ROM recognizes it's on a VM phone just fine. What's been issued is identical. On a VM phone, it sets up everything for VM -- boot animation, APN settings, everything. There is no need to flash an APN fix or alter any settings to adapt it to VM. That's why when people have tried to start Virgin Mobile threads here, there's been little to no response. There's virtually no need to do anything unique to VM when it comes to the S5. What works for the contract Sprint, works for the pay-as-you-go Sprint, aka VM.
I have not tested non-Stock ROMS, and don't know what you may run into if you start experimenting with custom Sprint ROMs on the VM phone.
If you want to alter your APN settings (though there should be no need on the stock ROM), you can search "Access Point Names" in S-Finder in the drop down menu once the ROM is installed.
d99x said:
The Sprint stock ROM recognizes it's on a VM phone just fine. What's been issued is identical. On a VM phone, it sets up everything for VM -- boot animation, APN settings, everything. There is no need to flash an APN fix or alter any settings to adapt it to VM. That's why when people have tried to start Virgin Mobile threads here, there's been little to no response. There's virtually no need to do anything unique to VM when it comes to the S5. What works for the contract Sprint, works for the pay-as-you-go Sprint, aka VM.
I have not tested non-Stock ROMS, and don't know what you may run into if you start experimenting with custom Sprint ROMs on the VM phone.
If you want to alter your APN settings (though there should be no need on the stock ROM), you can search "Access Point Names" in S-Finder in the drop down menu once the ROM is installed.
Click to expand...
Click to collapse
I would think that if you were to flash Cm 12 you would have to follow it up with some sort of apn fix
TheChiZ said:
I would think that if you were to flash Cm 12 you would have to follow it up with some sort of apn fix
Click to expand...
Click to collapse
thats more so what i meant. ive realized through a little research that using a sprint rom on my vm in fine. i believe this is so because unlike most other VM phones (such as my previous Galaxy S3 VM) the Galaxy S5 uses a VM sim card. something that i found unusual but suspect is the reason for never haveing to change anything ( please coeect me if you know im wrong on this information because right now im working with this as a hypothesis). however i dont know what will happen when i install CM12, which is something i want to try out. my VM S5 doesnt have a Data Toggle in the notification tray which annoys me to no extent. i cant seem to find a way to fix this nor can i find in the stock lollipop rom that the phone comes with. ive always loved stock lollipop and ran CM12 on my S3 but the community for it on Android Forums was huge as still is, so finding how to change the APNs on the VM locked S3 was easy. this isnt the case with the S5 neither there nor here at XDA. i either want to fix my data toggle on my stock rom so i can keep my fingerprint scanner (which for me works more times than not) or switch to CM12. i dont know which is the better option as far as keeping everything working.
revins95 said:
thats more so what i meant. ive realized through a little research that using a sprint rom on my vm in fine. i believe this is so because unlike most other VM phones (such as my previous Galaxy S3 VM) the Galaxy S5 uses a VM sim card. something that i found unusual but suspect is the reason for never haveing to change anything ( please coeect me if you know im wrong on this information because right now im working with this as a hypothesis). however i dont know what will happen when i install CM12, which is something i want to try out. my VM S5 doesnt have a Data Toggle in the notification tray which annoys me to no extent. i cant seem to find a way to fix this nor can i find in the stock lollipop rom that the phone comes with. ive always loved stock lollipop and ran CM12 on my S3 but the community for it on Android Forums was huge as still is, so finding how to change the APNs on the VM locked S3 was easy. this isnt the case with the S5 neither there nor here at XDA. i either want to fix my data toggle on my stock rom so i can keep my fingerprint scanner (which for me works more times than not) or switch to CM12. i dont know which is the better option as far as keeping everything working.
Click to expand...
Click to collapse
Have you tried MOAR v6.0
Hello to everyone.
I have a note 3 , N 9005. I rooted it at some point then i reset it to factory settings because the banking app and other apps did not work anymore. Yesterday I did flash the new android 5, which I downloaded from xda forum.
Everything went smooth, I was hoping the device status - custom message will go away with the new official firmware installation.
It still shows the same.
I tried the unmount sd card, wipe cache and restart with no success. I have also erased all data on the sd card (32 GB samsung).
How can I have my device status set to ''official'' so I can receive updates automatically?
When will there be a root method for android 5 ?
Thanks so much for your time.
Hamza
Hi
Thanks for writing to us at XDA Assist. Please standby while we have your thread/question moved to the appropriate sub-forum for your device.
For future reference you can find your specific device forum here (bookmark/subscribe this):
Samsung Galaxy Note 3
Within that section you will find a dedicated q&a sub-forum (this is where your thread is going to be moved to):
Galaxy Note 3 Q&A, Help & Troubleshooting
Good luck!
timmaaa said:
Hi
Click to expand...
Click to collapse
TIMMAAA...
You can set your system to official by using wanam xposed in the xposed installer. using wanam set systemb to official. Then request the update. Wait until it downloads then use odin to reinstall custom firmware. Then let the ota install. It will put you back to your original kk then it will download lollipop again. You cash also go back to fill in root by using odin to install factory firm ware. Keep an eye on it because after the firmware installs it will reset. As soon as it goes from boot to loading the rom pull the battery before any of your information gets in to the new firmware. P ut the battery back in hit vol up + menu + power in the stock recovery click factory reset let it load. Check out your factory set system then come back here and click thank you.
Hey dude,
I upgraded my Note3 to 5.0 and kept root. If you're still on KK you can install Xposed framework and install the Wanam module. You have a option in that module to "fake" the STATUS message to OFFICIAL. I can assure you that it works, but you can upgrade with MobileOdinPro and still have a rooted 5.0 Note3. The steps are easy, but with a search on google I'm sure you will be okay. If you still don't manage to find anything, you can PM me and I'm sure I can help.
Hi again to everyone. My device is not rooted now. I unrooted when I was still on kit kat because the mobile banking app did not work and other apps too.
I tried to root it using CF autoroot for android 5. It said fail .
That is the message I got from Odin. The phone is not bricked, it still works normally.
I have done alot of search on google, I have not found anything which seems ok, just a post on a blog, and people commented below that they bricked their devices with that method so I did not do it.
Thanks to everyone for their advices and for taking the time to reply to my post.
Any more ideas please? Thanks.
phonexpert_alex said:
Hey dude,
I upgraded my Note3 to 5.0 and kept root. If you're still on KK you can install Xposed framework and install the Wanam module. You have a option in that module to "fake" the STATUS message to OFFICIAL. I can assure you that it works, but you can upgrade with MobileOdinPro and still have a rooted 5.0 Note3. The steps are easy, but with a search on google I'm sure you will be okay. If you still don't manage to find anything, you can PM me and I'm sure I can help.
Click to expand...
Click to collapse
Hi . Yes I know. I should have rooted when I was on kit kat, then upgraded through mobile odin pro, and I would have kept root.
Thanks for your reply.
Hello.
Updates are:
I have downgraded to the latest kit kat. Rooted it. I flashed lollipop using mobile odin pro. It went ok but I had no root . I do not know why.
I rooted using chain fire auto root. I am rooted now finally. I managed to get rid of all the crapware. My wi fi acts up. I need to log in everytime i restart the phone.
the wifi turns on but it does not remember to log in automatically. Any fix for that?
Also I can't se the device status to "official" by using wanam exposed. Any ideas anyone?
Thanks.
I just swapped from my Amaze 4g, to a used Note 3, and I'm a little lost as far as where I should start.
It says that it's on 4.4.2, and that I cannot update due to a modified system.
Basically, I would like to get updated to 5.1.1 (or as close as is official for the Note 3), and root it.
I'm afraid I'm not familiar with Samsung devices, and because I purchased this from ebay, I don't know how to tell the exact state that the former user put it in (I expected they would return it to stock prior to selling).
It's currently a T-Mobile branded, SM-N900T, on 4.4.2, build is KOT49H, security software MDF v1.0 release 2. Kernel is 3.4.0-660648.
It is supposedly unlocked for carriers, though I have not attempted a SIM card use yet, until I can tell that what I have is a valid device and the IMEI is checked out.
Any thoughts on how to validate the IMEI, and sort out how to get my new phone up to date would be appreciated. As I stated, I expected the vendor would have returned it to stock, but that is clearly not the case, so I don't want to accidentally boot loop it by doing something I shouldn't. I have not owned a Samsung before, so I want to be careful on how it differs from my Nexus 7, Amaze 4g, and Droid X, as they're all obviously very different in the OS area.
Thank you for the help1
Download tbe stock 4.4.2 rom and use odin to install. Then you will get the OTA updates.
Sent from my SM-N900P using Tapatalk
There is no stock 5.1.1 for note 3, only cm12.1/ aosp. Latest is 5.0 and you can use odin to flash. Maybe it's rooted that's why you can't update.
bladebarrier said:
I just swapped from my Amaze 4g, to a used Note 3, and I'm a little lost as far as where I should start.
It says that it's on 4.4.2, and that I cannot update due to a modified system.
Basically, I would like to get updated to 5.1.1 (or as close as is official for the Note 3), and root it.
...
Thank you for the help1
Click to expand...
Click to collapse
Some apps to install from Play Store...
Phone INFO Samsung - this will tell you all about your phone and the firmware etc.
Root Checker Basic - tells you if you are rooted or not.
SuperSU - this is so valuable you should buy the Pro licence. Chainfire does some great work for our phones.
TWRP - I have the zip version on my extSDCard and an Odin version on PC in case I have to rebuild from a Stock firmware. CWN works OK but most ROM builds seem to be for TWRP I think and a backup from one will not work on the other.
I don't know your previous phone so you probably need Odin v3.09 - this sits on PC and lets you flash firmware to the phone. (connected by USB)
For which you need Samsung USB drivers so the PC will recognise the phone. Install on PC before connecting phone.
Then do some browsing and find the processes to root your phone and install the ROM you want. If you just want Stock and access to all your phone, you can root it after flashing the original v5.0 download (from Sammobile or similar site - note on Sammobile you need a free account to DL) and then install Custom recovery (if wanted - it WILL trip the Knox flag but that may not matter given it's 2nd hand and might already be tripped anyway)
Read, make SURE you understand what is being said BEFORE you do anything - ask if you don't.
Good luck...
N9005 Lollipop brick
Hi All, just need a huge help here, a friend of mine has been using a N9005 which was auto restarting, she went online and downloaded this firmware...N900AUCUEOC1_N900AATTEOC1_N900AUCUEOC1_HOME.tar.md5....2.5GB in size...and flashed it, but the phone is stuck in boot loop even after recovery wiping data and cache, the phone can boot into download mode but re flashing the firmware always fails.....is there a solution for this.....please help
Thank you all for the info, especially the detailed info from Journyman16. I checked, and it is flagged as custom, which is fine, so I'm going to go ahead and try to return to mostly stock, update it, and root it.
Ok, everything went well. I had to do two attempts at rooting, but I think it's just one of those things where sometimes it doesn't restart into the process every time.
All seems good. I'm on 5.0, rooted, busyboxed, and smooth sailing.
Thank you all, again, for the tips. The Note 3 is running very well. Thank you to all of the devs that have made this process so refined. I've donated to you before, and did so again today. It's outstanding to have such well versed coders, on XDA, helping out the community.
mjmbirige said:
Hi All, just need a huge help here, a friend of mine has been using a N9005 which was auto restarting, she went online and downloaded this firmware...N900AUCUEOC1_N900AATTEOC1_N900AUCUEOC1_HOME.tar.md5....2.5GB in size...and flashed it, but the phone is stuck in boot loop even after recovery wiping data and cache, the phone can boot into download mode but re flashing the firmware always fails.....is there a solution for this.....please help
Click to expand...
Click to collapse
You have never learned not to ask in others posts? What does your problem has to do with this topic at all?
When you need help. Just click on Q&A then Create a new thread. How hard is it?
Tab 4 (SM-T530NU) 4.4.2 = used ODIN & Flashed Kernel 2 Root w/ Towelroot; Flash back?
I have a Samsung Galaxy Tab 4 10.1 (SM-T530NU) Even though I'm running on 4.4.2., I wasn't able to ROOT using Towelroot.APK B/C the Kernel is A0A2. So, following the directions on a website (posted at the bottom of this post) I found my device's Model_ROOT.Kernel.Tar.md5 and it's Model_Kernel.Tar.md5 files the webpage stated I needed in order to ROOT my device via ODIN.
Using ODIN, I was successful in flashing the downloaded ROOT.Kernel.tar.md5 file. After completing the next step I was able to successfully gain ROOT privileges by opening TowelRoot.apk & clicking "Make it Rain"
I used a random Root Checker app I downloaded from the Google Play Store to verify whether or not Towelroot succeeded in ROOTING my device.
YEAH!! I HAVE SUPER USER PERMISSIONS!!
I was so excited to have ROOT access after several days of continuous research that I never proceeded to the final steps on the aforementioned website's tutorial. I didn't use Model.Kernel.tar.md5 to flash my device back. Know it's been 2-3 days since I ROOTED my Tab 4 & to the best of my knowledge, I haven't experienced too many relative issues other than both Lucky Patcher & Freedom apps have been unsuccessful when I attempt to get free In-App Purchases from other Apps & Games. Normally I would just uninstall both apps and shrug 'em off as being incompatible with my device but within the past 8-10 months, I've used both of these apps on 2 of my previously ROOTED devices & they both worked correctly from the start. Not to mention that one of those happened to be another Tab 4 which was the same Make & Model of the Tab 4 10.1 SM-T530NU I'm currently using & writing about - the only differences between the two is their SEstatus & their Kernels: Old Tab4 had Permissive SEstatus & the Kernel ended in AND1 while this new one is set to Enforcing SEstatus and it's Kernel ends in A0A2)
I have a few questions related to the information you just read in this Thread:
* Did I really f**k up when I 4got to Flash back after Rooting w/ Towelroot? (If so, what steps do I take)
* How do I get L.P. & Freedom.apk to work correctly? (Does having 'Enforcing' SE Linux Status an issue? Either way, I would like to know how I can switch my SEstatus to 'Permissive')
* How can I Factory Reset my Tab4 running on Kitkat 4.4.2 without losing ROOT access?)
SITE I USED AS A STEP-BY-STEP TUTORIAL TO HELP ME ROOT MY CURRENT TAB 4:
w0lfdroid DOT com (without spaces) /2014/09/TowelRoot-Samsung-Galaxy-S4-S5-and-Note3-Android-4.4.2-NF-or-Later DOT html
If anyone requires any additional information to be able to answer all/any of my Questions, please feel free to contact me.
Thanks a Million,
- B. O'Kane
a lot of letterssssssss
APKtech said:
* Did I really f**k up when I 4got to Flash back after Rooting w/ Towelroot? (If so, what steps do I take)
* How do I get L.P. & Freedom.apk to work correctly? (Does having 'Enforcing' SE Linux Status an issue? Either way, I would like to know how I can switch my SEstatus to 'Permissive')
* How can I Factory Reset my Tab4 running on Kitkat 4.4.2 without losing ROOT access?)
Click to expand...
Click to collapse
1) Yes. Flash the OA2 kernel the same way you did the root kernel
2) See my answer to your first question. SE Linux has nothing to do with this. If you want SE Status permissive, install a custom kernel or a custom rom
3) You can't
Sincerely,
Another SM-T530NU owner