Can someone please post bootloader unlock instructions - Nexus 6 Q&A, Help & Troubleshooting

This would be great to begin the Development section.
Links to Motorola drivers
Link to SDK & where to put it
Enabling unlock on the phone
When / how to run the fastboot commands
So if one of you could do this before someone else temporarily soft - bricks their phone? Please?

The instructions are no different from unlocking any nexus device with the exception that you need to check a box in developer settings. Just do a Google search.
Sent from my Nexus 6 using XDA Free mobile app

akellar said:
The instructions are no different from unlocking any nexus device with the exception that you need to check a box in developer settings. Just do a Google search.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
I myself have no problem with this, but
IMHO, I think the instructions need posting in said section. Lots of folks are getting a Nexus for 1st time. Are we going to advise all of them just to do a Google search? If that is the consensus, then so be it.

wtherrell said:
I myself have no problem with this, but
IMHO, I think the instructions need posting in said section. Lots of folks are getting a Nexus for 1st time. Are we going to advise all of them just to do a Google search? If that is the consensus, then so be it.
Click to expand...
Click to collapse
Fair but then write them or provide a link.
Sent from my Nexus 6 using XDA Free mobile app

akellar said:
Fair but then write them or provide a link.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
I think there are many more qualified than I to do that. But I will try to devote some time this week to finding drivers, lollipop SDK for windows, etc. Then, when I get the phone unlock it and record all the steps. Then (if successful) post them. Hoping all the while that someone else beats me to it.

Well for one thing you won't need to download the SDK at all.
Just get this: [TOOL]Minimal ADB and Fastboot Just tested it on Windows 10 and it works fine.
I searched for N6 drivers and couldn't find any. Motorola has a "software & drivers" section but it's empty right now.

No TWRP yet, either.

wtherrell said:
No TWRP yet, either.
Click to expand...
Click to collapse
It will come after root but google needs to post the factory images first.
Also of you download the google SDK then tap build number 7 times to enable Dev options you will be able to check he box that says allow OEM unlock. Then it's just a quick fastboot command

Pilz said:
It will come after root but google needs to post the factory images first.
Also of you download the google SDK then tap build number 7 times to enable Dev options you will be able to check he box that says allow OEM unlock. Then it's just a quick fastboot command
Click to expand...
Click to collapse
Thought I would use TWRP to flash SU update zip.
Guess I could root 1st, then flash recovery later.

Pilz said:
It will come after root but google needs to post the factory images first.
Also of you download the google SDK then tap build number 7 times to enable Dev options you will be able to check he box that says allow OEM unlock. Then it's just a quick fastboot command
Click to expand...
Click to collapse
It seems to work even without checking the OEM unlock in developer settings. I forgot all about that and ran fastboot unlock the second I opened the box and it worked without any issues.

wtherrell said:
Thought I would use TWRP to flash SU update zip.
Guess I could root 1st, then flash recovery later.
Click to expand...
Click to collapse
Yeah but TWRP took a week or two to get on the Nexus 9 after it was rooted so it will be a while. I just want root so I can install a new camera app that I have to manually move.
---------- Post added at 09:30 AM ---------- Previous post was at 09:28 AM ----------
eep2378 said:
It seems to work even without checking the OEM unlock in developer settings. I forgot all about that and ran fastboot unlock the second I opened the box and it worked without any issues.
Click to expand...
Click to collapse
Someone else did that without hitting the box and they got a softbrick so you got lucky. It's dumb that they added that extra step but I'm glad it's still unlockable.

Pilz said:
Someone else did that without hitting the box and they got a softbrick so you got lucky. It's dumb that they added that extra step but I'm glad it's still unlockable.
Click to expand...
Click to collapse
If you're referring to the other thread here, that isn't what caused his problem. Him powering down while it was formatting something likely was.

akellar said:
If you're referring to the other thread here, that isn't what caused his problem. Him powering down while it was formatting something likely was.
Click to expand...
Click to collapse
Yeah I let it sit for a while to do its thing then rebooted from fastboot. No issues. Not sure what is going on with the OP he said he let it sit for a long time and still nothing.

eep2378 said:
Yeah I let it sit for a while to do its thing then rebooted from fastboot. No issues. Not sure what is going on with the OP he said he let it sit for a long time and still nothing.
Click to expand...
Click to collapse
It could be something else that he did or and on his phone.

akellar said:
If you're referring to the other thread here, that isn't what caused his problem. Him powering down while it was formatting something likely was.
Click to expand...
Click to collapse
One of the softbricks came from selecting an incorrect device, IIRC.

gtalum said:
One of the softbricks came from selecting an incorrect device, IIRC.
Click to expand...
Click to collapse
Selecting an incorrect device? Not sure what you're referring to there.

akellar said:
Selecting an incorrect device? Not sure what you're referring to there.
Click to expand...
Click to collapse
Ignore that, I remembered something incorrectly.

Bjray said:
I searched for N6 drivers and couldn't find any. Motorola has a "software & drivers" section but it's empty right now.
Click to expand...
Click to collapse
You need to use the Google USB Drivers found here http://developer.android.com/sdk/win-usb.html#

akellar said:
Selecting an incorrect device? Not sure what you're referring to there.
Click to expand...
Click to collapse
That one was using the Wugfresh NRT somewhat prematurely. Quicker to use fastboot, I think.

jay_em113 said:
You need to use the Google USB Drivers found here http://developer.android.com/sdk/win-usb.html#
Click to expand...
Click to collapse
Thanks for the drivers link.

Related

[q] nexus 7 toolkit auto update v4.3.4

