[Q]help updating sph-L720 - Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot

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.

Related

[Q] Rogers i377m root/cwm

Have the Canadian s4 (rogers variant) i377m , I was running gummy 1.1 (kitkat) rom and decided to revert to stock after some issues with wifi camera, time not updating, etc.... and someone had requested some files from the variant for dev unbrick stuff. Crappy timing, because when I pulled the stock fw from samsungupdates it was 4.3 . flashed via odin, lost my cwm and root but figured I'd just repeat the auto-root method. Then I saw Knox. Did some research, and saw all the issues everyone is having with custom recoveries not booting. Then I found a work around, however performing said work around would set Knox status to 0x1 and void warranty. Since phone is only 2 weeks old, figured I'd hang tight for another method.
Did some more checking and t turns out, Knox isn't actually installed, nor are the files when I search by name, if I tap it it tells me I can download and install knox (no thanks) and I just haven't bothered. it's just a shortcut. I'm wondering if anyone can answer whether or not I can safely flash with Odin via auto-root method to re-root and install TWRP or CWM recovery? I'd prefer not to lose warranty, but since knox doesn't appear to be actually installed, not sure I have to worry about that.
Here are my particulars:
Rogers i377m
JB 4.3 (official)
im mk6 baseband
kernel is 3.4.0-2142508 with build date of sat nov 16 (believe still custom from rom???)
However, SEL Linux is now enforcing.
Can anyone tell me with above config, which method would be best to use (to obtain root) . I did backup my IEMI with qpst back when I was on 4.2.2 . Could I potentially restore said IEMI with qpst, then re-flash the 4.2.2 fw to get out of this Konx/SEL enforce I'm seeing?
I don't have a ton of experience, but I have been reading as much as I can, and I've flashed my phone from 4.2.2 to all my custom stuff (and a co-workers) and have reverted back to stock with odin. I don't have a usb jig if I soft brick (but I suppose I could make one), and I work in the IT field so I'm faily competent. Need a little direction/confirmation.
azuziel said:
Have the Canadian s4 (rogers variant) i377m , I was running gummy 1.1 (kitkat) rom and decided to revert to stock after some issues with wifi camera, time not updating, etc.... and someone had requested some files from the variant for dev unbrick stuff. Crappy timing, because when I pulled the stock fw from samsungupdates it was 4.3 . flashed via odin, lost my cwm and root but figured I'd just repeat the auto-root method. Then I saw Knox. Did some research, and saw all the issues everyone is having with custom recoveries not booting. Then I found a work around, however performing said work around would set Knox status to 0x1 and void warranty. Since phone is only 2 weeks old, figured I'd hang tight for another method.
Did some more checking and t turns out, Knox isn't actually installed, nor are the files when I search by name, if I tap it it tells me I can download and install knox (no thanks) and I just haven't bothered. it's just a shortcut. I'm wondering if anyone can answer whether or not I can safely flash with Odin via auto-root method to re-root and install TWRP or CWM recovery? I'd prefer not to lose warranty, but since knox doesn't appear to be actually installed, not sure I have to worry about that.
Here are my particulars:
Rogers i377m
JB 4.3 (official)
im mk6 baseband
kernel is 3.4.0-2142508 with build date of sat nov 16 (believe still custom from rom???)
However, SEL Linux is now enforcing.
Can anyone tell me with above config, which method would be best to use (to obtain root) . I did backup my IEMI with qpst back when I was on 4.2.2 . Could I potentially restore said IEMI with qpst, then re-flash the 4.2.2 fw to get out of this Konx/SEL enforce I'm seeing?
I don't have a ton of experience, but I have been reading as much as I can, and I've flashed my phone from 4.2.2 to all my custom stuff (and a co-workers) and have reverted back to stock with odin. I don't have a usb jig if I soft brick (but I suppose I could make one), and I work in the IT field so I'm faily competent. Need a little direction/confirmation.
Click to expand...
Click to collapse
I am waiting for an answer to that question too. Got my S4 on friday. Was on 4.2.2 and I let it update to 4.3 without even asking myself "Is that OK?". I've read all that stuff about MF3 (AT&T) and I am wondering if Canadian's MK6 is something like MF3. Forcing us to use other recoveries than CWM or TWRP.
Bleedos said:
I am waiting for an answer to that question too. Got my S4 on friday. Was on 4.2.2 and I let it update to 4.3 without even asking myself "Is that OK?". I've read all that stuff about MF3 (AT&T) and I am wondering if Canadian's MK6 is something like MF3. Forcing us to use other recoveries than CWM or TWRP.
Click to expand...
Click to collapse
Yeah I don't particularly care about the Knox counter and warranty, what I do care about is being able to run custom recovery (CWM in particular). I would hate to root, blow the knox counter, then find out can't run custom recoveries anyway. I've read conflicting info on this. I know once knox is installed, that's what can happen. However with our particular rogers variant (at least mine, I flashed with odin to 4.3 tho) Knox isn't installed anywhere, at all, just a shortcut to install if desired. And I don't desire. May have to just bite the bullet and try, but I'll wait a bit longer first to see if someone has a concrete answer on our particular MK6 version.
believe we have our answer
http://forum.xda-developers.com/showthread.php?p=47840073
According to post above, SGH-I337M from rogers running 4.3 MK6 can be rooted with CF-AUTO-ROOT
not sure about that bootloaders, but the method shoud work with odin.
Az
I also have the Rogers 4.3 update installed on my I337m, and I only see the Knox shortcut. Does this mean it's not installed? Will it still trip the counter if I root?
You can use that but it will trip the counter. I know because that's what I did. There are apparently other methods floating around that won't trip knox. However I am able to root and run custom recoveries and roms just like before no problems.
Sent from my SGH-I337M using XDA Premium 4 mobile app
maestro18 said:
I also have the Rogers 4.3 update installed on my I337m, and I only see the Knox shortcut. Does this mean it's not installed? Will it still trip the counter if I root?
Click to expand...
Click to collapse
Honestly? I don't know. I have the same. Knox shortcut (deleted). I guess the easiest way to check would be to boot into download mode (VOL down+power+home at start up) and check for
KNOX = 0x0 (warranty good)
KNOX = 0x1 (warranty void)
then just pull the battery and boot back up normally.
htc0101 said:
You can use that but it will trip the counter. I know because that's what I did. There are apparently other methods floating around that won't trip knox. However I am able to root and run custom recoveries and roms just like before no problems.
Click to expand...
Click to collapse
Yeah, there is a method of cooking the root into the image before flashing with odin. just google "universal root de la vega" for method. I haven't tried this method yet, but it seems to work well for everyone that has (on i337m) , and wants to keep knox un-tripped. Apparently Kingo can do it too, but i hear adware complaints about that. Not sure I care about knox, as there are other methods of flashing official modem update files via odin (when new updates are released) to obtain the updates without using OTA or kies.
canadian bell user here...
I flashed the 4.3 update and yes it does include knox bootloaders.
Yes, rooting, installing custom recovery or kernel will trip a Knox Warranty Counter, that has not been hacked yet. (word is, that it is software not hardware based).
Did I trip mine? yup.
Do I care? nope.
Bell Smartphone Protection Plan 8$ per month, plus 160$ when getting replacement (beats 600$) covers lost/stolen, water damaged, and smashed phones... and dont care if the bootloader or flash counter is tripped. (kinda hard to tell if the screen is smashed or phone is stolen anyway.)
They ship it to samsung who disassembles the phone, replaces the broken parts, and flashes back to stock with counter reset, tests, and puts it in the refurbished pile. . they never check, care or can do anything about it after a point.
This is how i got my S4, broke my S3 and had the opportunity to get a different replacement model for same price. They shipped my new phone in 3 days, with a return postage sticker for my old, cracked but still functional S3. 0 downtime. 0 hassle.
cf root work
Cf root worked for my 4.3 update on my Canadian rogers. I'm looking for the 4.3 stock rom for rogers now with no luck. Does anyone have any idea
4.3 stock is on Samsungupdates i cant post links yet or i would post it. I used it, and mentioned it in this thread.
Sent from my SGH-I337M
azuziel said:
4.3 stock is on Samsungupdates i cant post links yet or i would post it. I used it, and mentioned it in this thread.
Sent from my SGH-I337M
Click to expand...
Click to collapse
http://samsung-updates.com/device/?id=SGH-I337M
Yay, I can post links now. Enjoy. Make sure you mouse over region and find rogers variant.
azuziel said:
Yeah I don't particularly care about the Knox counter and warranty, what I do care about is being able to run custom recovery (CWM in particular). I would hate to root, blow the knox counter, then find out can't run custom recoveries anyway. I've read conflicting info on this. I know once knox is installed, that's what can happen. However with our particular rogers variant (at least mine, I flashed with odin to 4.3 tho) Knox isn't installed anywhere, at all, just a shortcut to install if desired. And I don't desire. May have to just bite the bullet and try, but I'll wait a bit longer first to see if someone has a concrete answer on our particular MK6 version.
Click to expand...
Click to collapse
Did it the easy way using the Cyanogen Installer (http://beta.download.cyanogenmod.org/install).
Ended with CM10.2 and CWM 6.0.4.4
Then I found this link for flashable zips for CWM and TWRP.
http://www.androidfilehost.com/?a=show&w=files&flid=8421
Got this link from there:
http://forum.xda-developers.com/showpost.php?p=43216990&postcount=3
Make sure you thank iB4STiD
I flashed CWM Touch 6.0.4.4
I was running the stock AMG1 which showed KNOX. I was told that if I can flash a custom recovery such as TWRP or CMR, that my phone is not locked. So I flashed AMDJ to see. I also flashed TWRP with no issues. I then installed Gummy version:1.1-11-21-13-UNOFFICIAL. I found KNOX but was able to remove it using Titanium Backup. Apparently it was not activated? I am now on Android 4.4, Baseband I337MVLUAMDJ, Kernel Version [email protected] #1 Thu Nov 21,2013, Gummy Version 1.1-11-21-13-UNOFFICIAL, Build Date Thu Nov 21, 2013, Build Number KRT16S, SELinux Status Permissive. I am using the SGH-I337M from BELL.
---------- Post added at 09:45 PM ---------- Previous post was at 09:36 PM ----------
I would like to install AWS Bands for T-Mobile on my BELL I337M. I am currently running Gummy 1.1 on version 4.4. I was told that I can't install T-Mobile AWS bands without messing up my IMEI etc. if I am not on a stock ROM. Can anyone confirm or deny this? My phone runs painfully slow on T-Mobile (Edge 2G). Any information would be much appreciated.
Fido s4 user here. I updated to 4.3, used auto root, and don't care about tripping counter. But since doing all that (2 weeks ago), I've tried two custom roms, and they don't get past boot screen after installation. I get this thing about seandroid and kernel, recovery. Not sure what to do about that. :-\
Sent from my SGH-I337M using Tapatalk
Miyamato said:
Fido s4 user here. I updated to 4.3, used auto root, and don't care about tripping counter. But since doing all that (2 weeks ago), I've tried two custom roms, and they don't get past boot screen after installation. I get this thing about seandroid and kernel, recovery. Not sure what to do about that. :-\
Sent from my SGH-I337M using Tapatalk
Click to expand...
Click to collapse
Try Flash the proper kernel. Do a factory reset via cwm after flashing as well to remove the old user data.
Sent from my SGH-I337M
azuziel said:
Try Flash the proper kernel. Do a factory reset via cwm after flashing as well to remove the old user data.
Sent from my SGH-I337M
Click to expand...
Click to collapse
What kernel are you talking about? Do you have a link by any chance?
so since updating to 4.3 via OTA, then rooting phone (auto root). If i wanted to unroot the phone (SELinux is enforcing), I shouldn't have any problem unrooting it via Odin 1.85 with fido firmware for 4.3, correct?
Targor_Avelany said:
What kernel are you talking about? Do you have a link by any chance?
Click to expand...
Click to collapse
If having kernel issues then i find easiest way to remedy is to flash a stock firmware. The img file contains the stock kernel. This will get you back to a working state, then use saferoot or kingo to reroot, goo manager for twrp or cwm installer for custom recovey, and off you go.
I generally avoid roms that don't include the proper kernel. Gummy rom (kitkat) includes proper kernel and is the most stable non stock fw ive run, personally.
Miyamato said:
so since updating to 4.3 via OTA, then rooting phone (auto root). If i wanted to unroot the phone (SELinux is enforcing), I shouldn't have any problem unrooting it via Odin 1.85 with fido firmware for 4.3, correct?
Click to expand...
Click to collapse
Selinux is enforced on 4.3 yes. There are methods for putting into permissive, but isnt really necessary as most apps have been updated to run on 4.3.
Regarind unroot via flashing stock, correct. Stock will flash stock recovery, stock kernel and os, and yes it removes root. Like any flash, be sure to wipe old sys/user data via a factory reset after flashinf stock if you boot loop (soft brick).
Sent from my SGH-I337M

Try new firmware on S4 without rooting possible?

Hi All,
Am using an i337M S4 from Rogers here in Canada and was wondering if it was possible to use ODIN and try out the new leaked 4.4 firmware. Is rooting required to achieve this?
rsarwar said:
Hi All,
Am using an i337M S4 from Rogers here in Canada and was wondering if it was possible to use ODIN and try out the new leaked 4.4 firmware. Is rooting required to achieve this?
Click to expand...
Click to collapse
First you must be certain the leak is for i337m model becuase there is the international version and the US version which are both different from the model you have (I have the same but Telus). Now as far as the files, if they are in .tar format then you can flash via Odin, if thet are .zip then you need a custom recovery to flash them. I know for certain you need to root to go the custom recovery route, I think you need to be rooted to flash they system files in Odin also (which if it is a stock rom you are flashing would loose root following the flash). Depending of the root method you choose be aware also that you may trip the Knox counter also, definately if you install a custom recovery. There a number of 4.4 roms for the i337m already that are not stock and are rooted, you may want to look at these also. Most importantly... before you attempt anything read...read ... read... there are pity falls you can end up in if you don't pay close attention......
Gage_Hero said:
First you must be certain the leak is for i337m model becuase there is the international version and the US version which are both different from the model you have (I have the same but Telus). Now as far as the files, if they are in .tar format then you can flash via Odin, if thet are .zip then you need a custom recovery to flash them. I know for certain you need to root to go the custom recovery route, I think you need to be rooted to flash they system files in Odin also (which if it is a stock rom you are flashing would loose root following the flash). Depending of the root method you choose be aware also that you may trip the Knox counter also, definately if you install a custom recovery. There a number of 4.4 roms for the i337m already that are not stock and are rooted, you may want to look at these also. Most importantly... before you attempt anything read...read ... read... there are pity falls you can end up in if you don't pay close attention......
Click to expand...
Click to collapse
Thanks for the reply .. actually I had a S2 before which was rooted and I used many different ROMs on it. I did root the S4 once as well but then lost it when I did the 4.3 update. Since then I never tried to re-root, is there an easy way too root right now for the i337M with 4.3?
If you are on stock unrooted 4.3 you should get official 4.4 update soon.
Also, questions go in the qna section not the development section
Sent from my SGH-I337 using Tapatalk
RK said:
If you are on stock unrooted 4.3 you should get official 4.4 update soon.
Also, questions go in the qna section not the development section
Sent from my SGH-I337 using Tapatalk
Click to expand...
Click to collapse
If you wait for the update you will likely be waiting longer for a root solution... if you want to root the phone, look up chainfire's CF-auto root for i337m

[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

[Q] Proper Rooting and SafeStrap Process NC4

Okay so I've been browsing through the forums and been reading up on this phone (even contacted Samsung about info on unlocking the bootloader, no go on that. Had to try though)
Basically I want to know what's the proper procedure for installing custom roms on an NC4 device 4.4.2
Things I know:
Bootloader is unlockable at the moment (hoping for some good news in the future)
Towelroot for rooting
Safestrap for recovery
(Both just download and install the apk)
Things I don't know:
Kernel?
Somebody said I had to flash the NC2 kernel via Odin?
Knox?
What is this? What trips it?
I did see the list of guides and I did read and watch all the necessary ones, but the date on those are from 2 years ago and I just need confirmation on if I'm going about this right.
Any help is appreciated. I thank you in advance for taking the time to read this.
Please excuse my lack of knowledge, this is my first Samsung device.
Also, what would happen if somebody were to flash the DE stock files via Odin to a Retail N3?
If you upgraded to NC4 or NK1, you're stuck until Samsung unlocks the bootloader or Verizon stops lying to their customers. There is no root available after upgrade at this moment in time.
Dravekx said:
If you upgraded to NC4 or NK1, you're stuck until Samsung unlocks the bootloader or Verizon stops lying to their customers. There is no root available after upgrade at this moment in time.
Click to expand...
Click to collapse
I didn't upgrade to NC4, it came like this.
rdar_93 said:
I didn't upgrade to NC4, it came like this.
Click to expand...
Click to collapse
That sucks. You can't do anything about it at the moment. I was forced to upgrade and lost root. Custom ROMs won't be available to you or me until someone finds a hole to unlock the bootloader. Welcome to our Verizon Note 3 rooting dilemma.
mirrin said:
You do not have a dev version so cm 11 or 12 is a far off dream you won't get. Your bootloader is locked there is no unlock.
You are in luck nc4 is root able using towel root then safe strap and the unified firmware. You will need odin and a pc for flashing a few things the NK1 modem towel root and the unified firmware. Pick a rom from the development thread i suggest jasmine 1.x or eclipse.
Click to expand...
Click to collapse
Copied from another post I had.
I don't know much about the device which is why I'm trying to find out.
Dravekx said:
That sucks. You can't do anything about it at the moment. I was forced to upgrade and lost root. Custom ROMs won't be available to you or me until someone finds a hole to unlock the bootloader. Welcome to our Verizon Note 3 rooting dilemma.
Click to expand...
Click to collapse
I actually just got root on my phone, I felt adventurous and installed towelroot and voila it rooted my phone.
I should state that I'm on 4.4.2, not 4.4.4.
Checked root status with Titanium Backup Pro, everything checked out a-okay.
rdar_93 said:
Okay so I've been browsing through the forums and been reading up on this phone (even contacted Samsung about info on unlocking the bootloader, no go on that. Had to try though)
Basically I want to know what's the proper procedure for installing custom roms on an NC4 device 4.4.2
Things I know:
Bootloader is unlockable at the moment (hoping for some good news in the future)
Towelroot for rooting
Safestrap for recovery
(Both just download and install the apk)
Things I don't know:
Kernel?
Somebody said I had to flash the NC2 kernel via Odin?
Knox?
What is this? What trips it?
I did see the list of guides and I did read and watch all the necessary ones, but the date on those are from 2 years ago and I just need confirmation on if I'm going about this right.
Any help is appreciated. I thank you in advance for taking the time to read this.
Please excuse my lack of knowledge, this is my first Samsung device.
Also, what would happen if somebody were to flash the DE stock files via Odin to a Retail N3?
Click to expand...
Click to collapse
Ahhhh... You're good to go then! Find a good custom ROM and follow the instructions. Whatever you do.. Don't upgrade!
rdar_93 said:
I actually just got root on my phone, I felt adventurous and installed towelroot and voila it rooted my phone.
I should state that I'm on 4.4.2, not 4.4.4.
Checked root status with Titanium Backup Pro, everything checked out a-okay.
Click to expand...
Click to collapse
Dravekx said:
Ahhhh... You're good to go then! Find a good custom ROM and follow the instructions. Whatever you do.. Don't upgrade!
Click to expand...
Click to collapse
Lol I still need clarification on the Kernel information that I don't know about.
What do I need to flash?
Do I flash it after I install a custom rom or before?
rdar_93 said:
Lol I still need clarification on the Kernel information that I don't know about.
What do I need to flash?
Do I flash it after I install a custom rom or before?
Click to expand...
Click to collapse
My opinion: If you're doing a custom kernel, make sure it works with whatever ROM you're flashing. I suggest sticking with the stock kernel* until you get the hang of things OR do a little research and learn a bit before you attempt anything. There's a lot of forums with details and help here. I've installed kernels before and after installing ROMs with little or zero problems, but I'm more of a dabbler than a professional.
I would suggest backing up your current setup in case you need to reflash. That's a definite.
Dravekx said:
My opinion: If you're doing a custom kernel, make sure it works with whatever ROM you're flashing. I suggest sticking with the stock kernel* until you get the hang of things OR do a little research and learn a bit before you attempt anything. There's a lot of forums with details and help here. I've installed kernels before and after installing ROMs with little or zero problems, but I'm more of a dabbler than a professional.
I would suggest backing up your current setup in case you need to reflash. That's a definite.
Click to expand...
Click to collapse
Lol that doesn't really answer the question. I hope somebody sees it and clears it up for me
rdar_93 said:
Lol that doesn't really answer the question. I hope somebody sees it and clears it up for me
Click to expand...
Click to collapse
The kernel can't be changed...although it can be "tuned" if you have root.
http://forum.xda-developers.com/showthread.php?p=58813428
Sent from my Note 3 via Tapatalk
Still hoping somebody helps me out and posts a short but precise guide to install a custom rom on 4.4.2 NC4
I don't want to end up bricking my device on the first try. I've been there already and it sucks lol
rdar_93 said:
Still hoping somebody helps me out and posts a short but precise guide to install a custom rom on 4.4.2 NC4
I don't want to end up bricking my device on the first try. I've been there already and it sucks lol
Click to expand...
Click to collapse
It really depends on the ROM, there is no set guide for all ROMs.
Did you install busybox? I like using busybox on rails. Just download the app and click install.
Download the safestrap apk (3.75 B04) and install that, open it and install recovery.
I'm currently running Clean ROM. I am on NC4. I downloaded the rom, and moved it to my SD card. I rebooted to safestrap, wiped data, cache and dalvik then installed the ROM to the stock slot. Then, following the instructions for Clean ROM, I rebooted to download mode from recovery and flashed the NC2 Kernel with odin.
The main thing is to read the installation instructions for the particular ROM you want to flash.
Don't forget to use Titanium backup to freeze SDM app (I think that's what its called) so your phone will stop trying to update.
---------- Post added at 05:29 PM ---------- Previous post was at 05:23 PM ----------
rdar_93 said:
Still hoping somebody helps me out and posts a short but precise guide to install a custom rom on 4.4.2 NC4
I don't want to end up bricking my device on the first try. I've been there already and it sucks lol
Click to expand...
Click to collapse
If you're at all proficient with Odin it is really REALLY hard to brick these phones.
BladeRunner said:
It really depends on the ROM, there is no set guide for all ROMs.
Did you install busybox? I like using busybox on rails. Just download the app and click install.
Download the safestrap apk (3.75 B04) and install that, open it and install recovery.
I'm currently running Clean ROM. I am on NC4. I downloaded the rom, and moved it to my SD card. I rebooted to safestrap, wiped data, cache and dalvik then installed the ROM to the stock slot. Then, following the instructions for Clean ROM, I rebooted to download mode from recovery and flashed the NC2 Kernel with odin.
The main thing is to read the installation instructions for the particular ROM you want to flash.
Don't forget to use Titanium backup to freeze SDM app (I think that's what its called) so your phone will stop trying to update.
---------- Post added at 05:29 PM ---------- Previous post was at 05:23 PM ----------
If you're at all proficient with Odin it is really REALLY hard to brick these phones.
Click to expand...
Click to collapse
Thanks man, I was supposed to update this thread saying that I got through with the proper procedure for installing Jasmine Rom
Although I was running Eclipse before, and I wanted to try going back to stock but it just got stuck on the Verizon splash screen
I'm thinking it's because I had the NC2 kernel active when I should have gone back to the NC4 kernel
I looked for a NC4 kernel to flash but I only saw the modems and tar files, so not knowing if those were the same as kernels I decided to just try Jasmine. So far, I like it.
I have crazy battery drain though. I think it's because I'm running it in Slot 1
just picked up a verizon note 3 android 4.4.2 NC4
one of the very first posts above says you cant do anything on NC4 and then another post says NC4 is ok but just not android 4.4.4
NC4 is the latest update as of this writing isnt it?
what can actually be done with this vzw note 3 on android 4.4.2 NC4?
non dev edition of course
what about knox?
if rooting can be done with this phone on this OS is there any safe way not to trip knox?
en11gma said:
just picked up a verizon note 3 android 4.4.2 NC4
one of the very first posts above says you cant do anything on NC4 and then another post says NC4 is ok but just not android 4.4.4
NC4 is the latest update as of this writing isnt it?
what can actually be done with this vzw note 3 on android 4.4.2 NC4?
non dev edition of course
what about knox?
if rooting can be done with this phone on this OS is there any safe way not to trip knox?
Click to expand...
Click to collapse
I'd be happy to answer your questions
If you have an NC4 device that's running 4.4.2, you are able to gain root access and install safestrap recovery on your device. However, if the android version is 4.4.4, you cannot root or install safestrap.
NC4 is just our last build number, but there are two versions I think, the 4.4.2 and the 4.4.4. In the 4.4.4, they blacklisted every single compatible kernel that could work on the device. They forgot to do it in the 4.4.2 version, that's why we're able to gain root.
On our NC4 4.4.2 Verizon Note 3, we can root, install safestrap recovery and install a very limited amount of roms from the non developer edition selection on the XDA forums.
Rooting via towelroot, to my knowledge, does not trip knox. However, installing safestrap recovery does. But if you're worried about your warranty being voided, I wouldn't panic too much because with our bootloader being locked, it is very easy to flash the original Stock Verizon files through Odin to go straight back to factory settings so it looks like if you just pulled it out the box. The knox code would be reset and you would have a device that looked like if it has never been rooted or modified.
rdar_93 said:
I'd be happy to answer your questions
If you have an NC4 device that's running 4.4.2, you are able to gain root access and install safestrap recovery on your device. However, if the android version is 4.4.4, you cannot root or install safestrap.
NC4 is just our last build number, but there are two versions I think, the 4.4.2 and the 4.4.4. In the 4.4.4, they blacklisted every single compatible kernel that could work on the device. They forgot to do it in the 4.4.2 version, that's why we're able to gain root.
On our NC4 4.4.2 Verizon Note 3, we can root, install safestrap recovery and install a very limited amount of roms from the non developer edition selection on the XDA forums.
Rooting via towelroot, to my knowledge, does not trip knox. However, installing safestrap recovery does. But if you're worried about your warranty being voided, I wouldn't panic too much because with our bootloader being locked, it is very easy to flash the original Stock Verizon files through Odin to go straight back to factory settings so it looks like if you just pulled it out the box. The knox code would be reset and you would have a device that looked like if it has never been rooted or modified.
Click to expand...
Click to collapse
Safestrap does not trip knox.
mjh68 said:
Safestrap does not trip knox.
Click to expand...
Click to collapse
Thanks. I must have tripped mine somehow cause my device says "custom" when booting.
I'm guessing it might be Xposed but I'm not too sure.
rdar_93 said:
Thanks. I must have tripped mine somehow cause my device says "custom" when booting.
I'm guessing it might be Xposed but I'm not too sure.
Click to expand...
Click to collapse
It will say custom, but that isn't tripping knox. Custom can be removed with the triangle away app. Custom just gets flagged like you were saying by changing the recovery , but it doesn't trip the knox counter.
mjh68 said:
It will say custom, but that isn't tripping knox. Custom can be removed with the triangle away app. Custom just gets flagged like you were saying by changing the recovery , but it doesn't trip the knox counter.
Click to expand...
Click to collapse
Then I must be confused about what knox really is.
What is "Knox" then?

