Is there currently any ROM that works on MDK, let's me keep root, and doesn't update the boot loader so I can always revert back? For 5.0.1, that is.
I second this. All of the flash instructions seem to assume you're using Safestrap, or coming from a build later than mdk.
For the "lucky" few of us still running rooted mdk, is there a rooted OC1 zip we can flash in recovery, the old-fashioned way?
MDK
SamXp said:
I second this. All of the flash instructions seem to assume you're using Safestrap, or coming from a build later than mdk.
For the "lucky" few of us still running rooted mdk, is there a rooted OC1 zip we can flash in recovery, the old-fashioned way?
Click to expand...
Click to collapse
The MDK 5.0.1 is here http://forum.xda-developers.com/gal...ment/rom-i545oc1-5-0-1-100-stock-mdk-t3097902
I'm still watching everyone's experience before flashing this myself.
Related
Hi,
So I have a SGS4 with ME7 and and unlocked bootloader. I am looking to upgrade to MJ7(4.3?) and be able to keep my full root. Is there a good way to do such a thing yet? Most info I see says MJ7 is only for safe strap, I have a custom recovery so I am not sure if it will work or if it is worth it. Please advise and help me....
Thank you in advance!!!
If you are on ME7 you only have safestrap, which is not available for MJ7. MJ7 upgrade while retaining root is covered in the general section of this site. There are files you need to download and first install MI1. There are no rom options but the benefit of a rom are little on ME7 as you can't get off TW and are stuck on 4.2.2 becaise of kernel limitations.
Read a bit but I took the update from ME7 after losing MDK due to insurance replacement. Only if you really have a custom recovery such as TWRP or CWM on MDK are you losing much.
Sent from my SCH-I545 using Tapatalk
kdo23 said:
If you are on ME7 you only have safestrap, which is not available for MJ7. MJ7 upgrade while retaining root is covered in the general section of this site. There are files you need to download and first install MI1. There are no rom options but the benefit of a rom are little on ME7 as you can't get off TW and are stuck on 4.2.2 becaise of kernel limitations.
Read a bit but I took the update from ME7 after losing MDK due to insurance replacement. Only if you really have a custom recovery such as TWRP or CWM on MDK are you losing much.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I have CWM Touch Recovery V1.0.3.5 with my ME7 phone so it sounds like I should probably not take the update... I am pretty sure I don't have safestrap. I was on MDK then updated to ME7 and kept my unlocked bootloader and root. I just wish there was a way I could get 4.3 or 4.4... I will keep reading and searching... Thank you.
sonnycohopie said:
I have CWM Touch Recovery V1.0.3.5 with my ME7 phone so it sounds like I should probably not take the update... I am pretty sure I don't have safestrap. I was on MDK then updated to ME7 and kept my unlocked bootloader and root. I just wish there was a way I could get 4.3 or 4.4... I will keep reading and searching... Thank you.
Click to expand...
Click to collapse
You updated the radio I take it? That will show you on ME7 but have the MDK bootloader. Thus leaving your TWRP intact.
So anyway, I'm looking for the same thing. Not happening right now
kdo23 said:
If you are on ME7 you only have safestrap, which is not available for MJ7. MJ7 upgrade while retaining root is covered in the general section of this site. There are files you need to download and first install MI1. There are no rom options but the benefit of a rom are little on ME7 as you can't get off TW and are stuck on 4.2.2 becaise of kernel limitations.
Read a bit but I took the update from ME7 after losing MDK due to insurance replacement. Only if you really have a custom recovery such as TWRP or CWM on MDK are you losing much.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Up until today I had ME7 *with* CWM Recovery. I have no idea how that happened but I think it had something to do with flashing Hyperdrive while I was on MDK. I flashed a ton of ROM's through CWM since having ME7. However, lately I started to have a few bugs that seemed to carry over even after flashing a new ROM (like intermittent boot loops) so I decided to go back to a factory image (without knowing the limitations of ME7). Since I was on ME7, my understanding is that I had to flash an ME7 factory image, which I did and *now* I can't get recovery back, aside from Safestrap. It's a bit of a bummer but I just wanted to post to point out that it is possible to have ME7 and a custom recovery, it just seems like it isn't possible to flash a custom recovery *after* you have ME7. If you got it, keep it.
Super Sam Galaxy said:
Up until today I had ME7 *with* CWM Recovery. I have no idea how that happened but I think it had something to do with flashing Hyperdrive while I was on MDK. I flashed a ton of ROM's through CWM since having ME7. However, lately I started to have a few bugs that seemed to carry over even after flashing a new ROM (like intermittent boot loops) so I decided to go back to a factory image (without knowing the limitations of ME7). Since I was on ME7, my understanding is that I had to flash an ME7 factory image, which I did and *now* I can't get recovery back, aside from Safestrap. It's a bit of a bummer but I just wanted to post to point out that it is possible to have ME7 and a custom recovery, it just seems like it isn't possible to flash a custom recovery *after* you have ME7. If you got it, keep it.
Click to expand...
Click to collapse
You didn't have stock me7 which was my meaning. You had an me7 rom I think is what you're saying.
Sent from my SCH-I545 using Tapatalk
kdo23 said:
You didn't have stock me7 which was my meaning. You had an me7 rom I think is what you're saying.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Well, it wasn't stock ME7 for sure. I think it changed to ME7 when I first flashed Hyperdrive, but was that way for a while on every ROM I flashed after Hyperdrive so whatever change Hyperdrive made seemed to be permanent. Or else I may have just been flashing ROM's that were ME7 by coincidence - do all ROM's explicitly set the baseband or do some just use whatever is already on the device? I don't really understand basebands too well. Anyway, sorry about the mix-up, I wasn't aware you were referring to stock. I sure hope that someone is able to figure out a workaround that allows for a custom recovery because I really like KitKat and I suppose we won't be seeing any TW based KitKat ROM's until Samsung releases an update first. My understanding is that Safestrap only works with TW.
I find a certain degree of irony in the fact that I've never permanently damaged a device when rooting or flashing ROM's (which is pretty good for a noob like me), yet I've done something even worse just by inadvertently allowing an update that came straight from the manufacturer! Why do they have to make things so complicated? :crying:
Super Sam Galaxy said:
Well, it wasn't stock ME7 for sure. I think it changed to ME7 when I first flashed Hyperdrive, but was that way for a while on every ROM I flashed after Hyperdrive so whatever change Hyperdrive made seemed to be permanent. Or else I may have just been flashing ROM's that were ME7 by coincidence - do all ROM's explicitly set the baseband or do some just use whatever is already on the device? I don't really understand basebands too well. Anyway, sorry about the mix-up, I wasn't aware you were referring to stock. I sure hope that someone is able to figure out a workaround that allows for a custom recovery because I really like KitKat and I suppose we won't be seeing any TW based KitKat ROM's until Samsung releases an update first. My understanding is that Safestrap only works with TW.
I find a certain degree of irony in the fact that I've never permanently damaged a device when rooting or flashing ROM's (which is pretty good for a noob like me), yet I've done something even worse just by inadvertently allowing an update that came straight from the manufacturer! Why do they have to make things so complicated? :crying:
Click to expand...
Click to collapse
Baseband is separate, your rom base is what we were referring to. The baseband change happened with a file you flashed for sure but likely not hyperdrive but a radio file. With a custom recovery you could have had mj7 baseband and custom recovery. Look at build number in the future.
Sent from my SCH-I545 using Tapatalk
Edit: build number can change too with a rom. Mdk is the only starting stock firmware which can be exploited to allow a custom recovery. Since you had one it meant you rooted on mdk and should not have odined to a later release.
Super Sam Galaxy said:
Up until today I had ME7 *with* CWM Recovery. I have no idea how that happened but I think it had something to do with flashing Hyperdrive while I was on MDK. I flashed a ton of ROM's through CWM since having ME7. However, lately I started to have a few bugs that seemed to carry over even after flashing a new ROM (like intermittent boot loops) so I decided to go back to a factory image (without knowing the limitations of ME7). Since I was on ME7, my understanding is that I had to flash an ME7 factory image, which I did and *now* I can't get recovery back, aside from Safestrap. It's a bit of a bummer but I just wanted to post to point out that it is possible to have ME7 and a custom recovery, it just seems like it isn't possible to flash a custom recovery *after* you have ME7. If you got it, keep it.
Click to expand...
Click to collapse
Absolutely impossible to have a custom recovery on an ME7 boot loader. You could've flashed a ME7 radio or a ME7 based rom such as HyperDrive but your boot loader is still MDK. Which is why you lost your recovery, you flashed the wrong factory image.
Sent from my SCH-I545 using XDA Premium 4 mobile app
kdo23 said:
Baseband is separate, your rom base is what we were referring to. The baseband change happened with a file you flashed for sure but likely not hyperdrive but a radio file. With a custom recovery you could have had mj7 baseband and custom recovery. Look at build number in the future.
Sent from my SCH-I545 using Tapatalk
Edit: build number can change too with a rom. Mdk is the only starting stock firmware which can be exploited to allow a custom recovery. Since you had one it meant you rooted on mdk and should not have odined to a later release.
Click to expand...
Click to collapse
I figured out the part about not flashing to a later release after the fact, unfortunately. It was simply a matter of not thoroughly researching and it's a pretty big bummer now because I can't flash! But I suppose worse things can come of not researching, like bricking and thankfully that hasn't happened yet (though I'm certainly going go be more careful in the future). Thanks for explaining about all the baseband/radio stuff, that is a bit over my head. Sure hope an exploit for ME7 (or a way to revert to MDK) is found soon, though from the sound of it that isn't likely.
Hi All,
I picked up an MI1 GS4 a month ago and after a few nights of scrolling through the forums I was able to get HD 10.2 loaded onto my phone via Safestrap. During the root process, I got a little bit a head of myself and flashed a custom recovery. After some research (and a presumed brick scare) I found that there is no way to get CWM recovery on the phone. While it's a major disappointment, it is what it is. So I have two questions:
So right now, my phone doesnt have a recovery and if I try to boot into it, it will go into Odin mode and give me some sort of an error. I assume I need to flash a new recovery through Odin, but am wondering if someone could point me in the direction of the correct file.
Is MJ7 the latest OTA from VZW? Should I wipe my device completely, go back to stock, and take the latest OTA? From what I am gathering, safestap is now working on MJ7, but I want to be sure that is what I will get to if I take the OTA. If I do want to take the OTA, how would I go about doing this and is the problem listed above an issue?
Thanks!
madtomatoes said:
Hi All,
I picked up an MI1 GS4 a month ago and after a few nights of scrolling through the forums I was able to get HD 10.2 loaded onto my phone via Safestrap. During the root process, I got a little bit a head of myself and flashed a custom recovery. After some research (and a presumed brick scare) I found that there is no way to get CWM recovery on the phone. While it's a major disappointment, it is what it is. So I have two questions:
So right now, my phone doesnt have a recovery and if I try to boot into it, it will go into Odin mode and give me some sort of an error. I assume I need to flash a new recovery through Odin, but am wondering if someone could point me in the direction of the correct file.
Is MJ7 the latest OTA from VZW? Should I wipe my device completely, go back to stock, and take the latest OTA? From what I am gathering, safestap is now working on MJ7, but I want to be sure that is what I will get to if I take the OTA. If I do want to take the OTA, how would I go about doing this and is the problem listed above an issue?
Thanks!
Click to expand...
Click to collapse
safestrap is a recovery of sorts, so what you are saying, you rooted, installed safestrap, installed HD10.2 than installed a recovery on top of that like CWM? So you soft bricked your phone?
Your only recourse is odin the full wipe stock image back and start over.
I suggest a thorough reading of the forum threads here first so you know better what to do.
I have a guide in the general forum here that lists steps to go from ME7 to MJ7 and root, install safestrap 3.65 and HD11....I'm not sure how it would play with your MI1 base phone so proceed at your own risk
decaturbob said:
safestrap is a recovery of sorts, so what you are saying, you rooted, installed safestrap, installed HD10.2 than installed a recovery on top of that like CWM? So you soft bricked your phone?
Click to expand...
Click to collapse
The other way around. I first rooted and attempted to install CWM. After that failed, I read further and discoved that only MDK roms are truly unlocked. From that point, I installed safestrap and HD. My phone is functional right now, I just have no way of getting into the stock recovery.
It's my understanding that I will need to use Odin to flash the stock MI1 image. I just want to confirm what happens from there. After flashing the stock image, I will be stock MI1, unrooted, with the opportunity to OTA to MJ7 (?). From that point, I'll take the OTA, re-root, reinstall safestrap, and finally HD11/12. Is all of this correct?
Thanks
madtomatoes said:
The other way around. I first rooted and attempted to install CWM. After that failed, I read further and discoved that only MDK roms are truly unlocked. From that point, I installed safestrap and HD. My phone is functional right now, I just have no way of getting into the stock recovery.
It's my understanding that I will need to use Odin to flash the stock MI1 image. I just want to confirm what happens from there. After flashing the stock image, I will be stock MI1, unrooted, with the opportunity to OTA to MJ7 (?). From that point, I'll take the OTA, re-root, reinstall safestrap, and finally HD11/12. Is all of this correct?
Thanks
Click to expand...
Click to collapse
that sounds about right. When you do HD12, be sure you have the safestrap version....
I just recently rooted and flashed CM11 on my little brothers phone because well.. I could.. So yeah I basically had to! But I would kiiiillll for baseband MDK at the moment. Is their any way to get that? Or at least get CM on a me7, Other than looking to buy an old phone..
Nope
Unfortunately CM is out of reach for you. In order to run it you must have the MDK bootloader. It is the only one that can be exploited (via loki) to allow the installation of a custom recovery such as CWM or TWRP. Without one of those you cannot flash CM. Safestrap will not allow the use of CM.
Does that mean, if I Odin back MDK and take the Loki approach - can I install CM11 then?
You are unable to Odin back to MDK once you have upgraded.
jmgib said:
You are unable to Odin back to MDK once you have upgraded.
Click to expand...
Click to collapse
This is correct. And if you do try at best the process will fail and you will reboot to where you were before, worse case you risk bricking your device.
Hi everyone, I haven't been active in awhile, and decided to upgrade from 4.4.4 to 5.0.1.
Device is:
Verizon Galaxy S4
MDK / Loki
TWRO 2.8.7.0
was on 4.4.4
I used the FlashFire upgrade method, because I wanted to have that upgrade modem, baseband etc. everything I needed.
Prior to root, I upgraded my TWRP, I did a TWRP backup.
I downloaded Odexed 5.0.1 stock update from the thread, and followed the instructions, it installed but on final reboot, it just got stuck at the Samsung / Custom screen. When I went to boot into recovery, it's now the stock system recovery LRX22c.I545VRUG0C1
Gives an error on the bottom as
Code:
#MANUAL MODE#
Appling Multi-CSC
Applied The CSC-code: VZW
remove failed file /system/csc_contents/ (read only file system)
If I try to apply update via external storage, using stock update I get:
Code:
footer is wrong
signature verification failed
Anyway I can flash TWRP via adb, then just re-flash the rom with loki manually? Or anyway without having to use odin and downgrade? I won't lose loki root will I? What do I do? Thanks in advanced.
well I'm trying to flash back to MDK via odin, and I keep getting aboot.img failure.. i'm really at a loss here, I can't even odin back to MDK.
notstevek said:
well I'm trying to flash back to MDK via odin, and I keep getting aboot.img failure.. i'm really at a loss here, I can't even odin back to MDK.
Click to expand...
Click to collapse
What instructions did you use? SS and FF were made specifically for locked bootloaders so they require a different instructions for flashing. You basically ignored the benefits of being on MDK by doing whatever you did. Doesn't sound like you're on MDK anymore and I need more details to help. Someone else might be able to help you.
If all you wanted was the OC1 modem, could have just flashed it from here. People have reported issues with TWRP versions above 2.8.4.0-jfltexx.
Neffy27 said:
What instructions did you use? SS and FF were made specifically for locked bootloaders so they require a different instructions for flashing. You basically ignored the benefits of being on MDK by doing whatever you did. Doesn't sound like you're on MDK anymore and I need more details to help. Someone else might be able to help you.
If all you wanted was the OC1 modem, could have just flashed it from here. People have reported issues with TWRP versions above 2.8.4.0-jfltexx.
Click to expand...
Click to collapse
The tutorial said for mdk, I followed it exactly and it didn't work. I then ****ed up by flashing lollipop through stock recovery so it flashed the new baseband, and I removed loki. That's my bad, however I did follow the instructions and it didn't work. I should have just flashed 5.1 manually. Oh well. Is there safestrap for lollipop, or a way to downgrade to me7 to use safestrap?
Sent from my SCH-I545 using Tapatalk
SS isn't compatible with Lollipop. Recommend switching to FF, apparently it can flash Stang's ROM on stock OC1. Still need root. Or look into MultiSystem but I'm not knowledgeable with them but hear of success with them.
Sent from my SCH-I545 using Tapatalk 2.4.15
You can use king root to get root, then search for instructions to swap to supersu. From here should be able to install FF.
Good luck.
Sent from my SCH-I545 using Tapatalk 2.4.15
I'm currently rooted on 4.3 MJ4. Yes I'm outdated and decided to finally update. I'm going to flash to stock 4.3 MJ4. My questions is, after I flash to stock 4.3 MJ4. Can I flash NC5 from MJ4? Or would I have to do it in these steps ( MJ4 then NAB then NC5? ).
Why not PH1? If you're wanting to stay with KK, NK4 is the last I believe. NH7 is the one most people used. Just trying to find out what you're trying to achieve
Also, if you're flashing a stock ROM, you don't need to first flash MJ4. Just flash what you want.
evilvoice said:
Why not PH1? If you're wanting to stay with KK, NK4 is the last I believe. NH7 is the one most people used. Just trying to find out what you're trying to achieve
Also, if you're flashing a stock ROM, you don't need to first flash MJ4. Just flash what you want.
Click to expand...
Click to collapse
Awesome! Thanks! I am trying to flash a stock rom, but thought I would need to go in steps instead of instantly flashing to the most current version.
As for my plan: I'm rooted and on a custom rom. I want to go back to stock rom and then root again and flash to either cm12.1 or cm13. From what I've read, I cant flash to either cyanogenmod roms until I was on either lollipop or higher. I was also thinking, would it work if I was to flash a rooted current version of a stock rom, that way I don't have to flash a stock rom and break root and have to root it again?
For better results, I would flash a full PH1 rom and root, then install whatever rom you want. Usually they want the bootloader to be upgraded to lollipop and that really only happens when either flashing a full Odin rom or a bootloader image. Doing only the bootloader doesn't upgrade anything else and may cause issues.
evilvoice said:
For better results, I would flash a full PH1 rom and root, then install whatever rom you want. Usually they want the bootloader to be upgraded to lollipop and that really only happens when either flashing a full Odin rom or a bootloader image. Doing only the bootloader doesn't upgrade anything else and may cause issues.
Click to expand...
Click to collapse
What is the PH1 rom? I've already flashed to stock NC5 so far and lost root.
It's the latest rom. I don't think an Odin has been posted, but you can grab from the Samsung firmware site. Load that, then root by flashing TWRP and boot into recovery and flash SuperSU. Done.
evilvoice said:
It's the latest rom. I don't think an Odin has been posted, but you can grab from the Samsung firmware site. Load that, then root by flashing TWRP and boot into recovery and flash SuperSU. Done.
Click to expand...
Click to collapse
EDIT: I went ahead and used the Full Restore. Fortunately, it did not WIPE any data. YEAH! And it looks like I am on my way to an updated NOTE3.
Hello. My Note3 is on 4.3. It was rooted a couple of years ago, but out of use since Oct 2015. I still want to use the Note3 for non-cell phone operations, browsing, camera, etc. I want to upgrade, but the OTA is locked out.
I am lost on all of the many, many posts on how to updated a rooted Note3, but most of them are outdated. I have it mostly backed up as far as handwritten notes, photos, etc. But I don't really want to have to start from scratch if I don't have to.
I am currently reviewing rwilco's one click options. There are two software packages listed in his directory. One of them is dated 02/27/15 and is called nodata restore. Will this keep from wiping the phone as opposed to the fullrestore exe posted 04/12/14 vs the tar posted 02/27/15.
I am not a complete dodo, but I am having a hard time getting this phone unrooted and updated.
Thanks for any detail instructions or links to the best way to update this as of 9/5/2016!!!
Everything you need to know is explained here. http://forum.xda-developers.com/galaxy-note-3/general/guide-how-to-disable-air-command-pop-t2960839
Sent from my SM-N920C using XDA-Developers mobile app