Develop Bugs

Need to return to stock w/out functioning power button

OK here's the quick version of what happened.
Last night, before leaving work, I was playing a game (dice w/buddies) and when I was finished I put the phone to sleep. Picked it up after my 45 min drive home and the screen wouldn't turn on at all. Pulled the battery and as soon as I put it back in the phone vibrated and started the boot process. I didn't even hit the power button. I let it do it's thing and just watched. The screen was all kinds of jacked!! Vertical banding and discoloration to say the least. Well it took about 10 min to boot but when it did the touchscreen was unresponsive. After about 10 min of batt pulls to reboot and check the screen, I called VZW for a replacement.. (They overnighted one and it will be here this morning) So after that call, I just put the phone down and fed my daughter and did a few things around the house. Went back about 2 hrs later and pulled the battery and rebooted the phone to find that the screen now works! BUT the power button does not. It won't wake the phone up,put it to sleep, nothing. It's dead. So I thought I would unroot/relock and take it back to stock so I can send it back. Here is the problem with that; with the power button broken, fastboot won't recognize the phone. I can get into the bootloader via rom toolbox lite (JRummy app) and that works fine. But whether I try it thru adb or WugFresh's toolkit, as soon as the phone hits "Checking fastboot status", it fails. When you go to the device manager in Win7 and try to update the drivers, it fails. It comes up as something like INTF7 or something like that.
So how can I return to stock without a working power button? Even if I was to get it back to stock somehow, I can't relock it as I would have to hit the power button to accept the warning. Is there any other way?

I heard there was some issues with adb on 4.2. You might want to try updating your adb on your comp and then retry fastboot. There was a post on here about what steps to take to troubleshoot adb.

eqjunkie829 said:
I heard there was some issues with adb on 4.2. You might want to try updating your adb on your comp and then retry fastboot. There was a post on here about what steps to take to troubleshoot adb.
Click to expand...
Click to collapse
SDK was updated last night to the newest version. I don't think it's an adb/sdk issue. They are not connecting (I think) because the power botton is broken and the phone turns on as soon as the battery is put in. It's almost like it thinks the power button is being held in.
Once you get it to reboot into fastboot mode, it doesn't do anything. None of the buttons work then. Volume or power. And all adb says is "waiting for device."

cubsfan187 said:
SDK was updated last night to the newest version. I don't think it's an adb/sdk issue. They are not connecting (I think) because the power botton is broken and the phone turns on as soon as the battery is put in. It's almost like it thinks the power button is being held in.
Once you get it to reboot into fastboot mode, it doesn't do anything. None of the buttons work then. Volume or power. And all adb says is "waiting for device."
Click to expand...
Click to collapse
ADB doesn't work in the bootloader (fastboot mode). It will work in a custom recovery, or once boot into Android though.
When in the bootloader the only commands that will work will be fastboot commands, and they should be all you need to get back to stock and lock your bootloader up.

cupfulloflol said:
ADB doesn't work in the bootloader (fastboot mode). It will work in a custom recovery, or once boot into Android though.
When in the bootloader the only commands that will work will be fastboot commands, and they should be all you need to get back to stock and lock your bootloader up.
Click to expand...
Click to collapse
The fastboot commands don't work. Once you get into bootloader mode, nothing works. The volume keys,power key, nothing. When you type in a fastboot command it sits at "waiting for device" and never does anything. If you look in device manager (Win7) is shows a strange INFT2 (or something like that) driver that needs to be installed. I have searched for hours and found nothing on that. Even the toolkits stall at fastboot commands.

cubsfan187 said:
The fastboot commands don't work. Once you get into bootloader mode, nothing works. The volume keys,power key, nothing. When you type in a fastboot command it sits at "waiting for device" and never does anything. If you look in device manager (Win7) is shows a strange INFT2 (or something like that) driver that needs to be installed. I have searched for hours and found nothing on that. Even the toolkits stall at fastboot commands.
Click to expand...
Click to collapse
This sounds like a driver issue with your PC. I recommend that you start fresh. Uninstalling the current drivers, and installing new ones. http://forum.xda-developers.com/showthread.php?t=1379875 <-- I recommend the Naked Driver. http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735 <-- guide there on how to install them.
If you used fastboot on this PC successfully in the past, you could also just do some tinkering to figure out why, but this may take more work to diagnose than actually just nuking the current setup and setting up new ones.

