Question about mdk and newer kernels - Verizon Samsung Galaxy S 4

I'm on MK2 right now and it seems hope of bootloader unlock may be in the form of reverting back to mdk.
Of this is the case here is my question.
If on mdk can you flash any stock kernel like mk2 or are you stuck with mdk based kernel. I ask this as mj7 had charger issues but mk2 doesn't.
Sent from my SCH-I545 using Tapatalk

tshelby73 said:
I'm on MK2 right now and it seems hope of bootloader unlock may be in the form of reverting back to mdk.
Of this is the case here is my question.
If on mdk can you flash any stock kernel like mk2 or are you stuck with mdk based kernel. I ask this as mj7 had charger issues but mk2 doesn't.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Where did you see that we could revert, or are even close to being able to?
Sent from my NCC 1701 using Tapatalk 4

Not able to revert but has been talked about. I'm just preparing in case it happens and finding out info. It may never happen.
Sent from my SCH-I545 using Tapatalk

tshelby73 said:
I'm on MK2 right now and it seems hope of bootloader unlock may be in the form of reverting back to mdk.
Of this is the case here is my question.
If on mdk can you flash any stock kernel like mk2 or are you stuck with mdk based kernel. I ask this as mj7 had charger issues but mk2 doesn't.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
If you're on an MDK s4 you'd be able to flash any kernels that are made for the phone as well as any modems.
Sent from my SCH-I545 using XDA Premium 4 mobile app

Thanks
Sent from my SCH-I545 using Tapatalk

Related

New to Android

I have a Verizon S4 and I am on 4.2.2 on an I545 VRUAME7. Is this how to get back to the original before the OTA to be able to unlock the bootloader? I found thisd but not sure if that is what that does http://forum.xda-developers.com/showthread.php?t=2289325 I am not rooted right now if that matters and I really don't wanna screw anything up but I really want to be able to flash custom roms
Thanks, Dan
No....the OTA ME7 you CAN NOT go back to before the OTA ME7. You are stuck till someone finds a way.... Sorry for the bad news
Sent from my SCH-I545 using xda app-developers app
You can root me7 tho.
Sent from my SCH-I545 using Tapatalk 2
For what you want, you are out of luck. You cannot revert back. You cannot install a recovery. You cannot install a custom rom.
Sent from my SCH-I545 using Tapatalk 4

[Q] Safestrap questions

Thanks for the helpful responses.
For anyone viewing this I was attempting to consolidate my 5 hours of reading into a nutshell.
Yes me7 is so far not vulnerable for romming but safestrap is a option soon to be for all me7 users. Big mistake if you wanted a bootloader workaround like loki to have custom recovery. I mean we can't say to claim the device defective as that can be seen as warranty fraud but your actions..
Sent from my SCH-I545 using Tapatalk 4
Addiso said:
Yes me7 is so far not vulnerable for romming but safestrap is a option soon to be for all me7 users. Big mistake if you wanted a bootloader workaround like loki to have custom recovery. I mean we can't say to claim the device defective as that can be seen as warranty fraud but your actions..
Sent from my SCH-I545 using Tapatalk 4
Click to expand...
Click to collapse
Thanks for the response. So then nothing can be flashed via Odin aside from a pure stock ME7 ROM?
Sent from my SCH-I545 using Tapatalk 2
AndroidSlave said:
Thanks for the response. So then nothing can be flashed via Odin aside from a pure stock ME7 ROM?
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Yep thats all that can be flashed in odin. On the s3 you could flash custom recovery via odin but that required an unlocked bootloader.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.

Enlighten me on baseband versions.

I'm hoping someone can clear up something for me. This is a screenshot of my baseband version. As you can see it's ME7, but I can flash any rom just fine without safestrap. This shouldn't work, right? Am I missing something or just being a dum dum?
Sent from my Vanir boosted Galaxy S4
You're on mdk with loki but with me7 baseband or as you can maybe say radio version. Just like HTC having its own radios and you can flash a newer version through recovery.
Sent from my SCH-I545 using Tapatalk
Awesome thank you!
Addiso said:
You're on mdk with loki but with me7 baseband or as you can maybe say radio version. Just like HTC having its own radios and you can flash a newer version through recovery.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Not 100% accurate. The latest radio is MJ7. Currently the only correct way to apply it is to flash via Odin.
FernBch said:
Not 100% accurate. The latest radio is MJ7. Currently the only correct way to apply it is to flash via Odin.
Click to expand...
Click to collapse
Yeah but he's only talking about me7 correct? I think so.
Sent from my SCH-I545 using Tapatalk
FernBch said:
Not 100% accurate. The latest radio is MJ7. Currently the only correct way to apply it is to flash via Odin.
Click to expand...
Click to collapse
I'm on MDK and I flashed MJ7 radio through TWRP... no problems here.
Sent from my SCH-I545 using Tapatalk
Yea I flashed the latest "radio" last night through twrp as well. Working great!
Sent from my Vanir boosted Galaxy S4

