If I just flash one of the custom roms using ODIN will it work okay? I'm on 5.0 with 3.4.0 Kernel. I'm really wanting root on 5.0 and it seems the only way that's going to happen is by flashing a non-stock ROM. Apologies for my noobiness.
Don't try flashing until you know you can !! The kernel # means nothing you need to know what build number the phone is. It must be prior to BOE1 to roll back and gain root. If your build number is BOE1 or BOG5 you have a locked down bootloader and can not root/flash ROM. If you have an earlier build you can roll it back, root and flash any of the ROMs out there including the stock rooted ROM but make sure you understand the process before starting. READ THE HOW TO
Related
So I've not updated my phone in a while. I decided maybe it was time to update to a more current ROM and I see that there have been a lot of updates and different options now.
I have the ATT S4, running 4.2.2 I337UCUAMF3-SHOstock-V2.3
Kernel: 3.4.0-Jeboo_kernel_v1.5+
Baseband: I337UCUAMDL
I like having a near custom ROM with as little additions as possible. What do I need to update to for the most current roms, or some updates that I need to stay away from. Sorry if this is a bit noobish. I got too far behind on this and all the different levels of updates have me all confused.
benk016 said:
So I've not updated my phone in a while. I decided maybe it was time to update to a more current ROM and I see that there have been a lot of updates and different options now.
I have the ATT S4, running 4.2.2 I337UCUAMF3-SHOstock-V2.3
Kernel: 3.4.0-Jeboo_kernel_v1.5+
Baseband: I337UCUAMDL
I like having a near custom ROM with as little additions as possible. What do I need to update to for the most current roms, or some updates that I need to stay away from. Sorry if this is a bit noobish. I got too far behind on this and all the different levels of updates have me all confused.
Click to expand...
Click to collapse
If you're running a custom kernel, then that means your bootloader is compatible with the loki exploit, and you should never flash any ODIN package besides MDL and don't flash any zip file that includes bootloaders. Other than that, you can flash any ROM you like. There's a stock prerooted NC1 zip which is the latest stock firmware with no mods but root. Just make sure you flash the version that doesn't include bootloaders and you'll be good to go. I don't know if it includes the kernel in the zip, but if you want to keep your custom kernel then just reflash it afterwards and make sure you flash loki if it doesn't by itself. Additionally, if you upgrade to a 4.4 ROM, I believe you will need to flash a 4.4 modem to get working sound and radio. You can use the flashable zips in RockRatt's thread safely through your recovery.
I'm trying to learn more about the S5 root world. I am currently running the OTA NHA build, and am rooted using towelroot, and have the latest safestrap installed (also have supersu and busybox). What i am trying to understand is how the custom rom's work now. I just got the S4, and never had my bootloader locked since i rooted/rom'd earlier on and never ran stock, and i was using TWRP so there were no rom slots or the like; you downloaded a rom, wiped your phone, flashed it, done.
This bootloader/kernel/baseband talk is what's confusing me. A question that i've been trying to find the answer for is as such: let's say i have my NHA rooted phone, but there is an NE9 rom on the forum i want to try (extreme syndicate/alliance). Can i just flash that to a rom slot and go, or do i flash the kernel as well? if i flash the kernel, won't that mess with my stock rom, or does that just patch the kernel inside of the rom slot?
I already understand that chronologically, the baseband/build versions are NCG>NE9>NHA>NI2, so understand that rom's baseband is a version behind NHA. Someone please help clarify some of this for me
Can it is possible? I have official firmware of jellybean dwnlded from sammobile.
Help.!
Not possible as the Knox-enabled bootloader prevents downgrades. Even if you were able to downgrade, say by perhaps not downgrading the bootloader while downgrading everything else, it's unlikely the radios on the device will ever function. About the only use there is for such a downgrade is to carrier unlock the S4 using RegionLock Away, and even then you only have to flash a modem to do that.
Downgrading to Android 4.4.2 should be possible, if you really want to. I'd recommend flashing a custom ROM instead. All the custom ROMs, regardless of whether they are Touchwiz-based, GPE-based or Cyanogenmod-based, all include the battery drain bugfix that stock ROMs lack.
Thanks but i dont want now bcz voltaqe kernel has solved my problem i.e sound gain
Excellent! Good to hear you got things resolved.
So, I bricked my phone and then got it working again by flashing N12, rooted and all that jazz and then upgrade to a deodexed BOG5 firmware with flashfire to keep root.
I want to flash a custom rom and im not sure if i should proceed. I had Optimal ROM and Freedom ROM in mind. Last time i tried to flash the optimal rom. This bricked my phone but at the time my baseband was OA8. idk if it had anything to do with bricking my phone but i did do what i found out was called a "dirty flash" which may have had something to do with it.
My question is with my build number from BOG5 and my baseband from N12, is there a need to update it? Dow do i go about upgrading it to match the build? I installed OD5 bootloader so im not sure why the baseband is not either from BOG5 or OD5. My kernel is also BOG5 3.4.0-4782027.
also last qeustion: can i dirty flash the rom after im done and set, or should i always wipe and then flash?
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.