Develop Bugs

[Q] Recover to stock

Currently my phone cannot boot up, get's stuck at the HTC white screen. I am trying to follow the directions here but I'm having some trouble. I can get into the recovery screen and by doing so it automatically starts loading the PG32IMG.zip file but does not do anything after that and I am unsure how to proceed. So far I have tried installing the .zip using the ClockworkMod Recovery but when I attempt to do so it says it can't open and just says (bad), installation aborted. Currently it is S-ON and I do not know if I can change it to S-OFF if I cannot boot it up. Right now I am waiting for the download to finish for this guide and I will hopefully be able to switch it but in the meantime if anyone has any ideas I would certainly like to hear from you.

Zook024 said:
Currently my phone cannot boot up, get's stuck at the HTC white screen. I am trying to follow the directions here but I'm having some trouble. I can get into the recovery screen and by doing so it automatically starts loading the PG32IMG.zip file but does not do anything after that and I am unsure how to proceed. So far I have tried installing the .zip using the ClockworkMod Recovery but when I attempt to do so it says it can't open and just says (bad), installation aborted. Currently it is S-ON and I do not know if I can change it to S-OFF if I cannot boot it up. Right now I am waiting for the download to finish for this guide and I will hopefully be able to switch it but in the meantime if anyone has any ideas I would certainly like to hear from you.
Click to expand...
Click to collapse
What happened before it got stuck at the white screen? Were you trying to flash a rom?

gtdtm said:
What happened before it got stuck at the white screen? Were you trying to flash a rom?
Click to expand...
Click to collapse
yes. I managed to root it last night and was attempting to add this rom this morning. I don't remember what steps I took exactly (I knew I should have written it down!) and now it refuses to boot up. I am able to get into the recovery mode and access the SD card by mounting it to my PC but that's it.

Zook024 said:
yes. I managed to root it last night and was attempting to add this rom this morning. I don't remember what steps I took exactly (I knew I should have written it down!) and now it refuses to boot up. I am able to get into the recovery mode and access the SD card by mounting it to my PC but that's it.
Click to expand...
Click to collapse
So you are HTC dev unlocked but not s-off if I'm understanding correctly. The flashing steps are a little different. You need to look around for flashing instructions for dev unlocked phones. I believe the Viper rom thread has the instructions, and they work for any rom.

gtdtm said:
So you are HTC dev unlocked but not s-off if I'm understanding correctly. The flashing steps are a little different. You need to look around for flashing instructions for dev unlocked phones. I believe the Viper rom thread has the instructions, and they work for any rom.
Click to expand...
Click to collapse
yes you would be correct in that understanding, is this the one you are talking about?

Zook024 said:
yes you would be correct in that understanding, is this the one you are talking about?
Click to expand...
Click to collapse
Yes, his install instructions from that OP are:
Be s-off (or dev unlock)
Install a custom recovery (twrp/4ext)
Download the ROM and place it on your external SD card.
Do a nandroid backup!
Start rom install process and make sure you select to wipe data in aroma
Select your desired setup in aroma, and finish
Reboot the device and enjoy!
If you are dev unlock, you need to pull the boot.img from the rom zip and fastboot it in hboot
I'm not dev unlock, so I've never actually done this, which is why I'm not being more specific. The boot.img is already in the zip you downloaded for the rom.
If you look in this thread, the phone is different, but the flash steps should be identical according to my understanding:
http://forum.xda-developers.com/showpost.php?p=28301167&postcount=1

gtdtm said:
Yes, his install instructions from that OP are:
Be s-off (or dev unlock)
Install a custom recovery (twrp/4ext)
Download the ROM and place it on your external SD card.
Do a nandroid backup!
Start rom install process and make sure you select to wipe data in aroma
Select your desired setup in aroma, and finish
Reboot the device and enjoy!
If you are dev unlock, you need to pull the boot.img from the rom zip and fastboot it in hboot
I'm not dev unlock, so I've never actually done this, which is why I'm not being more specific. The boot.img is already in the zip you downloaded for the rom.
If you look in this thread, the phone is different, but the flash steps should be identical according to my understanding:
http://forum.xda-developers.com/showpost.php?p=28301167&postcount=1
Click to expand...
Click to collapse
well I managed to install the ROM successfully but it still refuses to boot up, I've run out of ideas at this point, no idea why it refuses to boot up.

