Database Users

[Q]help updating sph-L720

Hello,
after a few days researching and trying to root/flash my samsung sph l720 i didnt found anything but first:
a cousin brought me his gs4 l720 from us, it was unlocked and i can "use" it but i cant enable the hotspot etc...
i was almost going to root it but i started reading about knox, bootloaders etc thats why i wanna ask if its possible to update it from 4.3 to 4.4 and enable the hotspot etc.
software version:
L720VPUAMDC
Hardware version
L720.08
Android Version:
4.3
baseband version:
L720VPUAMDC
kernel version:
3.4.0-1927016
[email protected] #1
Sat Nov 16 11:05:09 KST 2013
Compilation number:
JSS15J.L720VPUEMK2
thats all the info in about device... i wanna know if its possible to root it and install a custom recovery like CWM
also if its possible to update it to KitKat
what happend if the Knox flag triggers ? do my s4 bricks or something ? or it just voids the warranty, because i dont care about the warranty as im in another country.

Just to answer your knox question. All it does is void warranty. You can still unlock root and flash Roms with Knox tripped.
Sent from my SPH-L720 using Tapatalk

daniel4653 said:
Just to answer your knox question. All it does is void warranty. You can still unlock root and flash Roms with Knox tripped.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
Thanks, now the only thing i wanna know before i root it is how do i check if the bootloader is locked ?
i read in the cf auto root web that if the phone has a locked bootloader it can brick the phone.

grdenrique said:
Thanks, now the only thing i wanna know before i root it is how do i check if the bootloader is locked ?
i read in the cf auto root web that if the phone has a locked bootloader it can brick the phone.
Click to expand...
Click to collapse
Do some more reading ALL over the forums here. So far our device doesn't have completely locked bootloader. just the knox flag.
It's actually very hard to truly brick this device. You may softbrick but that's easily recoverable.
There are posts on how to update to MF9, MK2 or NAE.
You can root any of those with the latest CF-Autoroot and add a custom recovery and flash a way compatible ROMs as per the OPs directions.
BUT PLEASE take some time to read, search and read some more. If you do you will surely get the most of your time and more importantly your device.
Good luck.

Looks to me like your phone is already rooted. Or at the least has been seriously messed with. You have 3 mismatches in the info you posted. MDC baseband with 4.3, then complilation of MK2. These are all different versions. You need to figure out the exact configuration of your phone before we can proceed with helping you.

cruise350 said:
Looks to me like your phone is already rooted. Or at the least has been seriously messed with. You have 3 mismatches in the info you posted. MDC baseband with 4.3, then complilation of MK2. These are all different versions. You need to figure out the exact configuration of your phone before we can proceed with helping you.
Click to expand...
Click to collapse
i copy it exactly from the cellphone, its there any way that info could be wrong ?

Since it appears your phone may have been upgraded to MK2 at one point, you could try just downloading the full NAE (KIT KAT) tar file from here: http://forum.xda-developers.com/showthread.php?t=2663619 and upgrading to NAE in one quick swoop. Then if you want to root it, you can use cf autoroot and go from there. If your phone has already been unlocked it should maintain the unlock even with the flashing of the stock tar.

cruise350 said:
Since it appears your phone may have been upgraded to MK2 at one point, you could try just downloading the full NAE (KIT KAT) tar file from here: http://forum.xda-developers.com/showthread.php?t=2663619 and upgrading to NAE in one quick swoop. Then if you want to root it, you can use cf autoroot and go from there. If your phone has already been unlocked it should maintain the unlock even with the flashing of the stock tar.
Click to expand...
Click to collapse
Thank you very much for your response. Well, I'll tell you what happened: To sim-unlock that phone it was downgraded to MDC while using MK2 stock rom. My wife's L720 is in the same case and also a co-worker is in the same situation. So now my question is, is there any problem upgrading it to kitkat (NAE) knowing that my wife doesn't uses the rooted rom?

walalm said:
Thank you very much for your response. Well, I'll tell you what happened: To sim-unlock that phone it was downgraded to MDC while using MK2 stock rom. My wife's L720 is in the same case and also a co-worker is in the same situation. So now my question is, is there any problem upgrading it to kitkat (NAE) knowing that my wife doesn't uses the rooted rom?
Click to expand...
Click to collapse
No problem at all, just use the link I referenced earlier and flash using Odin. This will upgrade your phone to kit kat and you won't loose and data.

