Database Users

rooting

Hi
I am going to root my G2 for the first time. its currently on stock jellybean.
I would like to know if I should root now on jelly bean and install a custom rom or upgrade to stock kitkat first and then root?
if I am going to a kitkat custom rom would it make more sense to upgrade to stock kit kat first or is it easier to root from jellybean?
What are the advantages/disadvantages of either?

Hi
Can anyone advise on the above? I know I should be reading all the forums which I will but was just after a quick general answer so I know where to start from. I'm not new to rooting and flashing roms but I am new to the G2.
Thanks

I would recommend updating to Kit Kat first then rooting using IOroot25. That way you will have the latest radio/modem stuff to use KK Roms

Depends on the ROM. If the dev says you have to have Kitkat modem or other stuff from Kitkat, then update and root with ioroot25. If not, it will be a waste of time, so:
Download anything you need from the new ROM and put all in your phone storage (so that if you accidentally brick you still have files to flash in your SD), root, install recovery (I suggest TWRP) and from there flash your ROM!

Can I install CWM on the GS4?

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.

[Q] Xposed on locked bootloader and Rolling back questions

Hello all,
I recently installed 5.0.1 rooted on galaxy s4 I337 using muniz's method and had some questions?
The main reason I rooted was to try to get xposed so I can edit the ui, I understand that it is not working on samsung devices right now, but when it does work, I understand the only way to install it is using a custom recovery.
Since I have a locked bootloader and am on 5.0.1 I don't think there is a way to get a custom recovery on here, correct me if I'm wrong.
How would I install the xposed framework? Will flashfire be able to load it?
Also, if I were to revert back to the stock NB1 build, can I re-root and install clockworkmod (would LOKI work then?) on it and then go to a custom rom like cynogenmod or are there problems with this because I already have updated all the way to 5.0.1? (I've done this rollback through ODIN before and it's not too bad.)
I'm new to android modding so this has been a learning experience.
Thanks

Once upgraded to the locked bootloaders, there is no going back to loki. You can downgrade from 5.0.1 to 4.4.2, but you can only use safestrap recovery, and only touchwiz based firmware. Also, safestrap doesn't work on 5.0.1 yet. From what I have read, with 5.0.1 you'll have to wait and see what the developers come up with. If you care to learn more about the history of bootloaders, there is lots of info in these forums.

Engitheneer said:
Hello all,
I recently installed 5.0.1 rooted on galaxy s4 I337 using muniz's method and had some questions?
The main reason I rooted was to try to get xposed so I can edit the ui, I understand that it is not working on samsung devices right now, but when it does work, I understand the only way to install it is using a custom recovery.
Since I have a locked bootloader and am on 5.0.1 I don't think there is a way to get a custom recovery on here, correct me if I'm wrong.
How would I install the xposed framework? Will flashfire be able to load it?
Also, if I were to revert back to the stock NB1 build, can I re-root and install clockworkmod (would LOKI work then?) on it and then go to a custom rom like cynogenmod or are there problems with this because I already have updated all the way to 5.0.1? (I've done this rollback through ODIN before and it's not too bad.)
I'm new to android modding so this has been a learning experience.
Thanks
Click to expand...
Click to collapse
If xposed ever is updated to support Lollipop Touchwiz, you'll be able to flash it using Flashfire or using the Safestrap workaround (flash 4.4 kernel so you can get into safestrap, flash files, then flash 5.0 kernel). There's no way to go back to CWM or TWRP past the old MF3 4.2.2 update, which has long come and gone now.

OK2, Android 5.0.1--what are my options?

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.

Newbie requesting help to upgrade from 4.2.2 to Lollipop

Hello,
I have a rooted i337 with MDL baseband, running stock 4.2.2 firmware. I am currently out of the US and therefore cannot receive any OTA. I want to upgrade to Lollipop or Marshmallow based custom ROMs, esp those that can still use the IR feature of the S4.
Can anyone guide me on how I do this upgrade, without bricking my phone? Would truly appreciate your help. Thanks.

Have you tried running ota updates via wifi without a SIM card in the phone.
To run a custom rom, you would need to install a custom recovery to flash the rom. Some mm and LP ROMs may not work with a 4.2.2 modem and bootloader.

If you want to use a custom ROM, DO NOT take any OTA updates. If you take an OTA and it is successful, then you will no longer be able to install a custom ROM.
Here is the Cyanogenmod thread to install CM to your phone: http://forum.xda-developers.com/showthread.php?t=3008609
If you would like to update to official ATT/Samsung lollipop(there is also a way to have root)[remember, once you take an official update from MDL, then you will no longer be able to install a custom ROM and you may never be able to get Marshmallow]: http://forum.xda-developers.com/showthread.php?t=2926642