Is it normal to get the "Your device might be corrupt" message if you just unlock your bootloader? I have not flashed a customer kernel or Magisk, just unlocked the bootloader. I was rooted with the fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img, but I did a clean flash of the firmware, but still get this message. When I have verity disabled I don't get the message. Just want to make sure that the message is normal?
Normal if you are unlocked.
Yep, normal.
Ok just making sure. It sucks that you have to push the power button to start your phone with just the bootloader unlocked.
ilatimer1 said:
Ok just making sure. It sucks that you have to push the power button to start your phone with just the bootloader unlocked.
Click to expand...
Click to collapse
You don't. It'll still boot on its own, just give it a few seconds. Actually, I think pressing the power button once causes it to pause booting.
roirraW edor ehT said:
You don't. It'll still boot on its own, just give it a few seconds. Actually, I think pressing the power button once causes it to pause booting.
Click to expand...
Click to collapse
No there are two messages. The first one is that you device might be corrupt. It requires you to press the power button to continue. The second message is the bootloader unlocked message with will just boot if you ignore it.
ilatimer1 said:
No there are two messages. The first one is that you device might be corrupt. It requires you to press the power button to continue. The second message is the bootloader unlocked message with will just boot if you ignore it.
Click to expand...
Click to collapse
Hmmm. You say when you have verity disabled, you don't get the message. If this is accurate, I would consider either keep disabling it each time you flash the stock image, or if you have the energy, do a factory reset, but note of course that a factory reset will cause your phone to require complete setup as if it was new. You'd still get the one message about the bootloader being unlocked - that's the one that's normal.
At this time, it would probably be helpful to know your complete situation.
We know you've unlocked the bootloader, and that at some point you disabled Verity and Verification, and it sounds like you reflashed stock with Verity and Verification not disabled. Correct me if I'm wrong. Can you be more detailed about exactly what's been done since you unlocked the bootloader?
roirraW edor ehT said:
Hmmm. You say when you have verity disabled, you don't get the message. If this is accurate, I would consider either keep disabling it each time you flash the stock image, or if you have the energy, do a factory reset, but note of course that a factory reset will cause your phone to require complete setup as if it was new. You'd still get the one message about the bootloader being unlocked - that's the one that's normal.
At this time, it would probably be helpful to know your complete situation.
We know you've unlocked the bootloader, and that at some point you disabled Verity and Verification, and it sounds like you reflashed stock with Verity and Verification not disabled. Correct me if I'm wrong. Can you be more detailed about exactly what's been done since you unlocked the bootloader?
Click to expand...
Click to collapse
So there is a little more backstory. I was rooted with verity disabled and everything was working fine. When it came out that the new Magisk did not need verity disabled I decided to start from scratch and clean flash my phone.
I used the Google online flashing tool and around 3/4 of the way through the laptop froze and the flash failed. I ended up soft bricking my phone. I was able to get back to fastboot and did a clean flash using the flash-all.bat file. I noticed that I now had the corruption message.
So after that I decide to use the Google online flashing tool one more time and was successful, but I still had the corruption message. I finally decided to relock the bootloader to see if that would help. The corruption message did go away after locking the bootloader.
Now with everything back to clean stock I decide to try an unlock the bootloader again and when I reboot I get the corruption again. I am at kind of a loss now on what to try. Just as a FYI, I did try having the Google flashing tool force partition flashing to see if that would help, but it did not.
ilatimer1 said:
So after that I decide to use the Google online flashing tool one more time and was successful, but I still had the corruption message. I finally decided to relock the bootloader to see if that would help. The corruption message did go away after locking the bootloader.
Now with everything back to clean stock I decide to try an unlock the bootloader again and when I reboot I get the corruption again. I am at kind of a loss now on what to try. Just as a FYI, I did try having the Google flashing tool force partition flashing to see if that would help, but it did not.
Click to expand...
Click to collapse
Try a factory reset without any further flashing and see if that helps. Settings / System / Reset options / Erase all data (factory reset).
First, thank you all for offering advice. I ended up resolving my issue by downgrading to .37 and now the corruption message is gone with the bootloader unlocked .
ilatimer1 said:
First, thank you all for offering advice. I ended up resolving my issue by downgrading to .37 and now the corruption message is gone with the bootloader unlocked .
Click to expand...
Click to collapse
For my small part, you're welcome. Are you going to try to re-upgrade? It's a very unusual problem and there should be a solution - I just don't know what it is, but there are a lot more knowledgeable folks around here.
roirraW edor ehT said:
For my small part, you're welcome. Are you going to try to re-upgrade? It's a very unusual problem and there should be a solution - I just don't know what it is, but there are a lot more knowledgeable folks around here.
Click to expand...
Click to collapse
I just sideloaded the .17 update and everything is good to go!
Related
I was using my phone like I usually do, and then it suddenly froze. So I held down the power button, forcing it to restart. Ever since, the screen only shows "Google" for a while, then becomes blank; no booting animation. It would restart itself occasionally.
I tried booting into recovery mode by holding Power+VolDown, and selecting "recovery mode". For the first few tries, it would go back to the Google screen, the turn blank. After giving it a break and trying again, I finally got to the "no command" screen, and I wiped the cache partition. Sadly, I'm still having the same problem.
Is this a bootloop? How can I fix this?
Any help would be greatly appreciated.
This happened to me and Google sent a replacement phone. However the replacement phone is a refurbished phone that suffers from ghost touches Now trying to get a replacement for the replacement.
Ocelot584 said:
I was using my phone like I usually do, and then it suddenly froze. So I held down the power button, forcing it to restart. Ever since, the screen only shows "Google" for a while, then becomes blank; no booting animation. It would restart itself occasionally.
I tried booting into recovery mode by holding Power+VolDown, and selecting "recovery mode". For the first few tries, it would go back to the Google screen, the turn blank. After giving it a break and trying again, I finally got to the "no command" screen, and I wiped the cache partition. Sadly, I'm still having the same problem.
Is this a bootloop? How can I fix this?
Any help would be greatly appreciated.
Click to expand...
Click to collapse
can u boot into bootloader mode?
dominoeflux said:
can u boot into bootloader mode?
Click to expand...
Click to collapse
What's that? Is it the screen that comes up when you hold down Power+VolumeDown and gives you the option to select Start, Power Off, Restart Bootloader, or Recovery?
Ocelot584 said:
What's that? Is it the screen that comes up when you hold down Power+VolumeDown and gives you the option to select Start, Power Off, Restart Bootloader, or Recovery?
Click to expand...
Click to collapse
Yes that's the one. If u can get back to that screen you should be able to flash it back stock and re root the phone with out any problems
dominoeflux said:
Yes that's the one. If u can get back to that screen you should be able to flash it back stock and re root the phone with out any problems
Click to expand...
Click to collapse
So are you saying that I should factory reset my phone from the recovery menu, or do I have to use the method that requires the factory image?
My phone wasn't rooted btw, so I can't re-root it.
Ocelot584 said:
So are you saying that I should factory reset my phone from the recovery menu, or do I have to use the method that requires the factory image?
My phone wasn't rooted btw, so I can't re-root it.
Click to expand...
Click to collapse
Oh ok I thought it was sorry if I wasn't of any help
dominoeflux said:
Oh ok I thought it was sorry if I wasn't of any help
Click to expand...
Click to collapse
haha it's ok you tried to.
Rooted or not, do you think factory resetting it will fix the problem as long as I can get to the bootloader menu?
Ocelot584 said:
haha it's ok you tried to.
Rooted or not, do you think factory resetting it will fix the problem as long as I can get to the bootloader menu?
Click to expand...
Click to collapse
In pretty positive that it will, make sure u unlock the Bootloader first before you do anything. Do you know how to unlock it?
dominoeflux said:
In pretty positive that it will, make sure u unlock the Bootloader first before you do anything. Do you know how to unlock it?
Click to expand...
Click to collapse
nope...what's a bootloader anyway?
Ocelot584 said:
nope...what's a bootloader anyway?
Click to expand...
Click to collapse
The bootloader allows the phone to be unlocked to flash custom ROMs on it, without it unlocked you'll brick your phone. Read up about rooting your phone first so you can get the idea of what goes into it before attempting it. Once you get the general idea of unlocking the phone and flashing things on it, it becomes relatively easy. There's even a nexus root toolkit on this forum that you can download on your computer for free as well as "how-to's" for doing it
dominoeflux said:
The bootloader allows the phone to be unlocked to flash custom ROMs on it, without it unlocked you'll brick your phone. Read up about rooting your phone first so you can get the idea of what goes into it before attempting it. Once you get the general idea of unlocking the phone and flashing things on it, it becomes relatively easy. There's even a nexus root toolkit on this forum that you can download on your computer for free as well as "how-to's" for doing it
Click to expand...
Click to collapse
Wait...what?? So if I choose to factory reset my phone now without unlocking the bootloader, it might become completely useless? Is rooting necessary?
Ocelot584 said:
Wait...what?? So if I choose to factory reset my phone now without unlocking the bootloader, it might become completely useless? Is rooting necessary?
Click to expand...
Click to collapse
No is not necessary, but in order to re flash the factory image to fix the problem the bootloader must be unlocked. You never have to root your device but having a unlocked bootloader is essential to flashing anything on your device other wise like I said, you'll brick your phone. You can even lock it back to full stock once you've re flashed the image.
Edit: there's another way of flashing the factory image but it requires some searching. You might not be able to do it the way I'm explaining to you Because you would have to give it permission to be unlocked in the developers option while the phone is booted up and operative
dominoeflux said:
No is not necessary, but in order to re flash the factory image to fix the problem the bootloader must be unlocked. You never have to root your device but having a unlocked bootloader is essential to flashing anything on your device other wise like I said, you'll brick your phone. You can even lock it back to full stock once you've re flashed the image.
Edit: there's another way of flashing the factory image but it requires some searching. You might not be able to do it the way I'm explaining to you Because you would have to give it permission to be unlocked in the developers option while the phone is booted up and operative
Click to expand...
Click to collapse
Oh...I see. So what about the factory reset option in the recovery menu? Would you expect that to fix it too?
Ocelot584 said:
Oh...I see. So what about the factory reset option in the recovery menu? Would you expect that to fix it too?
Click to expand...
Click to collapse
Of course
Edit: have you tried resetting it in the factory recovery?
dominoeflux said:
Of course
Edit: have you tried resetting it in the factory recovery?
Click to expand...
Click to collapse
Nope...I was waiting to see if I could find a way to recover my data first
Ocelot584 said:
Nope...I was waiting to see if I could find a way to recover my data first
Click to expand...
Click to collapse
When u first bought your phone and it takes you through the set up window, when it asked you to put in your email, that right there backs up all your apps that you previously had in the phone so when you go through the setup again, it's going to ask you if you want to start as a new phone or recover your previous apps. You won't be able to recover all of your data but you should be able to recover all of your apps.
dominoeflux said:
When u first bought your phone and it takes you through the set up window, when it asked you to put in your email, that right there backs up all your apps that you previously had in the phone so when you go through the setup again, it's going to ask you if you want to start as a new phone or recover your previous apps. You won't be able to recover all of your data but you should be able to recover all of your apps.
Click to expand...
Click to collapse
Alright, but since all my data won't be recovered, is there a way to get access to files on my phone before I factory reset it?
Ocelot584 said:
Alright, but is there a way to get access to files on my phone before I factory reset it?
Click to expand...
Click to collapse
Sorry bro but I wish there was.... There actually is away, but you would have have to have been rooted with a custom recovery on your phone and since you had neither, there's my other way
Edit: I meant no other way
dominoeflux said:
Sorry bro but I wish there was.... There actually is away, but you would have have to have been rooted with a custom recovery on your phone and since you had neither, there's my other way
Edit: I meant no other way
Click to expand...
Click to collapse
oh... wow.
I'll just suck it up and reset it then. I'll let u know how it goes.
Hello XDA!
I have a Verizon Pixel XL that is stuck in a boot-loop after the 7.1.2 firmware update. The boot-loop did not begin immediately after the update which confuses me. I have never attempted to unlock the bootloader, root, or flash the firmware. I have thousands of pictures I am attempting to recover (I did not have coverage to backup the pictures in Google Photos) before I work on the boot-loop issue (or warranty replacement). I can access fastboot & recovery but these modes do not provide a backup option or backup command from ADB. When I boot to safe-mode the phone will stay on for about 10 seconds which has allowed me to disable a LOT of apps and enable USB debug.
As I see it, there are only two options available to me...
1) Find a way to 'halt' the system after start-up or find the mysterious app causing the issue and disable it.
2) Forensic (physical) data recovery for $500-$900
I have tried to research as much as possible (please correct me if I'm wrong): unlocking Verizon bootloader is not currently possible, installing custom recovery is either not possible or will wipe the device, and pushing a firmware update will also wipe the device.
If anyone has any suggestions or would like more information please let me know.
I will keep an eye on this thread to provide timely responses.
Thank you,
Matthew
w144mjb said:
Hello XDA!
I have a Verizon Pixel XL that is stuck in a boot-loop after the 7.1.2 firmware update. The boot-loop did not begin immediately after the update which confuses me. I have never attempted to unlock the bootloader, root, or flash the firmware. I have thousands of pictures I am attempting to recover (I did not have coverage to backup the pictures in Google Photos) before I work on the boot-loop issue (or warranty replacement). I can access fastboot & recovery but these modes do not provide a backup option or backup command from ADB. When I boot to safe-mode the phone will stay on for about 10 seconds which has allowed me to disable a LOT of apps and enable USB debug.
As I see it, there are only two options available to me...
1) Find a way to 'halt' the system after start-up or find the mysterious app causing the issue and disable it.
2) Forensic (physical) data recovery for $500-$900
I have tried to research as much as possible (please correct me if I'm wrong): unlocking Verizon bootloader is not currently possible, installing custom recovery is either not possible or will wipe the device, and pushing a firmware update will also wipe the device.
If anyone has any suggestions or would like more information please let me know.
I will keep an eye on this thread to provide timely responses.
Thank you,
Matthew
Click to expand...
Click to collapse
Flashing updates do not wipe your data. Download firmware of choice. Unzip it, place latest fastboot drivers in where update zip is. Rename it to something easy. fastboot update update.zip
Edit: enclosed fastboot drivers
Tulsadiver said:
Flashing updates do not wipe your data. Download firmware of choice. Unzip it, place latest fastboot drivers in where update zip is. Rename it to something easy. fastboot update update.zip
Edit: enclosed fastboot drivers
Click to expand...
Click to collapse
Thank you Tulsadiver!
Do you think the firmware update will also fix the boot loop?
w144mjb said:
Thank you Tulsadiver!
Do you think the firmware update will also fix the boot loop?
Click to expand...
Click to collapse
Of that I do not know. You really should go ahead and flash the entire firmware. You need to open the flash-all.bat and remove the -w or it WILL wipe your data.
Tulsadiver said:
Of that I do not know. You really should go ahead and flash the entire firmware. You need to open the flash-all.bat and remove the -w or it WILL wipe your data.
Click to expand...
Click to collapse
Being the noob that I am, I have a few more questions.
Do I have to unlock the bootloader to update the firmware?
I'm currently on NHG470 firmware, should I choose NHG47N or NHG47K or a different one?
I'd like to keep the phone on a factory image unless you suggest otherwise.
Thank you for your time and patience,
Matthew
w144mjb said:
Being the noob that I am, I have a few more questions.
Do I have to unlock the bootloader to update the firmware?
I'm currently on NHG470 firmware, should I choose NHG47N or NHG47K or a different one?
I'd like to keep the phone on a factory image unless you suggest otherwise.
Thank you for your time and patience,
Matthew
Click to expand...
Click to collapse
Yes, you must unlock the bootloader...you are on Verizon and I am unfamiliar with their procedure and even if the bootloader is unlockable. You had better talk to someone on a Verizon phone.
Tulsadiver said:
Of that I do not know. You really should go ahead and flash the entire firmware. You need to open the flash-all.bat and remove the -w or it WILL wipe your data.
Click to expand...
Click to collapse
Tulsadiver said:
Yes, you must unlock the bootloader...you are on Verizon and I am unfamiliar with their procedure and even if the bootloader is unlockable. You had better talk to someone on a Verizon phone.
Click to expand...
Click to collapse
On Android source I am reading that unlocking the bootloader requires a full wipe.
https://source.android.com/source/running#unlocking-the-bootloader
Please advise.
Thank you,
Matthew
w144mjb said:
On Android source I am reading that unlocking the bootloader requires a full wipe.
https://source.android.com/source/running#unlocking-the-bootloader
Please advise.
Thank you,
Matthew
Click to expand...
Click to collapse
That is true.
If you take it to a Verizon store and explain the situation they might be able to help.
Tulsadiver said:
That is true.
Click to expand...
Click to collapse
Ok, good to know.
The only reason for this thread is to explore data recovery options, not to fix the boot loop.
Thank you,
Matthew
w144mjb said:
Ok, good to know.
The only reason for this thread is to explore data recovery options, not to fix the boot loop.
Thank you,
Matthew
Click to expand...
Click to collapse
I understand but my stepson has worked for every Carrier and they have access to software that might help. You already have a phone coming in so no skin off their nose.
w144mjb said:
Ok, good to know.
The only reason for this thread is to explore data recovery options, not to fix the boot loop.
Thank you,
Matthew
Click to expand...
Click to collapse
I'm pretty sure you're SOL if you can't get it to boot to system. I don't think you can pull the data off the device without being in system. Even if you can it would be encrypted. So you wouldn't be able to do anything with it. Have you tried to boot in safe mode. If you get it to boot up in safe mode then you can pull the data off with no issues.
Tulsadiver said:
I understand but my stepson has worked for every Carrier and they have access to software that might help. You already have a phone coming in so no skin off their nose.
Click to expand...
Click to collapse
I'll give Verizon technical support a call tonight (or a few, as necessary) and update you after.
Thank you,
Matthew
toknitup420 said:
I'm pretty sure you're SOL if you can't get it to boot to system. I don't think you can pull the data off the device without being in system. Even if you can it would be encrypted. So you wouldn't be able to do anything with it. Have you tried to boot in safe mode. If you get it to boot up in safe mode then you can pull the data off with no issues.
Click to expand...
Click to collapse
It will stay on for about 10 seconds in Safe mode.
w144mjb said:
It will stay on for about 10 seconds in Safe mode.
Click to expand...
Click to collapse
Safe mode only runs stock apps so if you are still boot looping in safe mode it's unlikely an app is causing your problem. I'm not sure what you mean when you say you didn't have coverage to back up your photos in Google Photos --i thought all Pixel phones came with unlimited original quality photo backup as long as the photos were uploaded from your phone. At this point I don't think you can recover your photos unless you find a way to fix the boot loop. Your boot loop where it didn't happen immediately after the update and it allows you into safe mode briefly sounds kind of unusual and might be the result of a hardware problem on your phone rather than a software issue. Have you tried booting the phone up while it is plugged into a wall outlet to see if that makes any difference? Some people with boot loop issues on the Pixels have reported that allowing the battery to completely run down until the phone is dead and then plugging the phone into a wall outlet allowed them to boot up normally. If you try that maybe you will get lucky but your options are very limited at this point.
My mom's pixel 2 xl all of a sudden wont boot. It said cant find valid operation system. The device will not start. She said it might have updated overnight or something like that. I tried to download the factory image from google to restore the OS but it wont flash without bootloader being unlock. It odd that the phone was working and now it doesnt have an OS.
Any help is appreciated. Thanks.
sumasage said:
My mom's pixel 2 xl all of a sudden wont boot. It said cant find valid operation system. The device will not start. She said it might have updated overnight or something like that. I tried to download the factory image from google to restore the OS but it wont flash without bootloader being unlock. It odd that the phone was working and now it doesnt have an OS.
Any help is appreciated. Thanks.
Click to expand...
Click to collapse
Can you get to stock recovery for a factory reset?
It doesn't even let me get to recover. Picking recovery from the bootloader screen just make the phone restart like it try to go to recovery but then it come back to the same screen saying it can't find valid operating system.
Same happend to me on my first unit when I relocated the bootloader.
Unit resetted and then can no longer find an operating system..
Only option was to call Google and RMA it. I've seen it happen to others on the web as well
trim81 said:
Same happend to me on my first unit when I relocated the bootloader.
Unit resetted and then can no longer find an operating system..
Only option was to call Google and RMA it. I've seen it happen to others on the web as well
Click to expand...
Click to collapse
What did you say Google? Did you tell them it happened while re-locking boot loader? I am on same boat....I tried to relock bootloader and getting Can't find valid operating system
I rma the unit as well.
sumasage said:
I rma the unit as well.
Click to expand...
Click to collapse
Did they accept the RMA? Was the issue after an update or did you try to flash the update using adb or fastboot?
ram4ufriends said:
Did they accept the RMA? Was the issue after an update or did you try to flash the update using adb or fastboot?
Click to expand...
Click to collapse
Tell them exactly that. It no longer boots
As soon as I said there was no valid os the rep proceeded to rma. Seem like it a know issue so they didn't bother to transfer me to tech support.
Not sure if you want to try any of these solutions before you RMA, but here's another thread on the same "No OS ....." with several options, might be worth a try?
I ran into the same issue, however I found a solution, perhaps universal perhaps not.
When I enter fastboot mode, my phone shows (until I release the power/vol buttons) the "Start" option that is part of the boot mode. After releasing, I get the "no rom detected." So I used the script at the top of https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761. I used the script by running it WHILE pressing the Power/Vol keys.
This worked for me.
Note: I let go of power/vol after starting script.
megernic said:
I ran into the same issue, however I found a solution, perhaps universal perhaps not.
When I enter fastboot mode, my phone shows (until I release the power/vol buttons) the "Start" option that is part of the boot mode. After releasing, I get the "no rom detected." So I used the script at the top of https://forum.xda-developers.com/pi...l-deuces-bootloop-recovery-flashing-t3704761. I used the script by running it WHILE pressing the Power/Vol keys.
This worked for me.
Note: I let go of power/vol after starting script.
Click to expand...
Click to collapse
Did you check or uncheck OEM unlocking in Developer Options before doing this?
Hy guys, i need your help.
I bought a XA2 off of ebay with a bootloop issue. I thougth that a software recovery with PC companion would solve the issue, but sadly it didn`t. It failed to update the device.
The EMMA tool finds the device with the bootloader locked.
I tried multiple times to flash different stock roms with the flashtool, wiping all data from the phone. Nothing seems to work. When wiping all the data flashtool hangs, but when wiping all but leaving the user data, the flashtool completes but the phone is still in bootloop.
erase:userdata
erase status:fail
Write-TA:2:2311 --- hangs
Please advice further, thanks!
madhogg said:
Hy guys, i need your help.
I bought a XA2 off of ebay with a bootloop issue. I thougth that a software recovery with PC companion would solve the issue, but sadly it didn`t. It failed to update the device.
The EMMA tool finds the device with the bootloader locked.
I tried multiple times to flash different stock roms with the flashtool, wiping all data from the phone. Nothing seems to work. When wiping all the data flashtool hangs, but when wiping all but leaving the user data, the flashtool completes but the phone is still in bootloop.
erase:userdata
erase status:fail
Write-TA:2:2311 --- hangs
Please advice further, thanks!
Click to expand...
Click to collapse
Try 'newflasher'
hamirali said:
Try 'newflasher'
Click to expand...
Click to collapse
Tried, no luck.
It looks like the USERDATA has the issue. Everything hangs when it reaches that part of the flashing process.
madhogg said:
Tried, no luck.
It looks like the USERDATA has the issue. Everything hangs when it reaches that part of the flashing process.
Click to expand...
Click to collapse
Just a very amateur suggestion: load into twrp, change boot slot and try newflasher again.
hamirali said:
Just a very amateur suggestion: load into twrp, change boot slot and try newflasher again.
Click to expand...
Click to collapse
I don't know how to do that, do you have any guide i can follow? I am not shure if i can do that, since the bootloader is locked, and no way to unlock it, because i can't select the option in the system settings like usb debugging and allow oem unlock
madhogg said:
I don't know how to do that, do you have any guide i can follow? I am not shure if i can do that, since the bootloader is locked, and no way to unlock it, because i can't select the option in the system settings like usb debugging and allow oem unlock
Click to expand...
Click to collapse
Right I missed that bit in your first post about the bootloader being locked.
Well if I were in your position, I would assume - since it is in a bootloop - that both the other 2 things could have been already allowed by the previous owner.
It is not necessarily the obvious case, but there's no loss assuming that and try to unlock the bootloader vis usb.
you must know your IMEI though.
Hopefully, someone with real expertise can guide you here. Good luck!
I got impatient and decided to flash the Dec 2021 US Carrier factory image on my unlocked Pixel 6 Pro.
I set my device to OEM unlocking, grabbed the latest ABD/Fastboot files from Google, went into the bootloader and unlocked it w/ "fastboot flashing unlock", and then proceeded to flash my device. However, I now get a "Your device is corrupt. It can't be trusted and may not work properly" error w/ a red triangle exclamation mark upon boot. I can click the power button to get past it and the device will appear to boot, but it stays stuck on the Google screen w/ white background.
I'm able to manually restart into fastboot and fastboot devices recognizes the device.
I've flashed all my previous Pixel's many times before and never came across this error. Any ideas?
Deleted
You're going to have to use the Android flash tool now. Just follow the link in the Google factory image site. You'll be able to get back to December at the very end. It'll tell you to relock your bootloader Don't do it if you don't want to.
lil_michelle said:
Did you flash disable dm verity first after unlocking the bootloader before flashing a patched system image?
Click to expand...
Click to collapse
mac796 said:
You're going to have to use the Android flash tool now. Just follow the link in the Google factory image site. You'll be able to get back to December at the very end. It'll tell you to relock your bootloader Don't do it if you don't want to.
Click to expand...
Click to collapse
thank you! Using the Android Flash Tool resolved my issue.
I did this exact same thing, unlocked device, and flash-all.bat the December update, except my device was a hard brick. I could get zero response from the device, no matter how long I would hold in the power button. Connecting to computer would chime connected, then disconnect a second later. After the flash-all.bat command, it finished successfully, the phone rebooted to a screen that said software was corrupt and would not boot. Pressed power to move passed it and phone went black forever. Had 98% battery too. Had to send back to google for replacement. Did I miss something, or was it just the super buggy December update that did it. I am now scared to death to root this phone again fearing that I did something wrong, and that it will do this again. Is fastboot flashing the factory image a bad thing now, did I miss something, or was it just some weird glitch?
summitfox said:
I did this exact same thing, unlocked device, and flash-all.bat the December update, except my device was a hard brick. I could get zero response from the device, no matter how long I would hold in the power button. Connecting to computer would chime connected, then disconnect a second later. After the flash-all.bat command, it finished successfully, the phone rebooted to a screen that said software was corrupt and would not boot. Pressed power to move passed it and phone went black forever. Had 98% battery too. Had to send back to google for replacement. Did I miss something, or was it just the super buggy December update that did it. I am now scared to death to root this phone again fearing that I did something wrong, and that it will do this again. Is fastboot flashing the factory image a bad thing now, did I miss something, or was it just some weird glitch?
Click to expand...
Click to collapse
Hard to say, for those of us who haven't had any problems...yet. I've flashed the full factory image at least twice so far.
Normally, the USB cable and to a lesser extent, the USB port used on the computer, would be my first suspects as to the problem, but since you said it finished successfully, I have no clue.
Do I need to disable dm verity at least once, or is that just completely obsolete now.
summitfox said:
Do I need to disable dm verity at least once, or is that just completely obsolete now.
Click to expand...
Click to collapse
When using Magisk 23016 for rooting it is not necessary at all.
summitfox said:
Do I need to disable dm verity at least once, or is that just completely obsolete now.
Click to expand...
Click to collapse
The *only* time you *might* still need to disable verity and verification are for some custom kernels - until those kernels are updated the same way Magisk Canary 23016 was, and then they won't need it. If you're not planning on using custom kernels, and just rooting the stock kernel instead, then there's no reason to disable them anymore.
tuffCookie said:
I got impatient and decided to flash the Dec 2021 US Carrier factory image on my unlocked Pixel 6 Pro.
I set my device to OEM unlocking, grabbed the latest ABD/Fastboot files from Google, went into the bootloader and unlocked it w/ "fastboot flashing unlock", and then proceeded to flash my device. However, I now get a "Your device is corrupt. It can't be trusted and may not work properly" error w/ a red triangle exclamation mark upon boot. I can click the power button to get past it and the device will appear to boot, but it stays stuck on the Google screen w/ white background.
I'm able to manually restart into fastboot and fastboot devices recognizes the device.
I've flashed all my previous Pixel's many times before and never came across this error. Any ideas?
Click to expand...
Click to collapse
summitfox said:
I did this exact same thing, unlocked device, and flash-all.bat the December update, except my device was a hard brick. I could get zero response from the device, no matter how long I would hold in the power button. Connecting to computer would chime connected, then disconnect a second later. After the flash-all.bat command, it finished successfully, the phone rebooted to a screen that said software was corrupt and would not boot. Pressed power to move passed it and phone went black forever. Had 98% battery too. Had to send back to google for replacement. Did I miss something, or was it just the super buggy December update that did it. I am now scared to death to root this phone again fearing that I did something wrong, and that it will do this again. Is fastboot flashing the factory image a bad thing now, did I miss something, or was it just some weird glitch?
Click to expand...
Click to collapse
Did either of you verify the hash of the download before flashing?
Before flashing any image, the hash should always be verified as it ensures the file is secure and not corrupted.
JW09I4 said:
Before flashing any image, the hash should always be verified as it ensures the file is secure and not corrupted.
Click to expand...
Click to collapse
^ This. For years now, I've just gotten used to verifying the hash of every important thing that I download that has the hash value made available. Saves a lot of hassle later on since if the downloaded file is corrupted just slightly, everything will go wrong down the road in the process.
I also check for new Platform Tools and Google's USB driver each and every time I flash a new update. It's just habit and again, saves a lot of trouble.
To add on the previously said:
Windows has a built-in hash checker, you just need to open CMD and type
Get-FileHash <Drag'n'Drop'le'File'here>
Click to expand...
Click to collapse
Then just copy the hash (strg+c) into your browser search window where you downloaded the OTA/firmware (strg f to open search, strg v to paste) and if you get a match (1/1), the hash checks out.
It's easy, it's fast, it's reliable. It will only cost you a few seconds. No hassle involved.
Morgrain said:
Windows has a built-in hash checker, you just need to open CMD and type
Click to expand...
Click to collapse
For anyone who doesn't know, this is referencing Windows' built-in PowerShell. It may be the default these days as Microsoft pushes it and it's more capable than Command Prompt, but you can still open CMD and the "Get-FileHash" won't be available there.
Morgrain said:
To add on the previously said:
Windows has a built-in hash checker, you just need to open CMD... Then just copy the hash (strg+c) into your browser search window where you downloaded the OTA/firmware (strg f to open search, strg v to paste) and if you get a match (1/1), the hash checks out.
Click to expand...
Click to collapse
roirraW edor ehT said:
For anyone who doesn't know, this is referencing Windows' built-in PowerShell. It may be the default these days as Microsoft pushes it and it's more capable than Command Prompt, but you can still open CMD and the "Get-FileHash" won't be available there.
Click to expand...
Click to collapse
It's often better to use a program that will compare the hashes, else a SHA256 or SHA512 hash becomes tedious to manually compare - I'm partial to QuickHash [GitHub] due to its broad functionality (drag and drop file for it to auto-compute hash and you can paste what the hash should be either before or after)
For quick one or two-file comparisons, I prefer Implebits' HashTab, which adds a new configurable tab to the file properties dialog in Windows. I originally got turned onto the program when it was Beeblebrox.org, which being a Douglas Adams fan definitely got my attention back then but I stuck with it after they sold it.
Edit: I see Implebits is going out of business and HashTab will go to GitHub and be open source, so exciting times!
Implbits Software, LLC is going out of business
We will soon release Hashtab as an Open Source project on Github. Until we do... you can download the last build of Hashtab that we made using the link below:
Click to expand...
Click to collapse
Actually the same situation here. What's the version of your adb tool. Do I have to use the web tool to flash in the future? Could I use adb with flash.bat as always？
mac796 said:
You're going to have to use the Android flash tool now. Just follow the link in the Google factory image site. You'll be able to get back to December at the very end. It'll tell you to relock your bootloader Don't do it if you don't want to.
Click to expand...
Click to collapse
That's what I had to do and agree to relock bootloader
Joynaruto said:
Actually the same situation here. What's the version of your adb tool. Do I have to use the web tool to flash in the future? Could I use adb with flash.bat as always？
Click to expand...
Click to collapse
Tried that with no joy as future idk. My situation was different after flashing Los the recovery was overwritten and flashing stock said something about timestamp error
summitfox said:
I did this exact same thing, unlocked device, and flash-all.bat the December update, except my device was a hard brick. I could get zero response from the device, no matter how long I would hold in the power button. Connecting to computer would chime connected, then disconnect a second later. After the flash-all.bat command, it finished successfully, the phone rebooted to a screen that said software was corrupt and would not boot. Pressed power to move passed it and phone went black forever. Had 98% battery too. Had to send back to google for replacement. Did I miss something, or was it just the super buggy December update that did it. I am now scared to death to root this phone again fearing that I did something wrong, and that it will do this again. Is fastboot flashing the factory image a bad thing now, did I miss something, or was it just some weird glitch?
Click to expand...
Click to collapse
I think you should of used the full image not the update with flashall.bat
tuffCookie said:
I got impatient and decided to flash the Dec 2021 US Carrier factory image on my unlocked Pixel 6 Pro.
I set my device to OEM unlocking, grabbed the latest ABD/Fastboot files from Google, went into the bootloader and unlocked it w/ "fastboot flashing unlock", and then proceeded to flash my device. However, I now get a "Your device is corrupt. It can't be trusted and may not work properly" error w/ a red triangle exclamation mark upon boot. I can click the power button to get past it and the device will appear to boot, but it stays stuck on the Google screen w/ white background.
I'm able to manually restart into fastboot and fastboot devices recognizes the device.
I've flashed all my previous Pixel's many times before and never came across this error. Any ideas?
Click to expand...
Click to collapse
I had this before as well after manually flashing the November update. Got the device cannot be trusted. Rebooted, flashed again, and device completely fried. Wouldn't turn on, not recognized by computer, nothing. Complete brick. Suspect system board fried. I'll never try to manually flash an update with a Google device again. Hopefully it ends better for you.