Related
I'm been searching the Nexus One Q&A section for an answer to my problems, but I couldn't find a solution. I'm running a stock version of 2.3.3 on my phone. It's never been rooted, and I have never rooted a device as well. I'm entirely new to this and have no idea what I'm doing. My device has no warranty but I'm still concerned about it. Again, I have no experience at all.
Also, I don't know if I would want to unlock the bootloader as I could lose everything. If there is a way to retain everything reliably (I don't know if those back-up applications are the most effective) that would be convenient.
So, can anyone help me root my virgin Nexus One?
Thanks for your time,
Tread Fox
Mybackup pro backs up apps and data. After you root you can use titanium backup. Also smsbackup and restore for your SMS :]
Alright, that's re-assuring. But what about actually rooting the phone?
Hmm I can't help with rooting because I have an Evo, just sharing some backup knowledge :/
You can use this threads wiki for the N1 and the stickies here:
http://www.nexusoneforum.net/forum/nexus-one-development-hacking/
You need to read several guides until you get a good idea of what you are doing and why.
Use the apps mentioned above to back up your phone info, once rooted you can do a complete and immediate phone backup of everything, like a full image pc backup.
If you do the one-click method, make sure it is for you OS, you will be limited in some things you can do, like fastboot commands and will be unrooted if you dl OTA's.
Read, Read, Read!!!
Before you flash a rom read the op page carefully and the last 20 pages for tips, info, issues etc.
Ken
This works for 2.3.3?
EDIT: So my only options are to unlock the bootloader or roll back? Which do you recommend?
You probably saw this in XDA wiki for N1:
http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Guides_&_Tutorials#Root
I would unlock, more options as you get more into flashing and you can't be unrooted by Google OTA's.
This is good guide for the S, but you can glean steps and maybe better understanding for the process. At the bottom in related posts is a root guide. I like the steps, but things like the fastboot and superuser may not be for the N1. However you can find them online. Just an easy to understand guide.
http://jaxov.com/2011/02/install-android-2-3-3-gingerbread-on-nexus-one-manually/
TreadFox said:
This works for 2.3.3?
EDIT: So my only options are to unlock the bootloader or roll back? Which do you recommend?
Click to expand...
Click to collapse
Sorry man, just got your message (phone died on me, and I've been playing with my other toys anyway...)
Yes, your options are to unlock the bootloader or roll back.
Both options will lose all date, so you need to backup either way.
My preference is to unlock the bootloader, but I can understand why people may not want to. Unlocking the bootloader can effect any warranty that's remaining on the phone (the phone has a 1 year warranty, no matter who owns it).
Thanks for all your help guys. Does anyone have a specific guide for rolling back? I don't need or want a custom rom, just setcpu...
Read my signature, execute PASSIMG method with FRG33. if it doesn't work (and sometimes it doesn't) - you're out of luck.
TreadFox said:
Thanks for all your help guys. Does anyone have a specific guide for rolling back? I don't need or want a custom rom, just setcpu...
Click to expand...
Click to collapse
This is how to go back to FRG33: http://forum.xda-developers.com/showpost.php?p=11745519&postcount=21
But if I were you, I would just unlock your bootloader. Makes life easier.
I'll unlock the bootloader. I saw a guide on the nexusoneforums on how to do this. But it's about a year old. Is there anything that's changed?
I'm sorry I'm being indecisive, I'm trying to take suggestions from anybody!
TreadFox said:
I'll unlock the bootloader. I saw a guide on the nexusoneforums on how to do this. But it's about a year old. Is there anything that's changed?
I'm sorry I'm being indecisive, I'm trying to take suggestions from anybody!
Click to expand...
Click to collapse
No, nothing has changed. You need to have the Android SDK set up properly. Then just boot into the bootloader by holding down the trackball while pushing the power button. Then open a command prompt in the directory where the fastboot.exe file is (probably C:\Program Files\Android\android-sdk-windows\tools) then just type: fastboot oem unlock
Follow this to set up the, it's easier (just the first post):
http://www.nexusoneforum.net/forum/...mple-sdk-setup-manual-root-guide-windows.html
Sent from my Nexus One using XDA Premium App
I don't know what I'm doing. This is confusing. When I hook up the phone to the pc it says its found new hardware. I'm running XP. What do I do? I think I'm going over my head with this. Also, how do I make sure mybackup will work? I don't want to lose my stuff!
TreadFox said:
I don't know what I'm doing. This is confusing. When I hook up the phone to the pc it says its found new hardware. I'm running XP. What do I do? I think I'm going over my head with this. Also, how do I make sure mybackup will work? I don't want to lose my stuff!
Click to expand...
Click to collapse
If you feel like you are in over your head, you probably are, and have not done enough reading. I just looked at danger-rat's post in the link he provided, and it seems quite straight forward, no? He even tells you how to install the drivers. "Step #3" under "To install the drivers" in the first post TELLS you that windows will detect new hardware and will ask you to install a driver. What seems to be the problem?
I did, and nothing happened. At all. I asked for it to download files from usb driver. Nothing happened at all. Is it something I'm doing wrong?
I have the SDK file on my desktop, I have all of the files inside that are needed. When the computer asks me to download the drivers, I re-direct to the usb driver folder located in the SDK which is located on my desktop. The computer claimed installation was successful, but nothing happened. When I try clicking the fastboot.exe in the tools file, it immediately forcecloses. Is it my pc? Is it the file? Is it the phone? I did read the material and so far nothing has helped.
TreadFox said:
I did, and nothing happened. At all. I asked for it to download files from usb driver. Nothing happened at all. Is it something I'm doing wrong?
I have the SDK file on my desktop, I have all of the files inside that are needed. When the computer asks me to download the drivers, I re-direct to the usb driver folder located in the SDK which is located on my desktop. The computer claimed installation was successful, but nothing happened. When I try clicking the fastboot.exe in the tools file, it immediately forcecloses. Is it my pc? Is it the file? Is it the phone? I did read the material and so far nothing has helped.
Click to expand...
Click to collapse
Well, after you have installed the driver that the computer asked you to install. That's just the driver needed to sync your file and stuff on your sd card. The other driver and adb setup is needed to actually access your phone.
So I asked for it to install the wrong files? What files do I install? Because from that guide it said point to usb driver. I'm only following the guide like you all asked, and nothing happened.
You don't launch fastboot by clicking on it windows.
Sent from my Nexus One using XDA App
So I am a new person and therefor can not post this in the development thread under the forum where I feel it would belong with the other root related questions.... So i followed the SUPER GUIDE to root my phone (Thank you so much Slapshot and PirateGhost, I was beginning to regret not getting a skyrocket until I found your thread). My super user is running into an issue I can not seem to fix.....
Maybe this is simple or maybe I really messed something up....
Basically none of my apps have root anymore (they did at one point and to my knowledge I change nothing...)
When I go to the Super User app to update my binaries and hopefully get any issues resolved I am greeted by the following error message in the update log: "Failed to find currently installed SU binary. Update cannot continue"
Is there a resolution for this? I have not found anyone even running into the same issue on the Vivid.....
A little nervous.... I didnt have near this many issues rooting my ATRIX and modding the living daylights out of that.
Have you checked with Root Checker Basic to see if you even have Root? If you didn't follow the Super Guide step by step your phone could have relocked after you turned your phone off/on.
If it still fails to update you could try SuperUser Update Fixer.
Yes I have check with root checker.
This may be a dumb question but how do I uninstall Superuser? When I go to the typical application management it does not give me the option. I have done an install again to overwrite the files and nothing changed there.
I followed the instructions step by step (though obviously I messed up somewhere...)
Sent from my HTC PH39100 using XDA App
Kraizk said:
So I am a new person and therefor can not post this in the development thread under the forum where I feel it would belong with the other root related questions.... So i followed the SUPER GUIDE to root my phone (Thank you so much Slapshot and PirateGhost, I was beginning to regret not getting a skyrocket until I found your thread). My super user is running into an issue I can not seem to fix.....
Maybe this is simple or maybe I really messed something up....
Basically none of my apps have root anymore (they did at one point and to my knowledge I change nothing...)
When I go to the Super User app to update my binaries and hopefully get any issues resolved I am greeted by the following error message in the update log: "Failed to find currently installed SU binary. Update cannot continue"
Is there a resolution for this? I have not found anyone even running into the same issue on the Vivid.....
A little nervous.... I didnt have near this many issues rooting my ATRIX and modding the living daylights out of that.
Click to expand...
Click to collapse
Interesting... maybe your root didn't stick. We had a little trouble with that before but pirateghost fixed the CWM ROOT zip. You have a working CWM Recovery, correct?
In the superguide, I have a second option for root in case the first doesn't work. In your case, go ahead and try the second option. The one involving the supertool. That should get you perm root. If that doesn't even work, then we might have to put you back to stock and go at it again.
EDIT: BEFORE TRYING THE SUPERTOOL, try flashing the new CWM ROOT VER2 zip from CWM recovery and see if root sticks.
Slapshot, thank you for checking the General Thread, I really do appreciate that. I have tried both methods multiple times since the root failure seeing as so many people said they had to run the methods multiple times to make them stick (this admittedly may be part of the issue). The most recent one has been the CWM ROOT VER2. Still no dice. Is there a method to remove and re install super user? Or am I reading into the error too literally and instead I just basically do not have root.
Kraizk said:
Slapshot, thank you for checking the General Thread, I really do appreciate that. I have tried both methods multiple times since the root failure seeing as so many people said they had to run the methods multiple times to make them stick (this admittedly may be part of the issue). The most recent one has been the CWM ROOT VER2. Still no dice. Is there a method to remove and re install super user? Or am I reading into the error too literally and instead I just basically do not have root.
Click to expand...
Click to collapse
No problem. At this point I think you may just not have root... but first, go ahead and go into bootloader (power off, then power on while holding power and vol down). Does your device say unlocked?
*Just a clarification*
You have to unroot your phone to get rid of it Idk why I put uninstall/reinstall earlier...still out there from last night I guess.
slapshot30 said:
No problem. At this point I think you may just not have root... but first, go ahead and go into bootloader (power off, then power on while holding power and vol down). Does your device say unlocked?
Click to expand...
Click to collapse
Yes the device still says unlocked. That was one of the first things I checked... Haha....
As I said ive flashed the rooted CWM and it says it went over successfully.
If i use the Zerg exploit it still seems to go over successfully (I realize this has a tenancy to mess with internal storage and only provide a temp root but i do not even get that temp root).
How would I unroot my device? Do you mean flash to stock and relock my boot loader?
As I said I have flashed several devices in the past (Atrix, eee pad transformer, HTC Inspire, HTC DINC, SAMSUNG GALAXY S T-Mobile) but I am not completely up to date on all of the technical terms...
Kraizk said:
Yes the device still says unlocked. That was one of the first things I checked... Haha....
As I said ive flashed the rooted CWM and it says it went over successfully.
If i use the Zerg exploit it still seems to go over successfully (I realize this has a tenancy to mess with internal storage and only provide a temp root but i do not even get that temp root).
How would I unroot my device? Do you mean flash to stock and relock my boot loader?
As I said I have flashed several devices in the past (Atrix, eee pad transformer, HTC Inspire, HTC DINC, SAMSUNG GALAXY S T-Mobile) but I am not completely up to date on all of the technical terms...
Click to expand...
Click to collapse
Yes, I mean relock the bootloader and back to stock rom, then try again. Do you know how to get back to stock?
slapshot30 said:
Yes, I mean relock the bootloader and back to stock rom, then try again. Do you know how to get back to stock?
Click to expand...
Click to collapse
actually that one I do not know how to do... I realize this is probably somewhat annoying because I am sure you have said how to do it before.... Some help would be greatly appreciated
Kraizk said:
actually that one I do not know how to do... I realize this is probably somewhat annoying because I am sure you have said how to do it before.... Some help would be greatly appreciated
Click to expand...
Click to collapse
I haven't told anyone how to do it surprisingly, and I'm more than happy to help . I was honestly thinking about adding reverting back to stock to the superguide, and I think I just may do that. Here is the link. Pirateghost is the man.
http://forum.xda-developers.com/showpost.php?p=20821226&postcount=4
Thank you for this and all of your help, people like you and ghostpirate are why i still feel like I can turn to the XDA community. I will try this firs thing in the morning and give an update on how things went. I would try it tonight but lets be honest, its the 1st of the year and the last thing I need to be doing is messing with technology.....
Kraizk said:
Thank you for this and all of your help, people like you and ghostpirate are why i still feel like I can turn to the XDA community. I will try this firs thing in the morning and give an update on how things went. I would try it tonight but lets be honest, its the 1st of the year and the last thing I need to be doing is messing with technology.....
Click to expand...
Click to collapse
It's no problem, this isn't a dumb question or easy issue by any means. If the method I directed to you doesn't work, let me know. There is another way to do it without all the code.
slapshot30 said:
I haven't told anyone how to do it surprisingly, and I'm more than happy to help . I was honestly thinking about adding reverting back to stock to the superguide, and I think I just may do that. Here is the link. Pirateghost is the man.
http://forum.xda-developers.com/showpost.php?p=20821226&postcount=4
Click to expand...
Click to collapse
Worked perfectly. I flashed it back to stock using the thread you linked me to. Then I did the CWM Root method and so far so good. I appreciate all of your help
Nice, I'm glad you were able to get everything working.
Sent from my HTC PH39100 using xda premium
So this has been mind breaking for me. I failed to flash the blackrose hboot everytime i trie and on every rom. It gets to the point where it has sent it files and then it says <waiting for device>. This happens on stock, BuglessBeast, rcadsmixhd 2.3 & 1.6 and hypersense (i like sense ). Anyone has any advice . Btw it did not brick it.
the problem your having isn't actually related to which rom your using on your phone. its that its not being detected as an adb device. you need to make sure that your drivers are installed and you see it in device manager as an ADB interface under Android Phone.
m0_t3 said:
the problem your having isn't actually related to which rom your using on your phone. its that its not being detected as an adb device. you need to make sure that your drivers are installed and you see it in device manager as an ADB interface under Android Phone.
Click to expand...
Click to collapse
Ehm, usb debugging is enabled and detected by the software at first. It gets to the point that it sends its hboot and after that it says something like error: deviceoffline and then stuck on waiting for device forever.
it could be that another program like PDAnet is interfering.
do you use any other programs on your PC that would use adb?
m0_t3 said:
it could be that another program like PDAnet is interfering.
do you use any other programs on your PC that would use adb?
Click to expand...
Click to collapse
well maybe htc sync but that was closed and its process was killed by taskmanager. No other programs i can think of.
well if your drivers are fine and there is nothing causing some form of interruption then. its probably an issue coming from the phone.
since you've tried it with so many different roms am guessing you didnt bother running/installing any apps
try it without the SD card inserted maybe.
thinking i should try and see if i can't replicate your issue find out what the issue is.
m0_t3 said:
well if your drivers are fine and there is nothing causing some form of interruption then. its probably an issue coming from the phone.
since you've tried it with so many different roms am guessing you didnt bother running/installing any apps
try it without the SD card inserted maybe.
thinking i should try and see if i can't replicate your issue find out what the issue is.
Click to expand...
Click to collapse
SO without my sd card it did not make any difference, apart from that it now mixes the message: adb server is out of date. Killing... and then waiting for device again.
the first time i installed blackrose i didn't use this method but maybe you can try flashing the hboot manually, which is what i normally do now, find it more straight forward.
[edit]
is your bootloader unlock?
m0_t3 said:
the first time i installed blackrose i didn't use this method but maybe you can try flashing the hboot manually, which is what i normally do now, find it more straight forward.
[edit]
is your bootloader unlock?
Click to expand...
Click to collapse
Ehm obviously yes how i can flash roms other wise? How do i flash this hboot then. BTW i have slcd nexesus one phone if that matters
http://forum.xda-developers.com/showthread.php?t=1270589
download the manual version zip file from there. the instructions are contained inside the zip.
he removed the caution about slcd N1's so i think that shouldn't be a problem anymore.
m0_t3 said:
http://forum.xda-developers.com/showthread.php?t=1270589
download the manual version zip file from there. the instructions are contained inside the zip.
he removed the caution about slcd N1's so i think that shouldn't be a problem anymore.
Click to expand...
Click to collapse
WOW you are awesome sir thank you now it works i wish you could click the thanks button 30.000 times.
race55 said:
Ehm obviously yes how i can flash roms other wise? How do i flash this hboot then. BTW i have slcd nexesus one phone if that matters
Click to expand...
Click to collapse
You can easily flash ROMs without unlocking the bootloader. All that is required is to root the original OS and install a custom recovery using a program like ROM Manager.
But I believe the phone is detected differently when in fastboot mode. Did you verify that the phone is still properly recognized in device manager when in fastboot mode?
What happens if you put the device into fastboot mode (holding the trackball when powering on) and you type fastboot devices at your command prompt?
Awesome.
Glad to help ^_^
Sent from my Nexus One using xda premium
Not directly related but I had to use BREditor and create a new hboot with the 200/16/220 layout and flash that. I just could not get the ICS roms to flash otherwise... strange...
bassmadrigal said:
You can easily flash ROMs without unlocking the bootloader. All that is required is to root the original OS and install a custom recovery using a program like ROM Manager.
But I believe the phone is detected differently when in fastboot mode. Did you verify that the phone is still properly recognized in device manager when in fastboot mode?
What happens if you put the device into fastboot mode (holding the trackball when powering on) and you type fastboot devices at your command prompt?
Click to expand...
Click to collapse
It gives me attached device: Ht9 and thencq lot of numbers
Sent from my HTC Nexus One using XDA App
race55 said:
It gives me attached device: Ht9 and thencq lot of numbers
Click to expand...
Click to collapse
Well, that definitely means that your device is recognized. Did you get it working?
bassmadrigal said:
Well, that definitely means that your device is recognized. Did you get it working?
Click to expand...
Click to collapse
Ehm using manual method it worked. It was kinda confusing because in the blackrose thread it says that u must use manual for osx. He should update his post
race55 said:
Ehm using manual method it worked. It was kinda confusing because in the blackrose thread it says that u must use manual for osx. He should update his post
Click to expand...
Click to collapse
If you throw a post at the end stating what you had to do, he would probably update his original post.
Not directly related but I had to use BREditor and create a new hboot with the 200/16/220 layout and flash that. I just could not get the ICS roms to flash otherwise... strange...
Click to expand...
Click to collapse
ICS is too big for the stock ROM space on the N1, so you need to make those alterations so it can fit. texasice did make a striped down version that works on stock though.
race55 said:
Ehm obviously yes how i can flash roms other wise? How do i flash this hboot then. BTW i have slcd nexesus one phone if that matters
Click to expand...
Click to collapse
If you are like me, you have been flashing ROMS on your phone for years before you ever unlocked the bootloader. I didn't do it until about 6 months ago because I needed to flash Blackrose. Also, don't bite the hand that is trying to feed you.
Okay so, since I'm sort of new, I wanted to ask a few questions:
1. Is it possible to root xperia x8 with manufacturing date 11w48? At least at 95% chance. I'm a bit scared of the bricking part...
2. If it is possible, what kind of "ROM" (if I understood correctly) should I get?
3. If I get hard bricked/soft bricked what's the chance my phone will be still usable.
That's about it. Please don't rage at me for "OMG USE SEARCH BUTTON" type of thing.
I have tried doing it but no results found. Just threads and posts of people updating their.. ROMs I gues? Correct me if I typed anything wrong there.
But yeah, help would be appreciated. Thanks!
Jetboard said:
Okay so, since I'm sort of new, I wanted to ask a few questions:
1. Is it possible to root xperia x8 with manufacturing date 11w48? At least at 95% chance. I'm a bit scared of the bricking part...
2. If it is possible, what kind of "ROM" (if I understood correctly) should I get?
3. If I get hard bricked/soft bricked what's the chance my phone will be still usable.
That's about it. Please don't rage at me for "OMG USE SEARCH BUTTON" type of thing.
I have tried doing it but no results found. Just threads and posts of people updating their.. ROMs I gues? Correct me if I typed anything wrong there.
But yeah, help would be appreciated. Thanks!
Click to expand...
Click to collapse
1. You can safely root your x8 regardless of when it is manufactured, you will not brick it
2. You have 11w48 so it is very risky to unlock your bootloader, i suggest you flash ROMS that is for stock
3. If you get soft bricked you can flash the stock firmware back using flashtool or SEUS, if it is a hard brick, you need to go to the nearest Service center or use a JTAG
Swyped via Tapatalk 2
Thanks a whole bunch. I thought I cannot root because of my manufacturer date. But what is a flash ROM tho?
Jetboard said:
Thanks a whole bunch. I thought I cannot root because of my manufacturer date. But what is a flash ROM tho?
Click to expand...
Click to collapse
you can root your phone. but you can't unlock bl.
when you root your phone, you cam install cwm recovery. simply dl a rom for stock kernel and go to recovery and install(flash) the rom. remember to check the instructions first.
Just because i don't doesn't mean i can't.
All what I found until today was that if I cannot unlock BL I cannot install CWM recovery.
Maybe it is related to model - mine is Sony Xperia J. Y2012.
There is no fastboot available.
Am I wrong, can I have CWM, nandroid backup etc on stock ROM as only such one I may flash ?
F308 said:
All what I found until today was that if I cannot unlock BL I cannot install CWM recovery.
Maybe it is related to model - mine is Sony Xperia J. Y2012.
There is no fastboot available.
Am I wrong, can I have CWM, nandroid backup etc on stock ROM as only such one I may flash ?
Click to expand...
Click to collapse
this is for x8. not sure how it works on J. but yeah we don't havt fastboot either. but we can install cwm even with a locked bl. again that's for se x8.
edit: my advice is go to your phone's subforum. you'll get your answers there.
Just because i don't doesn't mean i can't.
Thank you. I understand that lot of things is device dependent but thought there are non-breakable rules, like gravity,
and what is possible to do under certain circumstances was one of them.
Need walk through XDA forum once more, maybe there is a hope.
F308 said:
Thank you. I understand that lot of things is device dependent but thought there are non-breakable rules, like gravity,
and what is possible to do under certain circumstances was one of them.
Need walk through XDA forum once more, maybe there is a hope.
Click to expand...
Click to collapse
there probably are a few unbreakable rules, but not being familiar with your device i can't guarantee that it's safe or it would work.
Just because i don't doesn't mean i can't.
Despite lot of reading I still am missing knowledge.
Question is:
What is fastboot ?
I found more than one definition of it and compiled into my own.
1.
Of course fastboot.exe is Windows binary (part of flashtool pack) which does certain type of work.
This is not what we are interested in.
2.
I concluded that:
- fastboot is one of modes into what android device can wake up. Just like linux can boot in different ways or Windows into single mode.
- this feature is encoded into boot.img, it is not separate android application.
- boot.img will work only with related kernel.img. They are like love and marriage (which is like horse and carriage - Bundy's).
- Sony sometimes disables stock boot.img to boot into this mode then without replacing boot .img it is impossible.
More comments ?
Fastboot is protocol used to update the flash filesystem in Android devices from a host over USB. It allows flashing of unsigned partition images.
Just because i don't doesn't mean i can't.
Okay, I got one more last question. Is this guide http://forum.xda-developers.com/showthread.php?t=906195&nocache=1 okay to use for rooting? I'm still trying to find the LATEST safe ones =/ I wonder if this one is okay.
Um, I tried that one it didn't work. It said some stuff are missing, then it exited randomly etc.. Can someone give me a link or a short/long guide which I can use that's latest? I do have some X8 drivers in a .zip file but no idea how to install them. Thanks in advance.
Jetboard said:
Okay, I got one more last question. Is this guide http://forum.xda-developers.com/showthread.php?t=906195&nocache=1 okay to use for rooting? I'm still trying to find the LATEST safe ones =/ I wonder if this one is good.
Click to expand...
Click to collapse
I rooted mine with this
Means its safe
Sent from my X8
Having few issues with the SuperOneClick thing... It sometimes randomly exits, tells me that some stuff are missing etc. Any help? =/
Hello everyone! I was hoping to root my Nexus 6 with Android 6.0 on board but I can't seem to find any info on the topic, can anyone help me out??
Thanks!
ichigo663 said:
Hello everyone! I was hoping to root my Nexus 6 with Android 6.0 on board but I can't seem to find any info on the topic, can anyone help me out??
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3059493
http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452
Anything that can be done on a Linux system?
Don't use toolkits on marshmallow.
Download TWRP, fastboot flash it, flash custom kernel, and SuperSu 2.52
Sent from my Nexus 6 running cyosp using Tapatalk
Can any of these be done without a computer. I only have my phone
pitbullmommy45245 said:
Can any of these be done without a computer. I only have my phone
Click to expand...
Click to collapse
No you will need a computer to do this. I would not advise modding your device at all if you do not have access to a PC.
That root kit worked for me on MM and was easy. Why?
Found this http://forum.xda-developers.com/nexus-6/help/root-computer-t3218176
khw1959 said:
That root kit worked for me on MM and was easy. Why?
Found this http://forum.xda-developers.com/nexus-6/help/root-computer-t3218176
Click to expand...
Click to collapse
Dont even get me started on using a kit.
As to why. If something goes wrong you will need a PC to fix it.
khw1959 said:
That root kit worked for me on MM and was easy. Why?
Found this http://forum.xda-developers.com/nexus-6/help/root-computer-t3218176
Click to expand...
Click to collapse
Because if something goes sideways, and eventually it will, youl'll have no clue what it did, and how to fix it.
Nexus phones have open source tools, adb and fastboot, to manipulate them, they are very easy and straightforward to use.
I understand that coming from different phones, that only have hacks and tricks to unlock the bootloader and change the recovery, using tools seems obvious, but with a Nexus it's counterproductive, and makes fixing things so much harder.
Sent from my Nexus 6 running cyosp using Tapatalk
Thank for that insight. I wanted and took the easy/prepared route for unlocking and root of this phone. I was once familiar with manual way when the N2 was unlocked. I got to re-learn again. My last job made me very anal retentive about following instructions, and I think that made the rootkit easy to use. In 3 days I used it when I got with 5.1.1 and yesterday for 6.0. Today I flash Roms to find the one I like.
ichigo663 said:
Anything that can be done on a Linux system?
Click to expand...
Click to collapse
Adb and fastboot work on linux.
Any easy way to root 58r ??
Exqctly like K and N. Flash modified boot.ing, and flash SuperSu.zip in TWRP.
Sent from my Nexus 6 running cyosp using Tapatalk
Why do people keep saying you need a custom kernel??? BTW, used nexus root toolkit on the K build without problems, no luck on R(never had N) but the tool got updated.... However... I would not be using any thing chainfire Su related sinds it got sold out.
ghost010 said:
Why do people keep saying you need a custom kernel??? BTW, used nexus root toolkit on the K build without problems, no luck on R(never had N) but the tool got updated.... However... I would not be using any thing chainfire Su related sinds it got sold out.
Click to expand...
Click to collapse
Because at one time it did require a kernel change to get root.
ghost010 said:
Why do people keep saying you need a custom kernel??? BTW, used nexus root toolkit on the K build without problems, no luck on R(never had N) but the tool got updated.... However... I would not be using any thing chainfire Su related sinds it got sold out.
Click to expand...
Click to collapse
Because you needed a custom boot.img to root 58K too. It will either contain a modified kernel with SELinux set to permissive (I've patched mine by hand, so I know what I'm talking about), or contain an updated sepolicy binary to allow su to work. Also since you said you didn't have red triangle, it means your fstab.shamu was also replaced with one with disabled verity.
So. Don't use rootkits. If you do use rootkits and discover you don't know what's happening, at least please don't keep correcting those who try to help you.
scryan said:
Adb and fastboot work on linux.
Click to expand...
Click to collapse
I was hoping that someone would answer this. Flashing files and rooting on Linux is MUUUUCH easier than Windows. Why? No need for special drivers to recognize your device.
Even better, if you try to run a adb/fastboot command without having them installed, Linux will tell you the actual command for you to type and download/install them...all within the command window.
This might sound confusing, but it is really easy and seamless, in my opinion.
AarSyl said:
I was hoping that someone would answer this. Flashing files and rooting on Linux is MUUUUCH easier than Windows. Why? No need for special drivers to recognize your device.
Even better, if you try to run a adb/fastboot command without having them installed, Linux will tell you the actual command for you to type and download/install them...all within the command window.
This might sound confusing, but it is really easy and seamless, in my opinion.
Click to expand...
Click to collapse
Most of what you said depends on your distro.
On Arch you definitely need to add u-dev rules for the phone to be noticed, and if you dont have them installed and you try to run it, it won't tell you how to download.
But.... If you install via a package manager it will be automatically added to your path
Also, I have NEVER downloaded drivers for my phone in windows, and never needed to.
That's good to know. I should've added that I use Ubuntu as my distro, and I love it.