Hello,
I have been following a thread in the Developer section, I'm unable to post there.
I could not find an answer?
I want to find out if there will be an issue using the NEXUS 7 TOOLKIT AUTO UPDATE V4.3.4 (SkipSoft.net)
I already have the Android SDK installed, a long story whilst playing about with a cheap Chinese Tablet :crying:
I realised the error of my ways and now have a nice Nexus 7 (4.2.2)
*** Anybody help please?, seeing that I can't post in the appropriate thread ***
Thanks
Dave
Nexus 7 toolkit auto update v4.3.4
NinjaMogglet said:
Hello,
I have been following a thread in the Developer section, I'm unable to post there.
I could not find an answer?
I want to find out if there will be an issue using the NEXUS 7 TOOLKIT AUTO UPDATE V4.3.4 (SkipSoft.net)
I already have the Android SDK installed, a long story whilst playing about with a cheap Chinese Tablet :crying:
I realised the error of my ways and now have a nice Nexus 7 (4.2.2)
*** Anybody help please?, seeing that I can't post in the appropriate thread ***
Thanks
Dave
Click to expand...
Click to collapse
Can anybody help please?,
No problems should arise. Though I don't quite understand your question. Is this right: You want to update/install a toolkit, but you have the Android SDK installed? If that's what you are asking then no, there will be no problems.
Confirmation
Logan_M said:
No problems should arise. Though I don't quite understand your question. Is this right: You want to update/install a toolkit, but you have the Android SDK installed? If that's what you are asking then no, there will be no problems.
Click to expand...
Click to collapse
Hi,
Sorry this is quite new to me.
Yes, I had installed the official Android SDK whilst playing/experimenting with a cheap tablet.
Now I have a Nexus 7, and it is recognised by my WinXP PC alraedy.
I want to unlock & root and found the thread in the developers section, but I'm unable to post there.
I wanted to ensure that I would not encounter problems/conflicts if I installed and used the Nexus 7 toolkit auto update v4.3.4 Tool on the same PC.
Hope this makes sense?
Thanks
NinjaMogglet said:
Hi,
Sorry this is quite new to me.
Yes, I had installed the official Android SDK whilst playing/experimenting with a cheap tablet.
Now I have a Nexus 7, and it is recognised by my WinXP PC alraedy.
I want to unlock & root and found the thread in the developers section, but I'm unable to post there.
I wanted to ensure that I would not encounter problems/conflicts if I installed and used the Nexus 7 toolkit auto update v4.3.4 Tool on the same PC.
Hope this makes sense?
Thanks
Click to expand...
Click to collapse
You already have the SDK, that means you don't need a toolkit....
Sent from my Nexus 7 using Tapatalk HD
Pirateghost said:
You already have the SDK, that means you don't need a toolkit....
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Unfortunately having the SDK does not mean I can actually use it
I got in over my head, hence trying to learn/read about it it on XDA
I found the thread that appeared to offer what I want,
a toolkit that I should be able to use to unlock/root with.
Thanks
But of you have the SDK and the drivers installed you don't need toolkit
Its like 3 commands
you dont have to know how to use the entire SDK, all you need to do is be able to follow directions. every nexus is rooted the exact same way. the only thing the toolkit does is hide the commands. you could take the few minutes to learn these commands
fastboot oem unlock
fastboot flash recovery nameofrecoveryfile.img
reboot to recovery
adb push SuperSU.zip /sdcard/ (or /data/media, whatever)
flash supersu.zip with your custom recovery....
Sent from my Nexus 7 using Tapatalk HD
Pirateghost said:
You already have the SDK, that means you don't need a toolkit....
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Pirateghost said:
But of you have the SDK and the drivers installed you don't need toolkit
Its like 3 commands
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Thanks...
It was the commands I had problems with on my last attempts
I got confused over ADB mode, Fastboot mode ??
I was not sure if they are device specific, given the Toolkits appear to be ??
I just don't want to brick my Nexus
Hence the thought of getting something(Toolkit) that I can just select options, hides the complexity.
Also
The toolkit looked like I could Backup all my Apps/Data, then unlock/root, and then do a Restore.
Thanks
NinjaMogglet said:
Thanks...
It was the commands I had problems with on my last attempts
I got confused over ADB mode, Fastboot mode ??
I was not sure if they are device specific, given the Toolkits appear to be ??
I just don't want to brick my Nexus
Hence the thought of getting something(Toolkit) that I can just select options, hides the complexity.
Also
The toolkit looked like I could Backup all my Apps/Data, then unlock/root, and then do a Restore.
Thanks
Click to expand...
Click to collapse
there are many guides and tutorials on all of these points.
here's the problem with toolkits:
THEY HIDE EVERYTHING FROM YOU
sure, more than likely you will be quite successful in merely rooting and unlocking your device with one....
then there is a pretty high certainty that you will begin experimenting with mods/roms/kernels/etc
at some point during your experimentation you will come across a 'soft-brick' or a bootloop, where all you see is either the google screen or the boot animation looping over and over. how do you get out of that situation? the toolkit didnt show you how, you plug in your trusty toolkit, only to find it doesnt see the device.... PANIC MODE ON!!....great. now you are going to come to XDA and make a damn thread about how you just 'bricked' your device and the world is ending....then you get told how to fix it albeit with some frustrations and complications....the right way, with fastboot and adb
or
you could just learn the damn thing and understand what it is you are doing to your device....then there would never be a situation you could not get out of using fastboot and adb.....
it really isnt complicated, and people around here are just Friggin lazy...its ridiculous.
XDA used to mean something, now its just a pisspot of people wanting their devices to be cool, without wanting to learn anything.
All Understould
Pirateghost said:
there are many guides and tutorials on all of these points.
here's the problem with toolkits:
THEY HIDE EVERYTHING FROM YOU
sure, more than likely you will be quite successful in merely rooting and unlocking your device with one....
then there is a pretty high certainty that you will begin experimenting with mods/roms/kernels/etc
at some point during your experimentation you will come across a 'soft-brick' or a bootloop, where all you see is either the google screen or the boot animation looping over and over. how do you get out of that situation? the toolkit didnt show you how, you plug in your trusty toolkit, only to find it doesnt see the device.... PANIC MODE ON!!....great. now you are going to come to XDA and make a damn thread about how you just 'bricked' your device and the world is ending....then you get told how to fix it albeit with some frustrations and complications....the right way, with fastboot and adb
or
you could just learn the damn thing and understand what it is you are doing to your device....then there would never be a situation you could not get out of using fastboot and adb.....
it really isnt complicated, and people around here are just Friggin lazy...its ridiculous.
XDA used to mean something, now its just a pisspot of people wanting their devices to be cool, without wanting to learn anything.
Click to expand...
Click to collapse
Hi,
All understould, and I couldnt agree more. The challenge, with many things now(on the Web) is finding the right information.
There are oodles, and oodles of sites with rooting information, tips and guides... etc..
I've probably watched a dozen or more "Youtube" vid's on the same subject, and they all have subtle differences..!!
I will look for "Manual" Unlocking and Rooting info for the Nexus.. and see what I find
Thanks...
NinjaMogglet said:
Hi,
All understould, and I couldnt agree more. The challenge, with many things now(on the Web) is finding the right information.
There are oodles, and oodles of sites with rooting information, tips and guides... etc..
I've probably watched a dozen or more "Youtube" vid's on the same subject, and they all have subtle differences..!!
I will look for "Manual" Unlocking and Rooting info for the Nexus.. and see what I find
Thanks...
Click to expand...
Click to collapse
not sure why you need to go anywhere other than right here on XDA....
theres a freakin sticky for it even...
http://forum.xda-developers.com/showthread.php?t=2150661
NinjaMogglet said:
Hi,
All understould, and I couldnt agree more. The challenge, with many things now(on the Web) is finding the right information.
There are oodles, and oodles of sites with rooting information, tips and guides... etc..
I've probably watched a dozen or more "Youtube" vid's on the same subject, and they all have subtle differences..!!
I will look for "Manual" Unlocking and Rooting info for the Nexus.. and see what I find
Thanks...
Click to expand...
Click to collapse
NinjaMogglet has given you all the information needed!
Just go grab the required files and chuck them in your platform-tools directory, run a command prompt and navigate to the directory and then run the said commands.
Still not clear??
smt8544 said:
NinjaMogglet has given you all the information needed!
Just go grab the required files and chuck them in your platform-tools directory, run a command prompt and navigate to the directory and then run the said commands.
Click to expand...
Click to collapse
I thank everybody for the comments...
I have since found other "Manual" methods, none of them are consistent
> Some use ADB commands to do certain things?
> There are references to making the "Recovery Stick", with some mnt, mv commands in ADB/FASTBOOT, it's not clear?
> There is reference to being in the right mode USB Debug Mode, PTP & MTP, but which?
> Install a Busy Box?
> and and ...
Whilst it maybe second nature to some of you folks, to me(others?) it a Black Art at the moment
I will do it, I just don't want to get part way in, and have a problem.
Thanks
NinjaMogglet said:
I thank everybody for the comments...
I have since found other "Manual" methods, none of them are consistent
> Some use ADB commands to do certain things?
> There are references to making the "Recovery Stick", with some mnt, mv commands in ADB/FASTBOOT, it's not clear?
> There is reference to being in the right mode USB Debug Mode, PTP & MTP, but which?
> Install a Busy Box?
> and and ...
Whilst it maybe second nature to some of you folks, to me(others?) it a Black Art at the moment
I will do it, I just don't want to get part way in, and have a problem.
Thanks
Click to expand...
Click to collapse
my previous post literally linked you to the ONLY thing you need....why did you ignore it?
its simple:
ADB can be used while in Custom Recovery or while booted into Android with USB debugging enabled.
Fastboot is used ONLY in fastboot mode
settings within the Android OS dont mean a damn thing in recovery or fastboot....which means it doesnt matter what USB mode you are in, or if debugging is enabled, as long as you are doing things from recovery or fastboot
every nexus device roots and unlocks in the same exact manner. the only difference would be that you need to use a recovery made SPECIFICALLY for that device...thats it
FOLLOW THE GUIDE THAT I ALREADY LINKED YOU TO....it tells you everything you need to do
Thanks
Pirateghost said:
my previous post literally linked you to the ONLY thing you need....why did you ignore it?
its simple:
ADB can be used while in Custom Recovery or while booted into Android with USB debugging enabled.
Fastboot is used ONLY in fastboot mode
settings within the Android OS dont mean a damn thing in recovery or fastboot....which means it doesnt matter what USB mode you are in, or if debugging is enabled, as long as you are doing things from recovery or fastboot
every nexus device roots and unlocks in the same exact manner. the only difference would be that you need to use a recovery made SPECIFICALLY for that device...thats it
FOLLOW THE GUIDE THAT I ALREADY LINKED YOU TO....it tells you everything you need to do
Click to expand...
Click to collapse
Thanks...
I did not ignore your link, I read all the pages.
Especially the one's that pointed out the ommisions, like un-lock first, and some of the key presses.
I will get back to this when I'm bright eyed, not 01:25 in the morning.... Just in case.
Thanks again

