I apologize for my n00b-ness. I went to Windows Phone (yeah, go ahead and laugh) for a little over a year, and am somewhat out of the rooting scene.
So I installed the TWRP 2.7.0.3 recovery based on the thread in this sub-forum here:
http://forum.xda-developers.com/showthread.php?t=2698134
Everything appears to have worked:
Code:
C:\android-sdk\sdk\platform-tools>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.247s]
finished. total time: 0.247s
C:\android-sdk\sdk\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 1830711296 bytes
sending 'recovery' (12496 KB)...
OKAY [ 1.212s]
writing 'recovery'...
OKAY [ 0.763s]
finished. total time: 1.974s
C:\android-sdk\sdk\platform-tools>
I'm not sure what to do from here. When my phone boots, I hold power to reboot, and I don't see any "reboot into recovery" option like I've seen on past phones. Is there another way I should access recovery so that I can finish rooting my phone? Or should flashing TWRP have effectively rooted it?
Thanks for any help.
ChodeNode said:
I apologize for my n00b-ness. I went to Windows Phone (yeah, go ahead and laugh) for a little over a year, and am somewhat out of the rooting scene.
So I installed the TWRP 2.7.0.3 recovery based on the thread in this sub-forum here:
http://forum.xda-developers.com/showthread.php?t=2698134
Everything appears to have worked:
Code:
C:\android-sdk\sdk\platform-tools>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.247s]
finished. total time: 0.247s
C:\android-sdk\sdk\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 1830711296 bytes
sending 'recovery' (12496 KB)...
OKAY [ 1.212s]
writing 'recovery'...
OKAY [ 0.763s]
finished. total time: 1.974s
C:\android-sdk\sdk\platform-tools>
I'm not sure what to do from here. When my phone boots, I hold power to reboot, and I don't see any "reboot into recovery" option like I've seen on past phones. Is there another way I should access recovery so that I can finish rooting my phone? Or should flashing TWRP have effectively rooted it?
Thanks for any help.
Click to expand...
Click to collapse
Press power restart when it goes off hold power volume down
Or download twrp app from play store
ChodeNode said:
I apologize for my n00b-ness. I went to Windows Phone (yeah, go ahead and laugh) for a little over a year, and am somewhat out of the rooting scene.
So I installed the TWRP 2.7.0.3 recovery based on the thread in this sub-forum here:
http://forum.xda-developers.com/showthread.php?t=2698134
Everything appears to have worked:
Code:
C:\android-sdk\sdk\platform-tools>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.247s]
finished. total time: 0.247s
C:\android-sdk\sdk\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 1830711296 bytes
sending 'recovery' (12496 KB)...
OKAY [ 1.212s]
writing 'recovery'...
OKAY [ 0.763s]
finished. total time: 1.974s
C:\android-sdk\sdk\platform-tools>
I'm not sure what to do from here. When my phone boots, I hold power to reboot, and I don't see any "reboot into recovery" option like I've seen on past phones. Is there another way I should access recovery so that I can finish rooting my phone? Or should flashing TWRP have effectively rooted it?
Thanks for any help.
Click to expand...
Click to collapse
Why don't you use one of the toolboxes:
http://forum.xda-developers.com/showthread.php?t=2699065
b0gd4n said:
Why don't you use one of the toolboxes:
http://forum.xda-developers.com/showthread.php?t=2699065
Click to expand...
Click to collapse
Cause toolkits are lazy and it should be encouraged to do everything manually where possible so that you understand what's actually happening so you have the knowledge to fix any possible issues
Just my 2p...
It appears the issue was my n00bness. I assumed the hboot menu would be replaced with the recovery screen. Didn't see the recovery option there in the list. Of course I use that menu item and I'm good to go.
Yeah - I'm dumb.
Was running latest slimkat for flo (2013) no problem.
Looking to start running with the Lollipop kids; figured a full wipe and start over would be great..
So far not much luck.
I couldn't get fastboot to recognize my device on linux (archlinux..)
Win 7 saw it just fine..
C:\Users\TempUser\Downloads\razor-lrx22c-factory-a9c6e55f>flash-all.bat
sending 'bootloader' (3911 KB)...
OKAY [ 0.140s]
writing 'bootloader'...
OKAY [ 1.643s]
finished. total time: 1.783s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 818480772 bytes
error: update package missing system.img
Press any key to exit...
adb version says 1.0.32 - can not find a way to get fastboot version..
Still have access to twrp 2.8.0.1, device still shows as unlocked, and it looks like slimkat still boots..
Should I just forego the system image?
Thanks in advance..
Just to share..
I've moved on from this..
Downloaded latest twrp (2.8.0.x) pushed that via fastboot.
Went into recovery, confirmed version.. attempted a quick adb push and adb sideload; sideload worked for small - failed for the 180MB Rom..
wiped device; rebooted recovery; adb push'd to /sdcard/, and installed from there.
Enjoying 5.0.2 with tons of space..
Thank you for reading.
Mystique said:
Was running latest slimkat for flo (2013) no problem.
Looking to start running with the Lollipop kids; figured a full wipe and start over would be great..
So far not much luck.
I couldn't get fastboot to recognize my device on linux (archlinux..)
Win 7 saw it just fine..
C:\Users\TempUser\Downloads\razor-lrx22c-factory-a9c6e55f>flash-all.bat
sending 'bootloader' (3911 KB)...
OKAY [ 0.140s]
writing 'bootloader'...
OKAY [ 1.643s]
finished. total time: 1.783s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 818480772 bytes
error: update package missing system.img
Press any key to exit...
adb version says 1.0.32 - can not find a way to get fastboot version..
Still have access to twrp 2.8.0.1, device still shows as unlocked, and it looks like slimkat still boots..
Should I just forego the system image?
Thanks in advance..
Click to expand...
Click to collapse
In case you run into the error again, a simple Google for this know problem: http://www.androidpolice.com/2014/1...-0-factory-images-heres-how-to-get-around-it/
Sent from my Nexus 5 using XDA Free mobile app
I have been trying to flash my tablet back to factory.. everything has failed, I can get into bootloader or it reboots to Google in white font with nothing else, besides the Unlock icon. I had it rooted before and it tried to update the OS then this happened. So i have tried multiple things, and friend software engineer even has tried helping, i have the adb and fastboot files and the factory image for the tablet but when i am done the flash-all.bat script it reboots to the white font Google. Any help!???
Also, When i run the flash-all script I see
sending 'bootloader' (3911 KB)...
OKAY [ 0.125s]
writing 'bootloader'...
OKAY [ 1.364s]
finished. total time: 1.505s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
the script continues.. then finishes with rebooting my device with the White font Google still.
I have also tried the commands manually one by one, and root kit tools. Any advice?
Okay, this might sound weird, but have you tried giving your Nexus 7 a good smack? Mine has been a bit stubborn lately, sometimes also getting stuck on the Google logo. For some reason, when I give it a hard smack on the back when it's stuck, it decides to continue the boot sequence. Otherwise, I'm not sure what would be wrong since you didn't get any errors.
tonytien said:
Okay, this might sound weird, but have you tried giving your Nexus 7 a good smack? Mine has been a bit stubborn lately, sometimes also getting stuck on the Google logo. For some reason, when I give it a hard smack on the back when it's stuck, it decides to continue the boot sequence. Otherwise, I'm not sure what would be wrong since you didn't get any errors.
Click to expand...
Click to collapse
You know I am so pissed off.....that worked. And I was flashing all afternoon and my software engineer buddy gave up he said he couldnt help me.. i wonder why.
Setting up the tablet now.. good grief. THANKS!
What... a smack could solve the problem?
Did you try reboot before I am wondering, because I have same problem.
cmtyresearch said:
What... a smack could solve the problem?
Did you try reboot before I am wondering, because I have same problem.
Click to expand...
Click to collapse
Yes it did. I reflashed the factory image and everything still had same issue until I gave it a smack!
Download script: HERE
Download Factory Images: HERE
Download ADB/Fastboot: Platform Tools
Download USB Drivers: USB Drivers -- Driver Installation Video
-----------------------------------------------------------------------------------------------------------------------------------------------------------
This script is for the UNLOCKED BOOTLOADER pixel2 / pixel2 XL, and will help:
Fix Bootloops
Flash both Slots A and B
Work with any Google-provided factory image
Detect bootloader and radio special *.img names automagically
(Optional): Unlock Bootloader and Critical
(Optional): Format Userdata
-----------------------------------------------------------------------------------------------------------------------------------------------------------
Instructions:
Extract factory image zip file, as well as the image zip file within it!
This will lead to ~21 .img files in the same folder, with the deuce-flash-all script!
SEE SCREENSHOT!!.
Once you have all these together, run the Deuce-Flash-All script. ( .bat for Windows, .sh for Linux)
-----------------------------------------------------------------------------------------------------------------------------------------------------------
If you are having issues with this script:
Verify you have the environment variable (path) set for adb and fastboot
Try a different USB port
Try a different cable (preferably USB A -> USB C)
Format Userdata in Stock Recovery
Boot plain factory image before doing mods like Locking Bootloader / Kernel / TWRP / Magisk
This was built for the 2 xl but I have modified it to work with the pixel 2.
The main thread, which has lots of troubleshooting Q/A is here:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Changelog:
06-13-2018: Added support for latest platform tools
01-14-2018: Fixed bug. Made unlocking optional to speed it up, combined scripts for taimen & walleye
01-09-2018: Removed support for locking bootloader, added hard-coded slot selections
12-26-2017: Added support for Pixel 2 (Walleye)
I have been using this on my walleye since v4, guess now we no longer get the errors for the critical unlock status.
Makes sense, thanks as always most beneficial tool besides adb itself for a pixel device!
Hey. When I boot my Pixel 2 XL I get a can’t find valid OS. Will this fix it?
It's possible ton unlock bootloader, install magisk / root without wipe the phone ?
Anyway, thanks for your great work !
Matt17000 said:
It's possible ton unlock bootloader, install magisk / root without wipe the phone ?
Anyway, thanks for your great work !
Click to expand...
Click to collapse
Unlocking the bootloader always wipes. Magisk, recovery, and other things will not.
You've saved me twice from a brick. Thank you.
Dude you are a freaking god send! THANK YOU!
Had anyone tested this with January 8.1 release? Just asking so I can update the top post. Working fine on XL
Deuces said:
Had anyone tested this with January 8.1 release? Just asking so I can update the top post. Working fine on XL
Click to expand...
Click to collapse
I am about to use it in 3 hrs. I am currently running dec patch with twrp and magisk. Ill try to sideload january patch soon.
I used it to recover from a softbrick, had an error on mac address 02:00 etc and fingerprint hardware, not sure if related to your Tool, but it did let me Boot back into system after everything else failed, all working again after factory flash with wipe
I modified the script to take away the locking section, as people can't seem to RTFM
Also included changes to hard-select the slot A/B and further warnings on relocking bootloader
Deuces said:
I modified the script to take away the locking section, as people can't seem to RTFM
Also included changes to hard-select the slot A/B and further warnings on relocking bootloader
Click to expand...
Click to collapse
Hi @Deuces, I wonder if you could take a look at this. I just tried running your script (third time so far). I used the latest Walleye script, made sure I had the latest fastboot and adb. Please see below...it looks like the script got as far as trying to write bootloader_b...then it got stuck at "waiting for any device" with the display blank. Eventually (after a long time) I gave up and unplugged the phone. I can't get it to turn on at ALL. Not by holding down power, not by using the key combo to get into fastboot...the phone just seems DEAD. I plug it into a charger, and nothing happens. Plug it back into PC, and the computer doesn't know that the phone has been plugged in. It's just not there in the Device Manager.
I tried following Google's steps to troubleshoot a phone that doesn't turn on. I did find that if I hold the power button down for about 30 seconds, I do feel the phone vibrate, and see a line across the display, like the few times that I've had to hard reboot. But that was it. Trying to get into fastboot mode, even holding the buttons for a long time, doesn't work.
Any idea what could have happened, or what I can do? The battery wasn't 100% full when I started, but it was at least at 85%. I'm sure the battery didn't die. I'm a bit freaked out, as I can't even get it to power on. Thanks in advance.
Deuces-flash-all-script-V4.3-Windows
for Walleye - Google Pixel 2
USE AT YOUR OWN RISK
Press any key to continue . . .
Make Sure your Device is in Fastboot Mode
(Power off, hold Volume-Down, hold Power)
Once you are in fastboot,
Press any key to continue . . .
Running Unlock
Look at your device,
press up arrow and Power to confirm
...
FAILED (remote: Device already : unlocked!)
finished. total time: 0.006s
This will say "failed" if already unlocked - ignore
Locating Bootloader and Radio Filenames
Flashing...
Setting current slot to 'a'...
OKAY [ 0.012s]
finished. total time: 0.014s
target reported max download size of 536870912 bytes
sending 'bootloader_a' (38644 KB)...
OKAY [ 1.189s]
writing 'bootloader_a'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 1.206s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.005s
target reported max download size of 536870912 bytes
sending 'radio_a' (60428 KB)...
OKAY [ 1.851s]
writing 'radio_a'...
(bootloader) Updating: modem @00001000 sz=03B01000
OKAY [ 0.690s]
finished. total time: 2.545s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.005s
Setting current slot to 'b'...
OKAY [ 0.015s]
finished. total time: 0.017s
target reported max download size of 536870912 bytes
sending 'bootloader_b' (38644 KB)...
OKAY [ 1.051s]
writing 'bootloader_b'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 1.069s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.005s
< waiting for any device >
JayBlack_686 said:
Hi @Deuces, I wonder if you could take a look at this. I just tried running your script (third time so far). I used the latest Walleye script, made sure I had the latest fastboot and adb. Please see below...it looks like the script got as far as trying to write bootloader_b...then it got stuck at "waiting for any device" with the display blank. Eventually (after a long time) I gave up and unplugged the phone. I can't get it to turn on at ALL. Not by holding down power, not by using the key combo to get into fastboot...the phone just seems DEAD. I plug it into a charger, and nothing happens. Plug it back into PC, and the computer doesn't know that the phone has been plugged in. It's just not there in the Device Manager.
I tried following Google's steps to troubleshoot a phone that doesn't turn on. I did find that if I hold the power button down for about 30 seconds, I do feel the phone vibrate, and see a line across the display, like the few times that I've had to hard reboot. But that was it. Trying to get into fastboot mode, even holding the buttons for a long time, doesn't work.
Any idea what could have happened, or what I can do? The battery wasn't 100% full when I started, but it was at least at 85%. I'm sure the battery didn't die. I'm a bit freaked out, as I can't even get it to power on. Thanks in advance.
Deuces-flash-all-script-V4.3-Windows
for Walleye - Google Pixel 2
USE AT YOUR OWN RISK
Press any key to continue . . .
Make Sure your Device is in Fastboot Mode
(Power off, hold Volume-Down, hold Power)
Once you are in fastboot,
Press any key to continue . . .
Running Unlock
Look at your device,
press up arrow and Power to confirm
...
FAILED (remote: Device already : unlocked!)
finished. total time: 0.006s
This will say "failed" if already unlocked - ignore
Locating Bootloader and Radio Filenames
Flashing...
Setting current slot to 'a'...
OKAY [ 0.012s]
finished. total time: 0.014s
target reported max download size of 536870912 bytes
sending 'bootloader_a' (38644 KB)...
OKAY [ 1.189s]
writing 'bootloader_a'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 1.206s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.005s
target reported max download size of 536870912 bytes
sending 'radio_a' (60428 KB)...
OKAY [ 1.851s]
writing 'radio_a'...
(bootloader) Updating: modem @00001000 sz=03B01000
OKAY [ 0.690s]
finished. total time: 2.545s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.005s
Setting current slot to 'b'...
OKAY [ 0.015s]
finished. total time: 0.017s
target reported max download size of 536870912 bytes
sending 'bootloader_b' (38644 KB)...
OKAY [ 1.051s]
writing 'bootloader_b'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 1.069s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.005s
< waiting for any device >
Click to expand...
Click to collapse
I've seen something similar as far as the phone not powering on. Technically tho, it was on but with a black screen.
Try holding VOL- and POWER for 30+ seconds to see if it powers off, then again to see if it comes back on.
I did read thoroughly and read that you've kinda tried this already, but after you get it to "power on" - do you get any return on the command:
fastboot devices
or
adb devices
?
Then, maybe try the new script i just updated - or tell me what OS you are running? if it's MAC / OSX, might wanna hold off.
Deuces said:
I've seen something similar as far as the phone not powering on. Technically tho, it was on but with a black screen.
Try holding VOL- and POWER for 30+ seconds to see if it powers off, then again to see if it comes back on.
I did read thoroughly and read that you've kinda tried this already, but after you get it to "power on" - do you get any return on the command:
fastboot devices
or
adb devices
?
Then, maybe try the new script i just updated - or tell me what OS you are running? if it's MAC / OSX, might wanna hold off.
Click to expand...
Click to collapse
Hi, thanks. I did try holding VOL - and power down for 30 seconds+. Actually, I did feel a vibration, but...nothing after. Couldn't get it to act like it was turning back on. Now that you mention it...I wonder if I did get it to turn on at some point during trying this over and over, because at times I saw the "scan line" appear across the screen briefly, like when I hard power off the device. But I've never seen the display light up at all, and nothing I've done has shown a device when issuing the "devices" command, either via fastboot or adb. I guess I need to screw around until I see that scan line, then it's "off." Then I've gotta get the thing to vibrate again, so it's "on." Then try seeing if I can run your script.
Boy am I glad I didn't try this late at night.
Oh, sorry, I'm on Windows 10.
Based on the return it looks like your bootloader got jacked up. I haven't seen that issue before. May want to get on chat with Google about an RMA.
Deuces said:
Based on the return it looks like your bootloader got jacked up. I haven't seen that issue before. May want to get on chat with Google about an RMA.
Click to expand...
Click to collapse
Sheeeeeeeit, just did that. Man...honestly, I might just go stock when I get this new one. Too much risk of mishaps, since I only keep the one phone around. Was just hoping to recover this one, as I'll be phone-less for a few days.
Side question - let's say I get the new phone, unlock the bootloader just in case, then don't do anything else, no rooting, etc. Do you know if that'll affect my ability to get OTAs actually over the air? I'm just bummed that every time there's an update, I've gotta go manually flash stuff and risk some shenanigans like this (and there's that persistent notification that doesn't go away unless I do so!). Should be easy, but I never had any luck with Google's flash-all script and always had to use yours to recover. Your script worked great...except for this time, something clearly went wrong (not pointing fingers, it's just how it goes).
Anyway, if you've got any other ideas, I'd try them out. Thanks for the responses thus far.
JayBlack_686 said:
Sheeeeeeeit, just did that. Man...honestly, I might just go stock when I get this new one. Too much risk of mishaps, since I only keep the one phone around. Was just hoping to recover this one, as I'll be phone-less for a few days.
Side question - let's say I get the new phone, unlock the bootloader just in case, then don't do anything else, no rooting, etc. Do you know if that'll affect my ability to get OTAs actually over the air? I'm just bummed that every time there's an update, I've gotta go manually flash stuff and risk some shenanigans like this (and there's that persistent notification that doesn't go away unless I do so!). Should be easy, but I never had any luck with Google's flash-all script and always had to use yours to recover. Your script worked great...except for this time, something clearly went wrong (not pointing fingers, it's just how it goes).
Anyway, if you've got any other ideas, I'd try them out. Thanks for the responses thus far.
Click to expand...
Click to collapse
If you can't get into bootloader, there's nothing I can do. There's some talk about using LG's downloader mode but LG has not released an image for it that I know of.
You can see this download mode by: Powered Off. Hold Vol+, insert USB cable connected from laptop.
If you have an unlocked bootloader, play store knows it - and some apps (netflix for example) - won't allow you to download their app from the play store. You could sideload the apk and it works fine, but still no updates from play store.. All of the apps I have work fine unlocked, minus Netflix.
You could disable OTA updates via developer options so that the notification goes away.
If you decide to stay stock, you could technically leave the bootloader locked, but the "allow oem unlocking" enabled in developer options. However, if something corrupts your OS, it's unlikely you'd be able to issue the unlocking commands from bootloader. That's the main reason I stay unlocked.
I've got the process down for upgrades myself. Download image, unzip, unzip the image within that, run my deuce-flash-all script. Boot up to Android once. Reboot to bootloader, fastboot boot twrp img, install magisk, reboot.
I do not flash twrp zip b/c it has been problematic for touchscreen drivers, and I'm around a computer anyway when doing these things.
The only reason I root is to use adaway. Every time I try to get used to stock, I hate using my phone because of ads.
I've tried the no-root-required VPN adblockers, but they drain battery.
Deuces said:
If you can't get into bootloader, there's nothing I can do.
...
If you have an unlocked bootloader, play store knows it - and some apps (netflix for example) - won't allow you to download their app from the play store. You could sideload the apk and it works fine, but still no updates from play store.. All of the apps I have work fine unlocked, minus Netflix.
...
The only reason I root is to use adaway. Every time I try to get used to stock, I hate using my phone because of ads.
I've tried the no-root-required VPN adblockers, but they drain battery.
Click to expand...
Click to collapse
Hey, thanks. I hear you. Oddly, I could've sworn that I had Netflix installed and updating on my bootloader-unlocked Pixel 2. Can't verify, sadly!
JayBlack_686 said:
Hey, thanks. I hear you. Oddly, I could've sworn that I had Netflix installed and updating on my bootloader-unlocked Pixel 2. Can't verify, sadly!
Click to expand...
Click to collapse
I can verify! I watch Netflix on my phone at work, downloaded from the play store on a pixel 2 unlocked, twrp installed and rooted with magisk. Not sure why everyone is having problems with it.
I took the Dec 2019 OTA, by uninstalling Magisk, took the OTA ( did not reboot) and where I think i went wrong was when re-patching the boot.img i choose to install on inactive slot.
I have since tried many other things to recover from this. Is it possible to fix it without wiping and losing my data?
I have myself at No vaild slot to boot
EDIT: No I am on Enter Reason: error boot prepare
=========================================
After 10hrs of throwing crap at the wall and having nothing stuck. I just started over with the Dec 2019 factory image.
Androider4Life said:
I took the Dec 2019 OTA, by uninstalling Magisk, took the OTA ( did not reboot) and where I think i went wrong was when re-patching the boot.img i choose to install on inactive slot.
I have since tried many other things to recover from this. Is it possible to fix it without wiping and losing my data?
I have myself at No vaild slot to boot. EDIT: No I am on Enter Reason: error boot prepare
Click to expand...
Click to collapse
What happens when you flash the stock boot.img? Have you tried fastboot flashing the full image (not OTA) removing the wipe flag (-w) from the flash-all.bat? If that doesn't work, your data may already be gone or corrupt. Next step, flash full image and allowing data wipe.
v12xke said:
What happens when you flash the stock boot.img? Have you tried fastboot flashing the full image (not OTA) removing the wipe flag (-w) from the flash-all.bat? If that doesn't work, your data may already be gone or corrupt. Next step, flash full image and allowing data wipe.
Click to expand...
Click to collapse
============================================================
boot.img flash, Phone reboots to White G Screen and sits there. If I hold the power button till it reboots it goes back to the White G Screen and sits there.
C:\Users\Clint\Desktop\Pixel\December\platform-tools>fastboot flash boot boot.img
Sending 'boot_a' (65536 KB) OKAY [ 2.835s]
Writing 'boot_a' OKAY [ 0.595s]
Finished. Total time: 3.705s
C:\Users\Clint\Desktop\Pixel\December\platform-tools>fastboot reboot
Rebooting OKAY [ 0.045s]
Finished. Total time: 0.052s
Androider4Life said:
============================================================
boot.img flash, Phone reboots to White G Screen and sits there. If I hold the power button till it reboots it goes back to the White G Screen and sits there.
C:\Users\Clint\Desktop\Pixel\December\platform-tools>fastboot flash boot boot.img
Sending 'boot_a' (65536 KB) OKAY [ 2.835s]
Writing 'boot_a' OKAY [ 0.595s]
Finished. Total time: 3.705s
C:\Users\Clint\Desktop\Pixel\December\platform-tools>fastboot reboot
Rebooting OKAY [ 0.045s]
Finished. Total time: 0.052s
Click to expand...
Click to collapse
Assuming that was the stock boot.img extracted from the Google image, you could also try flashing the same to both slots before trying flashing the full factory image, removing the wipe flag first. Some people like to update using OTA's. I ALWAYS flash the full image every month on my Pixel devices and have never had an issue.
v12xke said:
Assuming that was the stock boot.img extracted from the Google image, you could also try flashing the same to both slots before trying flashing the full factory image, removing the wipe flag first. Some people like to update using OTA's. I ALWAYS flash the full image every month on my Pixel devices and have never had an issue.
Click to expand...
Click to collapse
======================================================================================
Back to setting on the White G screen.
C:\Users\Clint\Desktop\Pixel\December\platform-tools>fastboot flash boot --slot all boot.img
Sending 'boot_a' (65536 KB) OKAY [ 2.635s]
Writing 'boot_a' OKAY [ 0.623s]
Sending 'boot_b' (65536 KB) OKAY [ 3.126s]
Writing 'boot_b' OKAY [ 0.618s]
Finished. Total time: 7.624s
C:\Users\Clint\Desktop\Pixel\December\platform-tools>fastboot reboot
Rebooting OKAY [ 0.033s]
Finished. Total time: 0.071s
C:\Users\Clint\Desktop\Pixel\December\platform-tools>
Flashing the December Full image (removing the -w) I am back to the Error Reason: no valid slot to boot. I have attached the log
See my thread a couple of posts down about the December update for the fix.
DOMF said:
See my thread a couple of posts down about the December update for the fix.
Click to expand...
Click to collapse
I have read thru it and tried somethings with no luck..which part fixed it for you?
If I could just get to a point that I can access my internal storage to back up some stuff, I'd be ok full wiping after that.
After 10hrs of throwing crap at the wall and having nothing stuck. I just started over with the Dec 2019 factory image.
flash-all.sh without -w, adb rebbot bootloader, fastboot boot image-newpixel3xlRemove.img, adb reboot bootloader, fastboot flash boot magisk-patched.img
DOMF said:
flash-all.sh without -w, adb rebbot bootloader, fastboot boot image-newpixel3xlRemove.img, adb reboot bootloader, fastboot flash boot magisk-patched.img
Click to expand...
Click to collapse
Having the same issue.
What is ''image-newpixel3xlRemove.img''