Was able to downgrade mi1 to mdk via odin - Verizon Samsung Galaxy S 4

I don't know if this is new but what happened was that I bought my Verizon s4 with build mi1.
I went full on noob rooted it and tried to flash twrp with goo manager. I soft bricked my phone I think as I was unable to boot and got the download screen with some red text saying it was unable to boot (don't remember the exact error).
So afterwards I searched for a stock firmware to reflash via Odin and I chose the mdk stock tar. I rebooted into download mode and got it to work. I'm now rooted on mdk with cwm recovery installed via loki method.
However when I install aosp roms I'm unable to receive and end calls. Just throwing the information out there, maybe it provides some insight or something. I'm now back on stock mdk with no issues.

---

jay876 said:
I don't know if this is new but what happened was that I bought my Verizon s4 with build mi1.
I went full on noob rooted it and tried to flash twrp with goo manager. I soft bricked my phone I think as I was unable to boot and got the download screen with some red text saying it was unable to boot (don't remember the exact error).
So afterwards I searched for a stock firmware to reflash via Odin and I chose the mdk stock tar. I rebooted into download mode and got it to work. I'm now rooted on mdk with cwm recovery installed via loki method.
However when I install aosp roms I'm unable to receive and end calls. Just throwing the information out there, maybe it provides some insight or something. I'm now back on stock mdk with no issues.
Click to expand...
Click to collapse
How the hell did you downgrade? As far as this community is concerned, there is no way to downgrade.
Sent from my SCH-I545 using xda app-developers app

---

jay876 said:
I don't know if this is new but what happened was that I bought my Verizon s4 with build mi1.
I went full on noob rooted it and tried to flash twrp with goo manager. I soft bricked my phone I think as I was unable to boot and got the download screen with some red text saying it was unable to boot (don't remember the exact error).
So afterwards I searched for a stock firmware to reflash via Odin and I chose the mdk stock tar. I rebooted into download mode and got it to work. I'm now rooted on mdk with cwm recovery installed via loki method.
However when I install aosp roms I'm unable to receive and end calls. Just throwing the information out there, maybe it provides some insight or something. I'm now back on stock mdk with no issues.
Click to expand...
Click to collapse
MANY others have tried, and have checked the code that checks the qfuses... So you are either mistaken, lying, or your phone is some amazing anomaly...
Nothing other then odin and a stock image? have a link to where you downloaded the image from?
Screen shot of about phone screen?

---

scryan said:
MANY others have tried, and have checked the code that checks the qfuses... So you are either mistaken, lying, or your phone is some amazing anomaly...
Nothing other then odin and a stock image? have a link to where you downloaded the image from?
Screen shot of about phone screen?
Click to expand...
Click to collapse
I'm not lying. It was ODIN/download mode with the green android logo with some red text saying the phone was unable to boot. I tried to flash the mdk tar in that state and it failed so I rebooted into download mode holding down the 3 buttons and it was flashed successfully.
I used this stock image - http://downloadandroidfiles.org/download-sch-i545_mdk_562219_stock_restore-zip/
requested screenshot -http://imgur.com/1IJEBB6

---

jay876 said:
I'm not lying. It was ODIN/download mode with the green android logo with some red text saying the phone was unable to boot. I tried to flash the mdk tar in that state and it failed so I rebooted into download mode holding down the 3 buttons and it was flashed successfully.
I used this stock image - http://downloadandroidfiles.org/download-sch-i545_mdk_562219_stock_restore-zip/
requested screenshot -http://imgur.com/1IJEBB6
Click to expand...
Click to collapse
Did you buy your phone used?
Sent from my SCH-I545 using Tapatalk

---

heath2805 said:
Did you buy your phone used?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Would be my second guess. I have seen people think their phone was downgraded after flashing an MDK radio.
Could this be the opposite, where the phone already had custom recovery I could see it having a stock Mi1 rom and showing Mi1 in the about phone while its still MDK base.
I'd love for this to be true, and don't mean to offend the OP... but this has been tried a ton of times and does not work, and its just so much more likely there is some confusion here rather then his phone simply not checking qfuses... Well, hopefully someone smarter than me will pick this apart tonight.

---

scryan said:
Would be my second guess. I have seen people think their phone was downgraded after flashing an MDK radio.
Could this be the opposite, where the phone already had custom recovery I could see it having a stock Mi1 rom and showing Mi1 in the about phone while its still MDK base.
I'd love for this to be true, and don't mean to offend the OP... but this has been tried a ton of times and does not work, and its just so much more likely there is some confusion here rather then his phone simply not checking qfuses... Well, hopefully someone smarter than me will pick this apart tonight.
Click to expand...
Click to collapse
Yeah but the scary thing is I don't recall ever seeing a MI1 stock build for mdk users.
Sent from my SCH-I545 using Tapatalk

---

heath2805 said:
Did you buy your phone used?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
yea it was slightly used. When I checked it out it had the mi1 firmware and I think someone tried to root it because it had terminal emulator and superuser installed. I ran root checker and it did not have root access so it was a failed attempt.
I factory reset everything at that point though then that's where my story began. Rooted, rom manager > goo manager > soft brick (odin/download mode) > flashed mdk stock > root > loki bypass bootloader for cwm > aosp rom issues with receiving and ending calls > stock with custom recovery
When I downloaded rom manager, I didn't know at the time that mi1 firmware was unable to get a custom recovery installed.

---

Could he have purchased used developers s4?

---

jamesd1085 said:
Could he have purchased used developers s4?
Click to expand...
Click to collapse
That's probably it. Now that it has a non-developer bootloader, it's now bootloader locked.

---

k1mu said:
That's probably it. Now that it has a non-developer bootloader, it's now bootloader locked.
Click to expand...
Click to collapse
It was previously a vrudmi1 bootloader. I don't think that's a dev unit. If it was a dev unit wouldn't I have been able to install the custom recovery successfully before right after rooting? Blah I guess it was a stroke of luck somewhere.

---

k1mu said:
That's probably it. Now that it has a non-developer bootloader, it's now bootloader locked.
Click to expand...
Click to collapse
Yeah...but seems like once surge gets the rest of the missing parts for his dev mdk tar he should be able to flash it back to dev

---

jay876 said:
It was previously a vrudmi1 bootloader. I don't think that's a dev unit. If it was a dev unit wouldn't I have been able to install the custom recovery successfully before right after rooting? Blah I guess it was a stroke of luck somewhere.
Click to expand...
Click to collapse
No, it was previously a MI1 build That's not the same as a MI1 bootloader.
You can have a MDK phone running a MK2 ROM. The build will show MK2 even though it's an older bootloader.

---

k1mu said:
No, it was previously a MI1 build That's not the same as a MI1 bootloader.
You can have a MDK phone running a MK2 ROM. The build will show MK2 even though it's an older bootloader.
Click to expand...
Click to collapse
Oh ok. Thanks. I didn't know that could be the case.

---

jay876 said:
Oh ok. Thanks. I didn't know that could be the case.
Click to expand...
Click to collapse
Well lets just make sure. Open terminal and type the following:
Code:
su
mount -o remount, rw /system
echo ON >/efs/carrier/HiddenMenu
Then dial *#1234# and post back with a screenshot of that screen

---

Surge1223 said:
Well lets just make sure. Open terminal and type the following:
Code:
su
mount -o remount, rw /system
echo ON >/efs/carrier/HiddenMenu
Then dial *#1234# and post back with a screenshot of that screen
Click to expand...
Click to collapse
http://imgur.com/uPmLbok

---

jay876 said:
http://imgur.com/uPmLbok
Click to expand...
Click to collapse
Hmm...looks like good ole run of the mill MDK...keep it...hard to get anymore

---

jay876 said:
http://imgur.com/uPmLbok
Click to expand...
Click to collapse
Okay, that was unexpected. Tell me how do you know for sure you were on VRUDMI1? Do you have a back up from then?
Open terminal post the output of the following commands:
Code:
su
cat /proc/version
cd /dev/block/platform/msm_sdcc.1/by-name
hexdump -C aboot|grep SW_ID

---

And since this has already caught surge's attention... He may be able to verify that flashing MDK modem +hlos bin may fix your aosp issues...

---

Surge1223 said:
Okay, that was unexpected. Tell me how do you know for sure you were on VRUDMI1? Do you have a back up from then?
Open terminal post the output of the following commands:
Code:
su
cat /proc/version
cd /dev/block/platform/msm_sdcc.1/by-name
hexdump -C aboot|grep SW_ID
Click to expand...
Click to collapse
Can't really figure out whats going on here..
First of all if you tried to flash MDK via odin on a MI1 BL you should have gotten an error "SW REV. CHECK FAIL: FUSED: 4, Binary: 1"