Related
Hey guys, I've done a lot of searching in this forum and found a lot of conflicting answers, so decided to start a fresh thread. I've been on 4.2.2/MF3 for a while now running Safetrap. I'm looking to take the OTA from AT&T and upgrade to 4.3.
I havent seen any root methods for 4.3 yet, but the question is, can I upgrade to 4.3 and retain root if I am running the latest version of SuperSU Pro with survival mode enabled?
A custom recovery with the option for installing ROMs is not needed, especially since I havent been able to do that since I updated to MF3. All I need is to keep root under 4.3 and I'll be more than happy, thanks!
kevinco1 said:
Hey guys, I've done a lot of searching in this forum and found a lot of conflicting answers, so decided to start a fresh thread. I've been on 4.2.2/MF3 for a while now running Safetrap. I'm looking to take the OTA from AT&T and upgrade to 4.3.
I havent seen any root methods for 4.3 yet, but the question is, can I upgrade to 4.3 and retain root if I am running the latest version of SuperSU Pro with survival mode enabled?
A custom recovery with the option for installing ROMs is not needed, especially since I havent been able to do that since I updated to MF3. All I need is to keep root under 4.3 and I'll be more than happy, thanks!
Click to expand...
Click to collapse
This is my exact question. I just need some concrete answer as to yes or no... but as you said way too many conflicting answers!
YES.
I used "Survival mode" and it worked for me.
ROOTED ATT MK2 using Tapatalk
Hi so there is a way to update stock to 4.3 and continue using safestrap to run 4.2.2 roms????I would doubt that with what Ive read so far.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
jball said:
YES.
I used "Survival mode" and it worked for me.
Click to expand...
Click to collapse
I too can confirm this works using Survival Mode from SuperSU Pro (https://play.google.com/store/apps/details?id=eu.chainfire.supersu.pro&hl=en).
Now, that being said, being a very big noob myself (switching over from heavily tweaked jailbroken iPhone 5), I did this, all was well, I thought I had some issues with some apps and thought 'hmm... maybe I'll just downgrade to MF3 and see if the problem is fixed'. Yeah, attempting to do that with Odin has left me soft-bricked, but for all intents and purposes (that I can tell) it's actually hard-bricked 'cause Kies did nothing, Odin does nothing, if I understand things correctly the only thing that could possibly help is if we had the MD5's available to us for MK2, which, my searching is coming up empty. So, point is according to what I can tell, if you go MK2, there is NO going back to 4.2.2, so use caution.
So just an important safety tip there (unless someone wants to correct my noobness).
Yes. I can confirm that enabling "survival mode" in SuperSU and updating will keep your root; i did this on my pphone coming from MF3.
However, with that being said, i quickly unrooted from there because i had issues with MMS/messaging and phone calls not being recieved, and i did not want to reset my phone. If you run into similar issues as i am not the only one reporting those issues you can so a reset on your data (your root will not be affected, you will be rooted after the reset) or an unroot will work.
happy updating
kevinco1 said:
Hey guys, I've done a lot of searching in this forum and found a lot of conflicting answers, so decided to start a fresh thread. I've been on 4.2.2/MF3 for a while now running Safetrap. I'm looking to take the OTA from AT&T and upgrade to 4.3.
I havent seen any root methods for 4.3 yet, but the question is, can I upgrade to 4.3 and retain root if I am running the latest version of SuperSU Pro with survival mode enabled?
A custom recovery with the option for installing ROMs is not needed, especially since I havent been able to do that since I updated to MF3. All I need is to keep root under 4.3 and I'll be more than happy, thanks!
Click to expand...
Click to collapse
First with Safestrap you CAN flash Roms. It is just limited to about 10 or so Roms that will work as they need to be 4.2.2 based.
Now with that said for those that ONLY want root on MK2 then someone in the Verizon thread has a WORKING ROOT available for MK2 4.3 firmware here http://forum.xda-developers.com/showthread.php?t=2565758 and it DOESN'T come with the maliscious code that Kango and VRoot does. This DOES NOT give you recovery but it does give root. So thank the OP in that thread for helping out the community. I did and I HOPE I will never need to use it!!!
Good luck and Happy Rooting...
Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337
Hey guys. I want to get to 4.4.2 but I'm currently on 4.2. I have root and a custom recovery, and my OTA updates are failing a verification check. The OTA is trying to update to 4.3.
Is there a zip I can flash to go to 4.4.2 without having to wipe my phone? Or do I need to flash in order? Or is my only option wiping everything and flashing stock (how would I do that)? If that's the case I'll probably just stick with 4.2. I want to skip right over 4.3 because that was a buggy mess for me that ultimately resulted in terrible battery life and broken apps. But I've heard good things about 4.4.2
bump..
Sounds like you want a flashable stock 4.2.2 build, right? Haven't tried it myself, but it seems this thread is where you want to look.
Use this : http://forum.xda-developers.com/showthread.php?t=2566042
It's a flashable zip of the 4.4.2 Stock ROM, only zipaligned (doesn't cause problems in OTA). Flash it through TWRP, and you're done. Good luck!
bruinhoo said:
Sounds like you want a flashable stock 4.2.2 build, right? Haven't tried it myself, but it seems this thread is where you want to look.
Click to expand...
Click to collapse
That's not quite what I was looking for but thank you for the answer.
Lt.Win said:
Use this : http://forum.xda-developers.com/showthread.php?t=2566042
It's a flashable zip of the 4.4.2 Stock ROM, only zipaligned (doesn't cause problems in OTA). Flash it through TWRP, and you're done. Good luck!
Click to expand...
Click to collapse
That's what I wanted! Thanks much, seems to be working great. Loving everything but the white phone app and I dislike Hangouts. Thanks much. :]
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.
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.