Related
Hi Guys,
I just bought a new Galaxy S3 here in New Zealand and before I start using it, I want to update it to the latest version, I believe 4.1.2 and then root it, can this be done? whats the best option for me? I see the Galaxy Toolkit to do the rooting, is this the most popular/best ?
Also after rooted, can I still do the OTA updates or will I have to flash custom roms?
m1k30rz said:
Hi Guys,
I just bought a new Galaxy S3 here in New Zealand and before I start using it, I want to update it to the latest version, I believe 4.1.2 and then root it, can this be done? whats the best option for me? I see the Galaxy Toolkit to do the rooting, is this the most popular/best ?
Also after rooted, can I still do the OTA updates or will I have to flash custom roms?
Click to expand...
Click to collapse
If 4.1.2 was not yet launched in NZ, then you will not get any update for your phone at the moment.
What you could do is, root your phone and then install the 4.1.2 version (Poland)(root is not required for flashing though). For rooting refer to the stickies in general section. Popular methods are CF-Root 6.4 (incl. CWM as recovery) or CF-Auto-Root (keeps stock recovery) (both can be found in dev. section).
After rooting you will not be able to get OTA updates though, whereas KIES should still work (but you will loose root if you update).
In addition, make sure to read all the stickies and guides for rooting before you touch anything! Especially the EFS backup procedure.
I hope it helps.
Rooting your phone voids it from getting OTA updates.
Sent from my GT-I9300 using xda premium
I just bought a new Galaxy S3 here in New Zealand and before I start using it, I want to update it to the latest version, I believe 4.1.2 and then root it, can this be done? whats the best option for me? I see the Galaxy Toolkit to do the rooting, is this the most popular/best ?
Click to expand...
Click to collapse
As said above 4.1.2 is still not available in NZ. So you can flash other ones (like Poland) if needed.
Also after rooted, can I still do the OTA updates or will I have to flash custom roms?
Click to expand...
Click to collapse
After rooting OTA updates will not work. But you can still get the firmware and flash them through Odin. This will remove root and will have to go through the rooting procedure again.
I feel samsung will release 4.1.2 for other regions soon and my suggestion would be to wait for that and then go ahead with rooting
You don't need to root your phone to install an official firmware!
Tyxerakias said:
You don't need to root your phone to install an official firmware!
Click to expand...
Click to collapse
No one says you need to in this post .
jje
Thanks guys yeah 4.1.2 does not look like its been released yet, I'll wait for it to come out then root cheers!
I used to wait for offical releases, then realised there was no need - the custom ROMs are far better than the official and much faster at new releases than regional Samsung rollout. They also get rid of the battery sapping bling most people only use the once.
If you are going to root anyhow, then the warranty isn't a concern.
Just had bad experiences with 3rd-party ROM's. Had a Desire Z and ran about 5 different roms, cyanogen, gingerbread and ICS variants, mimcry, ilwt, extreme mod, and none of them seemed to run very well after a few weeks of use. The stock ROM on this galaxy is flying like no tomorrow! especially after simply disabling the garbage apps
m1k30rz said:
Just had bad experiences with 3rd-party ROM's. Had a Desire Z and ran about 5 different roms, cyanogen, gingerbread and ICS variants, mimcry, ilwt, extreme mod, and none of them seemed to run very well after a few weeks of use. The stock ROM on this galaxy is flying like no tomorrow! especially after simply disabling the garbage apps
Click to expand...
Click to collapse
I'll admit that Samsung could teach HTC quite a few things about writing a good ROM, I'm sticking with customs of the stock jb 4.1.2 for now as it all works so well and saves me having to remember what needs disabling. I tried a few minimalist roms before sticking with the viking one.
I've got a 4.1.2 in NZ but that's because my phone bricked and they updated it when fixing it(4.1.2 supposed to have the fix for bricking)
Sent from my GT-I9300 using xda app-developers app
yeah, also because the thread is couple of months old
In case you wonder it seems that in S4 there is a bootloader hardware-level protection which can not be restored back once it is triggered (possibly efuse or something).
http://www.sammobile.com/2013/09/23...t-seems-to-prep-the-device-for-use-with-knox/
Hope not
It is coming to all 4.3 firmwares, for the s3, note 2, s4, and note 3.
I don't get it. What does it mean. Cant we root anymore?
Sent from my GT-I9300 using xda app-developers app
Not with out Samsung being able to tell.
It's a new bootloader in 4.3 that shows if you flash a different rom and ATM there is no fix so Samsung can refuse to fix. Look on s4 threads
Thnx will do that
Sent from my GT-I9300 using xda app-developers app
Don't update the bootloader unless you want KNOIX, and yes you can root still.
As always, flashing with CWM is 100% safer than Odin. It helped most of us avoid the untriganle-away-able bootloader for the S3 adn it is helping people avoid the KNOX bootloader on the S4. Those of you that like to dive on the Odin flashable firmwares... more fool you.
Kryten2k35 said:
Don't update the bootloader unless you want KNOIX, and yes you can root still.
As always, flashing with CWM is 100% safer than Odin. It helped most of us avoid the untriganle-away-able bootloader for the S3 adn it is helping people avoid the KNOX bootloader on the S4. Those of you that like to dive on the Odin flashable firmwares... more fool you.
Click to expand...
Click to collapse
Agree that cmw is safer than Odin. I'm going to wait for custom stock 4.3 firmware.
I'm currently on a Galaxy S3, but I have an S4 coming in on Friday.
I saw a thread for rooting the S4, but do I need to unlock the bootloader like I did in the S3 to install a rom?
Basically, where is the thread that has all the info I need to root, unlock, and install a custom recovery for the S4?
I have one for the S3, but can't find it for the S4.
GlitchMob said:
I'm currently on a Galaxy S3, but I have an S4 coming in on Friday.
I saw a thread for rooting the S4, but do I need to unlock the bootloader like I did in the S3 to install a rom?
Basically, where is the thread that has all the info I need to root, unlock, and install a custom recovery for the S4?
I have one for the S3, but can't find it for the S4.
Click to expand...
Click to collapse
you cant find thread? How hard did you look? There is a stickie can't be missed in the general section.
BTW, the bootloader is locked for all versions of firmware since mdk.
only option is safetrap.
decaturbob said:
you cant find thread? How hard did you look? There is a stickie can't be missed in the general section.
BTW, the bootloader is locked for all versions of firmware since mdk.
only option is safetrap.
Click to expand...
Click to collapse
Okay maybe my understanding on the purpose of unlocking the bootloader is incorrect.
I thought the bootloader has to be unlocked in order to install a custom rom?
On my S3 if the bootloader wasn't unlocked the phone would brick.
Safestrap is a custom recovery so how is that relevant to bootloader? I can't seem to draw the connection.
Thanks!
GlitchMob said:
Okay maybe my understanding on the purpose of unlocking the bootloader is incorrect.
I thought the bootloader has to be unlocked in order to install a custom rom?
On my S3 if the bootloader wasn't unlocked the phone would brick.
Safestrap is a custom recovery so how is that relevant to bootloader? I can't seem to draw the connection.
Thanks!
Click to expand...
Click to collapse
plenty of threads here to read to educate yourself.
S4 bootloader is locked since mdk firmware. MDK had an exploit that Loki process allowed custom recovery
safestrap uses an exploit to work around it so its the only custom recovery for the locked bootloader.
Each subsequent firmware release locks the bootloader and exploits down further. Anyone taking the next round of kit kat OTA's will likely loose root as well.
GlitchMob said:
I'm currently on a Galaxy S3, but I have an S4 coming in on Friday.
I saw a thread for rooting the S4, but do I need to unlock the bootloader like I did in the S3 to install a rom?
Basically, where is the thread that has all the info I need to root, unlock, and install a custom recovery for the S4?
I have one for the S3, but can't find it for the S4.
Click to expand...
Click to collapse
More then likely the device you get will come with the new baseband MJ7 or MK2. You need to check this before you start messing with anything. That said the bootloader is locked up tight and you will be very limited with what you can do with it. You can root, and install safestrap(a custom recovery by Hashcode that bypasses the bootloader). This will allow you to install certain touchwiz based roms but you have to be sure they are compatible with safestrap.
Root for 4.3 baseband:
http://forum.xda-developers.com/showthread.php?t=2565758
Safestrap:
http://forum.xda-developers.com/showthread.php?t=2441441
Both these links are in the android devlopment section. It is very difficult with this device because there are multiple root methods and recovery methods depending on baseband version. If by some chance you get the phone and the baseband is MDK, DO NOT UPDATE!!!! This will allow you to install loki'ed recovery and flash any rom you want. Chances are that won"t happen though. Good luck
decaturbob said:
you cant find thread? How hard did you look? There is a stickie can't be missed in the general section.
BTW, the bootloader is locked for all versions of firmware since mdk.
only option is safetrap.
Click to expand...
Click to collapse
decaturbob said:
plenty of threads here to read to educate yourself.
S4 bootloader is locked since mdk firmware. MDK had an exploit that Loki process allowed custom recovery
safestrap uses an exploit to work around it so its the only custom recovery for the locked bootloader.
Each subsequent firmware release locks the bootloader and exploits down further. Anyone taking the next round of kit kat OTA's will likely loose root as well.
Click to expand...
Click to collapse
I understand that I need to look into it, but the way things are organized is different. I've been on an S3 for almost two years now and the forums in the S4 are just overwhelming with information that is scattered. Here is an example of what I was hoping for when I came to the S4 section.
http://forum.xda-developers.com/showthread.php?t=1762709
onemeila said:
More then likely the device you get will come with the new baseband MJ7 or MK2. You need to check this before you start messing with anything. That said the bootloader is locked up tight and you will be very limited with what you can do with it. You can root, and install safestrap(a custom recovery by Hashcode that bypasses the bootloader). This will allow you to install certain touchwiz based roms but you have to be sure they are compatible with safestrap.
Root for 4.3 baseband:
http://forum.xda-developers.com/showthread.php?t=2565758
Safestrap:
http://forum.xda-developers.com/showthread.php?t=2441441
Both these links are in the android devlopment section. It is very difficult with this device because there are multiple root methods and recovery methods depending on baseband version. If by some chance you get the phone and the baseband is MDK, DO NOT UPDATE!!!! This will allow you to install loki'ed recovery and flash any rom you want. Chances are that won"t happen though. Good luck
Click to expand...
Click to collapse
Thank you. This is the response I was looking for. As you said there are many stipulations with each baseband. This is something I am not used to coming for an S3, which is far simpler to deal with. Thanks again!
GlitchMob said:
Thank you. This is the response I was looking for. As you said there are many stipulations with each baseband. This is something I am not used to coming for an S3, which is far simpler to deal with. Thanks again!
Click to expand...
Click to collapse
The difference isn't in the baseband, it's in the bootloader. You can run a newer baseband than your bootloader, for example, especially if you have the MDK bootloader.
Since you're starting from stock, the baseband and the bootloader revisions are the same and can be found from Settings/More/About phone.
Before you flash anything, please read the what you need to know thread in the General section. Also, there's my thread in this forum.
The S4 is more complicated than the S3 largely because Samsung has really locked it down much more effectively than the S3. Consequently, there's lots of ways to go wrong. Reading first can save you a lot of grief.
k1mu said:
The difference isn't in the baseband, it's in the bootloader. You can run a newer baseband than your bootloader, for example, especially if you have the MDK bootloader.
Since you're starting from stock, the baseband and the bootloader revisions are the same and can be found from Settings/More/About phone.
Before you flash anything, please read the what you need to know thread in the General section. Also, there's my thread in this forum.
The S4 is more complicated than the S3 largely because Samsung has really locked it down much more effectively than the S3. Consequently, there's lots of ways to go wrong. Reading first can save you a lot of grief.
Click to expand...
Click to collapse
One more question. Is there a way to flash the s4 back to stock? I'll find the info on how, but going into the whole rooting and coming phase it would be nice to know that I could flash back to stock with odin. As I have with my s3.
GlitchMob said:
One more question. Is there a way to flash the s4 back to stock? I'll find the info on how, but going into the whole rooting and coming phase it would be nice to know that I could flash back to stock with odin. As I have with my s3.
Click to expand...
Click to collapse
Yes. Read the second link in my reply above - it tells you how to identify what build you're on and has links to the downloadable Odin images for each build.
k1mu said:
Yes. Read the second link in my reply above - it tells you how to identify what build you're on and has links to the downloadable Odin images for each build.
Click to expand...
Click to collapse
Thanks for your help. Turns out I'm on MJ7. I'm going to let this puppy charge while I hit the gym. I'll root it and see what rom I can install later tonight. Thanks again!! :victory:
GlitchMob said:
Thanks for your help. Turns out I'm on MJ7. I'm going to let this puppy charge while I hit the gym. I'll root it and see what rom I can install later tonight. Thanks again!! :victory:
Click to expand...
Click to collapse
Mind as well update to mk2. You can do the same as mj7 but are most up to date. Just my 2 pennies. Btw I'm on bonestock 2.1 in SS romslot 1.
Sent from my SCH-I545 using xda app-developers app
Slowbalt said:
Mind as well update to mk2. You can do the same as mj7 but are most up to date. Just my 2 pennies. Btw I'm on bonestock 2.1 in SS romslot 1.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Is there a noticeable difference? If its the same, why upgrade?
I am coming from a similar situation as you. I cracked my screen on my S3 and Asurion replaced it with an S4, which I received on Monday. I thought that I was going to be able to load SlimKat and pick up where I left off, but no.
The posts that k1mu linked are a great starting point. A few of my thoughts that I came to realize this week. These are my ways of looking at it and may not be totally correct.
The bootloader is locked and there isn't a total unlock (yet). Safestrap allows you to crack the door open a little and reach your arm in to grab a few things.
You will need to stick with ROMs that work with the TouchWiz kernel. The post that k1mu referenced has a link to compatible ROMs. You will not be able to load SlimKat, CM, Carbon, etc. Basically any ROM you choose will have TW underneath. Some of the ROMs will try to look like an ASOP, but it is still a TW base.
Safestrap will allow you to create ROM slots where you can try out the ROM to see if you like it. I am still trying to decide what I want to use. Currently I have Hyperdrive as the leader. Everything that I do continues to work. The Eclipse ROM looks good but it is not quite there yet, but he is working on a build in the next couple days. Here is a link to their website with more up to date status. Eclipse . I also looked at the Foxhound ROM and it is good also. For me support and future upgrades are the most important. I am starting to think that i will embrace TW instead of trying to cover it up and will go with Hyperdrive.
If you use TiBu, read this post, especially with Hyperdrive http://forum.xda-developers.com/showthread.php?t=2653044.
The other realization that hit me was that while Safestrap can create partitions for loading different ROMs, each one is restricted to a maximum of a 3GB /data partition. When I tried to restore all of my apps this was quickly used up. It isn't supported by Safestrap to flash to the stock location, but it can and has been done. Since Safestrap isn't doing a flash there are more risks and I think that this should probably be kept to a minimum. This is where you want to test all the candidate ROMs first and then decide which one to use and then flash to the stock location. Obviously this could cause problems with the phone and would use ODIN as a fallback. Unless something get totally hosed and then you are out of a phone.
One thing that I realized a long time ago is that when you change devices you may want to do everything exactly the way it was before. On the phone or even when looking for information. But in most cases it is better to change your processes or work flow to work with the new device than it is to change the device to work in your previous work flow.
the phone in question is a T mobile Galaxy S5, used to be mine running full root since 4.4.4 and had cn 11 on it, now wife is useing it and she wated it stock, so I odined the latest stock t mobile 5.0 firmware onto it, since then it has updated twice to 5.1.1 as I'm not too familiar with 5.1.1 I figured I better ask if it can be rooted.
if it can it will be much appreciated, right now it has done random reboots three times so far today and she is about to go back to Applel
5.1.1 can be rooted using hispasian's kernel. It can find in the android development thread. BTW, tell your wife that Apple is tight about "rolling back" and/or if at all, to previous ios versions if the new version stinks. I was lucky to perform rollbacks on older iphone generations but the newer ones are harder for obvious reasons. I stayed on 4.4.2 because of towelroot -- I'm not too fond of 5.1.1 because of the lag and unstable root methods right now.
Any questions? Please let me know. We would wan't want your spouse to join the "dark side" we call Apple. =) <couldn't resist the star wars pun there>
Thanks I'll loom there here in a minute I want her to be an android person I like androids better because you can remove the SD card, Apple has no SD card, plus as long as it's not a s6 you can swap batteries, I usually keep two spares in my Jeep when we go looking in NC for houses just in case
Sent from my SCH-I545 using XDA Free mobile app
I meant FOL1 in the original thread
Please excuse my stupidity
well in another thread i was wondering if flashing TWRP+CM still works on FOL1 & the user said yes, so.... i'm sure root is always possible, unless your question is to keep knox (you're probably out of warranty anyway)
there are modified TW roms that are prerooted if self rooting fails
random reboots with what apps installed? disable any you dont use, disable gestures, samsung crap, etc etc...
I don't want knox, I don't want 5.1.1 either what I want is to put 4.4.4 on in or 4.4.2 and root it real fast before it updates
wolfen1086 said:
I don't want knox, I don't want 5.1.1 either what I want is to put 4.4.4 on in or 4.4.2 and root it real fast before it updates
Click to expand...
Click to collapse
not sure what the rush is, there is no such thing as sudden updates that you cant stop, if you flash 4.4 then it's stuck on 4.4, but what if the newer baseband wont work well with the old android?
also, 4.4 is crap, you'll be insecure with fewer features & so on
i really find it unlikely that 5.1.1 is causing all problems, also you could even try 5.0.1
wolfen1086 said:
I don't want knox, I don't want 5.1.1 either what I want is to put 4.4.4 on in or 4.4.2 and root it real fast before it updates
Click to expand...
Click to collapse
Turn off wifi and mobile data....
I tried but I was too late it went to 5.1.1, it is rooted though so until XDA cones out with a way to unlock the bootloader I have to wait. Because if I try installing TWRP like I did at first it hangs on the custom love indicator screen
Sent from my SCH-I545 using XDA Free mobile app
wolfen1086 said:
I tried but I was too late it went to 5.1.1, it is rooted though so until XDA cones out with a way to unlock the bootloader I have to wait. Because if I try installing TWRP like I did at first it hangs on the custom love indicator screen
Sent from my SCH-I545 using XDA Free mobile app
Click to expand...
Click to collapse
uh, at&t variant is locked, tmobile is unlocked... something is odd with this whole thread
Is there a root method for FOL1 that doesn't void Knox?
Playb3yond said:
Is there a root method for FOL1 that doesn't void Knox?
Click to expand...
Click to collapse
No, but it's hilariously easy to get Samsung to honor a warranty on a device with a tripped Knox flag, if that's what you're worried about
thisisapoorusernamechoice said:
No, but it's hilariously easy to get Samsung to honor a warranty on a device with a tripped Knox flag, if that's what you're worried about
Click to expand...
Click to collapse
What about OneClickRoot.apk
thisisapoorusernamechoice said:
No, but it's hilariously easy to get Samsung to honor a warranty on a device with a tripped Knox flag, if that's what you're worried about
Click to expand...
Click to collapse
What about OneClickRoot.apk
thisisapoorusernamechoice said:
No, but it's hilariously easy to get Samsung to honor a warranty on a device with a tripped Knox flag, if that's what you're worried about
Click to expand...
Click to collapse
sorry for such a simple question but I need expert and/or experienced advise.
I have a samsung galaxy S4 AT&T I337 Ver 5.0.1 firmware OK2.
Out of contract
I want to rid myself of the bloatware, my principal objective.
I worry about not getting security updates once rooted, (even though at&t is not quick about doing updates anyway). Do I just track the forums here to look for updates? Will i have to go back to kitkat for every update?
And second I have a mac air computer, so odin may not be easily done without ready access to a pc., and maybe not at all. I understand I have to odin back to 4.4.4 and then update with a rooted rom. I haven't found recent experiences using jodin on this particular device, and the jodin posts I found indicate it doesn't flash a large file. I don't know if I would be doing that or not.
Thanks for your all's opinion.
Do you play Pokemon go, then no, else of course root it!
AT&T phones have locked bootloaders, thus no root.
Sent from my ASUS_Z00A using XDA Labs
krasCGQ said:
AT&T phones have locked bootloaders, thus no root.
Sent from my ASUS_Z00A using XDA Labs
Click to expand...
Click to collapse
I see talk of locked bootloaders and then I see this thread about getting to root on OK2 http://forum.xda-developers.com/galaxy-s4-att/general/how-to-installed-custom-lollipop-rom-t3135396
Can you explain please.