I saw someone say it was possible and I rooted mine just to do that (before knowing that mj7 custom recovery was impossible). I just want to put google edition on my S4. If anyone knows if what that person said is correct could you please send me a link to the info I need to make it happen.
I heard that the method was somehow related to using odin to install the stock image to the mj7 s4 as google edition is an official edition which would be great if that were true.
Jerome the Just said:
I saw someone say it was possible and I rooted mine just to do that (before knowing that mj7 custom recovery was impossible). I just want to put google edition on my S4. If anyone knows if what that person said is correct could you please send me a link to the info I need to make it happen.
I heard that the method was somehow related to using odin to install the stock image to the mj7 s4 as google edition is an official edition which would be great if that were true.
Click to expand...
Click to collapse
Not possible to put any GE Rom on a S4 with MJ7.
The boot loader is locked and you will brick your phone.
Don't attempt.
Jerome the Just said:
I saw someone say it was possible and I rooted mine just to do that (before knowing that mj7 custom recovery was impossible). I just want to put google edition on my S4. If anyone knows if what that person said is correct could you please send me a link to the info I need to make it happen.
I heard that the method was somehow related to using odin to install the stock image to the mj7 s4 as google edition is an official edition which would be great if that were true.
Click to expand...
Click to collapse
no ability to install any custom ROM as MJ7 bootloader is pretty much lockdown for that, Odin has nothing to do with it. Now, Hashcode is working on safestrap port for MJ7 and MDK2 base users but that is no guarantee that a GE based rom will work when it is done. Some restrictions on kernel base and safestrap you see. You can read thread on ROMs that worked with safestrap and see what was said there for Google Edition Rom
decaturbob said:
no ability to install any custom ROM as MJ7 bootloader is pretty much lockdown for that, Odin has nothing to do with it. Now, Hashcode is working on safestrap port for MJ7 and MDK2 base users but that is no guarantee that a GE based rom will work when it is done. Some restrictions on kernel base and safestrap you see. You can read thread on ROMs that worked with safestrap and see what was said there for Google Edition Rom
Click to expand...
Click to collapse
I do recall that there were two Google Edition ROMs that were reported to work on Safestrap, actually. Chances are they were still using the stock kernel though, so since A.) The OP is probably on a newer kernel than those, and B.) The newest "GE" ROMs on 4.3 use an AOSP kernel, unfortunately we're gonna have to wait juuuust a bit longer.
I know how you feel. TouchWiz has to go.
But hey, on the bright side, we can at least have HyperDrive RLS11 on our MJ7 phones for the time being!
Related
Hi,
I have a Verizon Samsung Galaxy s4 with build number JSS15J.I545VRUEMK2, and I recently rooted it so I could run the Google Play Edition Rom. From various threads and guides I knew that I needed to use SafeStrap because you can't use CWM recovery on an MK2 device. After a couple of attempts installing the GPE Rom, I found out that the GPE roms i could find only work with SafeStrap and an ME7 device. Furthermore, I found out that the only ROM that works with and MK2 device is Hyperdrive 11. I was wondering if there is any way around this or, alternatively, if there are any plans to fix this.
Thanks in advance.
walkerna22 said:
Hi,
I have a Verizon Samsung Galaxy s4 with build number JSS15J.I545VRUEMK2, and I recently rooted it so I could run the Google Play Edition Rom. From various threads and guides I knew that I needed to use SafeStrap because you can't use CWM recovery on an MK2 device. After a couple of attempts installing the GPE Rom, I found out that the GPE roms i could find only work with SafeStrap and an ME7 device. Furthermore, I found out that the only ROM that works with and MK2 device is Hyperdrive 11. I was wondering if there is any way around this or, alternatively, if there are any plans to fix this.
Thanks in advance.
Click to expand...
Click to collapse
First of all. .the only way around is to hope our devs who pretty much do the work on their spare time...look at what can be done...Second their nothing broken that needs a fix.
If you want ability to load different roms buy the dev phone.
safestrap enabled, Hyperdrive driven
decaturbob said:
First of all. .the only way around is to hope our devs who pretty much do the work on their spare time...look at what can be done...Second their nothing broken that needs a fix.
If you want ability to load different roms buy the dev phone.
safestrap enabled, Hyperdrive driven
Click to expand...
Click to collapse
Thanks for the reply,
Just for clarification, are you saying that if I load hyperdrive, then I'll be able to load the GPE rom with safestrap?
Thanks
walkerna22 said:
Thanks for the reply,
Just for clarification, are you saying that if I load hyperdrive, then I'll be able to load the GPE rom with safestrap?
Thanks
Click to expand...
Click to collapse
Can't run gpe..
safestrap enabled, Hyperdrive driven
Would this work?
http://forum.xda-developers.com/showthread.php?t=2343355
dogginsteed said:
http://forum.xda-developers.com/showthread.php?t=2343355
Click to expand...
Click to collapse
You need a custom recovery to load any ROM. Problem with the build you are running is you cannot install a custom recovery because the bootloader is locked down tighter than Fort Knox. Devs are working on a solution and hopefully they will succeed. Don't hold your breath though as it may take a long while.
Until then, you can root, uninstall and de-crapify the bloatware and crapware from the phone. Change the launcher to GEL and get something closer to a GPE phone. Done all this to my S4 and it runs much more smoothly and gives me excellent battery service.
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.
Guys...
SOrry if this is a poor post, but I'm still new to the gs4 on verizon.
When I got the phone about a week ago, It immediately took an OTA upgrade. I'm geussing this was a mistake?
Only reason I say this, is because i'm now on NC5, and it seems that I'm limited as to what I can do as far as ROMS.
However, I'm seeing that there are people on "MDK" which I'm assuming is an older base...are able to put whatever AOSP rom posted in the forum....
DO all phones comes with MDK base?
I can call them and ask to send a replacement....what are the chances its MDK?
A little help would be appreciated....Thanks!
Doubtful vzn has any phones left with mdk (I'm assuming, it was the original base when this phone came out last summer). If it makes you feel any better you were probably on mk2 4.3 when you took the upgrade, so you didn't really lose anything.
You can root, just no custom kernels, no custom recoveries, just safestrap. I'm running a Google play edition aosp 4.4.3 on safestrap and it runs pretty well. There's a thread in the general section.
Sent from my SCH-I545 using XDA Premium 4 mobile app
docluv01 said:
Guys...
SOrry if this is a poor post, but I'm still new to the gs4 on verizon.
When I got the phone about a week ago, It immediately took an OTA upgrade. I'm geussing this was a mistake?
Only reason I say this, is because i'm now on NC5, and it seems that I'm limited as to what I can do as far as ROMS.
However, I'm seeing that there are people on "MDK" which I'm assuming is an older base...are able to put whatever AOSP rom posted in the forum....
DO all phones comes with MDK base?
I can call them and ask to send a replacement....what are the chances its MDK?
A little help would be appreciated....Thanks!
Click to expand...
Click to collapse
MDK bootloader was on the original GS4 and an exploit called loki was found that could bypass the bootloader lock so that you could root & install a custom recovery like TWRP or CWM & thereby flash both TouchWiz and AOSP roms. Thanks to Vzw /Att /Samsung, ota updates were issued that kills this exploit. All new phones are locked down. Can still root & use Safestrap recovery to flash TW based roms into a "sandbox" parallel system. Can't flash new kernels though.
Got it! Thanks
You know I looked at that ROM....considering giving it a try.,
Im on NC5 and SS, are there any issues with GPS etc?
rrrrrrredbelly said:
Doubtful vzn has any phones left with mdk (I'm assuming, it was the original base when this phone came out last summer). If it makes you feel any better you were probably on mk2 4.3 when you took the upgrade, so you didn't really lose anything.
You can root, just no custom kernels, no custom recoveries, just safestrap. I'm running a Google play edition aosp 4.4.3 on safestrap and it runs pretty well. There's a thread in the general section.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
docluv01 said:
Got it! Thanks
You know I looked at that ROM....considering giving it a try.,
Im on NC5 and SS, are there any issues with GPS etc?
Click to expand...
Click to collapse
I have flashed several ss compatible kitkat roms and used gigilies nc2 wifi fix and never had issues with wifi or bluetooth or GPS
sent by safestrap powered echo v26
I want to install a GPe ROM base from the i905 Dev Forums, specifically this one
http://forum.xda-developers.com/showthread.php?t=2555569
It seems that at least one person has installed this ROM on their VZW s4 before, but I can't see to find anything definitive that says it is safe to install on my phone, which is currently running the "official" GPe ROM from the VZW dev thread.
Is there a safe way to do this?
NikolaeVarius said:
I want to install a GPe ROM base from the i905 Dev Forums, specifically this one
http://forum.xda-developers.com/showthread.php?t=2555569
It seems that at least one person has installed this ROM on their VZW s4 before, but I can't see to find anything definitive that says it is safe to install on my phone, which is currently running the "official" GPe ROM from the VZW dev thread.
Is there a safe way to do this?
Click to expand...
Click to collapse
What not use this...
http://forum.xda-developers.com/showthread.php?t=2643031
It's a super smooth and trouble free ROM for both of my Verizon MDK S4's.
Sent from my GT-I9505G using XDA Free mobile app
I like the extra options, want the dark theme, and dislike how the "official" ROM contains absolutely no customizations whatsoever.
The loss of xposed really hurt my love of the complete stock ROMs and want something that has a been more flexibility.
I'm helping my friend install CyanogenMod 12 on his S4 (jfltevzw). We've rooted it and we're currently doing a full backup through Safestrap in case anything happens. Once that's finished, I'm unsure as to what we should do. CyanogenMod's wiki has installation instructions for the Verizon S4, but it says in big bold letters to not attempt this if on a ROM newer than I545VRUAMDK. He's on the latest version that Samsung/Verizon have pushed out, which is I545VRUFNK1. Is there an alternate way to install CyanogenMod on top of the newer stock ROM, or is it not possible?
vaindil said:
I'm helping my friend install CyanogenMod 12 on his S4 (jfltevzw). We've rooted it and we're currently doing a full backup through Safestrap in case anything happens. Once that's finished, I'm unsure as to what we should do. CyanogenMod's wiki has installation instructions for the Verizon S4, but it says in big bold letters to not attempt this if on a ROM newer than I545VRUAMDK. He's on the latest version that Samsung/Verizon have pushed out, which is I545VRUFNK1. Is there an alternate way to install CyanogenMod on top of the newer stock ROM, or is it not possible?
Click to expand...
Click to collapse
its not possible. ONLY mdk builds will work.
Raymondlikesroot said:
its not possible. ONLY mdk builds will work.
Click to expand...
Click to collapse
Dang, so there's absolutely nothing whatsoever that can be done? The page says you can't downgrade, but is anything at all possible now that he's beyond the MDK build? He really wants to make the switch and is fine with doing a complete wipe or whatever is necessary.
EDIT: I've been trying to read up on the VZW S4 and why this isn't possible, but I don't quite get it. Reading other threads it seems like the reason is because the bootloader is locked, but that can't be the case if he was able to install Safestrap. I'm coming from a Nexus 5 where everything is incredibly simple, so I apologize for my ignorance. (I don't mean to say you're wrong or anything as I have no idea myself, I just don't understand why it doesn't work on newer ROMs.)
vaindil said:
Dang, so there's absolutely nothing whatsoever that can be done? The page says you can't downgrade, but is anything at all possible now that he's beyond the MDK build? He really wants to make the switch and is fine with doing a complete wipe or whatever is necessary.
EDIT: I've been trying to read up on the VZW S4 and why this isn't possible, but I don't quite get it. Reading other threads it seems like the reason is because the bootloader is locked, but that can't be the case if he was able to install Safestrap. I'm coming from a Nexus 5 where everything is incredibly simple, so I apologize for my ignorance. (I don't mean to say you're wrong or anything as I have no idea myself, I just don't understand why it doesn't work on newer ROMs.)
Click to expand...
Click to collapse
The reason we use Safestrap as opposed to twrp is because the bootloader is locked.
Surge1223 said:
The reason we use Safestrap as opposed to twrp is because the bootloader is locked.
Click to expand...
Click to collapse
Oh, okay. Really unfortunate that this isn't possible now. So he's just stuck with TouchWiz and can't do anything about it?
vaindil said:
Oh, okay. Really unfortunate that this isn't possible now. So he's just stuck with TouchWiz and can't do anything about it?
Click to expand...
Click to collapse
Yep
Sent from my my Lollipopped S4
vaindil said:
Oh, okay. Really unfortunate that this isn't possible now. So he's just stuck with TouchWiz and can't do anything about it?
Click to expand...
Click to collapse
you can install hyperdrive rom
its not lolipop but its worlds better then stock ...
also there is a chance of getting the 5.01 GPE edition rom running when Samsung releases the lolipop update for the vz s4
that would at least give us a working lolipop kernel to use with the gpe rombase
and hey you never know there could be a exploite in the lolipop rom/kernel that lets us get kexec working
Basically safestrap loads after the kernel but early enough to replace point to a different root for the system. So we can load what ever system we want... But are stuck with the kernel the phone booted. If the system is based on the stock kernel this is fine... But when it starts making calls to custom kernel stuff you will have trouble.
So Cyanogenmod only provides the GUI? I've installed CM on two B&N tablets and I've been asked to root a new Verizon Samsung Galaxy S4. I've assumed that, because it's new, it will have I545VRUFNK1 4.4.2. I rooted my VSG s3 years ago to 4.3 and there was no going back on that one. It looks like it's the same with VSG s4. So, if CM provides only the GUI, then a rooted VSG s4 can still access Google Apps? What is the concern with with TW based ROMs? Is it the recovery/backup feature or only being stuck with the VSG s4 GUI?
Raymondlikesroot said:
its not possible. ONLY mdk builds will work.
Click to expand...
Click to collapse
This explains why I bricked my phone when I tried to flash CM12...
ryant35 said:
This explains why I bricked my phone when I tried to flash CM12...
Click to expand...
Click to collapse
haha yeah, that could maybe potentially probably be the issue. Just maybe.
Couldn't you ODIN back to an older baseband version and then try to flash CM12?
Lockett said:
Couldn't you ODIN back to an older baseband version and then try to flash CM12?
Click to expand...
Click to collapse
Nope, in order to get CM, you'll need to be on MDK. Samsung prevents downgrading.
btw. the baseband version doesn't matter much. Its the bootloader version that is the toughie.
Boo! I just picked up my S4 yesterday after a 5 month run of using Windows Phone so I'm trying to figure this phone out. I'm on NK1 and trying to figure out how to root now.
vaindil where did you find a VRUFNK1 compatible version of Safestrip?