Database Users

[Q] Boot loop after OTA update.

Hi,
I have been given this mobile to try and fix and despite two days of solid reading I cannot find an answer.
The phone was originally on T-Mobile and had stock rom, the phone HAD been rooted and unlocked.The phone boots up then after a few seconds will say "powering Off" then in boot mode I get the dreaded "Failed to boot 2" then it says "Starting RSD mode" and stays on that.
I have tried to boot into recovery and get the "Failed to boot 2" error.
I need to somehow clear the update from the internal memory but cannot see if that is possible.One the phone boots up I dont get long enough to get into the settings before it powers down.
I have tried every option including "fastboot" on the phone with no luck.
Cheers
Nick

Note that using the steps I did to get your phone booting again will cause you to lose all the data that you saved on your phone. Proceed only if you know what you're doing.
1)Download fastboot here
2)Connect your phone to your PC.
3)Run a command prompt in administrator's mode
4)Remove the battery and plug it back in
5)Phone should start, if not, power it on (if necessary press the vol down button while powering on)
6)Once phone is on, type fastboot -w
Your command prompt window should say
erasing 'userdata'.... OKAY
erasing 'cache' .... OKAY
finished. total time: x.xxs
7)Type fastboot reboot
Phone should boot normally.
With thanks to eval- (for the fastbook package) and thekooliest over here for the steps to clear the userdata. Credit goes to both of them
Happened to me a couple of hours ago after i tried to run a update OTA, my phone is rooted, unlocked too.

look here also: http://forum.xda-developers.com/showthread.php?t=1391940
This guy had the same problem as you and is able to recover.

Dead Nexus 4, very strange, advice welcome

