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.
Related
Is there a way to avoid the message you get when you reboot after unlocking the Bootloader? The black screen where you can wait 5 seconds or tap the power to go on...
I understand that is correct to show it...but it's boring and I'm already aware of it.
http://forum.xda-developers.com/nextbit-robin/general/guide-install-twrp-root-robin-t3334171/page7
maybe try and follow the instruction on post number 69
Thanks for the reply but that's for Moto X. Actually before Robin I was using a Moto X and I know that procedure, point is that on Moto X was just a screenshot before booting and nothing else, here looks a bit different and you can also skip it pressing the power button. Plus I would avoid to flash/use the logo.bin of Moto X...
Can anyone of Nextbit team provide any info? Thanks !
I also don´t like the screen... the opportunity to hide would be great.
here's the same, maybe someone can make a xposed module?
kcl0801 said:
here's the same, maybe someone can make a xposed module?
Click to expand...
Click to collapse
Hi, firmware/bootloader guy here - work for a Android vendor so I decided to have a quick look at the bootloader for you guys..
It's stored in the bootloader (aboot) if you are interested so you can't make a xposed module, it runs before Android (before init or zygote) does (or the Linux kernel). I haven't checked if Secure boot is on (if not, I suppose I could build a replacement aboot and just patched out the logic for that screen ) but I hope it's on for security reasons.
uberlaggydarwin said:
Hi, firmware/bootloader guy here - work for a Android vendor so I decided to have a quick look at the bootloader for you guys..
It's stored in the bootloader (aboot) if you are interested so you can't make a xposed module, it runs before Android (before init or zygote) does (or the Linux kernel). I haven't checked if Secure boot is on (if not, I suppose I could build a replacement aboot and just patched out the logic for that screen ) but I hope it's on for security reasons.
Click to expand...
Click to collapse
got it, in that case i will keep this message, but just hope it can pass faster, it says 5 secs but i feel it's about 30s to skip it...
kcl0801 said:
got it, in that case i will keep this message, but just hope it can pass faster, it says 5 secs but i feel it's about 30s to skip it...
Click to expand...
Click to collapse
Hey everyone, our team is looking into that nag screen. One of our devs pointed it out, so we're trying to see what we can do. :good:
any luck on the nag screen yet? maybe gone in the july update? =D lol
I get this message Everytime, any ideas? Help would be great
Akoolive said:
I get this message Everytime, any ideas? Help would be great
Click to expand...
Click to collapse
Make sure that the recovery.img is in the same folder as your adb/fastboot files. Let me know if that works!
makbomb said:
Make sure that the recovery.img is in the same folder as your adb/fastboot files. Let me know if that works!
Click to expand...
Click to collapse
Thanks that worked
Akoolive said:
I get this message Everytime, any ideas? Help would be great
Click to expand...
Click to collapse
Replace "recovery.img" at the end with the actual twrp filename and it should work.
I'd love to get rid of that error message on my new Robin, but I'm confused about whether or not the previous two posts were a solution to the problem. I had flashed TWRP after unlocking the bootloader, and the recovery was in the same folder as the ADB and Fastboot files, but I'm not sure what that has to do with removing the error message.
Thanks in advance!
Saaber said:
I'd love to get rid of that error message on my new Robin, but I'm confused about whether or not the previous two posts were a solution to the problem. I had flashed TWRP after unlocking the bootloader, and the recovery was in the same folder as the ADB and Fastboot files, but I'm not sure what that has to do with removing the error message.
Thanks in advance!
Click to expand...
Click to collapse
The last several message in this thread regarding 'recovery.img' was for someone trying to flash TWRP in fastboot, it has nothing to do with the 5-second nag screen.
Since khang never responded, I'm assuming this won't change and the nag screen will remain. I'm so used to keeping my finger on the power button when i reboot that it's almost habit now, so really doesn't bother me too much.
How can a device that is marketed for its unlockable bootloader and warranty coverage have an jnlockable bootloader experience that is worse than basically all devices. You don't see unlocked Sony or LG phones having boot screens that require user input. The only device I know of that is worse is the Pixel c, which has a 30 second "integrity check" if the bootloader is unlocked.
Nextbit_Khang said:
Hey everyone, our team is looking into that nag screen. One of our devs pointed it out, so we're trying to see what we can do. :good:
Click to expand...
Click to collapse
IS this going to change? really annoyed by it
..It's only 5 seconds, the only reason it seems longer is the fact that the message merges in with the boot logo
Nextbit_Khang said:
Hey everyone, our team is looking into that nag screen. One of our devs pointed it out, so we're trying to see what we can do. :good:
Click to expand...
Click to collapse
Very old thread here, but could you guys maybe release an optional "developer/enthusiast" bootloader update that gets rid of that nag screen? Or at least give the option to confirm the warning in future updates, like "I have read and understood this warning. Don't show again."
I am posting hoping some progress may or may not have been made on this. Its atrocious.
It's possible that it comes today/tomorrow at some point!!
Source: https://twitter.com/nvidiashield/status/913265527480475648
Yes, major speculating here, but usually Nvidia is very very quick with updates. SO let's all hope and pray. This COULD also be the Nvidia Spot announcement/availability.
Tomorrow 29th or today 28th. Their message is very cryptic. Google Assistant was just released for Nvidia Shield TV! Not Oreo unless they have their own announcement since Assistant one was by Google
Apparently some people are updating to Oreo already. But it looks like US only. :crying:
edit...not Oreo
kalinskym said:
Tomorrow 29th or today 28th. Their message is very cryptic. Google Assistant was just released for Nvidia Shield TV! Not Oreo unless they have their own announcement since Assistant one was by Google
Click to expand...
Click to collapse
Yes, correct. It was assistant that was released! http://www.androidpolice.com/2017/09/28/assistant-finally-come-shield-tv-looks-great/
JoeFCaputo113 said:
Yes, correct. It was assistant that was released! http://www.androidpolice.com/2017/09/28/assistant-finally-come-shield-tv-looks-great/
Click to expand...
Click to collapse
Unfurtunately only in U. S.... Hopefully there will be a way to get it, elsewhere
Kantraz said:
Unfurtunately only in U. S.... Hopefully there will be a way to get it, elsewhere
Click to expand...
Click to collapse
Wonder if changing the language to English US will force it to work like with phones. I'll have a play about tonight.
Also...from what I understand this is Nvidia Experience 6 and not Oreo. The new launcher is not yet here for the shield.
dunjamon said:
Wonder if changing the language to English US will force it to work like with phones. I'll have a play about tonight.
Also...from what I understand this is Nvidia Experience 6 and not Oreo. The new launcher is not yet here for the shield.
Click to expand...
Click to collapse
Hopefully it is enough, gonna try as soon as I get home from work!
Kantraz said:
Hopefully it is enough, gonna try as soon as I get home from work!
Click to expand...
Click to collapse
Snap! I've already told the missus to plug in the controller to get it charged up and ready. Ha!
dunjamon said:
Snap! I've already told the missus to plug in the controller to get it charged up and ready. Ha!
Click to expand...
Click to collapse
I can confirm that Google Assistant, can be enabled by changing the language
Just got the update. But it failed to install. It downloads the update and restarts the shield, but never finishes the install. Stops at about 20% on the Android System Update Screen then restarts back to the home screen asking if I want to install the Experience 6.0 update. Is it because I'm rooted? I don't have TWRP installed but I do have superuser installed....Tried 3 times.
dk1keith said:
Just got the update. But it failed to install. It downloads the update and restarts the shield, but never finishes the install. Stops at about 20% on the Android System Update Screen then restarts back to the home screen asking if I want to install the Experience 6.0 update. Is it because I'm rooted? I don't have TWRP installed but I do have superuser installed....Tried 3 times.
Click to expand...
Click to collapse
I always remove root then do the update. No TWRP either but it would always fail on me.
dk1keith said:
Just got the update. But it failed to install. It downloads the update and restarts the shield, but never finishes the install. Stops at about 20% on the Android System Update Screen then restarts back to the home screen asking if I want to install the Experience 6.0 update. Is it because I'm rooted? I don't have TWRP installed but I do have superuser installed....Tried 3 times.
Click to expand...
Click to collapse
Got #root#?!
If so, well there's your problem. You can NOT update in the conventional way once your rooted. In short you'll have to first download, and use fastboot, to flash the last 5.0.x Recovery For (Chiefly Recovery, System, and Vendor), and then most likely as not do a full system reset. Which if your unfortunate to be doing this on a Pro. Will mean about roughly 2.5h's+ of downtime. Before you'll then need to worry about the latest Update.
Unfortunately I keep telling myself to never root the damned thing again. 'Cause this IS a huge PitA! but, somehow I never learn.
JagXK8 said:
I always remove root then do the update. No TWRP either but it would always fail on me.
Click to expand...
Click to collapse
Alas One does NOT just remove root on the Shield. And, sadly 'cause of it. The only way I know of to be rid of it is flashing a new (Clean Recovery OS), and then factory resetting it fresh for the "New OS" to actually get written. Otherwise root seem to longer like a bad smell on the Shield.
And, now an aside...
Where is all this scuttlebutt about Oreo (Cookie), coming from?
Having done the above... (Sigh again!) I just finished wrapping up that part of the Install. When it occurred to me to check the Version... Which is still Android 7 (e.g. Nougat), so unless someones getting something I'm not. Then, this is not the Chocolate Wafer Cookie your looking for....
Which begs a different question. Why are they calling this "Experience 6..x", and not 5.x.x?
Ichijoe said:
Got #root#?!
If so, well there's your problem. You can NOT update in the conventional way once your rooted. In short you'll have to first download, and use fastboot, to flash the last 5.0.x Recovery For (Chiefly Recovery, System, and Vendor), and then most likely as not do a full system reset. Which if your unfortunate to be doing this on a Pro. Will mean about roughly 2.5h's+ of downtime. Before you'll then need to worry about the latest Update.
Unfortunately I keep telling myself to never root the damned thing again. 'Cause this IS a huge PitA! but, somehow I never learn.
Alas One does NOT just remove root on the Shield. And, sadly 'cause of it. The only way I know of to be rid of it is flashing a new (Clean Recovery OS), and then factory resetting it fresh for the "New OS" to actually get written. Otherwise root seem to longer like a bad smell on the Shield.
And, now an aside...
Where is all this scuttlebutt about Oreo (Cookie), coming from?
Having done the above... (Sigh again!) I just finished wrapping up that part of the Install. When it occurred to me to check the Version... Which is still Android 7 (e.g. Nougat), so unless someones getting something I'm not. Then, this is not the Chocolate Wafer Cookie your looking for....
Which begs a different question. Why are they calling this "Experience 6..x", and not 5.x.x?
Click to expand...
Click to collapse
I don't know about any Oreo update, but I updated to the new release without doing any data reset. Simply boot to fastboot and flash the downloaded system.img, boot.img, and recovery.img. No need to clear data. Then in the system you can install the OTA as normal and re-root using TWRP and Magisk/SuperSu.
eelsid said:
I don't know about any Oreo update, but I updated to the new release without doing any data reset. Simply boot to fastboot and flash the downloaded system.img, boot.img, and recovery.img. No need to clear data. Then in the system you can install the OTA as normal and re-root using TWRP and Magisk/SuperSu.
Click to expand...
Click to collapse
Can you elaborate on this? Maybe post a small guide? I am bootloader unlocked, and currently rooted, but recovery is stock. Where do I get the files you are talking about? Download, boot, and recovery img files? Thanks in advance!
bradleyw801 said:
Can you elaborate on this? Maybe post a small guide? I am bootloader unlocked, and currently rooted, but recovery is stock. Where do I get the files you are talking about? Download, boot, and recovery img files? Thanks in advance!
Click to expand...
Click to collapse
I found this guide here: https://forums.geforce.com/default/topic/667705/-guide-how-to-update-a-rooted-nvidia-shield/
I actually found this helpful guide for updating if you are on a pro and unlocked. http://nvidiashieldzone.com/2017/10/shield-tv-pro-500gb-experience-6-0-upgrade-solution/
I request all to first please understand the problem and give me suggestions as this gets slightly bonkers.
Thanks in advance.
So I had my OnePlus3 A3003 repaired for water Damage from a professional non OnePlus service called Yaantra. They basically replaced the Mother Board is what they say.
I have no reason to doubt, the Phone works flawlessly, everything is working nicely, from the camera to the battery performance and charging and SOT, the performance is as expected.
Only it runs on Oxygen OS 3.1.2.
Now I first got an OTA update notification for 4.5.1 and I immediately started downloading and attempted install. It went through the whole cycle of installing smoothly and after the first reboot, it splashed a linux Penguin Logo and then turned off, never turned back on. I manually pressed the power button after a long time but it again showed the Penguin for a few seconds and powered off. I figured that the phone is bricked. (this time my boot loader was Locked)
I had to follow the 2nd Method of the Mega Unbrick guide and got my phone up and running back on 3.1.2
I still get the OTA update but this time i thought I'll download the latest stable build of 5.0.1 and install it via ADB sideload. with the appropriate recovery
The phone got bricked again.
Then I thought of Installing regular TWRP after unlocking bootloader and flashed 5.0.1, No luck. had to unbrick it again.
Then I tried bluspark.
Then I flashed Experience OS with the latest firmware. It went through the entire cycle and installed but this time after it turned off and on again I was greeted to a new error.
it was in red saying "Battery does not match" in English and then in some Asian language. I was able to unbrick from that state as well.
After that I have tried Lineage OS but with same result. I get "Battery does not match"
Then I unbricked the device and i tried #*808# and checked Charger option. it says "itech_3000mah" that doesn't sound original, is it?
Basically no matter what I flash my phone gets bricked.
With Custom ROMs I get the "Battery does not match error"
With Official ROM I get the penguin Logo.
I've tried all sorts of Combination of Recovery and ROMs to no luck.
So far the only thing I haven't tried is flashing another Kernal.
Have to come back to 3.1.2 after unbricking which works flawlessly every time with no problems AT ALL. I wish to upgrade to the latest Official build of OOS (but i am ok with unofficial as well)
Alright, this is a new one.
Have you checked your system information with the app "AIDA64"? Download that app, and post a screenshot of what's under the System tab.
thes3usa said:
Alright, this is a new one.
Have you checked your system information with the app "AIDA64"? Download that app, and post a screenshot of what's under the System tab.
Click to expand...
Click to collapse
Thanks for the eyeball
AbhiM7 said:
Thanks for the eyeball
Click to expand...
Click to collapse
Okay, although AIDA64 doesn't indicate that your Motherboard is a Chinese mockup Mobo, I still suspect that the "Penguin" logo is some kind of third-party under the hood software.
Have you tried the unbrick tool which includes 5.x.x?
thes3usa said:
Okay, although AIDA64 doesn't indicate that your Motherboard is a Chinese mockup Mobo, I still suspect that the "Penguin" logo is some kind of third-party under the hood software.
Have you tried the unbrick tool which includes 5.x.x?
Click to expand...
Click to collapse
Oh I thought there was only the 3.1.2 available in the unbrick tool.
I would appreciate a link for the 5.x.x unbricking tool.
Which should hopefully include all he required firmware and recovery stuff.
What are other ways I can know if my Mobo is a Chinese mock-up?
AbhiM7 said:
Oh I thought there was only the 3.1.2 available in the unbrick tool.
I would appreciate a link for the 5.x.x unbricking tool.
Which should hopefully include all he required firmware and recovery stuff.
What are other ways I can know if my Mobo is a Chinese mock-up?
Click to expand...
Click to collapse
Hi firstly, you shouldnt have trusted your OnePlus3 with 3rd party service like Yaantra. After service they will deny any changes to your hardware and ask stupid questions "isn't your phone receiving call when we gave it back?"
After seeing your posts, it seems that they didn't flash the device properly. I seriously doubt your battery has been Jacked and replaced with some 3rd party mockup.
A simple search in forums can lead you to 5.x.x unbricking tool.
And your final question. If your phone doesn't bootup even after this, most probably you're dealing with some kind of mockup in the chipset.
Did you solve this issue? If so post how here so that others can use it later.
Thanks
SivaMaxwell said:
Hi firstly, you shouldnt have trusted your OnePlus3 with 3rd party service like Yaantra. After service they will deny any changes to your hardware and ask stupid questions "isn't your phone receiving call when we gave it back?"
After seeing your posts, it seems that they didn't flash the device properly. I seriously doubt your battery has been Jacked and replaced with some 3rd party mockup.
A simple search in forums can lead you to 5.x.x unbricking tool.
And your final question. If your phone doesn't bootup even after this, most probably you're dealing with some kind of mockup in the chipset.
Did you solve this issue? If so post how here so that others can use it later.
Thanks
Click to expand...
Click to collapse
I am downloading this msm recovery
https://forum.xda-developers.com/on...k-phone-msmdownloadtool-v3-0-6-t3575801/page2
and try for now.
I'll post my experience soon.
An official technician from OnePlus told me that fake batteries don't work well / won't find with OnePlus at all so there is 99% chance that it's not a mock-up.
thes3usa said:
Okay, although AIDA64 doesn't indicate that your Motherboard is a Chinese mockup Mobo, I still suspect that the "Penguin" logo is some kind of third-party under the hood software.
Have you tried the unbrick tool which includes 5.x.x?
Click to expand...
Click to collapse
The penguin is the old school linux kernel panic screen. It used to come on when kernel panic prevented the device from booting.
What I am thinking is that is not the right board for that device, which explains the battery error. The custom rom battery error could be gotten around I am sure. Just so it boots.
zelendel said:
The penguin is the old school linux kernel panic screen. It used to come on when kernel panic prevented the device from booting.
What I am thinking is that is not the right board for that device, which explains the battery error. The custom rom battery error could be gotten around I am sure. Just so it boots.
Click to expand...
Click to collapse
I see, do you know how can I get around the battery error?
And should I flash a new kernal to get around the Linux penguin warning?
What are my options other than the mega unbricking with a newer version of OOS
AbhiM7 said:
I see, do you know how can I get around the battery error?
And should I flash a new kernal to get around the Linux penguin warning?
What are my options other than the mega unbricking with a newer version of OOS
Click to expand...
Click to collapse
Sure. You will have to hook up the device to the pc while it is trying to boot and grabbing a logcat. This will tell you exactly what is failing. The build a rom that goes around the issue.
To be honest. I don't know what will work for sure but the logcat will tell you just what you need to know.
Piece of advice. If you are gonna do repairs like this. Do them yourself. Even if you fail you will be sure of the parts at least which you can't be with amature repair techs. Too many use knock off parts.
zelendel said:
Sure. You will have to hook up the device to the pc while it is trying to boot and grabbing a logcat. This will tell you exactly what is failing. The build a rom that goes around the issue.
To be honest. I don't know what will work for sure but the logcat will tell you just what you need to know.
Piece of advice. If you are gonna do repairs like this. Do them yourself. Even if you fail you will be sure of the parts at least which you can't be with amature repair techs. Too many use knock off parts.
Click to expand...
Click to collapse
Am not that much of an expert. I don't know about using logcat but I just read a little about it and am going to try.
I'll post my experience soon.
Should I also take the phone to an official OnePlus technician and ask them to check if the chipset/battery is a mock up, they should be able to tell right?
AbhiM7 said:
Am not that much of an expert. I don't know about using logcat but I just read a little about it and am going to try.
I'll post my experience soon.
Should I also take the phone to an official OnePlus technician and ask them to check if the chipset/battery is a mock up, they should be able to tell right?
Click to expand...
Click to collapse
That depends on how good they are but to be honest if it is a really good fake then it may fool even the best. But it cant hurt.
Actually I got stuck in the same situation. I also tried different ROMs but with custom ones I get the Replace Battery error and with official Roms I get the penguin. Is there any way to get rid of the Battery error by modifying the kernel or something?
You've a motherboard of OP3T not OP3
Try oneplus 3t full ota
Cheers
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.