Zook024 said:
well I managed to install the ROM successfully but it still refuses to boot up, I've run out of ideas at this point, no idea why it refuses to boot up.
Click to expand...
Click to collapse
More details will be very helpful to any of us that might be able to help you.
What rom are you trying to install?
What do you mean by won't boot up. Are you getting past the HTC screen now?

gtdtm said:
More details will be very helpful to any of us that might be able to help you.
What rom are you trying to install?
What do you mean by won't boot up. Are you getting past the HTC screen now?
Click to expand...
Click to collapse
my apologies, I had originally attempted to install this ROM. I thought I had followed the directions to the letter, obviously I screwed up somewhere. I then attempted to perform a factory reset from the ClockworkMod Recovery which yielded no results. I then attempted the Viper ROM, again wiping the data and that said installation was successful. Still it refused to boot. I then tried this return to stock and with that, the .zip folder is automatically loaded but then does nothing. As of right now I cannot get past the HTC screen.

Zook024 said:
my apologies, I had originally attempted to install this ROM. I thought I had followed the directions to the letter, obviously I screwed up somewhere. I then attempted to perform a factory reset from the ClockworkMod Recovery which yielded no results. I then attempted the Viper ROM, again wiping the data and that said installation was successful. Still it refused to boot. I then tried this return to stock and with that, the .zip folder is automatically loaded but then does nothing. As of right now I cannot get past the HTC screen.
Click to expand...
Click to collapse
Well don't panic first of all. It's not super easy for me to figure out what's going on because your setup is quite different from mine, but I'm willing to offer any knowledge I have gleaned from reading these forums (a lot).
When you tried to go to stock, you went to the bootloader and it found the PG32IMG? Or it just stayed on the options screen of reboot, recovery, factory reset, etc?
If it found the PG32IMG did it give you any messages? Did you check the md5 sum before trying to load it?

gtdtm said:
Well don't panic first of all. It's not super easy for me to figure out what's going on because your setup is quite different from mine, but I'm willing to offer any knowledge I have gleaned from reading these forums (a lot).
When you tried to go to stock, you went to the bootloader and it found the PG32IMG? Or it just stayed on the options screen of reboot, recovery, factory reset, etc?
If it found the PG32IMG did it give you any messages? Did you check the md5 sum before trying to load it?
Click to expand...
Click to collapse
haha too late for that, I'm already freaking out. It does find the PG32IMG automatically as I said and proceeds to load it. I was able to catch the message it flashes before it goes back to the default list, "wrong zipped image!" That doesn't sound good. I had not checked the md5sum prior to this, just did so now, says the codes do not match. Pardon my utter cluelessness but what on earth does that mean?

Zook024 said:
haha too late for that, I'm already freaking out. It does find the PG32IMG automatically as I said and proceeds to load it. I was able to catch the message it flashes before it goes back to the default list, "wrong zipped image!" That doesn't sound good. I had not checked the md5sum prior to this, just did so now, says the codes do not match. Pardon my utter cluelessness but what on earth does that mean?
Click to expand...
Click to collapse
You need to post the md5 sum from the return to stock thread, it is right below the download. If it doesn't match after that, you have a bad download and need to download it again on a good connection. I can't see the md5 very well in your screenshot, but it looks like it is correct. Then the other thing to check is that windows didn't add an extra .zip to the file name. You'll have to go into folder options and make it show known file types then see if it says it is PG32IMG.zip.zip or something. I'll keep looking around to help, but I'd suggest reading through a lot or all of that return to stock thread.
Is the file in the root of your microsd or in a different folder like downloads?

