Related
So, I'm on vacation last week, watching a movie on my tablet when it starts to become very laggy. After a minute or two, it locks up completely. Just like everyone else, I reboot it to find that it doesn't get any farther that the green Acer logo. I was running CWM recovery, but nothing seems to work... every command gives me an error. After reading this thread by NighPlayer32: http://forum.xda-developers.com/showthread.php?t=1749967 I switch to TWRP recovery and am able to push an update.zip to the internal sdcard, but still can't install it because none of my partitions will mount.
At this point, I've given up on getting this thing to work. I can get into fastboot and recovery, but beyond that I've had no luck and I'm guessing it's fault hardware (EMMC?). It was purchased in December, so it should be under warranty but it has a unlocked bootloader, which will cause some problems if I send it to Acer. Does anyone know of a way to restore it to a stock bootloader via fastboot or recovery? OR... has anyone with missing partitions been able to load an update.zip successfully?
Any help would be GREATLY appreciated!
Thanks in advance!
ED2O9 said:
So, I'm on vacation last week, watching a movie on my tablet when it starts to become very laggy. After a minute or two, it locks up completely. Just like everyone else, I reboot it to find that it doesn't get any farther that the green Acer logo. I was running CWM recovery, but nothing seems to work... every command gives me an error. After reading this thread by NighPlayer32: http://forum.xda-developers.com/showthread.php?t=1749967 I switch to TWRP recovery and am able to push an update.zip to the internal sdcard, but still can't install it because none of my partitions will mount.
At this point, I've given up on getting this thing to work. I can get into fastboot and recovery, but beyond that I've had no luck and I'm guessing it's fault hardware (EMMC?). It was purchased in December, so it should be under warranty but it has a unlocked bootloader, which will cause some problems if I send it to Acer. Does anyone know of a way to restore it to a stock bootloader via fastboot or recovery? OR... has anyone with missing partitions been able to load an update.zip successfully?
Any help would be GREATLY appreciated!
Thanks in advance!
Click to expand...
Click to collapse
Sorry to hear another one died. We've attempted a few methods but none have so far worked. If you can still push to internal SD you can try to push the a100 boot loader in recovery via adb but you'll lose cwm and fast boot so it will still go back with a custom recovery. There is a stock recovery image around which can also be flashed in recovery via abd which should put it back to normal aside from any custom ROM you may be running. If you're interested I'll try to find the stuff for you and setup some instructions. It'll be tomorrow though I'm about to head to bed.
Tapatalked from my A100 - CM10
I'm scared
How can I prevent my own a100's death
Sent from my LG-P500 using xda premium
-DarkKnight- said:
I'm scared
How can I prevent my own a100's death
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
Hardbricks you can't , its faulty emmc, you either have it or you don't.
Tapatalked from my A100 - CM10
-DarkKnight- said:
I'm scared
How can I prevent my own a100's death
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
me too lol, i just have rooted my tab but i preffer to not touching the bootloader.
---------- Post added at 05:19 PM ---------- Previous post was at 05:17 PM ----------
pio_masaki said:
Hardbricks you can't , its faulty emmc, you either have it or you don't.
Tapatalked from my A100 - CM10
Click to expand...
Click to collapse
hey pio! sorry but my english is a lil short, i dont understand that part, what do u mean?
pio_masaki said:
If you're interested I'll try to find the stuff for you and setup some instructions.
Click to expand...
Click to collapse
Thanks! Like I said, I've tried everything to get a ROM to load and all I get is "can't mount" failures, so I'm assuming that it need to go back to Acer. If you could give me any tips to restore it to the stock bootloader, I'd really appreciate it. There was a thread I found that had a link to a LOCKED bootloader restore script, but the link was dead.
Deshabilitado said:
me too lol, i just have rooted my tab but i preffer to not touching the bootloader.
---------- Post added at 05:19 PM ---------- Previous post was at 05:17 PM ----------
hey pio! sorry but my english is a lil short, i dont understand that part, what do u mean?
Click to expand...
Click to collapse
emmc is the part of the device where the storage is, everything from recovery, bootloader, system, data, internal sd, etc, are all on this chip, if it's damaged or faulty, you can't use that portion of the the memory. The first sign of it failing generally seems to be laggy, slow running, followed by a freeze. Then you are forced to hard reboot, and then you have problems of any partitions mounting.
@ED209 - I'll see if I have some time to hunt this stuff down, although the script pack that zeronull has for unlocking the bootloader also has the a100 and a revert script to restore the stock locked bootloader. The script may or may not work in recovery as it was meant to run from android, but it should be easy enough to either adapt to recovery, or just manually issue the commands over adb in recovery. The PC side will push the bootloader.blob and the script for the tablet side, then run the script on the tablet which will do the bootloader flash, then reboot, however we don't want it to reboot until you have stock recovery or you get locked out.
I know that flashing update.zip fails due to corrupt or missing partitions, but do you think restoring a backup package might work? I guess I'd need a stock backup image, push it to the internal sdcard and just try to run a restore from TWRP. I have a feeling it won't get any farther than the update.zip, but at this point I'll try anything. Do you remember ever seeming if someone posted a link to a stock restore .img?
Beyond that, is it possible to recreate the partitions through ADB?
Thanks again...
ED2O9 said:
I know that flashing update.zip fails due to corrupt or missing partitions, but do you think restoring a backup package might work? I guess I'd need a stock backup image, push it to the internal sdcard and just try to run a restore from TWRP. I have a feeling it won't get any farther than the update.zip, but at this point I'll try anything. Do you remember ever seeming if someone posted a link to a stock restore .img?
Beyond that, is it possible to recreate the partitions through ADB?
Thanks again...
Click to expand...
Click to collapse
There is parted in custom recovery which would in theory work, but its never been attempted before. I'm supposedly getting a brick sent to me (not 100% if it will happen or not) and it's one of the many things I plan to try.
Flashing and restoring will fail since the partitions can't be accessed.
A restore image will fail for the same reason.
I have tons of ideas but until I get ahold of a brick its all purely theory and speculation and until I'm sitting there looking at it I can't figure out how to do it, its weird I know but I can't just bust out what I want to do, I have to be doing it.....
Tapatalked from my A100 - CM10
I suggest you erase all evidence of it being rooted/modded then your warrenty is ok
Do you have a method to check if it is there so i can pretend to wipe everything and brick it, while pretending it wasn't my fault while my warrenty is still here?
-DarkKnight- said:
I suggest you erase all evidence of it being rooted/modded then your warrenty is ok
Do you have a method to check if it is there so i can pretend to wipe everything and brick it, while pretending it wasn't my fault while my warrenty is still here?
Click to expand...
Click to collapse
A pretend wipe is obvious. And what you just suggested isn't exactly honorable, returning an item as broken when its not. And wiping isn't bricking, during my time making the black hole tools I soft bricked at least 20 times, full out wrecked corrupted effed up partitions, always came back. You can't invoke this brick, you have it or you don't.
As for wiping it clean of mods, that is what we were discussing in this thread already. Its also kinda shady as the warranty expires when you root and again when you unlock, and yet again with the custom recovery and also the custom ROM. However it is a straight hardware failure, an issue Acer knows of. I would suggest calling or maybe chatting on their site, I'm pretty sure another brick victim is getting a replacement even rooted and unlocked.
As for checking, no I don't know of a way. The brick thread had aimed to condense all known information to try to isolate it to any build dates or anything specific, but not enough information was provided to do it. For awhile I thought cm9 was safe, but recently a brick occurred on cm9 as well.
I would advise your next step be to visit the Acer site, try to chat with a rep and ask about the hardware failure and your options with it rooted. You may get the same deal the other user did and just pay shipping.
Tapatalked from my A100 - CM10
I wouldn't send it in under warranty coverage if I felt that the issue was due to improper modifications that I made to the device. I'm typically pretty meticulous about following directions, and I was running the stock ROM. I had unlocked the bootloader and added CWM for back-up purposes (which I never got around to because I needed to make space on my SD card), and the lock-up occurred when I was watching a video clip I recorded that afternoon. Based on the severity of the "brick", I'm fairly certain that it's a hardware issue. I'm hearing people mention $150 repair bills, and I'd hate to pitch this tablet because of a EMMC failure, which appears to be increasingly common on this device.
ED2O9 said:
I wouldn't send it in under warranty coverage if I felt that the issue was due to improper modifications that I made to the device. I'm typically pretty meticulous about following directions, and I was running the stock ROM. I had unlocked the bootloader and added CWM for back-up purposes (which I never got around to because I needed to make space on my SD card), and the lock-up occurred when I was watching a video clip I recorded that afternoon. Based on the severity of the "brick", I'm fairly certain that it's a hardware issue. I'm hearing people mention $150 repair bills, and I'd hate to pitch this tablet because of a EMMC failure, which appears to be increasingly common on this device.
Click to expand...
Click to collapse
That wasn't aimed at you, no worries. I still suggest you go chat with Acer on their site, calling charges you, and see what they say about the tablet in its current state.
Tapatalked from my A100 - CM10
ED2O9 said:
I wouldn't send it in under warranty coverage if I felt that the issue was due to improper modifications that I made to the device. I'm typically pretty meticulous about following directions, and I was running the stock ROM. I had unlocked the bootloader and added CWM for back-up purposes (which I never got around to because I needed to make space on my SD card), and the lock-up occurred when I was watching a video clip I recorded that afternoon. Based on the severity of the "brick", I'm fairly certain that it's a hardware issue. I'm hearing people mention $150 repair bills, and I'd hate to pitch this tablet because of a EMMC failure, which appears to be increasingly common on this device.
Click to expand...
Click to collapse
Well 150 is less than the original price
And pio said its the hardware fault its either broken or not broken so modding wouldn't do anything
Sent from my LG-P500 using xda premium
fastboot oem unlock?
droc.noles said:
fastboot oem unlock?
Click to expand...
Click to collapse
What does that have to do with anything in this thread?
Tapatalked from my Galaxy S II - CM10
Probably trolling
Sent from my Full AOSP on a100 using XDA Premium HD app
pio_masaki said:
What does that have to do with anything in this thread?
Tapatalked from my Galaxy S II - CM10
Click to expand...
Click to collapse
Misinterpreted what OP was trying to get done, don't mind me.
I had an issue where I was locked out due to ignorantly running the revert to locked bootloader script. Boot verified failed, recovery verified failed. fastboot oem unlock got me back to the toggle between lock and unlock. My apologies, carry on.
droc.noles said:
Misinterpreted what OP was trying to get done, don't mind me.
I had an issue where I was locked out due to ignorantly running the revert to locked bootloader script. Boot verified failed, verified failed. fastboot oem unlock got me back to the toggle between lock and unlock. My apologies, carry on.
Click to expand...
Click to collapse
Ah ok. And glad you got that squared away, that info may be useful should that occur again.
Tapatalked from my A100 - CM10
pio_masaki said:
That wasn't aimed at you, no worries. I still suggest you go chat with Acer on their site, calling charges you, and see what they say about the tablet in its current state.
Tapatalked from my A100 - CM10
Click to expand...
Click to collapse
In looking back over the brick threads, I realized that you are the member that posted the scripts to return the tablet to a locked bootloader. The link is dead, so I was wondering if you could repost it.
Thanks!
Hey XDAers,
I need your help. I think my phone's eMmc chip is dead. Today my phone's screen didnt turn on, I suspected it to be just a buggy kernel or ROM so as any other person would do, I removed the battery and rebooted. Well it did reboot although the boot animation (of Vanir) was lagging. Then I got to my lockscreen but when i was entering my passcode it was extremely laggy and it continued that way for like a min or 2 just freezing for like 5 seconds then continuing until it finally froze for like a min and I decided to reboot. Same thing happened, I kept trying to reboot sometimes it would just freeze others it would reboot on its own. Then I went into recovery and fixed permissions... same thing. Then I wiped dalvik cache, same results. I finally decided to connect it to the PC and pulled everything from the phone using adb and made a nandroid backup to my USB flash drive using my OTG cable and CWM, because when I tried backing up normally to the internal memory I was faced with errors. So then as a last resort I just was gonna flash to stock using fastboot (by the Nexus toolkit). While flashing I got an error telling me that the baseband version I have is different than the one required. even though the baseband from the .tgz or whatever file was successfully flashed. So apparently my radio is UGLL1 (I think) and the radio included in .tgz package was XXLJ1 and even though it was flashed, it didnt change. I tried manually flashing the radio and it also didnt change. So i went in the .tgz file and edited the android-info.txt file inside so that it doesnt require the XXLJ1 baseband to be present and instead just the UGLL1. It started flashing but got stuck at flashing the system partition after it was "sent". At this point I started paniking because normally flashing stock solves everything. So I tried using ODIN (my first time with it) and it took 30 mins to flash everything (25 mins just for flashing system. I was feeling optimistic since it was successfully completed.
Then it rebooted and I see the Vanir boot animation >_> WHATTT??? after all these system flashes and wipes Vanir is still present?? Then after it boots it takes my right to my same lockscreen, like the data and system partition weren't even touched!!! And its still lagging and freezing. So I go to TWRP recovery and try deleting everything from /data/media which works then I reboot again in recovery and everything is back ??? I cant wipe anything. I can add things because I remember earlier during this process I pushed a zip file.
I AM DYING HERE OMG MY PHONE IS LIKE MY LIFE. PLEASE HELP!!!!!!!! I THINK ITS DEAD BUT I'LL TRY ANYTHING :crying:
Same issue I had; unfortunately that is describing the painful EMMC death. Had to buy another GNEX (http://forum.xda-developers.com/showthread.php?t=1909331 and http://forum.xda-developers.com/showthread.php?t=2354641)
jhonnyx said:
Same issue I had; unfortunately that is describing the painful EMMC death. Had to buy another GNEX (http://forum.xda-developers.com/showthread.php?t=1909331 and http://forum.xda-developers.com/showthread.php?t=2354641)
Click to expand...
Click to collapse
This is devastating me... I've been crying for the past half hour about this. I never thought this could happen, that this device could be bricked
Do you know if Samsung could help me with this, like if they could replace the motherboard maybe. Hopefully it doesn't cost much trying to think of any under-$100 options.
yasir.97 said:
This is devastating me... I've been crying for the past half hour about this. I never thought this could happen, that this device could be bricked
Do you know if Samsung could help me with this, like if they could replace the motherboard maybe. Hopefully it doesn't cost much trying to think of any under-$100 options.
Click to expand...
Click to collapse
You can try Samsungs warranty. Once I bricked my motherboard and got it replaced.
Sent from my Galaxy Nexus using Tapatalk
aaron13 said:
You can try Samsungs warranty. Once I bricked my motherboard and got it replaced.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
They said it would cost about $300 in total. The employee advised me to buy a new phone which I'm going to do. I'll get the Nexus 5 now .
I'm gonna miss this Galaxy Nexus community
yasir.97 said:
They said it would cost about $300 in total. The employee advised me to buy a new phone which I'm going to do. I'll get the Nexus 5 now .
I'm gonna miss this Galaxy Nexus community
Click to expand...
Click to collapse
If your screen is in good shape, you may be able to sell your Gnex for parts.
Sent from my Nexus 7 using xda app-developers app
So after a few months of using my google pixel 2 xl, while I was using it I randomly got a black screen with the message:
"Your device is corrupt. It can't be trusted and may not work properly.
Visit this link on another device: g.co./ABH
PRESS POWER BUTTON TO CONTINUE".
Now it happens every time I turn on my phone. :/
I Have tried doing a factory reset and it still appears.
My phone is not rooted, I have the official OS that I got it with it (updated it through the phone's updater).
The phone was purchased directly from the us google online store.
I've tried to contact their support but they didn't have a solution.
Please help me!!
almogsad said:
So after a few months of using my google pixel 2 xl, while I was using it I randomly got a black screen with the message:
"Your device is corrupt. It can't be trusted and may not work properly.
Visit this link on another device: g.co./ABH
PRESS POWER BUTTON TO CONTINUE".
Now it happens every time I turn on my phone. :/
I Have tried doing a factory reset and it still appears.
My phone is not rooted, I have the official OS that I got it with it (updated it through the phone's updater).
The phone was purchased directly from the us google online store.
I've tried to contact their support but they didn't have a solution.
Please help me!!
Click to expand...
Click to collapse
Sounds like one of those non harmful, annoying messages at boot up. Is your bootloader still locked I assume? If so, have you tried side loading the March OTA. I think sometimes during the OTA updater process that some files don't always make it to the system, which is why you get those messages. Is your phone still functioning properly??
Badger50 said:
Sounds like one of those non harmful, annoying messages at boot up. Is your bootloader still locked I assume? If so, have you tried side loading the March OTA. I think sometimes during the OTA updater process that some files don't always make it to the system, which is why you get those messages. Is your phone still functioning properly??
Click to expand...
Click to collapse
First of all thanks for the response!
yes my bootloader is still locked.
Badger50 said:
have you tried side loading the March OTA
Click to expand...
Click to collapse
How do I do that? ^^
and it seems like the phone still functions properly, but I guess only time will tell
almogsad said:
First of all thanks for the response!
yes my bootloader is still locked.
How do I do that? ^^
and it seems like the phone still functions properly, but I guess only time will tell
Click to expand...
Click to collapse
Just follow these instructions if you want to side load an OTA. It's really not that hard ??
https://developers.google.com/android/ota
Badger50 said:
Just follow these instructions if you want to side load an OTA. It's really not that hard
Click to expand...
Click to collapse
Thanks! I'll try that...
Do you think it might fix the problem?
Edit:
it says in the guide:
"find the appropriate driver for your device from the OEM drivers"
but I don't know which one is mine ^^
almogsad said:
Thanks! I'll try that...
Do you think it might fix the problem?
Edit:
it says in the guide:
"find the appropriate driver for your device from the OEM drivers"
but I don't know which one is mine ^^
Click to expand...
Click to collapse
Once you choose the proper OS version for your pc, and install SDK, when you plug your phone in, it should automatically update your device drivers :good:
And yes, there's a good chance it'll fix your problem. Never any guarantees with this tech stuff though
Badger50 said:
Once you choose the proper OS version for your pc, and install SDK, when you plug your phone in, it should automatically update your device drivers :good:
And yes, there's a good chance it'll fix your problem. Never any guarantees with this tech stuff though
Click to expand...
Click to collapse
Hey! It seems like it worked!!!! Thanks!!
I only wish I hadn't listened to the google support team , and hadn't done a factory reset to phone before lol they don't seem to understand too much about their phones, the guy told me he thinks it's just an add
Thanks again man!
almogsad said:
Hey! It seems like it worked!!!! Thanks!!
I only wish I hadn't listened to the google support team , and hadn't done a factory reset to phone before lol they don't seem to understand too much about their phones, the guy told me he thinks it's just an add
Thanks again man!
Click to expand...
Click to collapse
Oh sweet! Glad to hear it my friend, well done. Now you can help others out with the same issue if it comes up :good: Yeah, the Google folks are kinda funny sometimes. The factory reset is their standard MO! And right, an add on the boot up screen....yeah that's funny! I'd be willing to bet most of them use iPhones!!??????
Badger50 said:
Oh sweet! Glad to hear it my friend, well done. Now you can help others out with the same issue if it comes up :good: Yeah, the Google folks are kinda funny sometimes. The factory reset is their standard MO! And right, an add on the boot up screen....yeah that's funny! I'd be willing to bet most of them use iPhones!!
Click to expand...
Click to collapse
How ironic! lol ???
Badger50 said:
Sounds like one of those non harmful, annoying messages at boot up. Is your bootloader still locked I assume? If so, have you tried side loading the March OTA. I think sometimes during the OTA updater process that some files don't always make it to the system, which is why you get those messages. Is your phone still functioning properly??
Click to expand...
Click to collapse
Thanks!! I also had this issue and following your suggestion to sideload the latest OTA, it appears to have fixed the problem.
I've been getting the same corrupt error on reboots on my xl 2(also not rooted), but I have not been able to get the latest OTA to sideload. It nearly completes but aborts last second and gives a Status 1 error. I'm not sure what I'm doing wrong here. Any help will be appreciated.
Got a similar run-around with Google support. When the factory reset was unsuccessful, they've recommended replacing the phone since it's under warranty, however they think replacing my virtually brand new phone with a refurbished phone is appropriate.
Apsel said:
I've been getting the same corrupt error on reboots on my xl 2(also not rooted), but I have not been able to get the latest OTA to sideload. It nearly completes but aborts last second and gives a Status 1 error. I'm not sure what I'm doing wrong here. Any help will be appreciated.
Got a similar run-around with Google support. When the factory reset was unsuccessful, they've recommended replacing the phone since it's under warranty, however they think replacing my virtually brand new phone with a refurbished phone is appropriate.
Click to expand...
Click to collapse
Are adb/fastboot tools the very newest?
Apsel said:
I've been getting the same corrupt error on reboots on my xl 2(also not rooted), but I have not been able to get the latest OTA to sideload. It nearly completes but aborts last second and gives a Status 1 error. I'm not sure what I'm doing wrong here. Any help will be appreciated.
Got a similar run-around with Google support. When the factory reset was unsuccessful, they've recommended replacing the phone since it's under warranty, however they think replacing my virtually brand new phone with a refurbished phone is appropriate.
Click to expand...
Click to collapse
Unlock then re-lock your bootloader(/s) maybe?
Great job guys, this solution with sideload latest OTA worked for me too with no need to unlock bootloader! :good::good::good:
I can confirm this working again. Pixel 2 XL with 9.0 and November security update.
Thanks!
I just had the corrupt message pop up (bootloader locked), and the sideload ota update seems to have worked!
michaelbsheldon said:
Are adb/fastboot tools the very newest?
Click to expand...
Click to collapse
I'm experiencing the same problem as Apsel, yes the adb/fastboot are the latest.
Error applying update: 15 (ErrorCode : kNewRootfsVerificationError)
E:Error in /sideload/package.zip (status 1)
Badger50 said:
Just follow these instructions if you want to side load an OTA. It's really not that hard ??
https://developers.google.com/android/ota
Click to expand...
Click to collapse
I know this is an old post but I'm having the same issue. Also cannot connect to pc due to, I'm assuming daughterboard issue this and previous pixel models have. I have been rooting phones since the S3 and am no virgin to the sdk. I tried to take it to ubreakifix which was a 4 hour round trip for me. I was told I would have to sign a waiver since the screen is glued to the phone and that was the only way to get to the internals. When I arrived I watched 4 bozos poke at the charging port for 20 min and then contradicting what I was told the night before over the phone that they were not comfortable doing the repair and then they tried to sell me a new device. I just got off chat with google and they want to charge me 270 dollars to fix even though I went to an authorized service center when it was in warranty. Will fastboot work over wifi?
Toolmighty said:
Will fastboot work over wifi?
Click to expand...
Click to collapse
'fraid not. Both the bootloader and recovery have stripped down hardware support, limited essentially to the display and storage. Neither has WiFi support that I know of, thus you have to use a USB cable.
I figured it out after I figured out how to fix the daughterboard issue w/o replacing the daughterboard. Verizon are some sneaky *^&$^s. Thx for the reply tho. I'm sure ur quite busy.
My pixel xl started bootlooping. I can get into fastboot but that's it. If I try to boot twrp, bootloop, if I flash stock, bootloop. I've tried Oreo, pie. This came out of nowhere. I tried a gsi, bootloop. I'm very confused. The memory works because its flashing. Something has to be triggering a reboot. Only thing I know of that forces restart is unencrypted internal storage
same here... any updates?
ferydaboss said:
same here... any updates?
Click to expand...
Click to collapse
I just sat down to try again, I will keep you posted. this is a dev device for me so its kind of annoying it would randomly brick for no reason. luckily I always keep the bootloader unlocked
godkingofcanada said:
I just sat down to try again, I will keep you posted. this is a dev device for me so its kind of annoying it would randomly brick for no reason. luckily I always keep the bootloader unlocked
Click to expand...
Click to collapse
This was my personal device, got out of warranty, no google store or any other youbreakwefixit stores near me, and it just bricked by itself. No root,no custom rom, nothing i can barely get into Recovery mode, and when i do, i install the latest OTA, and hope for the best Thanks
ferydaboss said:
This was my personal device, got out of warranty, no google store or any other youbreakwefixit stores near me, and it just bricked by itself. No root,no custom rom, nothing i can barely get into Recovery mode, and when i do, i install the latest OTA, and hope for the best Thanks
Click to expand...
Click to collapse
I bought a one plus literally a week ago. Lucky on my end. Whatever google did it is bad. I opened up the kernel and disabled the securities. Unencrypted the data. Still nothing. I've manually flashed over every partition 1 by 1, switched to the other slot and tried there. This looks like its going to be a battle. I've got a feeling what we flash isn't copying over some things because it keeps the newest version, which is why we can flash but not overwrite the problem
godkingofcanada said:
I bought a one plus literally a week ago. Lucky on my end. Whatever google did it is bad. I opened up the kernel and disabled the securities. Unencrypted the data. Still nothing. I've manually flashed over every partition 1 by 1, switched to the other slot and tried there. This looks like its going to be a battle. I've got a feeling what we flash isn't copying over some things because it keeps the newest version, which is why we can flash but not overwrite the problem
Click to expand...
Click to collapse
So... there may be a solution in the near future? seeing that google themselves did this? because it is a coincidence, that i see literally 5 pots about the same problem under 4 days..
ferydaboss said:
So... there may be a solution in the near future? seeing that google themselves did this? because it is a coincidence, that i see literally 5 pots about the same problem under 4 days..
Click to expand...
Click to collapse
Google's update hurt some pixel devices, but they expect us to RMA repair the device... I went the other direction and opened it up to tinker with instead
mi wifes pixel is having the exact same issue.
google says im out of warranty so some of the patches ****ed us up....
So I've never had any issues with the Play Store before. Just a few days ago it was working fine. Now, I get the attached screen when I try to look for updates. I've cleared cache and data for the store, play services, etc. I've removed and re-added my Google account. Rebooted the device. I've tried everything I can think of. Has anyone ever encountered this?
TheIgster said:
So I've never had any issues with the Play Store before. Just a few days ago it was working fine. Now, I get the attached screen when I try to look for updates. I've cleared cache and data for the store, play services, etc. I've removed and re-added my Google account. Rebooted the device. I've tried everything I can think of. Has anyone ever encountered this?
Click to expand...
Click to collapse
+1 Can confirm that I have the same issue as well.
I haven't contacted Google yet because ultimately their advice is to format the device and that's a silly way to fix issues and takes so much time.
After a certain amount of time the updates listed under the Updates section will go away. My last one went away yesterday afternoon (Snapchat). If you don't have any updates to apps then you won't see anything there. There's nothing wrong with that. It's funny that you post about it because I just happen to take a screenshot of mine last night. It was empty like yours, but today I got one update, and now that one app shows.
bobbyphoenix said:
After a certain amount of time the updates listed under the Updates section will go away. My last one went away yesterday afternoon (Snapchat). If you don't have any updates to apps then you won't see anything there. There's nothing wrong with that. It's funny that you post about it because I just happen to take a screenshot of mine last night. It was empty like yours, but today I got one update, and now that one app shows.
Click to expand...
Click to collapse
Sorry, that's not the issue. Look at your screen shot and look at mine. See all the white space where apps are supposed to be on mine and see how there is no white space on yours? I have had it like your screen as well. But not with all the white space. There is truly an issue here.
TheIgster said:
Sorry, that's not the issue. Look at your screen shot and look at mine. See all the white space where apps are supposed to be on mine and see how there is no white space on yours? I have had it like your screen as well. But not with all the white space. There is truly an issue here.
Click to expand...
Click to collapse
Gotcha. I read what you tried also, and you don't mention if you tried uninstalling updates for the Play Store. Did you try that?
bobbyphoenix said:
Gotcha. I read what you tried also, and you don't mention if you tried uninstalling updates for the Play Store. Did you try that?
Click to expand...
Click to collapse
Yup.
I spent over an hour on chat with Google yesterday and we tried pretty much everything. They admit it is a bug. They want me to format the device. They are working on a fix currently and I am working with other "specialists" there before factory resetting my device. Good times.
TheIgster said:
Yup.
I spent over an hour on chat with Google yesterday and we tried pretty much everything. They admit it is a bug. They want me to format the device. They are working on a fix currently and I am working with other "specialists" there before factory resetting my device. Good times.
Click to expand...
Click to collapse
How long do you think it would take to do a factory reset as suggested vs all the time you have spent with support? I assume you are bl locked and unrooted so you can't flash a factory image.
TheIgster said:
Yup.
I spent over an hour on chat with Google yesterday and we tried pretty much everything. They admit it is a bug. They want me to format the device. They are working on a fix currently and I am working with other "specialists" there before factory resetting my device. Good times.
Click to expand...
Click to collapse
bobby janow said:
How long do you think it would take to do a factory reset as suggested vs all the time you have spent with support? I assume you are bl locked and unrooted so you can't flash a factory image.
Click to expand...
Click to collapse
They will likely keep replying to you (from different "specialists") asking you to do a ton of extra work that has no more reliability than the methods you could think of. Like bobby mentioned, flashing the factory image would be the best 1st step, but if not possible have you tried side loading the OTA through stock recovery?
sliding_billy said:
They will likely keep replying to you (from different "specialists") asking you to do a ton of extra work that has no more reliability than the methods you could think of. Like bobby mentioned, flashing the factory image would be the best 1st step, but if not possible have you tried side loading the OTA through stock recovery?
Click to expand...
Click to collapse
I haven't unlocked the bl in years so correct me if I'm wrong. You can't do anything other than sideload an OTA if it's locked? So the options, if that is correct, are what you said, OTA sideload or if it's not a VZW model (and the sideload didn't work) unlock the bl, that'll cause a reset, flash the full Dec factory image, then bl lock again. (another factory reset). Bet that'll fix the problem. And the whole shebang will take under an hour.
bobby janow said:
I haven't unlocked the bl in years so correct me if I'm wrong. You can't do anything other than sideload an OTA if it's locked? So the options, if that is correct, are what you said, OTA sideload or if it's not a VZW model (and the sideload didn't work) unlock the bl, that'll cause a reset, flash the full Dec factory image, then bl lock again. (another factory reset). Bet that'll fix the problem. And the whole shebang will take under an hour.
Click to expand...
Click to collapse
Pretty much, Bobby. If Verizon/locked BL, sideload current OTA (no downgrade possible). If you have a Google variant, you can still sideload OTA or unlock the BL (causing a reset) and then flash the factory image. If you go that route, I probably wouldn't re-lock the BL since stuff like this is as much a reason to keep the BL unlocked as rooting and other tinkering.
sliding_billy said:
Pretty much, Bobby. If Verizon/locked BL, sideload current OTA (no downgrade possible). If you have a Google variant, you can still sideload OTA or unlock the BL (causing a reset) and then flash the factory image. If you go that route, I probably wouldn't re-lock the BL since stuff like this is as much a reason to keep the BL unlocked as rooting and other tinkering.
Click to expand...
Click to collapse
Great, thanks. Only thing is if the OP is as security conscience as I am then relock. If not leave it as is. Being able to recover with a factory image is the only thing I miss. It's a big one too but I'm on VZW so I have no option. He could always leave the OEM switch enabled if ever it was needed again I guess.
I'm curious how this gets resolved as he's not the only one with this issue.
bobby janow said:
How long do you think it would take to do a factory reset as suggested vs all the time you have spent with support? I assume you are bl locked and unrooted so you can't flash a factory image.
Click to expand...
Click to collapse
Oh this will definitely take longer than factory resetting the device, but as an ex software developer, I have to see this through and make Google work. If they find and solve the issue, this will help others who have the issue or stop them from having the problem in the first place. It's a bug that needs to be fixed IMO and being on them about this is the way to go. Sure I could just go away and factory reset, but this way, they have to deal with it.
See the attached pic I took today. After installing an app, this appeared on the updates page. The white space is clearly a bug and it needs to be addressed. If they don't solve this by the new year and I can't get updates for apps I use a lot, then fine, I'll factory reset, but I think they should be aware of this issue and they should have to fix it.
bobby janow said:
I haven't unlocked the bl in years so correct me if I'm wrong. You can't do anything other than sideload an OTA if it's locked? So the options, if that is correct, are what you said, OTA sideload or if it's not a VZW model (and the sideload didn't work) unlock the bl, that'll cause a reset, flash the full Dec factory image, then bl lock again. (another factory reset). Bet that'll fix the problem. And the whole shebang will take under an hour.
Click to expand...
Click to collapse
It's not the factory reset, it's remembering all the passwords for the various apps I have, settings, placement of icons, widgets, etc. It is a pain in the a** to reset a device. Besides, I just got this thing set the way I wanted it setup in the last couple of weeks. I haven't even had it for a month.
TheIgster said:
It's not the factory reset, it's remembering all the passwords for the various apps I have, settings, placement of icons, widgets, etc. It is a pain in the a** to reset a device. Besides, I just got this thing set the way I wanted it setup in the last couple of weeks. I haven't even had it for a month.
Click to expand...
Click to collapse
I can certainly appreciate making Google fix this as well as your setup you currently have. However, I seem to recall that when I did a factory reset all the apps and wallpaper and location of icons were imported from I guess Google cloud? Passwords were not though. Time to pull out that yellow notepad and go over those. lol BTW, are you bl unlocked and have you rooted or modified the system in any way? That was not clear from you OP.
bobby janow said:
lol BTW, are you bl unlocked and have you rooted or modified the system in any way? That was not clear from you OP.
Click to expand...
Click to collapse
My bootloader is locked and I've never rooted my pixel 3 XL, yet I'm experiencing the same issue that the op is facing.
MadCow809 said:
My bootloader is locked and I've never rooted my pixel 3 XL, yet I'm experiencing the same issue that the op is facing.
Click to expand...
Click to collapse
And this happened just all of a sudden? You have any thoughts on why or if perhaps an app screwed things up? Stock launcher? Some setting perhaps? Very curious isn't it? And since it's not very widespread it would be nice to know in order to avoid it.
TheIgster said:
So I've never had any issues with the Play Store before. Just a few days ago it was working fine. Now, I get the attached screen when I try to look for updates. I've cleared cache and data for the store, play services, etc. I've removed and re-added my Google account. Rebooted the device. I've tried everything I can think of. Has anyone ever encountered this?
Click to expand...
Click to collapse
Just to clarify, is it just a cosmetic issue with displaying extra white space on that screen, or is there some other functional problem?
samnada said:
Just to clarify, is it just a cosmetic issue with displaying extra white space on that screen, or is there some other functional problem?
Click to expand...
Click to collapse
The white space was never there before and is not there on other devices that I have encountered. Do you have the white space on your device? Also, updates are not appearing to happen properly either. The only reason I saw that one update is because I just installed another app and it updated one app right after that. I normally have numerous updates, daily.
Google has already admitted to and are working on this as a bug.
TheIgster said:
The white space was never there before and is not there on other devices that I have encountered. Do you have the white space on your device? Also, updates are not appearing to happen properly either. The only reason I saw that one update is because I just installed another app and it updated one app right after that. I normally have numerous updates, daily.
Google has already admitted to and are working on this as a bug.
Click to expand...
Click to collapse
But.. But. 3 people with this issue and they are calling it a bug? Are they blowing some smoke your way? Is there a tracker for this? CSR are notorious for playing the game until you give up. Be wary. I say factory reset and fix it yourself. You have spent way too much time on this I fear. But it's your call at this point. Keep us posted.