Database Develop

.901 root possible?

I got the Bionic on Tuesday and one of the first things it asked me to do was an ota update. 893. I tried rooting at that point and couldn't. I just proceeded to upgrade to. 901. Now i ask can i still root or do i need to roll back first? Is it even possible?
Sent from my DROID BIONIC using xda premium

Anyone apply Full 5.5.893 FXZ and lost root? Yeah, me too!
Here is a Root Method for the Offical 5.5.893.
This has been crafted to carry over Root to 5.9.901 (tested stock rooted 55893 to 59901 via update).
1) Unzip contents of h t t p://dl.dropbox.co...236/ROTA893.ZIP
2) Inside ROTA893 directory is runmebbb.bat
3) Close yours eyes and take a nap.
4) Wake UP!
Easy rooting toolkit (v3.0bbb)
created by DooMLoRD
BioniCfied (silent C Mod) by realBBB for 5.5.893
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) roots 5.5.893 Bionic by oldschool zergRush (17 Oct)
(2) installs Busybox (1.19.0)
(3) installs SU files (binary: 3.0.3.2 and apk: 3.0.7)
(4) installs Minimal 43V3R Root by BBB
(5) Allows root carry through to 5.9.901
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
Happy New Years!
BBB
Running with Clogs.

the download link is broke i cant click on it plz edit or post a mirror

h t t p://dl.dropbox.com/u/54323236/ROTA893.ZIP
BBB
E=MC^2 is A=(PI)R^2 aka Energy is Two Dimensional.

So do i need to go back, get the root, and then go to 901 again?
Sent from my DROID BIONIC using xda premium

Yes...that is the only way until a new exploit is developed for .901 and later versions.

I attempted running this root exploit before upgrading to .901 but I still lost root after the upgrade. What's a guy to do?

rjp0615 said:
I attempted running this root exploit before upgrading to .901 but I still lost root after the upgrade. What's a guy to do?
Click to expand...
Click to collapse
use the bionic path saver it will roll you back 886 root you and push 893 and 901 to your phone. you do not have to install 901. after you flash 893 root and forever root the make sure forever root keeps after a reboot. using root explorer go to system/bin/mount.ext.sh or something like that and make sure you have 3 lines at the bottom that start with chmod 4755. if they are there then install 901

I've also tried the path saver, and after installing 901 I still lose root. I also tried installing 893, rebooting, noticing that I kept root, and then after running the 901 update I lost root again.
Edit: GOT IT! I used the pathsaver to restore to 893 and then I used ROTA893 to root and the r3l3as3d tool to forever root. now I'm on rooted 901! Thanks guys

rjp0615 said:
I've also tried the path saver, and after installing 901 I still lose root. I also tried installing 893, rebooting, noticing that I kept root, and then after running the 901 update I lost root again.
Edit: GOT IT! I used the pathsaver to restore to 893 and then I used ROTA893 to root and the r3l3as3d tool to forever root. now I'm on rooted 901! Thanks guys
Click to expand...
Click to collapse
r3leased not needed if you used rota893. It has a streamlined 43v3r already included.
pathsave then rota893.. good to go to 901 with root.
BBB
Still Thinking of All of It.

I am on 5.9.901 and still have root.
Pretty stable. It was hell trying to get on to 5.9.901 as I hosed the boot, hosed all sort of stuff. Took 30 hours worth of muck and many helps from XDA and other site to get it going. But managed to get back on to 5.9.901 and rooted.
Worth every hours spent!

I forever rooted while on 5.893 just flashed .901 update now I no longer have root access
do I have to go through this whole process again?

ROB281 said:
I forever rooted while on 5.893 just flashed .901 update now I no longer have root access
do I have to go through this whole process again?
Click to expand...
Click to collapse
did you make sure that foreverroot stayed after a reboot?

neckbonest said:
did you make sure that foreverroot stayed after a reboot?
Click to expand...
Click to collapse
Yes, actually ran 5.893 rooted for over a week with several reboots
Sent from my DROID BIONIC using xda premium

thats odd. i went from 893 to 901 back to 886 to 893 and now back on 901 and never lost root.

