Database Users

Broken touch screen, need to get Stock

The touchscreen on my Fire stopped working today. I already talked to Amazon and am getting a replacement, but I want to revert back to stock before sending it in. I've seen ways to do this with TWRP, but I don't have a touchscreen to use TWRP, or any recovery for that matter, with.
Is there any way to do this?
I do have full ADB and Fastboot access, with FireFireFire working, but do not have a currently working rom installed (I was on CM9, and it won't go past the boot screen).

drk.hd said:
The touchscreen on my Fire stopped working today. I already talked to Amazon and am getting a replacement, but I want to revert back to stock before sending it in. I've seen ways to do this with TWRP, but I don't have a touchscreen to use TWRP, or any recovery for that matter, with.
Is there any way to do this?
I do have full ADB and Fastboot access, with FireFireFire working, but do not have a currently working rom installed (I was on CM9, and it won't go past the boot screen).
Click to expand...
Click to collapse
There is a way to do this with adb... I just do not know the proper commands. Sorry

Does installing a custom rom void the warranty? Seems like it would be BS for Amazon not to honor it when it's apparently a hardware related issue.

sengwall said:
Does installing a custom rom void the warranty? Seems like it would be BS for Amazon not to honor it when it's apparently a hardware related issue.
Click to expand...
Click to collapse
No, I don't think it does, but I'd rather not take the chance.

drk.hd said:
No, I don't think it does, but I'd rather not take the chance.
Click to expand...
Click to collapse
YES! It absolutely does. The second the device was rooted it broke warranty.
Sent from my myTouch_4G_Slide using XDA App

The same thing actually happened to me earlier today. I was just browsing some sites on the ICS rom when it just stopped responding. I couldn't get it to recognize any touches even after a bunch of reboots, so I just figured it to be some bug that hadn't been squashed yet. When I dropped down to recovery and saw the same issue, I knew I had a real problem.
Hoping against hope, I tried both CWMR and TWRP on it and got no results. Like you, I figured it would have to go back to Amazon, so I started searching for a way to get it back to stock... nothing obvious jumped out at me because everything is written with access to recovery in mind... which doesn't help.
So, I started reading about adb and going through the built-in help. As I was familiarizing myself with some basic adb commands and options, I left TWRP open in front of me. I don't know how long I had it that way when I mindlessly tapped on the screen and thought I saw it flicker. Yes! I had pressed the Wipe button and it had taken me to that section. It's been working fine ever since.
I'm not claiming I did anything and I don't have a how-to on how to fix it, but it couldn't hurt to just leave the thing running in recovery for a while and see if the touchscreen comes back to life for you too.
Still, I'd love to see someone with more adb knowledge provide a simple tutorial on how to get it back to stock without access to recovery. I'm sure it would be helpful to someone in the future... maybe even me if the same problem comes up again.
Best of luck to you.

Just ignore my comment
Sent from my Amazon Kindle Fire using Tapatalk

If your on the rooted stock rom you could always wait until Amazon pushing the next OTA

You will have to make a fastboot image and flash that with fastboot. But before you create the image, you will have to create all the appropriate symlinks. Then you run...
Code:
make_ext4fs -l 512m -a system -s /path/to/fastboot_system.img /path/to/system_folder
That will create the fastboot image. Then when FFF gives you fastboot access, you run...
Code:
fastboot flash system fastboot_system.img
You will also need a fastboot image for recovery and the bootloader.

Isn't there any easy way like with my desire, simple ruu.
Or hasn't anyone created these images to flash. I also need to get back to stock everything and send it to amazon, my wifi gets error after some period of time and some times when screen goes off, try'd 3 roms and stock.

There is a way to tell the device to install /sdcard/update.zip via shell commands. I forget what they are tho. Something about the extendedcommands. If I have time tomorrow I'll look it up.

here it is:
http://www.theandroidsoul.com/kindle-fire-stock-rom-installation-guide/

b63 said:
here it is:
http://www.theandroidsoul.com/kindle-fire-stock-rom-installation-guide/
Click to expand...
Click to collapse
Thanks for the link. I'm back on this thread because I think my Kindle Fire touchscreen is now dead for good. However, those instructions do not work as-is because you need to press a button on the screen to tell the Kindle Fire to allow the host to mount it as a USB Mass Storage device. Although those instructions don't get you all the way there, I was able to use the core idea to get my Kindle Fire back to stock. So, many thanks for pointing me in the right direction.
On top of the touchscreen not working, I ended up partially bricking the device trying to find a way to flash it back to stock, so I had also posted in the Unbricking thread. I posted my solution there....
http://forum.xda-developers.com/showpost.php?p=23226260&postcount=701
Odds are, if you have a device that is booting correctly, you will be able to ignore steps 3 and 4 and get it booting back to stock. I do have a couple of other suggestions... Leave your USB cable hooked up to the Kindle Fire as it boots into stock for the first time. This is the only time that it will automatically mount the /sdcard to your computer and you will have a chance to reclaim (and delete) all the files stored there. You can also do something like 'adb pull /sdcard C:\sdcard' before you flash. Also, depending on what ROM and apps you were using before starting the process, you might want to delete your user data and reset the device to factory defaults. You can do this with 'fastboot erase userdata' and the next time you start the device, you'll get a warning that it's about to reset. Hit the power button and you should have a clean, fresh from the factory Kindle fire... albeit with a broken touchscreen. Good luck!

After several failed attempts to follow this guide (no offense to posters; I appreciate your contributions), I found this to be the simplest method.
http://stackoverflow.com/questions/10817721/wipe-data-factory-reset-through-adb
Download stock update, then it's basic procedure in adb:
adb push C:/update.zip /sdcard/update.zip
adb shell
recovery --wipe_data
After reboot, go back into to adb shell and do "recovery--update_package=/sdcard/update.zip"
Factory reset, etc. and you're good to go.

[Q] Nexus 10 stuck in boot after attempting root

Hi.
So, a quick overview. My laptop suddenly stopped recognizing my Nexus 10 while in the midst of transferring some files over. I decided to finally root. I used the cf-autoroot tool for Nexus 10 Lollipop. The last step of the rooting involves an automatic reboot. Now my Nexus 10 is stuck in the boot.
Details:
theunlockr (DOT) com/2014/11/22/how-to-root-the-nexus-10-on-android-5-0/
That is the guide I used, including the linked cf-autoroot. Sorry for the formatting, I don't have enough posts to post links.
My Nexus 10 is stuck on the step where it shows the four circles moving around. Not sure if that's important.
The cf-autoroot appeared to work successfully except for a piece in the middle that reads:
Same problem. The procedure seemed to go well, except maybe the mounting failed? It says:
Mounting...
- System
- Cache
--- Fail
I tried using the tool several times on two computers, and did my best to update drivers directly from Google (it appears the drivers are all up to date).
My Nexus 10 was on Lollipop. As far as I know, it was up to date, so I think that means it was on 5.0.1
Help?

Hello autoroot is no longer required. Supersu from recovery is enough.
You could just reflash original kernel
Does
Fastboot boot boot. Img works? It boots on the given image without flaging. The boot image is located in the archive to update
Sent from my Xiaomi MI2s

Khaon said:
Hello autoroot is no longer required. Supersu from recovery is enough.
You could just reflash original kernel
Does
Fastboot boot boot. Img works? It boots on the given image without flaging. The boot image is located in the archive to update
Sent from my Xiaomi MI2s
Click to expand...
Click to collapse
This is what I have come here to find out. I'm receiving my Nexus 10 in the mail today. I'm familiar with Nexus devices so I just assume everything is the same with the Nexus 10. But I know since Lollipop came out, there have been changes to how to root on certain devices. Are you saying that everything has been fixed to where I can just install the latest TWRP and flash the latest beta SuperSU on stock ROM and I will be good? If so, then it's the same as my Nexus 5 so I shouldn't have any issues.

jsgraphicart said:
This is what I have come here to find out. I'm receiving my Nexus 10 in the mail today. I'm familiar with Nexus devices so I just assume everything is the same with the Nexus 10. But I know since Lollipop came out, there have been changes to how to root on certain devices. Are you saying that everything has been fixed to where I can just install the latest TWRP and flash the latest beta SuperSU on stock ROM and I will be good? If so, then it's the same as my Nexus 5 so I shouldn't have any issues.
Click to expand...
Click to collapse
Yep, just flash once SU through twrp(in order to get the su binary in the system partition) and then you can use play store to update the binary and the program itself.
CM12 has built in su and nighties are official now.

Khaon said:
Yep, just flash once SU through twrp(in order to get the su binary in the system partition) and then you can use play store to update the binary and the program itself.
CM12 has built in su and nighties are official now.
Click to expand...
Click to collapse
Thanks. I just wanted to double check before I went jumping into it. I'm looking forward to tinkering with it when I get home from work.

Khaon said:
Yep, just flash once SU through twrp(in order to get the su binary in the system partition) and then you can use play store to update the binary and the program itself.
CM12 has built in su and nighties are official now.
Click to expand...
Click to collapse
So I attempted to do all this when I got home yesterday. I found that after unlocking the bootloader, I got stuck in a boot loop. After doing some research I found that this has been an issue with the Nexus 10. Is there a reason for this? I read that locking the bootloader again fixed it, which it did. But I didn't want it locked. So I researched more and found that a a factory reset in stock recovery would fix it. I still had a boot loop. I managed to somehow get everything straightened out with a series of random tries and after installing TWRP and rooting and, again, getting the boot loop I attempted to go back into recovery but accidentally did a simple restart. For some reason, it booted right up after the restart so now I think everything is fine. But why is the Nexus 10 being so difficult? I never had these issues with other Nexus devices. Maybe some of this info will help the OP as well.

Hm unlocking the bootloader does erase whole content but I guess you are already aware of that.
How long did you wait? First boot can take ages much longer than before.
I never had any issues and I have my bootloader unlocked

Khaon said:
Hm unlocking the bootloader does erase whole content but I guess you are already aware of that.
How long did you wait? First boot can take ages much longer than before.
I never had any issues and I have my bootloader unlocked
Click to expand...
Click to collapse
I let it sit for a while. I own a Nexus 5 and I'm familiar with the long first boot. It just seemed like a long time to me. I thought maybe since it was a two year old device that it may take longer. The device is new to me so I'm not familiar with boot times and all that are specific to it yet. But compared to the boot time after I relocked the boot loader, there was a big difference. After re-locking, it booted up in about a minute or two. Flashing TWRP even seemed to mess up some stuff. I think it may have deleted the OS or something. It couldn't mount anything afterwards and even selecting reboot boot loader gave me the prompt that there was no OS installed. So I flashed the system.img, cache.img and userdata.img manually. Which seemed to fix it. And even after I got everything straightened out, it boot up in about a minute or two again. The only time I had issues with getting it to boot is unlocking the boot loader coming from complete stock.

nexus 10 stuck on bootload up
jsgraphicart said:
I let it sit for a while. I own a Nexus 5 and I'm familiar with the long first boot. It just seemed like a long time to me. I thought maybe since it was a two year old device that it may take longer. The device is new to me so I'm not familiar with boot times and all that are specific to it yet. But compared to the boot time after I relocked the boot loader, there was a big difference. After re-locking, it booted up in about a minute or two. Flashing TWRP even seemed to mess up some stuff. I think it may have deleted the OS or something. It couldn't mount anything afterwards and even selecting reboot boot loader gave me the prompt that there was no OS installed. So I flashed the system.img, cache.img and userdata.img manually. Which seemed to fix it. And even after I got everything straightened out, it boot up in about a minute or two again. The only time I had issues with getting it to boot is unlocking the boot loader coming from complete stock.
Click to expand...
Click to collapse
I getting the exact same thing after following instructions to root the machine
I'm not the most experience but I did my nexus 4 & 7 on 4.4.4. now on this 5.0 it seemed a lot hard this time around
I left it on boot load up screen for 3hrs and its still going round? what do I do?
Quick update: I press power +vol up + down and it comes up with the screen saving its unlocked. but the recovery mode just comes up with a android and red exclamation mark.
please help?
regards
Tom

tomistrouble said:
I getting the exact same thing after following instructions to root the machine
I'm not the most experience but I did my nexus 4 & 7 on 4.4.4. now on this 5.0 it seemed a lot hard this time around
I left it on boot load up screen for 3hrs and its still going round? what do I do?
Quick update: I press power +vol up + down and it comes up with the screen saving its unlocked. but the recovery mode just comes up with a android and red exclamation mark.
please help?
regards
Tom
Click to expand...
Click to collapse
Once you get in recovery mode with the android and the red explanation mark, hit all three buttons (Vol up , down and power) until (It can be tricky keep trying) you get a menu. Then use the volume buttons to select "Wipe Data/Factory rest" let it do its thing and reboot. Allow it to boot for 5-10 minutes.
Good luck

Nexus 6p stuck on Google logo

I need your help, after upgrading to 7.1.1 the phone is dialed and restarted all the time in this way.
I would appreciate a solution, I leave an exact example of what happens to me.
OEM is not unlocked and debugging mode either because I can not start the phone
My problem is that it does not unlock OEM and I was not active debugging, the phone just let me enter Fastboot but at the time of choosing RECOVERY it restarts

emmafer44 said:
I need your help, after upgrading to 7.1.1 the phone is dialed and restarted all the time in this way.
I would appreciate a solution, I leave an exact example of what happens to me.
OEM is not unlocked and debugging mode either because I can not start the phone
Click to expand...
Click to collapse
Dude try Nexus toolkit my Wugfresh (NRT Toolkit) you have to boot to bootloader and use the application to clean install

I have this same problem. flashed MegaPixel6P, tried using the camera, and then my phone shut off and just keeps rebooting. i think /data and /system are corrupted. any attempt to nandroid backup or restore fails and causes TWRP to reboot.

Alot of users are facing this bootloop issue. So far no one has been able to figure out a pattern that will give us insight into what kind of devices might be affected by this issue. I have created this survey on GoogleForums so far there are very few responses. Please participate to help the community figure out the probable cause for this bootloop
https://docs.google.com/forms/d/1nGAVdnjbkOE1ohvZvqbntb_7afT4p2OzbFIJjJWiy9Q/edit?c=0&w=1
BTW what's your phone's manufacturing date? were you using Magisk or SuHide?

Dadud said:
I have this same problem. flashed MegaPixel6P, tried using the camera, and then my phone shut off and just keeps rebooting. i think /data and /system are corrupted. any attempt to nandroid backup or restore fails and causes TWRP to reboot.
Click to expand...
Click to collapse
If you can get to TWRP, you can just reflash via fastboot (or use NRT). You may be able to apply your TWRP backup afterwards if it is not corrupted.
As for OP, if the bootloader is locked, and "Allow OEM Unlock" is toggled off, your options are slim to none. If this setting was enabled before upgrading then it is still enabled. If it was not, you cannot unlock the bootloader.

v12xke said:
If you can get to TWRP, you can just reflash via fastboot (or use NRT). You may be able to apply your TWRP backup afterwards if it is not corrupted.
As for OP, if the bootloader is locked, and "Allow OEM Unlock" is toggled off, your options are slim to none. If this setting was enabled before upgrading then it is still enabled. If it was not, you cannot unlock the bootloader.
Click to expand...
Click to collapse
Ive tried literally every fix, its dead jim.

Dadud said:
Ive tried literally every fix, its dead jim.
Click to expand...
Click to collapse
Have you tried FORMATTING boot, system, data & vendor and then reflash? Format, not erase/wipe. Move your TWRP backup off to PC and try that. If you are rusty in ADB/Fastboot, then use NRT to do same in advanced tools. If you have a working recovery and your bootloader is unlocked, I would not give up yet. Good luck!

Dadud said:
I have this same problem. flashed MegaPixel6P, tried using the camera, and then my phone shut off and just keeps rebooting. i think /data and /system are corrupted. any attempt to nandroid backup or restore fails and causes TWRP to reboot.
Click to expand...
Click to collapse
Yeah your problem is a bit different that others and it's worth investigating.
To verify your complete emmc, you could try this command in twrp -> advanced settings -> terminal.
dd if=/dev/block/mmcblk0 of=/dev/null
Basically doing a read test by copying the complete mmc to the void. It should give you a status at the end that you can post here.
By the way, the recommended factory flashing is by using flash-all script that is inside the factory image itself. And you need the latests android SDK.

rchtk said:
Yeah your problem is a bit different that others and it's worth investigating.
To verify your complete emmc, you could try this command in twrp -> advanced settings -> terminal.
dd if=/dev/block/mmcblk0 of=/dev/null
Basically doing a read test by copying the complete mmc to the void. It should give you a status at the end that you can post here.
By the way, the recommended factory flashing is by using flash-all script that is inside the factory image itself. And you need the latests android SDK.
Click to expand...
Click to collapse
nope. i enter the command and it does nothing for about a minute before turning itself off
also, im not some complete n00b, so trust me when i say i've tried everything. any time i restore a backup, once it starts applying just /data or /system it'll shut off and bootloop without finishing.

Dadud said:
nope. i enter the command and it does nothing for about a minute before turning itself off
also, im not some complete n00b, so trust me when i say i've tried everything. any time i restore a backup, once it starts applying just /data or /system it'll shut off and bootloop without finishing.
Click to expand...
Click to collapse
You never know the level of the person you're talking about eh. Just tought you hadn't tried the dd.
So dd shutting down before completing wasn't expected but now if I read again your posts, you said doing a photo shuts down the phone and that's quite typical of power related problems. Sh*t.
Could be the battery not holding discharge. Can the device stay in twrp with screen off? Did you try to let it fully discharge and charge it with a slow charge?
There are a lot of information in /sys/ or dmesg but it won't solve your issue.
Still under warranty?

Dadud said:
nope. i enter the command and it does nothing for about a minute before turning itself off
also, im not some complete n00b, so trust me when i say i've tried everything. any time i restore a backup, once it starts applying just /data or /system it'll shut off and bootloop without finishing.
Click to expand...
Click to collapse
Forget restoring your backup for now. You're not a noob, so transfer your TWRP backup to PC, then FORMAT each partition first, including userdata and then reflash using a Google Imagehere. Ensure you are using the latest version of ADB/Fastboot. You didn't mention you have already attempted to Fastboot flash the NMF26F image. What was your result then? The reason I'm asking is that the Google script erases the partitions- does not format, but running the script will tell you which partition failed during writing.

Huawei Customer Service!!
Had the exact same problem creep up on me this past weekend. I ended up calling Huawei and they are doing a free warranty repair on my phone even though I'm almost two months out of warranty.

Make sure you are on SDK 25, I had the problem synonymous. I have been hunted at Huawei and only when I had already given it I realized that I was not on SDK 25 and I know of some others that was the reason with most.
Whether it was the reason with me, I know tomorrow, the device is back and can be picked up,

Tylog said:
Make sure you are on SDK 25...
Click to expand...
Click to collapse
Yes, the latest ADB / Fastboot is required. The rest of the SDK is not mandatory. You can get a minimalist ADB-Fastboot-Driver install from an XDA dev here.
Also, TWRP updated for Angler recently here. This update solved a persistent backup problem I had with the previous v3.0.2-2

bought it second hand, and the previous owner bought it at launch, so im just a month or so out of warranty. im trying to get the original receipt to attempt to RMA it. Huawei's IMEI lookup says its under warranty till april 4th next year.

Tylog said:
Make sure you are on SDK 25, I had the problem synonymous. I have been hunted at Huawei and only when I had already given it I realized that I was not on SDK 25 and I know of some others that was the reason with most.
Whether it was the reason with me, I know tomorrow, the device is back and can be picked up,
Click to expand...
Click to collapse
Was your phone stuck in Bootloop of death as well? How did you fix it? What do think causes this issue and how can it be avoided?

[Q] Warranty Repair/Replacememt Questions

My Nexus 6P is suferring from bootloop issues. I've tried to repair it using every method available but after doing some research online it seems to be a known hardware issue.
I bough my phone on BestBuy and have proof of purchase and everything. I already checked on the Huawei Warranty Query site and my device seems to be under warranty until june 2017.
I have some questions. First, nothing on that site points me to a phone or address about where to start the process. Do any of you who have gone trough this process can be kind to point me in the right direction about where to start.
Second, whats the policy regarding boot unlocking, root, etc etc.
I purchase my Nexus 6P 32GB(H1511 ) outrigh unlocked.
Thank you for any of your help.

Lare2 said:
My Nexus 6P is suferring from bootloop issues. I've tried to repair it using every method available but after doing some research online it seems to be a known hardware issue.
I bough my phone on BestBuy and have proof of purchase and everything. I already checked on the Huawei Warranty Query site and my device seems to be under warranty until june 2017.
I have some questions. First, nothing on that site points me to a phone or address about where to start the process. Do any of you who have gone trough this process can be kind to point me in the right direction about where to start.
Second, whats the policy regarding boot unlocking, root, etc etc.
I purchase my Nexus 6P 32GB(H1511 ) outrigh unlocked.
Thank you for any of your help.
Click to expand...
Click to collapse
Call the hotline support phone number at the bottom of the page you bookmarked. If your phone has boot loop of death Huawei likely can't tell what you did in terms of rooting. If the phone still works well enough that you can flash the full factory image then you should. My understanding is that unlocking the bootloader doesn't void the warranty on Nexus devices.
---------- Post added at 07:00 PM ---------- Previous post was at 06:58 PM ----------
Depending on where you are located Huawei might point you to a local service center rather than have you mail in the device. Huawei contracts with some phone repair chains.

The phone was working OK until suddenly it froze on me. I had to force a reboot and from then on it wasn't able to pass further that the Google logo before restarting again.
I can still get it to enter TWRP and can flash everything but as soon as I try to reatart it, the same happens, it just gets to the Google logo and restarts itself in a boot loop.

Lare2 said:
The phone was working OK until suddenly it froze on me. I had to force a reboot and from then on it wasn't able to pass further that the Google logo before restarting again.
I can still get it to enter TWRP and can flash everything but as soon as I try to reatart it, the same happens, it just gets to the Google logo and restarts itself in a boot loop.
Click to expand...
Click to collapse
Did you try flashing the full factory image with fastboot?

jhs39 said:
Did you try flashing the full factory image with fastboot?
Click to expand...
Click to collapse
Yes I did, using the flash-all.bat as per instructions and it succeeds without issues. But as soon as you restart the device and gets to the Google logo, it restarts again and again and again up to the Google logo and never past from there

I had this very same issue, I ended up using a toolkit and that did away my problems.
SkipSoft toolkit did the job, it's pretty straight forward. You can try pulling your data off the phone through twrp.
Then follow the toolkit to flash stock completely - I would recommend first without wiping userdata, if that doesn't work then with userdata.
For some reason the toolkit worked, and not me manually flashing the images in the correct order and a complete wipe.
Goodluck

TnT_ said:
I had this very same issue, I ended up using a toolkit and that did away my problems.
SkipSoft toolkit did the job, it's pretty straight forward. You can try pulling your data off the phone through twrp.
Then follow the toolkit to flash stock completely - I would recommend first without wiping userdata, if that doesn't work then with userdata.
For some reason the toolkit worked, and not me manually flashing the images in the correct order and a complete wipe.
Goodluck
Click to expand...
Click to collapse
I downloaded the Unified Android Toolkit.
I tried following this instructions
FLASH A STOCK IMAGE BACK TO YOUR DEVICE [FIXES NEARLY ALL PROBLEMS]:
1. Unplug the usb cable
2. Reboot manually to Fastboot Mode [see above for button combination]
3. Plug the usb cable back in
4. From the Toolkit Main Menu select option 9,1 to download/flash a stock firmware
image back to your device. Choose to format userdata and is should fix everything.
Mentioned on this Url
But I can't see and option for 9. When I initially open it it asks me to select the device and then asks me to choose the Android version to go but never see that option 9 mentioned above.
Can you guide me to the steps you followed to fix yours

TnT_ said:
I had this very same issue, I ended up using a toolkit and that did away my problems.
SkipSoft toolkit did the job, it's pretty straight forward. You can try pulling your data off the phone through twrp.
Then follow the toolkit to flash stock completely - I would recommend first without wiping userdata, if that doesn't work then with userdata.
For some reason the toolkit worked, and not me manually flashing the images in the correct order and a complete wipe.
Goodluck
Click to expand...
Click to collapse
The difference I see between the flash-all.bat and using the toolkit is formatting partitions instead of erasing them (including userdata and cache). I realize you are out of the woods now, but others experiencing the bootlooping should try manually fastboot formatting userdata and cache first. @Lare2

v12xke said:
The difference I see between the flash-all.bat and using the toolkit is formatting partitions instead of erasing them (including userdata and cache). I realize you are out of the woods now, but others experiencing the bootlooping should try manually fastboot formatting userdata and cache first. @Lare2
Click to expand...
Click to collapse
Well, for anyone scrolling through here. This is how my device semi-hard bricked (after not booting)
I was flashing PureNexus (I've been using it since I got my 6P in April, it was a standard update to me). I was going from November build to January build, and I thought nothing of it. Next thing I know my phone isn't booting, so I try flashing again. I realize I'm stuck so I backup all the stuff that isn't already backed up, and I wipe everything. Flash stock from my computer. Welp looks like that didn't work. So I go through and format everything before trying again, still. No luck. Vendor refused to flash at that point, so vendor had gotten corrupted in the process ( I kept on getting invalid directory for /vendor - weird right?). Or a string of complex errors in fastboot. I saw something earlier while I was helping someone, about the took. I usually like doing things myself, but I used it as a last resort. I flashed back to stock and everything worked. Then I flashed PureNexus again, and had to do the toolkit all over again. Because my phone absolutely refused to boot on December PureNexus for the angler.
TL;DR : I would not recommend flashing the December update of PureNexus at ALL

I have been trying to get it to work with all the suggestions mentioned here sin my last post. No luck at all. I'm in the process to call the warranty support number and will se how it goes.
Even though I have been unable to get it working this has been an amazing learning experience. I got to try several solutions that made me gain more knowledge that I know will be useful in the future.
I'll report back to see how it went with the warranty guys.
Thank you all

Nexus 6P: Bootloop

Hey, Thanks for taking the time to help.
Device: Nexus 6P
Previously Working ROM: Pure Nexus
Recovery Type Was: TWRP
So, I was on Pure Nexus just fine and decided okay! It's been a few updates I'll just update to the newest version. Went ahead and did a Clean Flash, wiped everything in TWRP except the Internal Data, proceeded with a Flash for the new Vendor Image and then to the newest ROM. Restarted and an immediate boot loop.
Thought okay, whatever. I'll just use the my backup that I have! booted into TWRP did backup.. still boot loops. At this point I'm pretty upset cause I know I'm in a pretty terrible spot now, so I decide to do a Factory Image complete restore through Fastboot flash-all.bin.
CONTINUES to boot loop after that, also doesn't even install the stock recovery or something because after a stock flash it shows "No Command". Decided okay, I'll flash TWRP and attempt a factory reset in there, do so. Still boot loop.
So yeah, here I am.
Any advice?

The bootloop of death may have caught up with your phone. When did you get the phone, you may have to rma the device. There is a thread here that many have the same issue. Some have gotten rma out of warranty some didn't. You may want to try.

Hey, the "No Command" is actually stock recovery. You should see the Android on its back with it's chest plate open or something like that. A red exclamation mark in a triangle as well, IIRC.
When you're on that screen, hold power and press and release volume up and that'll take you into stock recovery. If that doesn't work, do it the other way around. Hold volume up and press power.
If you can get into stock recovery, you should be able to use ADB to pull your files, at least.
My 6P screen crapped out yesterday and I just had to pull data myself, let me know if you need any help.

Thanks for the replies, still stuck in a boot loop even after trying another Factory Image in case the one I got was just no good.
Still nothing, was able to get into the recovery even with the no command thing to Factory Reset/Wipe Cache and the problem still persists.
I'm at a loss at this point, I even tried to flash each file in order manually instead of with the flash-all command anddddddd nothing In the end, I'll probably try and RMA since I'm still within a year.
Anyone been through the RMA process want to give any tips on the process? Should I re-lock the boot loader before sending it in?

Don't even bother, you're screwed basically. Call Google or Huawei were you bought it from and ask for a out of warranty RMA. I got mine only last week after they had it for a week. Prepared to be given the run around if this is with Huawei. Google is currently out of 6P's so you might be given credit if you bought from them, that's a big BUT. Good luck and I hope you have a backup of your files off the phone.

bammyman said:
Don't even bother, you're screwed basically. Call Google or Huawei were you bought it from and ask for a out of warranty RMA. I got mine only last week after they had it for a week. Prepared to be given the run around if this is with Huawei. Google is currently out of 6P's so you might be given credit if you bought from them, that's a big BUT. Good luck and I hope you have a backup of your files off the phone.
Click to expand...
Click to collapse
Actually, I'm still within the 12 months. But I know that the whole Custom Rom thing kind of voids that. I did end up calling Huawei and ended up getting the in-warranty RMA started but... kind of scared cause I'm not sure if the whole flashing the thing with a non-offical ROM gets flagged some how.
Should I call back and specifically request an OOW RMA? Or just take my chances with the In-warranty RMA?

They do not care about custom roms. Just send it in with a factory reset. I sent mine in with Android O and they were fine with it

I'm sorry I don't know who to turn to for help. I have a Nexus 6p and it is stuck in bootloop. I'm phone illiterate so I don't even know how to go about fixing it. There are very important photos and voice notes on there of my father that I would like to preserve as they are the last things I have of him before he passed away. Willing to pay $ to get this fixed. Any ideas?

BB12345 said:
I'm sorry I don't know who to turn to for help. I have a Nexus 6p and it is stuck in bootloop. I'm phone illiterate so I don't even know how to go about fixing it. There are very important photos and voice notes on there of my father that I would like to preserve as they are the last things I have of him before he passed away. Willing to pay $ to get this fixed. Any ideas?
Click to expand...
Click to collapse
Are you able to get into recovery?