Database Develop

[Q] Froyo to Froyo update [NOOB]

Hi,
Complete noob here!!
So I had rooted 2.1 stock and update to Froyo leak first one it came out I believe (System Version 2.3.9.MB810), and lost root.
I would like to upgrade to the new 2.3.13 Froyo, but I'm not sure if I could just follow the instructions on the threads because they are about going from 2.1 rooted to new Froyo.
Is there a difference in the installation? Can I recover root? Do I loose everything I have? I have Titanium root but since I lost root it hasn't been backing up I believe
I been looking at both of these threads lately, sound like the instructions might work (again complete noob , so not sure)
thread: forum.xda-developers.com/showthread.php?t=764304
thread: androidforums.com/droid-x-all-things-root/174152-brand-new-froyo-2-3-13-a.html
Thanks for your help in advance.
Update
I used the instructions on the thread on here and ran into an error when running the update zip
Says Error: Status 2
What can I do?

Neither will work without root... follow D2 root instructions.

So follow the instructions on this thread
forum.xda-developers.com/showpost.php?p=7838000&postcount=1
And then just follow the instructions as they are on the new froyo threads
Thanks!!!

Yes, that should work. Wait for someone else to confirm this though, unless you are adventurous.
rage-against-the-cage is a 2.2 exploit, the way I understand. It isn't specific to the D2, but as I said, wait on someone to confirm. I don't know a whole lot about this. More of a lurker than a do-er.

I saw it a while ago and thought about doing it, I was waiting for another 1-click-root type of thing, so I couldn't mess up. I'll wait and see if someone confirms it then.

I used this method to regain root after the 2.3.13 update and it worked. If you know how to use adb its pretty easy.
Sent from my DROIDX using XDA App

citanes-26 said:
I used this method to regain root after the 2.3.13 update and it worked. If you know how to use adb its pretty easy.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Hi I don't really. But I ran into a problem my computer wont recognize my phone in pc mode. I installed and uninstall the drivers and nothing. So I can't do anything!!
Any ideas?

Try and find a guide somewhere? I know there are guides to setting up the sdk.

None of my computers (Mac/Windows 7) would recognize my Droid on PC mode. What can I do??
Thanks

Venc said:
None of my computers (Mac/Windows 7) would recognize my Droid on PC mode. What can I do??
Thanks
Click to expand...
Click to collapse
Try turning usb debugging off (System settings > Applications > Development).
And then connect in PC mode again and see if the phone installs itself.

Try the other modes, mine work in mass storage.
Sent from my DROIDX using XDA App

meshdub said:
Try turning usb debugging off (System settings > Applications > Development).
And then connect in PC mode again and see if the phone installs itself.
Click to expand...
Click to collapse
Thank you! Thank you! X1000
I was in the last step to go back to 2.1 when I saw your reply
EDIT FINAL:
Finally done. It appears to be rooted. Barnacle is working again, so should be rooted
Thank you guys a million for the help had to do it using mass storage mode!

Ok I followed the intructions from where it says update to 2.2 in this thread
/forum.xda-developers.com/showthread.php?t=758907
but when I click on the update zip it aborts because of error in sdcard/update.zip status 2
Any ideas?

Venc said:
Thank you! Thank you! X1000
I was in the last step to go back to 2.1 when I saw your reply
EDIT FINAL:
Finally done. It appears to be rooted. Barnacle is working again, so should be rooted
Thank you guys a million for the help had to do it using mass storage mode!
Click to expand...
Click to collapse
Glad that helped!

Please help! How regain Root w/unlocked phone with a broken microUSB port?