cubsfan187 said:
When you go to the device manager in Win7 and try to update the drivers, it fails. It comes up as something like INTF7 or something like that.
cupfulloflol said:
This sounds like a driver issue with your PC. I recommend that you start fresh. Uninstalling the current drivers, and installing new ones. http://forum.xda-developers.com/showthread.php?t=1379875 <-- I recommend the Naked Driver. http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735 <-- guide there on how to install them.
If you used fastboot on this PC successfully in the past, you could also just do some tinkering to figure out why, but this may take more work to diagnose than actually just nuking the current setup and setting up new ones.
Click to expand...
Click to collapse
I already tried to mess with the drivers. They won't update while in fastboot mode. It comes up as INTF7 (or whatever it was) and they cannot be found. As long as I can lock the bootloader I will send it back rooted and maybe even on a close-to-stock rom. That's probably the best I can do.
Click to expand...
Click to collapse
Click to expand...
Click to collapse

cubsfan187 said:
I already tried to mess with the drivers. They won't update while in fastboot mode. It comes up as INTF7 (or whatever it was) and they cannot be found. As long as I can lock the bootloader I will send it back rooted and maybe even on a close-to-stock rom. That's probably the best I can do.
Click to expand...
Click to collapse
You can get back to stock as long as you are at least rooted. You can do this, which will allow you to do it all as long as the device can boot into Android.

cupfulloflol said:
You can get back to stock as long as you are at least rooted. You can do this, which will allow you to do it all as long as the device can boot into Android.
Click to expand...
Click to collapse
This is exactly what I am gonna try after getting the new phone set up. :good:

First bricked fire tv??

Not sure if its really bricked or not but Its all messed and wont fully boot so it doesnt have lan access anymore for ssh and adb over wifi. I have a male to male usb cable and my pc is recognizing when its plugged in but there are no device drivers installed and adb/fastboot wont recognize (no usb debugging enabled?) so it just hangs on <waiting on device> any idea how I can install devices drivers and move forward with restoring backup of the file I fuxored? Thx guys!

Have you tried disconnecting that A to A cable? When I tried using an A A cable from my laptop to the Fire, it hung when it booted.
It powered on, went to the first white on black Amazon logo, and halted. Disconnecting the cable and power cycling let it complete the boot cycle.

Havnt got that far yet myself but the way i tinker i will be there shortly .. but as a warning to others, if you are not 100% sure what you are doing, dont muck around especially if you remount /system as rw.
Playing around will be much safer once we get recovery..
Building a recovery shouldnt be too difficult.. its booting a custom recovery that will be the trick.. Jcase had allready said he has figured it out perhaps he will share now that root is out.

roustabout said:
Have you tried disconnecting that A to A cable? When I tried using an A A cable from my laptop to the Fire, it hung when it booted.
It powered on, went to the first white on black Amazon logo, and halted. Disconnecting the cable and power cycling let it complete the boot cycle.
Click to expand...
Click to collapse
Ive got fastboot connected now so it appears it was some funky unknown issue. Fastboot isnt like adb tho and the only time ive ever used it was to re-write whole img files so is that my only option or is there some way I can push stuff through fastboot? The OTA firmware links posted a few weeks back are now dead too..