Verizon Builds

[EDITED BASED OFF FEEDBACK]
Its hard to gather what order and what defines each build for the Verizon Galaxy S4 without a lot of reading. So here is my understanding! Please correct and or add onto this!!!
MDK - Original Build, can replace recovery, rootable
ME7 - 2nd build, cannot replace recovery, rootable, SafeStrap support
MI1 - 3rd build, cannot replace recovery, rootable, Safestrap support (you can install any ME7, or MI1 roms)
MJ7 - 4th build, cannot replace recovery, rootable, Safestrap is not supported
MK? -
ktamlyn said:
Its hard to gather what order and what defines each build for the Verizon Galaxy S4 without a lot of reading. So here is my understanding! Please correct and or add onto this!!!
MDK - Original Build, can replace recovery, rootable
ME7 - 2nd build, cannot replace recovery, rootable, extensive SafeStrap support
MI1 - 3rd build, cannot replace recovery, rootable, limited Safestrap support due to limited ROM selection* (HyperDrive only?)
MJ7 - 4th build, cannot replace recovery, rootable, Safestrap is not supported
Is it true that you cannot run ME7 Roms on a MI1 device using Safestrap?
Click to expand...
Click to collapse
No, You can run any ROM on MI1 that suports Safestrap on ME7 & is based on TouchWiz. You would just flash the MI1 kernel modules after you finish installing the ROM.
The only difference between ME7 and MI1 really is that screen rotation is broken on MI1 if you run a custom rom. Also MK2 is the newest build now.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Thanks this helped me greatly. Going to Odin back to MDK after reading this.
What are you on right now? You can't downgrade firmware.
Sent from my SCH-I545 using XDA Premium 4 mobile app
joshm.1219 said:
What are you on right now? You can't downgrade firmware.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just got a phone sent back from warranty and it's currently running on the MI1 firmware you can still used xposed framework and stuff if i were to root it right? Would you advise rooting now, or at what stage of firmware?
If you're in MI1 I wouldn't upgrade, it's the last build that you can still run safestrap on.
Sent from my SCH-I545 using XDA Premium 4 mobile app
joshm.1219 said:
If you're in MI1 I wouldn't upgrade, it's the last build that you can still run safestrap on.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So i can follow the MI1 root instructions and install safestrap , but will this void my warranty? i heard something about how something like a code change triggers a signal on their servers or something,to void warranty but is that with Knox?
Rooting your phone is technically voiding warranty, although there are ways to get back to complete stock. No servers are triggered and the rooting instructions will have you getrid of knox.
Sent from my SCH-I545 using XDA Premium 4 mobile app
joshm.1219 said:
Rooting your phone is technically voiding warranty, although there are ways to get back to complete stock. No servers are triggered and the rooting instructions will have you getrid of knox.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yeah, but there are "unroot" methods right? if i did that and had to use a warranty would they recognize it if i went back to stock recovery and unrooted? i've done a bit of research, only a little fuzzy now, jus cuz I started my saturday night a little early :victory: :good:

Leaked 4.4.2 for ATT S4

There is leaked copy of 4.4.2 for ATT with new a new bootloader
http://forum.xda-developers.com/showthread.php?t=2624782&page=10
This is NOT to be flashed on the Verizon variant, because you know somebody out there is going to want to try.
Sent from my SCH-I545
Running it right now.
Sent from my SAMSUNG-SGH-I337 using xda premium
skrazz said:
this is not to be flashed on the verizon variant, because you know somebody out there is going to want to try.
Sent from my sch-i545
Click to expand...
Click to collapse
because people are stupid!!!!!!!!!!!
A new bootloader means there's a good chance we may soon be able to flash custom recovers right?
Sent from my SCH-I545 using XDA Premium 4 mobile app
It is very doubtful unless they find an exploit that wasn't in the MK2 bootloader.
You can flash back to 4.3 after you flash this leak. It doesn't trip the qfuse. But once the official release is out that might change but yeah people on VZW should not flash this.
[email protected] said:
You can flash back to 4.3 after you flash this leak. It doesn't trip the qfuse. But once the official release is out that might change but yeah people on VZW should not flash this.
Click to expand...
Click to collapse
This might be good news. If the kernel changed for 4.4 and you can flash back devs might find a work around.
Sent from my SCH-I545 using Tapatalk

Categories

Resources