So for the past year I've had a grand ol' time playing with assorted ROMs and now I've run into a problem I can't fix. First, I'm 95% certain the microUSB on the bottom of my N1 is shot. It will still charge the phone, but cannot connect via Windows/ADB/Superboot or anything. I've tried different cables, different computers, different USB ports and different OSs... still cannot get any computer to recognize device. I'm not paying $200 for HTC to fix this (broken USB ports are not covered)... so here's where I stand:
I installed the Clockwork RomManager to try to DL and install ROMs more easily. It didn't work, it was unable to install anything, and it screwed up my original Amon_RA recovery. So then both means of flashing new ROMs were totally dead. Reluctantly, with no other choice (that I knew of) I reverted back to stock recovery and stock FRG83.
With the Stock ROM I lost Root privileges. And with the stock recovery program (the one with blue writing) I am entirely unable to flash ANY of the common rooted ROMs. I renamed a whole bunch (Cyanogen, Enomther, Rodriguez etc.) to the correct update.zip, but the stock recovery image refuses to flash any of them. It always fails on the Verification stage.
So I can't flash a rooted ROM via the stock recovery program, and I can't use ADB/Superboot/Fastboot to root the device via USB. How can I regain root? Are there any rooted ROMs that are certain to work with the stock recovery image program? Any other ways?
Since all my data is backed up with Titanium, I really need Root to get my life back! Thanks for any ideas!

If you're still on FRG83 (and not FRG83D), you may still be able to root on-device using Visionary, but I'm not sure which version of Visionary to counsel you to try.
If your USB port is broken, how are you charging it?
Which HBOOT version do you have? If none of the on-device methods are working, could you try the PASSIMG for FRF91 and roll back? Universal AndRoot and z4root should work on that build. From there if you want to re-upgrade and keep root, you'll need to take the pre-rooted update.zip format for custom recovery rather than the OTA.

Doesn't sound like it's broken... Weird. And you're 100% sure you have the drivers and everything installed on the computer?

Hi cmstlistand thanks for your advice.
I am now on FRG83D. I looked for Visionary in the market but didn't see it there.
The strange thing about the broken USB is that I'm still able to charge through it without any problems. This is why I'm only 95% sure it's broken... seems very odd that the wires for charging would still be making contact while the others wouldn't. (Please see in my OP all the things I've tried to get it to connect to a computer... certainly open to new ideas if I've missed any.)
I just checked and my HBOOT is version 0.35.0017. I'd be willing to "try the PASSIMG for FRF91" as you suggest. Would I just find the stock FRF91 and rename it PASSIMG and hold down volume down while powering on? Does that sound like my best option?
Thanks again!

KAwAtA said:
Doesn't sound like it's broken... Weird. And you're 100% sure you have the drivers and everything installed on the computer?
Click to expand...
Click to collapse
Sadly, no. I'd say I'm 95% certain...
The thing is I've tried to connect on my desktop PC with W7 64-bit, my XP laptop and another PC with Linux (Ubuntu and Kubuntu) all to no avail.
Here's what I've done on my main PC (Win7 64bit) to try and connect the N1 (which, btw, connected just fine a few months ago, albeit to a different W7 install). The problem might still be in here, and not in the hardware, so I'm open to any ideas.
1. Whenever I connect I get the "USB Device not Recognized" alert in the taskbar.Clicking on that alert yields no actionable information.
2. The Device Manager shows the exclamation mark by unidentified USB device. Uninstalling, Disabling and attempting to manually update the driver from within the Device Manager all have no effect. Windows says I already have the most current drivers.
3. Tried the USBDeview program. It's supposed to "show all hidden and previously installed usb drivers on your computer." It shows nothing related to HTC or Nexus or Google.
4. I tried manually installing the USB drivers from here.
5. I installed & uninstalled & reinstalled the Android SDK thinking that might fix the USB issue. It didn't.
6. Tried running W7 in Safe Mode and without firewall/anti-virus.
7. Tried three different cables on all of the USB ports on my PC.
All throughout... it's always "USB Device not Recognized"

There should be some PASSIMG files you can try at Shipped ROMs. Usually it's a ZIP inside of another ZIP, so you have to extract the inner file first and rename it PASSIMG.zip.
Visionary is not on the Market anymore, nor are most other rooting apps. You'll have to search for them on the web. So far I don't know of any apps that root FRG83D on-device.

Install pdanet on your pc, and try again. It's an easy way to update the drivers.
The sdk has changed with the gingerbread release, and you have to reload the drivers, etc...
Sent from my Nexus One using XDA App