You can download the OTA updates (they are complete roms). http://forum.xda-developers.com/showthread.php?t=2709811 - links still work, i just redownloaded them (not sure where I put my old ones).
Only problem is the recovery looks for them at /cache/, which isn't writable w/o root. I'm not sure of the functions available via fastboot w/ Fire TV (don't have a cable), but if you can't get into the recovery from fastboot, you can always try to boot a dumped recovery.img from fastboot... but still not sure how you can work around the stock recovery looking for the update file at /cache/
edit: actually don't think fastboot will be of much use with a locked bootloader.

Luxferro said:
You can download the OTA updates (they are complete roms). http://forum.xda-developers.com/showthread.php?t=2709811 - links still work, i just redownloaded them (not sure where I put my old ones).
Only problem is the recovery looks for them at /cache/, which isn't writable w/o root. I'm not sure of the functions available via fastboot w/ Fire TV (don't have a cable), but if you can't get into the recovery from fastboot, you can always try to boot a dumped recovery.img from fastboot... but still not sure how you can work around the stock recovery looking for the update file at /cache/
edit: actually don't think fastboot will be of much use with a locked bootloader.
Click to expand...
Click to collapse
Im rooted already, but basically what youre saying is to wait until bootloader is unlocked then flash that via fastboot and then flash recovery via fastboot. I feel like there has to be an easier way lol but im a noob so who knows.
Im not have any luck with those links either ive even tried assigning a static public dns to make sure my opendns stuff was no longer blocking. Does anyone have an alternate link?

alwaysbless said:
Im rooted already, but basically what youre saying is to wait until bootloader is unlocked then flash that via fastboot and then flash recovery via fastboot. I feel like there has to be an easier way lol but im a noob so who knows.
Click to expand...
Click to collapse
Nah, not saying that at all - would love for an unlocked bootloader, but you might be waiting forever.
this is also one of the reasons that jcase hasn't released what he had (according to his G+ page). since if you bork the stock rooted rom, you'll have a hard time getting it fixed (since the rooted rom is the only current way in). If you can't boot the rom, then you can't fix anything. I'm no expert, so maybe one will chime in. But I think the next step after rooting, is to have a custom recovery, and a way to boot into it if the rom breaks - which we don't have yet.

I had a similar instance. Gained root messed around too much and got it to not boot. Amazon is sending a replacement... But if there is a way around that in the future I would love to just fix it my self.
Sent from my Nexus 5 using XDA Premium 4 mobile app

Luxferro said:
Nah, not saying that at all - would love for an unlocked bootloader, but you might be waiting forever.
this is also one of the reasons that jcase hasn't released what he had (according to his G+ page). since if you bork the stock rooted rom, you'll have a hard time getting it fixed (since the rooted rom is the only current way in). If you can't boot the rom, then you can't fix anything. I'm no expert, so maybe one will chime in. But I think the next step after rooting, is to have a custom recovery, and a way to boot into it if the rom breaks - which we don't have yet.
Click to expand...
Click to collapse
So I couldnt even take the system.img and rewrite it using fastboot without having an unlocked bootloader? Sounds like the only way this thing will recover is install cwm/twrp recovery.img whenever that becomes available and then reflash w/ custom recovery.

alwaysbless said:
So I couldnt even take the system.img and rewrite it using fastboot without having an unlocked bootloader? Sounds like the only way this thing will recover is install cwm/twrp recovery.img whenever that becomes available and then reflash w/ custom recovery.
Click to expand...
Click to collapse
Except you won't be able to install a custom recovery since only your ROM has root access and it doesn't boot.
Sent from my Nexus 5 using Tapatalk

Luxferro said:
Except you won't be able to install a custom recovery since only your ROM has root access and it doesn't boot.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Got you now. So this is def the first bricked fire tv lol. Guess ill just sit it to the side and see if someone smarter than I can figure something like this out in the future.

Have you tried fastboot boot commands? Like fastboot boot blahblahblah.img? If it is softbricked i guess it can't hurt to try rite?

I don't know if this will work or not, but if you've already tried pulling the power, pulling USB and powering on the next thing I'd try is to obtain a 1 gig or so USB drive, format it fat32 and copy the OTA update to it.
- Leave it zipped.
- Name it update.zip
- pull the plug on the FTV
- put the USB stick in
- power it on and leave it for a bit. Watch it - is the power LED going out? If so, it may doing a recovery install of the signed OTA and rebooting - many Android devices will install anything on the sdcard called Update.zip if it's there at boot time.
What you're hoping is that the USB mass storage is mounted as a possible recovery source at power on and that the OTA is isntalled via the stock recovery. If it works, great, if it doesn't, too bad.

another brick on the wall ?
Dear OP ' i think you are not the only one .
im not sure if im bricked or plain noob
after i rooted successfully and did the blocking through host editor guide in fire tv news and for a good measure i run this command "su
pm disable com.amazon.dcp" . all was good and i had an issue with audio in xbmc and in my great wisdom i did a reset to factory settings.
since then i can not register to amazon i believe because it can not accsses amazon site for verification. so im stuck in there.
i tried to SSH and through command line no device was recognized .
any assistance to this stupidity will be much appericiated
thanks yigo

Yigo said:
after i rooted successfully and did the blocking through host editor guide in fire tv news and for a good measure i run this command "su pm disable com.amazon.dcp" .
Click to expand...
Click to collapse
Afraid I can't help you, but in light of preventing other people (and me) to have the same issues:
I assume the /etc/hosts file will survive factory-resets, it's a file that probably is not restored (so immediatly removed the host-lines from mine), but wonder if the pm disable dcp will also survice a reset ? I assume not (core funcationality for amazon, likely in factory-reset group), but you never know, esp. not in the v1 versions we are running.
Anybody knows if this is the case ? I like the pm disable solution, but if this means that borking up my installation will prevent me from ever restoring it (as unable to connect to amazon), I'll have to fall back to the router-blockage solution, and would suggest other ppl to do that as well

Deregistering AFTV may help with registration issue.
I had problems registering after factory reset.
I only disabled my amazon.dcp nad had dns and router blocks to prevent updates.
I did not edit my host file.
To de-register your Fire TV-
1 - log on to your amazon account
2 - Hold the mouse over where it says 'Your Account" but do not click. You will get a list of options.
3 - Click "Manage Your Content and Devices"
4 - Click the center tab "Your Devices"
5 - Click on your Fire TV.
6 - Click "Deregister" right below your Fire TV.
You will ge a message saying it there may be a delay for it to take effect.

[email protected] said:
I had problems registering after factory reset.
I only disabled my amazon.dcp nad had dns and router blocks to prevent updates.
I did not edit my host file.
Click to expand...
Click to collapse
So (while you need to de register the FTV itself within amazon), it looks like you can factory reset after disabling the amazon.dcp service.
Which is good news, as this allows easier disabling of update checks on machine level instead of router level (which not everybody will be able to do) and disabling the update service is better then overlooking a (hidden) fallback URL.
N=1 though, so'll have to wait if more confirmations come in, or somebody will be brave enough to try it

Still Learning - Passing it on.
JPDeckers said:
So (while you need to de register the FTV itself within amazon), it looks like you can factory reset after disabling the amazon.dcp service.
Which is good news, as this allows easier disabling of update checks on machine level instead of router level (which not everybody will be able to do) and disabling the update service is better then overlooking a (hidden) fallback URL.
N=1 though, so'll have to wait if more confirmations come in, or somebody will be brave enough to try it
Click to expand...
Click to collapse
I read your other posting about update blocking.
Seems I did not have my amazon.dcp disabled.
I was not in SU mode when executing command and amazon.dcp was just killed not disabled.
Sorry for any confusion. Thanks

JPDeckers said:
So (while you need to de register the FTV itself within amazon), it looks like you can factory reset after disabling the amazon.dcp service.
Which is good news, as this allows easier disabling of update checks on machine level instead of router level (which not everybody will be able to do) and disabling the update service is better then overlooking a (hidden) fallback URL.
N=1 though, so'll have to wait if more confirmations come in, or somebody will be brave enough to try it
Click to expand...
Click to collapse
I hope one of the folks with a softbricked device gets a chance to see what happens with the over the air update file copied to a fat32 formatted USB stick and renamed update.zip.
With luck, at power on if there is media present, the stock recovery is looking to removable media to see if there's a file named update.zip it can process.
I don't want to softbrick mine to test, though.

So if I am understanding correctly, you should enable updates before you factory reset?

Nexus 5x display is scrambled after rolling back from android n developer preview2

Hi All,
Request all to provide any suggestions related to the below issue:
I rolled back from android n preview 2 to android m after which my display is scrambled.I am not able to view any thing on it.
But I am getting calls and able to pick them when I roughly expect the place where I can swipe the dialer right to pick the call.
Few things that I want to highlight is :
1)I had unstable wifi connection while downloading the android m OTA.
2)I removed the unlock bootloader check before rolling back in the developer options.
3)I can also sense that i am able to take screen shots when I am holding the power button and the volume down button based on the sound it normally makes (while capturing screenshots)
I am not able to come to conclusion whether this a hardware issue?(may be i need the replacement of the screen) or can it be due to corrupt ota file update?
Any suggestions would be much appreciated.
thanks