cruise350 said:
No problem at all, just use the link I referenced earlier and flash using Odin. This will upgrade your phone to kit kat and you won't loose and data.
Click to expand...
Click to collapse
Confirmed, flashed my co-worker's phone and everything is working fine (I was unlocked using that downgrade) and remain unlocked.
Thank you very much, the next step is flash my wife's one.

[Q] at&t I337UCUFNC1 Root?

Is there any way to gain root for most recent att s4 update? Build number is KOT49H.I337UCUFNC1

I've been asking the same question every since the update as well. I was hoping to install a Custom ROM on my phone, but I am playing it safe until it's been confirmed workable with the latest update. As a back up, I've seen people mention it's possible to rollback this update to NB1. I've had no luck so far pulling up a thread about rolling back updates, though...

kot49h.i337ucufnc1
bluestar23 said:
Is there any way to gain root for most recent att s4 update? Build number is KOT49H.I337UCUFNC1
Click to expand...
Click to collapse
I tried the downgrade method for the NB1 and it failed with Odin3 V3.09 and got stuck with Odin3 V1.85

Root
Also looking for a way to root the i337ucufnc1

I337UCUFNC1 System Status
I was rooted yet my ATT phone still forced 2 ATT push updates. I lost root yet my phone is still showing as custom system status and unlocked custom icon on reboot.

Ditto
Jbjamin said:
I was rooted yet my ATT phone still forced 2 ATT push updates. I lost root yet my phone is still showing as custom system status and unlocked custom icon on reboot.
Click to expand...
Click to collapse
Are you able to access your external SD? I too have the same Build and have lost access to my SD, can't root, or unlock, even using the Network Unlock code from AT&T. I've lost apps, it has slowed waaaaaaaaaaaay down, and the battery is not lasting, even with Powersave. I just got this phone and the guy I bought it from factory reset it. There was an update that accepted, but it stopped and said I had to restart the update for some reason. I did, but it is still 4.4.2, but now has a different Security Software Version, MDF v1.0 Release 2. It won't accept USSD codes and gives me a 'connection error invalid mmi code' message.
Are you having the same issues? I sure wish I could find something on this. Every time I try to search, it changes the I337UCUFBNCI to "Did you mean: i337ucufnb1?" I can't find anything totally, just bits and pieces. UGHHHHHH

Success, I couldn't find a step by step tutorial to fix my issue but thanks to a full nb1 .tar and a couple other files all given by contributors I was able to odin download to reset the custom icon to official then I had to odin download the full nb1 .tar. after doing this I did the ota att nc1 update and my phone is good as factory. Until I decide to root again that is.
If you would like some help let me know

i337ucufnc1 root
Jbjamin said:
Success, I couldn't find a step by step tutorial to fix my issue but thanks to a full nb1 .tar and a couple other files all given by contributors I was able to odin download to reset the custom icon to official then I had to odin download the full nb1 .tar. after doing this I did the ota att nc1 update and my phone is good as factory. Until I decide to root again that is.
If you would like some help let me know
Click to expand...
Click to collapse
I would like some help! How were you able to root fnc1? ! And is safe strap the only custom recovery that will work I'm guessing?
thanks in advance.
adam

I did not root nc1, but it is possible thanks to some very smart contributors. I was previously rooted and wanted to unroot to factory. I became unrooted but my system was still unofficial and custom which I was having a problem getting rid of so I can trade in my phone in the future for credit. Just search nc1 root on xda and you should find the info. Its a bit of a process but you should be able to figure it out. You need to odin download back to nb1 first and go from there. If you would like some additional help I can try to give some advise but I'm no expert or developer just an enthusiast
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app

bluestar23 said:
Is there any way to gain root for most recent att s4 update? Build number is KOT49H.I337UCUFNC1
Click to expand...
Click to collapse
It will help you maybe: HERE

Reboot your phone into download mode and use the NB1 full odin tar. http://forum.xda-developers.com/show...66&postcount=2
Use the MK2 downgrade method to obtain root. http://forum.xda-developers.com/show....php?t=2663545
Then use the NC1 keep root http://forum.xda-developers.com/show....php?t=2730144
This should help.

Jbjamin said:
Reboot your phone into download mode and use the NB1 full odin tar. http://forum.xda-developers.com/show...66&postcount=2
Use the MK2 downgrade method to obtain root. http://forum.xda-developers.com/show....php?t=2663545
Then use the NC1 keep root http://forum.xda-developers.com/show....php?t=2730144
This should help.
Click to expand...
Click to collapse
Can you repost those links please because none of them are valid...
Somehow when the post was made the links were messed up so the middle part is missing and just has ... instead. Thanks!
Trying to fix my mothers phone which she accidentally updated!