danger-rat said:
Install pdanet on your pc, and try again. It's an easy way to update the drivers.
The sdk has changed with the gingerbread release, and you have to reload the drivers, etc...
Click to expand...
Click to collapse
I'd actually tried that before and forgot to mention it. So I just tried it again and no dice. At the point where you plug in your phone, I get the Device Not Recognized immediately in the taskbar. In Device Manager, there is no "Android Devices" category.
cmstlist said:
There should be some PASSIMG files you can try at Shipped ROMs. Usually it's a ZIP inside of another ZIP, so you have to extract the inner file first and rename it PASSIMG.zip.
Visionary is not on the Market anymore, nor are most other rooting apps. You'll have to search for them on the web. So far I don't know of any apps that root FRG83D on-device.
Click to expand...
Click to collapse
I tried the FRF81 from that site and yes it was a zip inside a zip. Renamed it to PASSIMG... but the installation failed at the verification stage.
Thanks for everyone's help so far. I'm totally at a loss with this thing. I don't even know if this is a software or hardware issue. All I know is that I'm dangerously close to driving a railroad spike through the screen.
Any other suggestions greatly appreciated!

JohnHenrySDM said:
I'd actually tried that before and forgot to mention it. So I just tried it again and no dice. At the point where you plug in your phone, I get the Device Not Recognized immediately in the taskbar. In Device Manager, there is no "Android Devices" category.
I tried the FRF81 from that site and yes it was a zip inside a zip. Renamed it to PASSIMG... but the installation failed at the verification stage.
Thanks for everyone's help so far. I'm totally at a loss with this thing. I don't even know if this is a software or hardware issue. All I know is that I'm dangerously close to driving a railroad spike through the screen.
Any other suggestions greatly appreciated!
Click to expand...
Click to collapse
If a passimg isn't working it's possible your on FRG33 or something else that doesn't like them. Just use visionary to root like suggested it's been taken down from the market so you'll have to find it here

Ozymandias88 said:
If a passimg isn't working it's possible your on FRG33 or something else that doesn't like them. Just use visionary to root like suggested it's been taken down from the market so you'll have to find it here
Click to expand...
Click to collapse
Visionary does not work on FRG83D, which is what the OP has. Thus my suggestion to try downgrading.
If you're on the newer HBOOT, try the KT_KR release of FRF91 (rootable with Universal Androot or z4root), or try FRG33 (rootable with Visionary). Both are available as PASSIMG files.

That's correct I have FRG83D so Visionary will not work.
Thanks for the suggestions Cmstlist.
Any advice on where to find the KT_KR release of FRF91? I'm searching as we speak, but not finding much...
EDIT: Never mind, just found it here Link. Downloading it now, I'll report back soon.
Thanks Again.

Ok I just DLd KT_KR release of FRF91, renamed it to PASSIMG, copied to root of SD card, rebooted holding volume down. Phone finds and starts to load PASSIMG but then I get the "Main Version is Older! Update fail!" error.
I'll look for and try the FRG33 PASSIMG next, but I'm pretty certain I'll get the same error.

Ok just tried FRG33 I found HERE.
It didn't work, but it didn't work in a different way.
HBOOT finds PASSIMG.zip and loads it (blue bar at top right). After loading it says (Checking... PASSIMG.zip) Then it stays there for a few seconds, and then just jumps back to the original HBOOT screen. There's no error message.
I guess where I'm confused now is that I currently have the newest version (FRG83D) installed. So won't all other PASSIMG files be older and therefore result in one of the above errors?
EDIT: Just thought of something else. For both of the above files I needed to rename them myself to PASSIMG. They were originally named Passion_Google_WWE_2.16.1700.1_FRG33_MFG_Shipment_ROM.zip and PASSIMG_Passion_KT_KR_2.15.1010.2_FRF91_release_signed.zip. I was correct in needing to rename them, right? Just want to make sure...

Yes you'd be correct to extract and rename them.
Usually the main version error relates to HBOOT and not the OS version itself, which is why I was hoping FRG33 would work for you.
Sent from my Nexus One using XDA App

I see. Thanks for the info.
Still looking for any new ideas to try if anyone has them.