gtdtm said:
You need to post the md5 sum from the return to stock thread, it is right below the download. If it doesn't match after that, you have a bad download and need to download it again on a good connection. I can't see the md5 very well in your screenshot, but it looks like it is correct. Then the other thing to check is that windows didn't add an extra .zip to the file name. You'll have to go into folder options and make it show known file types then see if it says it is PG32IMG.zip.zip or something. I'll keep looking around to help, but I'd suggest reading through a lot or all of that return to stock thread.
Is the file in the root of your microsd or in a different folder like downloads?
Click to expand...
Click to collapse
Ok I corrected myself with the md5sum checker and now it confirms the codes match. I then doubled checked the file extension and it looks good as far as I can tell, I did not see a double .zip.zip anywhere, even after I selected "show file extensions of known files". I just tried again and got the same message,
"Checking....[PG32IMG.zip]
Wrong zipped image!
Loading...[PG32IMG.nbh]
No image or wrong image!"

Zook024 said:
Ok I corrected myself with the md5sum checker and now it confirms the codes match. I then doubled checked the file extension and it looks good as far as I can tell, I did not see a double .zip.zip anywhere, even after I selected "show file extensions of known files". I just tried again and got the same message,
"Checking....[PG32IMG.zip]
Wrong zipped image!
Loading...[PG32IMG.nbh]
No image or wrong image!"
Click to expand...
Click to collapse
Well, I'm running out of ideas. Hopefully someone else can chime in. I'd try downloading again and make sure the md5 is good, put it on the root of the microsd, and try one more time. Other than that my knowledge is spent.
Sent from my Incredible 2 using xda app-developers app

gtdtm said:
Well, I'm running out of ideas. Hopefully someone else can chime in. I'd try downloading again and make sure the md5 is good, put it on the root of the microsd, and try one more time. Other than that my knowledge is spent.
Sent from my Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
well I certainly appreciate you trying to help anyways. just on a hunch I tried running through the steps of the HTCdev bootloader which I had originally done and after doing so, it now says the following,
"Main Version is older!
Update Fail!
Press <POWER> to reboot."
that is interesting, should I try the VIPER ROM again and see what happens now?

Well I am happy to report now I have figured it out! I managed to find this video and by following his steps, I was immediately able to get the Viper ROM up and running. So I guess that is what I was doing wrong, trying to follow the S-Off Method when I had already gone halfway with the HTCDev method. Very glad I was able to get it done tonight, another case of "if I can break it, I can fix it!" case closed.

Zook024 said:
Well I am happy to report now I have figured it out! I managed to find this video and by following his steps, I was immediately able to get the Viper ROM up and running. So I guess that is what I was doing wrong, trying to follow the S-Off Method when I had already gone halfway with the HTCDev method. Very glad I was able to get it done tonight, another case of "if I can break it, I can fix it!" case closed.
Click to expand...
Click to collapse
Awesome. I'm glad you figured it out.
Sent from my Incredible 2 using xda app-developers app

[Q] Can't go back to 4.3 stock rom.

