hi guys. i would like to root my nexus 4 preferably without flashing a custom ROM, but which way is easier and safer: flashing a custom ROM or just rooting with SU without flashing a custom ROM? i am a "beginner" and afraid of bricking my device. could you recommend be the best in your opinion rooting tutorial? i saw some on stickies but apparently they are from 2012. are they still relevant? thanks a lot!
you dont need to flash a custom rom to root your phone. your phone just stock and locked as well? there are couple different methods you can use to root depending on the current state of your phone (ie what version os you are running, locked/unlocked bootloader, etc..)
thank you for the answer
i am using 4.4.4 kitkat downgraded from 5 lollipop, so does it mean that my bootloader is unlocked? or not necessarily?
Related
Hello,
Lately I've seen a few ROMs in the Android Development section that claim they have completely removed Samsung KNOX (for example, Arrow ROM 9.0.0).
My question is, does it still upgrade the bootloader to the new one that has the 0x1 flag? What are the risks if it does upgrade the bootloader but the Knox apps are removed from the device?
Thanks a lot, I'm looking forward for an answer to make this clear for me.
No custom roms include a bootloader, therefore no custom rom wil upgrade your bootloader.
Only stock roms update the bootloader.
Lennyz1988 said:
No custom roms include a bootloader, therefore no custom rom wil upgrade your bootloader.
Only stock roms update the bootloader.
Click to expand...
Click to collapse
I understand now, thank you very much for the information!
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.
Hi,
I'm new to the custom roms and would like to see advice on the recommended method to install a custom rom onto my untouched I9505. It's currently running Lollipop 5.0.1, I9505XXUHOE4 with KNOX 2.3
Thank you
This would belong into the Q&A section.
Anyway, the first thing you will need to do is to install a custom recovery. I recommed TWRP.
Just google twrp s4.
Optional: if you want to backup any apps or data, you will have to root first. Use odin and cf auto root.
After you installed a custom recovery, just look for a rom that interests you and flash it. Every rom has flash instructions.
Also check to make sure your phone doesn't have a locked bootloader. If it does, things are going to get complicated. If it doesn't, then you're good to go. AT&T and Verizon lock the bootloaders.
Thanks for info GDReaper.
My concern here is KNOX. Will the new bootloader affect anything on the custom roms as compared to a pre KNOX bootloader. Do I need to downgrade the firmware first?
Thanks
Hi @elus,
Installing any custom firmware will trip Knox. You can't downgrade it to pre-Knox bootloader.
Sent from my GT-I9500
Knox will not affect anything. Flashing custom firmware will only trip knox. This means that you lose your warranty. But the warranty is crap anyway, so it doesn't matter.
You won't see any trace of knox in custom roms. You might as well forget you ever had something called knox.
An easy way to root the ROM with TWRP is to flash supersu.zip from TWRP. Upon first boot, open supersu and let it disable knox and update binary files if necessary. You should be fine from that point forward.
Great! Thanks guys for the guide. Let the custom rom mods begin! Happy New Year Everybody!
Hi everyone, I have question that I hope you can answer.
Today I flashed a Custom Recovery and Rooted my Note 3 SM N900. Everything is working fine, I rooted my phone in order to delete apps like trip advisor, s health among other apps. But I've seen that there are 6.0 ROMs for my phone. I've seen many tutorials and I would like to flash a custom ROM. (I'm thinking on flashing Resurrection Remix 5.1.1 for my SM N900). I already made my efs folder backup.
So, my question is this. When I decide to go back to a stock ROM (Lollipop Samsung Touchwiz the one I currently have) do I need to do something extra? Like, I would be able to flash a sotck samsung ROM through TWPR recovery for example? or what I need to do is just flash through odin?
Could you please tell me what I need to know on this cases?
Thank you very much! :good:
just flash with odin and you r good to go
raman99311 said:
just flash with odin and you r good to go
Click to expand...
Click to collapse
And What about the bootloader? Do I Need to unlock it if I want to install any custom ROM? I installed TWRP recovery on my phone, then I Rooted the phone. The steps that I've seen on the Internet to flash a Custom ROM doesn't have a step that unlocks bootloader or so.
Or the bootloader is unlocked since I rooted the phone? I'm confused. I really appreciated if you or someone could explain this doubt.
Thanks in advance. :good:
N900 is already factory bootloader unlocked
Sent from my SM-N920C
Using a bootloader unlock app could brick the phone. The only note 3 I know of with a locked bootloader is the AT&T Sm-900a.
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?