Is there any way I could just revert the phone back to a much earlier build, like ERExx ? Or any way to erase everything, but retain the unlocked state, and then load up a differrent build, one that's software rootable?
Or is it likely that I'm just grasping at straws here?

Rolling back to a much older built requires a modification to the misc partition to trick the HBOOT check... which you can only accomplish either with root, or over USB via fastboot.
Rooting FRG83D requires adb USB over USB. UNLESS... can you adapt the rageagainstthecage instructions to run them by typing or pasting meticulously into Terminal Emulator? Maybe that could root it.
Sent from my Nexus One using XDA App

Hmmm, good idea but I don't think anything involving a terminal emulator is likely to work, at least not with my skill set. I've already tried one other method that relied on terminal, and it failed because I couldn't get SU. Without root, I couldn't get super user permissions, without those, terminal was useless.
I just got off the phone with the insurance company (Asurion). I filed the claim and am now waiting to hear back what my options will be. The guy thought that since the N1 is no longer available, I'd be given a choice between a G2, a Vibrant or a Mytouch (not sure if 3g or4g model). And if I don't want any of those, then I'll just keep my N1.
So, the clock is ticking down! ANY ideas whatsoever are greatly appreciated! I'd much rather keep my N1...

JohnHenrySDM said:
Hmmm, good idea but I don't think anything involving a terminal emulator is likely to work, at least not with my skill set. I've already tried one other method that relied on terminal, and it failed because I couldn't get SU. Without root, I couldn't get super user permissions, without those, terminal was useless.
I just got off the phone with the insurance company (Asurion). I filed the claim and am now waiting to hear back what my options will be. The guy thought that since the N1 is no longer available, I'd be given a choice between a G2, a Vibrant or a Mytouch (not sure if 3g or4g model). And if I don't want any of those, then I'll just keep my N1.
So, the clock is ticking down! ANY ideas whatsoever are greatly appreciated! I'd much rather keep my N1...
Click to expand...
Click to collapse
Oops I pressed thanks instead of quote =)
What I was suggesting is that you try looking at the manual instructions for rageagainstthecage and adapting them to Terminal Emulator. Those instructions don't require you to already have root - they *give* you root. But now that I read them over, it seems there's also some adb start/stop/etc commands that I'm not sure you can replicate in Terminal emulator. Back to the drawing board...
If Asurion is willing to give you an MT4G or G2, I say go for it.
Just on a total whim... try booting up your phone without the SD card, or with a different one... does it still fail to recognize over USB?

cmstlist said:
Just on a total whim... try booting up your phone without the SD card, or with a different one... does it still fail to recognize over USB?
Click to expand...
Click to collapse
Ha ha you had me all excited there... first chance to try something new! Alas, no luck. Used the original SD card and tried again without one; still got the exact same Device Not Recognized.
I talked to another rep and they alluded that the MT4G was not going to be an option, but that the 3G probably would. The3G seems inferior, though.
You think the G2 would be a fair trade? How about the HD2 or the Vibrant? Any others come to mind?
Since I'll need to pay a $130 deductible (not to mention the $5 I've been spending every month for the last year) I want to make very, very certain that my new phone is not inferior to my beloved N1.
Thanks again; you've been very generous with the ideas!

[Q] You Tube on Nexus One not working right

I just got my Nexus about a week ago and I've pretty much figured the phone out by now. However one Issue I have is with the You Tube application.(part of the firmware)
I will get a still image of the video and audio on You Tube at first. Then when I select watch in normal quality the application either stop responding or I get and error message saying the video can't be played.
I was told by the guy who sold me the phone that it used to have Cyanogen installed on it but now it currently has the shipping (stock) ROM installed on it using AmonRA as the bootloader. He got the phone directly from Google when they first came out.
Suggestions ?

Reinstall Youtube app?

I wish I could or knew how. It's part of the firmware. There isn't even an option to get rid of it as it does not show up under the list of installed aps.

Grab the updated version from the Market.

I already tried that and it's not showing me a you tube aplication.

