Help! I don't know what I'm doing :( (Nexus 6) - Android Q&A, Help & Troubleshooting

Hi there,
I've tried everything and my phone is not responding,
A while ago (2 months) I unlocked the bootloader (right term?) and installed Android M Preview and over the following weeks updated to Preview 2.
However, last night I tried to root it using some software via my laptop and it ended up 'corrupting' my phone, that is if I try to power on my phone it loads up the Google start up screen with the unlocked padlock at the bottom of the screen and goes black and tries again, and then the screen changes to 'Your device is corrupt. It cannot be trusted and may not work properly' it then has a link to a page which suggests using a factory reset. However, I have reset my phone countless times, after selecting 'recovery mode' in the bootloader it takes me to a 'dead green man(?)' and says no command when I'm connected to my laptop, after that I held the power button and pressed volume up which led me to menu with the 'reboot system now' and 'reboot to bootloader' etc. along with the option to 'wipe data/factory reset and 'wipe cache partition', I have tried both of these and tried booting the device with no luck, the screen does the same as before ^^.
I have downloaded ADB, CF-Auto-Root-shamu-shamu-nexus6, WugFreshDevelopment (NRT_v2.0.5.sfx) (I think it was after I used this that it all went wrong), Elite_Shamu_LP-06_17_2015, UPDATE-SuperSU-v2.37.
I'm sure if any of that is helpful or not though.
Any questions about my current situation I'd be happy to answer, I'm really stuck! I just want to go back to stock Android and wait for the real Android M release!
I realise now that I'm a total noob and shouldn't have been messing around without knowing what I was doing.
Thanks in advance.

joespencer98 said:
Hi there,
I've tried everything and my phone is not responding,
A while ago (2 months) I unlocked the bootloader (right term?) and installed Android M Preview and over the following weeks updated to Preview 2.
However, last night I tried to root it using some software via my laptop and it ended up 'corrupting' my phone, that is if I try to power on my phone it loads up the Google start up screen with the unlocked padlock at the bottom of the screen and goes black and tries again, and then the screen changes to 'Your device is corrupt. It cannot be trusted and may not work properly' it then has a link to a page which suggests using a factory reset. However, I have reset my phone countless times, after selecting 'recovery mode' in the bootloader it takes me to a 'dead green man(?)' and says no command when I'm connected to my laptop, after that I held the power button and pressed volume up which led me to menu with the 'reboot system now' and 'reboot to bootloader' etc. along with the option to 'wipe data/factory reset and 'wipe cache partition', I have tried both of these and tried booting the device with no luck, the screen does the same as before ^^.
I have downloaded ADB, CF-Auto-Root-shamu-shamu-nexus6, WugFreshDevelopment (NRT_v2.0.5.sfx) (I think it was after I used this that it all went wrong), Elite_Shamu_LP-06_17_2015, UPDATE-SuperSU-v2.37.
I'm sure if any of that is helpful or not though.
Any questions about my current situation I'd be happy to answer, I'm really stuck! I just want to go back to stock Android and wait for the real Android M release!
I realise now that I'm a total noob and shouldn't have been messing around without knowing what I was doing.
Thanks in advance.
Click to expand...
Click to collapse
Hi, I would suggest flashing a factory image for 5.1.1 and starting fresh. Also, I suggest taking any further questions here:
http://forum.xda-developers.com/nexus-6/help/noob-friendly-qa-help-thread-t3068327
That's a friendly help thread in the nexus 6 forums, where everyone is happy to assist. I have the nexus 6 myself, and I'm sure we can get you fixed up.

Related

[P] Some options and buttons doesn't respond

Hi,
I have used http://forum.xda-developers.com/showthread.php?t=1171089 to install stock ROM and Recovery.
No I can't access "Settings\Storage and About tablet". I tried Factory data reset but cannot pres the "Reset tablet" button. Same thing when I try to "Power off" the tablet, I can't press "OK" or "Cancel" buttons or any other button.
My problems start 2 days ago when I noticed that Back, Home and all other buttons from system bar doesn't respond or responded after a lot of tries. Strange I could open the Shortcuts t Task manager and all others. Te tablet was in low power mode even if the battery was over 90%. The tablet wasn't rooted and had all updates up to date.
Before all I have tried Factory reset without success.
Next I have rooted the table and tried to install a new ROM http://forum.xda-developers.com/showthread.php?t=1488596 but the buttons still remained unresponsive. Even more I couldn't do anything because I couldn't press "Accept" button to Licence agreement of Swype. After more research I have installed the stock ROM specified above. Now the Back, Home and Clock works
This is my 3 years old kid tablet and he is crying since the tables broked, PLEASE HELP.
Samsung Galaxy Tab 10.1 GT-P5710UW
Ciprian_ said:
Hi,
I have used http://forum.xda-developers.com/showthread.php?t=1171089 to install stock ROM and Recovery.
No I can't access "Settings\Storage and About tablet". I tried Factory data reset but cannot pres the "Reset tablet" button. Same thing when I try to "Power off" the tablet, I can't press "OK" or "Cancel" buttons or any other button.
My problems start 2 days ago when I noticed that Back, Home and all other buttons from system bar doesn't respond or responded after a lot of tries. Strange I could open the Shortcuts t Task manager and all others. Te tablet was in low power mode even if the battery was over 90%. The tablet wasn't rooted and had all updates up to date.
Before all I have tried Factory reset without success.
Next I have rooted the table and tried to install a new ROM http://forum.xda-developers.com/showthread.php?t=1488596 but the buttons still remained unresponsive. Even more I couldn't do anything because I couldn't press "Accept" button to Licence agreement of Swype. After more research I have installed the stock ROM specified above. Now the Back, Home and Clock works
This is my 3 years old kid tablet and he is crying since the tables broked, PLEASE HELP.
Samsung Galaxy Tab 10.1 GT-P5710UW
Click to expand...
Click to collapse
Backup your data, preferrably with titanium backup.
Go into CW recovery. Do a full backup. Then wipe cache, data, and dalvik cache (the third one is in the "advanced" menu). wipe all three again (not necessary, I've heard someone say that this helped. I don't usually do it, but it can't hurt).
Reboot.
If that doesn't fix it, connect your tablet and put a ROM on the root of your tablet (zip file). Disconnect and then do the above steps, but after you've wiped, install the ROM from zip. When it reboots (give it 20 minutes on first boot before messing with it), is the problem solved?
I'm having this problem too. I have completely wiped the memory on the tablet, and have tried many different roms, but nothing seems to help. Can someone please help me?

Help unbrick TFP (looks like opt 3) please

Hello,
about 2 hours ago I decided that I would unlock my device (before that I read maximum informations that I could). Unlocking went fine and I also installed TWRP 2.1.3 (through ViperMod). So far so good.
Then I made backup in TWRP in case something goes wrong. I was going to try AOKP v40 so I downloaded it via goo manager and then I flashed it in TWRP Install option (and also installed gapps) and wiped cache. Device rebooted and I was stuck at AOKP boot animation for about 15 minutes when I decided to recover back. So I rebooted, restored and rebooted.
Now I'm stuck at first boot logo (eee pad). When I try to do VolDown+Power to get into recovery it doesn't ask for VolUp, but goes straight to selection of Wipe or USB. When I select fastboot or wait 10 secs device frozes. (I haven't tried wipe, just in case it would be needed to unbrick).
I read thread about unbricking (http://forum.xda-developers.com/showthread.php?t=1514088) and to me it seems like option 3, but I don't see recovery option.
In device manager I have 'ASUS Fastboot Interface'.
Here's video how it looks like: http://www.youtube.com/watch?v=7BGd1PIVbn8
Please please could anyone help me?
Btw: Is there any chance to shut down? Holding power button just resets, so does pinhole... :/
qery said:
Hello,
about 2 hours ago I decided that I would unlock my device (before that I read maximum informations that I could). Unlocking went fine and I also installed TWRP 2.1.3 (through ViperMod). So far so good.
Then I made backup in TWRP in case something goes wrong. I was going to try AOKP v40 so I downloaded it via goo manager and then I flashed it in TWRP Install option (and also installed gapps) and wiped cache. Device rebooted and I was stuck at AOKP boot animation for about 15 minutes when I decided to recover back. So I rebooted, restored and rebooted.
Now I'm stuck at first boot logo (eee pad). When I try to do VolUp+Power to get into recovery it doesn't ask for VolUp, but goes straight to selection of Wipe or USB. When I select fastboot or wait 10 secs device frozes. (I haven't tried wipe, just in case it would be needed to unbrick).
I read thread about unbricking (http://forum.xda-developers.com/showthread.php?t=1514088) and to me it seems like option 3, but I don't see recovery option.
In device manager I have 'ASUS Fastboot Interface'.
Here's video how it looks like: http://www.youtube.com/watch?v=7BGd1PIVbn8
Please please could anyone help me?
Btw: Is there any chance to shut down? Holding power button just resets, so does pinhole... :/
Click to expand...
Click to collapse
Shouldn't it be volume and power down to get to the option to press volume up for recovery?
Are you familiar with fastboot flashing recoveries? Either way that will be helpful info for us to have.
Most important thing, this is no big deal at all, it's really a minor issue. Don't let yourself get stressed out over it, the community will make sure you're good to go.
CharliesTheMan said:
Shouldn't it be volume and power down to get to the option to press volume up for recovery?
Click to expand...
Click to collapse
Yes sure my bad, it was typo (I was kinda sleepy and tired when I was writing)
CharliesTheMan said:
Are you familiar with fastboot flashing recoveries? Either way that will be helpful info for us to have.
Click to expand...
Click to collapse
Nope, this is my first time flashing.
You say you dont see the VOL_UP message. From the video it looks like it is there. You just did not press it within 5 seconds.
Once it comes up, let go of the buttons ;p
leppie said:
You say you dont see the VOL_UP message. From the video it looks like it is there. You just did not press it within 5 seconds.
Once it comes up, let go of the buttons ;p
Click to expand...
Click to collapse
nope it's not there. I was holding voldown from the start and as soon as it should say 'press volup for recovery' (time 0:04) it jumps (skips 5 seconds of waiting) directly to wipe/fastboot options (wipe is one that is selected on video)
Ok so I managed to fix my problem thanks to hanzo001's thread (http://forum.xda-developers.com/showthread.php?t=1662158). Someone should add this instructions to the [HOW-TO] Unbrick your Transformer Prime (or not) thread.
qery said:
Ok so I managed to fix my problem thanks to hanzo001's thread (http://forum.xda-developers.com/showthread.php?t=1662158). Someone should add this instructions to the [HOW-TO] Unbrick your Transformer Prime (or not) thread.
Click to expand...
Click to collapse
glad it's fixed, im sure hanzo001 will appriciate a simple thanks on his thread too..and let others know it worked for you

Nexus 10 - unlock bootloader didn't go as expected

Hi guys,
I tried to unlock the bootloader of my Nexus 10 before rooting it. Unfortunately, it didn't work and I can't use it anymore (I either have the "Loading X" forever or a dead droid while trying to go to the recovery mode).
I'm used to do that kind of modifications (only on Samsung Galaxy S and S3 though) and I don't know what I did wrong (but I usually flashed with Odin).
Anyway, I used this tool (after enabling the usb debug and allowing unknown sources) : http://forum.xda-developers.com/showthread.php?t=2001868
I installed the drivers on my PC (menu 1 in the tool), then I could see my device in ADB MODE (in the tool menu). I tried to unlock the bootloader (3rd option in the menu) and it was written completed. My device reboots and nothing happens. I can access the fastboot mode (is it the download mode ?).
I have Odin.
Can someone help me to get a working device ?
Thank you very much.
hiveNzin0 said:
Hi guys,
I tried to unlock the bootloader of my Nexus 10 before rooting it. Unfortunately, it didn't work and I can't use it anymore (I either have the "Loading X" forever or a dead droid while trying to go to the recovery mode).
I'm used to do that kind of modifications (only on Samsung Galaxy S and S3 though) and I don't know what I did wrong (but I usually flashed with Odin).
Anyway, I used this tool (after enabling the usb debug and allowing unknown sources) : http://forum.xda-developers.com/showthread.php?t=2001868
I installed the drivers on my PC (menu 1 in the tool), then I could see my device in ADB MODE (in the tool menu). I tried to unlock the bootloader (3rd option in the menu) and it was written completed. My device reboots and nothing happens. I can access the fastboot mode (is it the download mode ?).
I have Odin.
Can someone help me to get a working device ?
Thank you very much.
Click to expand...
Click to collapse
Easy fix. Get to the dead droid recovery menu and then press all 3 buttons on the top. You will get into the blue recovery options. Choose factory reset.
Sometimes unlocking the bootloaders scrambles a few things on this device and it goes into boot loop. After the factory reset, you'll be fine. PM me if you still have issues.
Sent from my Galaxy Nexus using Tapatalk 2
Blueback22 said:
Easy fix. Get to the dead droid recovery menu and then press all 3 buttons on the top. You will get into the blue recovery options. Choose factory reset.
Sometimes unlocking the bootloaders scrambles a few things on this device and it goes into boot loop. After the factory reset, you'll be fine. PM me if you still have issues.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Okay, thank you very much. I didn't know I had to press the 3 top buttons again after the dead droid screen, I thought it failed loading the Recovery Mode.
I have to setup my account etc again so I guess it is safe to say it worked.
Additionally, I tried this method after the recovery : http://forum.xda-developers.com/showthread.php?t=2015467
and it worked fine. My device has an unlocked bootloader and is rooted.
hey if someone could help me im stuck myself, after i had the dead android in recovery mode i tried to flash software with the toolkit in fastboot and now when i go to recovery its just a blank screen till i hold the bottom combo again and it takes me back to fastboot
Blueback22 said:
Easy fix. Get to the dead droid recovery menu and then press all 3 buttons on the top. You will get into the blue recovery options. Choose factory reset.
Sometimes unlocking the bootloaders scrambles a few things on this device and it goes into boot loop. After the factory reset, you'll be fine. PM me if you still have issues.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Hey,
I'm having the same problem. I get to the dead droid instead of recovery and tried hitting all three buttons again but it's just looping again.
Any ideas?
maximepull said:
Hey,
I'm having the same problem. I get to the dead droid instead of recovery and tried hitting all three buttons again but it's just looping again.
Any ideas?
Click to expand...
Click to collapse
It sounds like you didn't actually perform a factory reset. The key combination to get into stock recovery from the dead android screen is Power + Vol-Up. That will bring up the option to factory reset.
So if your powered off or bootlooping, hold the Power + Vol-Up + Vol-Down until you're back in the Bootloader. Use Vol buttons to select Recovery Mode and tap Power. When the droid w/ the Red "!" appears, hold the Power button and quick press the Vol-Up button. This should take you into stock recovery. Select Factory reset. Reboot. After a few minutes, the device should boot normally.
Good luck.
sharksfan7 said:
It sounds like you didn't actually perform a factory reset. The key combination to get into stock recovery from the dead android screen is Power + Vol-Up. That will bring up the option to factory reset.
So if your powered off or bootlooping, hold the Power + Vol-Up + Vol-Down until you're back in the Bootloader. Use Vol buttons to select Recovery Mode and tap Power. When the droid w/ the Red "!" appears, hold the Power button and quick press the Vol-Up button. This should take you into stock recovery. Select Factory reset. Reboot. After a few minutes, the device should boot normally.
Good luck.
Click to expand...
Click to collapse
Ok found a video showing that when you get to that part where there's the dead droid (the red !), you don't press hold hold all three buttons but tap them until the recovery screen shows up.
So finally did that but I still have the same problem.
My initial problem was, I received my N10, open the box, turned it on and it started freezing and rebooting. Can't get past the wifi step.
Tried hard and many times to finally get to enter my gmail account, etc
Updated to 4.3, problem persisted so I figured, maybe the factory flashed a bad rom?
So I unlocked it, rooted it and tried flashing older stock versions, same problem.
Tried flashing CM, same; PA, same...
Tried deactivating location service as suggested elsewhere: same; uninstall chrome: same
Even CM withouf GAPPS wouldnt work
So basically, I have a $500 brick. Completely useless as it freezes every 30 seconds.
Decided not to return the device because although I am Canadian, I live in SE Asia and had a visiting friend bring it to me. Way past the return period and the overall experience would be a real pain in the butt... Don't know what to do. Really hoping Kit Kat will solve it but I have doubts.
What do you think?
Sorry. I don't know enough about these things to give more in depth troubleshooting advice. I just recently got my N10 & unlocked it and based on your original post, I thought that's where you needed help. But it sounds like you got past that and got it unlocked.
Have you tried downloading a factory image directly from Google and installing that? If it's locking up on a fresh install of any ROM, it very well may be a hardware issue. You may have to file a warranty claim if possible.
maximepull said:
Ok found a video showing that when you get to that part where there's the dead droid (the red !), you don't press hold hold all three buttons but tap them until the recovery screen shows up.
So finally did that but I still have the same problem.
My initial problem was, I received my N10, open the box, turned it on and it started freezing and rebooting. Can't get past the wifi step.
Tried hard and many times to finally get to enter my gmail account, etc
Updated to 4.3, problem persisted so I figured, maybe the factory flashed a bad rom?
So I unlocked it, rooted it and tried flashing older stock versions, same problem.
Tried flashing CM, same; PA, same...
Tried deactivating location service as suggested elsewhere: same; uninstall chrome: same
Even CM withouf GAPPS wouldnt work
So basically, I have a $500 brick. Completely useless as it freezes every 30 seconds.
Decided not to return the device because although I am Canadian, I live in SE Asia and had a visiting friend bring it to me. Way past the return period and the overall experience would be a real pain in the butt... Don't know what to do. Really hoping Kit Kat will solve it but I have doubts.
What do you think?
Click to expand...
Click to collapse
sharksfan7 said:
Have you tried downloading a factory image directly from Google and installing that?
Click to expand...
Click to collapse
^ that's your solution. If you dont know how to just pm me
Sent from my Galaxy Nexus using XDA Premium HD app

Jiayu G4 (God I hate to title it like this, but yes) stuck in bootloop

How the problem occurred
So a year or two ago I bought a Jiayu G4A/T/Whatever they're calling it and safely got it here. I've used the stock ROM for a bit but I wanted to get rid of the bloatware that was still on it, so I eventually ended up with a properly rooted phone with a ROM from Jiayu.es (Everything worked, have ClockworkMod as recovery, accessible via Mobileuncle Tools), which was essentially a stock Kitkat rom made to work for the phone. Now I got sick of the ROM and recently saw the new EMUI version on Huawei's P8 Lite, so I figured I'd look around for a tailored ROM running that, and ended up at "jiayu-emui-3-0-stable" from Needrom.
What I did
1. I downloaded a ROM from Needrom with identifier "jiayu-emui-3-0-stable" (I can't post external links)
2. Backed up my important files following a guide from androidcentral titled "[Guide] How to Backup and Restore Apps and Data when installing new ROMs" that I can't link,and did a full backup using CWM
3. Placed the ZIP on my internal SD card, went into recovery, wiped data/cache (not dalvik, since it wasn't described in the instructions, I think this might be a probable cause) and installed the new ROM from ZIP
4. Rebooted the phone and now it's stuck in the boot loop I mentioned.
What the problem is
Bootloops aren't that much of a problem usually, except this one is... I can't get into recovery mode. From there on it'd be cake, since I made the right preparations, but I can't get into it. While connected to my PC it keeps powering on, showing a splash screen from Jiayu.es briefly (which shouldn't be present anymore) and powering off after 10 seconds, only to come back to the splash screen.
What I've tried
I've unplugged it, removed the battery, waited to get a full power cycle and tried to hold my buttons in these combinations: [power button + volume up], [power button + volume down] - but neither work. It just keeps going with the boot loop. I can succesfully power it down, and when I plug it in from there it shows the low battery image. At the moment of seeing that I thought I could connect to it using ADB / Fastboot, but no luck there either. It keeps saying no devices found, and with fastboot it keeps on <waiting for device>.
My questions
What exactly can I do if there is no way for me to get into recovery mode? Are there any alternatives? How can I get my device to be recognized by ADB? Is that even possible? Why is this bootloop any different from others?
Update from the massive Q&A thread:
ZipAddict said:
Is it booting up on its own too after being off? This happened to wifes phone and it turned out the power button was stuck. I took a pencil and hit the power button with the eraser a few times and it worked then. Her case mustve dislogded it. I will keep my fingers crossed for u. If not send me a private message and i will look for an answer tomorrow and get back with u
Click to expand...
Click to collapse
Thank you for the reply!
Yes, it does. I took the battery out and let it lay disassembled for a night, after which I cleaned it a little and re-inserted the battery. With the case back on, nothing happened, so the power button wasn't stuck for sure. When I powered it back on with the power button (no USB attached) it showed the emblem for ~8 seconds and powered off. It then buzzes to show it's powered on again and up comes the splash screen again. Could it be that the ROM was just a rebooting falsehood? Why would it disallow me getting into recovery mode? I really hope there is something that can still force the device into recovery mode / interact with it somehow while in this state.
Oh, I also tried to see if the volume down button was broken but all the contacts seem intact, plus, they worked an hour before I started switching roms.

Update to MOB30G - Failed and now can't boot?! - Please Help!

Hello All,
I have a completely stock (Not rooted, and bootloader is locked) Nexus 9 (wifi) that will no longer boot after trying to update to the latest security patch (MOB30G).
I received the notification that there was an update available for my Nexus 9 this weekend. It was functioning just fine, so I chose to download an install the update.
I let it do its thing, and some time during the process something went wrong. I came back to see the little android picture with red "!". There were no words or messages with the error picture.
When I rebooted, There was a momentary message that stated that, "Device is corrupt and cannot be trusted..." and "...press the power button to pause boot".
It then goes back to the little android picture with the red exclamation mark and says "No Command".
I am at a total loss at what to do. It was completely stock, never rooted or anything else and I was applying a factory update?
Please help!
-Jason
@Jsunn Try side-loading the OTA update again from recovery.
Instructions can be found here.
If that doesn't work, try side-loading the Android N OTA instead.
I just had to deal with this after the May OTA. My device was locked and ADB was not enabled but I was able to sideload the dev preview of Android N.
I used the info at this link: Search "Reset your Nexus device to factory settings"
Specifically these steps:
Option 2: Reset device in Recovery mode
If you can't open the Settings app because of device issues, you can use Recovery mode to factory data reset ("format") your device.
Tip: If your device becomes unresponsive at any point, you can restart it by holding down the Power button for several seconds.
After following all the Before you start steps above:
If your device is on, turn it off.
Press & hold the Volume down button. While holding Volume down, press & hold the Power button until the phone turns on. You'll see the word "Start" with an arrow around it.
Press the Volume down button until you highlight "Recovery mode."
Press the Power button to start recovery mode. You'll see an image of an Android robot with a red exclamation mark (you may also see "No command").
Press & hold the Power button. While holding Power, press the Volume up button once. Then release the Power button.
Press the Volume down button until you highlight "Wipe data/factory reset." Then press the Power button.
Press the Volume down button until you highlight "Yes" (or "Yes - delete all user data"). Then press the Power button to select it.
After the reset is complete, press the Power button to select "Reboot system now."
When you're done, restore your data.
My biggest issue was not realizing the second menu was available. After getting "No Command" the power and vol up buttons are what get you to where you can use adb to sideload even if you never unlocked your device. This might work with a normal marshmallow OTA (Search for "Factory Images for Nexus Devices") but I used the N preview 2 which can be found by searching for "volantis-npc91k"
This had me fuming for a few days... No way I was sending a nexus device back and paying shipping for bricking after a stock update.
NOTE: Sorry I had to remove the direct links. My profile doesn't have enough posts yet. Really dumb, but I get it. Hope this helps.
Thanks for your help. I will try it this week.
Pretty bummed about this, I didn't have a lot of stuff on there but don't like having to deal with this.
Do you know what could have caused it?
-J
Had same issu with May update and applied the N preview OTA (that's the only thing you can do on a locked bootloader).
Once booted in N preview, I've enrolled the device in the beta program, then retired. Few seconds after, I've received the downgrade OTA, and no more issue.
Before doing anything else, I've unlocked the bootloader so at least it if occurs again with the MOB30G, I will have some more access !
Jsunn said:
Thanks for your help. I will try it this week.
Pretty bummed about this, I didn't have a lot of stuff on there but don't like having to deal with this.
Do you know what could have caused it?
-J
Click to expand...
Click to collapse
Nobody knows what causes this, maybe a corrupted download of the OTA.
It happens to people's devices nearly every month when an OTA is available.
Try sideloading the failed OTA (linked above) again first before taking the Android N route.
Google Now provide full block level OTA images, so they can be sideloaded onto your device no matter what version your on.
https://developers.google.com/android/nexus/ota
Use the latest OTA image from that link, instead of sideloading the patching OTA zips.
I can't seem to sideload the package. My computer doesn't detect that a fastboot device in connected.
I am trying a factory reset now? If that doesn't work, I guess I can try the N preview? Other suggestions?
Thanks,
Jason
@Jsunn Make sure you have the correct drivers on your computer, Nexus Root Toolkit has a driver installation guide.
Check that your in fastboot mode and your device should show up in device manager as
Android Device - Android Bootloader Interface
@corkiejp, Thank you for the tip. That was it and I now am back up and running. I am back on the May 1 Security update. I'd really like to avoid having to do this again in the future. Do you have any suggestions? i.e. should I always sideload the update? Customer ROM etc?
Thanks,
-J
@Jsunn What was the trick? Reinstalling drivers, i Guess.
Remember to Enable OEM unlocking in developer options.
And if you have already factory reset? It might be a good time to Unlock Your bootloader with "fastboot oem unlock".
So if anything goes wrong in the future, you will have the option to flash factory images.
corkiejp said:
@Jsunn What was the trick? Reinstalling drivers, i Guess.
Remember to Enable OEM unlocking in developer options.
And if you have already factory reset? It might be a good time to Unlock Your bootloader with "fastboot oem unlock".
So if anything goes wrong in the future, you will have the option to flash factory images.
Click to expand...
Click to collapse
It was the drivers, I didn't think to check that the first time. I am going to unlock the book loader, I was thinking the exact same thing! I'm just glad to be back up and running.
-J

Categories

Resources