DornoDiosMio said:
Can you repost those links please because none of them are valid...
Somehow when the post was made the links were messed up so the middle part is missing and just has ... instead. Thanks!
Trying to fix my mothers phone which she accidentally updated!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=50667366
http://forum.xda-developers.com/showthread.php?t=2663545
http://forum.xda-developers.com/showthread.php?t=2730144
There you go

Rooting I337UCUFNC1
Hi. I have followed the threads for a while on rooting my I337. I purchased it used a month ago and really want to root it and install a custom rom. But by reading all the threads I am confused and somewhat worried I will brick it!
Can someone explain to me real clearly what software and files I should use to obtain root on AT&T I337UCUFNC1 and install a custom rom? I am ok with downgrading.
Thanks much.

Rooting the ATT SGH-I337 build I337UCUFNC1
I have this phone: build I337UCUFNC1, and was finally able to root it via the Towelroot method: Towelroot dot com.

fhuddles said:
I have this phone: build I337UCUFNC1, and was finally able to root it via the Towelroot method: Towelroot dot com.
Click to expand...
Click to collapse
i was able to root my I337UCUFNC1 using towelroot as well. however stuck trying to unlock my bootloader to install this custom rom: http://forum.xda-developers.com/showthread.php?t=2537495
any help is appreciated

Towelroot rooting fails

Hello everyone,
After getting my S5 yesterday one of the first things I did was try to root it via towelroot. Unfortunately it said phone not currently supported which is weird seeing as I found out it worked for others.
Anyway is it because I'm running too updated firmware or anything else of which I am not yet aware. If so I'd love to find out which version I need to flash and where I can find it. I also tried the automated towelroot with EasyRootToolkit(v12) and others but it got stuck on creating VM.
If anyone could help out I'll greatly appreciate it.

lyubor said:
Hello everyone,
After getting my S5 yesterday one of the first things I did was try to root it via towelroot. Unfortunately it said phone not currently supported which is weird seeing as I found out it worked for others.
Anyway is it because I'm running too updated firmware or anything else of which I am not yet aware. If so I'd love to find out which version I need to flash and where I can find it. I also tried the automated towelroot with EasyRootToolkit(v12) and others but it got stuck on creating VM.
If anyone could help out I'll greatly appreciate it.
Click to expand...
Click to collapse
If your firmware is ANGx Towelroot doesn`t work. Downgrade to an older version like ANE2 or follow this method http://forum.xda-developers.com/galaxy-s5/general/how-to-root-triggering-knox-2nd-method-t2843044.

..

Sorry about that, I was trying to find out more general information before going into specifics.
Anyway, my model's information's below
Model: SM-G900F
Version: 4.4.2
Build: KOT49H.G900FXXU1ANG9
Kernel: 3.4.0 ~ Fri. Jul 25 2014

..

I have the same problem.
I purchased mine a few days ago, and the kernel is from August. The model is 901F. It doesn't look like there's any older version to download.
How can I root it?

HippyBob said:
I have the same problem.
I purchased mine a few days ago, and the kernel is from August. The model is 901F. It doesn't look like there's any older version to download.
How can I root it?
Click to expand...
Click to collapse
Maybe Towelroot will be updated to a newer version for the NGx kernels in the future, for now there is only CF Auto Root for root which will trip the KNOX void warranty flag. Check if the 901F is supported by CF Root first.

gee2012 said:
Maybe Toewlroot will be updated to a newer version for the NGx kernels in the future, for now there is only CF Auto Root for root which will trip the KNOX void warranty flag.
Click to expand...
Click to collapse
Ah I see. As long as I can use the phone with the rom of my choice, along with having root access, I don't need the Knox void warranty flag to be intact. I had a look around yesterday, and CF Auto root didn't support 901F iirc. Would it still be safe to try without bricking it?
Edit: Ah I see you edited your post. Will just have to wait I guess.

HippyBob said:
Ah I see. As long as I can use the phone with the rom of my choice, along with having root access, I don't need the Knox void warranty flag to be intact. I had a look around yesterday, and CF Auto root didn't support 901F iirc. Would it still be safe to try without bricking it?
Click to expand...
Click to collapse
I would wait on Chainfire for a file suited for your device, you can (soft) brick a phone with the wrong file. You could also Google around for a compatible custom recovery for your device and then flash the latest superSU.zip file for your device to get root.

..

fffft said:
You didn't look very hard. There are firmware builds going back to May.
Use Odin to write an older firmware version, then Towel root will prevail.
.
Click to expand...
Click to collapse
Well I searched for firmwares for 901F. I found ones for other models such as 900F. Would I be able to use a 900F firmware on a 901F model?

..

fffft said:
You attached your post to a thread discussing the 900F and Towel root. Instead of hijacking someone else's thread, you should start your own. Particularly because you have a different, derivative model further confusing the subject under discussion.
The 900F has firmwares dating back to May. Your 901F doesn't. An extended search is your best option. As a very recent model and running 4.4.4 as well as a new kernel build you will have to see what exploits are found for your device. You might want to post some information in the CF-Autoroot thread to see if your device can be accommodated. Or you can wait it out and see what Chainfire, Geohot, et al can do with your model.
.
.
Click to expand...
Click to collapse
Ah sorry, just didn't want to add more threads when the subject would be pretty much the same. Will create one next time. I will play the waiting game and just endure TouchWiz.

HippyBob said:
Ah sorry, just didn't want to add more threads when the subject would be pretty much the same. Will create one next time. I will play the waiting game and just endure TouchWiz.
Click to expand...
Click to collapse
Or install Nova, Apex or any other launcher and a different icon pack from Play and turn off apps/widgets you don`t use