I would first see if flashing the m factory image solves the issue. Then look at hardware.

k.s.deviate said:
I would first see if flashing the m factory image solves the issue. Then look at hardware.
Click to expand...
Click to collapse
thank you but the problem is I am not able to see the screen at all and hence I am not able to go to the fastboot mode or recovery mode.

NeverBackDown said:
thank you but the problem is I am not able to see the screen at all and hence I am not able to go to the fastboot mode or recovery mode.
Click to expand...
Click to collapse
use "adb reboot bootloader" from command prompt to enter bootloader or if you know the device is off, press power + vol up + vol down for roughly 5sec, thatll get into bootloader. than flash factory image.
or last case scenario use wug fresh toolkit to force flash the image, make sure you select the device fails to boot box (I think that's what its called, the only other one states "device on/normal" <-- so NOT that one)

k.s.deviate said:
use "adb reboot bootloader" from command prompt to enter bootloader or if you know the device is off, press power + vol up + vol down for roughly 5sec, thatll get into bootloader. than flash factory image.
or last case scenario use wug fresh toolkit to force flash the image, make sure you select the device fails to boot box (I think that's what its called, the only other one states "device on/normal" <-- so NOT that one)
Click to expand...
Click to collapse
Thanks I am first looking for type c to usb to connect it to my computer,I will try for it tomorrow and also the first option you provided will work only if usb debugging is already enabled on my phone ,right?

NeverBackDown said:
Thanks I am first looking for type c to usb to connect it to my computer,I will try for it tomorrow and also the first option you provided will work only if usb debugging is already enabled on my phone ,right?
Click to expand...
Click to collapse
yes, the adb command will only work if debugging is on. Once in bootlader, use fastboot commands, debugging doesn't matter at that point.

k.s.deviate said:
yes, the adb command will only work if debugging is on. Once in bootlader, use fastboot commands, debugging doesn't matter at that point.
Click to expand...
Click to collapse
Hi All,
I got the cable ,I had everything to flash the official factory images.But the problem is as mentioned earlier I haven't checked the oem unlock in the developer option and this is not allowing to flash the factory images and fastboot flashing unlock is failing.
Is there any work around for this please?

NeverBackDown said:
Hi All,
I got the cable ,I had everything to flash the official factory images.But the problem is as mentioned earlier I haven't checked the oem unlock in the developer option and this is not allowing to flash the factory images and fastboot flashing unlock is failing.
Is there any work around for this please?
Click to expand...
Click to collapse
Not that I'm aware of. Sorry, there is a thread on here that may prove useful that deals with bricked phones with OEM unlocked off. The info there might help you at least get back to stock.

k.s.deviate said:
Not that I'm aware of. Sorry, there is a thread on here that may prove useful that deals with bricked phones with OEM unlocked off. The info there might help you at least get back to stock.
Click to expand...
Click to collapse
In that case ,do you think the service center guys have some other means to deal with if it is a software issue?

NeverBackDown said:
In that case ,do you think the service center guys have some other means to deal with if it is a software issue?
Click to expand...
Click to collapse
Possibly, I have no experience dealing with a service center unfortunately.

NeverBackDown said:
In that case ,do you think the service center guys have some other means to deal with if it is a software issue?
Click to expand...
Click to collapse
I also want to highlight that,I am getting a black screen on the fastboot mode too,i cant see nothing there..Only way i am able to identify that my device is in fastboot mode is by giving fastboot devices command.
So can this be a software issue?

NeverBackDown said:
Hi All,
I got the cable ,I had everything to flash the official factory images.But the problem is as mentioned earlier I haven't checked the oem unlock in the developer option and this is not allowing to flash the factory images and fastboot flashing unlock is failing.
Is there any work around for this please?
Click to expand...
Click to collapse
You might want to look into android screencast.
I don't know if it still works with the latest android releases, but back in kitkat days if I had a screen that wouldn't display I could use screencast and I'd get the framebuffer displaying on the PC. While viewing on PC I could then do touchscreen "guesses" more accurately and presumably you'd be able to enable OEM unlocked bootloader so you can flash factory images.

Bootloader unable to boot ROM, recovery. Computer not detecting fastboot presence

My latest configuration was:
Bullhead 32 GB board,
PureNexus (6.0.1): July build
PureNexus Gapps
Stock kernel
TWRP
SuperSU
Situation/problem: One day, the phone went off in my pocket, and I thought it accidentally got powered off or something. When I tried to boot it, it would load the Google screen, but not the boot process (this is not a bootloop as it won't even start the boot process). So I went to the BL, tried to boot from there, no luck.
Then I tried to get into recovery from BL, still it would freeze for a few seconds, load the google screen, and back to BL.
So I realized it was time to clean flash, I connected in fastboot mode, but my computer (Linux, Ubunutu 16.04) won't detect the device fastboot mode (I have done everything before on the same computer). Just to be sure, I tried connecting in 3 different computers so that it wasn't a driver problem, but to no avail.
I am now stuck with a device that won't go past the bootloader and won't even let me flash a new system.
Possible problems I think this may be a problem with the USB port and I had just not realized it, because I had dropped the phone from 1m high just a week ago.
When I called the LG service, they said they'd have to replace motherboard and that it can't have been the USB port.
I am perplexed now, as to what to do. I had saved up loads to buy the latest flagship Nexus just this January, and now it's going away...
Another observation: I was having problems with the phone as it was randomly rebooting every once in a while for a month, but I ignored flashing a new build because I was busy with studies. I don't know if this is related but just putting it out there.
Possible things that I could do? Appreciate your help in advance.

zakoda said:
My latest configuration was:
Bullhead 32 GB board,
PureNexus (6.0.1): July build
PureNexus Gapps
Stock kernel
TWRP
SuperSU
Situation/problem: One day, the phone went off in my pocket, and I thought it accidentally got powered off or something. When I tried to boot it, it would load the Google screen, but not the boot process (this is not a bootloop as it won't even start the boot process). So I went to the BL, tried to boot from there, no luck.
Then I tried to get into recovery from BL, still it would freeze for a few seconds, load the google screen, and back to BL.
So I realized it was time to clean flash, I connected in fastboot mode, but my computer (Linux, Ubunutu 16.04) won't detect the device fastboot mode (I have done everything before on the same computer). Just to be sure, I tried connecting in 3 different computers so that it wasn't a driver problem, but to no avail.
I am now stuck with a device that won't go past the bootloader and won't even let me flash a new system.
Possible problems I think this may be a problem with the USB port and I had just not realized it, because I had dropped the phone from 1m high just a week ago.
When I called the LG service, they said they'd have to replace motherboard and that it can't have been the USB port.
I am perplexed now, as to what to do. I had saved up loads to buy the latest flagship Nexus just this January, and now it's going away...
Another observation: I was having problems with the phone as it was randomly rebooting every once in a while for a month, but I ignored flashing a new build because I was busy with studies. I don't know if this is related but just putting it out there.
Possible things that I could do? Appreciate your help in advance.
Click to expand...
Click to collapse
Here's your solution for it not being detected in fastboot mode.......in fastboot mode, connect your phone to your computer. go to your device manager and find your device. double click on your device, right click on the second option and select update driver. than select browse my computer and than select pick from a list of drivers and manually install the driver for fastboot mode.....hope this helps :good:

dominoeflux said:
Here's your solution for it not being detected in fastboot mode.......in fastboot mode, connect your phone to your computer. go to your device manager and find your device. double click on your device, right click on the second option and select update driver. than select browse my computer and than select pick from a list of drivers and manually install the driver for fastboot mode.....hope this helps :good:
Click to expand...
Click to collapse
I have mentioned in my post: It is not a driver problem

zakoda said:
I have mentioned in my post: It is not a driver problem
Click to expand...
Click to collapse
if its not being detected in fastboot mode, than that means it's a driver problem since the same thing happened to me. you have to manually install the fastboot driver for fastboot mode. I've read your post and I understood exactly what you were talking about. have you even tried to check the driver? have you tried flashing back stock? if you've checked other computers that you have mentioned and it's still not detecting it in fastboot mode with the other computers, than the driver for fastboot mode needs to be updated manually, seeing that if it was detected by the other computers that you have, you wouldn't be asking for help right now because your device would already be up and running. hey i'm just trying to help u here. it doesn't hurt to double check your driver. I may be a junior member, but I know plenty seeing that I've been through the same situation myself. if it's not the driver as you say it's not, what version TWRP were you running and did you restore a backup with the EFS checked?

Hey, I can confirm it's not a driver problem.
I got the phone to boot up yesterday, flashed the latest PureNexus (7.x) and after a short while it again went into reboot cycles.
I tried TWRP, there also mid-flashing it randomly rebooted. I think it is rebooting after even small amount of activity. Maybe the thermal sensors are damaged causing it to flag warning with slightest heating. Or maybe some other circuitry is damaged, causing the temperature to actually rise in short while, and it is not being felt due to the plastic body. In any case I think this is a hardware damage, though I have no clue why. I will try contacting Google to see if they can replace it.
By the way, how long is the warranty valid? I had bought the device in Dec 2015.

zakoda said:
Hey, I can confirm it's not a driver problem.
I got the phone to boot up yesterday, flashed the latest PureNexus (7.x) and after a short while it again went into reboot cycles.
I tried TWRP, there also mid-flashing it randomly rebooted. I think it is rebooting after even small amount of activity. Maybe the thermal sensors are damaged causing it to flag warning with slightest heating. Or maybe some other circuitry is damaged, causing the temperature to actually rise in short while, and it is not being felt due to the plastic body. In any case I think this is a hardware damage, though I have no clue why. I will try contacting Google to see if they can replace it.
By the way, how long is the warranty valid? I had bought the device in Dec 2015.
Click to expand...
Click to collapse
In the most country, the warranty is 12month so maybe gone because now it's 21th of december

Question Phone bricked trying to update December patch

Hey guys, so I used googles flash tool to update December patch and it keeps failing at writing to phone 1 of 11.
It's now in a bootloop but can access fastboot.
Ive tried to completely reset the phone manually using adb but it fails. It just doesn't work and aborts basically the phone rejects all data transmission.
What am I doing wrong or can I get a more detailed way to reset the phone completely.
-Edit-
I was also rooted and was following the guide for rooted December 12.
The main error is
(Error reading sparse file)

Why did you use the flash tool? General recommendation is, as long as you're running stock, just use the full OTA packages.
For the flash tool to be usable you need to OEM unlock your phone (while it's in a working state!).
If you can access fastboot you should be able to access recovery as well, where you can flash the full OTA, which should fix your issue.

fonix232 said:
Why did you use the flash tool? General recommendation is, as long as you're running stock, just use the full OTA packages.
For the flash tool to be usable you need to OEM unlock your phone (while it's in a working state!).
If you can access fastboot you should be able to access recovery as well, where you can flash the full OTA, which should fix your issue.
Click to expand...
Click to collapse
Because I'm rooted and recovery doesn't work.
I should have just done it manually instead of the flash tool method published here.
I just don't get why the system image isn't flashing now, the bootloader and radio flash work, but not the actual update. It's the correct version and all.

If the online flash tool isn't working for you, download the factory image from google's website and use the flash-all.bat to flash the device. Ensure that you modify the flash-all.bat file to not wipe data before running. This can be done by modifying one line in the file. Which is the following:
Code:
fastboot -w update image-raven-....zip
to
Code:
fastboot update --disable-verity --disable-verification image-raven-....zip
When flashing ensure that phone is in bootloader first.

So I got it to work after several hours. Literally just worked after trying another Google USB cable that was USB c to USB c, or maybe it worked cause of something else. Not sure, I don't like how finicky pixels have become. I discovered it's sometimes a luck thing when it wants to flash or not according to many people when searching the internet for solutions.

So i got a lil problem. i updated the pixel 6 pro to december update but upon booting up it says your phone is corrupted and sits at the google bootup screen. i can still use fastboot and whatnot but every img i tried i get the same message and it sits again?

holla420 said:
So i got a lil problem. i updated the pixel 6 pro to december update but upon booting up it says your phone is corrupted and sits at the google bootup screen. i can still use fastboot and whatnot but every img i tried i get the same message and it sits again?
Click to expand...
Click to collapse
edit---
first try this method that was posted - sometimes you can save your phone this way. if that doesn't work: you can download the factory image and remove the "-w" command in the flash-all.bat file (save it properly) - this will prevent wiping your phone. you'll need adb/fastboot tool and drivers. if you need help with this just reply.
if that doesn't work, you can go this route (but it will wipe your phone) you can use the "flash" link on the factory image page here. if you press the "flash" link in blue, it will take you to the correct build at flash.android.com (click on the build version 12.0.0 (SD1A.210817.037, Nov 2021) - that's the one that worked for me.

ok the problem im havin is it sstill sayinbg courrpt. it cant be trusted and may not work

holla420 said:
ok the problem im havin is it sstill sayinbg courrpt. it cant be trusted and may not work
Click to expand...
Click to collapse
What method did you use to update? Are you rooted? If so, what version of Magisk did you use?

V0latyle said:
What method did you use to update? Are you rooted? If so, what version of Magisk did you use?
Click to expand...
Click to collapse
no root, just unlocked bootloader i manually installed using adb

holla420 said:
no root, just unlocked bootloader i manually installed using adb
Click to expand...
Click to collapse
Use the Android Flash Tool to flash the latest December update. Don't check any of the boxes.

ayye thanks this method worked

holla420 said:
ok the problem im havin is it sstill sayinbg courrpt. it cant be trusted and may not work
Click to expand...
Click to collapse
You'll always get this message upon reboot once the bootloader is unlock.
It's normal, and you can disregard it entirely (unless you want the absolutely most secure device possible, then you should lock the bootloader, and this message will go away)

Az Biker said:
You'll always get this message upon reboot once the bootloader is unlock.
It's normal, and you can disregard it entirely (unless you want the absolutely most secure device possible, then you should lock the bootloader, and this message will go away)
Click to expand...
Click to collapse
oh i know but this was a different message. it was in red and wouldnt boot pass the bootup screen,

coilbio said:
So I got it to work after several hours. Literally just worked after trying another Google USB cable that was USB c to USB c, or maybe it worked cause of something else. Not sure, I don't like how finicky pixels have become. I discovered it's sometimes a luck thing when it wants to flash or not according to many people when searching the internet for solutions.
Click to expand...
Click to collapse
sounds like a user error; if it's fixed you might want to update your first post with solutions in case others have similar issues.

coilbio said:
So I got it to work after several hours. Literally just worked after trying another Google USB cable that was USB c to USB c, or maybe it worked cause of something else. Not sure, I don't like how finicky pixels have become. I discovered it's sometimes a luck thing when it wants to flash or not according to many people when searching the internet for solutions.
Click to expand...
Click to collapse
There are definitely better and worse USB-C cables. I've successfully fully flashed my P6P connected to a powered USB-A (3.2 Gen 2) Hub in one room through a USB extension cable 10-15 feet from my computer in another room. The hub and the extension cable are reasonably "robust", and I've found them reliable, but they're not particularly reputable name brands by any means. The USB-A -> USB-C cable I have connected to that hub is from my old HTC 10, too.