Database Users

How To: Restore Your 2013 Nexus 7 Back To Stock Using A Full Factory Image And Root I

Prerequisites
In order to complete the steps below, you need to have the Android SDK installed. The SDK contains the latest version of adb and fastboot, which you will need for flashing files and issuing commands. You will also need a MicroUSB cable to execute adb sideload, fastboot flash, and other commands. You also need to unlock your bootloader - a process that wipes your data.
Enable Developer options by going to the Settings -> About screen and tapping Build number until the OS unlocks the hidden Developer options menu. Now go to Developer options and make sure you have USB debugging turned on. For security purposes, you can turn it off after we're done.
To unlock the bootloader, if you haven't already done so:
Reboot into the bootloader by issuing an adb reboot bootloader command on your computer or holding VolDn+Power while booting (power off, hold VolDn, then hold Power).
Warning: This will wipe your data. Type in fastboot oem unlock on your computer. Agree to the unlock by selecting Yes on your tablet (VolUp, then Power).
You have now unlocked your bootloader (and the data partition was wiped clean). Verify by rebooting to the bootloader again and looking at Lock State.
wm_IMG_20130809_162939
The Steps
Download the full factory image corresponding to your exact model (for example, 2013 Nexus 7 Wi-Fi is razor), which includes the full system, bootloader, recovery, kernel (boot.img), and radio (radio not included for Wi-Fi-only variants). It's a clean slate for these components - they'll flash cleanly over anything you have now.
Unpack the tgz (tar/gz) archive into its own directory. I use Total Commander, but you can use any tool that reads gz and tar, like 7-Zip:
image
Proceed with this step if you want to keep your data intact. If you skip this step, your data will be wiped. With your favorite text editor, edit (be careful not to run it by accident instead of editing) flash-all.bat (if you're on Windows) or flash-all.sh (Mac, Linux) and remove "-w" from the fastboot update command. For example, if the line reads fastboot -w update image-razor-jss15j.zip, it should now read fastboot update image-razor-jss15j.zip. The -w option instructs fastboot to wipe data.
Reboot into the bootloader and run the appropriate flash-all script:
8-9-2013 5-20-09 PM
That's it, you're done. In my case, the Nexus 7 is now running stock Android 4.3:
wm_Screenshot_2013-08-09-16-32-51
Note: The above procedure restored the factory recovery, so if you want a custom one, you can flash one now (see below).
For better security, you can relock the bootloader by issuing fastboot oem lock while booted to the bootloader. This will, however, mean that if you ever want to do anything that requires an unlocked bootloader, you will lose your data in the unlock process.
Rooting
Rooting a Nexus 7 is very easy. It requires an unlocked bootloader and a custom recovery. I recommend using TWRP.
Flash TWRP from here (Reboot into the bootloader as before and then fastboot flash recovery FILENAME.img).
Reboot into recovery (adb reboot recovery or hold VolUp and Power while booting).
Flash SuperSU from this post. To do that, download the zip, then put the recovery into adb sideload mode (in TWRP, it's under Advanced), and then do adb sideload FILENAME.zip. I've seen some people complain that doing so via CWM doesn't work, but flashing through TWRP and selecting Fix Superuser Permissions at the end does the trick.
You should be rooted.
Reboot, head to the Play Store, and update SuperSU.
wm_IMG_20130809_172741
To see full article with pictures go to source : cloudandro.com//revu_2_en.html

Nexus 4 only with 5 GB partition!?

Hello gents,
After messing around with the fastboot yesterday i got back to stock Android and realised i have only a 5GB partition....
I formatted the phone and installed again the stock Rom but that didn't work.
Anybody as any idea on how to solve this problem? thanks:good:

Anyone?

Fix for 16GB N4 showing as 8GB
I just experienced the same exact problem, and wasn't able to find a solution until I followed this guide: http://forum.xda-developers.com/showthread.php?t=2033692
Make sure you have the latest occam image https://developers.google.com/android/nexus/images#occam
Use 7-Zip to extract the files from within the .tgz file, and then the .tar file.
Shift + Right Click in the folder to Open a Command Prompt, and run the following commands:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-mako-makoz20i.img
fastboot reboot-bootloader
fastboot -w update image-occam-jwr66y.zip

jsteg94 said:
I just experienced the same exact problem, and wasn't able to find a solution until I followed this guide: http://forum.xda-developers.com/showthread.php?t=2033692
Make sure you have the latest occam image https://developers.google.com/android/nexus/images#occam
Use 7-Zip to extract the files from within the .tgz file, and then the .tar file.
Shift + Right Click in the folder to Open a Command Prompt, and run the following commands:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-mako-makoz20i.img
fastboot reboot-bootloader
fastboot -w update image-occam-jwr66y.zip
Click to expand...
Click to collapse
Its a common error after flashing the factory images and all you usually have to do is this:
-Boot into STOCK RECOVERY (If you are running a custom recovery you must flash to stock)
-Clear cache
-Factory reset
which is right at the top of el daddy's thread

kzoodroid said:
Its a common error after flashing the factory images and all you usually have to do is this:
-Boot into STOCK RECOVERY (If you are running a custom recovery you must flash to stock)
-Clear cache
-Factory reset
which is right at the top of el daddy's thread
Click to expand...
Click to collapse
Thanks, kzoodroid. I didn't realize that you had to be in Stock Recovery. Every time I followed the above steps on el daddy's thread, I was using TWRP, which never solved the problem.

Well i´ve been trying and trying... its simple to follow the guide but wen i get to this step fastboot -w update image-occam-jdq39.zip the CMD crashes all the time...
I´ve restarted the computer and everything but it crashes always...
And also i can´t get into stock recovery... The droid with the triangle come up the i press power and then vol up but nothing happends...

Yeah, i think i just found a easy way to go around this problem!
Very simple:
1. After flashing the stock rom use Nexus Root Toolkit to do a OEM Lock
2. Run CMD fastboot and use this command: fastboot oem unlock. You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept.
3 Restart and that's it! Your back to 13GB again
Thanks to all for your help. I will share this info on El Daddy thread.

SWEagle said:
Yeah, i think i just found a easy way to go around this problem!
Very simple:
1. After flashing the stock rom use Nexus Root Toolkit to do a OEM Lock
2. Run CMD fastboot and use this command: fastboot oem unlock. You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept.
3 Restart and that's it! Your back to 13GB again
Thanks to all for your help. I will share this info on El Daddy thread.
Click to expand...
Click to collapse
I've had this issue come up more times than I can count, and just the other day I wasn't able to get back to the full storage allotment after several attempts following the steps to erase all the partitions and reflash. I did exactly what you did by flashing the factory images, re-locking the bootloader, then unlocking it again, and my storage was back to normal. I'm not exactly sure what happened, but I discovered this works, just as you did

hp420 said:
I've had this issue come up more times than I can count, and just the other day I wasn't able to get back to the full storage allotment after several attempts following the steps to erase all the partitions and reflash. I did exactly what you did by flashing the factory images, re-locking the bootloader, then unlocking it again, and my storage was back to normal. I'm not exactly sure what happened, but I discovered this works, just as you did
Click to expand...
Click to collapse
Cool! :laugh:

SWEagle said:
Well i´ve been trying and trying... its simple to follow the guide but wen i get to this step fastboot -w update image-occam-jdq39.zip the CMD crashes all the time...
I´ve restarted the computer and everything but it crashes always...
And also i can´t get into stock recovery... The droid with the triangle come up the i press power and then vol up but nothing happends...
Click to expand...
Click to collapse
With my phone I have to press power and volume+ a bunch of times to get it to finally go into stock recovery it never does it on the first few tries and can take a few minutes of playing to hit them perfectly to get it to open.

SWEagle said:
Yeah, i think i just found a easy way to go around this problem!
Very simple:
1. After flashing the stock rom use Nexus Root Toolkit to do a OEM Lock
2. Run CMD fastboot and use this command: fastboot oem unlock. You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept.
3 Restart and that's it! Your back to 13GB again
Thanks to all for your help. I will share this info on El Daddy thread.
Click to expand...
Click to collapse
Wow, that's actually a lot easier. Thanks for finding a simpler way, SWEagle! I'll try that next time.

jsteg94 said:
Wow, that's actually a lot easier. Thanks for finding a simpler way, SWEagle! I'll try that next time.
Click to expand...
Click to collapse
Instead of using the toolkit you probably could just use fastboot to lock the device too.
fastboot oem lock

kzoodroid said:
Instead of using the toolkit you probably could just use fastboot to lock the device too.
fastboot oem lock
Click to expand...
Click to collapse
I thought about that too. It might work. If it does it's even easier

Locked Boot loader, Encrypted Device, BootLoop, No Recovery/ Factor. HELP

So the title pretty much says it all..
I have a Nexus 6P
Last night It got stuck in a bootloop. The only access I have to the device is it will launch into the boot loader. But no options work, factory, recovery do not work. USB Debugging was turned off, OEM unlock is turned off, developer options are on. But I have zero access to the android only the boot loader screen. Fastboot does work but it gives me "DEVICE IS LOCKED" on most commands. Oh and the icing on top is I'm on Android N 7.0 beta.
I've ordered a replacement, but I have all my personal data on the phone. I'd like to either fix it and get it working so I can get all my stuff off it. Or at very least try to wipe the device.
Also Fastboot Format, erase, do not work. It says Locked Device. HELP PLEASE. I can answer any more questions.

can you adb pull and push files?
If so, on your Windows machine, type this:
Code:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys

It won't connect via ADB only Fastboot.
adb devices
List of devices attached
Wiltron said:
can you adb pull and push files?
If so, on your Windows machine, type this:
Code:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
Click to expand...
Click to collapse

Not sure if this will work, but try downloading the latest TWRP img file from their website, then running this command:
Code:
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
If you get it into recovery, then pull the files you need for a backup, and then use adb push to push a new ROM to the device.
Make sure you format all partitions/data.
Note: adb push should work better in recovery, vs. the command line that didn't work earlier.

What do you mean by "recovery doesn't work"? Please explain what happens when you boot into it.
Sent from my Nexus 5X using Tapatalk

an276123 said:
It won't connect via ADB only Fastboot.
adb devices
List of devices attached
Click to expand...
Click to collapse
Why not download stock Marshmallow and attempt to flash?
https://developers.google.com/android/nexus/images#angler
A locked bootloader should still allow you to flash a signed ROM.
An unlocked bootloader means you can boot and install anything.
Rule #1 If you are running *ANYTHING* other than an OTA, unlock the bootloader!
Unlocking the bootloader DOES NOT void the warranty.
Final note, it's encrypted. If you can't get into it, nobody interested in your data can.
Even if they can, it's block level encrypted. Who cares, no need to wipe.

SlimSnoopOS said:
What do you mean by "recovery doesn't work"? Please explain what happens when you boot into it.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
When I click down and then power on recovery it should go into the recovery. But instead it just gets back into an endless loop of starting.

tech_head said:
Why not download stock Marshmallow and attempt to flash?
https://developers.google.com/android/nexus/images#angler
A locked bootloader should still allow you to flash a signed ROM.
An unlocked bootloader means you can boot and install anything.
Rule #1 If you are running *ANYTHING* other than an OTA, unlock the bootloader!
Unlocking the bootloader DOES NOT void the warranty.
Final note, it's encrypted. If you can't get into it, nobody interested in your data can.
Even if they can, it's block level encrypted. Who cares, no need to wipe.
Click to expand...
Click to collapse
On a side note. I am running stock android N 7.0 and it was OTA. I just didn't think to unlock it since it was all done OTA.
Thats what I'm thinking too on the data.

Wiltron said:
Not sure if this will work, but try downloading the latest TWRP img file from their website, then running this command:
Code:
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
If you get it into recovery, then pull the files you need for a backup, and then use adb push to push a new ROM to the device.
Make sure you format all partitions/data.
Note: adb push should work better in recovery, vs. the command line that didn't work earlier.
Click to expand...
Click to collapse
When I try to run this I get this.
downloading 'boot.img'...
OKAY [ 0.397s]
booting...
FAILED (remote: unlock device to use this command)
finished. total time 0.421s

That means you need to unlock your bootloader, which should already be done, or if it's not, it will erase your internal storage.
You can unlock your bootloader, or try too, with
Code:
fastboot flashing unlock

Wiltron said:
That means you need to unlock your bootloader, which should already be done, or if it's not, it will erase your internal storage.
You can unlock your bootloader, or try too, with
Code:
fastboot flashing unlock
Click to expand...
Click to collapse
He said OEM unlock is turned off so that won't work.

So any luck to boot this sucker ? Don't even have stock recovery ..

have you tried "fastboot boot boot.img" from the correct factory image ?

Boot loop plus no recovery equals BLOD. Sorry but likely you are done.

Boot loop after Android O DP2 update

I installed Android O DP2 update via OTA yesterday. The phone updated, rebooted to the new build and restarted abruptly and since then has been stuck in a boot loop. The Google logo shows up, goes to the android animation step and then Google logo appears again.
I don't have bootloader unlocked, don't have TWRP and have done OTA updates. I am able to get into the stock recovery mode.
How do I fix this, i.e. make it work in any way without erasing the user data? I don't mind extreme steps (without erasing user data) because I was planning to reflash 7 with unlocking & rooting today.

Try to wipe cache from recovery - in recovery hold volume-down and select "Wipe cache partition". Should do the trick

I tried, didn't work. Had to factory reset in the end. Also opted out of beta

I just read that some people that took the update from certain builds had boot loops due to the update only replacing part of the OS but leaving the 7.x.x system in place causing it to boot loop. I think it was like on android authority or something like that.
Sent from my Nexus 6P using XDA-Developers Legacy app

I have similar problem. Phone became stuck at Google logo and bootloop. I didn't have OEM unlock and debugged enable when phone was working. Now I'm stuck because It cannot flash with any factory image rom. Anyone with solution, please help. Thanks

citifone said:
I have similar problem. Phone became stuck at Google logo and bootloop. I didn't have OEM unlock and debugged enable when phone was working. Now I'm stuck because It cannot flash with any factory image rom. Anyone with solution, please help. Thanks
Click to expand...
Click to collapse
You can unlock your bootloader to flash a stock ROM. Do you need the steps?
---------- Post added at 09:54 AM ---------- Previous post was at 09:38 AM ----------
citifone said:
I have similar problem. Phone became stuck at Google logo and bootloop. I didn't have OEM unlock and debugged enable when phone was working. Now I'm stuck because It cannot flash with any factory image rom. Anyone with solution, please help. Thanks
Click to expand...
Click to collapse
To flash a system image:
Download the latest system image for your Nexus 6p, then unzip it to a safe directory.
https://dl.google.com/dl/android/aosp/angler-n2g47o-factory-dc258043.zip
or Download any of your choice from here
https://developers.google.com/android/images
Connect your device to your computer over USB.
Start the device in fastboot mode with one of the following methods:
adb tool
http://developer.android.com/tools/help/adb.html
Using a key combo: Turn the device off, then turn it on and immediately hold down the relevant key combination for your device.
POWER BUTTON + VOLUME DOWN BUTTON
Click to expand...
Click to collapse
If necessary, unlock the device's bootloader using one of the following methods:
Code:
fastboot flashing unlock
If you are updating an older device, run this command:
Code:
fastboot oem unlock
The target device will show you a confirmation screen. (This erases all data on the target device.)
Open a terminal and navigate to the unzipped system image directory or Open a command prompt from within your System image folder (navigate to where you have flash-all.bat located on your PC, shift + right click anywhere within that folder, select open command prompt here
Execute the flash-all script.
Code:
fastboot flash-all.bat
This script installs the necessary bootloader, baseband firmware(s), and operating system.
Once the script finishes, your device reboots. You should now lock the bootloader for security:
Start the device in fastboot mode again, as described above.
Execute:
Code:
fastboot flashing lock
or, for older devices, run:
Code:
fastboot oem lock
Locking bootloader will wipe the data on some devices. After locking the bootloader, if you want to flash the device again, you must run fastboot oem unlock again, which will wipe the data.

Mavelos said:
You can unlock your bootloader to flash a stock ROM. Do you need the steps?
---------- Post added at 09:54 AM ---------- Previous post was at 09:38 AM ----------
To flash a system image:
Download the latest system image for your Nexus 6p, then unzip it to a safe directory.
https://dl.google.com/dl/android/aosp/angler-n2g47o-factory-dc258043.zip
or Download any of your choice from here
https://developers.google.com/android/images
Connect your device to your computer over USB.
Start the device in fastboot mode with one of the following methods:
adb tool
http://developer.android.com/tools/help/adb.html
Using a key combo: Turn the device off, then turn it on and immediately hold down the relevant key combination for your device.
If necessary, unlock the device's bootloader using one of the following methods:
Code:
fastboot flashing unlock
If you are updating an older device, run this command:
Code:
fastboot oem unlock
The target device will show you a confirmation screen. (This erases all data on the target device.)
Open a terminal and navigate to the unzipped system image directory or Open a command prompt from within your System image folder (navigate to where you have flash-all.bat located on your PC, shift + right click anywhere within that folder, select open command prompt here
Execute the flash-all script.
Code:
fastboot flash-all.bat
This script installs the necessary bootloader, baseband firmware(s), and operating system.
Once the script finishes, your device reboots. You should now lock the bootloader for security:
Start the device in fastboot mode again, as described above.
Execute:
Code:
fastboot flashing lock
or, for older devices, run:
Code:
fastboot oem lock
Locking bootloader will wipe the data on some devices. After locking the bootloader, if you want to flash the device again, you must run fastboot oem unlock again, which will wipe the data.
Click to expand...
Click to collapse
Thanks for your reply..But you can only do this only if you have an unlocked bootloader and debugged mode on. I didn't have either so it won't allow to flash with locked bootloader.

citifone said:
Thanks for your reply..But you can only do this only if you have an unlocked bootloader and debugged mode on. I didn't have either so it won't allow to flash with locked bootloader.
Click to expand...
Click to collapse
Exactly why i posted that. You can unlock your bootloader without turning USB debugging ON. Just Boot up with the POWER + VOLUME down Combination and use the bootloader unlock command in my previous post.

FAILED (remote: OEM unlock is not allowed)
Mavelos said:
Exactly why i posted that. You can unlock your bootloader without turning USB debugging ON. Just Boot up with the POWER + VOLUME down Combination and use the bootloader unlock command in my previous post.
Click to expand...
Click to collapse
What I think he is telling you and the same problem I have, when We try the unlock command we are getting this error :
FAILED (remote: OEM unlock is not allowed)
any suggestions ?
Regards.

Lord Aguacate said:
What I think he is telling you and the same problem I have, when We try the unlock command we are getting this error :
FAILED (remote: OEM unlock is not allowed)
any suggestions ?
Regards.
Click to expand...
Click to collapse
Yes, I got the same error. Again, it's because of bootloader locked and debug is off. Any other ways to unlock or flash this phone?

citifone said:
Yes, I got the same error. Again, it's because of bootloader locked and debug is off. Any other ways to unlock or flash this phone?
Click to expand...
Click to collapse
To unlock you first need to have ticked the allow OEM unlock from developer menu within the OS. It won't work otherwise.

Lord Aguacate said:
What I think he is telling you and the same problem I have, when We try the unlock command we are getting this error :
FAILED (remote: OEM unlock is not allowed)
any suggestions ?
Regards.
Click to expand...
Click to collapse
You'll have to use a Rescue OTA
Download the latest Nexus 6P OTA from here https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
STEPS TO FOLLOW
To apply an OTA update image:
Download the appropriate update image for your device below.
https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
Boot into your recovery from fastboot
use the key combination for your device
Code:
POWER + VOLUME DOWN
and then select the Recovery option from the bootloader menu. The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.
Hold the Power button and press Volume Up once, and a menu will appear. Select the option Apply update from ADB.
Run the following command on your PC:
Code:
adb devices
and check that your device shows up with "sideload" next to its name.
Run the following command:
Code:
adb sideload ota_file.zip
where ota_file.zip is the name of the file you have downloaded and verified.
Once the update finishes, reboot the phone by choosing Reboot system now.

Mavelos said:
You'll have to use a Rescue OTA
Download the latest Nexus 6P OTA from here [="https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip"]https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
STEPS TO FOLLOW
To apply an OTA update image:
Download the appropriate update image for your device below.
="https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip"]https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
Boot into your recovery from fastboot
use the key combination for your device
Code:
POWER + VOLUME DOWN
and then select the Recovery option from the bootloader menu. The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.
Hold the Power button and press Volume Up once, and a menu will appear. Select the option Apply update from ADB.
Run the following command on your PC:
Code:
adb devices
and check that your device shows up with "sideload" next to its name.
Run the following command:
Code:
adb sideload ota_file.zip
where ota_file.zip is the name of the file you have downloaded and verified.
Once the update finishes, reboot the phone by choosing Reboot system now.
Click to expand...
Click to collapse
Dear Mavelos,
I already tried that and the installation was successful, but my first problem still there, when I installed the Android O Beta, the touch of my screen stop working after the 2nd day of installation.
Now I don't know if this is a problem with Android O or just a coincidence and the hardware its broken.
I went to a lot of forums but nobody its talking about that (Touch Screen not working)
Did You guys hear anything about it?

Mavelos said:
You'll have to use a Rescue OTA
Download the latest Nexus 6P OTA from here https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
STEPS TO FOLLOW
To apply an OTA update image:
Download the appropriate update image for your device below.
https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
Boot into your recovery from fastboot
use the key combination for your device
Code:
POWER + VOLUME DOWN
and then select the Recovery option from the bootloader menu. The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.
Hold the Power button and press Volume Up once, and a menu will appear. Select the option Apply update from ADB.
Run the following command on your PC:
Code:
adb devices
and check that your device shows up with "sideload" next to its name.
Run the following command:
Code:
adb sideload ota_file.zip
where ota_file.zip is the name of the file you have downloaded and verified.
Once the update finishes, reboot the phone by choosing Reboot system now.
Click to expand...
Click to collapse
I have the same problem as others, stuck in a bootloop and had not enabled unlock in dev options. I can get to bootloader but not recovery mode (bootloops when I select this). I would love to try this OTA side load, but I can't see my device in adb. I can see it however in fastboot. Not sure how to get it up in adb....
Any help would be much appreciated.

scorneil said:
I have the same problem as others, stuck in a bootloop and had not enabled unlock in dev options. I can get to bootloader but not recovery mode (bootloops when I select this). I would love to try this OTA side load, but I can't see my device in adb. I can see it however in fastboot. Not sure how to get it up in adb....
Any help would be much appreciated.
Click to expand...
Click to collapse
If you get a bootloop when selecting recovery, try rebooting to recovery with fastboot
Code:
fastboot reboot recovery
if that doesn't work, then i think your device is bricked.
---------- Post added at 06:19 AM ---------- Previous post was at 06:16 AM ----------
Lord Aguacate said:
Dear Mavelos,
I already tried that and the installation was successful, but my first problem still there, when I installed the Android O Beta, the touch of my screen stop working after the 2nd day of installation.
Now I don't know if this is a problem with Android O or just a coincidence and the hardware its broken.
I went to a lot of forums but nobody its talking about that (Touch Screen not working)
Did You guys hear anything about it?
Click to expand...
Click to collapse
If your touch screen isn't working, it might be related to the Android O Beta you flashed. Can you boot the phone up? If you have an OTG cable, connect a mouse to your phone. Turn on OEM unlocking in developer options. Do a factory reset.

i have the same problem with this, and i cannot unlock it too, is there anyway to unlock this phone?

OTG works Perfect! But.....
Mavelos said:
If you get a bootloop when selecting recovery, try rebooting to recovery with fastboot
Code:
fastboot reboot recovery
if that doesn't work, then i think your device is bricked.
---------- Post added at 06:19 AM ---------- Previous post was at 06:16 AM ----------
If your touch screen isn't working, it might be related to the Android O Beta you flashed. Can you boot the phone up? If you have an OTG cable, connect a mouse to your phone. Turn on OEM unlocking in developer options. Do a factory reset.
Click to expand...
Click to collapse
So I Follow your suggestion and I bought the OTG adapter, works perfectly I unlocked the bootloader from the developers options, did a factory restore with a previous image, etc.... Touch still not working, I'm starting to believe this a hardware problem with the screen.... Bad Luck maybe, I don't know! ..... I will have to buy that expensive screen ($140).
Anyway thanks for the help...
Regards

Lord Aguacate said:
So I Follow your suggestion and I bought the OTG adapter, works perfectly I unlocked the bootloader from the developers options, did a factory restore with a previous image, etc.... Touch still not working, I'm starting to believe this a hardware problem with the screen.... Bad Luck maybe, I don't know! ..... I will have to buy that expensive screen ($140).
Anyway thanks for the help...
Regards
Click to expand...
Click to collapse
You're welcome. Get your phone fixed and return to the flashing community.

last night i my phone inside my freezer hehehe and this morning i tried to turn it on, and it pass the google logo boot normally but it only lasted for a few minute and then turn off and bootloop again. so i guess my 6p has a hardware faulty

Help Wiping (or Unlocking) With a Broken Screen

The screen on my Stock unrooted & locked Nexus 6P is completely non-functional (shattered, not displaying anything, likely not responding to touch) and I'd like to wipe it before disposing of it.
I'm able to blindly navigate to the bootloader but I'm having trouble unlocking for the purposes of
Code:
fastboot erase system -w
.
Process
Boot into bootloader then issue the unlock command:
Code:
fastboot flashing unlock
Because I can't see the screen, I'm assuming pressing up or down will select 'Yes' and power will confirm it.
Either way (up+pwr or down+pwr or just pwr) the phone restarts and I let it sit for a while.
I reboot into the bootloader but the unlocked variable returns no.
I figured the closest analog would be to reflash via
Code:
fastboot -w update "image.zip"
, which will wipe userdata and cache - is that sufficient?

Don't worry....just download and install Nexus toolkit or do it manually by downloading Adb fastboot minimal <10mb size.
First, install driver for flashing firmware.
Reboot to bootloader,
Connect to pc,it will make sound if connected.
Now,put system.img to adb minial folder.
Right click and open cmd in adb minimal folder.
Type adb fastboot flash system system.img
Then,in the middle disconnect from pc.since,it will corrupt your system file.Do this for 2-3 times,that is flashing system.img and disconnecting in the middle to insure that system file have corrupted.
Then,at last flash system.img till end to complete.
Voila...you will have a factory reset phone.
I did this trick before selling my galaxy s5 broken display phone.
When buyer put display in front of me,it was factory reset.

Phylum said:
The screen on my Stock unrooted & locked Nexus 6P is completely non-functional (shattered, not displaying anything, likely not responding to touch) and I'd like to wipe it before disposing of it.
I'm able to blindly navigate to the bootloader but I'm having trouble unlocking for the purposes of
Code:
fastboot erase system -w
.
Process
Boot into bootloader then issue the unlock command:
Code:
fastboot flashing unlock
Because I can't see the screen, I'm assuming pressing up or down will select 'Yes' and power will confirm it.
Either way (up+pwr or down+pwr or just pwr) the phone restarts and I let it sit for a while.
I reboot into the bootloader but the unlocked variable returns no.
I figured the closest analog would be to reflash via
Code:
fastboot -w update "image.zip"
, which will wipe userdata and cache - is that sufficient?
Click to expand...
Click to collapse
Run a drill bit through the upper 1/4 of the screen and through the motherboard then dispose.

hawkswind1 said:
Run a drill bit through the upper 1/4 of the screen and through the motherboard then dispose.
Click to expand...
Click to collapse
Lol sounds good to me!
zameer hassan said:
Don't worry....just download and install Nexus toolkit or do it manually by downloading Adb fastboot minimal <10mb size.
First, install driver for flashing firmware.
Reboot to bootloader,
Connect to pc,it will make sound if connected.
Now,put system.img to adb minial folder.
Right click and open cmd in adb minimal folder.
Type adb fastboot flash system system.img
Then,in the middle disconnect from pc.since,it will corrupt your system file.Do this for 2-3 times,that is flashing system.img and disconnecting in the middle to insure that system file have corrupted.
Then,at last flash system.img till end to complete.
Voila...you will have a factory reset phone.
I did this trick before selling my galaxy s5 broken display phone.
When buyer put display in front of me,it was factory reset.
Click to expand...
Click to collapse
Excellent excellent excellent advice - much appreciated.

You need to have USB debugging enabled btw to unlock your phone and issue those fastboot commands.