smilepak said:
I am on 5.9.901 and still have root.
Pretty stable. It was hell trying to get on to 5.9.901 as I hosed the boot, hosed all sort of stuff. Took 30 hours worth of muck and many helps from XDA and other site to get it going. But managed to get back on to 5.9.901 and rooted.
Worth every hours spent!
Click to expand...
Click to collapse
I also had a hell of a fiasco when I tried to upgrade liberty rom to .901. Took me half a day at work to get my phone back up and working again. I'm at .901 stock unrooted and I think I'll stay here for a while. Gun shy at this point.

deitiphobia said:
I also had a hell of a fiasco when I tried to upgrade liberty rom to .901. Took me half a day at work to get my phone back up and working again. I'm at .901 stock unrooted and I think I'll stay here for a while. Gun shy at this point.
Click to expand...
Click to collapse
I am running 901 unrooted temporarily as well until a new exploit is available. The path saver did root the previous build for me but the second I pushed the 901 update root was lost.

CAn this exploit be run on a MAC?

cb7tuner93 said:
CAn this exploit be run on a MAC?
Click to expand...
Click to collapse
By exploit are you referring to the path saver? I am not very familiar with Macs and what files they are able to run but if I had to wager a guess I would say no. Perhaps via bootcamp though.

This may sound dumb and noobish but I have an idea I would like to put out there. Is it possible to look at the code from Motorola's update files and copy said signature into the superuser file? This, in theory, would fool the phones factory recovery into installing the file and thus rooting the device.
Just brainstorming here

5.9.905 - Just got prompted to Download and Install

I was on stock, rooted 5.9.902 and was just prompted to Download and Install 5.9.905 OTA. I backed up root with Voodoo OTA Root Keeper, temp unrooted, downloaded and installed 5.9.905, let the phone reboot, then restored root using Voodoo OTA Root Keeper. All went smooth and am now on the official OTA with root. I noticed the addition of Google+ as a preinstalled app. I am assuming, however, that there is no difference between the 5.9.905 that was pulled from Motorola's servers a few weeks back.

Thanks I was wondering what I should do about the root. Went back to unsafe mode, unrooted with backup thanks to rootkeeper, and now I'm waiting for the update! Cheers.

You will need to remove safestrap and may even have to FXZ or fastboot your preinstall partition before the OTA will succeed.

that's what i was afraid of... can i just download the update and do it myself with safestrap installed? I'm not the complete expert so step by step instructions would be appreciated.

I will wait for the OTA notice. if I have to reroot and reeinstall Safestrap I will.

cellzealot said:
You will need to remove safestrap and may even have to FXZ or fastboot your preinstall partition before the OTA will succeed.
Click to expand...
Click to collapse
OHbenhamean said:
that's what i was afraid of... can i just download the update and do it myself with safestrap installed? I'm not the complete expert so step by step instructions would be appreciated.
Click to expand...
Click to collapse
You don't have to remove Safestrap, or un-root as long as you haven't removed any bloatware apps. They can be frozen in TB and it will install. You will lose root, I used Motofail to re-root, then you will have to rerun the install for safestrap recovery. 15 minutes and your good to go.

Agreed. I just removed safe strap, didn't bother to unroot. Tried to force the update repeatedly with no luck. So i took it from the Phandroid news link. Flashed in stock recovery. Kept root (used for3ver root to root I months and months ago). Reinstalled safe strap, then switched back to my safe side which was DroidTheory's ICS, but now with a better radio now. Radio synced immediately...whereas normally it takes a minute or two. Loving this update.
--Sent from GlaDos baked potato

hey just fyi if you flashed it back to 902 stock and took the update you can use the 902 one click root to reroot, i just tried it

Still rooted
I just let the 5.9.905 ota run this morning on my rooted Bionic. No unroot, no backup, or nuthin. I know, not the wisest thing to do but hey, I was caffeine deficient and spoiling for a fight Anyway after the reboot:
Root check shows it's still rooted.
Opened a shell on the handset with Terminal Explorer and successfully su.
Opened an adb shell and successfully su.
I haven't had a chance to explore what's changed yet, but I did notice that Google+ is no longer un-installable.
I might be the exception, but it appears that the ota doesn't affect root on a previously rooted handset. All seems good in my little piece of the world.

Every time I try to update, it says I need a valid Motorola account. I'm on stock, but have done many customizations to it, along with the webtop. I know how to get back to plain stock, just haven't felt like doing it yet. I suppose at some point I will have to when we finally get ICS.
the funny part is that I never had any issues with my data connection until 905 came around, but I have been having them for the past 2 weeks or so.
Sent from my DROID BIONIC using XDA

