Related
I've been tinkering with my AT&T GS4 (build MK2) and I had a hard time finding good root and flash methods. I eventually rooted with SafeRoot, and then started doing my research. After a lot of unsuccessful messing around with ROM Installer and GooManager, I tried flashing CWM through GooManager, but apparently I messed it up because now I can only boot into Download Mode. I thought my phone was bricked, but I figured out how to reboot.
My current status is that I am still running MK2, I'm still rooted, and I have not been able to access recovery mode because I just get the "Warning! Do not turn off target!!" screen with the text below:
Could not do normal boot.
ODIN MODE
PRODUCT NAME: SGH-I337
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNAL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE enabled​
I would like to flash a new recovery (or at least reset to the stock recovery) so that I can flash CyanogenMod. Alternatively, I'm wondering if this issue will preclude me from flashing a custom ROM through Odin. If not, I'll need an Odin compatible CyanogenMod ROM (.tar, I believe) but I haven't been able to track one down. Has anyone run into this problem before? Now that I have some idea about how this whole process works, is there an "approved solution" for installing custom ROMs on the MK2? According to galaxys4root.com, I shouldn't try to use Odin to flash CWM since it's the AT&T model.
Thanks in advance!
go4bacon said:
I've been tinkering with my AT&T GS4 (build MK2) and I had a hard time finding good root and flash methods. I eventually rooted with SafeRoot, and then started doing my research. After a lot of unsuccessful messing around with ROM Installer and GooManager, I tried flashing CWM through GooManager, but apparently I messed it up because now I can only boot into Download Mode. I thought my phone was bricked, but I figured out how to reboot.
My current status is that I am still running MK2, I'm still rooted, and I have not been able to access recovery mode because I just get the "Warning! Do not turn off target!!" screen with the text below:
Could not do normal boot.
ODIN MODE
PRODUCT NAME: SGH-I337
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNAL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE enabled​
I would like to flash a new recovery (or at least reset to the stock recovery) so that I can flash CyanogenMod. Alternatively, I'm wondering if this issue will preclude me from flashing a custom ROM through Odin. If not, I'll need an Odin compatible CyanogenMod ROM (.tar, I believe) but I haven't been able to track one down. Has anyone run into this problem before? Now that I have some idea about how this whole process works, is there an "approved solution" for installing custom ROMs on the MK2? According to galaxys4root.com, I shouldn't try to use Odin to flash CWM since it's the AT&T model.
Thanks in advance!
Click to expand...
Click to collapse
The only thing you can use with AT&T MK2 is the latest version of Safestrap (there is a couple of threads about it).
go4bacon said:
I've been tinkering with my AT&T GS4 (build MK2) and I had a hard time finding good root and flash methods. I eventually rooted with SafeRoot, and then started doing my research. After a lot of unsuccessful messing around with ROM Installer and GooManager, I tried flashing CWM through GooManager, but apparently I messed it up because now I can only boot into Download Mode. I thought my phone was bricked, but I figured out how to reboot.
My current status is that I am still running MK2, I'm still rooted, and I have not been able to access recovery mode because I just get the "Warning! Do not turn off target!!" screen with the text below:
Could not do normal boot.
ODIN MODE
PRODUCT NAME: SGH-I337
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNAL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE enabled​
I would like to flash a new recovery (or at least reset to the stock recovery) so that I can flash CyanogenMod. Alternatively, I'm wondering if this issue will preclude me from flashing a custom ROM through Odin. If not, I'll need an Odin compatible CyanogenMod ROM (.tar, I believe) but I haven't been able to track one down. Has anyone run into this problem before? Now that I have some idea about how this whole process works, is there an "approved solution" for installing custom ROMs on the MK2? According to galaxys4root.com, I shouldn't try to use Odin to flash CWM since it's the AT&T model.
Thanks in advance!
Click to expand...
Click to collapse
MK2 firmware ONLY with SAFESTRAP . RECOVERY AND TW ROM ONLY....NO GPE, CM, AOKP, AOSP......try flashing i337MK2stockrecovery.tar.md5 from my thread >>>POST #3<<<..........Hope this help ........GOODLUCK. ........PLEASE DO SOME READING.....AND HIT THANK IF I HELPED U......
Swyped from MK2 Deadly Venom SS
This is EXACTLY why people need to read before they do anything. I miss the old XDA days -.-
Sent from my SGH-I337 using Tapatalk
ted77usa said:
MK2 firmware ONLY with SAFESTRAP . RECOVERY AND TW ROM ONLY....NO GPE, CM, AOKP, AOSP......try flashing i337MK2stockrecovery.tar.md5 from my thread >>>POST #3<<<..........Hope this help ........GOODLUCK. ........PLEASE DO SOME READING.....AND HIT THANK IF I HELPED U......
Swyped from MK2 Deadly Venom SS
Click to expand...
Click to collapse
Understood, so in what order would I proceed? Would I have to flash i337MK2stockrecovery.tar.md5 before flashing the stock ROM? Before I received any replies to this thread last night, I attempted to flash the Stock ROM through Odin, but received a "fail" notification.
Alternatively, is there any way I can revert to an older build?
toxicpaulution said:
This is EXACTLY why people need to read before they do anything. I miss the old XDA days -.-
Sent from my SGH-I337 using Tapatalk
Click to expand...
Click to collapse
I tried to read up before I started messing with my phone, but the jargon was so daunting that I couldn't figure out where to start. Recovery, ROM, bootloaders, flash...it was all greek to me until I started learning through failure! If I can flash the stock recovery, perhaps I can "unroot" and do things correctly next time around.
go4bacon said:
Understood, so in what order would I proceed? Would I have to flash i337MK2stockrecovery.tar.md5 before flashing the stock ROM? Before I received any replies to this thread last night, I attempted to flash the Stock ROM through Odin, but received a "fail" notification.
Alternatively, is there any way I can revert to an older build?
Click to expand...
Click to collapse
Follow the thread on post# 3 that iposted earlier for unbricked method it should get your phone back to mk2. ... goodluck. .... and make sure u got all the mf3 emergency files and download MF3>MK2 update.zip files from OP Cox u gonna need it in the end. ... .. READ THE GUIDE ALL THE WAY AND MAKE SURE THAT U UNDERSTAND. .... BEFORE U DO ANYTHING. ..... GOODLUCK. ....PM ME IF U NEED MORE HELP. ....
Swyped from MK2 Deadly Venom SS
go4bacon said:
I tried to read up before I started messing with my phone, but the jargon was so daunting that I couldn't figure out where to start. Recovery, ROM, bootloaders, flash...it was all greek to me until I started learning through failure! If I can flash the stock recovery, perhaps I can "unroot" and do things correctly next time around.
Click to expand...
Click to collapse
If you don't understand what you are reading or trying to do, why are you still trying to do it anyway? I can tell you that you are not reading enough.
scott14719 said:
If you don't understand what you are reading or trying to do, why are you still trying to do it anyway? I can tell you that you are not reading enough.
Click to expand...
Click to collapse
We were all guilty of not reading enough at some point or the other
http://forum.xda-developers.com/showthread.php?t=1408581
Go4bacon: Read this thread and make sure it makes a bit more sense.
http://forum.xda-developers.com/showthread.php?t=2314494
The only reason most gripe at people is because they know how easily you can brick a device using the "trial by fire" methods to learn.
scott14719 said:
If you don't understand what you are reading or trying to do, why are you still trying to do it anyway? I can tell you that you are not reading enough.
Click to expand...
Click to collapse
I agree with you, I want to know the exact reason why he wants to boot a custom rom, I have seen way to many peopledo it to be "cool" and then brick their device >.>
toxicpaulution said:
I agree with you, I want to know the exact reason why he wants to boot a custom rom, I have seen way to many peopledo it to be "cool" and then brick their device >.>
Click to expand...
Click to collapse
yay...the q&a police strike again.
remember this ?
http://forum.xda-developers.com/showthread.php?t=1368747
hednik said:
We were all guilty of not reading enough at some point or the other
http://forum.xda-developers.com/showthread.php?t=1408581
Click to expand...
Click to collapse
That is clearly one of the most ignorant things I have seen on this site. You went back 2 years to find a post about another phone that had questions that I asked that had not yet been answered and decided to post it in this thread? If you actually took the time to look through that old thread, you would see that I answered the previously unanswered question myself and posted the info so others could benefit. It had absolutely nothing to do with lack of searching and / or reading comprehension. If you have nothing better to do than dig up 2 year old posts that have absolutely nothing to do with the subject of this post, move on.
scott14719 said:
That is clearly one of the most ignorant things I have seen on this site. You went back 2 years to find a post about another phone that had questions that I asked that had not yet been answered and decided to post it in this thread? If you actually took the time to look through that old thread, you would see that I answered the previously unanswered question myself and posted the info so others could benefit. It had absolutely nothing to do with lack of searching and / or reading comprehension. If you have nothing better to do than dig up 2 year old posts that have absolutely nothing to do with the subject of this post, move on.
Click to expand...
Click to collapse
Its just every response you have is arrogant to any question someone asks you feel is beneath you. If you don't like questions don't come into q&a. Treating people in here with loathsome arrogance only serves to stroke your ego.
And it took 30 seconds to find your first thread.
We all ask stuff we could have searched for, even you. I ask stuff that might be obvious too.
Sent from my SGH-I337 using XDA Premium 4 mobile app
hednik said:
Its just every response you have is arrogant to any question someone asks you feel is beneath you. If you don't like questions don't come into q&a. Treating people in here with loathsome arrogance only serves to stroke your ego.
And it took 30 seconds to find your first thread.
We all ask stuff we could have searched for, even you. I ask stuff that might be obvious too.
Sent from my SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Telling people to search and read is not arrogance. Asking people why they do things that they don't understand is not arrogance. As any Moderator will tell you, this is not a "support" forum it is a development forum. There is no reason why someone needs to ask questions that have been answered dozens of times. And then after being told the answers already exist, turn around and continue to not read and learn.
Why do you have such a problem with this forum and the rules? The thing is, you are no different than the OP, and me telling the OP that they need to read and learn about their device means that you too, must put a little effort into learning. And that is why you (and others like you) really have a problem with me. It is not rude or arrogant to let people know they are going about things the wrong way by not learning and reading (and doing so until they understand what they are reading). Telling someone they need to read and learn about their device before they screw it up further is ALWAYS the correct answer especially if it is a topic that has been covered several times already. If you or any one else has an issue with that...tough.
YOU:
"Hey guys, I never bothered learning how to drive, but decided to jump behind the wheel anyway...now I'm wrapped around a tree. What should I have done differently?"
ME:
"You should have learned how to drive before getting behind the wheel, why didn't you?"
YOU:
"You're arrogant!"
Really?
Anyway back on topic.
OP, you need to read the "pinned" threads in the general and Q&A section and follow the links in those threads for your specific model and firmware until you completely understand what to do and how to do it. The answers and information you need are in those threads, it is up to you to make use of it or not.
I just think its best to think how other's might view your responses as opposed to being arrogant. I'm just saying that if everyone responded with how you do it would be a sad place to learn. That's what this place is for. Learning... Bottom line. Yes you can correct but it should be done with tact and understanding. BTW your example did not apply to said situation.
Sent from my SGH-I337 using XDA Premium 4 mobile app
I know this is probably been asked 100 times already, but while I've found a lot of comprehensive guides about rooting the Nexus 7 I can't find the same thing for the S4. I'm going to buy one soon, and since I'm in italy it should be the GT-I9505 version.
I want to root the telephone, install a custom rom (I don't know which one, I'll have to check later) and be able to revert to the stock settings/rom so that I can avoid to void the warranty. Every guide I checked used a different software, or was specifically about the AT&T or Verizon model, or just didn't include how to do all the things aforementioned, so please, someone link me the best guides on rooting the S4 and being able to revert the telephone to stock settings (I imagine installing custom roms has specific guides for every rom, so no need for that).
Really, really thanks to anyone who answers.
Hi..
http://forum.xda-developers.com/showthread.php?t=2419762
AnaMajhol said:
Hi..
http://forum.xda-developers.com/showthread.php?t=2419762
Click to expand...
Click to collapse
Thanks but I read the FAQ already, that's partially why I felt stupid opening this thread, not even the noob-friendly FAQ answered everything.
So, I use chainfire auto-root to root the device, and then with Odin I can eventually unroot it in case I need the warranty?
Soory for the double post, but I need new answers about this topic.
I'll use CF auto root to root the device, but this trips the knox flag and nullifies warranty. How do I avoid that? I heard of a Triangle awayy app which resets the Triangle Counter or something like that and I don't think it's the same thing. How do I root while keeping my warranty?
Also, how is the app which reverts the device custom rom to the stock rom called? I always hear different names, it's a bootloader, or recovery mode or now another thing all together, I just need to eventually revert the custom rom to the original rom in order to avoid breaking the warranty if possible.
Last question, feel free to disregard this one because I can search it somewhere else: if I use a custom rom, how do I keep up to date with the official Android builds/functions? Ie, 4.5 comes out and I have Cyanogen, do I have to wait for a new Cyanogen update which brings the Android 4.5 features or am I missing the point entirely?
Again, thanks.
cloudropis said:
Soory for the double post, but I need new answers about this topic.
I'll use CF auto root to root the device, but this trips the knox flag and nullifies warranty. How do I avoid that? I heard of a Triangle awayy app which resets the Triangle Counter or something like that and I don't think it's the same thing. How do I root while keeping my warranty?
Also, how is the app which reverts the device custom rom to the stock rom called? I always hear different names, it's a bootloader, or recovery mode or now another thing all together, I just need to eventually revert the custom rom to the original rom in order to avoid breaking the warranty if possible.
Last question, feel free to disregard this one because I can search it somewhere else: if I use a custom rom, how do I keep up to date with the official Android builds/functions? Ie, 4.5 comes out and I have Cyanogen, do I have to wait for a new Cyanogen update which brings the Android 4.5 features or am I missing the point entirely?
Again, thanks.
Click to expand...
Click to collapse
You don't avoid tripping the knox flag. And you can't reset it. If your phone has Knox and you want to root it, you have to trip the knox flag. Period.
Here is everything you could possibly ever want to know about Knox.
http://forum.xda-developers.com/showthread.php?t=2470635
And yes, you have to keep updating the custom roms to get the latest features. Odds are VERY strong that the custom roms will have the updates before the carrier based ROMs OTA's come out.
Skipjacks said:
You don't avoid tripping the knox flag. And you can't reset it. If your phone has Knox and you want to root it, you have to trip the knox flag. Period.
Here is everything you could possibly ever want to know about Knox.
http://forum.xda-developers.com/showthread.php?t=2470635
And yes, you have to keep updating the custom roms to get the latest features. Odds are VERY strong that the custom roms will have the updates before the carrier based ROMs OTA's come out.
Click to expand...
Click to collapse
Got it. So a lot of people still root their phones even if it voids their warranty huh? I guess that the benefits must be greater then the cons (for one, being able to use my Dualshock 3 without cables is way enough, maybe the eventual repair centre won't notice, or maybe I'll just keep a freaking eye on my phone).
Again, I couldn't find an answer in the Rooting thread's first post, so to be safe rather than sorry I'll ask here: The device update is ready, it upgrades Android to 4.4.2 (currently 4.3, but if I got it right the KB shouldn't give me problems because I am not changing rom), does CF autoroot work anyway? Knox flag or not? I dropped the idea of using a custom rom, so I just need to know if I can still root it with CF.
cloudropis said:
Got it. So a lot of people still root their phones even if it voids their warranty huh? I guess that the benefits must be greater then the cons (for one, being able to use my Dualshock 3 without cables is way enough, maybe the eventual repair centre won't notice, or maybe I'll just keep a freaking eye on my phone).
Again, I couldn't find an answer in the Rooting thread's first post, so to be safe rather than sorry I'll ask here: The device update is ready, it upgrades Android to 4.4.2 (currently 4.3, but if I got it right the KB shouldn't give me problems because I am not changing rom), does CF autoroot work anyway? Knox flag or not? I dropped the idea of using a custom rom, so I just need to know if I can still root it with CF.
Click to expand...
Click to collapse
It strongly depends on which part of the world you live.
In the EU the store you bought it from still has to fix it. Samsung in the Netherlands has stated that rooted phones etc will still have warranty.
Lennyz1988 said:
It strongly depends on which part of the world you live.
In the EU the store you bought it from still has to fix it. Samsung in the Netherlands has stated that rooted phones etc will still have warranty.
Click to expand...
Click to collapse
I live in italy and I highly doubt warranty is intact after rooting, so heh.
In case someone missed it, this is the last question before I'm satisfied and can let this thread be closed: if I do the official update which brings the device's Android version to 4.4.2, can I still root it? I'm not saying the upgraded Android is a problem, I'm just asking if that specific update perhaps brought some security changes or something which don't allow rooting or make it harder.
Sorry but I'm bumping again I really need this.
Bump again
You can root it.
I just had to replace my S4 because I broke the screen on my old one. Unfortunately, the new one was shipped to me with NAE firmware and boot loader already installed. This means I'm already on KNOX from the first second of turning it on.
I have seen plenty of guides on how to update to NAE, and get root, etc. by not allowing KNOX to installed. However, I haven't really seen anything about what can be done if it's already installed. There's things scattered all over the net that suggest there might be ways around this, but nothing on the forums here that I have been able to find yet.
I'm not looking to flash any crazy roms or anything right now, I really just want root, but it seems like even that might be impossible now. Could I use something like "DrKetan Multitool" to "DeKNOX" my device and then root it? Does this tool even work on the S4, he claims it does but I've not seen it mentioned on the actual S4 forums. Any advice would be greatly appreciated. Note, I am looking for a method that doesn't trip the flash counter; or at least allows a reset afterwards. I'd rather not void the warranty on a brand new device if possible.
http://forum.xda-developers.com/showthread.php?p=53166571
Try this...it is a custom ROM but really close to stock
Sent from my SPH-L720 using XDA Premium 4 mobile app
I was already planning on installing UnknownForce Stock Rooted NAE Rom, if it's possible. However, you didn't really answer my question. Is there a method to bypass/kill the KNOX boot loader at this point or not? If not, then I might as well just stop now. I'm not prepared to void the warranty at this point.
tcatut said:
I was already planning on installing UnknownForce Stock Rooted NAE Rom, if it's possible. However, you didn't really answer my question. Is there a method to bypass/kill the KNOX boot loader at this point or not? If not, then I might as well just stop now. I'm not prepared to void the warranty at this point.
Click to expand...
Click to collapse
No. Once you have Knox, you have it.
Sent from my SPH-L720 using Tapatalk
Hello guys, I need a quick help. My friend sent me a Gs4 all the way from Canada. As it was locked, I made it unlocked in a store by paying 2000 bucks(it wasn't cheap). It runs on a 4.3 version(mentioned in about phone). I want to update it to kitkat without re-locking the phone. I don't know what he did or how he unlocked the phone. When I got the phone from him, it was rooted. That's all I know about the unlocking. I've got a little experience in backing up and flashing(experimented on my old Atrix2). But never unlocked a phone before.
So what I want to know now is wether there a way to update my SGH I377M to kitkat without messing it up by locking SIM again!!!
if there is a way, please help me out in doing it.
if there is not, can I unlock it myself after flashing it with kitkat and HOW ???
Hey, I'm not as new to this, but have some experience from mistakes. I'm pretty sure if you leave the root untouched, so will the unlock. That being said, there are guides to keep root while flashing a new custom, stock-like kitkat rom. Also, there are guides to re-unlock. Youtube is usually your best bet. I would definitely wait for the other, more experienced members to help you out. I wish you the best of luck.
Firefrazed said:
Hey, I'm not as new to this, but have some experience from mistakes. I'm pretty sure if you leave the root untouched, so will the unlock. That being said, there are guides to keep root while flashing a new custom, stock-like kitkat rom. Also, there are guides to re-unlock. Youtube is usually your best bet. I would definitely wait for the other, more experienced members to help you out. I wish you the best of luck.
Click to expand...
Click to collapse
Thanks for your time mate. I don't understand why ppl here stopped being much helpful to the newbies. No replies at all!! Anyways, can u please direct me to flash without loosing the root?
Thanks in advance
I know this question has been asked, and have been searching around the forums, but everything I am seeing says the reason that there are no real custom roms for this device is because the Bootloader is locked.. In my developer options on my device I am given the choice to enable OEM Unlock. Will this allow me to bypass the issues others are having? My Goal is to eventually learn what needs to be done so I can create my own rom or take a stock debloated rom and customize it completely to an end result I am happy with including UI/apps etc..
Thanks,
KaboneIsLegend
KaboneIsLegend said:
I know this question has been asked, and have been searching around the forums, but everything I am seeing says the reason that there are no real custom roms for this device is because the Bootloader is locked.. In my developer options on my device I am given the choice to enable OEM Unlock. Will this allow me to bypass the issues others are having? My Goal is to eventually learn what needs to be done so I can create my own rom or take a stock debloated rom and customize it completely to an end result I am happy with including UI/apps etc..
Thanks,
KaboneIsLegend
Click to expand...
Click to collapse
Nope. We can still have custom roms but we're just stuck with the one kernel required for root.
KaboneIsLegend said:
I know this question has been asked, and have been searching around the forums, but everything I am seeing says the reason that there are no real custom roms for this device is because the Bootloader is locked.. In my developer options on my device I am given the choice to enable OEM Unlock. Will this allow me to bypass the issues others are having? My Goal is to eventually learn what needs to be done so I can create my own rom or take a stock debloated rom and customize it completely to an end result I am happy with including UI/apps etc..
Thanks,
KaboneIsLegend
Click to expand...
Click to collapse
Bootloader is still locked. As of right now there is no way to unlock it so there is no way to have a custom ROM.
If you look at the development thread, you can see the options. One is a mod of the OEM ROM (PD8 only), but the other two are ROMs - on bade on 935U (echoe) and the other is a cleaned up modified Stock ROM.
With the locked bootloader you can only flash signed by Samsung ROMs - so no ASOP, CMxx ROMs. But by taking a stock ROM or the exiting unbloated one (with permission if you want to post your ROM - which would be welcome) it is something you can do right now (after you are rooted of course).
We also don't have custom recoveries, but flashing and backing up with FlashFire works pretty good, so go for it !
Binary100100 said:
Nope. We can still have custom roms but we're just stuck with the one kernel required for root.
Click to expand...
Click to collapse
Your talking the engineering boot.img ?
ShrekOpher said:
Bootloader is still locked. As of right now there is no way to unlock it so there is no way to have a custom ROM.
Click to expand...
Click to collapse
No way to force this?
gaww said:
If you look at the development thread, you can see the options. One is a mod of the OEM ROM (PD8 only), but the other two are ROMs - on bade on 935U (echoe) and the other is a cleaned up modified Stock ROM.
With the locked bootloader you can only flash signed by Samsung ROMs - so no ASOP, CMxx ROMs. But by taking a stock ROM or the exiting unbloated one (with permission if you want to post your ROM - which would be welcome) it is something you can do right now (after you are rooted of course).
We also don't have custom recoveries, but flashing and backing up with FlashFire works pretty good, so go for it !
Click to expand...
Click to collapse
I'm sure I know the answer to this, but can we fake signing? Also where would I need to go to research what needs to be done to remove the locked bootloader for my specific device? Maybe I can contribute something towards helping this get done. Are there any places people have shared their research?
Thanks guys for the awesome replies
KaboneIsLegend said:
I'm sure I know the answer to this, but can we fake signing? Also where would I need to go to research what needs to be done to remove the locked bootloader for my specific device? Maybe I can contribute something towards helping this get done. Are there any places people have shared their research?
Click to expand...
Click to collapse
People have been working on this since the device launched back in March. As far as I know, the files are cryptographically signed by Samsung, and the only way to bypass that is to find some kind of security exploit. As of yet, it hasn't been done. The leaked engineering kernel is basically the only known path at the moment to step outside of Samsung's locked down system.
andrewNY said:
People have been working on this since the device launched back in March. As far as I know, the files are cryptographically signed by Samsung, and the only way to bypass that is to find some kind of security exploit. As of yet, it hasn't been done. The leaked engineering kernel is basically the only known path at the moment to step outside of Samsung's locked down system.
Click to expand...
Click to collapse
Alright I will look into this then. I'm new to the android scene, but have experience with disassembly for applications, and reverse engineering for the older video game consoles. So why is there an option to oem unlock the phone if it doesn't really do that?
KaboneIsLegend said:
Alright I will look into this then. I'm new to the android scene, but have experience with disassembly for applications, and reverse engineering for the older video game consoles. So why is there an option to oem unlock the phone if it doesn't really do that?
Click to expand...
Click to collapse
Because not all variants have a locked bootloader. Just the US Qualcomm versions.
Binary100100 said:
Because not all variants have a locked bootloader. Just the US Qualcomm versions.
Click to expand...
Click to collapse
Thanks for that. I understand now.
We are rooted only because of the engineering bootloader. Stupid question time - with the problems with the kernel which are only partially fixed, ccouyld the kernel inself be modified or would it then be blocked by the bootloader.
There may custom kernels out there that would not work on a locked bootloader, but is the engineering kernel possibly open to modifications?