My Nexus 4 is in a sorry state and I'm looking for some advice before I RMA, just in case it can be saved. It's very odd.
My N4 was on charge overnight and my alarm went off this morning as normal, Cancelling it crashed the clock app, and when I unlocked the device I was greeted with a cascade of crashing services. So I turned the device off but it will not start and hangs on the Google logo with a padlock icon displayed at the bottom of the screen, The device is not encrupted and the battery is fully charged.
I am running stock 4.2.2 with an unlocked bootloaded and the device _will_ boot to fastboot mode. Selecting the Recovery option displays the Android red warning triangle icon.
So I fired up the Nexus 4 Toolkit and this will let me flash a temporary recovery image. But neither CWM and TWRP can mount /cache, /system, /data or /sd-card, so a factory reset/Dalvik wipe etc will not work. Very odd.
As a last resort I downloaded the official 4.2.2 image but the toolkit cannot flash it and it displays:
Starting Flash Process..
Flashing Bootloader Image..
sending 'bootloader' (2188 KB)...
OKAY [ 0.140s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.156s
An Error Occured
I am out of ideas so any suggestions are welcome.

rec71 said:
My Nexus 4 is in a sorry state and I'm looking for some advice before I RMA, just in case it can be saved. It's very odd.
My N4 was on charge overnight and my alarm went off this morning as normal, Cancelling it crashed the clock app, and when I unlocked the device I was greeted with a cascade of crashing services. So I turned the device off but it will not start and hangs on the Google logo with a padlock icon displayed at the bottom of the screen, The device is not encrupted and the battery is fully charged.
I am running stock 4.2.2 with an unlocked bootloaded and the device _will_ boot to fastboot mode. Selecting the Recovery option displays the Android red warning triangle icon.
So I fired up the Nexus 4 Toolkit and this will let me flash a temporary recovery image. But neither CWM and TWRP can mount /cache, /system, /data or /sd-card, so a factory reset/Dalvik wipe etc will not work. Very odd.
As a last resort I downloaded the official 4.2.2 image but the toolkit cannot flash it and it displays:
Starting Flash Process..
Flashing Bootloader Image..
sending 'bootloader' (2188 KB)...
OKAY [ 0.140s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.156s
An Error Occured
I am out of ideas so any suggestions are welcome.
Click to expand...
Click to collapse
I suggest you leave it as is and OEM lock it before you send it in. If they see its OEM locked they shouldn't give you a problem with it

brandonc0526 said:
I suggest you leave it as is and OEM lock it before you send it in. If they see its OEM locked they shouldn't give you a problem with it
Click to expand...
Click to collapse
It won't relock.
It's like it's read-only.

rec71 said:
It won't relock.
It's like it's read-only.
Click to expand...
Click to collapse
Hmmm. Try booting into TWRP from the toolkit and flashing a rom. If that doesn't work just try wiping everything and toggling/untoggling all the mounts. I had this issue on my old galaxy S and wiping did the trick, although I had to flash my ROM again

Strange. TWRP asks for a password - is this normal? The device has never had encryption enabled. But if I skip this I still cannot mount or access any part of the storage.

Same error. Have you find any solution?
Hello, did you find any solution? I just had the same exact problem. I wiped it through fastboot but when I try to flash the image, I get the same error
rec71 said:
My Nexus 4 is in a sorry state and I'm looking for some advice before I RMA, just in case it can be saved. It's very odd.
My N4 was on charge overnight and my alarm went off this morning as normal, Cancelling it crashed the clock app, and when I unlocked the device I was greeted with a cascade of crashing services. So I turned the device off but it will not start and hangs on the Google logo with a padlock icon displayed at the bottom of the screen, The device is not encrupted and the battery is fully charged.
I am running stock 4.2.2 with an unlocked bootloaded and the device _will_ boot to fastboot mode. Selecting the Recovery option displays the Android red warning triangle icon.
So I fired up the Nexus 4 Toolkit and this will let me flash a temporary recovery image. But neither CWM and TWRP can mount /cache, /system, /data or /sd-card, so a factory reset/Dalvik wipe etc will not work. Very odd.
As a last resort I downloaded the official 4.2.2 image but the toolkit cannot flash it and it displays:
Starting Flash Process..
Flashing Bootloader Image..
sending 'bootloader' (2188 KB)...
OKAY [ 0.140s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.156s
An Error Occured
I am out of ideas so any suggestions are welcome.
Click to expand...
Click to collapse

Don't use a toolkit, use the guide posted in the general section, toolkits are often very faulty as they only tend to work on working devices
Sent from my Nexus 4 using xda app-developers app

Same problem here, tried flashing everything through fastboot,
"fastboot flash recovery recovery-twrp-2.5.0.0-mako.img
sending 'recovery' (7510 KB)...
OKAY [ 0.473s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 0.479s"
Anything I flash I get the same response.
Any help would be appreciated

This is likely an emmc hardware failure
I've seen something very similar happen a couple of times with people on the one x.
Bootloader magically relocked itself. All partitions only read only. Unable to flash anything or issue lock/unlock commands
Sent from my Nexus 4 using xda app-developers app

highessupremacy said:
Same problem here, tried flashing everything through fastboot,
"fastboot flash recovery recovery-twrp-2.5.0.0-mako.img
sending 'recovery' (7510 KB)...
OKAY [ 0.473s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 0.479s"
Anything I flash I get the same response.
Any help would be appreciated
Click to expand...
Click to collapse
I'm having the exact same issue. Going to try to warranty it but since it the bootloader can't be relocked I have the feeling I'm screwed.

remote flash write failure
Same issue here.
My phone was unlocked and rooted, with stock firmware. I haven't made any changes to my phone for months since I re-rooted after 4.2.2 was released.
Had some apps crashing yesterday afternoon, not a big deal I thought, I'll just reboot. When I rebooted, the phone got stuck on the nexus boot screen - left it for hours and nothing.
Tried clearing the cache and doing a factory reset, no effect at all. Today, I tried reflashing, erased all the partitions first, but couldn't flash anything. Tried stock firmware first, but also custom recovery partitions and custom boot roms. Nothing.
Same issue here. Can't flash anything, I always get "FAILED (remote: flash write failure)" I also cannot re-lock the bootloader. I guess I will have to send it back for warranty repair to Google/LG?
This is the only thread I could find on this issue, I wonder if some recent app update broke my N4?

nothing to add besides same issue here. I got a google services failed message that I couldn't clear so I turned off my phone and then stuck on X. Haven't even installed a new app or anything in a couple of weeks. I have tried command prompt method and toolkit and both give flash write failure. I have cleared everything via command prompt and same result. Always told you cannot brick a Nexus...

Did you try to connect via adb after fastbooting to CWM (or even on X logo)?
We could compare our kernel logs then, hope it might clarify something...

Had any luck this far? I've got my nexus bootloader unlocked but not rooted, and I fear it will happen to me too.

Same problem here.
I believe I was able to fastboot erase /userdata but every 'flash' command fails. I am able to relock it though so I will try to send it in.
Good thing I kept my Galaxy Nexus and I was able to fit my micro SIM into it

Am I screwed?
Hey guys, another affected Nexus 4 user checking in. Same exact symptoms: was charging, checked something on it, saw a cascade of force closes. Shut it down, then it wouldn't boot past the Google screen. At one point I got it past that to the X screen, but it was stuck there indefinitely (for hours).
I'm running stock 4.2.2 with an unlocked bootloader. Same issues when trying to do anything over fastboot. Had the same idea to flash back to stock with no luck.
So... am I just screwed out of a phone? Or has anyone had luck getting it replaced?

This sounds like an simular issues my LG optimus G had. I would have to flash the misc.img in fastboot to get it to work again due to the misc partition getting corrupt Has anyone tried that yet?
Sent from my HTC One using Tapatalk 4 Beta

Just got off the phone with Google Play support. They had me run through a few tests (boot to fastboot, go into recovery, try booting from there; boot to fastboot, go into recovery, factory reset, reboot). Same thing: stuck on the "x" screen. I mentioned I wasn't rooted, but they didn't ask about the bootloader being unlocked. They went ahead and treated it as a normal in-warranty RMA. They're sending a new Nexus 4, and then I send the defective one back once it arrives.
If you have this issue with a Nexus 4 bought from Google Play, I suggest you call Google Play hardware support at (855) 836-3987. They were super friendly and helpful. While I'm bummed something went wrong with my phone, I'm glad I don't have to buy a new one.
---------- Post added at 09:17 PM ---------- Previous post was at 09:14 PM ----------
XsMagical said:
This sounds like an simular issues my LG optimus G had. I would have to flash the misc.img in fastboot to get it to work again due to the misc partition getting corrupt Has anyone tried that yet?
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
I don't see a misc.img in the stock image from Google for the Nexus 4. But anything else I tried to do via fastboot failed, which I've never had before.

I had the same exact issue experienced with the original poster. The apps were crashing on me like crazy. I was at the dog park. I remember the only app that was being updated at that time was AirDroidv2 just literally like 2 minutes ago before the google apps started to go crazy. I started to shut it down and boot it back up. I got stuck on the "X" screen. after an hour, i went home and tried the toolkit. then i went manual with cmd. all i get is "FAILED (remote: flash write failure)" whenever i attempt to flash it.
after a while, the OS wasn't even booting up. No "google" logo or "X" logo. Only i got was the bootup into fastboot. Now it doesn't even power up unless i connect the usb.
curious, is anyone hearing any rattling sounds in their device and/or red led dot when connecting to usb? I fear it's a bad connection to the battery.

Count me in as one of the unlucky folks as well. I noticed my N4 was auto-updating some apps last night, then later when I went to pick it up I couldn't get the screen to turn on. Held down power until it rebooted, then was stuck at the Google logo and never got any farther. Bootloader mode works, trying to boot into recovery gives a black screen. Tried to re-flash recovery.img from stock but got the same error as others: "FAILED (remote: flash write failure)"
I called Play Support and they were helpful in getting the RMA process started. Unfortunately I expressed some concern about my cracked glass back affecting the return and the CSR mentioned that he'd have to escalate. (As a point of reference, my glass cracked a few months ago). We discussed how common cracked glass backs are with the N4 and how I hoped it wouldn't affect my RMA as the device has been working fine for months. He's waiting to hear back from the specialist before we can move forward.
Really hoping that everything works out.
UPDATE: Warranty claim denied due to the broken glass. Not sure what my next step is. :/

Stuck at Google Screen won't do anything HELP

Ok I'm pretty good with Windows but I know nothing at all about Android. So I got this tablet off a site the guy said it needed a new motherboard which I never heard of. He said he didn't do anything to it it just stopped loading one day.
So I go all over and find all the little tricks to try and make it work. I did the power and volume button thing. I tried to reset it with the Rootkit program. I even tried to get SDK but that won't run on my PC for some reason.
Anyway what is happening is the tablet gets stuck on the Google word. I see nothing before that and it stays on that forever. I waited 15 minutes and nothing. When I try the rootkit program it gets stuck when it tries to reboot. The tablet just never turns back on. I can get it to boot into the bootloader screen. But nothing after that is functional. So what are my options here? If any. I'm hoping I can fix it. I am pretty quick at picking stuff up but this one is really stumping me.
Any help or advice or direction would be GREATLY appreciated. Thanks
Ok so when I do the Soft Brick Flash Stock + Unroot everything works up until the command prompt attempts to reboot. It turns off and never turns back on The last paragraph of the cmd prompt reads as follows and is what may be the issue. It reads
sending 'bootloader' <2100kb>
FAILED <remote: Bootloader is locked.>
finished. total time:0.145s
rebooting into bootloader...
OKAY [ 0.020s]
So I'm thinking it has something to do with this FAILED section as everything else works with no issues. Also after this I'm stuck at the < waiting for device > and my tablet doesn't power back on. I have a 100% charge and did all the driver stuff first.
Any ideas?????
Nexus 7 2012

Cr8zyJay said:
Ok I'm pretty good with Windows but I know nothing at all about Android. So I got this tablet off a site the guy said it needed a new motherboard which I never heard of. He said he didn't do anything to it it just stopped loading one day.
So I go all over and find all the little tricks to try and make it work. I did the power and volume button thing. I tried to reset it with the Rootkit program. I even tried to get SDK but that won't run on my PC for some reason.
Anyway what is happening is the tablet gets stuck on the Google word. I see nothing before that and it stays on that forever. I waited 15 minutes and nothing. When I try the rootkit program it gets stuck when it tries to reboot. The tablet just never turns back on. I can get it to boot into the bootloader screen. But nothing after that is functional. So what are my options here? If any. I'm hoping I can fix it. I am pretty quick at picking stuff up but this one is really stumping me.
Any help or advice or direction would be GREATLY appreciated. Thanks
Ok so when I do the Soft Brick Flash Stock + Unroot everything works up until the command prompt attempts to reboot. It turns off and never turns back on The last paragraph of the cmd prompt reads as follows and is what may be the issue. It reads
sending 'bootloader' <2100kb>
FAILED <remote: Bootloader is locked.>
finished. total time:0.145s
rebooting into bootloader...
OKAY [ 0.020s]
So I'm thinking it has something to do with this FAILED section as everything else works with no issues. Also after this I'm stuck at the < waiting for device > and my tablet doesn't power back on. I have a 100% charge and did all the driver stuff first.
Any ideas?????
Nexus 7 2012
Click to expand...
Click to collapse
Try unlocking the bootloader. It says your bootloader is still locked.

riggerman0421 said:
Try unlocking the bootloader. It says your bootloader is still locked.
Click to expand...
Click to collapse
I did and it doesn't boot back up after it completes the unlock. The tablet just stays powered down. I am going to try and do it manually instead of the Root toolkit

LeEco Le 3 Pro - Phone in constant reboot loop

Hey guys,
Been looking around on the forum but couldn't find any info about this.
I recently purchased a Le 3 Pro and was actually working well. I had a few random reboots (I read this was something normal - happened in Snapchat, but after clearing the app cache all was well again).
Anyway, so today at work I noticed the phone just rebooted for no reason, but then it just kept rebooting and rebooting.
I have the stock Chinese rom (it's the X720 vesion by the way) so I have not done any rooting. Was planning to, but thought I'd give stock a run for its money.
So, not I'm stuck with a phone that's stuck in reboot mode.
I can get into fastboot and I tried flashing TWRP into Recovery, and that "seemed" to work (the command came back successful) however when going into recovery mode, it's just the LeEco Recovery and it doesn't do anything. So, I have to power cycle again and then gets stuck in the reboot cycle.
I don't think OEM unlocking was enabled, but seeing I can't get into the OS I can't check. The bootloader was unlocked upon arrival.
I turned the phone off (volume up and down + power button)
Now, I also tried putting the phone into the charger, (it was still at 85%-ish as far as I can remember) however it doesn't seem to be charging. So I'm thinking there may be a hardware issue.
However, maybe a software solution... never know, so if anybody DOES know - highly appreciated
Thx
EDIT: so I've been fiddling around using some guides on this forum... nothing...
C:\Users\Ryan\Desktop\LEMAX2>fastboot devices
403077b2 fastboot
C:\Users\Ryan\Desktop\LEMAX2>fastboot flash aboot emmc_appsboot.mbn
target reported max download size of 536870912 bytes
sending 'aboot' (787 KB)...
OKAY [ 0.048s]
writing 'aboot'...
OKAY [ 0.023s]
finished. total time: 0.079s
C:\Users\Ryan\Desktop\LEMAX2>fastboot oem unlock-go
...
OKAY [ 0.009s]
finished. total time: 0.010s
C:\Users\Ryan\Desktop\LEMAX2>fastboot oem device-info
...
(bootloader) Device product name: [le_zl1_whole_netcom]
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
(bootloader) Display panel:
OKAY [ 0.092s]
finished. total time: 0.094s
** NOTE --> this was always showing unlocked (even if not doing any of these steps).
C:\Users\Ryan\Desktop\LEMAX2>fastboot flash recovery twrp-3.1.0-0-x2.img
target reported max download size of 536870912 bytes
sending 'recovery' (59348 KB)...
OKAY [ 1.284s]
writing 'recovery'...
OKAY [ 0.407s]
finished. total time: 1.697s
Click to expand...
Click to collapse
This would normally allow me to boot into TWRP recovery. however it just takes me to the Stock Recovery (and does nothing - ie: there is no option to do anything).

Have you tried booting into TWRP instead of flashing it? Try "fastboot boot recovery twrp-3.1.0-0-x2.img"
EDIT: What recovery you are using?

Presterin said:
Have you tried booting into TWRP instead of flashing it? Try "fastboot boot recovery twrp-3.1.0-0-x2.img"
Click to expand...
Click to collapse
Yes, tried that as well. Afterwards I tried:
Fastboot reboot
And also just manually booting into Recovery straight from the Fastboot screen (volume up + power).
Both times it just takes me to the "standard" LeEco Recovery Screen (it just says LeEco, some Chinese text and "Recovery") and doesn't allow me to do anything.
Also, I tried multiple chargers, no sign of the phone being charged at all (no sounds, no on screen display, no LED).
So, basically all I can do is turn it on and watch it reboot over and over again, or go into Fastboot, do some commands (which all seem to do nothing - although I get an "OK" status) or go into the standard LeEco Recovery (even after flashing TWRP into Recovery).
I'm seriously starting to think this is just a Hardware malfunction. However, I've scoured the net and haven't really found a case like mine.

Are you trying to flash Le Max 2 recovery on Le Pro 3? I don't know if it should work, but I would try one from this forum meant for this phone. For example this: https://drive.google.com/file/d/0B7uXK7jfW17nZGRCWmFmZU9NVWs/view (link copied from official LineageOS13 thread)

Presterin said:
Are you trying to flash Le Max 2 recovery on Le Pro 3? I don't know if it should work, but I would try one from this forum meant for this phone. For example this: (link removed) (link copied from official LineageOS13 thread)
Click to expand...
Click to collapse
No. Actually my dad and girlfriend have the Le Max 2 and had to install a new ROM on one of them, hence the LEMAX2 directory (where I'm just centralizing the flash files).
Basically I just want the stock (China) rom for the X720 -as that seemed to be working perfectly for me... for now (well, not now.. but you know what I mean).

I would try clearing all the data from recovery. See if that gets it to "reset".
If that doesn't work you could see about getting a hold of an "update.zip", pushing it to the device and flashing it from the stock recovery to see if it gets it out of the loop.

slgooding said:
I would try clearing all the data from recovery. See if that gets it to "reset".
If that doesn't work you could see about getting a hold of an "update.zip", pushing it to the device and flashing it from the stock recovery to see if it gets it out of the loop.
Click to expand...
Click to collapse
thanks for the answer, would you mind pointing me in the direction of how to "clear the data from recovery"?
Also, I'm not sure if I tried, by ADB doesn't work in Fastboot (to push the zip). At the moment, even in stock recovery I can't do anything.
EDIT: so, home from work. I've had the phone OFF for about 12 hours now. Plugged it in to charger and now I get an LED. Boots up normally, but battery was at 0%. I have no idea what's going on or why it now works, or even why the battery is at 0% (it was at 85% or so when it "crashed" yesterday I believe). Is this a known issue by chance? Or does this seem like a one off type of thing?

Ryanx0r said:
No. Actually my dad and girlfriend have the Le Max 2 and had to install a new ROM on one of them, hence the LEMAX2 directory (where I'm just centralizing the flash files).
Basically I just want the stock (China) rom for the X720 -as that seemed to be working perfectly for me... for now (well, not now.. but you know what I mean).
Click to expand...
Click to collapse
Can't get over "x2" in recovery image file, it points to Le Max 2 recovery.

Ryanx0r said:
thanks for the answer, would you mind pointing me in the direction of how to "clear the data from recovery"?
Also, I'm not sure if I tried, by ADB doesn't work in Fastboot (to push the zip). At the moment, even in stock recovery I can't do anything.
EDIT: so, home from work. I've had the phone OFF for about 12 hours now. Plugged it in to charger and now I get an LED. Boots up normally, but battery was at 0%. I have no idea what's going on or why it now works, or even why the battery is at 0% (it was at 85% or so when it "crashed" yesterday I believe). Is this a known issue by chance? Or does this seem like a one off type of thing?
Click to expand...
Click to collapse
There are some odd issues with this phone and charging. I'm not sure why it would bootloop and then die, only to charge and boot up again finally. Consider yourself fortunate that it works now! I ordered an Anker charger off of amazon and now use that for quick charging instead of the stock charger just in case...

What is the solution for this?
Ryanx0r said:
Yes, tried that as well. Afterwards I tried:
Fastboot reboot
And also just manually booting into Recovery straight from the Fastboot screen (volume up + power).
Both times it just takes me to the "standard" LeEco Recovery Screen (it just says LeEco, some Chinese text and "Recovery") and doesn't allow me to do anything.
Also, I tried multiple chargers, no sign of the phone being charged at all (no sounds, no on screen display, no LED).
So, basically all I can do is turn it on and watch it reboot over and over again, or go into Fastboot, do some commands (which all seem to do nothing - although I get an "OK" status) or go into the standard LeEco Recovery (even after flashing TWRP into Recovery).
I'm seriously starting to think this is just a Hardware malfunction. However, I've scoured the net and haven't really found a case like mine.
Click to expand...
Click to collapse
Can you reply me as soon as possible the solution for the constant reboots.

shivaraju07 said:
Can you reply me as soon as possible the solution for the constant reboots.
Click to expand...
Click to collapse
No solution. It "died" again (and to think I only used it for about 2 days).
I got into contact with the seller on Ali Express, I was told to send it back so they could look into it.
But Ali Express paid me back (while the seller was still looking into the problem). I didn't 'really' want my money back, just wanted the phone and an explanation - however, once I was paid back, the RMA was stopped and I was told to place a new order. Trying to do so, resulted in the seller letting me know that they no longer make the LeEco Pro 3.
So... I just went for OnePlus 5 instead - great phone

Ryanx0r said:
however, once I was paid back, the RMA was stopped and I was told to place a new order. Trying to do so, resulted in the seller letting me know that they no longer make the LeEco Pro 3.
Click to expand...
Click to collapse
I've read that LeEco stopped making phones. What they sell are the remaining stock, that it.

ZeblodS said:
I've read that LeEco stopped making phones. What they sell are the remaining stock, that it.
Click to expand...
Click to collapse
It's a real shame, because they're actually really good phones. My girlfriend has one and is really happy with it. It's the LeMax 2, but still a nice piece of (cheap, but great quality) hardware.

I have leeco le s3. After update Google Play Services, my phone always restarted continuosly when using GPS. Is that same with your issue?

InitialDS said:
I have leeco le s3. After update Google Play Services, my phone always restarted continuosly when using GPS. Is that same with your issue?
Click to expand...
Click to collapse
Have you solved the problem?

Google Pixel XL October Factory/OTA Images Available + Boot image

Google Pixel XL October Factory and OTA Images are available to download with 4 functional updates and no security fixes.
OTA: https://dl.google.com/dl/android/aosp/marlin-ota-ppr2.181005.003-469ae02d.zip
Factory: https://dl.google.com/dl/android/aosp/marlin-ppr2.181005.003-factory-59b2d3dd.zip
Boot image on my Google Drive: https://drive.google.com/file/d/1-lVIwMO6y-8lBHm9AnPVV6M0i3EO6flb/view?usp=drivesdk
Changes:
Code:
- Improved performance for certain protected media formats (Pixel 2, Pixel 2 XL)
- Improved stability when using Android Auto (Pixel 2, Pixel 2 XL)
- Improved fast-charging behavior for Pixel devices (Pixel, Pixel XL)
- Modified Call Screening behavior when using Maps Navigation (All Pixels)
October security bulletin: https://source.android.com/security/bulletin/pixel/2018-10-01
So who's ready to fast charge on Pie?

unfortunately, the incremental OTA update bricked my phone. Don't see anything posted about it yet. Sucks being first sometimes.

kentexcitebot said:
Google Pixel XL October Factory and OTA Images are available to download with 4 functional updates and no security fixes...
Changes:
Code:
- Improved performance for certain protected media formats (Pixel 2, Pixel 2 XL)
- Improved stability when using Android Auto (Pixel 2, Pixel 2 XL)...[/QUOTE]
Pixel XL forum!
Click to expand...
Click to collapse

Pretty good fast charging

I started the OTA update before going to sleep and woke up in the morning with a black screen.
I thought the battery was drained (though it was connected to a working power brick during the night). So I connected it to another good charger and left it for around 2 hours alone. The Pixel Xl's screen is black. There is nothing on it no matter what I tried.
The device is not OEM unlocked so stock ROM on it.
I tried to hard reboot it but there is just vibration going on after 30s or so and then nothing.
When connected to a Windows 10 PC it will show eventually after several "normal" reboots / reboots with volume down a Android Bootloader Interface.
It is beieng recognised as "123456789012 fastboot". Typing "fastboot reboot" makes it disappear from WIndows 10 Device manager but nothing more. Screen is dead.
Since I'm not OEM unlocked, I've no idea how to flash anything. I tried the flash-all.bat from the factory image but it is not recognising the device as marlin but as 'msm8996'. WT...
Any ideas guys? Did I miss something?

Pretty sure you have to sideload in stock recovery if locked.
Sent from my Pixel XL using Tapatalk

How do I enter the stock recovery if the screen is off? I tried to press 2 times vol down and then power and other "blind" guesses but the only thing happened was that the bootloader disappeared from windows device manager.

rambobo said:
How do I enter the stock recovery if the screen is off? I tried to press 2 times vol down and then power and other "blind" guesses but the only thing happened was that the bootloader disappeared from windows device manager.
Click to expand...
Click to collapse
Power off phone disconnect USB cord, press and hold the power and volume down buttons until you see "Start", press Volume Up or down button until you see "Recovery mode".

rambobo said:
I started the OTA update before going to sleep and woke up in the morning with a black screen.
I thought the battery was drained (though it was connected to a working power brick during the night). So I connected it to another good charger and left it for around 2 hours alone. The Pixel Xl's screen is black. There is nothing on it no matter what I tried.
The device is not OEM unlocked so stock ROM on it.
I tried to hard reboot it but there is just vibration going on after 30s or so and then nothing.
When connected to a Windows 10 PC it will show eventually after several "normal" reboots / reboots with volume down a Android Bootloader Interface.
It is beieng recognised as "123456789012 fastboot". Typing "fastboot reboot" makes it disappear from WIndows 10 Device manager but nothing more. Screen is dead.
Since I'm not OEM unlocked, I've no idea how to flash anything. I tried the flash-all.bat from the factory image but it is not recognising the device as marlin but as 'msm8996'. WT...
Any ideas guys? Did I miss something?
Click to expand...
Click to collapse
Homeboy76 said:
Power off phone disconnect USB cord, press and hold the power and volume down buttons until you see "Start", press Volume Up or down button until you see "Recovery mode".
Click to expand...
Click to collapse
Sorry m8 but as I said above "There is nothing on it no matter what I tried." I am sending the phone back now, sadly. Bought it in June so "lucky" me...

rambobo said:
Sorry m8 but as I said above "There is nothing on it no matter what I tried." I am sending the phone back now, sadly. Bought it in June so "lucky" me...
Click to expand...
Click to collapse

Still Waiting
I still have not received the Oct update, Is this normal?

it ended up being this
The beta program didn't unroll everyone I had to go to the website and do it manually. I got the update immediately after that.

Do we have a TWRP flashable?

You can flash the ota in twrp. Just be sure to flash twrp again before booting or you will lose it.
Sent from my Pixel XL using Tapatalk

sewey said:
I still have not received the Oct update, Is this normal?
Click to expand...
Click to collapse
Do this:
sewey said:
it ended up being this
The beta program didn't unroll everyone I had to go to the website and do it manually. I got the update immediately after that.
Click to expand...
Click to collapse
Thanks for the tip, had the same exact situation

Factory Image
Factory image isn't working? I don't remember it updating the bootloader in other updates. It just fails everytime. Could it be because I'm going from August to October? I'm using the stock factory image instead of the verizon one on my Verizon Pix XL. I don't believe it should matter. I uninstalled Magisk first and took off my pin. IDK.

perfectswanson said:
Factory image isn't working? I don't remember it updating the bootloader in other updates. It just fails everytime. Could it be because I'm going from August to October? I'm using the stock factory image instead of the verizon one on my Verizon Pix XL. I don't believe it should matter. I uninstalled Magisk first and took off my pin. IDK.
Click to expand...
Click to collapse
error: cannot load 'bootloader-marlin-8996-012001-1804121206.img'
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.011s
error: cannot load 'radio-marlin-8996-130181-1806061856.img'
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 5.003s
W/ ( 9772): Unable to open 'image-marlin-ppr2.180905.006.zip': No such file or directory
error: failed to open zip file 'image-marlin-ppr2.180905.006.zip': I/O Error
Press any key to exit...
I checked the file checksum sha256. File isn't corrupt this time. I have no idea. I pretty much get the same message every time whether it's the October update or Sept. I'm on August.
---------- Post added at 01:22 AM ---------- Previous post was at 01:18 AM ----------
perfectswanson said:
error: cannot load 'bootloader-marlin-8996-012001-1804121206.img'
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.011s
error: cannot load 'radio-marlin-8996-130181-1806061856.img'
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 5.003s
W/ ( 9772): Unable to open 'image-marlin-ppr2.180905.006.zip': No such file or directory
error: failed to open zip file 'image-marlin-ppr2.180905.006.zip': I/O Error
Press any key to exit...
I checked the file checksum sha256. File isn't corrupt this time. I have no idea. I pretty much get the same message every time whether it's the October update or Sept. I'm on August.
Click to expand...
Click to collapse
Got new platform tools...
D:\Root Stuff\platform-tools_r28.0.1-windows\platform-tools>flash-all.bat
Sending 'bootloader' (32384 KB) FAILED (Write to device failed (Unknown error))
Finished. Total time: 15.009s
rebooting into bootloader FAILED (Write to device failed (Unknown error))
Finished. Total time: 5.005s
Sending 'radio' (57140 KB) FAILED (Write to device failed (Unknown error))
Finished. Total time: 15.010s
rebooting into bootloader FAILED (Write to device failed (Unknown error))
Finished. Total time: 5.004s
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
getvar:version-bootloader FAILED (Write to device failed (Unknown error))
fastboot: error: requirements not met!
Press any key to exit...

Have you tried a different cable/ USB port ?

sewey said:
it ended up being this
The beta program didn't unroll everyone I had to go to the website and do it manually. I got the update immediately after that.
Click to expand...
Click to collapse
did it wipe your phone?

redskykiter said:
did it wipe your phone?
Click to expand...
Click to collapse
No, it did not