Hi,
I had very same problem with GS3. I solved problem with a Windows based Kingo ROOT software. No need ti downgrade etc. Everything went so smoothly and easy.

[Q] Rooted S5 - How to prepare to sell it? (unroot to stock?)

I don't know much about rooting, but I was able to root my Verizon S5 and customize it extensively.
I'm not actually selling it. My mom is eligible for upgrade, so I'm going to use her upgrade to get a S6 and give her my S5. I think I'd like to get the S5 back to stock so my mom doesn't have to worry about not updating, etc.
I tried searching, but surprisingly couldn't find a sold thread about returning the S5 to stock ROM. Seems like it should be a sticky. Maybe it is and I missed it?
Anyway, I have a "Stock" package under Restore in Safestrap. Not sure if that could be used. Can someone point me toward the un-rooting process? I don't know what I need to do, and whether I need to worry about knox, etc.

ergalthema said:
I don't know much about rooting, but I was able to root my Verizon S5 and customize it extensively.
I'm not actually selling it. My mom is eligible for upgrade, so I'm going to use her upgrade to get a S6 and give her my S5. I think I'd like to get the S5 back to stock so my mom doesn't have to worry about not updating, etc.
I tried searching, but surprisingly couldn't find a sold thread about returning the S5 to stock ROM. Seems like it should be a sticky. Maybe it is and I missed it?
Anyway, I have a "Stock" package under Restore in Safestrap. Not sure if that could be used. Can someone point me toward the un-rooting process? I don't know what I need to do, and whether I need to worry about knox, etc.
Click to expand...
Click to collapse
Flash a retail stock tar file of your choice depending what firmware you want. Start taking the updates to make sure that is working.
http://forum.xda-developers.com/ver...ment/stock-collection-kernels-modems-t2842069

Tulsadiver said:
Flash a retail stock tar file of your choice depending what firmware you want. Start taking the updates to make sure that is working.
http://forum.xda-developers.com/ver...ment/stock-collection-kernels-modems-t2842069
Click to expand...
Click to collapse
I'm sorry, but I don't understand what to do. There are many options on that thread. Is there a step-by-step instructions anywhere?

ergalthema said:
I'm sorry, but I don't understand what to do. There are many options on that thread. Is there a step-by-step instructions anywhere?
Click to expand...
Click to collapse
Have you ever used Odin?

Tulsadiver said:
Have you ever used Odin?
Click to expand...
Click to collapse
No. I'm on a Mac, and it couldn't find a version for Mac.

ergalthema said:
No. I'm on a Mac, and it couldn't find a version for Mac.
Click to expand...
Click to collapse
What firmware are you on? Check your build under settings, about phone.

Tulsadiver said:
What firmware are you on? Check your build under settings, about phone.
Click to expand...
Click to collapse
Device name: SAMSUNG-SM-G900V
Model number: SM-G900V
Android version: 4.4.2
Baseband version: G900VVRU1ANCG
Kernel version: 3.4.0, [email protected]#1
Hardware version: G900V.05
Security software version: MDF v1.0Release2, VPN v1.4 Release 1
Towelroot

