I have a tmobile sm-900t. I want to install 4.4.2 roms but I'm unsure of the whole process. This is my first samsung phone everything is new to me.
Do I need to flash a specific firmware to be able to run 4.4.2 roms?
Are there any restrictions on which roms would be compatible with my model #? As opposed to only flashing from the limited selection over in the tmobile sub forums.
Do I need a certain version of CWM or TWRP to be able to flash KK roms?
RomanHelmet said:
I have a tmobile sm-900t. I want to install 4.4.2 roms but I'm unsure of the whole process. This is my first samsung phone everything is new to me.
Do I need to flash a specific firmware to be able to run 4.4.2 roms?
Are there any restrictions on which roms would be compatible with my model #? As opposed to only flashing from the limited selection over in the tmobile sub forums.
Do I need a certain version of CWM or TWRP to be able to flash KK roms?
Click to expand...
Click to collapse
Head over HERE and check out the T-Mobile ROMS, you can flash certain N9005 ROMs but you gotta play with patches and kernels. Read the T-Mobile forum and compare the ROMs here and there you will see the compatible ones
It's been awhile, and I'm not too clear on what I should watch for in regards to KNOX.... Getting it to the latest stock OTA is my main concern.
I have 2 in this state, the other I'm going to flash a custom ROM and bootloader, so... Are there plenty of stable full featured ROM's out these days? How about bootloaders? The forum doesn't seem as "updated" as usual (older device now, I know).
I'd like to be able to load a custom ROM on my MicroSD and flash it via the bootloader. What's the most stable bootloader/kernel combo around?
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.
My younger brother has a Note 4. It was previously on Kitkat 4.4.2, stock rom, rooted with dual recovery...
He wanted to manually update to either a 5.1.1 Lollipop rom or even 6.01 Marshmallow.
After having tried several 6.01 roms, the phone either bootloops or the sim card is not reading...
After having trying to flash the radio & bootloader to flash via odin, it keeps failing when trying to do so.
Could someone please recommend a simple Lollipop rom or Marshmallow rom that actually WORKS and the sim card is read as it should?
With my current Sony Z2, it is so much simpler, flashing any roms automatically comes with the kernal, radio, recovery, root, etc...
With Samsung it is much more complex and finding a rom which comes with everything seems difficult to find.
Some roms even ask to choose a kernel & modem/radio. How the F**K do i know which one I need? Even when selecting one it results in a bootloop.
I'm not interested in overclocking or using a custom kernel. I just want something that works and any 5.1.1 rom or Marshmallow rom would do. I want something as close as stock as possible. Not interested in Cyanogen mod, custom roms or such.
Thanks!!
you need to flash a compatible modem for your model number and version of android. If it helps, I'm using: N910FXXUICOL2 with Marshmallow
I have the N910F model.
Hmm, I don't know why you are having problems, actually its Samsung where you can simply flash a ROM with Odin, no need of ADB or anything.
You just make sure that you COMPLETELY WIPE your phone before flashing a stock ROM via Odin. You should not have any problem at all, no one should, unless its hardware.
this is bit different.
my bootloader is locked not changed yet.
but i want to flash .35 version available here.
how do i proceed??
is it gonna brick device or i will get complete new flashed device??
or it wont go ahead??
will it change my baseband???
can i use RSDLite??
Somebody??