Non-rooted Bionic constantly trying to download 5.9.905
The past few days my Bionic has been constantly trying to download an update. I came online to investigate the reason and found that 5.9.905 just got released. The download symbol has been in the notification bar all day for the last few days and the battery is always dead when I wake up.
I have looked online to try to update manually but all the filenames of the 5.9.905 download links are actually labeled Blur_Version.5.9.902.XT875.Verizon.en.US.zip. Link this one here at xda: http://forum.xda-developers.com/showthread.php?t=1297714&page=40. Anyone have any suggestions? Thanks.

The filename is in regards to the version over which it can install.
You just have to download one from may or later, I believe. Pick a page that says it's the 905 update, download the zip file with 902 in the name, put it on your external sd card, and reboot into stock recovery (I use adb reboot recovery), press both volume buttons in, then "install zip from sdcard" use power button to select. go down to the zip file we just put on the sdcard, hit the power button and BING BANG BOOM 905!

Re: Non-rooted Bionic constantly trying to download 5.9.905
Thanks, 5thAgent. I'll give it a try.

[Q] USB Port Dead / How to Unroot?

The micro USB charging port on my wife's D4 just died. I received the warranty replacement from VZW. I need to return the old D4 to stock.
Battery is dead and can't charge via USB. I bought the D4 inductive charge door from VZW, and will buy a powermat to charge it, so charging it should not be a problem.
I did a search on this, and found various threads for dead USB ports, but not a solution for what I need.
QUESTION: How can I unroot, return to stock ROM and recovery, and re-lock the bootloader without USB access? I know there are various apps I can use to transfer files to the device via wifi, but is there a ZIP file I can flash with Clockworkmod Recovery to re-load stock ROM, unroot, re-lock bootloader, and re-load stock recovery?

SoCalNewb said:
The micro USB charging port on my wife's D4 just died. I received the warranty replacement from VZW. I need to return the old D4 to stock.
Battery is dead and can't charge via USB. I bought the D4 inductive charge door from VZW, and will buy a powermat to charge it, so charging it should not be a problem.
I did a search on this, and found various threads for dead USB ports, but not a solution for what I need.
QUESTION: How can I unroot, return to stock ROM and recovery, and re-lock the bootloader without USB access? I know there are various apps I can use to transfer files to the device via wifi, but is there a ZIP file I can flash with Clockworkmod Recovery to re-load stock ROM, unroot, re-lock bootloader, and re-load stock recovery?
Click to expand...
Click to collapse
Assuming you are successful in getting your D4 charged, following these steps SHOULD get you back to a stock unrooted phone without the use of the USB port. Make sure you have backup up anything you don't want to lose before you do this.
1. Go in to safestrap recovery, delete any ROM slots, and boot back into your stock ROM.
2. Open up the safestrap app and select uninstall recovery.
3. Uninstall the safestrap app.
4. While you are still rooted, use a file explorer and delete any incriminating leftover files (nandroid backups, etc.)
5. Install and run Ginger Unroot from the Play Store (Full disclosure: I have never actually used this app). Costs 99 cents.
6. After Ginger Unroot does it's thing, check to make sure Superuser is not longer installed on the phone.
7. Boot in to stock recovery and perform a factory reset.
Honestly, I would probably just skip step 6 and manually delete superuser. It's pretty unlikely they will really be looking to see if you rooted it since you're returning it for a hardware issue. Also, according to another thread on XDA, rooting the D4 triggers some sort of check that cannot be undone. If true, unrooting your phone won't help.
Good luck!

kwyrt said:
It's pretty unlikely they will really be looking to see if you rooted it since you're returning it for a hardware issue.
Good luck!
Click to expand...
Click to collapse
Do you really think so? As since ics I have not rooted my for as I have bad luck with the ear piece speaker in my past d4...
Sent from my DROID4 using xda app-developers app

dbreezy187 said:
Do you really think so? As since ics I have not rooted my for as I have bad luck with the ear piece speaker in my past d4...
Sent from my DROID4 using xda app-developers app
Click to expand...
Click to collapse
Just my personal opinion so take it for what it's worth. I've never actually had to return a phone myself. But, I have yet to hear of someone being turned down for a warranty repair/return because their phone was rooted. And I do know someone personally that returned their D4 under warranty for a faulty screen that was rooted and running a custom ROM and they never said a thing. I'm guessing the only reason they would look into it being rooted was if you soft bricked it, wouldn't boot, something like that where they suspect it was something you did to cause it.
Sent from my D4 - AOKP

