Develop Bugs

[Q] KF2 "data too large" error when trying to recover

I have a 'demo' KF2 that is currently stuck at the white and yellow Kindle Fire logo... I'm trying to use KFFirstAide to restore it to factory, then will try to root/install TWRP/install JB. I have a factory cable (which is how I was able to get it into fastboot) and the ADB drivers appear to be installed correctly.
I am seeing the following error message when doing the restore to factory:
sending 'system' (777953 KB)...
FAILED (remote: data too large)
Any ideas on how to proceed? I get a similar message trying to restore 10.2.3, the system.img is even larger on that version.
Here is the complete output from KFFirstAide:
sending 'boot' (8192 KB)...
OKAY [ 2.059s]
writing 'boot'...
OKAY [ 0.749s]
finished. total time: 2.808s
sending 'recovery' (8192 KB)...
OKAY [ 2.044s]
writing 'recovery'...
OKAY [ 0.733s]
finished. total time: 2.792s
sending 'system' (777953 KB)...
FAILED (remote: data too large)
finished. total time: 0.016s
erasing 'userdata'...
OKAY [116.502s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.016s]
erasing 'cache'...
OKAY [ 30.926s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.010s]
finished. total time: 147.454s
rebooting...
finished. total time: 0.000s
**************************************
* Success!!! The Kindle Fire 2 7" *
*Restored To Software Version 10.2.1 *
**************************************
Press any key to continue . . .