[Q] How would you root? I'm on day FOUR of unsuccessful attempts

It started here:
http://forum.xda-developers.com/showthread.php?t=2530605
I followed this post.
http://forum.xda-developers.com/showthread.php?t=2509676
Got nowhere because of the puttytel window timeout problem.
Related to this post was this post:
http://forum.xda-developers.com/showthread.php?p=47749358#post47749358
I have an unlocked bootloader on Moto X from sprint. I just need the easiest way to root.
This looked confusing. http://forum.xda-developers.com/showthread.php?t=2536200. Gotta be another way.
Have considered restoring to stock and taking the dang thing back http://atsgadgets.com/how-to-restor...lite-att-t-mobile-sprint-verizon-us-cellular/. So frustrated.
I've offered paypal to those who can do it successfully. I am so burnt out on trying to make this work. This PITA is not worth android. I have a one click jailbroken phone now. And I have successfully rooted and installed custom roms before but this is totally out of hand how complex this is for me. Maybe I'm just remedial but it seems several are having trouble with this model. For open source, this should not be this tough.
/rant. Almost ready to throw in the towel, but still listening.....
Sorry for the multiple posts. Just trying to get some new opinions. HTC Evo 4 g was done in 10 minutes. This has taken 4 days.
:crying:
bullpen7979 said:
I have an unlocked bootloader on Moto X from sprint. I just need the easiest way to root.
This looked confusing. http://forum.xda-developers.com/showthread.php?t=2536200. Gotta be another way.
Have considered restoring to stock and taking the dang thing back http://atsgadgets.com/how-to-restor...lite-att-t-mobile-sprint-verizon-us-cellular/. So frustrated.
I've offered paypal to those who can do it successfully. I am so burnt out on trying to make this work. This PITA is not worth android. I have a one click jailbroken phone now. And I have successfully rooted and installed custom roms before but this is totally out of hand how complex this is for me. Maybe I'm just remedial but it seems several are having trouble with this model. For open source, this should not be this tough.
/rant. Almost ready to throw in the towel, but still listening.....
Sorry for the multiple posts. Just trying to get some new opinions. HTC Evo 4 g was done in 10 minutes. This has taken 4 days.
:crying:
Click to expand...
Click to collapse
Are you on 4.4 and what computer OS are you using?
I am on android version 4.2.2 and windows xp SP 3. thanks for your response, sir.
bullpen7979 said:
I am on android version 4.2.2 and windows xp SP 3. thanks for your response, sir.
Click to expand...
Click to collapse
Here, go into Settings -> About Phone and tell me what your Build Number is (at the very bottom).
Do not put in the cmd window mfastboot, just try fastboot flash recovery twrp 2.6.3.1-ghost-4.4.img. Now also put the recovery image in the same folder as fast boot, I believe its SDK tools folder
Sent on my Moto X
bullpen7979 said:
I am on android version 4.2.2 and windows xp SP 3. thanks for your response, sir.
Click to expand...
Click to collapse
The method that you thought was confusing, is the one you should use. If I have time, I could try helping you with it.
ALU0506, the build number is 13.9.0Q2.X-116-MX-17-57-1. Thanks everyone for your help.
I have downloaded the files mentioned in the thread. Thats as far as i have gotten. If you have time to help, that would be great. I mean like over the top great
bullpen7979 said:
I have downloaded the files mentioned in the thread. Thats as far as i have gotten. If you have time to help, that would be great. I mean like over the top great
Click to expand...
Click to collapse
I can try helping over gtalk.
bullpen7979 said:
I have downloaded the files mentioned in the thread. Thats as far as i have gotten. If you have time to help, that would be great. I mean like over the top great
Click to expand...
Click to collapse
Plug in your phone and put it into fastboot by typing adb reboot bootloader then type fastboot devices does it show that you are connected?
I will try that as soon as I can and get back to you. I have two computers one at my hotel and one here. I'm not sure I have the ADB tools on my netbook
Sent from my XT1056 using xda app-developers app
bullpen7979 said:
I will try that as soon as I can and get back to you. I have two computers one at my hotel and one here. I'm not sure I have the ADB tools on my netbook
Sent from my XT1056 using xda app-developers app
Click to expand...
Click to collapse
if you are still looking for help i can help you get this done on gtalk as well. send me a pm with your username. it will take virtually no time at all
jayboyyyy said:
if you are still looking for help i can help you get this done on gtalk as well. send me a pm with your username. it will take virtually no time at all
Click to expand...
Click to collapse
especially since he already unlocked the bootloader. Just flash recovery, then flash supersu.zip.
aooga said:
especially since he already unlocked the bootloader. Just flash recovery, then flash supersu.zip.
Click to expand...
Click to collapse
ya during his four days of misery, he could have just read for 1 hour on the stuff so it would seem confusing anymore and then he would have had a rooted phone. But either way, his problem is solvable with a few simple instructions.
OK Jay/Aooga.
Finally back from work.
Plug in your phone and put it into fastboot by typing adb reboot bootloader then type fastboot devices does it show that you are connected?
open cmd window, typed adb reboot bootloader, and got:
T063202TFL and fastboot, and then a prompt.
OK Jay/Aooga.
Finally back from work.
Plug in your phone and put it into fastboot by typing adb reboot bootloader then type fastboot devices does it show that you are connected?
open cmd window, typed adb reboot bootloader, and got:
T063202TFL and fastboot, and then a prompt.
Phone is in fastboot mode with white, yellow green text.
Device is unlocked. Status code 3.
Battery OK Charging
Transfer mode USB connected.
It looked as though I had to be able to accept the 4.4 kitkat OTA in order to get this done. but when i went to the usual spot to look for system updates it said there were none available.
Anyhow, I am super grateful for your help. Sorry to be such a remedial doofus
Looks like we can wait till tomorrow. Or today. Or whatever timeline it is.