kwyrt said:
Assuming you are successful in getting your D4 charged, following these steps SHOULD get you back to a stock unrooted phone without the use of the USB port. Make sure you have backup up anything you don't want to lose before you do this.
1. Go in to safestrap recovery, delete any ROM slots, and boot back into your stock ROM.
2. Open up the safestrap app and select uninstall recovery.
3. Uninstall the safestrap app.
4. While you are still rooted, use a file explorer and delete any incriminating leftover files (nandroid backups, etc.)
5. Install and run Ginger Unroot from the Play Store (Full disclosure: I have never actually used this app). Costs 99 cents.
6. After Ginger Unroot does it's thing, check to make sure Superuser is not longer installed on the phone.
7. Boot in to stock recovery and perform a factory reset.
Honestly, I would probably just skip step 6 and manually delete superuser. It's pretty unlikely they will really be looking to see if you rooted it since you're returning it for a hardware issue. Also, according to another thread on XDA, rooting the D4 triggers some sort of check that cannot be undone. If true, unrooting your phone won't help.
Good luck!
Click to expand...
Click to collapse
kwyrt - THANK YOU for your help! I am heading out later today to get a charging mat to use with the inductive charger, then I will try the steps you outlined above.:laugh:

Yes thank you putting it that way I may finally get mine rooted again...
Sent from my DROID4 using xda app-developers app

Update: I have not been able to test the above directions yet because no local stores seem to carry the inductive charging mat (I've tried Verizon Wireless, Sprint, Radio Shack, and Best Buy).
I will buy the charging mat online, then update thread with outcome once it arrives.

Update 2: the PowerMat that I ordered on Amazon arrived today. Unfortunately it is not compatible with the Droid 4 inductive charging case (Droid 4 requires QI, PowerMat is not QI).
I ordered a QI charging mat, and it arrives Monday. I'll report progress then.

kwyrt said:
Assuming you are successful in getting your D4 charged, following these steps SHOULD get you back to a stock unrooted phone without the use of the USB port. Make sure you have backup up anything you don't want to lose before you do this.
1. Go in to safestrap recovery, delete any ROM slots, and boot back into your stock ROM.
2. Open up the safestrap app and select uninstall recovery.
3. Uninstall the safestrap app.
4. While you are still rooted, use a file explorer and delete any incriminating leftover files (nandroid backups, etc.)
5. Install and run Ginger Unroot from the Play Store (Full disclosure: I have never actually used this app). Costs 99 cents.
6. After Ginger Unroot does it's thing, check to make sure Superuser is not longer installed on the phone.
7. Boot in to stock recovery and perform a factory reset.
Honestly, I would probably just skip step 6 and manually delete superuser. It's pretty unlikely they will really be looking to see if you rooted it since you're returning it for a hardware issue. Also, according to another thread on XDA, rooting the D4 triggers some sort of check that cannot be undone. If true, unrooting your phone won't help.
Good luck!
Click to expand...
Click to collapse
So the inductive charger arrived last Monday. It worked! Device is all charged up despite the non-functional USB port.
Rooted device when it was on GB, then the OTA update brought it to ICS (which removed root).
Here's where I'm at:
- no root (but superuser still installed, and can't be removed)
- stock recovery
- broken USB port
Here's what I've tried:
- Ginger Unroot did not work
- Can't remove superuser from Google Play
- Can't remove superuser from settings/apps
- Can't remove superuser with Root Explorer (no longer have root, so I can't acquire root privileges)
- Can't remove superuser with Titanium Backup (no longer have root, so I can't acquire root privileges)
Given lack of USB, and lack of root, any ideas how I can remove Superuser and restore to stock?

SoCalNewb said:
So the inductive charger arrived last Monday. It worked! Device is all charged up despite the non-functional USB port.
Rooted device when it was on GB, then the OTA update brought it to ICS (which removed root).
Here's where I'm at:
- no root (but superuser still installed, and can't be removed)
- stock recovery
- broken USB port
Here's what I've tried:
- Ginger Unroot did not work
- Can't remove superuser from Google Play
- Can't remove superuser from settings/apps
- Can't remove superuser with Root Explorer (no longer have root, so I can't acquire root privileges)
- Can't remove superuser with Titanium Backup (no longer have root, so I can't acquire root privileges)
Given lack of USB, and lack of root, any ideas how I can remove Superuser and restore to stock?
Click to expand...
Click to collapse
Like previously stated, its prolly going to get tossed into a refurb bin where it will under go fresh flash of firmware after some little asian will replace the speaker and usb port. I wouldnt stress it.

