Hey guys,
My cousin's friend bought him a second-hand Verizon SGS4 SH-I545. Little did he know my cousin is not on Verizon.
I said: No matter we got XXA baby!
So here are my questions:
1. What is the latest firmware that you recommend him to flash? He is currently on: I545VRUFNC5 - which I see as the latest on SamMobile.
2. Is the phone locked in any way? If so, what's the best way to unlock it?
3. I want to have him rooted using a stock kernel, so that he can get rid of bloatware and use Titanium Backup
Suggestions, guides, links are all appreciated
Thank you!
-Dubbed
Read the stickie in general forum.... Most your answers are there
sent via safestrap 3.72 and echo v25.1! !
decaturbob said:
Read the stickie in general forum.... Most your answers are there
sent via safestrap 3.72 and echo v25.1! !
Click to expand...
Click to collapse
There's so much info there and more so it is apparently impossible to downgrade to bootloader and thus flash?
I just want someone to list it down for me in simple bullet points - not direct me to massive threads that have 20 links in them
TotallydubbedHD said:
There's so much info there and more so it is apparently impossible to downgrade to bootloader and thus flash?
I just want someone to list it down for me in simple bullet points - not direct me to massive threads that have 20 links in them
Click to expand...
Click to collapse
Why would we want to type all that over again? Read the sticky: http://forum.xda-developers.com/showthread.php?t=2606501
If you won't be bothered to read that, then here's some short, bullet points:
You can't downgrade the bootloader.
You can't have a custom recovery (except for the unsupported Safestrap)
You can't have CyanogenMod.
The only ROMs you can flash are those that are Safestrap and NC5 compatible
You can root using Towelroot
However, please read the sticky at the very least. If you won't do that, you WILL brick your phone.
k1mu said:
Why would we want to type all that over again? Read the sticky: http://forum.xda-developers.com/showthread.php?t=2606501
If you won't be bothered to read that, then here's some short, bullet points:
You can't downgrade the bootloader.
You can't have a custom recovery (except for the unsupported Safestrap)
You can't have CyanogenMod.
The only ROMs you can flash are those that are Safestrap and NC5 compatible
You can root using Towelroot
However, please read the sticky at the very least. If you won't do that, you WILL brick your phone.
Click to expand...
Click to collapse
Yeah read that already but wasn't sure- simply because it seems a little disorganised and very hard to understand with loads of links flying left and right.
TotallydubbedHD said:
Yeah read that already but wasn't sure- simply because it seems a little disorganised and very hard to understand with loads of links flying left and right.
Click to expand...
Click to collapse
If it's too difficult to digest perhaps modding a phone isn't for you...
sent via safestrap 3.72 and echo v25.1! !
decaturbob said:
If it's too difficult to digest perhaps modding a phone isn't for you...
sent via safestrap 3.72 and echo v25.1! !
Click to expand...
Click to collapse
lol...
TotallydubbedHD said:
lol...
Click to expand...
Click to collapse
S4 has alot of peculiarities, depending on firmware series. Once you go past MDK, custom recovery is limited to Safestrap and yet we see people all the time trying to load Twrp or CWM and end up borking their phone. Simple reading would prevent almost all those situations from happening. I know I had my thunderbolt for a couple years and loaded a ton of ROMS on it and when I moved up to S4 it was a rude awakening on what I can and can't do.
There is a lot of info to digest, even for the experienced people. Lately with kitkat many people run into wifi and bluetooth issues. Why? Mostly because they aren't loading right modules that have been discussed countless times.
decaturbob said:
S4 has alot of peculiarities, depending on firmware series. Once you go past MDK, custom recovery is limited to Safestrap and yet we see people all the time trying to load Twrp or CWM and end up borking their phone. Simple reading would prevent almost all those situations from happening. I know I had my thunderbolt for a couple years and loaded a ton of ROMS on it and when I moved up to S4 it was a rude awakening on what I can and can't do.
There is a lot of info to digest, even for the experienced people. Lately with kitkat many people run into wifi and bluetooth issues. Why? Mostly because they aren't loading right modules that have been discussed countless times.
Click to expand...
Click to collapse
I totally agree - that's why I'm asking as I'm unsure.
Last thing I want is something going wrong - and due to it being locked I don't want him running into problems.
So from what I understand I can't flash down and then flash back up?
I can however root? But what about unlocking?
TotallydubbedHD said:
I totally agree - that's why I'm asking as I'm unsure.
Last thing I want is something going wrong - and due to it being locked I don't want him running into problems.
So from what I understand I can't flash down and then flash back up?
I can however root? But what about unlocking?
Click to expand...
Click to collapse
if you mean unlocking the bootloader...NO
the sim is unlocked
decaturbob said:
if you mean unlocking the bootloader...NO
the sim is unlocked
Click to expand...
Click to collapse
bootloader is locked apparently...and to unlock it I would have to make my lil cousin supposedly flash an older version...
Sim being unlocked is the biggest thing
TotallydubbedHD said:
bootloader is locked apparently...and to unlock it I would have to make my lil cousin supposedly flash an older version...
Sim being unlocked is the biggest thing
Click to expand...
Click to collapse
the bootloader CAN NOT be unlocked,,,,,,there was an exploit in MDK firmware that "loki" process was able to use, since then da nada......devs been looking at it for almost 2 year and substantial bounty so far, da nada
sure fire way to brick the phone is messing with bootloader....
decaturbob said:
the bootloader CAN NOT be unlocked,,,,,,there was an exploit in MDK firmware that "loki" process was able to use, since then da nada......devs been looking at it for almost 2 year and substantial bounty so far, da nada
sure fire way to brick the phone is messing with bootloader....
Click to expand...
Click to collapse
haha cool beans thanks for confirming.
TotallydubbedHD said:
haha cool beans thanks for confirming.
Click to expand...
Click to collapse
No problem... We want to help people from messing up their S4..
sent via safestrap 3.72 and echo v25.1! !
OK - so my cousin tried putting another SIM in the phone (T-MOBILE) and he wasn't able to get it registered on network - it wouldn't allow him to do so.
Thus the phone is not sim locked then?
What do I have to do in order to unlock it? That's all I want to do and then root it after that.
TotallydubbedHD said:
OK - so my cousin tried putting another SIM in the phone (T-MOBILE) and he wasn't able to get it registered on network - it wouldn't allow him to do so.
Thus the phone is not sim locked then?
What do I have to do in order to unlock it? That's all I want to do and then root it after that.
Click to expand...
Click to collapse
No, it is not SIM locked. This is yet another frequently asked question, sadly.
The phone is configured with Verizon APNs. When you install a non-Verizon SIM, you must configure the APN for your non-Verizon carrier. (Settings/More networks/Mobile networks/Access Point Names, use the "+" to add an APN.)
Hopefully T-mo has a band in common with your VZ phone in your area.
k1mu said:
No, it is not SIM locked. This is yet another frequently asked question, sadly.
The phone is configured with Verizon APNs. When you install a non-Verizon SIM, you must configure the APN for your non-Verizon carrier. (Settings/More networks/Mobile networks/Access Point Names, use the "+" to add an APN.)
Hopefully T-mo has a band in common with your VZ phone in your area.
Click to expand...
Click to collapse
Anyway of getting APN settings for TMobile?
TotallydubbedHD said:
Anyway of getting APN settings for TMobile?
Click to expand...
Click to collapse
Read one of the several other T-Mobile threads here, or ask T-Mobile.
Yeah, I'm being lazy and not searching for you, but you can search as easily as I can.
Samsung Updates
OK I have the device rooted and running Hyperdrive 17.1. The only issue I'm having is how to block Samsung's constant attempt at upgrading the software. Running a custom Rom with Safestrap on Kit Kat. Anyway to get rid of that annoying reminder from Samsung about software updates???
Thanks
Krissy
Isis111 said:
OK I have the device rooted and running Hyperdrive 17.1. The only issue I'm having is how to block Samsung's constant attempt at upgrading the software. Running a custom Rom with Safestrap on Kit Kat. Anyway to get rid of that annoying reminder from Samsung about software updates???
Thanks
Krissy
Click to expand...
Click to collapse
Well if you're on stock Touchwiz you freeze SDM using TiBu. I believe hyperdrive already has SDM removed?!
Are you talking about the Security Policy update? If that is what you're talking about just search for that using TiBu and freeze that....
Sent from my SCH-I545 using Tapatalk
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
Been reading various threads and wondering if there is a preferred method for rooting S4. If so, is it based on ability the unroot it later? I am a noob to phone rooting...having only (but successfully) rooted my Nook Tablet a long time ago. I want to make sure I choose the "best practice" method to minimize my risk of borking it. I am on verizon and have
SCH-1545
Build: JDQ39.1545VRUAME7
As for the specifics, is it assumed once I format the SD card to exfat that it runs from and remains in the phone itself or can it be repurposed?
http://forum.xda-developers.com/showthread.php?t=2380325
This is for root. With ME7 you can not use a custom recovery just as a FYI. But safestrap recovery works with ME7. You can find that also in the android Dev section.
wedmiston said:
Been reading various threads and wondering if there is a preferred method for rooting S4. If so, is it based on ability the unroot it later? I am a noob to phone rooting...having only (but successfully) rooted my Nook Tablet a long time ago. I want to make sure I choose the "best practice" method to minimize my risk of borking it. I am on verizon and have
SCH-1545
Build: JDQ39.1545VRUAME7
As for the specifics, is it assumed once I format the SD card to exfat that it runs from and remains in the phone itself or can it be repurposed?
Click to expand...
Click to collapse
Each firmware version has its own method, and theres only 1 for each. Since your on me7 you have to use the .pwn method and once your rooted you can reformat your card/delete the files that were used.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk. now Free
I have also noticed a number of people wanting to go back to stock. Is this because root is unstable or has issues? Is there a pretty foolproof method for going back (my phone is only 3 months into my renewed VZ contract so unlike my Nook, I may need support at some point)
wedmiston said:
I have also noticed a number of people wanting to go back to stock. Is this because root is unstable or has issues? Is there a pretty foolproof method for going back (my phone is only 3 months into my renewed VZ contract so unlike my Nook, I may need support at some point)
Click to expand...
Click to collapse
Its absolutely stable. Most realize its not for them or they return their phones. Odin in my.opinion is the easiest way to remove root.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk. now Free
So does this NOT apply to my phone since it cites a different model?
\http://forum.xda-developers.com/showthread.php?t=2465713
Travisdroidx2 said:
http://forum.xda-developers.com/showthread.php?t=2380325
This is for root. With ME7 you can not use a custom recovery just as a FYI. But safestrap recovery works with ME7. You can find that also in the android Dev section.
Click to expand...
Click to collapse
wedmiston said:
So does this NOT apply to my phone since it cites a different model?
\http://forum.xda-developers.com/showthread.php?t=2465713
Click to expand...
Click to collapse
That root method is for Verizon S4 on ME7 firmware. If that is not you then I would not try it myself.
Could qualify as the dumb question of the day, but I have Build: JDQ39.1545VRUAME7...is this considered ME7 or are there different flavors?
Travisdroidx2 said:
That root method is for Verizon S4 on ME7 firmware. If that is not you then I would not try it myself.
Click to expand...
Click to collapse
wedmiston said:
Could qualify as the dumb question of the day, but I have Build: JDQ39.1545VRUAME7...is this considered ME7 or are there different flavors?
Click to expand...
Click to collapse
Only one ME7 for Verizon you are good.
Given that this was profiled as a "cover story" on the XDA home page is this the latest and greatest and is it different than
http://forum.xda-developers.com/showthread.php?t=2380325
Just want to clarify before i proceed
Travisdroidx2 said:
Only one ME7 for Verizon you are good.
Click to expand...
Click to collapse
wedmiston said:
Given that this was profiled as a "cover story" on the XDA home page is this the latest and greatest and is it different than
http://forum.xda-developers.com/showthread.php?t=2380325
Just want to clarify before i proceed
Click to expand...
Click to collapse
That is the same link I sent you in post 2. That is the root method for you on ME7.
OK, then maybe my question is, how is that different from this?
http://www.xda-developers.com/android/official-android-4-3-i9505xxuemj5-firmware-for-the-galaxy-s-4/
Travisdroidx2 said:
That is the same link I sent you in post 2. That is the root method for you on ME7.
Click to expand...
Click to collapse
wedmiston said:
OK, then maybe my question is, how is that different from this?
http://www.xda-developers.com/android/official-android-4-3-i9505xxuemj5-firmware-for-the-galaxy-s-4/
Click to expand...
Click to collapse
Thats for a different model of s4 and is android 4.3 while me7 is 4.2.2
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk. now Free
wedmiston said:
OK, then maybe my question is, how is that different from this?
http://www.xda-developers.com/android/official-android-4-3-i9505xxuemj5-firmware-for-the-galaxy-s-4/
Click to expand...
Click to collapse
Because that is not for Verizon. Or ME7. Your build version shows ME7. The root method is in the Verizon thread for ME7. It is pretty clear.
Affirmative to both of you and very much appreciated!
as long as I have two guys smarter than me, one more...how is this different
http://forum.xda-developers.com/showthread.php?t=2252248
wedmiston said:
as long as I have two guys smarter than me, one more...how is this different
http://forum.xda-developers.com/showthread.php?t=2252248
Click to expand...
Click to collapse
Thats motochopper I believe and its for mdk verizon versions.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk. now Free
and I know I have to block OTA updates...want to get this in place immediately so what is the best way to do this?
wedmiston said:
and I know I have to block OTA updates...want to get this in place immediately so what is the best way to do this?
Click to expand...
Click to collapse
Put the phone in airplane mode. Freeze or delete SDM.apk
Confirm successful root. Also froze SDM.01 file via TB Pro - am I good to go? Any other files need attention?
Travisdroidx2 said:
Put the phone in airplane mode. Freeze or delete SDM.apk
Click to expand...
Click to collapse
Does anybody know if anyone is building a root and recovery process for the VRUEMJ7 build. I got this S4 unrooted with the new build done....UGG
downhillvinnie said:
Does anybody know if anyone is building a root and recovery process for the VRUEMJ7 build. I got this S4 unrooted with the new build done....UGG
Click to expand...
Click to collapse
There are people working on root and @Hashcode is looking into getting Safestrap to work with it. But as to a recovery like twrp or CWM no dice on any build after mdk to install that.
Sent from my SCH-I545 using xda app-developers app
I think you are hosed if you are already on MJ7
Pardon if this is a noobish response, but can't we just use ODIN to force downgrade back to a build we can root and/or use custom recoveries?
OrionSX said:
Pardon if this is a noobish response, but can't we just use ODIN to force downgrade back to a build we can root and/or use custom recoveries?
Click to expand...
Click to collapse
The bootloader blocks being downgraded. Only way to downgrade would be to jtag from what I heard which us extremely dangerous to the average user
DemonSoul1996 said:
The bootloader blocks being downgraded. Only way to downgrade would be to jtag from what I heard which us extremely dangerous to the average user
Click to expand...
Click to collapse
There are no confirmed cases of anyone managing to downgrade even using JTAG. It's best to assume that you'll probably never be able to downgrade.
k1mu said:
There are no confirmed cases of anyone managing to downgrade even using JTAG. It's best to assume that you'll probably never be able to downgrade.
Click to expand...
Click to collapse
Sure there is read the original thread about it from hellsdroid he commented he downgraded an me7 phone to mdk several times.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
hexitnow said:
Sure there is read the original thread about it from hellsdroid he commented he downgraded an me7 phone to mdk several times.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
Click to expand...
Click to collapse
Hmm. The basis of my statement:
http://forum.xda-developers.com/showthread.php?t=2500826
Has anyone ever heard more from h311sdr0id about his post (see here) to get more info about this "state" that allows you to flash MDK over ME7 in Odin
Click to expand...
Click to collapse
No response. I know that h311sdr0id is "indisposed", of course. However, nobody has come forward to say that they've witnessed this. Thus my claim that it's unconfirmed.
It'd be great if JTAG was able to do this, but I'm rather skeptical given the fuses that get blown with each build to block going backwards. However, there is some hope as these are qfuses.
I originally updated from MI1 to MJ7, which was a stupid move, but just wondering if there is anyway to downgrade back in order to have full root and benefits?
I want to restore my phone and if I can go back, that would be great, because I don't want to go forward because if there is a new upadte it would make it worse instead of better, in terms of rooting.
Please advise
elite-fusion said:
I originally updated from MI1 to MJ7, which was a stupid move, but just wondering if there is anyway to downgrade back in order to have full root and benefits?
I want to restore my phone and if I can go back, that would be great, because I don't want to go forward because if there is a new upadte it would make it worse instead of better, in terms of rooting.
Please advise
Click to expand...
Click to collapse
you can root mj7 mine is
i heard that vroot isnt a good way to go...no?
Can I install custom roms on MJ7?
what would be the best way to restore this? with a file, or just go through the settings and do a factory reset?
elite-fusion said:
i heard that vroot isnt a good way to go...no?
Can I install custom roms on MJ7?
what would be the best way to restore this? with a file, or just go through the settings and do a factory reset?
Click to expand...
Click to collapse
Just keep taking OTAs up to MK2 (The latest). From there you can root and install safestrap (and a safestrap compatible rom). You cannot flash AOSP roms; the bootloader is locked down post MDK. This thread is pretty much all you need http://forum.xda-developers.com/showthread.php?t=2606501
so can mk2 be rooted?
elite-fusion said:
so can mk2 be rooted?
Click to expand...
Click to collapse
You should probably read the stickied thread at the top of the forum.
Its called What you need to know before, during and after modifying your verizon S4
Its probably relevant to your interests no?
This is the second time someone has linked you to it. I promise you if you READ THE WHOLE THING before asking anymore questions, you wont have questions to ask.
elite-fusion said:
so can mk2 be rooted?
Click to expand...
Click to collapse
Yes. Search for "Saferoot". I can't stress enough....... RESEARCH FIRST. It will save you a lot of headaches.
Sent from my NCC-1701 using Tapatalk 4
alright, one last question because it is NOT listed in that thread,
Where can i download the mk2 to load it manually because i am not a verizon customer but have a verizon s4 which i use with tmobile so it does not allow me to do OTA because it keeps telling me that Service is temporarily unavailable.
Please advise
elite-fusion said:
alright, one last question because it is NOT listed in that thread,
Where can i download the mk2 to load it manually because i am not a verizon customer but have a verizon s4 which i use with tmobile so it does not allow me to do OTA because it keeps telling me that Service is temporarily unavailable.
Please advise
Click to expand...
Click to collapse
As linked to from the provided thead Customizing your Verizon Galaxy S4 - what's possible and what's not
Has links to the updates that it is possible to flash, see the recover by reflashing stock section.
Seriously, its a pretty expensive phone and you can totally ruin it. Not a bad idea to read through that info people keep trying to give you.
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.