[Q] Think I soft-bricked my Nexus 6...any ideas?

Some background...Rooted and unlocked. I removed encryption right after I bought it.
I attempted to flash 5.1 the update. I flashed the bootloader and radio first, and rebooted the bootloader. Everything went fine until I tried to flash the system image. I got a lot of "sparse" errors.
When it rebooted it re-encrypted the device. But now nothing works. Phone, NFC ect shows errors. I can get into the bootoader, and I can flash stuff, but the recovery menu is gone,. It's just an error icon with "no connection" now.
Any ideas on how I can salvage this? I already backed everything up before I started. Is there a way I can just wipe everything and go back to stock? Even if it is 5.01?
EDIT - My bootloader is still showing as unlocked. I did not re-lock it.
JeffDenver said:
Some background...Rooted and unlocked. I removed encryption right after I bought it.
I attempted to flash 5.1 the update. I flashed the bootloader and radio first, and rebooted the bootloader. Everything went fine until I tried to flash the system image. I got a lot of "sparse" errors.
When it rebooted it re-encrypted the device. But now nothing works. Phone, NFC ect shows errors. I can get into the bootoader, and I can flash stuff, but the recovery menu is gone,. It's just an error icon with "no connection" now.
Any ideas on how I can salvage this? I already backed everything up before I started. Is there a way I can just wipe everything and go back to stock? Even if it is 5.01?
EDIT - My bootloader is still showing as unlocked. I did not re-lock it.
Click to expand...
Click to collapse
Install factory images using fastboot
https://developers.google.com/android/nexus/images
You might have "soft bricked" it, but if you still have bootloader access you are fine
I actually tried that, but it will not recognize it from ADB...I can flash stuff via fastboot, but ADB does not see it.
I did fully update the android SDK before I started. Should'nt that have updated all the drivers needed for ADB?
JeffDenver said:
I actually tried that, but it will not recognize it from ADB...I can flash stuff via fastboot, but ADB does not see it.
I did fully update the android SDK before I started. Should'nt that have updated all the drivers needed for ADB?
Click to expand...
Click to collapse
you update via fastboot, while youre in the bootloader. adb has nothing to do with it.
When I go to the platform tools folder, and use "adb devices", it tells me nothing after "list of devices attached". As if it does not see the phone.
When I attempt to "fastboot -w update image-shamu-lmy47d.zip", a window comes up and scrolls 3 or 4 lines too fast to see, and then exits. Nothing happens.
JeffDenver said:
When I go to the platform tools folder, and use "adb devices", it tells me nothing after "list of devices attached". As if it does not see the phone.
Click to expand...
Click to collapse
Have you updated the SDK? Drivers installed? Also, read up on how to use fastboot. Fastboot only works from bootloader, not when booted into Android.
I'm all for adb, but save yourself a headache and get wugs toolkit and use force flash.
Sent from my Nexus 6 using XDA Free mobile app
Better to learn some basics first then you shall fear no soft brick ever!
http://forum.xda-developers.com/showthread.php?t=2277112
Evolution_Freak said:
Have you updated the SDK? Drivers installed? Also, read up on how to use fastboot. Fastboot only works from bootloader, not when booted into Android.
Click to expand...
Click to collapse
SDK is updated. I assumed it updated drivers as well. If not, where do I get those?
I do understand that fastboot only works while in the bootloader. I have not attempted to use it while in Android.
JeffDenver said:
When I attempt to "fastboot -w update image-shamu-lmy47d.zip", a window comes up and scrolls 3 or 4 lines too fast to see, and then exits. Nothing happens.
Click to expand...
Click to collapse
Just extract the .zip and flash the things inside separately using fastboot. You can skip user data I believe (or not if you don't care about erasing your device). Using the -w switch would have erased it anyway. The commands are easy, just "fastboot flash system system.img" and the like. Change "system" and "system.img" for the file you're flashing.
Evolution_Freak said:
Have you updated the SDK? Drivers installed? Also, read up on how to use fastboot. Fastboot only works from bootloader, not when booted into Android.
Click to expand...
Click to collapse
Konfuzion said:
I'm all for adb, but save yourself a headache and get wugs toolkit and use force flash.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Where do I get that from?
JeffDenver said:
Where do I get that from?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=56913254
Sent from my Nexus 6 using XDA Free mobile app
---------- Post added at 12:56 PM ---------- Previous post was at 12:55 PM ----------
Evolution_Freak said:
Better to learn some basics first then you shall fear no soft brick ever!
http://forum.xda-developers.com/showthread.php?t=2277112
Click to expand...
Click to collapse
Better fear the bootloader downgrade soft brick
Sent from my Nexus 6 using XDA Free mobile app
Konfuzion said:
I'm all for adb, but save yourself a headache and get wugs toolkit and use force flash.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Are you sure you know what adb is?
:/
rootSU said:
Are you sure you know what adb is?
:/
Click to expand...
Click to collapse
What's it to you? Yeah I'm fine with adb thanks. If you want to discuss something other than helping the OP go ahead and pm me.
Sent from my Nexus 6 using XDA Free mobile app
mwalt2 said:
Just extract the .zip and flash the things inside separately using fastboot. You can skip user data I believe (or not if you don't care about erasing your device). Using the -w switch would have erased it anyway. The commands are easy, just "fastboot flash system system.img" and the like. Change "system" and "system.img" for the file you're flashing.
Click to expand...
Click to collapse
Ok, I did this. It appeared to work correctly, but...
My phone looks like it did before. In "about" I see it shows 5.1 as the version. I have lost root. Shouldn't I be reset to factory appearance since I overwrote the entire system? Everything looks intact, including nova launcher.
Phone appears to be working normally. I am on the phone on hold as I type this. I am just worried about problems down the road. Do I need to flash anything else? Can I assume the bootloader and radio installed correctly?
Konfuzion said:
What's it to you? Yeah I'm fine with adb thanks. If you want to discuss something other than helping the OP go ahead and pm me.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Its just you mentioned a toolkit as an alternative to adb but adb has nothing to do with any of this so if you're going to be helping the OP, I thought I'd better check that you know what you're talking about. ...which I don't think you do... So back to the point, how I'm helping the OP is by telling him to ignore everything you say. THAT'S "what's it" to me. Cheeky chops
@JeffDenver, ignore this guy. Use fastboot. Read general > all in one guide > question 28 for any info you may need, including drivers.
to repeat again, you use fastboot to flash the factory img, while youre in the bootloader. it should take you just several minutes to do, or a little bit longer if you are being very carefull. adb has nothing to do with it.
JeffDenver said:
Ok, I did this. It appeared to work correctly, but...
My phone looks like it did before. In "about" I see it shows 5.1 as the version. I have lost root. Shouldn't I be reset to factory appearance since I overwrote the entire system? Everything looks intact, including nova launcher.
Phone appears to be working normally. I am on the phone on hold as I type this. I am just worried about problems down the road. Do I need to flash anything else? Can I assume the bootloader and radio installed correctly?
Click to expand...
Click to collapse
its probably a good idea to factory reset since you're going up a major version and have already had problems.
rootSU said:
Its just you mentioned a toolkit as an alternative to adb but adb has nothing to do with any of this so if you're going to be helping the OP, I thought I'd better check that you know what you're talking about. ...which I don't think you do... So back to the point, how I'm helping the OP is by telling him to ignore everything you say. THAT'S "what's it" to me. Cheeky chops
@JeffDenver, ignore this guy. Use fastboot. Read general > all in one guide > question 28 for any info you may need, including drivers.
Click to expand...
Click to collapse
The reason I suggested wugs, is the first thing it has you do after installation is walks you through removing old drivers and installing the correct drivers and making sure that the phone is recognized. Then it will download the needed files and check the md5's which would help to avoid further problems.
Sent from my Nexus 6 using XDA Free mobile app

Any Help/Ideas would be appreciated

Ok so I have a stock, rooted, unlocked but encrypted Nexus 6. Last night it took a bad fall. The glass only cracked in one spot, however the LCD is cracked in several areas. Turning the phone on resulted in a black display. it flickers a few small bars of convoluted color, then goes black. The phone was still on and with launch everywhere I could still "Ok Google..." to do a few things.
Now, like the total idiot I am, for some damn reason I turned the phone off after getting off the phone with Asurion. And because of encryption and the screen being unresponsive (black display) I can't enter the damn screen pattern to unlock it, so I can't boot it up to drag and drop files or use adb to wipe the phone.
Does anyone have any suggestions to where I can somehow either access my files or at the very least wipe the phone? Most of my info that was on the phone is backed up to Googles servers. The are few items that aren't, that I hope I can get, but if I can't, I need to make sure are wiped. Can I enter fastboot without the pattern unlock? Or should I look into someone to repair the screen to at least get it turned on and functional to do what I need?
Thanks in advance!
Phaded said:
Can I enter fastboot without the pattern unlock?
Click to expand...
Click to collapse
If memory serves me right, you can run fastboot commands without having to enter the pattern/pin.
jj14 said:
If memory serves me right, you can run fastboot commands without having to enter the pattern/pin.
Click to expand...
Click to collapse
OK thanks. I will try that when I get home and just flash the factory image to wipe. thanks!
Hmm... from Google support pages:
If your device is running Android 5.1 or higher: Your device is protected to prevent other people from using it if it's been reset to factory settings. To ensure that it's really you doing the reset, you'll need to enter a Google username and password associated with the device after factory reset. If you don't have this information, you won't be able to finish the setup process and use the device at all after factory reset.
Does this mean even if I wipe it, the phone won't be usable for anyone?? they can't refurbish the phone because the phone will need my google info??
Eh screw it... Just gonna send it into Motorola
Phaded said:
Hmm... from Google support pages:
If your device is running Android 5.1 or higher: Your device is protected to prevent other people from using it if it's been reset to factory settings. To ensure that it's really you doing the reset, you'll need to enter a Google username and password associated with the device after factory reset. If you don't have this information, you won't be able to finish the setup process and use the device at all after factory reset.
Does this mean even if I wipe it, the phone won't be usable for anyone?? they can't refurbish the phone because the phone will need my google info??
Click to expand...
Click to collapse
yup, mean even after you wipe it, lets say 100 times, itll still ask you for your password. its security, there would be no point if you could wipe it away. but, there is a way to get rid of it, by flashing the 5.0 or 5.0.1 factory images.
simms22 said:
yup, mean even after you wipe it, lets say 100 times, itll still ask you for your password. its security, there would be no point if you could wipe it away. but, there is a way to get rid of it, by flashing the 5.0 or 5.0.1 factory images.
Click to expand...
Click to collapse
oh so if i flash an older factory image that didn't have that security feature it'll work? thanks.
Phaded said:
oh so if i flash an older factory image that didn't have that security feature it'll work? thanks.
Click to expand...
Click to collapse
yes, as long as your bootloader is unlocked. those images didn't have the security yet.
Phaded said:
they can't refurbish the phone because the phone will need my google info??
Click to expand...
Click to collapse
Hate to say this, but that's their problem You can bet that Google/Motorola will know how to get around it
---------- Post added at 01:42 PM ---------- Previous post was at 01:40 PM ----------
simms22 said:
yes, as long as your bootloader is unlocked. those images didn't have the security yet.
Click to expand...
Click to collapse
Wasn't there some issue with downgrading the bootloader causing problems? Or am I confusing with some other device?
jj14 said:
Hate to say this, but that's their problem You can bet that Google/Motorola will know how to get around it
---------- Post added at 01:42 PM ---------- Previous post was at 01:40 PM ----------
Wasn't there some issue with downgrading the bootloader causing problems? Or am I confusing with some other device?
Click to expand...
Click to collapse
It's my understanding, but I am new to the N6 so correct me if I am wrong, you can downgrade the 5.0 or 5.0.1 factory img as long as you don't downgrade to 71.05 bootloader.
byrdcfmma said:
It's my understanding, but I am new to the N6 so correct me if I am wrong, you can downgrade the 5.0 or 5.0.1 factory img as long as you don't downgrade to 71.05 bootloader.
Click to expand...
Click to collapse
that sounds about right. Just wanted to make sure op didn't flash all images in the factory image
jj14 said:
that sounds about right. Just wanted to make sure op didn't flash all images in the factory image
Click to expand...
Click to collapse
Maybe someone with more exp can give the exact process. I assume you are looking for a img with no bootloader, recovery, and radio like these http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052 but older img's
I just got my N6 yesterday, and been reading my a$$ off so I don't mess anything up. So far I have unlocked the bootloader, rooted and installed TWRP.
byrdcfmma said:
Maybe someone with more exp can give the exact process. I assume you are looking for a img with no bootloader, recovery, and radio like these http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052 but older img's
I just got my N6 yesterday, and been reading my a$$ off so I don't mess anything up. So far I have unlocked the bootloader, rooted and installed TWRP.
Click to expand...
Click to collapse
One can always go to the google developer images site (developers.google.com/android/nexus/images) and download the image they need. Unzip the downloaded file, and unzip the resulting file. In that, you'll find yet some img files, and yet another zip file that will contain the rest of the img files. Choose which one you want, and flash away
Ok so I was able to get it so the lock screen pattern is gone.
At this point I'm about to do insurance claim.
I want to pull my data (pics etc) off.
I have twrp installed and can get into recovery. Adb devices results in showing my device.
Adb/USB debugging isn't active when booted normally as I flashed new system
Tried using a tool to pull using adb, but no data gets pulled
Anyone have a method for pulling my data off? It's set to charge mode by default so it doesn't show in windows explorer.
Thanks
Sent from my Nexus 6 using XDA Free mobile app
I'm currently in the exact same predicament. Let me know how it goes.
Phaded said:
Ok so I was able to get it so the lock screen pattern is gone.
At this point I'm about to do insurance claim.
I want to pull my data (pics etc) off.
I have twrp installed and can get into recovery. Adb devices results in showing my device.
Adb/USB debugging isn't active when booted normally as I flashed new system
Tried using a tool to pull using adb, but no data gets pulled
Anyone have a method for pulling my data off? It's set to charge mode by default so it doesn't show in windows explorer.
Thanks
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Use adb pull from booted into recovery.
danarama said:
Use adb pull from booted into recovery.
Click to expand...
Click to collapse
Do you happen to know what path I would enter to pull from? I have to specify the target correct? I tried using an adb recovery tool, but when it went to /sdcard it said that path didn't exist.
I believe right now I flashed a 5.0 image (pre forced encryption?)
Sent from my Nexus 6 using XDA Free mobile app
This is the tool I tried to use:
http://forum.xda-developers.com/showthread.php?t=2339530
Sent from my Nexus 6 using XDA Free mobile app
Phaded said:
Do you happen to know what path I would enter to pull from? I have to specify the target correct? I tried using an adb recovery tool, but when it went to /sdcard it said that path didn't exist.
I believe right now I flashed a 5.0 image (pre forced encryption?)
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Is it lollipop?
You need to mount data or sdcard first.
this should work
Code:
adb shell
mount /data
exit
adb pull /data/media/0/* c:\users\phaded\desktop\mybackup\
I've made some assumptions above.
danarama said:
Is it lollipop?
You need to mount data or sdcard first.
this should work
Code:
adb shell
mount /data
exit
adb pull /data/media/0/* c:\users\phaded\desktop\mybackup\
I've made some assumptions above.
Click to expand...
Click to collapse
Yes it's lollipop, just an earlier version of it that didn't have the pattern lock (or whatever security) prompt at boot. I think 5.0.1.
I'm not rooted, does that matter for adb shell in recovery?
/data/media/0/ is my whole sd card correct? Is there a command that will show my directory in that path so I can cherry pick the folders to extract?
Sent from my Nexus 6 using XDA Free mobile app

Bad first time experience when I tried rooting my Nexus 6 Marshmallow.

I just bought myself an almost mint condition Nexus 6 (build MRA58R). It's running Marshmallow and I tried rooting it today. After I researched how to go by obtaining root I tried it out, felt very confident, didn't come across any errors. But then when I was booting back up, a screen with red letters saying something about my phone being corrupted was not allowing my phone to boot. Naturally, first I panicked. Afterwards I researched, found and then executed a manual flash of system, boot, bootloader, cache and recovery images. Then, my phone was back up and running. Discouraged and defeated, here I am knowing I could've done some better things with my time than mash commands into a terminal to fix my nooby mistake for a few hours. How should I approach obtaining root on my phone if at all possible with my model?
meeniemuffin said:
.... But then when I was booting back up, a screen with red letters saying something about my phone being corrupted was not allowing my phone to boot.
Click to expand...
Click to collapse
You could bring Google to court when your device is working 100% and the message says it is corrupt. Read the OP of this link. http://forum.xda-developers.com/showthread.php?t=3059493
meeniemuffin said:
I just bought myself an almost mint condition Nexus 6 (build MRA58R). It's running Marshmallow and I tried rooting it today. After I researched how to go by obtaining root I tried it out, felt very confident, didn't come across any errors. But then when I was booting back up, a screen with red letters saying something about my phone being corrupted was not allowing my phone to boot. Naturally, first I panicked. Afterwards I researched, found and then executed a manual flash of system, boot, bootloader, cache and recovery images. Then, my phone was back up and running. Discouraged and defeated, here I am knowing I could've done some better things with my time than mash commands into a terminal to fix my nooby mistake for a few hours. How should I approach obtaining root on my phone if at all possible with my model?
Click to expand...
Click to collapse
-enable "OEM unlocking" in developer options
-unlock bootloader
-flash TWRP using fastboot
-flash a custom kernel
-flash SuperSU 2.52
-KEEP BOOTLOADER UNLOCKED
-KEEP "OEM unlocking" ENABLED
---------- Post added at 09:50 AM ---------- Previous post was at 09:42 AM ----------
NLBeev said:
You could bring Google to court when your device is working 100% and the message says it is corrupt. Read the OP of this link. http://forum.xda-developers.com/showthread.php?t=3059493
Click to expand...
Click to collapse
There's nothing mentioned there.
Droidphilev said:
There's nothing mentioned there.
Click to expand...
Click to collapse
Hmm, here the links works. It is a link to a stock rom that is already rooted.
The rom is updated with the latest security OTA.
Full name of the OP.
[ROM]【6.0_r3】Stock MRA58R [Lite] - 【Marshmallow】【hC kernel】- 11/05/15
NLBeev said:
Hmm, here the links works. It is a link to a stock rom that is already rooted.
The rom is updated with the latest security OTA.
Full name of the OP.
[ROM]【6.0_r3】Stock MRA58R [Lite] - 【Marshmallow】【hC kernel】- 11/05/15
Click to expand...
Click to collapse
It indeed works but i thought it would bring to a page about the court thing you have mentioned.
Droidphilev said:
It indeed works but i thought it would bring to a page about the court thing you have mentioned.
Click to expand...
Click to collapse
No I was joking, sorry. But there is something serious behind the joke.
Here on XDA there are too many posts/questions about the 'corrupt message'.
The distance between ' customizing the phone' and 'Google' is growing.
NLBeev said:
No I was joking, sorry. But there is something serious behind the joke.
Here on XDA there are too many posts/questions about the 'corrupt message'.
The distance between ' customizing the phone' and 'Google' is growing.
Click to expand...
Click to collapse
Aha! i saw you posting this before but never knew that it was a joke
I didn't even need to read all this stuff. First thing I did was get into developer mode and almost instinctual that I turned on OEM unlocking before setting about unlocking the bootloader.
Sent from my Nexus 6 using Tapatalk
Yeah I bought my N6 recently and had a bad first time experience too. I ended up using a toolkit to root and all that, didn't need a custom rom so I kept it stock with TWRP and I'm very happy. Since then, I rooted some of the old devices I had laying around (you can check my signature), so I should be more prepared next time I need to update. My problem is I didn't really understand the commands, what did what and what exactly was required for root. Now that I have had plenty to practice with I'm pretty comfortable with commands and recoveries. Practice makes perfect I guess
NLBeev said:
No I was joking, sorry. But there is something serious behind the joke.
Here on XDA there are too many posts/questions about the 'corrupt message'.
The distance between ' customizing the phone' and 'Google' is growing.
Click to expand...
Click to collapse
Pretty much the trend. I bet by Android 7.0, rooting will be impossible.
shadowcore said:
Pretty much the trend. I bet by Android 7.0, rooting will be impossible.
Click to expand...
Click to collapse
I hope not. Google's software and design will be the weak point. Google could not give us some simple options like a dark interface, reboot options and dpi settings.
So, people, to sum it all up... The road to obtaining root on this Marshmallow enabled phone is?
If bootload is locked, unlock it - This will erase everything backup your device
1. Get modified boot.img for your version, flash it
2. Flash twrp
3. Flash SuperSu 2.52
meeniemuffin said:
So, people, to sum it all up... The road to obtaining root on this Marshmallow enabled phone is?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=63999613&postcount=3
!!!
Droidphilev said:
http://forum.xda-developers.com/showpost.php?p=63999613&postcount=3
!!!
Click to expand...
Click to collapse
Sorry! Slow to learn over here. I still have a question...do I need a custom kernel and flash stock rom? Or just a custom stock ROM thats already prerooted? Both, perhaps? Would I have to flash Twrp in order to even do this?
meeniemuffin said:
Sorry! Slow to learn over here. I still have a question...do I need a custom kernel and flash stock rom? Or just a custom stock ROM thats already prerooted? Both, perhaps? Would I have to flash Twrp in order to even do this?
Click to expand...
Click to collapse
You have a stockrom now, right?
if you want to keep that for now then this is the easiest way. The TWRP step is there to be able to flash the custom kernel. (and of course make backups and flash other roms in the future)
Droidphilev said:
You have a stockrom now, right?
if you want to keep that for now then this is the easiest way. The TWRP step is there to be able to flash the custom kernel. (and of course make backups and flash other roms in the future)
Click to expand...
Click to collapse
I had an epiphany earlier. I did everything....it all hit me at once. I finally managed to get Pure Nexus ROM working. Time for a test drive.
Thanks for the advice.
meeniemuffin said:
I had an epiphany earlier. I did everything....it all hit me at once. I finally managed to get Pure Nexus ROM working. Time for a test drive.
Thanks for the advice.
Click to expand...
Click to collapse
enjoy!
but DO NOT forget to keep "OEM unlocking" enabled!
(it will save you when you ever get locked out from your google acoount because you became aflashoholic)

Categories

Resources