wheeliest said:
Like previously stated, its prolly going to get tossed into a refurb bin where it will under go fresh flash of firmware after some little asian will replace the speaker and usb port. I wouldnt stress it.
Click to expand...
Click to collapse
Gotcha. I just want to avoid getting charged the $300 because they see it was rooted. Would be lame since the device's mechanical USB port failure was completely unrelated to the device being rooted.
Has anyone returned a device to VZW that is still rooted? Did they charge you the $299?

I need help please
PLEASE...... I FLASHED MY LG-E739 wit MIUI V4 rom,
Den i decided to run a font.....when i reboot for de font to take effect it refuse to boot..stopped at de miui logo and have
tried everything to gain recovery mode but none seems to be working...
Please if anybody can render help to me i'd be very greatful.

[Trifecta] Jelly Bean Update

This one is pretty straight forward...Especially if you haven't done much modding to your
phone.
If you're stock or close to, you can probably just move the update to the phone sd and use stock recovery to apply update, and you're good to go. If you are already rooted try the OTA RootKeeper app, hopefully it'll work for you. being that it seems to be hit & miss, i'm guessing it didn't work for people that had issues updating, but will work for those whose update goes smooth.
I on the other hand had already rooted and did the GSM hack on mine so I ran into a few issues that I've others have been having too.
Probably the biggest and most common are "system 7" errors. I've realized you get these when the update checks and finds that ICS files have changed, are frozen, gone, etc. and it's a bit harder to diagnose because it keeps changing depending on what's wrong.
For example it had a code then something else and it referrenced my STK.apk file, then I realized when I did the GSM hack I renamed those to Stk.apk.bak & stk.odex.bak as recommended. So I fixed those & tried update again.
Failed this time at build.prop, yep another GSM mod, but I didn't back-up or save orig settings, so I had to find a bionic ICS build.prop and replace it. found it here (will update with link asap).
Tried again, IIRC, this is the time it worked, but only booted to animation loop. This sucked. Tried to use House of Bionic to fix, couldn't get it to work, but ended finding a fix using recovory "AP Fastboot" had to use pc CMD to reinstall preinstall.img & system.img from the HoB ICS FXZ file.
Look HERE. Thanks to ERIC for this, he gives you everything you need. He's also responsible for dead battery workaround I put below.
When you do this, you can't boot phone back up but you can go into stock recovery & re-apply update from sd on your phone. It wipes everything tho, so if you used OTA RootKeeper, it's gone. But you get phone back.
Bottom line...MAKE BACK-ups or save everything you've changed.
If you've heavily modded things on your phone it might be more worth it (easier) to back up & save what you can as far as apps & personal stuff then redo ICS stock, Maybe root & use OTA RootKeeper here, tho I've heard this doesn't always work either (the OTA part), then apply JB update. then re-install / apply what you were able to save / back-up.
So in hindsight I would guess modding anything within the system is what gives you the "system 7" error, and depending on what you did, or maybe someone you bought the phone from already rooted & modded, it can take you all day to fix / replace those files, just do the reflash of the (2) img files & call it a day. This way you can probably avoid the boot loop issue too.
One other thing about the boot loop one...if you wait & wait & wait like I did it KILLS your battery, and you won't be able to use Fastboot.
IF THIS HAPPENS...find an old phone charger or DC plug, like for your computer, clip off the end and line up the positive & negative connections on the battery then push it into the phone so the wires are touching the phone connections too. Be careful what it's putting out tho, I found I had one that the output was 6 (watts i believe) and 300 mah. It worked the trick just fine. you don't want anything to high as you don't want to burn up any circuits. most USB plug phone chargers go around 5 (watts) I believe. just FYI.
Hope this helps someone.
Cheers.

[Q] Update witout PC