I'm fairly new to custom roms and flashing. On my AT&T Galaxy S3, I decided to update to 4.3. However, I tried updating ota using the About Phone > Software Update, however, that wasn't working for me (It kept saying: No updates available). I knew this wasn't true, so I searched around and found an option (In which all I had to use was the stock recovery and flash it on there, so I did. However, I found out about Knox and how rooting is not an option with knox, so I decided to look into custom roms. I got a custom recovery, noticed warranty bit 1, don't really care about that since I'm out of warranty anyways. So I flashed a lot of custom roms and their versions (Cm 10.2/11, Paranoid Android, Slim Bean, Illusion, and more) only to find out that I can't play any videos (browser, youtube, 3rd party apps, gallery, and even recording camera didn't work)(Also audio doesn't work at all). Now I want to switch back to regular stock 4.3 using the same file I used before. I tried flashing with a custom recovery (twrp and cwm) and it kept giving me:
(assert failed: file_getprop("/system/build.prop". robuild.fingerprint")
== "samsung/d2uc/d2att:4.1.2/JZO54K/I747UCMG2:user/release-keys" ||
file_getprop("/system/build.prop". robuild.fingerprint")
== "samsung/d2uc/d2att:4.3/JSS15J/I747UCUEMJB:user/release-keys"
E:Error in /sdcard/update43.zip
(status 7)
Installation aborted)
I searched around, and other people got this error mostly on a nexus when trying to get back to stock firmware. I found out that I need the stock recovery for the samsung galaxy s3 At&t, which I've searched around, and I can't find. Does anyone know a thread, or can upload their at&t samsung galaxy s3 stock recovery?

Status 7 is an error in the updater script. You may have a bad zip. Have you checked the MD5SUM in the zip that you downloaded?

codemonkey98 said:
Status 7 is an error in the updater script. You may have a bad zip. Have you checked the MD5SUM in the zip that you downloaded?
Click to expand...
Click to collapse
I re-downloaded the zip (which worked before on stock recovery). I don't know how to check the md5sum (On most roms, maybe this one since this one doesn't get to the point where it checks for it, it says checking for md5sum, then later says no md5sum found and skips). Maybe this is because It's expecting me to be on the "samsung/d2uc/d2att:4.1.2/JZO54K/I747UCMG2" version so I can update to the "samsung/d2uc/d2att:4.3/JSS15J/I747UCUEMJB" version. On Keyes 3 under my device apparently my current version is:
I747UCUEMJ2/I747ATTEMJ2//I747UCUEMJ2
And Keyes tells me that my devices current firmware is not supported to update firmware via keyes. Any ideas how to get back to stock? Also, does anyone have a clue why any sound and any video won't work on custom roms for me?

danman0 said:
I re-downloaded the zip (which worked before on stock recovery). I don't know how to check the md5sum (On most roms, maybe this one since this one doesn't get to the point where it checks for it, it says checking for md5sum, then later says no md5sum found and skips). Maybe this is because It's expecting me to be on the "samsung/d2uc/d2att:4.1.2/JZO54K/I747UCMG2" version so I can update to the "samsung/d2uc/d2att:4.3/JSS15J/I747UCUEMJB" version. On Keyes 3 under my device apparently my current version is:
I747UCUEMJ2/I747ATTEMJ2//I747UCUEMJ2
And Keyes tells me that my devices current firmware is not supported to update firmware via keyes. Any ideas how to get back to stock? Also, does anyone have a clue why any sound and any video won't work on custom roms for me?
Click to expand...
Click to collapse
I've had this issue before, VERY annoying. What I did was I downloaded a program for Windows called Notepad++ which allows you to edit the md5sum file.
What you need to do is unzip the file and search for the md5sum file and open it in Notepad++. Delete the lines that read "assert" and have the troublesome ID you mentioned in the OP. Re-zip the file and try flashing it again. Should be fine.

n_alvarez2007 said:
I've had this issue before, VERY annoying. What I did was I downloaded a program for Windows called Notepad++ which allows you to edit the md5sum file.
What you need to do is unzip the file and search for the md5sum file and open it in Notepad++. Delete the lines that read "assert" and have the troublesome ID you mentioned in the OP. Re-zip the file and try flashing it again. Should be fine.
Click to expand...
Click to collapse
I already have notepad++, but where do I search for the md5sum, since I've wanted to use Odin to flash this but it isn't a tar or md5 file. Should I check the updater script? And is this the reason audio and video don't work on any custom room I try?

danman0 said:
I already have notepad++, but where do I search for the md5sum, since I've wanted to use Odin to flash this but it isn't a tar or md5 file. Should I check the updater script? And is this the reason audio and video don't work on any custom room I try?
Click to expand...
Click to collapse
Sorry for sounding like a noob, but I am new to all of this. All I need is some help, I would prefer to run custom roms over stock (I like Illusion) except for video won't work as well as audio? Is there any way to fix that at least, or is there a way to fix my rom/recovery?

danman0 said:
Sorry for sounding like a noob, but I am new to all of this. All I need is some help, I would prefer to run custom roms over stock (I like Illusion) except for video won't work as well as audio? Is there any way to fix that at least, or is there a way to fix my rom/recovery?
Click to expand...
Click to collapse
http://www.sammobile.com/firmwares Search for you're model and download the LATEST firmware. Returning to 4.1.2 or lower will brick you're phone

Ali7000 said:
http://www.sammobile.com/firmwares Search for you're model and download the LATEST firmware. Returning to 4.1.2 or lower will brick you're phone
Click to expand...
Click to collapse
Can't do that since At&t update 4.3 (Latest) is pretty much ota and can't be downloaded from that site. It only goes up to 4.04.

