Hi, all. I rooted my continuum a couple of years ago via Odin, so I've done it once and I'm not afraid of it. But now I have a GS3 with the new MF1 update. I want to root so I can get rid of the VZW junk and find the best tethering option. I paid $400 for my phone instead of upgrading with Verizon so I can keep my unlimited data, so I'm not about to wantonly brick it, which is why I'm asking dumb questions!
1) Can I root without unlocking the bootloader? The reason why I'm asking is that I don't want to flash any custom roms at this time, just clean out the bloatware and have SU. Or am I mistaken...I thought the only reason to unlock it was to install a custom recovery, but that the recovery is only needed to flash a custom rom, not to root it.
1a) If I can root without unlocking the bootloader, which is the best way?
I went through [GUIDE] Root for Jelly Bean 4.1.1 or 4.1.2 OTA ***UPDATED 5/29*** here --> http://forum.xda-developers.com/showthread.php?t=2046439
But it seems that the VRBMF1 bootchain is not available yet. Someone mentioned flashing mb1 with Odin, and then using the mb1 bootchain to root, but that seems counterintuitive if I don't plan on then flashing a custom rom.
1b) What would happen if I flashed a different bootchain than the version I currently have and tried rooting?
2) If my phone is soft-bricked, as has happened to a couple of people using the Casual method, is it possible/hard to unbrick it?
3) I have baseband VRBMF1, but I noticed that with the Casual method, whoever did it in the video had VRBMA2. Now, I understand that the baseband version is independent of the firmware, but can the baseband version interfere with the rooting process, for instance using the Casual method?
Also, the main reason why I haven't done Casual is that it bricked a few phones. I'm not opposed to having a custom recovery, as would be installed with Casual, but given the few failures, I'm not eager to try it.
4) I've been using PDANet+ to tether, but I'm not convinced that using PDANet with wifi is good, as it seems to use the phone's hotspot (unlike using the USB function in the app). What is the best way to hide tethering from Verizon? And are there better options available to root users?
Thanks for any advice!
You have the guide you need. Just follow the directions. You can root without unlocking boot loader. If you unlock the boot loader then you can flash a custom Rom that has built in tether feature if you don't want to use pda. I would just bite the bullet and do casual. It really is fool proof.
Sent from my SCH-I535 using Tapatalk 2
bbqsfire said:
You have the guide you need. Just follow the directions. You can root without unlocking boot loader. If you unlock the boot loader then you can flash a custom Rom that has built in tether feature if you don't want to use pda. I would just bite the bullet and do casual. It really is fool proof.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the reply. I agree with you about having the guide I need for the Odin method, but I still don't have the correct bootchain. Will another work? And the casual root does seem foolproof, except for the few bricks. No one has identified what caused those, whether some java issue, or something else.
So if I used the Odin method, does it matter which bootchain for 4.1.2 I use, either MB1 or MD3, considering i'm on MF1?
hturbulence said:
Thanks for the reply. I agree with you about having the guide I need for the Odin method, but I still don't have the correct bootchain. Will another work? And the casual root does seem foolproof, except for the few bricks. No one has identified what caused those, whether some java issue, or something else.
So if I used the Odin method, does it matter which bootchain for 4.1.2 I use, either MB1 or MD3, considering i'm on MF1?
Click to expand...
Click to collapse
It will not matter because you can flash the radio later. You will be flashing an older bootchAin but once you flash a Rom and the radio you are fine.
Sent from my GT-P5113 using xda premium
If the bootchain doesn't matter, why are there different versions? I'm not so concerned about the radio because that doesn't change with rooting, does it? I guess my question would be, if I'm on the VRBMF1 build, and say I used the VRBMD3 bootchain, would everything go as planned? I mean, doesn't the bootchain just tell the phone in which order to use files for boot?
I really appreciate your help!:good:
I came from the continuum too, have to say I miss the ticker, but not the lack of RAM!
I used this method to root my S3:
http://forum.xda-developers.com/showthread.php?t=1984436
Used the first link (mb1 no wipe). It is Stock, locked bootloader, stock recovery, rooted. Then I used OTA Rootkeeper (from play store) to back up root. Then I took the OTA to MF1. This will get you to the latest stock firmware with root. You can unlock the bootloader and install a custom recovery later if you want, which is what I did. . No issues for me so far.
Sent from my SCH-I535 using xda app-developers app
Thanks for the info. I actually rooted with casual about an hour ago. I was nervous about the casual method because of the few bricks with MF1, but I gave it a shot, and it worked.
Now, just have to figure out best way to tether without VZW knowing!
Sent from my SCH-I535 using xda app-developers app
Related
I've spent an hour searching for something to explain what bootchains are. I want to understand how they allow the S3 to be rooted and why you need to put them back when you're done. But I'd settle just for a simple what are they.
TommyTFC said:
I've spent an hour searching for something to explain what bootchains are. I want to understand how they allow the S3 to be rooted and why you need to put them back when you're done. But I'd settle just for a simple what are they.
Click to expand...
Click to collapse
A bootchain is the process your phone takes in order to boot. Flashing a specific bootchain is the bootchain available at the time when it was released.
It specifically tells the phone to boot through a series of steps in order to make sure the phone is running correct files. If any part of the chain is broken, the phone won't be able to boot up.
An example which we bypass on our specific phone is the aboot step in the bootchain. To unlock the phone, we simply flash a modified aboot file that makes the phone think it's running the correct rom and kernel. Aboot is only one part of the bootchain.
Hope that makes sense.
Sent from my SCH-I535 using Tapatalk 2
So the files in the tar are programs and they each execute in turn?
The rooting instructions say it doesn't matter if you put the original back. Know why?
Sent from my SCH-I535 using xda app-developers app
TommyTFC said:
So the files in the tar are programs and they each execute in turn?
The rooting instructions say it doesn't matter if you put the original back. Know why?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Basically you got it. That's exactly what's in the tar file.
I'm not really sure how exactly the new rooting process works the way it does, but I know it has something to do with breaking the chain and allowing it to inject a superuser app and recovery. The original bootchain blocks this process and doesn't allow superuser permission. ICS allowed this, which is why it was easier to root it. JB blocks this method, which is why a modified bootchain is needed.
I'm only assuming, but restoring to the original bootchain is simply recommended because it's what should be on the phone. If there's something wrong with the modified bootchain then it may break your booting checkpoints. You're probably safe not restoring it, but you can be sure you're safe if you do restore it.
Sent from my SCH-I535 using Tapatalk 2
Yea you should restore the original bootchains. You want to be original.
Did a search, and this was the best thread I could find.
I'm looking to root, and know that I need to download the correct bootchain.
Question: How do I determine which one that is?
I'm running the (new, awful) version of 4.1.2 that just updated my Verizon Galaxy S3. Currently, I'm stock... but not for long.
Thanks for the assistance.
ccstra54 said:
Did a search, and this was the best thread I could find.
I'm looking to root, and know that I need to download the correct bootchain.
Question: How do I determine which one that is?
I'm running the (new, awful) version of 4.1.2 that just updated my Verizon Galaxy S3. Currently, I'm stock... but not for long.
Thanks for the assistance.
Click to expand...
Click to collapse
You can get everything you need from the S3 link in my signature. Instructions are there also.
If anyone is more curious about this, you should google "2nd-init" or "milestone bootchain" theres a couple good blogs/posts discussing how they got past the locked boot loader on the Motorola Droid/ milestone.
Hello everyone, so I have a couple questions for you guys in regards to rooting my S3. Back in November when I got the phone, I had rooted it and unlocked it using Odin and the EZ-Unlock app off of the play store. Not long after that, i returned back to stock, and here we are 6/7 months later and I am wanting to re-root, but I have discovered that the way to go about this has since changed.
I have looked at this guide http://forum.xda-developers.com/showthread.php?t=2046439 and looked at these videos http://forum.xda-developers.com/showthread.php?t=2295146 but am still a little iffy about jumping right into this since the methods involved are different than the last time I did it. One thing I noticed on the guide that I linked is that they do not have the bootchain for the version on my phone (VRBMF1).
Basically so this thread does not turn into a short story, I am just going to ask if the steps I lay out is the correct way to go about this. I am strictly wanting to root and unlock so that I can flash to a custom ROM, mainly CM10.
1. install samsung drivers
2. download Odin
3. download the "both root and unlocked bootloader"
4. download VRALEC bootchain
5. download either CWM or TWRP
6. and for this step, should I just flash to either VRBMB1 or VRBMD3, or should I just skip this step since it is optional and go straight to flashing a custom ROM?
In addition to this, I have heard things mentioned about backing up the IMEI, and I see them saying you can do it in a Terminal Emulator (the su and reboot nvbackup commands) . Is this something that has to be done after root and unlock?
I would love to get back to rooted and running custom ROMS again, so any help you can provide would be greatly appreciated.
Bump.
Flash the VRBMD3 bootchain and backup your IMEI after rooting and unlocking the bootloader but before flashing a custom ROM.
Thanks for your reply. Is there any benefit to flashing the md3 bootchain if I am just going to be flashing to a custom ROM?
Sent from my SCH-I535 using Tapatalk 2
The boot chain makes a great stable platform before you go off on a custom. That way you can boot and make sure the root has taken
Sent from my SCH-I535
Lord_Tardis said:
The boot chain makes a great stable platform before you go off on a custom. That way you can boot and make sure the root has taken
Sent from my SCH-I535
Click to expand...
Click to collapse
Thanks for your reply. I am happy to report that I listened and flashed the VRBMD3 bootchain and am successfully unlocked and rooted and am running a custom ROM. I did not know that the bootchain would have an effect after I had flashed a custom ROM, so I am glad that I did that. Thanks for your replies everyone. One question though. Since my baseband version is VRBMF1, is there any downside to flashing the VRBMD3 bootchain or does it really matter?
Atwooooood said:
Thanks for your reply. I am happy to report that I listened and flashed the VRBMD3 bootchain and am successfully unlocked and rooted and am running a custom ROM. I did not know that the bootchain would have an effect after I had flashed a custom ROM, so I am glad that I did that. Thanks for your replies everyone. One question though. Since my baseband version is VRBMF1, is there any downside to flashing the VRBMD3 bootchain or does it really matter?
Click to expand...
Click to collapse
The mf1 is the most current radio data. I do not believe there is harm in flashing to an older one. The best bet is to find the one that gives you the best signal strength.
Sent from my SCH-I535
If I wanted to test a couple bootchains as far as signal strength goes , am I able to flash to a different one after I've already flashed a custom ROM or are there more steps involved?
Sent from my SCH-I535 using Tapatalk 2
Correct me if I'm wrong. But bootchains do not affect signal. Only modems/basebands. You can go download any which one as long as kids meant for your model/carrier.
Sent from my SCH-I535 using Tapatalk 4
Sandman-007 said:
Correct me if I'm wrong. But bootchains do not affect signal. Only modems/basebands. You can go download any which one as long as kids meant for your model/carrier.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
You, sir, are correct.
Sent from my SCH-I535 using xda app-developers app
Thanks for clarifying guys. Appreciate your alls help.
Sent from my SCH-I535 using Tapatalk 2
Ok so I never messed around with rooting until my phone got the 4.3 update the other night. I decided I hated the update so much that I did the saferoot method, and I'm now rooted.
Only after I did that did I discover that my bootloader is perma-locked and I can't try to unroot or rollback the android version or I'll hardbrick. I can't do roms. Essentially I can't fix what I rooted in order to fix, and trying to enter recovery mode and odin mode lights me up with a verizon warning. So:
1. Just what can I do SAFELY now that I'm rooted? I've already used titanium to uninstall the verizon apps, but I don't know what I'm doing beyond that to remove bloatware/make this thing faster.
2. Will there be a time in the future when I'll be able to totally unlock my phone and escape Verizon's tyranny even though I took the 4.3 OTA? I want to make it look like stock nexus android.
Thanks for any and all help!
1. That's about it. Maybe use Xposed and the Greenify module to hibernate apps that typically drain your battery. Can't do much more besides remove apps on TW 4.3.
2. Possibly or possibly never. Nobody knows if the Knox Bootloader and extra security checks put forth by Verizon will be overcome.
Sent from my SCH-I535 using Tapatalk 4
I use Greenify to hibernate apps I sometimes use and titanium backup to freeze apps I never use. I don't uninstall them just in case. It's running great for me, much better than 4.1.2
I know you can't downgrade from 4.3, but you can't unroot either?
Sent from my SCH-I535
The Arbiter said:
Ok so I never messed around with rooting until my phone got the 4.3 update the other night. I decided I hated the update so much that I did the saferoot method, and I'm now rooted.
Only after I did that did I discover that my bootloader is perma-locked and I can't try to unroot or rollback the android version or I'll hardbrick. I can't do roms. Essentially I can't fix what I rooted in order to fix, and trying to enter recovery mode and odin mode lights me up with a verizon warning. So:
1. Just what can I do SAFELY now that I'm rooted? I've already used titanium to uninstall the verizon apps, but I don't know what I'm doing beyond that to remove bloatware/make this thing faster.
2. Will there be a time in the future when I'll be able to totally unlock my phone and escape Verizon's tyranny even though I took the 4.3 OTA? I want to make it look like stock nexus android.
Thanks for any and all help!
Click to expand...
Click to collapse
go back to this forum: http://forum.xda-developers.com/showthread.php?t=2565758 Lots of comments on how to unroot if that is what you want. and give the DEVs some time, there will be a method, there is usually one found after a while. OR stick with what you have for a while, i can make mine look just like my rooted version with little variation, and stock isn't too bad, so far.
be patient grasshopper...
Would I be able to Odin back to 4.1.2 so I can re root, unlock bootloader and flash custom ROM's again? Thanks
bmatty14 said:
Would I be able to Odin back to 4.1.2 so I can re root, unlock bootloader and flash custom ROM's again? Thanks
Click to expand...
Click to collapse
No. If you took the 4.3 OTA you are stuck on it. You will hard brick your device if you try to Odin back to 4.1.2. Been mentioned tons of times in numerous threads.
Sent from the Shark Tank using XDA Premium 4 mobile app
The Arbiter said:
Ok so I never messed around with rooting until my phone got the 4.3 update the other night. I decided I hated the update so much that I did the saferoot method, and I'm now rooted.
Only after I did that did I discover that my bootloader is perma-locked and I can't try to unroot or rollback the android version or I'll hardbrick. I can't do roms. Essentially I can't fix what I rooted in order to fix, and trying to enter recovery mode and odin mode lights me up with a verizon warning. So:
1. Just what can I do SAFELY now that I'm rooted? I've already used titanium to uninstall the verizon apps, but I don't know what I'm doing beyond that to remove bloatware/make this thing faster.
2. Will there be a time in the future when I'll be able to totally unlock my phone and escape Verizon's tyranny even though I took the 4.3 OTA? I want to make it look like stock nexus android.
Thanks for any and all help!
Click to expand...
Click to collapse
Same situation...I flashed Stock_rooted_4.3 after taking the OTA and my phone said unauthorized software detected, take to Verizon. Luckily I found the original image and it flashed back to totally stock 4.3 build ML1.
Basic root would be fine for now so would you please link me to the method you used if you are also on ML1?
Thanks
LordAlexx said:
Same situation...I flashed Stock_rooted_4.3 after taking the OTA and my phone said unauthorized software detected, take to Verizon. Luckily I found the original image and it flashed back to totally stock 4.3 build ML1.
Basic root would be fine for now so would you please link me to the method you used if you are also on ML1?
Thanks
Click to expand...
Click to collapse
here you go: http://forum.xda-developers.com/showthread.php?t=2565758
saferoot is discovered for Galaxy S4 but can be use safely on S3 also.
buhohitr said:
here you go: http://forum.xda-developers.com/showthread.php?t=2565758
saferoot is discovered for Galaxy S4 but can be use safely on S3 also.
Click to expand...
Click to collapse
OK cool...just wanted to be sure; I am subscribed to that thread. Just gotta get ADB to see the phone. Everything else works via USB in all modes, kinda odd.
Thanks!
I have read through multiple posts but I am still slightly confused. So I have a Samsung Galaxy S3 running VRUCNC1. I have read that it is unrootable and that using ODIN to downgrade is the only option, but I have also read that downgrading will brick your phone. Could someone assist me with this?
Trevon75 said:
I have read through multiple posts but I am still slightly confused. So I have a Samsung Galaxy S3 running VRUCNC1. I have read that it is unrootable and that using ODIN to downgrade is the only option, but I have also read that downgrading will brick your phone. Could someone assist me with this?
Click to expand...
Click to collapse
Once your phone has taken either 4.3 OTA (VRUCML1 or VRUCNC1), downgrading to 4.1.2 will result in a hard brick. You can only switch between VRUMCL1 and VRUCNC1, the phone will essentially not boot on any other firmware. Downgrade to VRUCML1 then root via Saferoot. It is safe to do this.
Users with unlocked bootloaders (aka people who did not take either 4.3 OTA) can switch to ICS or JB 4.1.2 via Odin without fail or issue. We can do so, unless somehow we end up taking either 4.3 ota.
SlimSnoopOS said:
Once your phone has taken either 4.3 OTA (VRUCML1 or VRUCNC1), downgrading to 4.1.2 will result in a hard brick. You can only switch between VRUMCL1 and VRUCNC1, the phone will essentially not boot on any other firmware. Downgrade to VRUCML1 then root via Saferoot. It is safe to do this.
Users with unlocked bootloaders (aka people who did not take either 4.3 OTA) can switch to ICS or JB 4.1.2 via Odin without fail or issue. We can do so, unless somehow we end up taking either 4.3 ota.
Click to expand...
Click to collapse
Thank you! I apologize for the late response, but you explained this perfectly for me. I was able to downgrade and root, install safestrap, and even flash a ROM. However, I have only gotten one ROM to flash correctly. Is there another step I have missed? I have only gotten CleanROM 8.1 to flash correctly while everything else flashes but does not boot. I really appreciate the help!
Trevon75 said:
Thank you! I apologize for the late response, but you explained this perfectly for me. I was able to downgrade and root, install safestrap, and even flash a ROM. However, I have only gotten one ROM to flash correctly. Is there another step I have missed? I have only gotten CleanROM 8.1 to flash correctly while everything else flashes but does not boot. I really appreciate the help!
Click to expand...
Click to collapse
Unsure why it won't flash any other roms try this thread it's a good starting point
http://forum.xda-developers.com/showthread.php?t=2639337
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
My brother gave me his Bell locked Galaxy S4 today, so I've spent the day trying to unlock it to use on Rogers. After much reading of posts here, I managed to get it unlocked as follows:
I am no expert, though I am experienced with rooting and such. The following steps describe what I did to unlock my phone. I am not sure if all of these steps are necessary but they did work. Since I am not an expert, there is no point asking me questions if you have any problems, since I will not be able to help. Of course, some of these steps can void warranty, and could brick your phone if done improperly. I am not responsible for anything bad that happens.
1) Download and flash stock Columbia 4.2.2 rom with Odin (i used 3.09)
2) Root with CF-Auto Root
3) Flash Clockwork Mod (I use Caboomi's img2tar for this)
4) Get rid of KNOX by "installing" DE-KNOX zip in CWM (DE-SAMSUNGNIZER_KNOX_REMOVAL_SCRIPT_V2.0)
5) Download Chainfire's RegionLock Away, install and run
6) Restart and success!
7) Finally, I flashed the current (4.4.2) firmware of the provider I switched to (Rogers), as I was having problems with the phone and some other things. This seems to be operating properly now.
Note: I was able to install 4.2.2 rom even though I was unable to downgrade to 4.3. (Fail to flash aboot like many people get) I assume this is because the 4.2.2 rom does not modify aboot. Also, Chainfire states the RegionLock Away only works for the Note 3, however many people have used it successfully on the S4 as well. It did not work for me on 4.4.2, so I'm guessing either installing 4.2.2, or removing KNOX, or both got it to work.
I hope this helps some people. If it does, thank the developers who made everything above!
What firmware where you on when u began? 4.4.2? Or earlier?
Sent from my SGH-I337M using XDA Free mobile app
I don't think KNOX affects the sim locking and unlocking. I know for sure that RegionLockAway works in 4.2.2 because I downgraded my phone to that rom and unlocked it...without doing any of the KNOX related stuff.
I think this method you are using trips the KNOX fuse when you downgrade from KitKat.
OK but how did u downgrade? I don't care about the Knox flag mine is tripped I just want to get back to 4.2 so I can use real custom Roms. Everything I have seen suggests you cannot downgrade
Sent from my SGH-I337M using XDA Free mobile app
Psykologikal said:
OK but how did u downgrade? I don't care about the Knox flag mine is tripped I just want to get back to 4.2 so I can use real custom Roms. Everything I have seen suggests you cannot downgrade
Sent from my SGH-I337M using XDA Free mobile app
Click to expand...
Click to collapse
I downgraded to 4.2.2 by simply using ODIN. This process will trip the fuse. The trick in getting it to work is to clear all of the leftover files from 4.4.2 after the flash. You can't boot directly into the system after the flash. You have to go into recovery mode and do a factory reset. If you don't do this, the system wouldn't boot as what everyone is finding.
So do I need to do a nand erase or something? Or just regular flash then boot into recovery factory reset then flash again? Cuz I would love to get back to 4.2 and start flashing custom Roms agaib
Sent from my SGH-I337M using XDA Free mobile app
Psykologikal said:
So do I need to do a nand erase or something? Or just regular flash then boot into recovery factory reset then flash again? Cuz I would love to get back to 4.2 and start flashing custom Roms agaib
Sent from my SGH-I337M using XDA Free mobile app
Click to expand...
Click to collapse
Just a simple factory reset should do.
So nothing for 4.4.2 directly? We have to downgrade? Thanks