Hello,
Maybe this has already been answered, but does anyone know if it's possible to flash an updated radio.img, system.img, bootoader.img and boot.img? I'm a bit of a noob, and I want to upgrade my Nexus 6 to 5.1 once the factory images are released (and the modified boot.img to remove encryption). However, I'd like to do this without the use of a computer. I would use the Nexus Root Toolkit, but for some reason my PC no longer recognizes my device (even though I've tried EVERYTHING to fix, including different cables, ports, drivers, restarts etc.). Maybe the 5.1 update will fix, but I think I have a faulty micro usb port on the device.
I don't want to wipe my data or lose root, which is why I would only update the above images. I thought it could be done through Flashify, but the dev said I'd have to flash an entire .zip through TRWP, but I need the files along with the correct commands. I would lose root, but would use the Towelroot apk to get it back.
Please let me know if this is correct or if I'm missing something. Or if there is an easier way (like maybe Nexus Update Checker).
Thanks

ryan4a said:
Hello,
Maybe this has already been answered, but does anyone know if it's possible to flash an updated radio.img, system.img, bootoader.img and boot.img? I'm a bit of a noob, and I want to upgrade my Nexus 6 to 5.1 once the factory images are released (and the modified boot.img to remove encryption). However, I'd like to do this without the use of a computer. I would use the Nexus Root Toolkit, but for some reason my PC no longer recognizes my device (even though I've tried EVERYTHING to fix, including different cables, ports, drivers, restarts etc.). Maybe the 5.1 update will fix, but I think I have a faulty micro usb port on the device.
I don't want to wipe my data or lose root, which is why I would only update the above images. I thought it could be done through Flashify, but the dev said I'd have to flash an entire .zip through TRWP, but I need the files along with the correct commands. I would lose root, but would use the Towelroot apk to get it back.
Please let me know if this is correct or if I'm missing something. Or if there is an easier way (like maybe Nexus Update Checker).
Thanks
Click to expand...
Click to collapse
first off, towelroot doesnt work in android 5.0+. 2ndly, if you are planning on flashing the official 5.1, you need a computer. if you are planning on updating a custom rom, and you have twrp recovery, download the rom and flash it via twrp.

simms22 said:
first off, towelroot doesnt work in android 5.0+. 2ndly, if you are planning on flashing the official 5.1, you need a computer. if you are planning on updating a custom rom, and you have twrp recovery, download the rom and flash it via twrp.
Click to expand...
Click to collapse
Thanks. I don't have a custom ROM. So I guess I'll wait for one to get updated, then install it. Like I said, using a computer is not an option

ryan4a said:
Thanks. I don't have a custom ROM. So I guess I'll wait for one to get updated, then install it. Like I said, using a computer is not an option
Click to expand...
Click to collapse
thats the easiest way. i dont own a computer nor laptop, so i try to do everything from the phone. but its easier to update via recovery anyways. one thing though, since you are on the stock rom, you will have to wipe your data before flashing a custom rom, since the majority are aosp based, and wont flash over stock.

Before you give up, try a different computer (preferably running Linux), or booting the one you have on a livecd/usb.
If the USB plug on the phone is, in fact, broken, try calling motorola. The phone is still under warranty....

doitright said:
Before you give up, try a different computer (preferably running Linux), or booting the one you have on a livecd/usb.
If the USB plug on the phone is, in fact, broken, try calling motorola. The phone is still under warranty....
Click to expand...
Click to collapse
Thanks. I've tried on multiple computers (PC & Mac, but not Linux). Nothing works. I originally thought it was one of the modifications I made to the device, like root, unlock, custom boot.img, custom recovery, modified build.prop, etc. The more I search, the more I think it's hardware. I'd like to not have to warranty it because I'd have to wipe everything, restore to factory settings, unroot, etc. It's just a big hassle. Plus I'd be without a phone until the replacement arrives. I may end up just living with staying on lollipop 5.0.1 forever. It's just super frustrating.

ryan4a said:
Thanks. I've tried on multiple computers (PC & Mac, but not Linux). Nothing works. I originally thought it was one of the modifications I made to the device, like root, unlock, custom boot.img, custom recovery, modified build.prop, etc. The more I search, the more I think it's hardware. I'd like to not have to warranty it because I'd have to wipe everything, restore to factory settings, unroot, etc. It's just a big hassle. Plus I'd be without a phone until the replacement arrives. I may end up just living with staying on lollipop 5.0.1 forever. It's just super frustrating.
Click to expand...
Click to collapse
update your nexus 6 driver, or install the adb driver. your computer cant see your phone until it has one of the drivers installed. if you had it installed, uninstall it and reinstall.