danman0 said:
Can't do that since At&t update 4.3 (Latest) is pretty much ota and can't be downloaded from that site. It only goes up to 4.04.
Click to expand...
Click to collapse
http://www.sammobile.com/2013/11/20/android-4-3-rolling-out-for-the-att-galaxy-s-iii/ Just a news update

Have you tried this rom?
http://forum.xda-developers.com/showthread.php?t=2252932
I have been running this and have had no problems with anything working. As others have said don't flash anything besides 4.3 or you risk bricking your phone.

COfatboy said:
Have you tried this rom?
http://forum.xda-developers.com/showthread.php?t=2252932
I have been running this and have had no problems with anything working. As others have said don't flash anything besides 4.3 or you risk bricking your phone.
Click to expand...
Click to collapse
I am flashing this right now. I hope that this will work. It turns out that only mxplayer videos work, and no other third party video app. I looked around and these issues are most likely from not updated binaries or something, as mentioned in some threads.

Turns out that this rom: http://forum.xda-developers.com/show....php?t=2252932 doesn't work on my phone since it just never boots from the glowing samsung logo. I have attached a link to my video of how audio and video don't workand and only work on mxplayer.
http://www.youtube.com/watch?v=231HdNzlauQ

danman0 said:
Turns out that this rom: http://forum.xda-developers.com/show....php?t=2252932 doesn't work on my phone since it just never boots from the glowing samsung logo. I have attached a link to my video of how audio and video don't workand and only work on mxplayer.
http://www.youtube.com/watch?v=231HdNzlauQ
Click to expand...
Click to collapse
I tried a bit later and got this rom to boot, but I'm having same issues with audio and video. Also, I can't turn on wifi.

danman0 said:
I tried a bit later and got this rom to boot, but I'm having same issues with audio and video. Also, I can't turn on wifi.
Click to expand...
Click to collapse
You will need to flash a kernel to get the wi-fi to work. Try this one. works for me and many others who have suggested it. http://www.androidfilehost.com/?fid=23196940996968860
Post # 3 here, http://forum.xda-developers.com/showthread.php?t=2498233, is where I got that kernel. Be sure to thank him when it works.

BCSC said:
You will need to flash a kernel to get the wi-fi to work. Try this one. works for me and many others who have suggested it. http://www.androidfilehost.com/?fid=23196940996968860
Post # 3 here, http://forum.xda-developers.com/showthread.php?t=2498233, is where I got that kernel. Be sure to thank him when it works.
Click to expand...
Click to collapse
I got the wifi to work, but I still can't record video or hear audio. However, youtube does play up to 4 seconds of video, then the video freezes, but the bar resets to 0 and keeps moving forward and I don't see any more video other than the frozen frame. Could this be because of my custom binary count being 13?

danman0 said:
I got the wifi to work, but I still can't record video or hear audio. However, youtube does play up to 4 seconds of video, then the video freezes, but the bar resets to 0 and keeps moving forward and I don't see any more video other than the frozen frame. Could this be because of my custom binary count being 13?
Click to expand...
Click to collapse
The custom binary count just means you have been busy flashing non-official stuff. It is not related to your audio problem. Are you still on S3rx? Have you Factory wiped since discovering these issues?

BCSC said:
The custom binary count just means you have been busy flashing non-official stuff. It is not related to your audio problem. Are you still on S3rx?
Click to expand...
Click to collapse
Yes, I'm still on S3rx. When I first reboot my phone, I can't see the clock widget on the lock screen, but when i unlock and relock, it appears. Also, my imei and phone info is wiped, but since that doesn't explain audio and video not working, it doesn't matter at the moment. What else could be causing audio and video to not work?

danman0 said:
Yes, I'm still on S3rx. When I first reboot my phone, I can't see the clock widget on the lock screen, but when i unlock and relock, it appears. Also, my imei and phone info is wiped, but since that doesn't explain audio and video not working, it doesn't matter at the moment. What else could be causing audio and video to not work?
Click to expand...
Click to collapse
Sorry but I'm gonna ask a few more questions and see what I can find,
1. When you last tried to flash the stock 4.3 update, did you use the OTA zip that includes Knox and the bootloader?
2. Have you attempted to flash the stock rooted Att S3 image without the bootloader attached. See here:http://forum.xda-developers.com/showthread.php?t=2540998
3. Without imei you aren't receiving service are you?
The reason I'm asking so much about the stock ROMs is because somehow the audio/video issue you are having may be fixed by going back to stock and wiping everything and reinstalling your kernel again. I have not experienced an issue like this myself, these are just the steps I would take.

