Hi trying to understand whether i can install custom ROM or not. I have i337ucufni1 baseband and according to terminal emulator i have the same bootloader (NI1)? How do I know if this is a locked bootloader or not so I can Root/Install custom ROM?/
Please advise,
Locked Bootloader
hol64 said:
Hi trying to understand whether i can install custom ROM or not. I have i337ucufni1 baseband and according to terminal emulator i have the same bootloader (NI1)? How do I know if this is a locked bootloader or not so I can Root/Install custom ROM?/
Please advise,
Click to expand...
Click to collapse
It is locked. But with safestrap it can be unlocked and rooted with Towelroot. A custom rom can be tricky as it must you Touchwiz same as stock firmware. Maybe someone else can give you more details.
Just to add on to TailGunner. They are all locked but the early bootloaders, of which you are not, can use an exploit called loki-doki to bypass Sammy's security checks.
Start here--
http://forum.xda-developers.com/galaxy-s4-att/general/summary-rooting-roming-i337-t2872013
You will need SafeStrap, no custom recoveries, kernels etc.
Read carefully so as not to brick anything.
Oh, BTW MODS will move this to Q&A--
Good Luck--:good:
All you need to know http://forum.xda-developers.com/showthread.php?t=2616221
Related
Hello, I have a Rogers Canada SGH-I337M rooted running 4.4.2 I337MVLUFNE1 and I would like to try custom roms on my phone but I have never tried doing this before and I don't know what custom recovery I can use with this baseband version. I was going to try Safestrap but the versions for it that I saw on its XDA page were for NB1, MK2, and MF3 baseband versions. Will the latest version of Safestrap be compatible with my phone, or will I need to downgrade/upgrade my android version to get a different baseband version? If I will need to do so, would I need to unroot or make changes before changing the android version? Help would be greatly appreciated.
amb240 said:
Hello, I have a Rogers Canada SGH-I337M rooted running 4.4.2 I337MVLUFNE1 and I would like to try custom roms on my phone but I have never tried doing this before and I don't know what custom recovery I can use with this baseband version. I was going to try Safestrap but the versions for it that I saw on its XDA page were for NB1, MK2, and MF3 baseband versions. Will the latest version of Safestrap be compatible with my phone, or will I need to downgrade/upgrade my android version to get a different baseband version? If I will need to do so, would I need to unroot or make changes before changing the android version? Help would be greatly appreciated.
Click to expand...
Click to collapse
Safestrap is primarily for the phones with a locked bootloader because we are not able to flash any other type of recovery. Since your bootloader is not locked, you should use philz touch or TWRP. That way you'll be able to flash kernels, as well.
Best advice I can give you is to read before flashing anything that way you know what you are getting yourself into. Since you are i337M, I would start with this thread... http://forum.xda-developers.com/showthread.php?t=2314494
guut13 said:
Safestrap is primarily for the phones with a locked bootloader because we are not able to flash any other type of recovery. Since your bootloader is not locked, you should use philz touch or TWRP. That way you'll be able to flash kernels, as well.
Best advice I can give you is to read before flashing anything that way you know what you are getting yourself into. Since you are i337M, I would start with this thread... http://forum.xda-developers.com/showthread.php?t=2314494
Click to expand...
Click to collapse
Okay, thank you very much for clarifying that my phone's bootloader was not actually locked, I just assumed it was because I couldn't find anyone else with that baseband version. I have also read the thread you linked, I am going to try TWRP.
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.
Looked thru the other threads, and didnt see anything that pertained directly perhaps someone can point me in the right direction.
Have my stock S5 from verizon, on 4.4.4 NK2 firmware. Looking to update to whatever is the most current stock firmware with root. I'm coming to this from years of rooting Sprint devices, this is my first Verizon and I've been putting it off forever. Been getting the nag screen everyday now for a software update and I figured it was the time to update this and get myself root.
Thanks in advance for any help in where to look. Please forgive me in advance if this is a duplicate, I searched...I really did, but since its all new to me I wanted to ask.
Looks like the process is to flash 4.4.2, root, check if bootloader can be unlocked, and then proceed 2 different ways if it can be dev bootloader unlocked. If it can, unlock bootloader, flash twrp, and then flash whatever rom you want. If you can't unlock the bootloader, folow the guides to upgrade keeping root with safestrap and use roms that are TW for locked bootloaders. Someone correct me if I'm wrong. I just got a 4.4.4 g900v myself in a trade and I'm figuring out how to proceed as well.
Ok, slight difference. You can root & check the bootloader from 4.4.4...
Root here (Using NCG stock kernel...
http://forum.xda-developers.com/ver.../safely-upgrade-root-4-4-4-nha-volte-t2879348
If you're having trouble finding the NI2 kernel like I did it's here...
http://forum.xda-developers.com/showthread.php?t=2784880
Then use the method bootloader unlock from method 3 here...
http://forum.xda-developers.com/ver...t/rd-unlocking-galaxys-s5-bootloader-t3337909
If you can unlock your bootloader (I could), then flash the bootloader of choice from that link above to correspond to the rom you want. I'll be trying out Phoenix with pd4 (installed from above link) from here...
http://forum.xda-developers.com/verizon-galaxy-s5/development/port-phoenix-rom-v12-0-t3400292
Been off this thread for awhile (you know how life gets in the way) and was wondering if there are any meaningful upgrades to an S4 with 1545VRUGOF1 rooted via Flashfire. with stock.
C
If you want marshmallow, then custom ROMs are the only way to get it.
Which s4 do you have? Isn't flash fire for the i337?
audit13 said:
Which s4 do you have? Isn't flash fire for the i337?
Click to expand...
Click to collapse
SCH-1545
Android 5.0.1
I545VRUGOF1
At the time, Flashfire was the only path to root
Look here for a possible answer: http://forum.xda-developers.com/galaxy-s4-verizon
Any guidance? I have the VRUGOF1 Bootloader and consequently was only able to root with Flashfire. Not sure if there has been any development to allow Marshmallow to be put on this device
wedmiston said:
Any guidance? I have the VRUGOF1 Bootloader and consequently was only able to root with Flashfire. Not sure if there has been any development to allow Marshmallow to be put on this device
Click to expand...
Click to collapse
Yes, there are ROMs for that device. But you can only flash with a custom recovery so you'll have to find one.
Look in the Verizon forum. This forum is for the international version of the s4.
Pwnycorn said:
Yes, there are ROMs for that device. But you can only flash with a custom recovery so you'll have to find one.
Click to expand...
Click to collapse
Maybe I'm not being clear, but I was uder the impression if you have the OF1 Build you can only root with Flashfire, and, you cannot install CWM or TWRP as it will brick your device. I am not looking to add another ROM, I am fine with stock. My goal is to see if there is a way to go from Lollipop to Marshmallow safely given my specific device parameters
wedmiston said:
Maybe I'm not being clear, but I was uder the impression if you have the OF1 Build you can only root with Flashfire, and, you cannot install CWM or TWRP as it will brick your device. I am not looking to add another ROM, I am fine with stock. My goal is to see if there is a way to go from Lollipop to Marshmallow safely given my specific device parameters
Click to expand...
Click to collapse
If you can't install any custom recovery, then there isn't any way you can.
There is no official TouchWiz Marshmallow ROM for the S4, as such, the only way to get marshmallow is through a custom ROM.
A custom ROM can only be flashed via custom recovery.
Ergo, if you can't flash a custom recovery, there is no way to get marshmallow.
The Verizon OF1 bootloader is locked and not exploitable. Only the MDK bootloader had that luxury. You also cannot downgrade to it. If you want to flash a ROM other that stock head to the Verizon Galaxy S4 development forum and read up on SafeStrap and ROMs that can be installed with it. A custom recovery such as TWRP is not able to be installed on your device. Because of that ROMs such as CM, JDC custom ROMs, etc. are out of reach for you.
Pwnycorn said:
If you can't install any custom recovery, then there isn't any way you can.
There is no official TouchWiz Marshmallow ROM for the S4, as such, the only way to get marshmallow is through a custom ROM.
A custom ROM can only be flashed via custom recovery.
Ergo, if you can't flash a custom recovery, there is no way to get marshmallow.
Click to expand...
Click to collapse
Thanks
So to summarize, since I am on the OF1 build and could only root via Flashfire, the bootloader remains locked...consequently I still cannot flash TWRP or CWM, and as you put it, out of luck to get Marshmallow.
However, has anyone successfully used Flashfire and Xposed? I saw it on another thread: https://www.reddit.com/r/AndroidQuestions/comments/406o9w/verizon_galaxy_s4_unlocked_bootlaoder/
but there was no definitive conclusion that it was successful. Anyone have any direct experience with this? Since Safestrap and Flashfire are both custom recoveries installed alongside of your locked bootloader, do either work to get to Marshmallow?
wedmiston said:
Thanks
So to summarize, since I am on the OF1 build and could only root via Flashfire, the bootloader remains locked...consequently I still cannot flash TWRP or CWM, and as you put it, out of luck to get Marshmallow.
However, has anyone successfully used Flashfire and Xposed? I saw it on another thread: https://www.reddit.com/r/AndroidQuestions/comments/406o9w/verizon_galaxy_s4_unlocked_bootlaoder/
but there was no definitive conclusion that it was successful. Anyone have any direct experience with this? Since Safestrap and Flashfire are both custom recoveries installed alongside of your locked bootloader, do either work to get to Marshmallow?
Click to expand...
Click to collapse
You are a little confused. SafeStrap is not a custom recovery so to speak, TWRP is. SafeStrap allows the installation of some mods, etc. on devices with a locked BL. A quick look in the Verizon S4 Android Development forum does not show a MM build that can be installed via SS, only LP builds.
The issue with a locked BL and SS is you cannot install a different kernel which limited what could be installed.
I saw a set of OF1 instructions out on Stang5litre's OP for his ROM. Has this been validated as a stable rom for those of us on OF1?
I have a question since I watched the youtube video on how to upgrade my phone samsung s4 at&t to Oreo, but I read that I need a bootloader. Then when I read articles here in xda, mostly says that this phone can't be unlock? so How do I deal with this? Please explain simply because I am new in this.
If the phone is running an MDL bootloader, it may be possible to flash Oreo. If the phone is running a newer bootloader, the phone can only run TWRP and will not run Nougat or Oreo.
hjayc24 said:
I have a question since I watched the youtube video on how to upgrade my phone samsung s4 at&t to Oreo, but I read that I need a bootloader. Then when I read articles here in xda, mostly says that this phone can't be unlock? so How do I deal with this? Please explain simply because I am new in this.
Click to expand...
Click to collapse
You cannot unlock the bootloader. However, if you're on the MDL bootloader then you can use an exploit called loki doki to install a custom recovery and a custom ROM. If you're on a newer bootloader other than MDL, then you are stuck with only booting custom touch wiz based ROMs and must use safe strap if on kit kat or flash fire if on lollipop.
Can you oden back to mdl if you are running NJ4.
does it matter id i upgraded to Kittkatt with a custon rom vs ota update on if the bootloader got locked? does goldeneye kittkatt 4.4.4 lock the bootloader?
cousindan said:
Can you oden back to mdl if you are running NJ4.
does it matter id i upgraded to Kittkatt with a custon rom vs ota update on if the bootloader got locked? does goldeneye kittkatt 4.4.4 lock the bootloader?
Click to expand...
Click to collapse
No you cannot odin back to MDL, if you try you will brick your phone. It doesn't really matter how you update given your bootloader is locked (unless you're on the MDL firmware). Golden eye ROM does not lock the bootloader, no custom ROMS lock the bootloader.