hello, Is there a toolkit for nexus 5x for users using mac?
IMO i wouldn't bother with tool kits, learn to use fastboot and adb, it will make troubleshooting easier since you will be able to see what is going on, toolkits mask that and always have a chance of crashing in the middle of a process without you knowing where it stopped working.
Related
Hello Everyone. Im receiving my slide tomorrow and you already know i must root this (been a g1 user with root for 2 years now). But as i see, rooting this device isn't like a G1 and this involves ALOT of adb work which in my situation kind of sucks because my windows vista fails and wont boot and im stuck on ubuntu and my adb on ubuntu is kind of crazy (doesn't adb push anything and it doesn't seem like all the adb commands even work.. only thing that seems to work is getting an logcat) and all rooting methods involve using windows. I don't know which version my slide is going to come with i dunno if its going to have the OTA update or not already preinstalled because if it does i can't use the linux simpleroot by eugene and wesgarner because it requires you to be on the stock firmwire. Also from researching i see hardly anyone can revert back to the stock firmwire. So any suggestions? I hate being on Stock.. Alot lol
Hi all
Is there a thread on how to root on a Mac? I've been looking for it but not able to find it.
BTW, I'm on Verizon.
Thanks
Just check the manual methods for windows, but use "./" in front of the commands. There are no "one-click" methods for OSX to my knowledge. But its simple enough manually. Its only a few prompts to unlock the bootloader and/or push a few files.
If you need just ADB and Fastboot for OSX (so you don't have to install the SDK), I've attached them to this post.
I do like manual methods, I'll check them out and give them. Thank you for the file
Yup, use fastboot to do it. Do not forget the "./" it took me while to figure out that i needed to physically use ./ instead of just /
Rooting with a Mac
I just happened to end up with a Mac Book Pro, Cheap. So I am new to it. I was just waiting to get a new computer so I could root m Galaxy Nexus.
Could somebody provide a little more detail on exactly how t is done.
addcancercat said:
I just happened to end up with a Mac Book Pro, Cheap. So I am new to it. I was just waiting to get a new computer so I could root m Galaxy Nexus.
Could somebody provide a little more detail on exactly how t is done.
Click to expand...
Click to collapse
Watch my video. Its for a nexus s 4g but the steps are exactly the same. https://www.youtube.com/watch?v=sP9ZDWmbLVM&feature=youtube_gdata_player
Sent from my Galaxy Nexus using xda premium
Back in my htc evo days rooting was easy (to me at least). Easy because I didn't know how to use and command prompt and still don't. I returned my nexus s because I was a little intimidated by the process. I just purchased the nexus and want to root. What is the easiest way to root this bad boy hopefully without using command prompt
You can use a toolkit for a "one click" method.
I recommend you just learn how to open the command prompt and time like 10 lines to root your phone. Honestly if you can't figure out how to do that then I'm not sure you deserve to gain root lol. Whether you choose to use that method or not, the knowledge will help when (see how I said when, not if?) things go wrong.
Easiest us the toolkit. On my phone otherwise I would link you to it just search toolkit. Others will say to learn the command prompts, I won't since you just asked for the easiest way.
Sent from my Galaxy Nexus using Tapatalk 2
http://forum.xda-developers.com/showthread.php?t=1529058
This will show you how to do it properly.
You could use a toolkit but learning is the best way otherwise you will end up posting here that you have some problem you can't fix all because you didn't bother learning at the start.
The nexus is probably the easiest phone to root/flash roms and kernels to.
Thanks guys i will try to learn the command prompt
Sorry for the hijack, but it is (somewhat) related.
I just purchased a Galaxy Nexus from the play store this afternoon. I am coming from an Infuse, running a Custom rooted GB rom.
I had to flash back to stock, because of a no-root policy being pushed down from my work, since I use my handset to collect work email.
For the Nexus, is there a temporary unroot process/application I could run so that the [GOOD] application will not detect root?
I have already cleared that config/situation with our infrastructure team.
- Thanks, Kevin
KevinAlbrecht said:
Sorry for the hijack, but it is (somewhat) related.
I just purchased a Galaxy Nexus from the play store this afternoon. I am coming from an Infuse, running a Custom rooted GB rom.
I had to flash back to stock, because of a no-root policy being pushed down from my work, since I use my handset to collect work email.
For the Nexus, is there a temporary unroot process/application I could run so that the [GOOD] application will not detect root?
I have already cleared that config/situation with our infrastructure team.
- Thanks, Kevin
Click to expand...
Click to collapse
I think supercurio has a temporary unroot app in the market.
Thanks. I tried all of those apps when I was first presented with this obstacle. It did not work for the rom I was using because they had developed some sort of auto root on reboot, built in.
So I guess I am asking if anyone has experience with them working. I plan in keeping it stock, but wanted to know if this was an option.
Sent from my SAMSUNG-SGH-I997 using xda premium
I've been using the GNex toolkit since I got my nexus and never had one issue. Even flashed stock 4.1.1 on it. My question is, why is everyone so against the toolkit? Why is it so dangerous? Please don't bash me because I came from an Atrix 2 and have only been using the nexus for a couple weeks but I'm just curious. Thanks.
Sent from my Galaxy Nexus using xda premium
http://forum.xda-developers.com/showthread.php?t=1469909
basically, the toolkits sometimes fail.. and fail hard. like at one point, the toolkit wanted to flash a verizon firmware on to a GSM phone (which can brick the phone). or something goes wrong, and the user has no idea how to fix it so the thread begins with "i used such and such toolkit, but i have no idea why my phone wont boot. HALP!"
I would like to say that the Toolkit actually is a shell of the adb command and fastboot command. That's all.
Using a toolkit means clicking a few buttons and not thinking about what you're doing.
%90 percent of all "OMG BRICKED" posts begin with "I used _______ toolkit to unlock and root. I've been on ____________ for ________ weeks and flashed ____________ and now it won't boot!"
This in itself speaks leaps-and-bounds about the user.
Using a toolkit to unlock and root should have no impact on future usage.
If you used toolkitA and she used toolkitB the information is not relevant.
This leads me to believe they think the toolkit is doing some mystical process (it isn't) specific to that "method" or "program."
Then, say, I want them to ADB push something to their phone.
Or ADB pull their SDCard to save it.
They have no idea what I'm talking about...and I (and others) are stuck trying to teach them how to set up ADB and get the drivers correctly installed with a broken device.
If you have ADB set up...and know it's working...it's 100x easier to fix things when they go wrong.
But if you're "bricked" and then tell us "adb devices" isn't showing anything and all commands list "no device found" we don't know if it's because ADB/drivers are set up incorrectly or if your phone is truly hosed to the point of being unrecognized...again, leading to more guesstimation in the debugging process.
Also, the toolkit will say "done" and not spit out any errors that help to debug if something goes wrong.
All-in-all...
Any user who chooses the toolkit over a few simple commands is going to end up with more problems...due to lack of knowledge.
Doing things manually is not only easy; but a learning process.
I'd recommend you look at my guide.
You don't need to unlock/root again or anything...
But get ADB/Fastboot set up and push a file to your phone to see how it all works.
Right packaged all in one folder with basic commands. But wouldnt the main cause of toolkit errors be user error? Because all the commands are set for each option example: if I choose to unlock the boot loader on GSM Maguro 4.1.1 then it'll 100% always unlock my boot loader correct? But if I, by mistake, choose the Toro etc and it messes me up then I could in theory blame the toolkit because I didn't pay attention therefore I would've suspected the toolkit as the culprit. So I'm saying, errors with the toolkit are all basically user errors right?
Sent from my Galaxy Nexus using xda premium
DarkJatrix said:
Right packaged all in one folder with basic commands. But wouldnt the main cause of toolkit errors be user error? Because all the commands are set for each option example: if I choose to unlock the boot loader on GSM Maguro 4.1.1 then it'll 100% always unlock my boot loader correct? But if I, by mistake, choose the Toro etc and it messes me up then I could in theory blame the toolkit because I didn't pay attention therefore I would've suspected the toolkit as the culprit. So I'm saying, errors with the toolkit are all basically user errors right?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
no. its not all user error. this is an example: http://forum.xda-developers.com/showthread.php?t=1803743
Jubakuba said:
Using a toolkit means clicking a few buttons and not thinking about what you're doing.
%90 percent of all "OMG BRICKED" posts begin with "I used _______ toolkit to unlock and root. I've been on ____________ for ________ weeks and flashed ____________ and now it won't boot!"
This in itself speaks leaps-and-bounds about the user.
Using a toolkit to unlock and root should have no impact on future usage.
If you used toolkitA and she used toolkitB the information is not relevant.
This leads me to believe they think the toolkit is doing some mystical process (it isn't) specific to that "method" or "program."
Then, say, I want them to ADB push something to their phone.
Or ADB pull their SDCard to save it.
They have no idea what I'm talking about...and I (and others) are stuck trying to teach them how to set up ADB and get the drivers correctly installed with a broken device.
If you have ADB set up...and know it's working...it's 100x easier to fix things when they go wrong.
But if you're "bricked" and then tell us "adb devices" isn't showing anything and all commands list "no device found" we don't know if it's because ADB/drivers are set up incorrectly or if your phone is truly hosed to the point of being unrecognized...again, leading to more guesstimation in the debugging process.
Also, the toolkit will say "done" and not spit out any errors that help to debug if something goes wrong.
All-in-all...
Any user who chooses the toolkit over a few simple commands is going to end up with more problems...due to lack of knowledge.
Doing things manually is not only easy; but a learning process.
I'd recommend you look at my guide.
You don't need to unlock/root again or anything...
But get ADB/Fastboot set up and push a file to your phone to see how it all works.
Click to expand...
Click to collapse
I'm very familiar with ADB I had an HTC amaze and a couple days after the release I had to learn adb really quick in unlocking the boot loader and flashing custom Roms. I just like convenience of having everything in one folder and one program. I do trust ADB but my issue has always been putting files in right folders and pushing and pulling files etc. Lol. But I appreciate the info you guys. I'll think twice before using toolkits again.
Sent from my Galaxy Nexus using xda premium
Zepius said:
no. its not all user error. this is an example: http://forum.xda-developers.com/showthread.php?t=1803743
Click to expand...
Click to collapse
Lest* better to use adb, I've used jubakuba's guide and worked flawless.
I don't hate toolkits but they seem to cause more problems rather then solve. Anyone who I see needs to root I direct them to jubakuba's thread.
Sent from my Galaxy Nexus using Tapatalk 2
withbloodskies said:
Lest* better to use adb, I've used jubakuba's guide and worked flawless.
I don't hate toolkits but they seem to cause more problems rather then solve. Anyone who I see needs to root I direct them to jubakuba's thread.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
That's what I'm saying. I am plenty smart enough to read before I flash, therefore I wouldn't of flashed that and I wouldn't of had an issue but if someone else would've flashed it then it would've technically been their fault for not paying attention. I understand that the toolkit had the mistake but if I pay close attention than I'll notice the mistakes and avoid them. Does that sou d pretty knowledgeable?
Sent from my Galaxy Nexus using xda premium
I have a 4.4.2 LTE N7 (KVT49L) that I'm rooting and installing xposed for sms today. I'm planning on using the Wug kit. I don't have enough stuff on it to worry about backing up apps and such. I have several rooted devices but this will be the first I root myself.
Any final tips before I start?
bob60626 said:
I have a 4.4.2 LTE N7 (KVT49L) that I'm rooting and installing xposed for sms today. I'm planning on using the Wug kit. I don't have enough stuff on it to worry about backing up apps and such. I have several rooted devices but this will be the first I root myself.
Any final tips before I start?
Click to expand...
Click to collapse
Without knocking toolkits (I've used them myself also still do when I am lazy) I'd use fastboot and flash manually etc, that way if you run into any problems you can fix them. Isn't really much else tbh, Wug's toolkit is pretty good for stuff though.
radicalisto said:
Without knocking toolkits (I've used them myself also still do when I am lazy) I'd use fastboot and flash manually etc, that way if you run into any problems you can fix them. Isn't really much else tbh, Wug's toolkit is pretty good for stuff though.
Click to expand...
Click to collapse
^^THIS^^ Especially since this is your first time rooting your own device. Doing it manually the first time will help you learn what exactly is going on in each step. The Nexus devices are super simple to unlock and root manually with only a few command prompts.
Thanks guys! I actually started before any replies... that was easy! The hardest part was the backup.
I installed xposed and have a few modules on there now. That was even easier. I'm getting sms now through hangouts (go sms pro was too laggy) with my sim in, though I'm still getting the pop up notifications.
Sent from my Nexus 7 using Tapatalk
I agree with previous replies. You can boot into recovery without flashing it to root from fastboot, and it really is the best way to go always. Added bonus: once you get used to all of the fastboot and adb commands, you are much more proficient in fixing problems when they arise.
Sent from my Nexus 7 2013 using Tapatalk