A few of us purchased the Dev Edition and it appears there are some things where clarification is required concerning the three "R's":
1. Rooting: I understand this wonderful rooting exercise is successful: http://forum.xda-developers.com/showthread.php?t=2290798. I would think since the Dev Edition is unlocked, an owner would only utilize Step 3, and NOT the kernel exchange section. Correct?
2. ROMing: Since the ROMS were created using the Loki enabled system, does this affect ROMing the Dev Edition since it is already unlocked? What does a user need to do? Or, does it not matter? Do the Loki enabled ROMS work on a Dev Edition?
3. Recovery: Again, it appears TWRP and CWM are Loki adjusted, so does this affect recovery on the Dev Edition and restoring? Also, is there a Stock Factory Image which will NOT turn the phone back to a locked bootloader? Or, does the one which exists OK to use?
I only ask these questions since a few of us are somewhat confused.
Thanking you in advance!
markwebb said:
A few of us purchased the Dev Edition and it appears there are some things where clarification is required concerning the three "R's":
Click to expand...
Click to collapse
I've been thinking about buying the Verizon S4 Dev Edition phone, but have been hesitant due to not knowing how simple it would be to root. Is it as simple as just running MotoChopper? Or is there a better way?
Being that the bootloader on this phone is truly unlocked, can you install the current versions of CWM or TWRP that are LOKI enabled, and will it work on this phone? I haven't seen any compiled versions that were non-loki (standard).
Same question goes for kernels too.
The first batch of Dev phones sold out in less than 24 hours, so I'd expect some of the people that have them would start posting their experience with it here soon. At least, I hope so!
Root failed when just applying the Motochopper step! It says it installs correctly and then it reboots and SuperSu is installed and then I checked for an upgrade which it took. However, it says it cannot install binary, there is a problem and closes.
I uninstalled SuperSu and tried a few times to root again but it doesn't work.
My phone states:
Kernel Version: 3.4.0-562219 dated May 15th
Build Number: JDQ439.I545OYUAMDK
Baseband: I545OYUAMDK
Must be something we can do....
markwebb said:
Root failed when just applying the Motochopper step! It says it installs correctly and then it reboots and SuperSu is installed and then I checked for an upgrade which it took. However, it says it cannot install binary, there is a problem and closes.
I uninstalled SuperSu and tried a few times to root again but it doesn't work.
My phone states:
Kernel Version: 3.4.0-562219 dated May 15th
Build Number: JDQ439.I545OYUAMDK
Baseband: I545OYUAMDK
Must be something we can do....
Click to expand...
Click to collapse
I wonder if step 2 and 4 are still required? (swapping kernels)
Even though the bootloader is unlocked, the kernel may still have root blocked?
guyd said:
I wonder if step 2 and 4 are still required? (swapping kernels)
Even though the bootloader is unlocked, the kernel may still have root blocked?
Click to expand...
Click to collapse
It sounds like it. But wouldn't swapping kernels render the Dev Edition to a retail version? Kinda defeats the purpose, no? Or, am I missing something?
The question is: Does the Dev Edition have the same kernel as the Retail Edition? If so, then it would make sense to swap kernels. I think we need the devs to weigh in.
markwebb said:
It sounds like it. But wouldn't swapping kernels render the Dev Edition to a retail version? Kinda defeats the purpose, no? Or, am I missing something?
The question is: Does the Dev Edition have the same kernel as the Retail Edition? If so, then it would make sense to swap kernels. I think we need the devs to weigh in.
Click to expand...
Click to collapse
From what I've been able to gather, Samsung has put in place a SetUID restriction on the stock release kernel via CONFIG_SEC_RESTRICT_SETUID. Apparently the D2 prerelease kernel doesn't have this restriction in place. That seems to be why flashing that is required prior to using MotoChopper to gain root. What I can't figure out is why you can flash the release DK afterwards and still keep root?
On the T-Mobile and Sprint S4 they've been able to remove the SetUID restriction on their latest DL release kernel by recompiling the kernel source with the SetUID restriction commented out
Thanks for the thoughts and analysis. Hopefully someone will find an alternate
root method for the dev edition since it has been available for a week and it sold out in less than twenty four hours, somebody with know how must have purchased it and is tinkering as we speak.
I would hate to render it back to a retail version otherwise.
Sent from my SCH-I545 using xda app-developers app
markwebb said:
Thanks for the thoughts and analysis. Hopefully someone will find an alternate
root method for the dev edition since it has been available for a week and it sold out in less than twenty four hours, somebody with know how must have purchased it and is tinkering as we speak.
I would hate to render it back to a retail version otherwise.
Click to expand...
Click to collapse
I think I may have found a solution. With the Developer Edition we have an unlocked bootloader, so there is no need to use loki. I was looking for a non-loki patched (normal) recovery that could be flashed in Odin. I think I found one here http://forum.xda-developers.com/showthread.php?t=2322675. Look for the "Latest version can be found here" link, not the "loki patched" link. The filename is : Philz_touch_5.06.6-jfltevzw.tar.md5
If this works like it did in previous unlocked Samsung devices, then we should be able to flash the custom recovery in Odin, and then boot into recovery afterwards to flash SuperUser. From there, we're rooted.
If I had my dev edition S4, I'd test it out myself. But I'm still waiting for them to get back in stock!
Great..am somewhat game to try. Well report back. Thanks!!
Sent from my SCH-I545 using xda app-developers app
IT WORKED...somewhat!!! When it boots, I now get Samsung Custom and unlocked symbol and I am in Philz Touch Recovery backing up the image.
As expected, the backup image is 4GB+ (saved on external card of course).
However, I can't update binary for root.
You, sir, are a genius...thanks so much..almost there!
Not really rooted though. Can't update binary and when in Root Explorer I can explore most folders but Root checker says I am not rooted.
Now what do I do? LOL
markwebb said:
IT WORKED...somewhat!!! When it boots, I nLet me know how it goes ow get Samsung Custom and unlocked symbol and I am in Philz Touch Recovery backing up the image.
As expected, the backup image is 4GB+ (saved on external card of course).
However, I can't update binary for root.
You, sir, are a genius...thanks so much..almost there!
Click to expand...
Click to collapse
Did you flash SuperSU from recovery via the zip file? (from this thread) http://forum.xda-developers.com/showthread.php?t=1538053. Look for the UPDATE-SuperSU-v1.41.zip file in the download section.
This should give you root after flashing in recovery! If you can't get root in a root app after flashing this file, then the kernel is blocking root. You can thank Samsung for adding that in the DK kernel.
You can easily work around this by flashing a custom kernel!
Let me know how it goes.
guyd said:
Did you flash SuperSU from recovery via the zip file? (from this thread) http://forum.xda-developers.com/showthread.php?t=1538053. Look for the UPDATE-SuperSU-v1.41.zip file in the download section.
This should give you root after flashing in recovery! If you can't get root in a root app after flashing this file, then the kernel is blocking root. You can thank Samsung for adding that in the DK kernel.
You can easily work around this by flashing a custom kernel!
Let me know how it goes.
Click to expand...
Click to collapse
BINGO!!!!!!!!!!!! THANKS!!!!
Now we need a thread/tutorial started for the Dev Edition Owners on how to do this!!
markwebb said:
BINGO!!!!!!!!!!!! THANKS!!!!
Now we need a thread/tutorial started for the Dev Edition Owners on how to do this!!
Click to expand...
Click to collapse
Do you now have root with the stock DK kernel, or did you flash a custom kernel?
Root with stock kernel.
Sent from my SCH-I545 using xda app-developers app
markwebb said:
Root with stock kernel.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Now I know exactly what I need to do when I get mine!
Thanks for testing it out on your device
guyd said:
Now I know exactly what I need to do when I get mine!
Thanks for testing it out on your device
Click to expand...
Click to collapse
You are welcome. Now, the next question: Can we flash the ROM's which are Loki adjusted?
markwebb said:
You are welcome. Now, the next question: Can we flash the ROM's which are Loki adjusted?
Click to expand...
Click to collapse
Good question. From what I have seen thus far, the recovery is the piece that has to be Loki adjusted to allow it to be flashed on a locked bootloader. I don't think the ROM cares one way or the other. The only thing I still have questions about is the kernel. Is the kernel in the Developer Edition different than the carrier version?
guyd said:
Good question. The only thing I still have questions about is the kernel. Is the kernel in the Developer Edition different than the carrier version?
Click to expand...
Click to collapse
How do I/we find out? If you have any suggestions, let me know. I have gone this far and sweated.
markwebb said:
How do I/we find out? If you have any suggestions, let me know. I have gone this far and sweated.
Click to expand...
Click to collapse
If we could get an MD5 of the Developer DK kernel (boot.img), and compare it to the MD5 of a completely stock DK kernel (boot.img). Or maybe compare the kernel build numbers? I dunno, just throwing some ideas out.
Related
Is this downgrading from ME7 to MDK possible? If so please guide me in the right direction.
Its not possible... Once you take the update theres no going back...
Sent from my SCH-I545 using xda premium
So I am new to the s4 and rooting. I really want to install the Hyperdrive ROM. I have been researching and researching what to do and I think i have found my answer for now and im not happy about it.
From what i gathered, since i installed the update and I am now on ME7, there is no root method bc they locked the phone down. Is this correct?
hondabomdc5 said:
So I am new to the s4 and rooting. I really want to install the Hyperdrive ROM. I have been researching and researching what to do and I think i have found my answer for now and im not happy about it.
From what i gathered, since i installed the update and I am now on ME7, there is no root method bc they locked the phone down. Is this correct?
Click to expand...
Click to collapse
Use the search button...this has been posted about a 1000 times...but yes you can root it but no custom recovery.
hondabomdc5 said:
So I am new to the s4 and rooting. I really want to install the Hyperdrive ROM. I have been researching and researching what to do and I think i have found my answer for now and im not happy about it.
From what i gathered, since i installed the update and I am now on ME7, there is no root method bc they locked the phone down. Is this correct?
Click to expand...
Click to collapse
You can root, but cant install custom recoveries or roms.
bfmetcalf said:
You can root, but cant install custom recoveries or roms.
Click to expand...
Click to collapse
Thanks for being kind and thanks for the info. I did state that I was new and have been looking. I could have started a whole new thread but instead asked the question in here. I do want to install the Hyperdrive rom but since with ME7 you cant install roms...looks like i wont be rooting until somebody gets this figured out. Again, thanks for being cool and answering my question.
y can't we just odin back to mdk?
Stauf99 said:
y can't we just odin back to mdk?
Click to expand...
Click to collapse
because of the bootloader will only allow signed packages to be installed on the phone and checks against older firmware and will not allow it. Unless you have the signed key you ain't flashing anything unless we find a workaround.
magneticzero said:
Use the search button...this has been posted about a 1000 times...but yes you can root it but no custom recovery.
Click to expand...
Click to collapse
So why is there ROMs for the ME7 build if they can't be flashed?
This [email protected] sucks!
So, I'm stuck on ME7 as well (32GB S4, otherwise I'd just go down to the store and swap it, complaining about something -- seems they don't stock them at any local corporate stores).
I'm coming from a Samsung Galaxy Nexus, and we have OMAP-Flash, which is like a low-level PROM flashing tool from the Samsung R&D team, and I could fix even a DEAD, or bricked phone with that. Is there something like that here to get back the original bootloader? I cant believe we're stuck on this crap... How 'bout a 2nd-init like my Droid-x days, or something slick like SafeStrap on the RAZR family?
...Just thinkin' "out loud".
IMGetwired said:
So, I'm stuck on ME7 as well (32GB S4, otherwise I'd just go down to the store and swap it, complaining about something -- seems they don't stock them at any local corporate stores).
I'm coming from a Samsung Galaxy Nexus, and we have OMAP-Flash, which is like a low-level PROM flashing tool from the Samsung R&D team, and I could fix even a DEAD, or bricked phone with that. Is there something like that here to get back the original bootloader? I cant believe we're stuck on this crap... How 'bout a 2nd-init like my Droid-x days, or something slick like SafeStrap on the RAZR family?
...Just thinkin' "out loud".
Click to expand...
Click to collapse
Short answer is 'no' - you're currently stuck with root as your best option. Hopefully this will change in the not-too-distant future.
Sent from my SCH-I545 using xda app-developers app
Yeah, this does suck.
Seems like we need someone to pick up the Dragonboard 8074 development kit to help us figure this out...even then, I'm sure Samsung has so many mods in there it'd be nuts to reverse engineer... Ugh, I'm so impatient! :silly:
Slimfast35 said:
So why is there ROMs for the ME7 build if they can't be flashed?
Click to expand...
Click to collapse
Because there for people that didn't get robbed by Samsung and update through the evil over the air update lol
Slimfast35 said:
So why is there ROMs for the ME7 build if they can't be flashed?
Click to expand...
Click to collapse
You're not quite understanding what a rom is and is not. There is no such thing as a rom for ME7. There are roms that use the ME7 base. They are flashable only by those who have the MDK bootloader. When a build number is listed for a rom, it is the build that the rom is based from.
Sent from my SCH-I545 using Tapatalk 4
Slimfast35 said:
So why is there ROMs for the ME7 build if they can't be flashed?
Click to expand...
Click to collapse
The ROM's that the devs based on MDK have been updated with the ME7 code just like any good developer does. But the bootloader those users have is still from their MDK (original) install. Once you go ME7 you can never go back, downgrade, crossgrade or get beyond the bootloader, for now anyways. Someone will find a way.
Nm
So I had plugged my device in to my computer, and it updated to 4.3. I did a factory reset, but it is too late. Does this mean my bootloader is now locked without a way to unlock at the moment? I came across ★ [Rom][I605VRUEMJ9][4.3] Stock Root Odex/Deodex [12/08/13]★ - xda-developers but it appears that I need an unlocked bootloader in order to flash it. Any advice on what I can do? I tried the instructions at Root I605VRUEMJ9 - Verizon Galaxy Note 2 SCH-I605 Android 4.3 Jelly Bean Firmware | True Android | #1 Custom Android Resource but got a failed (and am now worried that the KNOX counte ris stuck at 0x1.
pendraggon87 said:
So I had plugged my device in to my computer, and it updated to 4.3. I did a factory reset, but it is too late. Does this mean my bootloader is now locked without a way to unlock at the moment? I came across ★ [Rom][I605VRUEMJ9][4.3] Stock Root Odex/Deodex [12/08/13]★ - xda-developers but it appears that I need an unlocked bootloader in order to flash it. Any advice on what I can do? I tried the instructions at Root I605VRUEMJ9 - Verizon Galaxy Note 2 SCH-I605 Android 4.3 Jelly Bean Firmware | True Android | #1 Custom Android Resource but got a failed (and am now worried that the KNOX counte ris stuck at 0x1.
Click to expand...
Click to collapse
For the moment, yes. Attempting to return to a previous stock ROM, even via ODIN, will fail - I tried this myself last night. ODIN hangs on trying to install the last part of the ROM (the bootloader, if I remember right). If you do try to use ODIN to restore a stock ROM, you will need to run a repair install of the 4.3 ROM (you'll lose all data on the phone). Fun stuff.
So in short, we're locked & unrooted if we update using the official update via Verizon's update software.
computerslayer said:
For the moment, yes. Attempting to return to a previous stock ROM, even via ODIN, will fail - I tried this myself last night. ODIN hangs on trying to install the last part of the ROM (the bootloader, if I remember right). If you do try to use ODIN to restore a stock ROM, you will need to run a repair install of the 4.3 ROM (you'll lose all data on the phone). Fun stuff.
So in short, we're locked & unrooted if we update using the official update via Verizon's update software.
Click to expand...
Click to collapse
Damn. So I am completely willing to wipe everything. I already have everything backed up. If I am willing to have everything wiped, is there a way around it, or just wait for the good folks here at xda to stick it to Verizon
pendraggon87 said:
Damn. So I am completely willing to wipe everything. I already have everything backed up. If I am willing to have everything wiped, is there a way around it, or just wait for the good folks here at xda to stick it to Verizon
Click to expand...
Click to collapse
You can try to root with kingo (google it, xda won't allow links to it) but you may be out of luck on unlocking the bootloader again unless someone finds another exploit.
akellar said:
You can try to root with kingo (google it, xda won't allow links to it) but you may be out of luck on unlocking the bootloader again unless someone finds another exploit.
Click to expand...
Click to collapse
I saw references to kingo, but it looked sketchy. Can you tell more about it, and perhaps why XDA doesn't allow links?
computerslayer said:
I saw references to kingo, but it looked sketchy. Can you tell more about it, and perhaps why XDA doesn't allow links?
Click to expand...
Click to collapse
Nothing I can tell you that you can't find searching for it. Plenty of conversations about it already. No need for another one really.
akellar said:
Nothing I can tell you that you can't find searching for it. Plenty of conversations about it already. No need for another one really.
Click to expand...
Click to collapse
Thanks - I did find a lot threads. It does look sketchy, though nothing definitive.
Unless someone has found a root method for one of the other Samsung 4.3 builds, you better go out to your nearest wholesale store and buy the jumbo size of Vaseline.
imnuts said:
Unless someone has found a root method for one of the other Samsung 4.3 builds, you better go out to your nearest wholesale store and buy the jumbo size of Vaseline.
Click to expand...
Click to collapse
Kingo works on Note 3. Obviously different device but in theory it should work.
akellar said:
You can try to root with kingo (google it, xda won't allow links to it) but you may be out of luck on unlocking the bootloader again unless someone finds another exploit.
Click to expand...
Click to collapse
I did an OTA of 4.3 on my Note 2 already and was able to root using Kingo, no problems.
gee1000 said:
I did an OTA of 4.3 on my Note 2 already and was able to root using Kingo, no problems.
Click to expand...
Click to collapse
Ditto here. Though trying to flash a recovery (say, through Goo Manager) trips the Knox counter....and fails to boot ('unauthorized software' message)
computerslayer said:
Ditto here. Though trying to flash a recovery (say, through Goo Manager) trips the Knox counter....and fails to boot ('unauthorized software' message)
Click to expand...
Click to collapse
Yup. Bootloader is locked. That's why there's a sticky saying not to take OTA's.
akellar said:
Yup. Bootloader is locked. That's why there's a sticky saying not to take OTA's.
Click to expand...
Click to collapse
Sometimes one's role in life is to serve as a warning to others. Guess its my turn.
imnuts said:
Unless someone has found a root method for one of the other Samsung 4.3 builds, you better go out to your nearest wholesale store and buy the jumbo size of Vaseline.
Click to expand...
Click to collapse
Aren't both the S4 and N3 4.3 builds rooted? Maybe you're thinking bootloader unlocking???
After OTA my n2 lost root.
I can also confirm, that Kingo roots the N2 after taking the Verizon OTA, but the bootloader remains locked. For me acquiring root again was great, because I use the Xposed framework a lot and many other apps that need root. As for the bootloader, I'm sure that sooner or later, one of the great devs will kick butt and get it unlocked. For those guys that challenge is like an itch.
Sent from my SCH-I605 using XDA Premium 4 mobile app
rdeluis said:
After OTA my n2 lost root.
I can also confirm, that Kingo roots the N2 after taking the Verizon OTA, but the bootloader remains locked. For me acquiring root again was great, because I use the Xposed framework a lot and many other apps that need root. As for the bootloader, I'm sure that sooner or later, one of the great devs will kick butt and get it unlocked. For those guys that challenge is like an itch.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Wouldn't bet on it. S4 and Note 3 are both locked and will likely remain that way. Never say never but the likelihood is slim.
You're right and honestly as long as I have, root I don't care much anymore. If it happens great, if it doesn't ok. Sooner or later we will upgrade to a new toy. Lol
Sent from my SCH-I605 using XDA Premium 4 mobile app
Ok, a little info on me. I have had an iPhone since 2007. I decided to buy a used G S4 to see if I would like it. So far I like it a lot but need help getting it just right.
I am trying to install custom roms on my device. I want to try CM.10 first. So far I have achieved root aaccess, and installed gooManager.
The problem is that when I install a custom recovery script so I can have a custom recovery the phone locks up. What could I be doing wrong? I am sure this has been covered a hundred times but there is so much info on here its overwhelming to someone new to android. Thanks to everyone for the great work and contributions s already made.
Try odin to flash!
iPhone*convert said:
Ok, a little info on me. I have had an iPhone since 2007. I decided to buy a used G S4 to see if I would like it. So far I like it a lot but need help getting it just right.
I am trying to install custom roms on my device. I want to try CM.10 first. So far I have achieved root aaccess, and installed gooManager.
The problem is that when I install a custom recovery script so I can have a custom recovery the phone locks up. What could I be doing wrong? I am sure this has been covered a hundred times but there is so much info on here its overwhelming to someone new to android. Thanks to everyone for the great work and contributions s already made.
Click to expand...
Click to collapse
when i installed my custom recovery i used cwm recovery (my preference) and used odin to flash it. its not as easy but its more reliable to me just look up a tutorial on how to flash custom recovery on odin. There are many vids on youtube
mylifeandroid said:
when i installed my custom recovery i used cwm recovery (my preference) and used odin to flash it. its not as easy but its more reliable to me just look up a tutorial on how to flash custom recovery on odin. There are many vids on youtube
Click to expand...
Click to collapse
I watched all of the videos. Do I have a locked boot loader? Does that keep me from installing open recovery script? If so do I need a device with an older baseband in order to root, install custom recovery, and run custom roms?
I have a SCH-I545 running 4.3 with an mk2 baseband.
Yes, your bootloader is locked and currently there is no way to unlock it. Safestrap is your only option for ROMs now. Start with reading the OP.
http://forum.xda-developers.com/showthread.php?t=2441441
Sent from my SCH-I545 using Tapatalk
How do I find an older gs4 with an unlocked bootloader? How will I know when I find one? What baseband version should I be looking for?
iPhone*convert said:
How do I find an older gs4 with an unlocked bootloader? How will I know when I find one? What baseband version should I be looking for?
Click to expand...
Click to collapse
Where your phone says mk2 the other will say mdk. . As far as finding one people sell them on ebay
iPhone*convert said:
How do I find an older gs4 with an unlocked bootloader? How will I know when I find one? What baseband version should I be looking for?
Click to expand...
Click to collapse
Check out www.swappa.com
People have em up for sale, just look for the last three letters of the build (or baseband I suppose) to be MDK. Anything newer than that is locked down.
Sent from my SCH-I545 using Tapatalk
iPhone*convert said:
How do I find an older gs4 with an unlocked bootloader? How will I know when I find one? What baseband version should I be looking for?
Click to expand...
Click to collapse
Information is easily available in these forums concerning bootloaders and rooting and recoveries....with you phone your only option is safestrap and just one or 2 roms are available..
look before you jump
Nobody posts the build number in their adds on ebay or that swappers site. I'm messaging them all individually haha. Lmfao why didn't I read about this more before buying this boot locked pos lol.
Me7 and mj7 are worthless right?
iPhone*convert said:
Me7 and mj7 are worthless right?
Click to expand...
Click to collapse
I will be honest this is the first phone that i have ever been satisfied with rooted debloated stock but I am very greatful my flashing itch is able to be somewhat scratched with safestrap. The above builds aren't worthless but I guess that all depends on your point of view and what your wanting to do with your device.
iPhone*convert said:
Me7 and mj7 are worthless right?
Click to expand...
Click to collapse
don't understand the statement?
the stock roms run extremely well and with root you can debloat pretty easily. S4 phone is a superior device to most anything else out there at this moment whether you mod it or not
Hey your in luck there is a guy selling his mdk s4 for 330 on the general thread.
I'm currently on a Galaxy S3, but I have an S4 coming in on Friday.
I saw a thread for rooting the S4, but do I need to unlock the bootloader like I did in the S3 to install a rom?
Basically, where is the thread that has all the info I need to root, unlock, and install a custom recovery for the S4?
I have one for the S3, but can't find it for the S4.
GlitchMob said:
I'm currently on a Galaxy S3, but I have an S4 coming in on Friday.
I saw a thread for rooting the S4, but do I need to unlock the bootloader like I did in the S3 to install a rom?
Basically, where is the thread that has all the info I need to root, unlock, and install a custom recovery for the S4?
I have one for the S3, but can't find it for the S4.
Click to expand...
Click to collapse
you cant find thread? How hard did you look? There is a stickie can't be missed in the general section.
BTW, the bootloader is locked for all versions of firmware since mdk.
only option is safetrap.
decaturbob said:
you cant find thread? How hard did you look? There is a stickie can't be missed in the general section.
BTW, the bootloader is locked for all versions of firmware since mdk.
only option is safetrap.
Click to expand...
Click to collapse
Okay maybe my understanding on the purpose of unlocking the bootloader is incorrect.
I thought the bootloader has to be unlocked in order to install a custom rom?
On my S3 if the bootloader wasn't unlocked the phone would brick.
Safestrap is a custom recovery so how is that relevant to bootloader? I can't seem to draw the connection.
Thanks!
GlitchMob said:
Okay maybe my understanding on the purpose of unlocking the bootloader is incorrect.
I thought the bootloader has to be unlocked in order to install a custom rom?
On my S3 if the bootloader wasn't unlocked the phone would brick.
Safestrap is a custom recovery so how is that relevant to bootloader? I can't seem to draw the connection.
Thanks!
Click to expand...
Click to collapse
plenty of threads here to read to educate yourself.
S4 bootloader is locked since mdk firmware. MDK had an exploit that Loki process allowed custom recovery
safestrap uses an exploit to work around it so its the only custom recovery for the locked bootloader.
Each subsequent firmware release locks the bootloader and exploits down further. Anyone taking the next round of kit kat OTA's will likely loose root as well.
GlitchMob said:
I'm currently on a Galaxy S3, but I have an S4 coming in on Friday.
I saw a thread for rooting the S4, but do I need to unlock the bootloader like I did in the S3 to install a rom?
Basically, where is the thread that has all the info I need to root, unlock, and install a custom recovery for the S4?
I have one for the S3, but can't find it for the S4.
Click to expand...
Click to collapse
More then likely the device you get will come with the new baseband MJ7 or MK2. You need to check this before you start messing with anything. That said the bootloader is locked up tight and you will be very limited with what you can do with it. You can root, and install safestrap(a custom recovery by Hashcode that bypasses the bootloader). This will allow you to install certain touchwiz based roms but you have to be sure they are compatible with safestrap.
Root for 4.3 baseband:
http://forum.xda-developers.com/showthread.php?t=2565758
Safestrap:
http://forum.xda-developers.com/showthread.php?t=2441441
Both these links are in the android devlopment section. It is very difficult with this device because there are multiple root methods and recovery methods depending on baseband version. If by some chance you get the phone and the baseband is MDK, DO NOT UPDATE!!!! This will allow you to install loki'ed recovery and flash any rom you want. Chances are that won"t happen though. Good luck
decaturbob said:
you cant find thread? How hard did you look? There is a stickie can't be missed in the general section.
BTW, the bootloader is locked for all versions of firmware since mdk.
only option is safetrap.
Click to expand...
Click to collapse
decaturbob said:
plenty of threads here to read to educate yourself.
S4 bootloader is locked since mdk firmware. MDK had an exploit that Loki process allowed custom recovery
safestrap uses an exploit to work around it so its the only custom recovery for the locked bootloader.
Each subsequent firmware release locks the bootloader and exploits down further. Anyone taking the next round of kit kat OTA's will likely loose root as well.
Click to expand...
Click to collapse
I understand that I need to look into it, but the way things are organized is different. I've been on an S3 for almost two years now and the forums in the S4 are just overwhelming with information that is scattered. Here is an example of what I was hoping for when I came to the S4 section.
http://forum.xda-developers.com/showthread.php?t=1762709
onemeila said:
More then likely the device you get will come with the new baseband MJ7 or MK2. You need to check this before you start messing with anything. That said the bootloader is locked up tight and you will be very limited with what you can do with it. You can root, and install safestrap(a custom recovery by Hashcode that bypasses the bootloader). This will allow you to install certain touchwiz based roms but you have to be sure they are compatible with safestrap.
Root for 4.3 baseband:
http://forum.xda-developers.com/showthread.php?t=2565758
Safestrap:
http://forum.xda-developers.com/showthread.php?t=2441441
Both these links are in the android devlopment section. It is very difficult with this device because there are multiple root methods and recovery methods depending on baseband version. If by some chance you get the phone and the baseband is MDK, DO NOT UPDATE!!!! This will allow you to install loki'ed recovery and flash any rom you want. Chances are that won"t happen though. Good luck
Click to expand...
Click to collapse
Thank you. This is the response I was looking for. As you said there are many stipulations with each baseband. This is something I am not used to coming for an S3, which is far simpler to deal with. Thanks again!
GlitchMob said:
Thank you. This is the response I was looking for. As you said there are many stipulations with each baseband. This is something I am not used to coming for an S3, which is far simpler to deal with. Thanks again!
Click to expand...
Click to collapse
The difference isn't in the baseband, it's in the bootloader. You can run a newer baseband than your bootloader, for example, especially if you have the MDK bootloader.
Since you're starting from stock, the baseband and the bootloader revisions are the same and can be found from Settings/More/About phone.
Before you flash anything, please read the what you need to know thread in the General section. Also, there's my thread in this forum.
The S4 is more complicated than the S3 largely because Samsung has really locked it down much more effectively than the S3. Consequently, there's lots of ways to go wrong. Reading first can save you a lot of grief.
k1mu said:
The difference isn't in the baseband, it's in the bootloader. You can run a newer baseband than your bootloader, for example, especially if you have the MDK bootloader.
Since you're starting from stock, the baseband and the bootloader revisions are the same and can be found from Settings/More/About phone.
Before you flash anything, please read the what you need to know thread in the General section. Also, there's my thread in this forum.
The S4 is more complicated than the S3 largely because Samsung has really locked it down much more effectively than the S3. Consequently, there's lots of ways to go wrong. Reading first can save you a lot of grief.
Click to expand...
Click to collapse
One more question. Is there a way to flash the s4 back to stock? I'll find the info on how, but going into the whole rooting and coming phase it would be nice to know that I could flash back to stock with odin. As I have with my s3.
GlitchMob said:
One more question. Is there a way to flash the s4 back to stock? I'll find the info on how, but going into the whole rooting and coming phase it would be nice to know that I could flash back to stock with odin. As I have with my s3.
Click to expand...
Click to collapse
Yes. Read the second link in my reply above - it tells you how to identify what build you're on and has links to the downloadable Odin images for each build.
k1mu said:
Yes. Read the second link in my reply above - it tells you how to identify what build you're on and has links to the downloadable Odin images for each build.
Click to expand...
Click to collapse
Thanks for your help. Turns out I'm on MJ7. I'm going to let this puppy charge while I hit the gym. I'll root it and see what rom I can install later tonight. Thanks again!! :victory:
GlitchMob said:
Thanks for your help. Turns out I'm on MJ7. I'm going to let this puppy charge while I hit the gym. I'll root it and see what rom I can install later tonight. Thanks again!! :victory:
Click to expand...
Click to collapse
Mind as well update to mk2. You can do the same as mj7 but are most up to date. Just my 2 pennies. Btw I'm on bonestock 2.1 in SS romslot 1.
Sent from my SCH-I545 using xda app-developers app
Slowbalt said:
Mind as well update to mk2. You can do the same as mj7 but are most up to date. Just my 2 pennies. Btw I'm on bonestock 2.1 in SS romslot 1.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Is there a noticeable difference? If its the same, why upgrade?
I am coming from a similar situation as you. I cracked my screen on my S3 and Asurion replaced it with an S4, which I received on Monday. I thought that I was going to be able to load SlimKat and pick up where I left off, but no.
The posts that k1mu linked are a great starting point. A few of my thoughts that I came to realize this week. These are my ways of looking at it and may not be totally correct.
The bootloader is locked and there isn't a total unlock (yet). Safestrap allows you to crack the door open a little and reach your arm in to grab a few things.
You will need to stick with ROMs that work with the TouchWiz kernel. The post that k1mu referenced has a link to compatible ROMs. You will not be able to load SlimKat, CM, Carbon, etc. Basically any ROM you choose will have TW underneath. Some of the ROMs will try to look like an ASOP, but it is still a TW base.
Safestrap will allow you to create ROM slots where you can try out the ROM to see if you like it. I am still trying to decide what I want to use. Currently I have Hyperdrive as the leader. Everything that I do continues to work. The Eclipse ROM looks good but it is not quite there yet, but he is working on a build in the next couple days. Here is a link to their website with more up to date status. Eclipse . I also looked at the Foxhound ROM and it is good also. For me support and future upgrades are the most important. I am starting to think that i will embrace TW instead of trying to cover it up and will go with Hyperdrive.
If you use TiBu, read this post, especially with Hyperdrive http://forum.xda-developers.com/showthread.php?t=2653044.
The other realization that hit me was that while Safestrap can create partitions for loading different ROMs, each one is restricted to a maximum of a 3GB /data partition. When I tried to restore all of my apps this was quickly used up. It isn't supported by Safestrap to flash to the stock location, but it can and has been done. Since Safestrap isn't doing a flash there are more risks and I think that this should probably be kept to a minimum. This is where you want to test all the candidate ROMs first and then decide which one to use and then flash to the stock location. Obviously this could cause problems with the phone and would use ODIN as a fallback. Unless something get totally hosed and then you are out of a phone.
One thing that I realized a long time ago is that when you change devices you may want to do everything exactly the way it was before. On the phone or even when looking for information. But in most cases it is better to change your processes or work flow to work with the new device than it is to change the device to work in your previous work flow.
I'm kind of a noob to modding my phone is there any guides for newbies who have never backed up.. Also need help finding s ROM that would work with my phone l.. Any help would be great?
delphox said:
I'm kind of a noob to modding my phone is there any guides for newbies who have never backed up.. Also need help finding s ROM that would work with my phone l.. Any help would be great?
Click to expand...
Click to collapse
http://true-android.blogspot.com/2014/01/install-cwm-6045-advance-edition-on_2385.html?m=1
Here u can find how to install cmw recovery and custom rom
delphox said:
I'm kind of a noob to modding my phone is there any guides for newbies who have never backed up.. Also need help finding s ROM that would work with my phone l.. Any help would be great?
Click to expand...
Click to collapse
OK, here are a few thoughts that can help you....
1. Are you aware of Knox? If yes, then good. Because installing custom recovery on your device will trip the Knox security fuse on your shiny new phone. If no, please read the thread entitled something along the lines of "survey for those who tripped Knox," and the thread devoted to rooting and not tripping Knox.
2. What is your software version? Please show your about phone screen (settings, general, about device). If you're not on the latest firmware, we'll get you there.
3. Your general trajectory of things once on the latest firmware version NC5 and you're OK with tripping Knox, which your question implies, should be...
-->Install recovery (TWRP or PhilZ CWM), latest versions can be found in the original development forum and Android development forum, respectively. Both are outstanding, none is best, neither is cross-compatible. Pick your poison.
-->Install a pre-rooted rom or just root your phone.
-->Have a blast
In closing, I highly recommend choosing a TouchWiz based rom before you flash any AOSP based variant, mostly because these will give you the closest to familiar feel without losing features.
There is no best except that which you like most.
Please report back with the info requested herein and we can block and tackle this, with the incredible resources hewn and stored here on xda.
No reason to depart from these fine forums to do that which is rightly done and freely available only here.
Sent from my SM-N900P using Tapatalk
I would suggest as micmars has said you do a little reading on KNOX first. Then to get your feet wet, if you decide to go ahead and root your device. I would go with rooting the stock rom in your phone first, then add a custom recovery ( TWRP or PHILZ CWM ) . I run PHILZ CWM works great and its easy to use. Now once its rooted you can disable KNOX and remove the extra apps that you are not using that clog up the operating system ( OS ) of you device. This is called BLOATWARE go to this XDA site to get lists of safe to remove apps http://forum.xda-developers.com/showthread.php?t=2770729 . Once you have done that now make a backup of your slimmed down De-Bloated OS. Now your ready to go and start installing custom roms, and if doesn't work out you can always recover your backup and get back to square one. Then try a another rom till you find one you like !!! :fingers-crossed:
Is there an updated all in one tool kit for these devices
Sent from my SPH-L900 using XDA Free mobile app
rickberg said:
Is there an updated all in one tool kit for these devices
Sent from my SPH-L900 using XDA Free mobile app
Click to expand...
Click to collapse
yes but you have to donate on his site to get them. i did long ago and i believe it only goes up to nab as of now.
kaos420 said:
yes but you have to donate on his site to get them. i did long ago and i believe it only goes up to nab as of now.
Click to expand...
Click to collapse
OK so is it not recommended to use the all in one than and what is the latest version on these devices. Are there the same recurring issues with these as the n2 where once you update to the latest version bootloader you can't go back I.e. on n2 you couldn't downgrade to mk4 once you booted into the ne2 bootloader
Sent from my SPH-L900 using XDA Free mobile app
rickberg said:
OK so is it not recommended to use the all in one than and what is the latest version on these devices. Are there the same recurring issues with these as the n2 where once you update to the latest version bootloader you can't go back I.e. on n2 you couldn't downgrade to mk4 once you booted into the ne2 bootloader
Sent from my SPH-L900 using XDA Free mobile app
Click to expand...
Click to collapse
nc5D is the latest version. yes once updated you cant go back just like any other samsung now.