adamsavage said:
I already tried that and it's not showing me a you tube aplication.
Click to expand...
Click to collapse
Is the boot-loader unlocked?
Is the phone rooted?
I'm assuming since you said it has CM7 on it, that the boot-loader is unlocked.
In this case you could try flashing a different ROM that has gapps bundled into it, or just flash over the gapps zip.

The phone is NOT rooted as I ran test using a app called Android Terminal Emulator and typed in "SU" I got back "permission denied" I have no idea if the bootloader is unlocked. For flashing ..Well I've never flashed a phone before so I would have no idea what I was doing or how to do it.

adamsavage said:
The phone is NOT rooted as I ran test using a app called Android Terminal Emulator and typed in "SU" I got back "permission denied" I have no idea if the bootloader is unlocked. For flashing ..Well I've never flashed a phone before so I would have no idea what I was doing or how to do it.
Click to expand...
Click to collapse
Try the attachment I uploaded, its the new YouTube app. Took it straight from my phone.
Just copy to SD card, and use a file manager to install it.

Using astro file manager and when I select open with app manager it says it cannot open the file you uploaded for me. I tried a different file manager and this one said it had problem parsing the file.

Hmmm. Sounds like some type of data loss when downloading the file. Try redownloading again. I just download it and it worked fine for me. Also, could try downloading it through the xda app on the market. Its what I just did and it worked fine.
Sent from my Nexus One using XDA App

Download directly from the site on the app and it still says problem parsing the package. I don't have a rooted phone and its using stock firmware.
Sent from my Nexus One using XDA App

adamsavage said:
Download directly from the site on the app and it still says problem parsing the package. I don't have a rooted phone and its using stock firmware.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Ok try this since you can't find it on the market on the device.
https://market.android.com/details?id=com.google.android.youtube
Also are you running 2.1 or 2.2?

I'm using 2.1 and I've checked for updates by going to settings-about phone-System updates. I can't get the newer 2.2 version as far as I know. I could always root the phone. I've googled on how to do it and it looks pretty straight forward.
For my firmware:
I have basebrand version: 32.36.00.28u_4.06.00.12_7
Kernel Version 2.6.29: gad36b87 [email protected]#1
Build Number: ERD79

Upgrade to the latest 2.2.2 stock or custom ROM. It'll bring you tons of benefits besides making Youtube work.

Do this:
1)Read the wiki in Jack_R1's signature.
2)Do a nandroid backup from recovery (amon_ra).
3)Go here http://forum.xda-developers.com/showthread.php?t=927935. Download the first file "Stock, with no modifications but root". Move it to your SDcard. (This is the latest stock ROM (FRG83G / 2.2.2) with root access. It is unmodified except allowing for root access.)
4)Flash it through recovery

tech338 said:
Do this:
1)Read the wiki in Jack_R1's signature.
2)Do a nandroid backup from recovery (amon_ra).
3)Go here http://forum.xda-developers.com/showthread.php?t=927935. Download the first file "Stock, with no modifications but root". Move it to your SDcard. (This is the latest stock ROM (FRG83G / 2.2.2) with root access. It is unmodified except allowing for root access.)
4)Flash it through recovery
Click to expand...
Click to collapse
I don't think he even has a custom recovery.
So with assuming he does not.
Follow this link and use the guide there to upgrade to froyo.
http://android.modaco.com/content/g...es-zip-online-kitchen-optional-root-insecure/

McFroger3 said:
I don't think he even has a custom recovery.
Click to expand...
Click to collapse
In reading his first post, he mentions having AmonRa as the bootloader... If he does have that, then fixing the issue by flashing a new ROM should be pretty straight forword.
adamsavage said:
I was told by the guy who sold me the phone that it used to have Cyanogen installed on it but now it currently has the shipping (stock) ROM installed on it using AmonRA as the bootloader. He got the phone directly from Google when they first came out.
Click to expand...
Click to collapse

Ok so I read the guide and it seems to be straight forward. Gonna read over it a couple more time tomorrow to make sure it's sinking in.

I'm stuck in the guild at stage 2.."Setup SDK"..The guide does no tell you that you need this special version of Java to open the program.. I have both SDK and the java setup on the computer. However where I'm stuck is simply getting windows to install usb drivers for the phone. I went to update drivers and told it to look in the folder SDK was installed and it refused by saying there was no drivers for the phone in there. When I set up the SDK program there is no option for "usb drivers" for me to even install..

