I have another S5 I am running 4.4.2 on and would like to load the MOAR Rom to it. How can I do this and get around the Verizon warning about unapproved software? My phone is rooted and had Safestrap 3.75 right now. I tried to load the MOAR Rom via safestrap and got the unapproved software warning. Thanks! I am a noob with fighting these super locked down things from VZW.
I would lke to know the same thing
This is my recommendation as to i don't care to flash anything higher than OD5. You can flash Muniz_ri's to OC4 and keep root ROM and from there flash away to any ROM in this Forum section and update the firmware by flashing the latest firmware NO Bootloader Zips. Again that's what I do and haven't had any issues and i can Odin back to NCG and "officially" run a KK ROM. Also, I'm currently running the MOAR ROM and on the latest firmware which is PB1. Was running Jrkruse's Norma Note5 ROM but went back to MOAR for the moment....
Related
Hello, I've been out of the rooting scene for over a year now since I bought my Galaxy S4. When I first bought it, i had it rooted but could not install a custom rom because it was on MF3. So, once again I am trying to get back into rooting with the latest OTA update and a NC1 baseband. I've been looking around on how to root and install a custom rom but I've been gone so long that I'm just lost.
From threads I have read I can downgrade my phone to NB1 then to MK2 to root. However, I haven't really been able to find an answer to if I can install a custom rom to it, only upgrading back to the OTA and keeping root. I have been having massive overheating problems with the stock firmware and have a large burn mark on the back of my phone and would like to switch back to CWM which i had on an old phone.
Laemon said:
Hello, I've been out of the rooting scene for over a year now since I bought my Galaxy S4. When I first bought it, i had it rooted but could not install a custom rom because it was on MF3. So, once again I am trying to get back into rooting with the latest OTA update and a NC1 baseband. I've been looking around on how to root and install a custom rom but I've been gone so long that I'm just lost.
From threads I have read I can downgrade my phone to NB1 then to MK2 to root. However, I haven't really been able to find an answer to if I can install a custom rom to it, only upgrading back to the OTA and keeping root. I have been having massive overheating problems with the stock firmware and have a large burn mark on the back of my phone and would like to switch back to CWM which i had on an old phone.
Click to expand...
Click to collapse
No CWM. You can only use Safestrap, a variant of TWRP for locked bootloaders that doesn't flash kernels. Due to that restriction (if we tried to flash a custom kernel we'd get bootloader check fails) we can only run ROMs which the stock kernel supports, meaning other Touchwiz ROMs and the one GPE that's been posted in the General section. Part of the downgrade and root process is using Safestrap to update to 4.4.2 with a modified OTA, and so you just replace that step with flashing a ROM, the kernel modules, and then the ODIN files.
I just purchased an unlocked stock I337 S4 from Ebay that I intend to send to the Phillipines for my fiancee. It currently has MK2 firmware. I would like to upgrade it to OC4 before I send it overseas. I tried using ODIN to flash it to OC4, but it fails.
I managed to root it using Saferoot, and that worked except now it has a lock icon and says CUSTOM on the boot screen, but it still boots fine.
Anyway, I have been reading through this forum for about 3 hours now, and have found no sensible way to update this phone. Even if I could just update it to 4.4.4 I would be happy. Do I have to upgrade it step by step through all the firmware updates? Do I really need to have Safestrap installed to do a stock upgrade from a stock ROM?
Any links that could be provided to make this an easy process would be most appreciated..
You're so close. http://forum.xda-developers.com/showthread.php?t=2616221
Snapping along on stock rooted 0C4 I337, wishing for some good up to date lollipop ROM's to throw into flashfire
I currently have AT&T stock (I used to have a custom ROM then had to flash to stock ROM to be able to flash to another custom ROM--however, I accidentally flashed a newer version of the AT&T stock ROM which locked my bootloader and I could no longer flash to a custom ROM). I updated my AT&T stock ROM recently and now my back/menu buttons don't work, so I want to see if I can flash to a custom ROM now.
I don't remember the procedure to flash a custom ROM--do I first need to get root in order to unlock the bootloader to be able to flash ROMs (i.e. if I have root then I am guaranteed to be able to unlock bootloader in order to flash ROM)? Is the baseband version the only thing that determines whether I can unlock the bootloader and then be able to flash ROMs?
I currently have OK2 as broadband version and checked one of the stickied threads which said this:
" ROOT
OK2 -- No direct root method. Must Odin OC4 kernel, use Kingroot, then Odin OK2 kernel back."
Does that mean what I have to do is use Odin to get OC4 kernel, then use Kingroot, then Odin OK2 kernel and then I will be able to have root, which means I can then unlock my bootloader and be able to flash to ANY ROM (not just TouchWiz-based ROMs)? Is there anything else I need to consider or is this 100% foolproof? In the future, what should I be careful of in order to prevent getting my bootloader locked again--just that I don't flash a stock (AT&T) ROM that is known to lock back the bootloader?
Thank you all!
There's no way to unlock the bootloader if you have updated your device to the lastest firmware version. The only thing you can do is flash SafeStrap and use Stock Kernel Based ROMs which are compatible with Safestrap.
As regards to the procedure of rooting an OK2 firmware, I'm afraid I won't be able to help you.
Have a happy new year.
mindstormer said:
...however, I accidentally flashed a newer version of the AT&T stock ROM which locked my bootloader ...
Click to expand...
Click to collapse
I was just about to sit down and flash a stock ROM. Can you explain what you mean by this? Did you flash OK2 and it caused you a problem?
smock9 said:
I was just about to sit down and flash a stock ROM. Can you explain what you mean by this? Did you flash OK2 and it caused you a problem?
Click to expand...
Click to collapse
It was a while ago but I used to have I believe an MDL broadband version which meant I could flash any ROM available. I tried a different ROM, didn't like it, then decided to flash back to the stock ROM but accidentally flashed a newer version of it, which meant that my bootloader is now locked. With a locked bootloader, apparently I can only flash to a newer stock ROM (not other ROMs like Cyanogenmod) via Safestrap.
I think if you don't have the MDL broadband version you shouldn't worry about it anyway because it is locked and you will only be limited to flashing stock ROMs.
Slight correction
The previous entry is not entirely correct. Like the OP, I was originally on an unlocked bootloader on my i337. I'd purchased my i337 on the first day and eschewed OTA updates. I wanted to try a touchwiz based ROM, Hyperdrive, and in doing so I recall flashing the stock NB1 firmware. Every firmware beginning with NB1 has a locked bootloader and there has been no progress for more than a year in unlocking the bootloader again. This can limit you to either stock ROMs OR other touchwiz based ROMs like Hyperdrive. I love the Hyperdrive ROM (now on release 21) but its developer has moved on to a newer phone, so it's stuck at Android 4.4.2 and no one has picked up the project in many months. There are several other touchwiz based ROMs for the i337 version of the S4 which I have also tried but I prefer Hyperdrive's myriad customization, even without proper patching. I'll be moving on soon to the Nexus 6P as my daily driver, but would very much like to keep my S4 up to date with a custom ROM. Given the number of people that have been in this same situation, where a newer stock ROM from AT&T locked a previously unlocked bootloader, it's been surprising that the issues have not been overcome on a phone as popular as the Galaxy S4 was and continues to be. I've seen unlocked versions of the S4 selling for just under $400 in the last week of 2015.
Use the desktop version of Kingoroot to root and use Super su and update the binary. Don't forget to hit thanks if this helped.
The bootloader for the at&t s4 was never unlocked. The MDL bootloader had a flaw in it that allowed you to use LOKI which is a lock bypass, not a way to unlock the bootloader.
Install Custom Recovery Samsung Galaxy AT&T S4 SGH-I337 Ver 5.0.1 Non-Rooted. OK2
Hello, I Want to do some modifications to my Samsung Galaxy S4 and Have so many questions that I am not sure were to start? Yes I'm a noob but learning. I have a SGH-I337 phone that is unlocked so I use it for T-mobile. The phone came with KitKat 4.4.2 NB1 firmware but I managed to update it manually to the latest firmware OK2.
What I would like to do is install a custom recovery and install a clean non bloated Rom. Maybe a custom such as CyanogenMod? Questions: Is there any recovery software that will work on my present upgraded phone such as Safestrap, TWARP,PhilZ or CWM and in doing so I am guessing I need to root my phone first? When you root a phone does that unlock the boot loader? I have read articles saying you can only install custom recovery on the older firmware such as kitkat 4.4.2. or unless a update comes out. I also have read articles that I cannot downgrade and am not sure what that means as I have read articles that I can use Odin and reinstall my stock firmware NB1 is that true? Is there a way to downgrade your upgrades?
I see a lot of articles how to install recovery software but they do not always say what firmware version they are installing it to so I wont even try it. I am guessing-it is the older firmware 4.4.2.
I have read I can flash my kernel to an older Kernel such as NB1 then root it install a custom recovery then upgrade the kernel again? Not sure it I can upgrade or downgrade kernels that are for my phone?
I did manage to root my phone awhile back when it had kitkat 4.4.2 NB1 but had problems later on with my touch screen going crazy as if someone was in my phone so I brought it back to stock by using Odin and reinstalling NB1 firmware hoping to fix the problem. After installing stock firmware I decided to upgrade to lollipop 5.0.1 OB2 and that is were I am now. About my touch screen going crazy I have been reading it may be due to cheap USB chargers which I am using but that is another story.
Well any-help or leads would be appreciated.
Maybe if I wait long enough someone will come up with a custom ROM for my latest firmware as well as rooting it?
Steve
I was rooted, running sacs custom rom v5.6, an android 4.3 rom on mk2 baseband and firmware. It's been on these BB/FW for a long while now.
Sounds stupid as I type it out, but I want to play pokemon go. It requires 4.4.2 or newer android.
I went to sammobile and downloaded the newest stock, ok3.
I flashed it with Odin and it took, booted right up. I go to check BB and FW, still on mk2. Using the menu to try and get it to update the BB and FW doesn't do anything other than tell me I have the newest version. I can't flash this custom ROM I want unless I am on one of the newest firmwares.
Wll, I got angry and flashed stock mja. It's currently sitting on the yellow Sprint screen, it's only been about 5 minutes so far so I might give it a chance for the next few minutes... (25 minutes later I gave up and reflashed ok3)
How bad did I mess up?
Can I go back to stock mk2 and have it update itself to ok3 (or download and flash manually with Odin)?? I briefly looked but I couldn't find any ok3 modem only, and I was under the impression that I needed the full firmware to get the newest TW ROMS working anyway.
Download mode shows knox is 0x0.
What can I do to get it updated fully? I can root and flash again after updating if needed. Any help is greatly appreciated.
I flashed ok3 in odin again and am now on ok3 baseband and firmware.