simms22 said:
update your nexus 6 driver, or install the adb driver. your computer cant see your phone until it has one of the drivers installed. if you had it installed, uninstall it and reinstall.
Click to expand...
Click to collapse
For a driver, it isn't a question of seeing it. Its a question of knowing how to talk to it. Further, one of the reasons I suggest he use something that runs linux, is because it avoids this whole driver problem altogether. The other reason is that it is actually consistent, and trivial to determine whether the devices itself actually made a connection, i.e. "dmesg -w", plug it, and see if it says anything.

simms22 said:
update your nexus 6 driver, or install the adb driver. your computer cant see your phone until it has one of the drivers installed. if you had it installed, uninstall it and reinstall.
Click to expand...
Click to collapse
I've deleted and reinstalled the google driver, and installed the ADB driver. No dice. I'm telling you...I've tried everything. That's why I think it's hardware, however unlikely.

ryan4a said:
I've deleted and reinstalled the google driver, and installed the ADB driver. No dice. I'm telling you...I've tried everything. That's why I think it's hardware, however unlikely.
Click to expand...
Click to collapse
when getting adb to work, thats the #1 issue, installing and getting the driver to work. so, i can tell you, many people dont get the driver working without help in manually installing it. it seems those with older windows have less issues then those with newer windows. i really doubt that its a hardware issue.

simms22 said:
when getting adb to work, thats the #1 issue, installing and getting the driver to work. so, i can tell you, many people dont get the driver working without help in manually installing it. it seems those with older windows have less issues then those with newer windows. i really doubt that its a hardware issue.
Click to expand...
Click to collapse
Man I hope you're right. But my PC doesn't even recognize my device. Like it's not even showing up in the device manager. At best, I can sometimes get the PC to recognize it as an "unknown device". When I try to automatically update the driver, it says complete. But nothing changes. What do I do at that point? I haven't been successful in manually updating the driver.

As a matter of fact, I thought my new Turbo charger was broken because it stopped charging my phone. But when I unchecked USB debugging AND unchecked the MTP connection, the charger started working again. Very strange!

ryan4a said:
Man I hope you're right. But my PC doesn't even recognize my device. Like it's not even showing up in the device manager. At best, I can sometimes get the PC to recognize it as an "unknown device". When I try to automatically update the driver, it says complete. But nothing changes. What do I do at that point? I haven't been successful in manually updating the driver.
Click to expand...
Click to collapse
i wouldnt be able to help you there, as i dont own a computer. but there are many that can help out. maybe someone else will see this thread..

ryan4a said:
As a matter of fact, I thought my new Turbo charger was broken because it stopped charging my phone. But when I unchecked USB debugging AND unchecked the MTP connection, the charger started working again. Very strange!
Click to expand...
Click to collapse
Like I said, TRY LINUX.
No drivers required. Everything is built into the kernel.
Fedora even has an "android-tools" package that includes adb. You just install it with "yum install android-tools" -- even on the livecd (it will install to ramdisk).
Quit screwing around with wondoze and TRY IT.

Linux is a mega pita. Nothing is intuitive or easy. All these commands that have to be typed in, yuk. Give me good ol' Windows any day. Lol.
To the OP. Are you on windows 8.1? Have you disabled 'driver signature verification'?

killall said:
Linux is a mega pita. Nothing is intuitive or easy. All these commands that have to be typed in, yuk. Give me good ol' Windows any day. Lol.
To the OP. Are you on windows 8.1? Have you disabled 'driver signature verification'?
Click to expand...
Click to collapse
I'm using Windows 7. Don't think I'll be using Linux either. I'm running out of options for upgrading android versions without a PC. I'm highly considering installing CM12. I'd rather not because it's seems unnecessary on a Nexus device, but don't know what else to do.

There is also about a 5 second delay from the time I plug my device into any charger, to when it actually begins charging. I'm thinking these two issues are related, which leads to believe it's hardware.

Definitely sounding more and more like hardware

ryan4a said:
There is also about a 5 second delay from the time I plug my device into any charger, to when it actually begins charging. I'm thinking these two issues are related, which leads to believe it's hardware.
Click to expand...
Click to collapse
I have the same delay when plugging in a charger. But my PC recognizes my N6 without any problems.

On my Droid Maxx I had driver issues. I asked on XDA and got it figured out. I can't check now but have a look at my posts and you may find your answer.
Back to V-Day.