BCSC said:
Sorry but I'm gonna ask a few more questions and see what I can find,
1. When you last tried to flash the stock 4.3 update, did you use the OTA zip that includes Knox and the bootloader?
2. Have you attempted to flash the stock rooted Att S3 image without the bootloader attached
3. Without imei you aren't receiving service are you?
The reason I'm asking so much about the stock ROMs is because somehow the audio/video issue you are having may be fixed by going back to stock and wiping everything and reinstalling your kernel again. I have not experienced an issue like this myself, these are just the steps I would take.
Click to expand...
Click to collapse
I don't remember what a bootloader is, but I downloaded the stock firmware from here http://www.smartphonejam.com/2013/11/upgrade-att-galaxy-s3-official-android43-i747ucuemjb-ota-update.html since software update option wasn't showing any updates for me. Later on I installed loserskater's 4.3 noknox and selinux permissive version but i had the same problems as i do with S3rx right now. Then I decided to go to custom roms, thats when sound and video don't work at all.
I don't know how to unattach the bootloader image (if there is one).
Yes, I don't receive and service http://www.youtube.com/watch?v=231HdNzlauQ

danman0 said:
I don't remember what a bootloader is, but I downloaded the stock firmware from here http://www.smartphonejam.com/2013/11/upgrade-att-galaxy-s3-official-android43-i747ucuemjb-ota-update.html since software update option wasn't showing any updates for me. Later on I installed loserskater's 4.3 noknox and selinux permissive version but i had the same problems as i do with S3rx right now. Then I decided to go to custom roms, thats when sound and video don't work at all.
I don't know how to unattach the bootloader image (if there is one).
Yes, I don't receive and service http://www.youtube.com/watch?v=231HdNzlauQ
Click to expand...
Click to collapse
I'd recommend heading here and installing the upndwn4par stock ROM again. You did flash the one with the bootloader via that link you sent me. This link does not contain that bootloader. It has already been removed. Flash this and then wipe everything (cache,dalvik and full wipe/factory reset). http://forum.xda-developers.com/showthread.php?t=2540998. This could fix your video/audio issue.
s for your IMEI problem you may find your answer here: http://forum.xda-developers.com/showthread.php?t=2374063

ADB Sideload Error: unknown volume for path

I just ADB sideloaded NMF26Q over NMF26O using the full OTA files from Google.
It seemed to work fine, but I did get the following error in the recovery adb sideloaded screen:
Step 2/2
E:unknown volume for path /cache/recovery/uncrypt_status
Anyone seen this before? Is it normal? The sideloaded seems successful.

xdatastic said:
I just ADB sideloaded NMF26Q over NMF26O using the full OTA files from Google.
It seemed to work fine, but I did get the following error in the recovery adb sideloaded screen:
Step 2/2
E:unknown volume for path /cache/recovery/uncrypt_status
Anyone seen this before? Is it normal? The sideloaded seems successful.
Click to expand...
Click to collapse
Are you using the latest SDK?
Also stock recovery etc?

DaveHTC200 said:
Are you using the latest SDK?
Also stock recovery etc?
Click to expand...
Click to collapse
Yep, I updated the android tools before I did it. Using Ubuntu Linux.
Also, my XL 32GB is completely stock, locked bootloader etc.

Weird then!
It does seem to imply it as successful, but I'm guessing in about the update has not completed?

DaveHTC200 said:
Weird then!
It does seem to imply it as successful, but I'm guessing in about the update has not completed?
Click to expand...
Click to collapse
It seems to have been successful. Build.prop shows all the expected correct values.
I tried sideloading again, but same error.

xdatastic said:
It seems to have been successful. Build.prop shows all the expected correct values.
I tried sideloading again, but same error.
Click to expand...
Click to collapse
Well it's it worked I wouldn't worry ?

