Related
I've bought my son and daughter a nexus 7 each for Christmas.
His upgraded over the air fine, hers downloaded the firmware, rebooted and the installation started.
After a couple of minutes the Android fell over with a red exclamation mark.
I've tried forcing the upgrade and the same happened.
Any ideas how to upgrade her nexus 7?
Thanks
Fastboot mode is working ?
Sent from my GT-I9100 using xda premium
I've not tried it.
How do I try it?
Assuming it's ok, does that help with upgrading?
Any issue truing fast boot mode?
Any ideas? Or will it need replacing?
Factory reset and try again
Sent from my Nexus 7
I have the same problem.
Hey guys,
I made an account just to post this, however it was all done my G2 so I apologize for poor formatting and/or not completely clear instructions. This issue has kept me up for hours upon hours, and I finally figured out how to fix it. The issue apparently has something to do with the way the Nexus was formatted, prohibiting the update from working. Google/Asus support have been useless regarding the issue which is a very simple fix just requiring the user to reflash the N7 with a stock image. It has been confirmed working by not just me but other people on the reddit nexus 7 board. Here is what I did (copy/pasted from my reddit thread):
---------------------------------------------------------------------------------------------------------------------
There are two methods to fix this, an in depth method, and an easy and quick method. My first time I used the in depth, but I tested this with the easy method too so I'll just post that. I'm on a cell phone so I'm not going into the in depth method - I'm posting this so hopefully the other people like me who got this on Christmas won't have to return it.
----------------
For the quick and easy method, download Wug's toolkit here:
(google this, forums wont let me post links until I reach 10 posts)
Run the driver install guide, making sure to follow the parts about uninstalling previous drivers. Follow this to a T. Next, unlock your bootloader. Its painless and takes seconds. Next, go here and download your Nexus specific update.
(Find this on google developer site, you can google it too - forums wont let me post links - also make sure its 4.2.1)
Click on the "back to stock + unroot" -- we never rooted, but just do this. Select other/browse and browse to the image you downloaded. Flash this. You WILL fail on three files - it says something like recovery.sig failed - it will do it for two other .sig files. This is fine. Let it do its thing. A few minutes later your android will boot up. Log in, and go to settings. Click about tablet. Click on build number like 10 times, until it tells you developer options unlocked. Go into developer options and enable USB debugging. Now, go back to Wugs toolkit and lock the bootloader. There you have it, an updated nexus running stock everything, and locked so your warranty is not void.
----------------------------------------------------------------------------------------------------------------------------
This was a very sloppy guide put together on my cell phone. Any questions just post and I'll do my best to get back to you. Goodluck!
Hi.
Thanks for the reply.
Just wondering if there is an easier way to do this.
I'm not comfortable flashing a new device.
What was the suggestion about fast boot?
Thanks
albert_htc said:
Hi.
Thanks for the reply.
Just wondering if there is an easier way to do this.
I'm not comfortable flashing a new device.
What was the suggestion about fast boot?
Thanks
Click to expand...
Click to collapse
This is definitely the easiest way for you to fix your problems. The risk of your device becoming unusable is practically none. This is the beauty of nexus devices, Google provides official factory reset ROMs for you to flash in these sorts of situations. You can either use Wugs or mskip's tookit as advised to automate the process (fastboot commands used to flash the recovery image, fastboot commands are simply used to flash it to your device) or you can use fastboot to flash it yourself manually (still very easy)
I would 100% do this to fix your device. Don't be scared! This is the official way of fixing a nexus device when it doesn't function.
Thanks.
I'm trying this now.
I've uninstalled all previous drivers, and it's updated to an 'Android Phone -> Android Composite ADB Interface'
I've clicked the Reboot BootLoader Button.. and nothing happens on the tablet.
This was trying with the #3 driver option.
I'm now trying driver #2 !!
Another quick question...
Once all this is done, will I have issues with it in the future, or should this resolve future updates.?
albert_htc said:
Another quick question...
Once all this is done, will I have issues with it in the future, or should this resolve future updates.?
Click to expand...
Click to collapse
I'm not certain about the driver issues because I don't use Wug's toolkit, sorry!
However, when you get this completed, it should solve this problem in the future.
I've had to go with option 1 for the drivers..
but it's done and working
One thing I did have to do after unlocking the boot loader was reset up on the wifi and re enable USB debugging before I could continue.
all sorted thanks
albert_htc said:
Thanks.
I'm trying this now.
I've uninstalled all previous drivers, and it's updated to an 'Android Phone -> Android Composite ADB Interface'
I've clicked the Reboot BootLoader Button.. and nothing happens on the tablet.
This was trying with the #3 driver option.
I'm now trying driver #2 !!
Click to expand...
Click to collapse
Let us know how it comes out and if there's problems, exactly where you're hitting the problem. I will try to help you out and later today I could probably get on team viewer and help you figure the drivers out.
Sent from my Nexus 7 using Tapatalk HD
Hi CharliesTheMan..
It's working. Had to use option 1 for the drivers.. but its updated and working
Thanks
Glad it worked out!
Sent from my Nexus 7 using Tapatalk HD
Hello forums!
Well, this my be a noob-like question, or not, I have no idea. So, here it goes...
My Sony Xperia T does not want to be rooted no matter what method I use. Bootlocker unlock is not allowed, but I have seen many root when they have this too, so it's not that causing the problem.
I used DoomLord's rooting toolkit first of all, to be told by the application that my phone LT30p is not accepted, even though the root includes that phone...
I then used Bin4ry's root with restore, and once again, that didn't work. I was taken to the service menu and had to click on Display, but that didn't work. The rooting toolkit just didn't do anything, just sat there...
Then I tried SRS Root, and that didn't work either.
I have PC companion, and I have USB Debugging and Unknown sources all enabled AND I have the ADB drivers... what is the problem!
This has been bugging me for a long time, I could do with some help!
Thanks in advance,
Joe.
Install ADB Driver first -_-
What is your OS on PC ?
Yenkazu said:
Install ADB Driver first -_-
What is your OS on PC ?
Click to expand...
Click to collapse
Yeah I have installed the ADB Driver, and I am running Windows 8.
CommandoOS said:
Yeah I have installed the ADB Driver, and I am running Windows 8.
Click to expand...
Click to collapse
Known issue, ADB driver cannot working under Windows 8
Just switch to older OS
Or find another PC without Windows 8 inside
XD
Yenkazu said:
Known issue, ADB driver cannot working under Windows 8
Just switch to older OS
Or find another PC without Windows 8 inside
XD
Click to expand...
Click to collapse
Aweeeeesome!
Thanks man, let me go test this on my laptop!
Okay, new problem. On my laptop, I have installed PC Companion, the device drivers have installed but now, when I try to add adb drivers it will not let me, and when I use the ADB Installer, it is not recognizing my device.
CommandoOS said:
Okay, new problem. On my laptop, I have installed PC Companion, the device drivers have installed but now, when I try to add adb drivers it will not let me, and when I use the ADB Installer, it is not recognizing my device.
Click to expand...
Click to collapse
Try disable any antivirus or similar program like that
Don't use non specific ADB driver
I guess, installing PCC it's enough
Btw, I never use any Sony software now
The best ADB driver you can find, by using ADB driver from flashtool
XD
Okay well, I got the drivers working (thanks to you) but...
dom...dom. doooooooooooom!
Still not working. For example, when using Bin4ry's root, I get to the part where you have to sit on service tests>display and nothing happens, and after about 10 minutes, it simply says root failed in console, but device does restart, but is not rooted.
CommandoOS said:
Okay well, I got the drivers working (thanks to you) but...
dom...dom. doooooooooooom!
Still not working. For example, when using Bin4ry's root, I get to the part where you have to sit on service tests>display and nothing happens, and after about 10 minutes, it simply says root failed in console, but device does restart, but is not rooted.
Click to expand...
Click to collapse
I had same problem as you
I installed flashtool then installed all driver, and i used the root thing on flashtool and it worked perfectly
CommandoOS said:
Okay well, I got the drivers working (thanks to you) but...
dom...dom. doooooooooooom!
Still not working. For example, when using Bin4ry's root, I get to the part where you have to sit on service tests>display and nothing happens, and after about 10 minutes, it simply says root failed in console, but device does restart, but is not rooted.
Click to expand...
Click to collapse
Don't use Binary method
Using Doomlord easy root
What the Build number your current OS ?
Yeah I have tried that, even though it clearly says that the Xperia T can be used with it:
Hi, I recently got a Xperia T and couldn't get it to root.
After messing around I finally got it to Root. What I had to do was use Bin4ry's root method first choosing option 2.
Once that was done, I then had to use Doomlord's easy root. After that was done I ran SU which deleted the version from Bin4ry's root and success, my phone was rooted.
I don't know why I have to use Bin4ry's method and the Dommlord's but I do know the only way to get my phone to root is by doing both root methods starting with Bin4ry's first.
I know for a fact this is the case because I re-flashed my phone to stock, trying different methods, in different orders. The only way to get it to root was to do Bin4ry's and then Doomlord's one after the other.
Tried it, it didn't work for me Thanks anyway dude.
CommandoOS said:
Tried it, it didn't work for me Thanks anyway dude.
Click to expand...
Click to collapse
Sorry Mate
Just use this
http://forum.xda-developers.com/showthread.php?t=2378400
I already am running that firmware?
CommandoOS said:
I already am running that firmware?
Click to expand...
Click to collapse
It's a little different
Already rooted
=)
Just find what suitable for you
Odexed or Deodexed
How do I add it. I am new to this, I understand I must seem like a noob but I guess everyone has to start somewhere.
Could you please tell me how I can add it safely?
CommandoOS said:
How do I add it. I am new to this, I understand I must seem like a noob but I guess everyone has to start somewhere.
Could you please tell me how I can add it safely?
Click to expand...
Click to collapse
you must downgrade to JB firmware that can be rooted using Binary or Doomlord method
After that, root, install CWM for locked bootloader
Then, follow instruction from the OP ( link above )
Just Google if you need more information
Yes but how can I downgrade? What do I need to do? I have looked for tutorials, I can't seem to find any.
CommandoOS said:
Yes but how can I downgrade? What do I need to do? I have looked for tutorials, I can't seem to find any.
Click to expand...
Click to collapse
All in One Thread
Just find what info you need
http://forum.xda-developers.com/showthread.php?t=1903137
I bought a Sony Xperia Z1 (C6903) on eBay, and it came installed with Kitkat.
I decided I wanted to root the device and install a custom ROM before I used it much, so I followed a guide on XDA and flashed it with the 14.1.G.1.534 build using Flashtool. (I had to install several drivers to get Flashtool to work.)
After that, I attempted to root it using Vroot, but the program didn't work (the error message was in Chinese, and when I clicked the supplied link, it was something about enabling USB debugging, which I had already done.) I then tried Kingo Android ROOT, which tried to download drivers for the phone, but always failed, so I downloaded and installed them manually as suggested. Kingo Android ROOT then did the same thing as Vroot, and told me to enable USB debugging, even though it was already enabled.
I tried reflashing it using Flashtool and trying again, but same issue.
I finally got fed up and tried to just upgrade to Kitkat again using the Software Updates feature in Phone info, but now the phone fails every time I try to update! It starts, enters the Android update screen, and then reboots a few seconds in. When the phone loads again, it says the update failed and asks me to redownload the file. I tried this several times, including leaving the phone off for a while before upgrading, and making sure it was at full charge AND on AC power, but still nothing.
So, to sum up, I can't root my phone, I can't upgrade my phone and I'm stuck on an outdated version of stock Android. I'm really frustrated with this and am hoping someone can help me.
YamiWheeler said:
So, to sum up, I can't root my phone, I can't upgrade my phone and I'm stuck on an outdated version of stock Android. I'm really frustrated with this and am hoping someone can help me.
Click to expand...
Click to collapse
Try rooting with this to see if it works
https://www.youtube.com/watch?v=1aq9YTlfCgc
Ahki767 said:
Try rooting with this to see if it works
Click to expand...
Click to collapse
MrMurphysLaw said:
https://www.youtube.com/watch?v=1aq9YTlfCgc
Click to expand...
Click to collapse
I tried this, but still nothing. :/
http://i.imgur.com/JboJ9VF.png
I'm beginning to think this is a driver issue, because I installed several drivers in an attempt to get Flashtool to work, but I don't know how to fix this. I used USBDeview to remove several drivers from my computer. After doing this, I plugged in my Xperia Z1 and it installed "C6903" on my computer, but it also prompted me to install software on the phone screen, but each time I click Install, it doesn't do anything...
I'm about ready to just chuck this phone out the window.
Windows doesn't even pick it up properly anymore, MTP doesn't install, I don't know how to fix this.
Does anyone know how to manually uninstall all of the drivers that Flashtool installs?
YamiWheeler said:
I'm about ready to just chuck this phone out the window.
Windows doesn't even pick it up properly anymore, MTP doesn't install, I don't know how to fix this.
Does anyone know how to manually uninstall all of the drivers that Flashtool installs?
Click to expand...
Click to collapse
Don't know how to uninstall the drivers (maybe in device manager?) but make sure you installed the correct ones from the flashtool drivers folder. The first time you plugged your phone in with usb debugging on, did the phone show anything about rsa keys?
Ahki767 said:
Don't know how to uninstall the drivers (maybe in device manager?) but make sure you installed the correct ones from the flashtool drivers folder. The first time you plugged your phone in with usb debugging on, did the phone show anything about rsa keys?
Click to expand...
Click to collapse
Not to my knowledge, no. :/
I suggest you need those drivers.
Firstly you need to read more. Vroot is NOT a trusted way to root your phone. It send your IMEI address to an ip address in chice for no known reason.
Secondly, there is no need to root on .534 FW, that's the point of downgrading to it. Just install the dual recovery whilst on that FW and then flash SuperSU.zip from chainfires website.
Then just flash a 4.4 rom of your choice.
YamiWheeler said:
Not to my knowledge, no. :/
Click to expand...
Click to collapse
Well i'm sure if the drivers ain't installed correctly you wouldn't be able to flash anyways so i don't think its a driver problem. try flashing .534 again and turn on usb debugging and plug your phone in with the screen on and see if there's any pop up
Edit: Just saw gregs reply, totally forgot this method but yes try installing nuts dualrecovery
gregbradley said:
I suggest you need those drivers.
Firstly you need to read more. Vroot is NOT a trusted way to root your phone. It send your IMEI address to an ip address in chice for no known reason.
Secondly, there is no need to root on .534 FW, that's the point of downgrading to it. Just install the dual recovery whilst on that FW and then flash SuperSU.zip from chainfires website.
Then just flash a 4.4 rom of your choice.
Click to expand...
Click to collapse
Wow, after all of the various options I tried, the Dual Recovery worked, even when nothing else on my system was recognizing the phone. Thank you so much. I managed to install Superuser too, but how do I flash a ROM at this point? By starting the dual recovery again?
Forgive my lack of knowledge of this, the only thing I've ever rooted was a Samsung Galaxy S3 Mini, and that process seemed a lot simpler than this. :/ At least, before your method.
YamiWheeler said:
Wow, after all of the various options I tried, the Dual Recovery worked, even when nothing else on my system was recognizing the phone. Thank you so much. I managed to install Superuser too, but how do I flash a ROM at this point? By starting the dual recovery again?
Click to expand...
Click to collapse
Press up button while booting (Sony logo) to get into TWRP to flash roms. ROM threads always have guides on how to flash their roms so just check there for any flashing guide.
Ahki767 said:
Press up button while booting (Sony logo) to get into TWRP to flash roms. ROM threads always have guides on how to flash their roms so just check there for any flashing guide.
Click to expand...
Click to collapse
But don't I have to unlock the bootloader first?
no
Thanks for all your help, it's working and all is well.
Hello all, after spending many hours Googling, rebooting, retrying, and staying up way too late, I am stuck. Hopefully someone can provide some guidance as I'm lost.
Yesterday I received my 64GB Nexus 6 from Motorola. I'm on Verizon. Popped in my SIM and was in business. Got it set up in short order, and it applied 5.0.1 OTA almost immediately. I downloaded the .zip for 5.1 and wanted to sideload it as I didn't want to wait for the OTA to hit my phone who-knows-when. Downloaded all the proper utilities and got the phone to show up when executing adb devices. I followed the sideloading guide and was golden up to the point of adb sideload xxxxxxx.zip. Error is "device not found". I uninstalled and reinstalled more drivers than I can shake a stick at, and the phone just won't show up in Device Manager once it's in Recovery. I did my fair share of Googling before posting here and there are many suggestions - most of which point to the driver - but none of them seem to work. I even tried the NRT by Wug and while it gives me two thumbs up as far as drivers are concerned, no dice once the phone is in Recovery.
I am on a Windows 7 Pro 64-bit machine.
So my questions are:
What the heck am I doing wrong?
Is there a way to sideload with the file on the phone already and not have to use adb?
Any help, suggestions, "hey dummy you forgot this", etc., is most welcome . Thank you in advance!
@Lucky Armpit
When you are in recovery, at the adb sideload screen, unplug your N6 and plug it in again.
Lucky Armpit said:
Hello all, after spending many hours Googling, rebooting, retrying, and staying up way too late, I am stuck. Hopefully someone can provide some guidance as I'm lost.
Yesterday I received my 64GB Nexus 6 from Motorola. I'm on Verizon. Popped in my SIM and was in business. Got it set up in short order, and it applied 5.0.1 OTA almost immediately. I downloaded the .zip for 5.1 and wanted to sideload it as I didn't want to wait for the OTA to hit my phone who-knows-when. Downloaded all the proper utilities and got the phone to show up when executing adb devices. I followed the sideloading guide and was golden up to the point of adb sideload xxxxxxx.zip. Error is "device not found". I uninstalled and reinstalled more drivers than I can shake a stick at, and the phone just won't show up in Device Manager once it's in Recovery. I did my fair share of Googling before posting here and there are many suggestions - most of which point to the driver - but none of them seem to work. I even tried the NRT by Wug and while it gives me two thumbs up as far as drivers are concerned, no dice once the phone is in Recovery.
I am on a Windows 7 Pro 64-bit machine.
So my questions are:
What the heck am I doing wrong?
Is there a way to sideload with the file on the phone already and not have to use adb?
Any help, suggestions, "hey dummy you forgot this", etc., is most welcome . Thank you in advance!
Click to expand...
Click to collapse
Use Wugs toolkit to install drivers. It has a great step by step set-up to make sure it works and it tests everything so you know it works..
cam30era said:
@Lucky Armpit
When you are in recovery, at the adb sideload screen, unplug your N6 and plug it in again.
Click to expand...
Click to collapse
Hi cam30era, I tried that but it didn't help. I didn't try it after using Wug's toolkit so it's worth another shot.
Xplicit84 said:
Use Wugs toolkit to install drivers. It has a great step by step set-up to make sure it works and it tests everything so you know it works..
Click to expand...
Click to collapse
Hi Xplicit84, I used the Wugs toolkit provided in the NRT to install the proper drivers (it worked fantastic, by the way... mad props to Wug). That didn't help unfortunately.
try a different usb port
goto the device manager in windows and see if everything is good (no ! by a device)
apristel said:
try a different usb port
goto the device manager in windows and see if everything is good (no ! by a device)
Click to expand...
Click to collapse
Hi apristel, yup, tried that too, as I had read that perhaps there may be an issue with USB 3.0 ports. I don't think I have USB 3.0 ports (my laptop is a 2012-era Alienware M17x R3) but I tried a different port for the sake of doing it and it didn't make a difference.
Where did you get the 5.1 .zip file? Give us the exact name of the file because the 5.1 VZW .zip file that has been posted here that ends with .xml.zip is not designed for an adb sideload command. I.e., not designed to be flashed in recovery at all.
teddyearp said:
Where did you get the 5.1 .zip file? Give us the exact name of the file because the 5.1 VZW .zip file that has been posted here that ends with .xml.zip is not designed for an adb sideload command. I.e., not designed to be flashed in recovery at all.
Click to expand...
Click to collapse
Hi teddyearp, I downloaded it from a link on Droid-Life. I don't remember the exact name of the file because I renamed it to something much shorter, but here's where I got it from -
http://www.droid-life.com/2015/03/1...s-for-nexus-devices-4-5-6-7-9-10/#more-163271
Edit - Here's the direct link (the one I used) - http://android.clients.google.com/p...ed-shamu-ota-LMY47D-from-LRX22C-fullradio.zip
Lucky Armpit said:
Hello all, after spending many hours Googling, rebooting, retrying, and staying up way too late, I am stuck. Hopefully someone can provide some guidance as I'm lost.
Yesterday I received my 64GB Nexus 6 from Motorola. I'm on Verizon. Popped in my SIM and was in business. Got it set up in short order, and it applied 5.0.1 OTA almost immediately. I downloaded the .zip for 5.1 and wanted to sideload it as I didn't want to wait for the OTA to hit my phone who-knows-when. Downloaded all the proper utilities and got the phone to show up when executing adb devices. I followed the sideloading guide and was golden up to the point of adb sideload xxxxxxx.zip. Error is "device not found". I uninstalled and reinstalled more drivers than I can shake a stick at, and the phone just won't show up in Device Manager once it's in Recovery. I did my fair share of Googling before posting here and there are many suggestions - most of which point to the driver - but none of them seem to work. I even tried the NRT by Wug and while it gives me two thumbs up as far as drivers are concerned, no dice once the phone is in Recovery.
I am on a Windows 7 Pro 64-bit machine.
So my questions are:
What the heck am I doing wrong?
Is there a way to sideload with the file on the phone already and not have to use adb?
Any help, suggestions, "hey dummy you forgot this", etc., is most welcome . Thank you in advance!
Click to expand...
Click to collapse
Any luck, having the same problem and it's driving me nuts.
Mongo23ny said:
Any luck, having the same problem and it's driving me nuts.
Click to expand...
Click to collapse
Are you selecting "apply update from ADB" in recovery and then hitting power?
Then: adb sideload <filename of update.zip>
?
apristel said:
Are you selecting "apply update from ADB" in recovery and then hitting power?
Then: adb sideload <filename of update.zip>
?
Click to expand...
Click to collapse
Yes, as soon as boots into recovery it completely disappears from device manager. If I run the command after apply update from adb it says device not found.
Mongo23ny said:
Yes, as soon as boots into recovery it completely disappears from device manager. If I run the command after apply update from adb it says device not found.
Click to expand...
Click to collapse
Most likely a driver issue. I can remote in and check it out if you want using teamviewer
Go through the driver setup in wug again, pay close attention when you are deleting any old drivers..... delete anything that says google nexus or android... I had to do it twice.... put the phone into adb side load mode... check device manager again.. make sure you dont have a ? by android device... I did... update the driver from wug ( also I hid the sdk driver folder by renaming it so windows didn't try to pick up the driver from there again... once installed bingo!
apristel said:
Most likely a driver issue. I can remote in and check it out if you want using teamviewer
Click to expand...
Click to collapse
When I run the command reboot bootloader, no problem. But when it is in recovery I watched it disappear from device manager.
---------- Post added at 10:19 PM ---------- Previous post was at 10:18 PM ----------
Gage_Hero said:
Go through the driver setup in wug again, pay close attention when you are deleting any old drivers..... delete anything that says google nexus or android... I had to do it twice.... put the phone into adb side load mode... check device manager again.. make sure you dont have a ? by android device... I did... update the driver from wug ( also I hid the sdk driver folder by renaming it so windows didn't try to pick up the driver from there again... once installed bingo!
Click to expand...
Click to collapse
I used CF auto root to unlock the bootloader and root. I do have the NRT on my computer though.
Mongo23ny said:
When I run the command reboot bootloader, no problem. But when it is in recovery I watched it disappear from device manager.
---------- Post added at 10:19 PM ---------- Previous post was at 10:18 PM ----------
I used CF auto root to unlock the bootloader and root. I do have the NRT on my computer though.
Click to expand...
Click to collapse
I still think its a driver issue for you though. I am using the ones you can download here and it works fine.
http://developer.android.com/sdk/win-usb.html#download (Where it says... Click here to download the latest Google USB Driver ZIP file.)
apristel said:
I still think its a driver issue for you though. I am using the ones you can download here and it works fine.
http://developer.android.com/sdk/win-usb.html#download (Where it says... Click here to download the latest Google USB Driver ZIP file.)
Click to expand...
Click to collapse
How do I install it properly? I got rid of some old drivers as well
Mongo23ny said:
How do I install it properly? I got rid of some old drivers as well
Click to expand...
Click to collapse
Well you can just change them in the device manager.
I'm willing to use team viewer and show you how. (you'd see everything i do) It's hard to write it out for me right now..just had hand surgery this morning and my hand is still completely numb. If you want to download this and run it http://download.teamviewer.com/download/TeamViewerQS_en.exe
PM me the id and password and i'll connect up and show ya. Just so you know, it'd be a one time thing connecting, your password changes everytime and you'd have to have that running to connect. I own a computer repair store and use it frequently.
apristel said:
I still think its a driver issue for you though. I am using the ones you can download here and it works fine.
http://developer.android.com/sdk/win-usb.html#download (Where it says... Click here to download the latest Google USB Driver ZIP file.)
Click to expand...
Click to collapse
I'm thinking that's the problem for me too, but I don't understand what I'm missing. When I ran Wug, I removed anything and everything that had the word "Google" next to it. Wug installed the drivers (had to do option #2 before I got no errors at all) and it reports that everything is hunky-dory. But as Mongo23ny said, that's exactly what happens... when it's at the boot menu it's in Device Manager but the moment I select Recovery it disappears.
Lucky Armpit said:
I'm thinking that's the problem for me too, but I don't understand what I'm missing. When I ran Wug, I removed anything and everything that had the word "Google" next to it. Wug installed the drivers (had to do option #2 before I got no errors at all) and it reports that everything is hunky-dory. But as Mongo23ny said, that's exactly what happens... when it's at the boot menu it's in Device Manager but the moment I select Recovery it disappears.
Click to expand...
Click to collapse
I can try to fix your drivers too, just follow the link i posted for him and send me the info. I don't have stock recovery on my phone to replicate your issue.
apristel said:
I can try to fix your drivers too, just follow the link i posted for him and send me the info. I don't have stock recovery on my phone to replicate your issue.
Click to expand...
Click to collapse
PM sent. Thanks
Hello XDA forums,
I really don't like the issue of trying to set the drivers of fastboot/google and so on....also all of these adb commands.
Is there a way to unlock bootloader & root by:
1) one of these "1 click" tools that do everything for the use? (such as "wugfresh Nexus Root Toolkit")
2) Just do everything by the phone? (if there is a possible to install some how a recovery such as twrp and than root by some app?)
Could anybody guide me through the steps, if needed?
Many thanks!
shabydog said:
Hello XDA forums,
I really don't like the issue of trying to set the drivers of fastboot/google and so on....also all of these adb commands.
Is there a way to unlock bootloader & root by:
1) one of these "1 click" tools that do everything for the use? (such as "wugfresh Nexus Root Toolkit")
2) Just do everything by the phone? (if there is a possible to install some how a recovery such as twrp and than root by some app?)
Could anybody guide me through the steps, if needed?
Many thanks!
Click to expand...
Click to collapse
AFAIK you will need a pc to 1)unlock your bootloader and 2)flash TWRP. After that the rest can be done locally. I also never used any toolkit. Making it easy is making it more dangerous IMHO.
Droidphilev said:
I also never used any toolkit. Making it easy is making it more dangerous IMHO.
Click to expand...
Click to collapse
Second that.
shabydog said:
2) Just do everything by the phone? (if there is a possible to install some how a recovery such as twrp and than root by some app?)
Click to expand...
Click to collapse
So at least once you need to connect your phone to a desktop computer. It can be practically running anything, within reason of course: Wiindows. Mac OSX, Linux (almost any distro).
You need to unlock your bootloader with one command, but a warning here: Unlocking the bootloader will erase everything from your phone..
Then you need to install a custom recovery, preferably TWRP. After that everything can be done from the phone itself. Well at least until you soft brick it somehow, then you'll might have to use the PC again.
Also two things:
1. No OTAs for rooted phones
2. Don't lock your bootloader if you want to mess with it, because with a locked bootloader, and Enable OEM Unlocking set to off, and without TWRP, if you soft brick it accidentally, you are boned.
Hello XDA forums,
I really don't like the issue of trying to set the drivers of fastboot/google and so on.
Is there a way to unlock bootloader & root by:
1) one of these "1 click" tools that do everything for the use?
2) Just do everything by the phone? (if there is a possible to install some how a recovery such as twrp and than root by some app?)
Could anybody guide me through the steps, if needed?
And i really prefer to do it on the device and not by ADB commands.
@istperson
I dont want to mess with th BL ... only for installing dev roms (or later then the stock with root).
Many thanks!
shabydog said:
@istperson
I dont want to mess with th BL ... only for installing dev roms (or later then the stock with root).
Many thanks!
Click to expand...
Click to collapse
Well, you still will have to unlock it, if you want root, or want to flash a custom recovery.
Sent from my Nexus 6 running cyosp using Tapatalk
shabydog said:
......I really don't like the issue of trying to set the drivers of fastboot/google and so on!
Click to expand...
Click to collapse
Than do not 'root' your phone.
hi xda.. i want to root my phone but dont want to touch it. is there a way to root my n6 without touching it? :silly:
simms22 said:
hi xda.. i want to root my phone but dont want to touch it. is there a way to root my n6 without touching it? :silly:
Click to expand...
Click to collapse
Ha ha, or I don't want my birthday to be on the day I was born every year ?
I can recommend the NTRT, the Nexus Telepathic Rooting Tools.
OK.
I want to do that with a toolkit, only bcs it install the drivers.
What Is the most recommended and easiest to use?
I do looking for the 1 click do all.
Does NTRT do that?
Thank you all.
we are eventually goung to have a "my n6 is bricked, how do i fix it with one click" thread here. seriously though, thats what happens when you use toolkits, but do no real research about modding your device.
Toolkits are fine if you first understand what they are doing. Otherwise it's like giving a hand grenade to a child to play with.
Sent from my Nexus 6 using Tapatalk
shabydog said:
Could anybody guide me through the steps, if needed?
Click to expand...
Click to collapse
<prev> step <next>
simms22 said:
seriously though, thats what happens when you use toolkits, but do no real research about modding your device.
Click to expand...
Click to collapse
I seriously belive that if a user know exactly for to chose and click - yes it could be great.
wtherrell said:
Toolkits are fine if you first understand what they are doing. Otherwise it's like giving a hand grenade to a child to play with.
Click to expand...
Click to collapse
It is fairly enough to read directions and slowly-slowly.
NLBeev said:
<prev> step <next>
Click to expand...
Click to collapse
Thanks!
==========================================================
Bottom line:
Guess many users completed the unlocking & rooting by this tool
Why not?
shabydog said:
I seriously belive that if a user know exactly for to chose and click - yes it could be great.
Click to expand...
Click to collapse
i agree with you. if there is somebody who knows the ins and outs already, a one click root would be great. and there will be. problem is that marshmallow just came out, and a few things have changed, like like yoe also need a custom kernel to have root on marshmallow.
shabydog said:
I seriously belive that if a user know exactly for to chose and click - yes it could be great.
It is fairly enough to read directions and slowly-slowly.
Bottom line:
Guess many users completed the unlocking & rooting by this tool
Why not?
Click to expand...
Click to collapse
There is a reason you're pushing this topic, and I'm quite sure it's because you would feel safer, if there was a tool that did the scary things instead of you. Well, there's no such tool. If you were willing to search XDA, you would find out that the first two weeks after Marshmallow came out were about people bricking their Nexus 6s with toolkits. Then the toolkit got updated and suddenly it knew that is has to flash a modified boot.img too for the root not to brick the phone. But for two weeks it didn't know, because it wasn't necessary for Lollipop. And it will only work until the next security update comes out. And that's once a month.
Meanwhile those who were willing to use the search function, and learned the five minute procedure, were able to update their rooted phones to the next security update and were able to root it as soon as the new modified boot image came out.
And this above is not something somebody will put in a help, or instructions for future updates.
Actually, this is my first time and I was able to do it pretty easily.
fastboot devices
fastboot oem unlock
my bootloader was unlocked within 30 seconds of turning it on.
then, you can easily root via CF Auto root. Just put it into fastboot then doubleclick on the windows, then root, etc....
or.............go into fastboot flash recovery twrpxxxx.img, then it always offers to run SuperSU, and you get custom recovery and root at the same time, etc......
actually the biggest pain is unlocking the bootloader. My Galaxy S4 already was unlocked, so all I did was use goomanager, flash TWRP which always offers to run SuperSU if you don't have it.
Pretty easy, I did unlock bootloader, root, and custom recovery in 10 min.
---------- Post added at 01:48 AM ---------- Previous post was at 01:44 AM ----------
............................Then I got sick of stock Google's ROM in 15 min and wiped it and put a custom ROM instead.
Thank you all so much...
@mikeprius
Thank you so much for the info'!
But, could you plz write more details? such as:
1. How did you installed the drivers? (from my expirience, many times the pc dosent install this easily).
I just need the Google oem driver and that's it?
2. When drivers was set - did you made anything in your phones settings? Which?
3. What did you had to do before pushing the files? (Like...put all the files in the same folder? *which files?)
4. And then entered to fastboot mode and typed in these commands in pc:
fastboot devices
fastboot oem unlock
Regarding your last sentence ("or...."):
If i just flash the recovery via fastbot mode I can enter to twrp recovery and it offers to flash the SuperSU?
Sounds to me the best option.
Thanks!
1. The drivers were set from a previous device, so I didn't have to set them, but they can be downloaded and set though.
2. You need to enable developer options and select OEM unlock and USB debugging.
3. I didn't push the files, I just had them on my computer and ran fastboot commands.
4. Those commands are to unlock the bootloader.
There are a lot of different ways to do the same thing (Root, custom recovery, unlock bootloader)
1. Run CF Auto Root on a locked bootloader. It will unlock it automatically (Chainfire has it set that way), root, then download Flashify app and flash the latest img of TWRP.
2. Run fastboot commands to manually unlock the bootloader, flash TWRP, then use TWRP's SuperSU which will root it.
3. Run fastboot commands to unlock bootloader, run CF Autoroot which will root and load SuperSU, then flash TWRP via Flashify or fastboot.
There are many different ways to do the same thing. I actually just googled youtube videos and watched them.
TWRP has SuperSU and root built in. TWRP knows if you don't have it and offers to load it for you.
I went the scenic route just because, but presumably you can achieve all (3) using Option #1 without having to deal with fastboot, adb, etc.....Chainfire's script runs automatically.
I realy try to help people but users that run into problems because of the usage of tookits (and innability to solve problems and/or even lack the most basic knowledge needed) should ask the toolkit dev. for support imo, and not boughter users that have invested time and effort to gain that knowledge to clean up their mess. Period