[Q] New to rooting

I have a Galaxy S5 SM-G900V Version 5.0 I am wondering if it is possible to root it any help would be greatly appreciated
If you read the post above yours, or any of the posts in this forum, you will probably figure out how to root your device. Pro tip!
I have read them and have tried several different ways but I must be missing something because when I flash my device it keeps going into boot recovery and I cant get it to go any further
bobyluvjr said:
I have read them and have tried several different ways but I must be missing something because when I flash my device it keeps going into boot recovery and I cant get it to go any further
Click to expand...
Click to collapse
You soft bricked it. I recommend using Kies 3 to repair and initialize the phone again to stock, unless you made a nandroid backup. Then, you'll have to flash a NK2 retail stock, since no one has been able to find a method to root AO8 Lollipop 5.0 without tripping knox. If you don't mind tripping knox, which voids your warranty.
Rapunzl said:
You soft bricked it. I recommend using Kies 3 to repair and initialize the phone again to stock, unless you made a nandroid backup. Then, you'll have to flash a NK2 retail stock, since no one has been able to find a method to root AO8 Lollipop 5.0 without tripping knox. If you don't mind tripping knox, which voids your warranty.
Click to expand...
Click to collapse
you are wrong lmao.. we have root for the g900v (he must be having user errors if he cant get it to work) but there is NO process for the g900v that will trip Knox at all because we cant touch the BL due to it being locked.. Knox has nothing to do with anything at this point. His warranty is still good but yes, his phone is soft bricked if he cant boot up
Sent from my SM-G900V using XDA Free mobile app
bobyluvjr said:
I have a Galaxy S5 SM-G900V Version 5.0 I am wondering if it is possible to root it any help would be greatly appreciated
Click to expand...
Click to collapse
Have you tried finding a full ncg tar file (full meaning it includes the kernel), Odin that to put you on ncg. Download towelroot and install it. Run towelroot and that should root you. Download latest safestrap and install it. Then download any other the rooted lollipop roms and the lollipop kernel(kernel will be downloaded on computer) . Install it via safestrap, boot directly into download mode and Odin the lollipop kernel. Reboot. Should be rooted lollipop and good to.
New too rooting
ok I managed to figure this all out i think I got it to restore back to 5.0 using odin by flashing the stock files I found on the forums then I found another tutorial on rooting and followed it and managed to figure it out so now I am running
Android Version
4.4.4
Baseband Version
G900VVRU1ANHA
Kernel Version
3.4.0
[email protected]#1
Build Number
KTU84P.G900VVRU1ANHA
I don't know if that means any thing to you guys but my next task is to find a rom that ultimately will get rid of allot of the boat from verizon and ideally I would like to have the multi user feature but I am not sure that is availible for android 4.4.4
elliwigy said:
you are wrong lmao.. we have root for the g900v (he must be having user errors if he cant get it to work) but there is NO process for the g900v that will trip Knox at all because we cant touch the BL due to it being locked.. Knox has nothing to do with anything at this point. His warranty is still good but yes, his phone is soft bricked if he cant boot up
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
I'm new to the locked bootloader, so I stand corrected on that point. You taught me something, and I got a laugh out of you.

Categories

Resources