DaveHTC200 said:
Well it's it worked I wouldn't worry
Click to expand...
Click to collapse
FYI, had exact same message when updating sailfish (non-XL) from NMF26O to NMF26V. Can't find a problem post boot (and correctly shows NMF26V for Build number)

Had exact same error and the only search result led me to this thread. Until someone in the know comments I guess.

It doesn't seem to be an actual problem, the sideloading process still has a flag in it to throw that error message if it can't find the uncrypt status file at that path but phones that use the dual-slot partition system no longer have a separate /cache partition. Someone just hasn't gotten around to commenting out that location check for a/b partitioned phones yet.

Got this error today updating from 7.1.1 to 7.1.2 on my Pixel.
Thankfully as noticed, doesn't seem to actually cause any issues.

getting "your device is corrupt and cannot be trusted pixel"

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.

Please hold my hand on rolling back my OS. phone hasn't worked right since I got the android 12 update

I have a oneplus 7t, on straight talk using verizon towers.
So since I got the android 12 update, I have spent several hours on the phone with customer service, and haven't been able to fix every issue.
We did fix the problem where I had no data, customer service walked me through updating the APN and that was fixed.
-I still can't receive MMS pictures through the standard app, I can work around that using the google messages app, but that's frustrating since I know something isn't working correctly.
-I randomly get call failed when I try to accept a phone call. This happens very often, but i'm not sure why it doesn't happen every time. I seem to be able to make outbound calls without any issues.
Not being able to fix the call issues, and MMS issues makes me want to roll back to android 11. the phone worked great until this android 12 update. I tried a factory reset, and still have the same issues.
I've tried searching for instructions but all of them are lacking thorough instructions. They say "pick the matching file for your phone", but mine is 1905, but only 1901 and 1903 are listed. I'm sure one of those are supposed to work, but which one?
"download this apk"...... ok, now i have a .apk.zip file that i don't know what to do with.
-delete .zip and i don't know how to make the .apk file install or open
-unzip, and i have 500 files that i don't know what to do with.
"move this to the root storage".... how?
I used to be more tech enabled, but it's been so long since i've rooted a phone or something else this involved. I really just want my phone to work properly again.

Well I can get the local update apk to open, but I can't figure out where to place or what to name the roll back file for that apk to find it. This is frustrating and wasting many hours of my life

https://oxygenos.oneplus.net/OnePlus7TOxygen_14.I.31_OTA_0310_all_2112101928_downgrade_327348e7ed1f4427.zip

HueyT said:
https://oxygenos.oneplus.net/OnePlus7TOxygen_14.I.31_OTA_0310_all_2112101928_downgrade_327348e7ed1f4427.zip
Click to expand...
Click to collapse
Thanks, but that's not super helpful. I'm at the point where I'm struggling to get local update to find it, because I'm not sure where or how to move it to make it be found

dempseyjosh said:
Thanks, but that's not super helpful. I'm at the point where I'm struggling to get local update to find it, because I'm not sure where or how to move it to make it be found
Click to expand...
Click to collapse
Does the file contain something called MSM tool? If so you will need to do this from a Windows PC (or VM).
EDIT: nevermind disregard this post.

dempseyjosh said:
Thanks, but that's not super helpful. I'm at the point where I'm struggling to get local update to find it, because I'm not sure where or how to move it to make it be found
Click to expand...
Click to collapse
Move it from \sdcard\downloads to \sdcard root

I Need a little more specific help than that. Do I need to be hooked to a computer to do that? Does it mean to be changed at all? .zip.jar is correct? Because I've tried moving it from the downloads folder to device storage. It feels right to me, but it's not finding the file to update with.

dempseyjosh said:
I Need a little more specific help than that. Do I need to be hooked to a computer to do that? Does it mean to be changed at all? .zip.jar is correct? Because I've tried moving it from the downloads folder to device storage. It feels right to me, but it's not finding the file to update with.
Click to expand...
Click to collapse
No on pc. Yes to rename jar file to zip

HueyT said:
No on pc. Yes to rename jar file to zip
Click to expand...
Click to collapse
Thank you, that was the last bit of help I needed with that. I've successfully rolled back and my phone is working correctly, as far as I can tell.

Well you answered my question. "Do not take this upgrade"