I've spent hours searching and I know this is an old phone. Is ther anyway to root the Lollipop and download Jelly Bean (custom or stock) to it? I'm not worried about Warranties. I'm not exactly a newb and I don't like Lollipop at all. I don't mind KitKat, but what I hate is the front facing camera can't be flipped. Dumbest thing ever.
http://forum.xda-developers.com/galaxy-s4-sprint
Search for CF-Autoroot.
Strephon Alkhalikoi said:
http://forum.xda-developers.com/galaxy-s4-sprint
Search for CF-Autoroot.
Click to expand...
Click to collapse
I'm supposedly rooted. I used KingRoot and then switched over yo SuperSU. But I can't seem to get the Rom's to install. This is where I'm probably going wrong. I'm assuming it has to do with the Bootloader.
BikerSk8rKid said:
I'm supposedly rooted. I used KingRoot and then switched over yo SuperSU. But I can't seem to get the Rom's to install. This is where I'm probably going wrong. I'm assuming it has to do with the Bootloader.
Click to expand...
Click to collapse
Ask the right questions if you want the right answer.
You said you're not a newb. So what exactly was the procedure used to to install those ROMs?
Well, you should be using CF-Autoroot, as it's the recommended method to root these devices. That said, unless you have a frankenphone, only AT&T and Verizon models have locked bootloaders. Enter download mode and verify your device's model number please?
GDReaper said:
Ask the right questions if you want the right answer.
You said you're not a newb. So what exactly was the procedure used to to install those ROMs?
Click to expand...
Click to collapse
I was half asleep and stressed out when I posted this. It's been a couple weeks or longer since I messed with the phone. Damn forums weren't resetting my password. When I mean I'm not a newb I mean I'm not like brand new to this and I know how to research. I guess you could say I'm not THAT stupid. haha
I'mma have to try this again and figure out what path's I kept trying. I'm so spaced out I can't remember hard any of it. Just that I tried to flash a stock and rooted rom with old odin and new odin. Spent 2 days straight messing with it and trying to get around it. But I kept getting blocked. I didn't come across CF-Autoroot. So I'll try that.
Strephon Alkhalikoi said:
Well, you should be using CF-Autoroot, as it's the recommended method to root these devices. That said, unless you have a frankenphone, only AT&T and Verizon models have locked bootloaders. Enter download mode and verify your device's model number please?
Click to expand...
Click to collapse
Of all the researching I've done (I couldn't login) that one never showed up in my searchs. haha I'll have to give that one a try. It's been a couple weeks or longer. SPH-L720. I had a few Tri-Bands, but it seemed those were limited compared to the standard model.
Update: I went the CF-AutoRoot route and then tried to use Odin to flash stock mk2 rom. Now that I remember it kept failing everytime and then it would corrupt the current rom. I also tried using TWRP and couldn't get it to work properly.
That's a Sprint device, so your bootloader is unlocked.
Here's something you should note: If you want to flash a ROM, of any kind, you don't necessarily have to be rooted.
Stock ROMs require Odin and custom ROMs require a custom recovery. None of them require root.
Your flash to an older version fails most probably due to the fact that you're trying to downgrade the bootloader (Any stock ROM flash also modifies the bootloader and modem partitions).
But your windows, cable, USB port and windows can also be at fault here.
GDReaper said:
That's a Sprint device, so your bootloader is unlocked.
Here's something you should note: If you want to flash a ROM, of any kind, you don't necessarily have to be rooted.
Stock ROMs require Odin and custom ROMs require a custom recovery. None of them require root.
Your flash to an older version fails most probably due to the fact that you're trying to downgrade the bootloader (Any stock ROM flash also modifies the bootloader and modem partitions).
But your windows, cable, USB port and windows can also be at fault here.
Click to expand...
Click to collapse
For some reason I kept reading that it was locked or thinking it was locked because of not being able to downgrade.
So that's what I thought and I guess that's what I was trying to get at in my first post. Trying to go from Lollipop 5 to Jelly Bean 4.3 or so. Is it possible to do that whether it's custom or not?
I just hate the Lollipop and the KitKat. My Galaxy S2 had the JB and Power Button took a crap. So I ended up getting a S3 and now been sitting on an S4.
I know it's not the cable or at least it shouldn't be because it works to flash the stock current rom everytime I corrupt it. The computer is like brand new and running Windows 8.1
BikerSk8rKid said:
For some reason I kept reading that it was locked or thinking it was locked because of not being able to downgrade.
So that's what I thought and I guess that's what I was trying to get at in my first post. Trying to go from Lollipop 5 to Jelly Bean 4.3 or so. Is it possible to do that whether it's custom or not?
I just hate the Lollipop and the KitKat. My Galaxy S2 had the JB and Power Button took a crap. So I ended up getting a S3 and now been sitting on an S4.
I know it's not the cable or at least it shouldn't be because it works to flash the stock current rom everytime I corrupt it. The computer is like brand new and running Windows 8.1
Click to expand...
Click to collapse
Downgrading sometimes succeeds. There are also guides on how to downgrade, though there aren't any special procedures. Maybe the bootloader version of the firmware-to-be-flashed matters.
With custom ROMs it's definitely possible, as they do not change the bootloader.
GDReaper said:
Downgrading sometimes succeeds. There are also guides on how to downgrade, though there aren't any special procedures. Maybe the bootloader version of the firmware-to-be-flashed matters.
With custom ROMs it's definitely possible, as they do not change the bootloader.
Click to expand...
Click to collapse
I guess I'm more of a newb with this than I expected. :/ It's been years since I've been on the forums or even tinkered with phones. HTC Touch Pro 2 was the last one I believe. haha
So... With that being said. Custom Roms are typically to the current stock rom, correct? or is it possible to get a Custom Jelly Bean and flash/overwrite it to the Lollipop/current? Since I just tripped wit the Knox Warranty with the CF-AutoRoot. LoL
BikerSk8rKid said:
I guess I'm more of a newb with this than I expected. :/ It's been years since I've been on the forums or even tinkered with phones. HTC Touch Pro 2 was the last one I believe. haha
So... With that being said. Custom Roms are typically to the current stock rom, correct? or is it possible to get a Custom Jelly Bean and flash/overwrite it to the Lollipop/current? Since I just tripped wit the Knox Warranty with the CF-AutoRoot. LoL
Click to expand...
Click to collapse
If you can find some viable download links, then yes, you should be able to flash custom jelly bean ROMs. But you need a custom recovery in order to do that.
The recovery can be flashed with Odin. Or, since you're rooted, you can also flash a recovery by using an app called Flashify.
Odin requires a .tar file and Flashify requires a .img file.
Oh, and you also need the gapps package for the Google Apps. You need a package for that specific android version, so it should be jelly bean gapps.
GDReaper said:
If you can find some viable download links, then yes, you should be able to flash custom jelly bean ROMs. But you need a custom recovery in order to do that.
The recovery can be flashed with Odin. Or, since you're rooted, you can also flash a recovery by using an app called Flashify.
Odin requires a .tar file and Flashify requires a .img file.
Oh, and you also need the gapps package for the Google Apps. You need a package for that specific android version, so it should be jelly bean gapps.
Click to expand...
Click to collapse
I'll look into that and give it a shot. Thank you! I knew it wasn't THAT easy. LOL
Related
Hi all,
I am interested in the CM11 ROM. Last night I spent 6hrs trying and failed, epically.
Here is what I did already:
1. Downgraded from 4.4.2 back to factory
2. Successfully rooted
3. Installed ROM Manager
4. Successfully downloaded CM11 and latest GApps
Then when I tried to boot into recovery it kept going to a screen with a little android guy lying on his back with a red triangle!!! I tried six times.
I got frustrated and just updated back to 4.4.2 and have been dealing with it. I am still rooted and have been able to remove my bloatware and other things you need root access for.
Any thoughts or help as to how I can install the CM11 rom?? I am happy running NovaLauncher and using DynamicNotifications to approximate it but really want to try out CM11.
Cheers and thanks!
Lucky there is no way to root on 4.4.2 yet or atleast no Recovery's yet it could be worse you're atleast rooted and it didn't brick your phone
Sent from my VS980 4G using Tapatalk
Did you actually try flashing a recovery first? Just installing ROM manager won't install the custom recovery needed to flash ROMs. You have to do that step as well.
JRJ442 said:
Did you actually try flashing a recovery first? Just installing ROM manager won't install the custom recovery needed to flash ROMs. You have to do that step as well.
Click to expand...
Click to collapse
No, I didn't. I am super new with android. Had an iphone for a long time. How do I flash a recover? Can I still do it now on 4.4.2 b/c its rooted?
Sorry about the noob questions, everyone is being very helpful!
follow this step..
http://forum.xda-developers.com/showthread.php?t=2681205
android_nashville said:
No, I didn't. I am super new with android. Had an iphone for a long time. How do I flash a recover? Can I still do it now on 4.4.2 b/c its rooted?
Sorry about the noob questions, everyone is being very helpful!
Click to expand...
Click to collapse
LG blocked the Loki exploit with 4.4.2 so you can't flash recoveries currently. You'd have to flash back to 4.2.2 to do that. Which if you want custom ROMs now its going to have to be done sooner or later. Which carrier and model number do you have? If you have an international D802 the above post by @zekurosu will work for you, otherwise don't use that one. You're gonna have to find the method for your model number.
My first guess was that you missed the flashing the custom recovery step, which people above me have already helped ya out on. For being new to Android you did fairly well, you just missed that one step.
Good luck!
JRJ442 said:
LG blocked the Loki exploit with 4.4.2 so you can't flash recoveries currently. You'd have to flash back to 4.2.2 to do that. Which if you want custom ROMs now its going to have to be done sooner or later. Which carrier and model number do you have? If you have an international D802 the above post by @zekurosu will work for you, otherwise don't use that one. You're gonna have to find the method for your model number.
Click to expand...
Click to collapse
thanks, forgot to mention it was only for D802 :good:
zekurosu said:
thanks, forgot to mention it was only for D802 :good:
Click to expand...
Click to collapse
I have an ATT D800 running 4.4.2. I can't decide whether its worth it to flash back to 4.2.2 to try again. Pretty happy with NovaLauncher + widgetlocke and fairly closely approximates what I am looking for.
For what its worth, I was in 4.2.2 when I tried the first time and failed. I think mackster is right, I didn't flash the custom recovery. I basically flashed back to 4.2.2->rooted->tried to boot into recovery (OVER and OVER) then gave up and upgraded back to 4.4.2.
Thanks for all the help. At least I now have a rooted phone and have been able to do some cool stuff with that. My goal is to get nexus 5 software in an LG G2 body (battery, camera, etc)
@android_nashville There's a way to have the best of both worlds. You can flash back to 4.2.2 (10d preferably) root, flash a custom recovery with Flashify or FreeGee. Both available on the play store. Then actually update to 4.4.2 following this thread http://forum.xda-developers.com/showthread.php?t=2483043. Eventually, if you want to flash custom ROMs you're going to have flash back to 4.2.2 and do this process regardless. The 4.4 aboot image (bootloader) can't be bypassed with Loki. Its been blocked. But some brilliant devs basically found out they can make a hybrid setup, with the 4.2.2 aboot, and everything else 4.4.2. This way you can have the ability to flash custom recovery, kernels and ROMs.
Hello all. First off I have a I337m with baseband NE1. I never see this mentioned anywhere and wanted to know what I can do with this phone.
I've rooted already (with towelroot) and wanted to get a custom bootloader. I've read and read then read somemore but found too many mixed staments regarding this.
Can I install a custom bootloader (say through goo manager) without worries or is there more to it? Does it completely overwrite the stock bootloader?
Do I need to worry about Loki?
Can we use other carrier ROMs?
Is it safe to say that everything in this sub forum works with my device?
Im familiar with flashing and the likes coming from the S2 with CM10.2 but there are too many varients and mixed statments (old to new methods) and I can't for the life of me find direction.
This is what I know about the i337m, mind you I don't have the device:
You can root using chainfires cf-auto root
Use trwp manager to install twrp
You can flash any rom here and you don't need Loki
Sent from my Nexus 5 using XDA Free mobile app
Bluntified said:
Hello all. First off I have a I337m with baseband NE1. I never see this mentioned anywhere and wanted to know what I can do with this phone.
I've rooted already (with towelroot) and wanted to get a custom bootloader. I've read and read then read somemore but found too many mixed staments regarding this.
Can I install a custom bootloader (say through goo manager) without worries or is there more to it? Does it completely overwrite the stock bootloader?
Do I need to worry about Loki?
Can we use other carrier ROMs?
Is it safe to say that everything in this sub forum works with my device?
Im familiar with flashing and the likes coming from the S2 with CM10.2 but there are too many varients and mixed statments (old to new methods) and I can't for the life of me find direction.
Click to expand...
Click to collapse
I have the same phone on Telus... as far as the "custom bootloader" I think you really mean custom recovery, I use TWRP version 2.7. You can also use Philz recovery or CWM but I perfer TWRP as it hasnt given me any issues. If you load TWRP don't go for the latest version as I have seen guys have problems with the latest and greatest.
Once you have twrp on your phone... before you do anything else... make a backup in twrp of your current rooted stock rom so you have a starting point. In twrp, I like to do all backups to the external sd card as there may come a time where you do a factory wipe... and poof its gone...
In the developement thread... there is a rom called Mapleleaf works very well on this phone... I run it myself with the googy-max3 kernel.
If you decide to flash anything else... make sure it will work for i337m, I have seen people get into trouble flashing things meant for the US version (i337). Our bootloader is unlocked so you don't need saftey strap or loki or other things that the i337 users need.
When in doubt... search the forum... if you find nothing... ask before you do anything strange.
As far as the bootloader goes... try to stay on your current one.. mine is still MK6. Once the bootloader is updated there is no going back... period.....
This helped a lot man, I appreciate it.
So just to clarify, can I use goo manager for the recovery or should I use Odin? And is there any version in particular [TWRP] that I should use? What version are you running?
How do I check my bootloader version?
Sent from my SGH-I337M using XDA Free mobile app
Bluntified said:
This helped a lot man, I appreciate it.
So just to clarify, can I use goo manager for the recovery or should I use Odin? And is there any version in particular [TWRP] that I should use? What version are you running?
How do I check my bootloader version?
Sent from my SGH-I337M using XDA Free mobile app
Click to expand...
Click to collapse
You can use goo manager or Odin. Just make sure you have the right version. FYI twrp 2.5.0.2 is the most reliable version that I have used for this device.
Tapatalked from California Custom Chrome M&M I337m
If you want an older version of twrp use odin... goomanager will likely try to load the latest version... as for checking which bootloader version you have, download the app phone info from the play store.... here... https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo&hl=en
my version of twrp is 2.6.3.1 and it works fine... as stated... 2.5 is also recommended by some of the devs....
My bootloader ends in NE1, does that pose a problem - I rarely see it mentioned anywhere? I took the OTA in case anyone is wondering. Basically, can I flash something that's not NE1?
Also, I've been reading that the ROM that's going to be flashed needs to be the same Android Version as the current one on the phone, is this still true?
Bluntified said:
My bootloader ends in NE1, does that pose a problem - I rarely see it mentioned anywhere? I took the OTA in case anyone is wondering. Basically, can I flash something that's not NE1?
Also, I've been reading that the ROM that's going to be flashed needs to be the same Android Version as the current one on the phone, is this still true?
Click to expand...
Click to collapse
This will mean you can flash any rom (for i337m) that is 4.4.2 version of android. You can always go up on android version to bootloader but you can't go down versions unless the bootloader is an earlier version. Since most roms are 4.4.2 or higher, I don't think this should be an issue, not many people are looking to go to an older version of android..... bigger... better and all that...
Gage_Hero said:
This will mean you can flash any rom (for i337m) that is 4.4.2 version of android. You can always go up on android version to bootloader but you can't go down versions unless the bootloader is an earlier version. Since most roms are 4.4.2 or higher, I don't think this should be an issue, not many people are looking to go to an older version of android..... bigger... better and all that...
Click to expand...
Click to collapse
Is this true, bc I have a bell galaxy 4, 4.4.2 i337m NE1 , I want to install a custom recovery,
but I thought my bootloader was locked because its says write protection enabled on the download screen which I thought
meant the bootloader was locked.
strakn said:
Is this true, bc I have a bell galaxy 4, 4.4.2 i337m NE1 , I want to install a custom recovery,
but I thought my bootloader was locked because its says write protection enabled on the download screen which I thought
meant the bootloader was locked.
Click to expand...
Click to collapse
The I337M bootloader is not locked. What you are seeing when you boot after rooting is that you tripped KNOX since new bootloaders are closely tied to KNOX so any violation = tripped KNOX.
I have I337M from Telus with NE1 bootloader (4.4.2) and custom Rom PhoeniX. Everything is great except a newly discovered TD Bank App and inability to link my TD Visa to it...
Just got my I337, using with simple mobile. Managed to sim unlock via this method, and was feeling pretty good. I think I had (have?) MK2. So using the stock ROM, it kept on asking to autoupdate. Didn't know if that would screw anything up, so attempted to install a kitkat venom ROM. I now can't get out of safestrap recovery. I'm not sure if the issue was trying to install a kitkat ROM, or if I mistakenly put it in the primary ROM slot. Anyway, I'm on a linux box without any immediate access to windows, so it looks like ODIN is out of the question. Been scouring the forums, but I have a few questions:
1. What are the limitations of the locked bootloader? Not really sure what I'm sidestepping by using a custom recovery. I had read that it limited me to TW ROMS (which is fine by me actually), but I see AOSP and other ROMs posted...
2. What exactly is meant by MK2, NC1, MF3, etc? I understand that they are progressions of SOMETHING, but not sure what--guessing it's the whole AT&T update, including ROM, modem, kernel? And I can't seem to find what exactly the progression is...
3. Is there a ROM that I should try to flash to get me back up and running before I start trying to screw with something else? Like I said, I have access to safestrap 2.71, adb, and an SD card, so I feel like this shouldn't be TOO hard to fix
nola mike said:
Just got my I337, using with simple mobile. Managed to sim unlock via this method, and was feeling pretty good. I think I had (have?) MK2. So using the stock ROM, it kept on asking to autoupdate. Didn't know if that would screw anything up, so attempted to install a kitkat venom ROM. I now can't get out of safestrap recovery. I'm not sure if the issue was trying to install a kitkat ROM, or if I mistakenly put it in the primary ROM slot. Anyway, I'm on a linux box without any immediate access to windows, so it looks like ODIN is out of the question. Been scouring the forums, but I have a few questions:
1. What are the limitations of the locked bootloader? Not really sure what I'm sidestepping by using a custom recovery. I had read that it limited me to TW ROMS (which is fine by me actually), but I see AOSP and other ROMs posted...
2. What exactly is meant by MK2, NC1, MF3, etc? I understand that they are progressions of SOMETHING, but not sure what--guessing it's the whole AT&T update, including ROM, modem, kernel? And I can't seem to find what exactly the progression is...
3. Is there a ROM that I should try to flash to get me back up and running before I start trying to screw with something else? Like I said, I have access to safestrap 2.71, adb, and an SD card, so I feel like this shouldn't be TOO hard to fix
Click to expand...
Click to collapse
Well, fixed my problem, though still don't have all the answers to my questions. I couldn't find a way to unbork without odin. Luckily my mom was in town visiting, and had a windows box that I used--I think I would have been hosed otherwise. Anyway, managed to revert to MK2 stock, and then upgrade to Goldeneye kit kat ROM via this method (my baseband is now listed as xxxxxxMLD).
I guess that MLD/NC1/NB1/MK2 are just ROM/radio firmware versions (kernel too, or is that completely unchangeable)? Still don't know the exact order of release, and if anyone could enlighten me a bit as to my other questions, I'd appreciate it...
I'll probably hold off on trying to change anything else until I have reliable access to windoze, unless someone can give me the steps using linux/adb.
nola mike said:
Well, fixed my problem, though still don't have all the answers to my questions. I couldn't find a way to unbork without odin. Luckily my mom was in town visiting, and had a windows box that I used--I think I would have been hosed otherwise. Anyway, managed to revert to MK2 stock, and then upgrade to Goldeneye kit kat ROM via this method (my baseband is now listed as xxxxxxMLD).
I guess that MLD/NC1/NB1/MK2 are just ROM/radio firmware versions (kernel too, or is that completely unchangeable)? Still don't know the exact order of release, and if anyone could enlighten me a bit as to my other questions, I'd appreciate it...
I'll probably hold off on trying to change anything else until I have reliable access to windoze, unless someone can give me the steps using linux/adb.
Click to expand...
Click to collapse
The order of firmware versions with Android version - MDB(4.2.x) -> MDL(4.2.x) - > MK2(4.3)->MLD(4.4 leak)->NB1(4.4.x)->NC1(4.4.x)
The bootloader for SGH-I337 was always locked.
1. This means that the stock kernel and recovery cannot be replaced.
2, The bootloader cannot be downgraded.
But, there was a bug in the first 2 releases, that loki exploited and provided a workaround for #1.
When flashing a firmware that contains the bootloader (aboot.mbn), it does a version check. The version check is through a fuse count maintained in the bootloader. MLD and MK2 although are different Android versions, have the same bootloader version. That means you can flash one over the other (go back and forth). The same with NB1 and NC1. But, once you update to NB1, you cannot go back to MK2.
Since the kernel cannot be replaced, all the ROMs we flash have to be compatible with the kernel that we have on the phone. Hence the mention of TW only ROMS. We cannot flash CM/AOSP/AOKP/GPE (most) ROMS. The AOSP ROMS you are seeing are themed TW roms only.
jmjoyas said:
The order of firmware versions with Android version - MDB(4.2.x) -> MDL(4.2.x) - > MK2(4.3)->MLD(4.4 leak)->NB1(4.4.x)->NC1(4.4.x)
The bootloader for SGH-I337 was always locked.
1. This means that the stock kernel and recovery cannot be replaced.
2, The bootloader cannot be downgraded.
But, there was a bug in the first 2 releases, that loki exploited and provided a workaround for #1.
When flashing a firmware that contains the bootloader (aboot.mbn), it does a version check. The version check is through a fuse count maintained in the bootloader. MLD and MK2 although are different Android versions, have the same bootloader version. That means you can flash one over the other (go back and forth). The same with NB1 and NC1. But, once you update to NB1, you cannot go back to MK2.
Since the kernel cannot be replaced, all the ROMs we flash have to be compatible with the kernel that we have on the phone. Hence the mention of TW only ROMS. We cannot flash CM/AOSP/AOKP/GPE (most) ROMS. The AOSP ROMS you are seeing are themed TW roms only.
Click to expand...
Click to collapse
Thanks for that, very enlightening.
nola mike said:
Thanks for that, very enlightening.
Click to expand...
Click to collapse
Just as an update, seems there's a workaround for Odin called heimdall, which is cross platform. . Haven't tried it, but looks like it should work.
I've been trying to figure this out for the last day, with no success.
I've got a rooted Note 3 N9005 (MJ7) stock. this is a 4.3 Rom. Knox status is0x0 (didn't trip it when I've rooted it ages ago).
I had enough of sammy rom, and I want to play with some of the new 4.4.4 custom roms.
I'm totally and utterly lost regarding what's tripping knox, and what are the needed steps in order to achieve that.
From what I understand, flashing TWRP (or any other custom recovery) will trip knox. I'm fine with that.
I'm not sure if I'm supposed to first upgrade my 4.3 to an official 4.4.2, and what / if is all the lock/unlock bootloader which seems to differ between versions (4.3 and 4.4). There also seem to be different versions of TWRP depending on if you're on 4.3 or 4.4?
Can I simply flash TWRP on my rooted 4.3, backup, flash new shinny 4.4.4 rom, and be happy ? Will that keep the root ?
Otherwise, do i need to upgrade to official 4.4.2 version first? will that lose root and I'll have to reroot the new version, and then flash TWRP and then flash 4.4.4 roms?
Any kind of help (or point me to an article that discusses it, even though I didn't find any, and i've searched) will be highly appreciated.
Cheers and thanks in advance.
_Noctis_ said:
I've been trying to figure this out for the last day, with no success.
I've got a rooted Note 3 N9005 (MJ7) stock. this is a 4.3 Rom. Knox status is0x0 (didn't trip it when I've rooted it ages ago).
I had enough of sammy rom, and I want to play with some of the new 4.4.4 custom roms.
I'm totally and utterly lost regarding what's tripping knox, and what are the needed steps in order to achieve that.
From what I understand, flashing TWRP (or any other custom recovery) will trip knox. I'm fine with that.
I'm not sure if I'm supposed to first upgrade my 4.3 to an official 4.4.2, and what / if is all the lock/unlock bootloader which seems to differ between versions (4.3 and 4.4). There also seem to be different versions of TWRP depending on if you're on 4.3 or 4.4?
Can I simply flash TWRP on my rooted 4.3, backup, flash new shinny 4.4.4 rom, and be happy ? Will that keep the root ?
Otherwise, do i need to upgrade to official 4.4.2 version first? will that lose root and I'll have to reroot the new version, and then flash TWRP and then flash 4.4.4 roms?
Any kind of help (or point me to an article that discusses it, even though I didn't find any, and i've searched) will be highly appreciated.
Cheers and thanks in advance.
Click to expand...
Click to collapse
If you aren't concerned about KNOX, upgrade to a 4.4 ROM (Official) via ODIN which will upgrade the bootloader, then once that's all done, flash TWRP for 4.4 then download your ROMs and flash via TWRP as normal.
radicalisto said:
If you aren't concerned about KNOX, upgrade to a 4.4 ROM (Official) via ODIN which will upgrade the bootloader, then once that's all done, flash TWRP for 4.4 then download your ROMs and flash via TWRP as normal.
Click to expand...
Click to collapse
Not concerned any more ...
Out of curiosity, what exactly kills the root? flashing a rom doesn't. upgrading via odin ? I'm assuming it has nothing to do with the system/cache, since each flash usually wipes them, so, where does it live?
Cheers
_Noctis_ said:
Not concerned any more ...
Out of curiosity, what exactly kills the root? flashing a rom doesn't. upgrading via odin ? I'm assuming it has nothing to do with the system/cache, since each flash usually wipes them, so, where does it live?
Cheers
Click to expand...
Click to collapse
Reflashing the ROM back to stock is what kills root. It's easy to re-root again once you've tripped KNOX anyways.
But tbh, once you install a custom recovery after you've upgraded your boot loader, you won't need to root. It isn't required for custom recovery
Sent from my Spectrum ZX +2
EDIT: Have you used ODIN to flash stock images before? If not, have a read around, it's pretty straight forward though.
radicalisto said:
Reflashing the ROM back to stock is what kills root. It's easy to re-root again once you've tripped KNOX anyways.
But tbh, once you install a custom recovery after you've upgraded your boot loader, you won't need to root. It isn't required for custom recovery
Sent from my Spectrum ZX +2
EDIT: Have you used ODIN to flash stock images before? If not, have a read around, it's pretty straight forward though.
Click to expand...
Click to collapse
I see ... so -> flash stock (kills root) -> flash TWRP (trips knox) -> flash custom rom without worrying about root ? (wouldn't i need it for titanium backup ,or do custom roms come with SU preinstalled?)
Yep, used odin. file on comp, download mode, couple of ticks, clicky clicky, happiness ensues ...
Yeah you're pretty much spot on. Yeah most ROMs are pre-rooted and if they aren't you can just flash superSU via your recovery. But you should be good to go and know what you're doing by the sounds of it.
Enjoy flashing them ROMs and make an efs backup and store off the device too. There's an adb script for it here (forget where but its here, development thread I think) don't use any apps from the play store as they are notorious for bricking Samsung devices.
Sent from my Spectrum ZX +2
radicalisto said:
Yeah you're pretty much spot on. Yeah most ROMs are pre-rooted and if they aren't you can just flash superSU via your recovery. But you should be good to go and know what you're doing by the sounds of it.
Enjoy flashing them ROMs and make an efs backup and store off the device too. There's an adb script for it here (forget where but its here, development thread I think) don't use any apps from the play store as they are notorious for bricking Samsung devices.
Sent from my Spectrum ZX +2
Click to expand...
Click to collapse
lol ...notorious for bricking samsung devices ... i like it ...
i ran one already (zipped a 6MB and a 14.5MB image and tar into a 300kb zip), and been told you can do that from inside TWRP as well ...
I'll take a deep breath, and start downloading the official image and roms ...
I'll update if i'll get to the other side
out of curiosity ... does it matter which official 4.4.2 image i'm flashing ? (i'm getting the NZ one ...but i assume they should all be similar, and / or that it doesn't matter since i'll be flashing something else on it anyways, right ?
_Noctis_ said:
out of curiosity ... does it matter which official 4.4.2 image i'm flashing ? (i'm getting the NZ one ...but i assume they should all be similar, and / or that it doesn't matter since i'll be flashing something else on it anyways, right ?
Click to expand...
Click to collapse
Yeah try and keep to the country your device is from, otherwise you have to find the right PIT file, and the partitions vary etc
radicalisto said:
Yeah try and keep to the country your device is from, otherwise you have to find the right PIT file, and the partitions vary etc
Click to expand...
Click to collapse
Rubbish. ..I don't recall seeing an australian one... I'll have another look, otherwise ill look into the pit thingy. Thanks.
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?