adamsavage said:
I'm stuck in the guild at stage 2.."Setup SDK"..The guide does no tell you that you need this special version of Java to open the program.. I have both SDK and the java setup on the computer. However where I'm stuck is simply getting windows to install usb drivers for the phone. I went to update drivers and told it to look in the folder SDK was installed and it refused by saying there was no drivers for the phone in there. When I set up the SDK program there is no option for "usb drivers" for me to even install..
Click to expand...
Click to collapse
Try this.
10 characters.

[Q] How to root Build # FRG83G 2.2.2

Hi, Can any kind soul poin tme in the right direction on How to root Build # FRG83G 2.2.2?
Superoneclick does not work and it does not look like anything is out there for superboot on build FRG83G.
I have ditched my Vibrant and returned to my N1. Bought it off of ebay and the boot loader remains intact.
Thanks again.
Larry

If SuperOne click doesn't work - it means you didn't do something right.
Read the Wiki, read the SOC guides, and try again - until you understand what you're doing, and it'll succeed.

Thanks for the reply. Maybe I should have been more clear. Superoneclick is not compatable with the 2.2.2 build.

Maybe I should have been more clear. It IS compatible:
http://forum.xda-developers.com/showpost.php?p=10570981
It was asked not once and not twice, and not even 10 times here. MUCH more. Multiple people rooted 2.2.2 builds with it.

It worked for me.
An error message would really help us help you... Or you could do the manual rage-against-the-cage method.

oklahomatulsa said:
Hi, Can any kind soul poin tme in the right direction on How to root Build # FRG83G 2.2.2?
Superoneclick does not work and it does not look like anything is out there for superboot on build FRG83G.
I have ditched my Vibrant and returned to my N1. Bought it off of ebay and the boot loader remains intact.
Thanks again.
Larry
Click to expand...
Click to collapse
SOC will work but you need to have your device recognised by the PC you are using. Is there a chance that the drivers for your N1 aren't installed properly? This is one reason why SOC rooting can fail.
Providing that you are on Windows, this can be checked by opening 'Device Manager'.

Confused
..Well... I went to a forum last night and saw that superone click ..hell, maybe it was oneclick root was not compatible. Obviously I was wrong. I originally rooted my first N1 the first week of January 2010.
SO I went to the unlockr and followed theor old method. Unforutnately the the "superboot that I attempted to unroot the phone with was for Build FRG83 and not "FRG83G". So the phone shows that the bootloader is unlocked( once it boots up) but according to "root checker and and trackball/powerbutton hold) that is not the case.
Also the superone click shows that it is waiting for my device. I have tried this on Laptop(win7) and desktop (XP)
Thanks

Manual root guide...
http://www.nexusoneforum.net/forum/...mple-sdk-setup-manual-root-guide-windows.html
Sent from my Nexus One using XDA App

oklahomatulsa said:
..Well... I went to a forum last night and saw that superone click ..hell, maybe it was oneclick root was not compatible. Obviously I was wrong. I originally rooted my first N1 the first week of January 2010.
SO I went to the unlockr and followed theor old method. Unforutnately the the "superboot that I attempted to unroot the phone with was for Build FRG83 and not "FRG83G". So the phone shows that the bootloader is unlocked( once it boots up) but according to "root checker and and trackball/powerbutton hold) that is not the case.
Also the superone click shows that it is waiting for my device. I have tried this on Laptop(win7) and desktop (XP)
Thanks
Click to expand...
Click to collapse
I think you are confusing a couple of things.
First of all, if, when you power-up your device, you see the padlock on the splash screen, your bootloader is unlocked. If that is the case, use fastboot to flash a custom recovery (i.e., download the recovery you want to the directory where the fastboot executable is and connect your phone and type fastboot flash recovery insert-name-of-recovery-here.img then you can flash ChainsDD superuser file found here: http://forum.xda-developers.com/showthread.php?t=682828 from recovery.

Android 6.0 Root..?

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.