You need to obtain a "sparse" system image OR if you have adb access you can push your system.IMG to the sdcard and use the DD command to write it to your system partition
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Fixed!
I fought this all day, trying to load/reload with the KFFirstAide utility... After a while I tried to load TWRP on it and was able to boot to TWRP and wipe everything. I was then able to mount the device to Windows, copy a JB ROM to it and attempt to flash it. When the flash failed with an error (something like 'can't find tablet') I then realized I had a 1st gen Kindle, instead of what the ad stated on Ebay. Installed the correct JB and all is well... I guess 'data too large' was trying to tell me something
Not a bad deal for $31, but I really wanted 8G.
If I had to do this all over again (and knew it was a 1st gen Demo Kindle), I'd have done it this way:
Install TWRP
Wipe everything (cache, dalvik, system, sdcard)
Mount SDcard with TWRP, format with windows, copy JB and Gapps to SDcard
Install JB and Gapps
enjoy

Need sparse image
I have a mac and am having trouble mounting the system.img to create a sparse image. Is there anyone who has the sparse system.img file? I've been reading and trying to figure this out for 3 days now and any help would be appreciated.

zoey said:
I have a mac and am having trouble mounting the system.img to create a sparse image. Is there anyone who has the sparse system.img file? I've been reading and trying to figure this out for 3 days now and any help would be appreciated.
Click to expand...
Click to collapse
If you download just the batch file from here and open it as text you will find the urls under option1, i believe
http://forum.xda-developers.com/showthread.php?t=2096888
--
Sent from my Kindle Fire 2, CM 10.1

mindmajick said:
If you download just the batch file from here and open it as text you will find the urls under option1, i believe
http://forum.xda-developers.com/showthread.php?t=2096888
--
Sent from my Kindle Fire 2, CM 10.1
Click to expand...
Click to collapse
I downloaded that file and it still says its too big to flash

zoey said:
I downloaded that file and it still says its too big to flash
Click to expand...
Click to collapse
Hm... What is the exact command you are using?
--
Sent from my Kindle Fire 2, CM 10.1

KF2?
zoey said:
I downloaded that file and it still says its too big to flash
Click to expand...
Click to collapse
Are you sure you have a KF2? I had the same 'data too large' error, my tablet was NOT a KF2 (even though the seller on Ebay said it was).
I looked around a bit on Google, found some ways to tell which is which:
On an original KF, there is a 'gear' in the upper left corner you tap on for settings. On a KF2 or HD, you have to 'pull down' the top bar for settings.
On your Home screen, if the first link is Newsstand, you have a first gen KF. If the first link is shop, you have a 2nd Gen.
KF1 version is 6.x.x, KF2 version is 10.x.x
Although none of the above may help you much now that it's non-operational
Larry

Might help him and you. There are a lot more recovery options for the kf1
--
Sent from my Kindle Fire 2, CM 10.1

I know its a kinldle fire 2 it was on 10.2.6 before I started messing with it. I have another kf2 that I rooted and installed cm10.1. I've pulled the images from that and pushed them to this one. All the files worked accept the system.img. I was even able to boot back into twrp but every time I push a file to it it reboots back into recovery automatically when it is finished pushing the file and the file is gone. I know it is pushing the file because I can see it in twrp file manager as it's being pushed through. I've messed with a bunch of different devices and have always been able to bring them back when I've screwed up but this one has got me stumped.

Try to wipe cache, wipe system, I even had to wipe the sdcard and 'android secure' when I hosed my KF.... Then try to mount USB via TWRP. If windoze wants to format the KF2, I would let it do that also.
You have TWRP installed, you're 90% there... I'm sure someone here can figure this out.
Sent from my Kindle Fire that thinks it's a Nexus 7 using xda app-developers app

Yea I tried but I can't mount, wipe or format anything from twrp adb or fastboot I will keep trying though
---------- Post added at 06:41 AM ---------- Previous post was at 05:58 AM ----------
mindmajick said:
Hm... What is the exact command you are using?
--
Sent from my Kindle Fire 2, CM 10.1
Click to expand...
Click to collapse
fastboot -i 0x1949 flash system system.img I've flashed boot and recovery but system doesn't want to work for me. I have a backup of the system.IMG from cm10 and the system file from kf2 10.2.3 and one more I downloaded from here also but can't get any to work.

The only one that will work is the "sparse image" downloaded from the batch file.
You SURE you tried that one with the command above?
AND you downloaded the system.img for the kf2 and not another device (kf2 7" hd for example). Have you tried both the 10.2.3 version and the 10.2.1?
Last question- you're sure it's a kf2, not a kf1 or kfhd? What's the model number on the back of the device?
I know you tried adb... What about adb sideload in the twrp menu? It has to be a flashable zip file..
--
Sent from my Kindle Fire 2, CM 10.1

If you can't wipe via TWRP, I don't think anything else is going to work until you fix that... Can you try mounting the USB via TWRP and trying it on another computer? You won't need to install any drivers or adb stuff on the other computer.
Maybe do a factory wipe, or try installing the latest TWRP. Before doing anything drastic I would have a fast boot cable on hand (I did a factory wipe but can't recall if if cleared TWRP too).
Sent from my KF that thinks its a Nexus 7

Usb mount works on TWRP? I was under the impression it didn't work. Hence the suggestion to adb sideload the cm10.1 rom
If he can't do basic functions on TWRP... dunno. Very weird
I'm at a loss
--
Sent from my Kindle Fire 2, CM 10.1

USB works for me
mindmajick said:
Usb mount works on TWRP? I was under the impression it didn't work. Hence the suggestion to adb sideload the cm10.1 rom
If he can't do basic functions on TWRP... dunno. Very weird
I'm at a loss
Click to expand...
Click to collapse
USB mount via TWRP works for me.... I've used it with versions 2.4.1.0 and 2.4.3.0
You can only see the SDcard, I've copied ROMs to it and used TWRP to install.
I agree, if he can't do a wipe something is really messed up. I'd try the latest version of TWRP first, then try a factory wipe (as long as he has a fastboot cable just in case).

larryf said:
USB mount via TWRP works for me.... I've used it with versions 2.4.1.0 and 2.4.3.0
You can only see the SDcard, I've copied ROMs to it and used TWRP to install.
I agree, if he can't do a wipe something is really messed up. I'd try the latest version of TWRP first, then try a factory wipe (as long as he has a fastboot cable just in case).
Click to expand...
Click to collapse
Ok. Where do i get the updated versions!?!?!!
Wtf?! You have twrp no one else has?
We ONLY HAVE 2.3.3.0 HERE:
http://goo.im/devs/Hashcode/otter2/
Do you even have this device? You people are really getting me confused..
According to your post you have a kf1. Not helpful. Since the devices are different it's better not to advise others when you don't know.
--
Sent from my Kindle Fire 2, CM 10.1

mindmajick said:
The only one that will work is the "sparse image" downloaded from the batch file.
You SURE you tried that one with the command above?
AND you downloaded the system.img for the kf2 and not another device (kf2 7" hd for example). Have you tried both the 10.2.3 version and the 10.2.1?
Last question- you're sure it's a kf2, not a kf1 or kfhd? What's the model number on the back of the device?
I know you tried adb... What about adb sideload in the twrp menu? It has to be a flashable zip file..
--
Sent from my Kindle Fire 2, CM 10.1
Click to expand...
Click to collapse
So I've downloaded both the 10.2.1 and the 10.2.3 images from that link and they arent working. I don't believe either one is a "sparse image" they seem to be the same size as the other system.img files floating around xda for the kf2. I have a mac and i was thinking that might be part of my problem but that wouldn't explain why twrp isn't working. I have the latest twrp installed (2.3.3.0) and I have updated adb also. Usb mount says its working on twrp but my computer can't see it. And also adb sideload says "error closed".

The v10.2.1 and 10.2.3 are sparse images and should flash fine.
Honestly though, I haven't a clue. The only other thing I can suggest is to install Linux or windows on your Mac.
When you say you can't do anything in twrp.. What happens?
At this point I'm just fishing for information, but other than trying a different OS... I haven't any idea
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

mindmajick said:
The v10.2.1 and 10.2.3 are sparse images and should flash fine.
Honestly though, I haven't a clue. The only other thing I can suggest is to install Linux or windows on your Mac.
When you say you can't do anything in twrp.. What happens?
At this point I'm just fishing for information, but other than trying a different OS... I haven't any idea
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Well i think i killed it somehow. I tried pushing backup files from my other kindle to this one and it just shut off in the middle of it and now it wont turn back on no fastboot or nothing. and it had a full charge. Sucks, I really wanted to figure this out.
When i tried to do anything in twrp it could never mount data or system or anything so everything failed.

[Q] Can't wipe phone (GSM Galaxy Nexus)

I can't wipe my phone. So far I've tried:
Factory reset from Settings menu
Hard reset from recovery mode
fastboot -w
Flashing latest version of Yakju from Google
Locking and unlocking bootloader
Wiping from TWRP
Formatting userdata
In addition, I've tried uninstalling apps and removing files via adb shell. In both cases, the apps/files would return on reboot. (And the phone will reboot spontaneously when booted normally, although uninstalling some apps will make it take longer.)
Some background: I forgot to plug in my phone Friday night, and when I checked on it Saturday evening, it was dead. I plugged it into the wall charger, but it wouldn't charge. I poked around the charger port a bit, and got it working again. At 1/4 charge, I tried booting it, only to find that when doing a normal boot, it would stall at the Google start-up screen, while a recovery boot would show the dead android image with no text.
I had some more trouble getting it to charge, and ultimately damaged the USB port. (I got it replaced earlier today (Monday).) To fix the booting problem, I downloaded the latest yakju image from Google and tried flashing it. Not realizing that it would take 25 minutes to write system, I pulled the battery before that point. In spite of this, I was now able to boot the phone, even if it could no longer charge.
Today I got the USB port replaced, but found that the phone would crash every minute or so. I suspect that this is symptomatic of the larger problem of the phone not wanting to change from how it was Saturday morning when it died. No settings changes seem to stick. Every time I start up, I get the same SMS notification from Friday night. Deleted files are restored, and even my attempts to replace the recovery img with TWRP failed. (I managed to load it with fastboot boot, but it didn't do me much good.)
I've also run it through a successful flash of yakju, once I realized it would take half an hour to run. So far the only thing I can think of that I haven't tried is ODIN!
I have three sets of logs from logcat running up until the time of a crash, and the output of adb bugreport, if those are helpful.
Does anyone have any other suggestions?

I've attached the logs.
I've poked around a bit more, trying to get things working, or failing that, not working in a different manner. I started it up TWRP and ran a few tests. I uploaded the zipped image files to /sdcard, downloaded them again, and verified that result was identical. I used dd to copy the recovery partition to a file, grabbed it from the phone, and tried to use dd to copy TWRP over top. dd seemed to think it was successful, but grabbing the partition again, I get the same contents as before.
I'd assume it's something like the flash memory is never actually flushing its cache, so none of the changes I make get committed. I can run 'sync', and it will pause briefly if there was recent activity, but if I write data to a partition, unmount then remount it, the change is gone. If this is the case, I have no idea how I'd go about fixing it - the problem is sufficiently low level that the OS doesn't seem to be aware of it. If there are any tools available to test this, could you let me know?
At this point, I'm considering cutting my losses and getting a new phone.

Have you tried
fastboot erase boot
Fastboot erase system
Etc etc with userdata and cache also?
Might not work but worth a try.
G-Nexus Sent

ifly4vamerica said:
Have you tried
fastboot erase boot
Fastboot erase system
Etc etc with userdata and cache also?
Might not work but worth a try.
G-Nexus Sent
Click to expand...
Click to collapse
"userdata"
Sent from my Nexus

Yeah userdata! Thanks man.
G-Nexus Sent

alfedenzo said:
I can't wipe my phone. So far I've tried:
Factory reset from Settings menu
Hard reset from recovery mode
fastboot -w
Flashing latest version of Yakju from Google
Locking and unlocking bootloader
Wiping from TWRP
Formatting userdata
In addition, I've tried uninstalling apps and removing files via adb shell. In both cases, the apps/files would return on reboot. (And the phone will reboot spontaneously when booted normally, although uninstalling some apps will make it take longer.)
Some background: I forgot to plug in my phone Friday night, and when I checked on it Saturday evening, it was dead. I plugged it into the wall charger, but it wouldn't charge. I poked around the charger port a bit, and got it working again. At 1/4 charge, I tried booting it, only to find that when doing a normal boot, it would stall at the Google start-up screen, while a recovery boot would show the dead android image with no text.
I had some more trouble getting it to charge, and ultimately damaged the USB port. (I got it replaced earlier today (Monday).) To fix the booting problem, I downloaded the latest yakju image from Google and tried flashing it. Not realizing that it would take 25 minutes to write system, I pulled the battery before that point. In spite of this, I was now able to boot the phone, even if it could no longer charge.
Today I got the USB port replaced, but found that the phone would crash every minute or so. I suspect that this is symptomatic of the larger problem of the phone not wanting to change from how it was Saturday morning when it died. No settings changes seem to stick. Every time I start up, I get the same SMS notification from Friday night. Deleted files are restored, and even my attempts to replace the recovery img with TWRP failed. (I managed to load it with fastboot boot, but it didn't do me much good.)
I've also run it through a successful flash of yakju, once I realized it would take half an hour to run. So far the only thing I can think of that I haven't tried is ODIN!
I have three sets of logs from logcat running up until the time of a crash, and the output of adb bugreport, if those are helpful.
Does anyone have any other suggestions?
Click to expand...
Click to collapse
i have the exact same issue.. i cant wipe anything, after rebooting everything comes back to the phone, even if the flash or odin success, the same old files and OS come back again and nothing changes.
and as in your case, system take like 30 min to write, or even more.
i've tried fastboot erase userdata, fastboot erase system, etc, odin, format partitions from adb, toolkits, etc everything you can think of, and nothing works.
please, post if you fix your phone, because mine has been dead for a month atleast, id like to fix it but i dont know how.

ifly4vamerica said:
Have you tried
fastboot erase boot
Fastboot erase system
Etc etc with userdata and cache also?
Might not work but worth a try.
G-Nexus Sent
Click to expand...
Click to collapse
Sorry I didn't see this earlier. I ran the commands just now:
Code:
$ ./fastboot devices; ./fastboot erase boot; ./fastboot erase system; ./fastboot erase userdata; ./fastboot erase cache 130 ↵
016B75D71500B013 fastboot
erasing 'boot'...
OKAY [ 0.006s]
finished. total time: 0.006s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.007s]
finished. total time: 0.007s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.032s]
finished. total time: 0.032s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 1.881s]
finished. total time: 1.882s
Then it just boots up into the same old. (I'd tried at least some of those earlier, but I couldn't remembe which ones.)

This happened on the incredible to one of my rom users. Emmc or hardware related most likely. Either way there's not much hope to fix it if the usual methods don't work.
Sent from my Galaxy Nexus using Tapatalk 2

can't wipe & phone powers down right after boot
Ok it looks like I have the same problem as alfadenzo, except when my Nexus finishes booting, I get a buzz, a red exclamation point in the battery icon, and a popup saying "battery is not charged, please plug in charger", and powers down.
I've flashed 3 or 4 different stock firmares via Odin.
I've flashed complete sytem img's via fastboot, first wiping everthing.
Despite all this, the same splash screen loads. I think its a from CM7
I've flashed cwm by itself via fastboot , but it doesnt stick. Instead I get the "exclamation point android" , and then the stock recovery which I cant do anything with.
I have *3* whole smacking batteries that I've used, allong with two seperate usb cables. One that came with the phone, and on that came with a different Nexus.
Is this a kernel or bootloader issue? Im all out of the options that I know of
Galaxay Nexus I505
Tuna
variant - toro
bootloader - primekk15
baseband I515 EK02 CDMA
carrier - none
Unlocked

Hi,
I am having the same issue. I tried everything. The recovery mode shows that partitions and files are erased/deleted. However, on next boot all comes live ! and my phone boots. but restarts within a few seconds!
When trying to flash using ODIN, the "system" update fails!
Anyone to help?

Hi, I'm having the same problem.
Have you found the solution??
I'm trying to
- Flash ROM from fastboot
- Flash TWRP from fastboot
- Erase partition from fastboot
- Go to recovery and delete all data in /sdcard using adb
- Trying to delete 1 widget from home screen and reboot
- Try to restore stock image using Odin, Fail in system.img
Nothing happened. My gnex boot like usual to the old home screen and nothing changed.
Then it reboot by itself.
Any ideas?

Same problems with me as I reported earlier! Some are saying that the internal memory has gone readonly and its permanent!
Do you think you can contact Samsung service for a solution? I have thought of so, but need to bring out some time for that.
rakun123 said:
Hi, I'm having the same problem.
Have you found the solution??
I'm trying to
- Flash ROM from fastboot
- Flash TWRP from fastboot
- Erase partition from fastboot
- Go to recovery and delete all data in /sdcard using adb
- Trying to delete 1 widget from home screen and reboot
- Try to restore stock image using Odin, Fail in system.img
Nothing happened. My gnex boot like usual to the old home screen and nothing changed.
Then it reboot by itself.
Any ideas?
Click to expand...
Click to collapse

sudiptochoudhury said:
Same problems with me as I reported earlier! Some are saying that the internal memory has gone readonly and its permanent!
Do you think you can contact Samsung service for a solution? I have thought of so, but need to bring out some time for that.
Click to expand...
Click to collapse
I haven't contact samsung service center yet. This is my old phone, it's already out of warranty so it might be costly.
I thought read only mode should give you an error message at least.
In this case, I'm feeling like using Deep Freeze but for Android

Looks like my gnex chip have emmc brickbug. I cannot check anymore using brickbug app checker because it always crashed after booting. But the symptoms is the same.
Still haven't found a way to fix it

Indeed sounds like a fried emmc. Sorry guys.
Sent from my Galaxy Nexus using XDA Free mobile app

On the same boat as you guys !
Same Scenario here ! :silly: ..... i got a GT-9250 brand new in box , was pulled out only once to try it out and it's in the EXACT same condition as mentioned by previous posters ! i have tried : Odin , fastboot flashes , Cyanogenmod Installer ( the one i had the most progress but failed as well ) , the regular reset procedure , nothing works ! its impossible to clean wipe the device !!! no matter what you do .... once the phone restarts , everything comes back again ! old apps , old data , old software !
I've read somewhere that the problem was related to the READ , WRITE permissions on the phone partitions , somehow .... and i know everyone of us come from different specific scenarios , but it may be worth to give it a try if someone knows how to help us out on that part because it makes sense, it seems the filesystem on the device is protected somehow and when we try to overwrite everything things go wrong ...
Too many people with that crazy issue without a solution , warranty claims or checks on that device are long gone blues ... so dont even think about it .... not with samsung or with the carriers ... its over for us , so we need to figure out a solution for this issue and get our devices back working properly ! :highfive:

Bootloop out of nowhere, possibly bricked. :(

Background:
My phone started to bootloop as soon as I charged it. It didn't have any problem then it bootlooped out of nowhere. The last time I remember doing is I uninstalled the trial version of Tasker (which has been working well for me for a week) and then bought the paid version and reloaded the backup.xml and set the device admin and accessibility stuff. I then browsed for a while and then I had to charge it then bootlooping started.
Situation:
In TWRP I can't mount /data and /cache. Also internal storage says 0mb.
I don't have a backup on my current setup as I was not expecting this and I don't wish to lose my data.
Phone setup:
2.11.510.16 Fully stock, xposed, greenify and tasker.
Any help would be much appreciated.
Edit:
I tried to flash uninstall xposed, wipe dalvik/cache, fix permissions sometimes it would display success although on the terminal it says unable to mount /data. I don't think anything I do in twrp is working.
I then erased recovery via fastboot and flashed recovery again via fastboot (success) and now I can't access recovery.
I can't believe I'm getting ****ed over a bootloop that occurred out of nowhere. fml

You need to flash back to stock and start over. This is the exact reason i wont root my m9. Twrp just isn't reliable enough.
Sent from my HTC One M9 using Tapatalk

Xposed can be tricky sometimes, if you put in something your rom don't like,it can cause thinks to mess up. Your best bet may be to reformat and start from scratch

shivadow said:
You need to flash back to stock and start over. This is the exact reason i wont root my m9. Twrp just isn't reliable enough.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
BR7fan said:
Xposed can be tricky sometimes, if you put in something your rom don't like,it can cause thinks to mess up. Your best bet may be to reformat and start from scratch
Click to expand...
Click to collapse
Ok I am doing an RUU now but I seem to be stuck at 100%. For about 20min now my phone is just bootlooping. Ruu says updating the rom image on your android phone. It also changes from "waiting for bootloader...." to "checking header..." to "sending...." to "updating boot...." to "updating radio...." Then it reboots and wait for bootloader again. Fkkk. :/

Is this even the right response to flashing a recovery? I can't seem to make my recovery work again.
Code:
C:\Users\kenneth\AppData\Local\Android\sdk\platform-tools>fastboot flash recovery C:\Users\kenneth\Downloads\twrp-2.8.7.0-hima.img
target reported max download size of 800000000 bytes
sending 'recovery' (36288 KB)...
OKAY [ 2.686s]
writing 'recovery'...
(bootloader) HOSD CL#591203
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 2.251s]
finished. total time: 4.940s
Also I tried relocking bootloader but it's still **unlocked**.
Code:
C:\Users\kenneth\AppData\Local\Android\sdk\platform-tools>fastboot oem lock
...
(bootloader) RELOCK device
OKAY [ 0.951s]
finished. total time: 0.952s
RUU doesn't work either. :|
Edit: Also noticed at the bottom of download mode it says
Code:
FILE /mnt/media_rw/ext_sd/0PJAIMG.zip
File NOT FOUND

On download mode I format system and cache then erased recovery. I tried to format userdata too but it says "FAILED (remote: unknown command)".
I tried to do it all in bootloader mode but apparently I have to be s-off to do that.
So I may be missing my userdata partition?
There is very limited resources for my device. I am using the ACG RUU which has worked for me before but now it just get stuck at 100% and bootlooping.
I'd like to try and flash stock system, recovery and userdata but I don't know where to get them.
Please help. I'm already losing my hair on this unexpected brick.

nethoinkz said:
On download mode I format system and cache then erased recovery. I tried to format userdata too but it says "FAILED (remote: unknown command)".
I tried to do it all in bootloader mode but apparently I have to be s-off to do that.
So I may be missing my userdata partition?
There is very limited resources for my device. I am using the ACG RUU which has worked for me before but now it just get stuck at 100% and bootlooping.
I'd like to try and flash stock system, recovery and userdata but I don't know where to get them.
Please help. I'm already losing my hair on this unexpected brick.
Click to expand...
Click to collapse
Try the link in my sig and follow instructions. Hopefully you have GSM it works well on my att phone. It will give 4-5 updates including marshmallow

BR7fan said:
Try the link in my sig and follow instructions. Hopefully you have GSM it works well on my att phone. It will give 4-5 updates including marshmallow
Click to expand...
Click to collapse
Thanks but I'm CDMA. How do you make a zip out of a RUU though? Maybe if I make a zip out of ACG RUU it might do something.
Cause in my download mode it says:
Code:
FILE /mnt/media_rw/ext_sd/0PJAIMG.zip
File NOT FOUND

nethoinkz said:
Thanks but I'm CDMA. How do you make a zip out of a RUU though? Maybe if I make a zip out of ACG RUU it might do something.
Cause in my download mode it says:
Code:
FILE /mnt/media_rw/ext_sd/0PJAIMG.zip
File NOT FOUND
Click to expand...
Click to collapse
I found it here on the boards a long time ago. I saved it to my cloud because I could never get the exe one to work on my pc. It's saved my butt a few times
---------- Post added at 11:59 PM ---------- Previous post was at 11:46 PM ----------
nethoinkz said:
Thanks but I'm CDMA. How do you make a zip out of a RUU though? Maybe if I make a zip out of ACG RUU it might do something.
Cause in my download mode it says:
Code:
FILE /mnt/media_rw/ext_sd/0PJAIMG.zip
File NOT FOUND
Click to expand...
Click to collapse
Do you have sprint or Verizon ? I found Verizon here and Sprint here Both have links to the 0PJAIMG.zip this way you won't have to change cid

BR7fan said:
I found it here on the boards a long time ago. I saved it to my cloud because I could never get the exe one to work on my pc. It's saved my butt a few times
---------- Post added at 11:59 PM ---------- Previous post was at 11:46 PM ----------
Do you have sprint or Verizon ? I found Verizon here and Sprint here Both have links to the 0PJAIMG.zip this way you won't have to change cid
Click to expand...
Click to collapse
My carrier is ntelos. The only RUU that works for me is ACG but even on that one I still get stuck probably because my bootloader is unlocked but I can't even lock it. :|
I can't boot, use recovery, use RUU or lock bootloader. ARHAGRHGJRHAJKJKJARJHAGRIUQW!!! Thanks though...

You can try try this ruu zip https://www.androidfilehost.com/?fid=24385658843825243. Rename it to 0PJAIMG.zip, stick it on your fat32 formated sd card, and boot to download mode. It should find the file and prompt you to press vol up to flash. If that dosent work, and i dont think it will while s-on unlocked and modified. You may want to find someone with a clip and get it s-off. Then you can flash what ever you want. Although it sounds like your partitions may be corrupted.

cmlusco said:
You can try try this ruu zip https://www.androidfilehost.com/?fid=24385658843825243. Rename it to 0PJAIMG.zip, stick it on your fat32 formated sd card, and boot to download mode. It should find the file and prompt you to press vol up to flash. If that dosent work, and i dont think it will while s-on unlocked and modified. You may want to find someone with a clip and get it s-off. Then you can flash what ever you want. Although it sounds like your partitions may be corrupted.
Click to expand...
Click to collapse
Didn't work it just reboots. How do I restore/format a corrupted partition?
Edit: Also do you know where I could get stock recovery for ACG? Is it possible to extract it from that zip file?

I give up. I guess the cause is when I dropped it into the snow and then I dried it out, after a few minutes it was working fine but when I charged it it started bootlooping. I guess something short circuited inside and broke the userdata partition. I will be sending it to HTC tomorrow hoping for a replacement, they said I might qualify for uh oh protection as it might be considered water damage but I'm pretty sure I would have to pay for a few things. Although I'm scared they might reject to fix it due to the things I've done trying to fix it. If that's the case this would be my first and last htc device. Shame, I liked one m9 too but it broke just like that.

Help - Pixel 3 stuck after failed flash-all...

Hi, I'm new here... After browsing all over Internet and trying for many hours, hope I can get some help here.
So I was brave yesterday and wanted to root my pixel 3 to install some new themes. Unlocked bootloader, but I screwed up with Magisk / TWRP and the phone could not boot any more. At that point, I was still able to see the phone in adb. Then I tried to flash the stock rom using flash-all, but the process failed at one file (vendor_a?).
Unfortunately, I decided to reboot the phone - and now I'm stuck because the phone will be deadlocked showing the Google screen, and my PC cannot recognize the phone any more. adb shows no device, and device manager doesn't see any Android device. I have the latest developer tools and also installed the latest Google USB driver (at least I think), but now when I plug the phone in, I do hear the new device sound, but it is only recognized as a general USB device.
I can't even turn off the phone. Long pressing power will only go back to restart the phone and the first screen shows "this device is corrupted". Go on to the second screen will only give me an option to pause, with nothing else to choose from. I can't reboot into TWRP or recovery.
Any thoughts? Thanks a lot...

edx2000 said:
Hi, I'm new here... After browsing all over Internet and trying for many hours, hope I can get some help here.
So I was brave yesterday and wanted to root my pixel 3 to install some new themes. Unlocked bootloader, but I screwed up with Magisk / TWRP and the phone could not boot any more. At that point, I was still able to see the phone in adb. Then I tried to flash the stock rom using flash-all, but the process failed at one file (vendor_a?).
Unfortunately, I decided to reboot the phone - and now I'm stuck because the phone will be deadlocked showing the Google screen, and my PC cannot recognize the phone any more. adb shows no device, and device manager doesn't see any Android device. I have the latest developer tools and also installed the latest Google USB driver (at least I think), but now when I plug the phone in, I do hear the new device sound, but it is only recognized as a general USB device.
I can't even turn off the phone. Long pressing power will only go back to restart the phone and the first screen shows "this device is corrupted". Go on to the second screen will only give me an option to pause, with nothing else to choose from. I can't reboot into TWRP or recovery.
Any thoughts? Thanks a lot...
Click to expand...
Click to collapse
First off, if you did successfully unlock your bootloader there is a 99% chance you will be able to recover from this. In fastboot mode is the phone state shown as "unlocked" ? Do you have a second PC or laptop to install the standalone adb/fastboot binaries on? adb does not work in fastboot mode, only in stock recovery mode. First re-try fastboot flashing the full image while in fastboot mode without modifying the flash-all.bat (allow it to wipe). You may also want to check the CRC (checksum) on the image you downloaded to verify it is not corrupt. If unlocked and that install fails capture the error and report back. Then try using adb from the stock recovery. You Tube how to get into recovery and use update via adb with a (different) full OTA image. The full OTA images are also available on the same Google dev site as the factory image, and is sometimes called a rescue OTA. You're in the right place to get help, but you need to provide all relevant information (such as previously installing a custom rom).

try holding power and vol down until the phone reboots and comes back to the menu where you should hopefully get back to Android Recovery mode where you should be able to use adb and the OTA via a sideload......for some strange reason I always get screwed on the vendor partition when using the flash-all script....never have figured it out
GL!!

v12xke said:
First off, if you did successfully unlock your bootloader there is a 99% chance you will be able to recover from this. In fastboot mode is the phone state shown as "unlocked" ? Do you have a second PC or laptop to install the standalone adb/fastboot binaries on? adb does not work in fastboot mode, only in stock recovery mode. First re-try fastboot flashing the full image while in fastboot mode without modifying the flash-all.bat (allow it to wipe). You may also want to check the CRC (checksum) on the image you downloaded to verify it is not corrupt. If unlocked and that install fails capture the error and report back. Then try using adb from the stock recovery. You Tube how to get into recovery and use update via adb with a (different) full OTA image. The full OTA images are also available on the same Google dev site as the factory image, and is sometimes called a rescue OTA. You're in the right place to get help, but you need to provide all relevant information (such as previously installing a custom rom).
Click to expand...
Click to collapse
cmh714 said:
try holding power and vol down until the phone reboots and comes back to the menu where you should hopefully get back to Android Recovery mode where you should be able to use adb and the OTA via a sideload......for some strange reason I always get screwed on the vendor partition when using the flash-all script....never have figured it out
GL!!
Click to expand...
Click to collapse
Thank you guys. I was able to make some progress but now I'm stuck somewhere else.
If I run flash-all, the error message I get is:
"Sending sparse 'vendor_a' 1/2 (262140 KB) FAILED (Error reading sparse file)
Finished. Total time: 108.152s
Press any key to exit..."
Alternatively, I tried sideload in recovery mode, and I get:
"E:footer is wrong
Update package verification took 0.2s
E:Signature verification failed
E:error:21
So it seems the zip I downloaded is corrupted? But I downloaded two different versions from Google Developers and both failed.
Any suggestions? I'm going to try it one more time with another computer.

edx2000 said:
Thank you guys. I was able to make some progress but now I'm stuck somewhere else.
If I run flash-all, the error message I get is:
"Sending sparse 'vendor_a' 1/2 (262140 KB) FAILED (Error reading sparse file)
Finished. Total time: 108.152s
Press any key to exit..."
Alternatively, I tried sideload in recovery mode, and I get:
"E:footer is wrong
Update package verification took 0.2s
E:Signature verification failed
E:error:21
So it seems the zip I downloaded is corrupted? But I downloaded two different versions from Google Developers and both failed.
Any suggestions? I'm going to try it one more time with another computer.
Click to expand...
Click to collapse
Have you also tried a 2.0 USB A to USB C cable, or a different set of cables period?

do what I told you....I always fail at the vendor junk but can easily get the ota sideloaded....give it a try, forget flash-all
EDIT: just read the rest of your post...hmm....
well assuming you get the correct hash after downloading, it should work. after that its computer, port, drivers, sdk, and cable thats a potential issue.
again for me, I always fail on vendor. it happened on my pixel 2xl and still on the 3xl. I have tried multiple pc's, cables, etc and always fail at the vendor partition, but the ota sideload through android recovery always worked. YMMV

cmh714 said:
do what I told you....I always fail at the vendor junk but can easily get the ota sideloaded....give it a try, forget flash-all
EDIT: just read the rest of your post...hmm....
well assuming you get the correct hash after downloading, it should work. after that its computer, port, drivers, sdk, and cable thats a potential issue.
again for me, I always fail on vendor. it happened on my pixel 2xl and still on the 3xl. I have tried multiple pc's, cables, etc and always fail at the vendor partition, but the ota sideload through android recovery always worked. YMMV
Click to expand...
Click to collapse
If vendor "always" fails on your PXL3 you may want to find out why. Could be a symptom of some problem with your phone.

Homeboy76 said:
If vendor "always" fails on your PXL3 you may want to find out why. Could be a symptom of some problem with your phone.
Click to expand...
Click to collapse
I doubt that....happened with my xl2 as well....tried multiple PC's, ports, cables, etc. nothing seems to work so I have been using the OTA as that has been bulletproof thus far

Make your you have latest fastboot and adb, a good non usbc to usb c cable, boot into fastboot, flash all, profit. If your bootloader is unlock your good.

edx2000 said:
Thank you guys. I was able to make some progress but now I'm stuck somewhere else.
If I run flash-all, the error message I get is:
"Sending sparse 'vendor_a' 1/2 (262140 KB) FAILED (Error reading sparse file)
Finished. Total time: 108.152s
Press any key to exit..."
Alternatively, I tried sideload in recovery mode, and I get:
"E:footer is wrong
Update package verification took 0.2s
E:Signature verification failed
E:error:21
So it seems the zip I downloaded is corrupted? But I downloaded two different versions from Google Developers and both failed.
Any suggestions? I'm going to try it one more time with another computer.
Click to expand...
Click to collapse
You should verify the crc checksums of the files you are using. There are many tools to do this and the signature is posted with each image. That, and like Badger says.. try a different cable (A to C). and try another PC. Google provides these image files to enable users who have unlocked their bootloader to completely restore the phone to it's factory state. I'm thinking the problem is with a corrupt image, a marginal cable, or the adb/fastboot setup on your PC/laptop. You don't need the complete Android SDK, only the standalone platform tools. The fact you have a working stock recovery and are bootloader unlocked means your likelihood of success is very high.

Badger50 said:
Have you also tried a 2.0 USB A to USB C cable, or a different set of cables period?
Click to expand...
Click to collapse
Wow, using a USB A to C worked!!
Changing to another computer did nothing.
Thanks everybody!!

edx2000 said:
Wow, using a USB A to C worked!!
Changing to another computer did nothing.
Thanks everybody!![/QUOTGlad you got it working :good:!! Pixel 2 & 3 XL's definitely have something in common. They're both picky sons of guns when it comes to cables! :good:
Click to expand...
Click to collapse

edx2000 said:
Wow, using a USB A to C worked!!
Changing to another computer did nothing.
Thanks everybody!!
Click to expand...
Click to collapse
Pixel 3a here. Found this through a bit of intense google-fu. This did the trick. Hilarious that this was the source of it. Previously was using usbc to usbc on a win10 laptop and it failed at the same part mentioned here.
Sorry for the necro bump but I think it deserves a mention. Thanks everyone here

Help..Pixel 2 XL..Android 10 update..Lockscreen flickers..Cannot load android system

Hello everyone,
This saga started after I updated my Pixel 2 XL to Android 10 about a month ago. My phone had become a bit laggy for a while so I was keenly waiting for the update since it promised to smoothen things up for but post the update nothing changed so I was a little disappointed. Anyways, one fine day when I tried to change my lockscreen wallpaper through an app which I had been using for a while, 'Wallpaper Modder' (downloaded from the Google Playstore) nothing happened. I tried again and still, nothing happened. So I simply restarted my phone since it seemed a little laggy. Since then it goes through the usual bootup sequence with Google on the screen, then the Google logo (G) with 'Powered by android' at the bottom but then the lockscreen doesn't load. Instead, I get a flashing time, battery symbol & percentage and the back arrow (bottom left) on the screen, and after a while it restarts and shows up the Android Recovery screen:
Android Recovery
google/taimen/taimen
10/QP1A.191005.007.A1/5908163
user/release-keys
Use volume up/down and power.
Cannot load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device.
Try again
Factory data reset
The reason I am asking for your help is that I do not want to lose my data that I have on the phone by doing a factory data reset. FYI, I do have my photos backed up to Google Photos but there's more stuff in there that I didn't backup. :|
Please note that I have already taken the following troubleshooting steps after going through a lot of forums since then.
1. Restart the phone in Safe Mode
2. Soft Reset - Restarting the phone 7 times continuously
3. Sideload the October OTA update again using ADB and recently the November update as well.
PS: I have stock android and have not tweaked my phone in any manner whatsoever. Hence the bootloader is locked. I simply had the developer options enabled. But I am unsure if USB debugging is enabled or not.
Please help!!!

anubhavsood said:
Hello everyone,
This saga started after I updated my Pixel 2 XL to Android 10 about a month ago. My phone had become a bit laggy for a while so I was keenly waiting for the update since it promised to smoothen things up for but post the update nothing changed so I was a little disappointed. Anyways, one fine day when I tried to change my lockscreen wallpaper through an app which I had been using for a while, 'Wallpaper Modder' (downloaded from the Google Playstore) nothing happened. I tried again and still, nothing happened. So I simply restarted my phone since it seemed a little laggy. Since then it goes through the usual bootup sequence with Google on the screen, then the Google logo (G) with 'Powered by android' at the bottom but then the lockscreen doesn't load. Instead, I get a flashing time, battery symbol & percentage and the back arrow (bottom left) on the screen, and after a while it restarts and shows up the Android Recovery screen:
Android Recovery
google/taimen/taimen
10/QP1A.191005.007.A1/5908163
user/release-keys
Use volume up/down and power.
Cannot load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device.
Try again
Factory data reset
The reason I am asking for your help is that I do not want to lose my data that I have on the phone by doing a factory data reset. FYI, I do have my photos backed up to Google Photos but there's more stuff in there that I didn't backup. :|
Please note that I have already taken the following troubleshooting steps after going through a lot of forums since then.
1. Restart the phone in Safe Mode
2. Soft Reset - Restarting the phone 7 times continuously
3. Sideload the October OTA update again using ADB and recently the November update as well.
PS: I have stock android and have not tweaked my phone in any manner whatsoever. Hence the bootloader is locked. I simply had the developer options enabled. But I am unsure if USB debugging is enabled or not.
Please help!!!
Click to expand...
Click to collapse
First, try fastbooting the current boot.img to both slots with..fastboot flash boot boot.img --slot=all
If that doesn't work, then try fastbooting the factory image, not the OTA, one slot at a time with the -w removed from the flash-all.bat file.
If neither of those 2 work, then you'll likely have to do a factory reset

Badger50 said:
First, try fastbooting the current boot.img to both slots with..fastboot flash boot boot.img --slot=all
If that doesn't work, then try fastbooting the factory image, not the OTA, one slot at a time with the -w removed from the flash-all.bat file.
If neither of those 2 work, then you'll likely have to do a factory reset
Click to expand...
Click to collapse
Unfortunately, his bootloader is locked; so I can't imagine flashing the full factory is a viable option....
I'm wondering if it'll do anything by switching the slots and/or updating via an OTA/sideloading... I don't know the commands for it offhand and/or if it can be done with a locked bootloader....

Badger50 said:
First, try fastbooting the current boot.img to both slots with..fastboot flash boot boot.img --slot=all
If that doesn't work, then try fastbooting the factory image, not the OTA, one slot at a time with the -w removed from the flash-all.bat file.
If neither of those 2 work, then you'll likely have to do a factory reset
Click to expand...
Click to collapse
Didn't work...this is what I get...
PS C:\adb> fastboot flash boot boot.img --slot=all
Sending 'boot_a' (40960 KB) OKAY [ 0.563s]
Writing 'boot_a' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot: error: Command failed
PS C:\adb> flash-all.bat
Sending 'bootloader_b' (36352 KB) OKAY [ 0.601s]
Writing 'bootloader_b' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.006s
Sending 'radio_b' (60388 KB) OKAY [ 1.005s]
Writing 'radio_b' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.006s
--------------------------------------------
Bootloader Version...: TMZ30h
Baseband Version.....: g8998-00012-1905270706
Serial Number........: 712KPMZ1266923
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.001s]
Checking 'version-bootloader' OKAY [ 0.001s]
Checking 'version-baseband' OKAY [ 0.001s]
Setting current slot to 'b' FAILED (remote: 'Slot Change is not allowed in Lock State
')
fastboot: error: Command failed
Press any key to exit...

simplepinoi177 said:
Unfortunately, his bootloader is locked; so I can't imagine flashing the full factory is a viable option....
I'm wondering if it'll do anything by switching the slots and/or updating via an OTA/sideloading... I don't know the commands for it offhand and/or if it can be done with a locked bootloader....
Click to expand...
Click to collapse
Looks like it's a lost cause...I have even tried to boot TWRP but I get the same error 'Flashing is not allowed in Lock State'
PS C:\adb> fastboot flash recovery twrp-3.3.0-0-taimen.img
Sending 'recovery' (40960 KB) OKAY [ 0.348s]
Writing 'recovery' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot: error: Command failed
PS C:\adb>
Apart from this I was trying to uninstall the Wallpaper Modder app in the hope that the default lockscreen wallpaper might get loaded when I bootup the phone but unfortunately the I get 'error: closed' when I try to run any adb shell commands...
Anyways, I seriously feel that there should be a way to fix this. Because I am pretty sure it's the custom lockscreen wallpaper that messed up my phone post the update. I don't remember where but I did come across a post where this has happened to someone else as well. This situation is pretty lame if you ask me. I expected more from Google.

simplepinoi177 said:
Unfortunately, his bootloader is locked; so I can't imagine flashing the full factory is a viable option....
I'm wondering if it'll do anything by switching the slots and/or updating via an OTA/sideloading... I don't know the commands for it offhand and/or if it can be done with a locked bootloader....
Click to expand...
Click to collapse
Ah crap simple man, I overlooked that in his post. My old eyes miss things from time to time. However, you are correct....he's jacked. FDR time

Exactly same thing here just that I haven't installed any app recently. Phone starts, flickrs on login screen and restarts and goes to recovery screen. I don't want to factory reset w/o backing up my data. Is there a way to recover my photos atleast ?

Sharing my experience while looking for answers: Twice this week, I woke up to find my Pixel 2 XL bricked. Completely stock, not rooted.
"Cannot load Android system. Your data may be corrupt. If you continue to get this message, you need to perform a factory data reset and erase all user data stored on this device."
When retrying, both in safe and regular mode, the lock screen flashes. If I'm quick enough to get it unlocked, it just shuts down. One time, I managed to get a "System UI" crash dialog.
I attempted flashing the latest Android 10 OTA (without a factory reset) and it did not resolve the issue. Since I have everything backed up (except my 2FA tokens...lesson learned) I went ahead and did a factory reset. Spent an entire day getting my phone set back up, and this morning I woke up to the same issue. I'm new so I can't link the video, but look for YouTube Video ID: NLrI6bIsTNM
I have a message in to support since my phone should still be under warranty (bought in June of 2018).

I am having same issue, Factory data reset then next morning, it happens again. is there any way to fix this? No more warranty for my phone

huteri said:
I am having same issue, Factory data reset then next morning, it happens again. is there any way to fix this? No more warranty for my phone
Click to expand...
Click to collapse
Add me to the club - same issue on my Pixel 2 XL. First time it happened was on 9 March 2020, now it's done it again twice in 24 hours.
Mine is doing exactly the same thing as xraydrx's phone is - screen flashes on and off for a minute or so before it goes back to the recovery screen.

Same problem - 2 Phones!
Would you believe I now have this same issue...and it's happened 3 times on 2 different phones?
Each time it happens overnight. First was March 14th into 15th, and the second was 11 days later (March 25th into 26th). I requested a RMA, received it March 30th, set up the new phone with the backups I had from my old user profile...and now basically 11 days later (April 10th into 11th) it has happened once again on the new phone. So I'm basically willing to say that it's not a hardware issue.
Sideboots don't work, mounting /system doesn't work...each time it needs a full factory reset.
Curiously, I thought I posted about this in the Android Community forums, but that post now appears to be missing.
Only thing I can think of was brought up earlier in this thread with wallpaper modding - I was using the "cityscapes" wallpaper setting and telling the phone to download a new wallpaper every day. Going to not do that this time around; we'll see if the phone can make it past 11 days.

Same issue. Something with one or more of their new updates. It actually happened -during- (not immediately after) the last update, and I did the factory reset (OUCH! I had that whole 128GigaBytes FULL of... well, God knows what. And God only knows now because I can't remember all the junk I had on there but I know that a lot of it was not replaceable. Videos, movies, personal videos and photos, music, my own music and recordings and etc. etc. etc.
Thought I was good, I did the factry reset and unlocked bootloader, but didn't take the time to install TWRP nor a custom ROM, nor even root. Just unlocked bootloader. Welp, it just happened again now. Reboots, the lockscreen flashes, then disappears, then flashes and disappears, a few times, then the phone reboots and goes to the recovery screen stating that I may be corrupted and asking if I want to try to reboot again, or factory reset.
This is clearly happening to many of us, so it's a software issue, but one that we have not been able to solve yet; and one that Google seems unwilling to help us with. I am already on my first Refurb replacement (I had the vertical pink line issue that eventually grew into a large vertical yellow bar or something. Phone was ugly and began to become unusable. So I ate the bullet and paid the hundred or so to get a replacement Refurb. Not sure what that gets you exactly. It looked brand new and had plastic all over it, but who knows. I guess they'd HAVE to replace the battery, and ensure it was working correctly and wiped of any data. So hey, I was fine with it. Until this. Not sure if they'll throw me another phone at this point. I think they will give you 2 in every calendar year, as long as you keep paying for that damn insurance. I'm sure I've already given them enough insurance payments to cover a new Pixel 4 XL at this point...
Can anyone help me avoid another Factory Butt-Rape? I have a bunch of inspired musical recordings, drone videos, and sentimental photos that I'd really like to keep. And all this covid19 documentation...! Unless we can factory reset the entire planet, coronavirus itself, all of the lost lives, and our global economy... well, then I'd much rather find another way out of this bootloop. Thanks...

Grrrrr... I ended up doing another factory reset. Couldn't get the Pixel 2 xl to show up in adb devices. Screw it. Sucks because I lost another batch of important, non-replaceable stuff. Is this gonna keep happening? It's been over a month since the first time. I think I'm going to root, install a custom recovery (TWRP), and maybe even a custom ROM based on the latest version/security patch of Android (Pie?). Any suggestions? Anyone figure out how to fix this without a factory reset?

It's happened 3 or 4 times now, Factory Reset each time. And every time I tell myself, I have to root and install TWRP and create a nandroid backup, etc. and every time I've skipped it and regretted it. Like now. My phone is so empty after these resets that this may be my new norm. Or I'll somehow get to the bottom of it, and actually install TWRP, etc.
4th times a charm? I'm surprised more people aren't posting on this thread because I'm starting to see reference to this issue on a number of different forums and it looks like Google done messed us up good this time (possibly in combination with a number of apps, but still....).
Anyone else having this issue? ANyone solve it? Post! Post! Post! The more people report this the better chance we have of getting big G's attention for a fix....
THanks!

have you tried cleaning / stopping digital wellbeing? That produced me some bug, but when I reinstalled it the bugs gone