ergalthema said:
Device name: SAMSUNG-SM-G900V
Model number: SM-G900V
Android version: 4.4.2
Baseband version: G900VVRU1ANCG
Kernel version: 3.4.0, [email protected]#1
Hardware version: G900V.05
Security software version: MDF v1.0Release2, VPN v1.4 Release 1
Towelroot
Click to expand...
Click to collapse
If you have frozen SDM in order to not get any more update requests, go unfreeze it. OpenGo into safestrap recovery and restore your stock copy. Open safestrap. Uninstall recovery. Go into settings, applications and uninstall safestrap. Now you should be able to open SuperSU , go into settings, go down to where it says to fully unroot your phone and unroot it. Or you could go down to software update and take an update. You will lose root then.

Tulsadiver said:
If you have frozen SDM in order to not get any more update requests, go unfreeze it. OpenGo into safestrap recovery and restore your stock copy. Open safestrap. Uninstall recovery. Go into settings, applications and uninstall safestrap. Now you should be able to open SuperSU , go into settings, go down to where it says to fully unroot your phone and unroot it. Or you could go down to software update and take an update. You will lose root then.
Click to expand...
Click to collapse
This sounds promising. Thanks!

Tulsadiver said:
If you have frozen SDM in order to not get any more update requests, go unfreeze it. OpenGo into safestrap recovery and restore your stock copy. Open safestrap. Uninstall recovery. Go into settings, applications and uninstall safestrap. Now you should be able to open SuperSU , go into settings, go down to where it says to fully unroot your phone and unroot it. Or you could go down to software update and take an update. You will lose root then.
Click to expand...
Click to collapse
SDM is not frozen by Titanium Backup, but I have not been getting update requests. Is there somewhere else it would be frozen?
Do I need to worry about "KLMS Agent 2.2.101" or "Knox Notification Manager 2.0" or "Support & Protection 3.0.1"? Those are frozen by TB.
Also, how risky is this method of unrooting?

ergalthema said:
SDM is not frozen by Titanium Backup, but I have not been getting update requests. Is there somewhere else it would be frozen?
Do I need to worry about "KLMS Agent 2.2.101" or "Knox Notification Manager 2.0" or "Support & Protection 3.0.1"? Those are frozen by TB.
Also, how risky is this method of unrooting?
Click to expand...
Click to collapse
You want stock so unfreeze everything. I believe you run the risk of losing root but that is the point, right? Everything you do with a rooted phone has risks but all you are doing is removing root.

Tulsadiver said:
You want stock so unfreeze everything. I believe you run the risk of losing root but that is the point, right? Everything you do with a rooted phone has risks but all you are doing is removing root.
Click to expand...
Click to collapse
Yes, I wanted to unroot and return to stock. That totally worked!!! Many thanks!!!

Reliable DOWNGRADE stock instructions

I have a Verizon S5 (SM-G900V) currently on 6.0.1, Baseband version G900VVRU2DPJ2. Build number MMB29M.G900VVRU2DPJ2.
Looking for instructions on how to downgrade to 5.0 on this phone without bricking it.
If this is possible, please provide instructions or a good URL to do so.
Thanks

I think all you need to do is Odin stock PB1.
Sent from my XT1650 using Tapatalk

Yep, just got done. Worked like a charm.

Also, I am thinking about root and custom rom to get rid of the bloat....but I don't want to brick it.
Looks like i will follow these instructions....http://forum.xda-developers.com/verizon-galaxy-s5/general/guide-painiacs-essential-guide-to-t3319848

wetherb67 said:
Also, I am thinking about root and custom rom to get rid of the bloat....but I don't want to brick it.
Looks like i will follow these instructions....http://forum.xda-developers.com/verizon-galaxy-s5/general/guide-painiacs-essential-guide-to-t3319848
Click to expand...
Click to collapse
I have a GS5 with the same baseband version and build number. Were you able to root or load custom ROM?

jwgilesjr said:
I have a GS5 with the same baseband version and build number. Were you able to root or load custom ROM?
Click to expand...
Click to collapse
So, to follow up on this, I downgraded to PB1 and was able to achieve root using instructions I found in the forum. Turns out I have the Toshiba version of the phone, so I'm unable to unlock the bootloader and can't upgrade to MM without losing root.
Still, the information in the forum is very helpful. Just takes some reading and patience,