Related
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
4.2.2 / MDL here. I'm rooted to freeze the metric ton of bloatware/greenify/xposed. Didn't get into ROMs because I'm afraid of bricking my only phone.
Been sidelined for several months with health issues, wondering if there's been any new stuff down the pipeline or if I should stay at 4.2.2/MDL? TIA.
Sliced bread has come out. Jk, given the time taken for someone to answer you, nothing new has come out that's earth shaking. Other than new firmware. If everything works for you it probably isn't worth upgrading.
You're on mdl which allows you to flash a number of different roms which you aren't taking advantage of. The latest firmware, nc1, is rootable with towel root. You can flash touch wiz based roms but that doesn't seem to be an interest to you So you might consider updating to nc1 if you want the latest firmware. But many people would like to be in your shoes with mdl firmware.
Sent from my Nexus 5 using XDA Free mobile app
If you have root and custom recovery (TWRP or CWM) and want to update to newer firmware I would suggest Sho-Stock-i V7.0 Then you w I uld have the newest firmware without having to use Safestrap and be limited to what you can do with your phone.
I would STAY AWAY from updating to the newest firmware (stock firmware) NC1 as right now you can do ANYTHING you want with your phone. That is why I suggested ShoStock to have the best of both worlds. Personally there is NOT MUCH different between your MDL 4.2.2 firmware and the newest 4.4.2 firmwares. Maybe a little smoother.
Sent From My ATT S3 i747 Dark Blue BadAss Theme
Would reception be better with 4.4.2? We recently took a road trip and on a very long stretch my hubby on 4.4.2 had coverage the whole time while I had 0 service for about 1/2 of the stretch. Other areas he was pulling data fine while my phone showed no service or a G and up and down arrows which was completely new to me. It's bizarre.
RockRatt said:
If you have root and custom recovery (TWRP or CWM) and want to update to newer firmware I would suggest Sho-Stock-i V7.0 Then you w I uld have the newest firmware without having to use Safestrap and be limited to what you can do with your phone.
I would STAY AWAY from updating to the newest firmware (stock firmware) NC1 as right now you can do ANYTHING you want with your phone. That is why I suggested ShoStock to have the best of both worlds. Personally there is NOT MUCH different between your MDL 4.2.2 firmware and the newest 4.4.2 firmwares. Maybe a little smoother.
Sent From My ATT S3 i747 Dark Blue BadAss Theme
Click to expand...
Click to collapse
I don't think I have recovery? I only remember rooting, no option for twrp or cwm. Am I hosed now?
Wittyusernametaken said:
I don't think I have recovery? I only remember rooting, no option for twrp or cwm. Am I hosed now?
Click to expand...
Click to collapse
If you are still in fact on MDL then you can get TWRP or CWM recovery and flash as I stated above. You can use ShoStock-i once you have a custom recovery. First VERIFY you have MDL bootloaders. Then if you do look into "Motochopper +Loki" which will give you the custom recovery. Then flash to ShoStock-i. Then you can flash any of the modems in my thread to find which works best for your phone in your area. Maybe see which "baseband" (baseband=Modem) your husbands phone has (if it is also a i337 S4).
Sent fron I337 Red BadAss Themed ShoStock 7.0
do you have a link for the Sho-Stock-i V7.0? I can't find it? Also would any version of CyanogenMod work? I can't find one that would work without me upgrading to 4.4 if my google searches are correct. Sorry for the delay in replying... health issues are a PITA.
Wittyusernametaken said:
do you have a link for the Sho-Stock-i V7.0? I can't find it? Also would any version of CyanogenMod work? I can't find one that would work without me upgrading to 4.4 if my google searches are correct. Sorry for the delay in replying... health issues are a PITA.
Click to expand...
Click to collapse
You do NOT need to update to run ShoStock. Just flash his newest in recovery (TWRP/ cwm/etc.) It will give you the newer firmware of 4.4.2 but NOT give you the 4.4.2 bootloader. So you can always flash back to your MDL stock firmware via odin. Like I said, the best of both worlds. Keeping the bypassed bootloader while running newer firmware. Just use ShoStock 8.1 (NOT THE SAFESTRAP VERSION)
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.
Greetings! Im new to the rooting scene and i have a rooted note 3 on 4.3. I would like to know if it is better to install the ota update then root again or just flash a new rom that is kitkat already.
Thanks in advance.
beefy314 said:
Greetings! Im new to the rooting scene and i have a rooted note 3 on 4.3. I would like to know if it is better to install the ota update then root again or just flash a new rom that is kitkat already.
Thanks in advance.
Click to expand...
Click to collapse
You cannot OTA update since you have rooted. You can only download stock firmware and flash via Odin. And yes, you have to root again, also via Odin.
A new (custom) rom is another option, I have no idea with it.
For the time being, I would browse the Note 3 Android Development forum and see if a custom ROM is what you want. If it is, then by all means go ahead and flash one. If not, then upgrading to 4.4.2 and rooting is the best bet. Personally, I was on stock 4.4.2 rooted, and it didn't take long for me to flash a custom ROM. I'm on my third custom ROM in a month, so it can definitely get addicting.
You can update via OTA.
Thereafter, flash the old kernel xxund3.
root via towel root, and reflash the Kernel that came with the OTA update.
All via Odin. I don't think there's any way to do it, yet, and at the same time keeping knox 0x0.
link is here: http://forum.xda-developers.com/galaxy-note-3/general/root-root-xxufnf4-stock-firmware-knox-t2840150
Cheers!
After rooting my Note 3 (not branded or simlocked) many moons ago with Towelroot, I've come to the point of wanting to update things a tad. I never installed a custom recovery so it's just a root.
However, looking through the multiple threads here and not wishing to make a bad mistake I'm a little confused and could do with some clear pointers.
I am currently on 4.3 Jellybean BL: N900XXUBMJ3 so most threads deal with later versions and I really want to know what the best path is to now being able to start trying out custom roms such as the DarkWolf ROM or just get this to Lollipop. Obviously now Knox 1x0 is no longer a problem as it's out of warranty.
I assume that the step should really be to install a custom recovery and for that there is a confusion of whether I can do that directly on my current bootloader or do I have install 4.4.2 as some threads suggest?
Probably due to my misunderstanding I am not sure if a 4.4 bootloader is separate from the firmware. If it comes to having to update the bootloader do I have to completely upgrade to Kitkat or can I just update the bootloader only?
louiscar said:
After rooting my Note 3 (not branded or simlocked) many moons ago with Towelroot, I've come to the point of wanting to update things a tad. I never installed a custom recovery so it's just a root.
However, looking through the multiple threads here and not wishing to make a bad mistake I'm a little confused and could do with some clear pointers.
I am currently on 4.3 Jellybean BL: N900XXUBMJ3 so most threads deal with later versions and I really want to know what the best path is to now being able to start trying out custom roms such as the DarkWolf ROM or just get this to Lollipop. Obviously now Knox 1x0 is no longer a problem as it's out of warranty.
I assume that the step should really be to install a custom recovery and for that there is a confusion of whether I can do that directly on my current bootloader or do I have install 4.4.2 as some threads suggest?
Probably due to my misunderstanding I am not sure if a 4.4 bootloader is separate from the firmware. If it comes to having to update the bootloader do I have to completely upgrade to Kitkat or can I just update the bootloader only?
Click to expand...
Click to collapse
You can flash custom recovery for 4.3 but all 5.1.1 and 6.0 roms require 5.0 bootloader to make the camera to work correctly.
Flash 4.3 custom recovery. Then flash the rom of your choice. Then flash 5.0 bootloader. After that flash 4.4.2/5.0 recovery.
Or flash 5.0 firmware. Flash 4.4.2/5.0 custom recovery. Flash the rom of your choice.
Sent from my SM-G925F using XDA Free mobile app
Rosli59564 said:
You can flash custom recovery for 4.3 but all 5.1.1 and 6.0 roms require 5.0 bootloader to make the camera to work correctly.
Flash 4.3 custom recovery. Then flash the rom of your choice. Then flash 5.0 bootloader. After that flash 4.4.2/5.0 recovery.
Or flash 5.0 firmware. Flash 4.4.2/5.0 custom recovery. Flash the rom of your choice.
Sent from my SM-G925F using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for that Rosli,
I actually found that OTA was working still so I let it update. This went through a lot of updates one by one till it got to the latest 4.3. All this left root intact. Then it downloaded the kitkat but that failed. I had figured that if I let it update to Lollipop I could then root it with CF Autoroot but as it's not going any further (probably due to the fact that I'm rooted .. maybe), I will have to manually update via Odin.
I would probably in that case prefer your advice of flashing 5.0 directly then custom recovery, however, do I have to CF autoroot or can I flash recovery without root and then root after that?
louiscar said:
Thanks for that Rosli,
I actually found that OTA was working still so I let it update. This went through a lot of updates one by one till it got to the latest 4.3. All this left root intact. Then it downloaded the kitkat but that failed. I had figured that if I let it update to Lollipop I could then root it with CF Autoroot but as it's not going any further (probably due to the fact that I'm rooted .. maybe), I will have to manually update via Odin.
I would probably in that case prefer your advice of flashing 5.0 directly then custom recovery, however, do I have to CF autoroot or can I flash recovery without root and then root after that?
Click to expand...
Click to collapse
Can flash custom recovery then root. But if you're going to flash custom rom no need to root after custom recovery.
Sent from my SM-G925F