Related
Hey guys,
apart from my Un-Bricking-Thread I wanted to start a Thread dealing with how to prevent a brick in the first place.
--- Already bricked your Prime? Read on here, maybe you can recover it ---
In the last days I learned quite a few things about the TFP, its CWM and how to work with it. I also hard bricked my Prime so I certainly know what I am talking about
Unfortunately ASUS didn't fully unlock our Bootloader. We still can't use NVFLASH for low level flashs.
This also means that we can't recover some things we could with NVFLASH access (like a broken bootloader).
So lets start with the things you better not do:
DON'T
Once you unlocked the prime and installed CWM, do NOT try to install a super blob from ASUS (that is a blob file from one of the 'full' updates from their site)
It seems that doing so totally bricks your Prime with no chance of recovery... (happened at least twice so far)
Don't flash kernels like you used to flash (with write_raw_image to /boot). This does not work on the Prime. More on how to do it later.
Don't rely on your newly created ROM to work, ALWAYS have a backup of a working ROM on your sdcard (or a zip of a working ROM)
Currently we can't mount the USB-Storage from inside CWM, so transferring files to the Prime while being in recovery is not as easy for many not so advanced users.
Always make sure you have all files you need before rebooting to recovery.
DO
Kernel flashing: There seem to be two methods on how to flash a new kernel. One is safer but needs a bit more work, and the other is rather unsafe but okay when you (or the ROM dev) know what needs to be done.
Flash your boot.img via fastboot. This is usually rather safe (as safe as fastboot can be) but needs you to have a working fastboot environment. Update: It seems kernel flashing via fastboot does not work at all. Fastboot doesn't give you an error but it doesn't update the kernel either...
Flash your kernel via the /staging partition. In order to use this method you first need to pack your boot.img into a blob file.
Then you need put the data from the blob file to the /staging partition.
Once you reboot the kernel gets automatically installed.
Please be aware that you can flash almost everything like this, even the bootloader.
So if you screw up packing the blob file, you could easily brick your Prime.
The advantage of this method is that the user doesn't need to do anything, but you really need to take care of what you are doing.
Also make sure that the /staging partition is ALWAYS unmounted before flashing anything to it. Otherwise this will result in a Brick 3.
Always make a backup of your current ROM before flashing anything else. As stated earlier, we currently have no access to the sdcard in recovery, so transferring files to Prime is not as easy in recovery mode.
So I hope I can find some more topics in the future, but for now that's it
Diamondback said:
DON'T
Once you unlocked the prime and installed CWM, do NOT try to install a super blob from ASUS (that is a blob file from one of the 'full' updates from their site) It seems that doing so totally bricks your Prime with no chance of recovery... (happened at least twice so far)
Click to expand...
Click to collapse
But but but how can I has update?! I want Update! RWAR!
Thanks, thanks, bump, and thanks again! Due to the current state of our device's development (especially with an early build of CWM), misinformation floating around, etc. this is invaluable! Now I know what "staging" is and what its use is. Well done - keep up the great work
Sent from my Transformer Prime TF201 using xda premium
mtotho said:
But but but how can I has update?! I want Update!
Click to expand...
Click to collapse
Use custom ROMs. We currently don't really know if it ALWAYS bricks your Prime. We just know that two updates bricked two primes
I think nobody wants to try
Diamondback said:
Use custom ROMs. We currently don't really know if it ALWAYS bricks your Prime. We just know that two updated bricked two primes
I think nobody wants to try
Click to expand...
Click to collapse
Yea I am just kidding. I knoweth better plus I like custom roms (and I am very flash happy)
I won't be happy until we get some sort of nightly rom that I can flash daily
thanks diamondback this prob saved me lots of time and the almost $700 i have in my device+dock
Sent from my Transformer Prime TF201 using xda premium
Will be possible to use NVFLASH anytime? Have we to look for a dev or is Asus that must upgrade its apk?
Thanks Diamondback for making this. This needs to become a sticky immediately. To many people are blindly unlocking then get mad when they find out they can't do OTA updates. Or people installing CMW without even unlocking and blaming others issues on that when they found out device should've been unlocked first..lmfao
Unlock tool release=operation sabotage for those who don't know any better or ignorant or lazy to research first. QnA section had several people with semi or hard bricked primes. Primes are dying off left n right..lol
Diamondback said:
Unfortunately ASUS didn't fully unlock our Bootloader.
Click to expand...
Click to collapse
So you download their software, run it to completely void your warranty (they've already denied support on one unrelated hardware issues that I know of), and you STILL don't have full access?
WTF!?!?!!?
Not being able to use NVFlash has completely put me off, for me NVFlash was the ultimate aim for unlocking the bootloader ... pretty **** !
(unhappy smiley)
Diamondback, I'm so sorry to hear that you bricked your Prime! Any luck getting unbricked yet?
Thank you so much for posting this invaluable guide. You are generous beyond words, to go to this effort to save other users from the lessons you had to learn the hard way. There aren't enough thanks in the world.
If we can at least ATM use fastboot that's a good thing. A good thing for fastboot is you can first do-
fastboot boot boot.img and it will boot the kernel the first time, basically so you can test it before it writes the .img
then you can fastboot flash boot.img to write the image. It'll work for now, sucks that any non-dev who just wants to flash a kernel has to set up fastboot
Edit- girluvsdroid- just saw you were in wilmington- me too.
This was very helpful.
BUMP!
Reading is fundamental! Lol I don't know how many times I've just glanced over post, just to get the newest firmware, and kernals, just to end up on the verg of a bricked device. Thanks.
What ?
So If I UnlockBootLoader
I cant OTA Anymore ? Seriously
AndyMclamb said:
What ?
So If I UnlockBootLoader
I cant OTA Anymore ? Seriously
Click to expand...
Click to collapse
But why would you unlock if you were not going to install custom roms (that have the latest OTA built in) anyway?
Diamondback said:
Flash your boot.img via fastboot. This is usually rather safe (as safe as fastboot can be) but needs you to have a working fastboot environment.
Click to expand...
Click to collapse
Hmm.. Does not seem to work for me. Built a kernel, switched in fastboot mode. Then:
Code:
$ sudo ./fastboot -i 0x0b05 boot zImage blob.LNX-ramdisk.cpio.gz
creating boot image...
creating boot image - 4214784 bytes
downloading 'boot.img'...
OKAY [ 0.748s]
booting...
FAILED (remote: ()
finished. total time: 0.749s
Prime displays: Failed to process command boot error(0x120000)
Any advice?
saturn_de said:
Hmm.. Does not seem to work for me. Built a kernel, switched in fastboot mode. Then:
Code:
$ sudo ./fastboot -i 0x0b05 boot zImage blob.LNX-ramdisk.cpio.gz
creating boot image...
creating boot image - 4214784 bytes
downloading 'boot.img'...
OKAY [ 0.748s]
booting...
FAILED (remote: ()
finished. total time: 0.749s
Prime displays: Failed to process command boot error(0x120000)
Any advice?
Click to expand...
Click to collapse
Yes. fastboot boot does not work at all.And we also found out that kernel flashing via fastboot does not work either.
You have to flash your kernels via a custom made blob ;-)
Gesendet von meinem Desire HD mit Tapatalk
Prime Stuck in CWM boot loop hell.
I have a Prime that is stuck in a CWM Recovery boot loop.
Brick 1a
All thanks (sincerely) to Viperboy and his ViperMOD PrimeTime 4.5, I had my Prime rooted, boot loader unlocked and loaded with ClockworkMOD Recovery 5.5.0.4.
I used CWM to create a backup, wipe the data/factory, cache partition and Dalvik cache, rebooted the system (from CWM menu) just to verify that the unit was really wiped back to setup, powered down the unit, rebooted into CWM Recovery (using Power while holding Vol.Down, wait for small/white text, Vol.Up) and Restored using the previously created Backup.
I rebooted Android from CWM menu and my Prime was restored.
Everything was great, but not for long.
The next time that I booted into CWM recovery I selected “Reboot System Now”.
It went dark, displayed the ASUS splash screen, went dark and went back into CWM.
I am stuck in that loop.
I have tried all the suggested fixes I can find but all methods are useless because:
1. I can’t acquire an ADB connection because Windows doesn’t identify the bricked Prime correctly and won’t install the USB drivers. Device Manager sees “Full Android as Emulator”.
2. I can’t boot into the boot loader to use Fastboot because I never see the option to choose it. It boots or reboots directly into CWM after “Booting Recovery Kernel Image”, ever while holding the Vol.Down button.
I have repeatedly tried installing and uninstalling the drivers by installing and uninstalling the Asus Sync and Asus Android USB Drivers. I have repeatedly tried to install the drivers via the Device Manager. No good. I’ve installed and uninstalled Android SDK Tools repeatedly.
Is there a way out of this? I hope I'm not efed.
Thank you in advance for any help.
Temporalmind said:
I have a Prime that is stuck in a CWM Recovery boot loop.
Brick 1a
[..]
I apologize for the length of this post. I hope I’m not efed.
Click to expand...
Click to collapse
Please try to manually installing these drivers here
http://forum.xda-developers.com/showthread.php?t=1426502
Adb should be working afterwards
Universal Naked Driver works great!
Ok, you saved me and my precious.
Your drivers were exactly what I needed.
After installing them in Device manager I was able to achieve a “ASUS Android Composite ADB Interface” connection.
Following the “How to Unbrick your Transformer Prime (or not)”, Option 1a and restoring I’m up and running.
Thank you!
Then, I deliberately caused the boot looping condition again to see if I could figure out how I got there.
There is an app that I think comes preinstalled on the Prime called ”Transformer Recovery Boot”. The icon is labeled "Recovery". This is the app that took me into the Brick 1a the first time and I duplicated it the next time I used it.
Then I was able to ADB my way back to civilization, again.
Thought I’d pass that on incase it helps to determine why the unlocked Prime seems to be so susceptible to bricking.
Again, Thank You!
I had screwed around with the system files to try and replace the docking files to get webtop access on my phone without an hd dock. Here...
http://forum.xda-developers.com/showpost.php?p=12250126&postcount=459
Instead of copying the files one by one, I decided to use root explorer and just replace everything. Unfortunately that cause all my apps to force close and now my phone boot loops at the 'M' screen. Fastboot/adb/ all the other stuff still work, just Android doesn't anymore.
I think I need a copy of the system Files for this phone so I can just copy it over somehow. None of the SBF links for fixing bricked phones work and none of the uploaded links for /system files work.... So If anyone has them and can upload them that would be great, also a brief how to would be helpful. Or if there is another way and my thinking is just horribly flawed please let me know.
I have a bell Atrix that was running 2.3.6 that is rooted but I don't think I unlocked the bootloader..
Thanks to anyone who can help.
unlocking a bricked phone
So I've done a bit more reasearch and I think, I got myself a system.img file, from what I understand when the device is unlocked you can just go fastboot flash system system.img, but I think mine isn't, I guess when I rooted it I didn't unlock it as well.
Everytime I enter the comand or try to flash a recovery or system.img I get "Failed to process command flash.system error(0x180002)" (this was when I tried to flash the system.img file) I get a similar error message when I try to flash the recovery.
This message is displayed on my phone.
Is there a way to unlock the bootloader just through fastboot or something? When I try to unlock it with RSD lite it just fails at the reboot part since the phone just boot loops at the motorola logo.
Any help again would be helpful
Thanks
Hey guys, if this is in the wrong section feel free to move it. For whatever reason there still isn't a sub-section for the Pantech Flex...
Anyways, long story short, I had some issues with the stock setup and so I used the built-in Reset option under Settings -> Backup & Reset..
This resulted in a soft-brick of sorts, I can't get past the AT&T logo screen, and since it had just been reset, USB Debugging is NOT enabled.. *sigh*
So, I'm trying to use Fastboot to flash/boot CWM so I can recover from this little predicament (I hadn't successfully flashed CWM yet).. but on 99% of Fastboot commands, I get the following error:
Code:
C:\> fastboot flash recovery cwm.img
sending 'recovery' (8076 KB)...
OKAY [ 0.608s]
writing 'recovery'...
FAILED (remote: Not Support !!)
finished. total time: 0.608s
Which leads me to believe I need to unlock some things.. and upon looking around (the VERY limited information for this device...) I found a few suggestions of using "fastboot oem unlock", however it gives the same "FAILED (remote: Not Support !!)" command..
Anyone know anything that may help? Thanks guys!
You probably should be able to get out of trouble with this thread: http://forum.xda-developers.com/showthread.php?t=2472487
Ur lucky its soft brick!
Mine got super hard bricked.....
There are many ways to solve soft brick....
Just go cwm and flash a right rom for u.....
If u dont have cwm feel free to search in the forum......
Sent from my iPad mini using Tapatalk HD
Thy Boss said:
Ur lucky its soft brick!
Mine got super hard bricked.....
There are many ways to solve soft brick....
Just go cwm and flash a right rom for u.....
If u dont have cwm feel free to search in the forum......
Sent from my iPad mini using Tapatalk HD
Click to expand...
Click to collapse
OP stated that they have not had any luck getting CWM to work.
And to OP - sorry! I just double checked the instructions I linked to, but realized you need adb working for the method if you are already on JB. Please let me know if you are ICS or JB and I'll see if I can't give you better direction...
es0tericcha0s said:
OP stated that they have not had any luck getting CWM to work.
And to OP - sorry! I just double checked the instructions I linked to, but realized you need adb working for the method if you are already on JB. Please let me know if you are ICS or JB and I'll see if I can't give you better direction...
Click to expand...
Click to collapse
Sadly yes, I'm already on JB.. My apologies for the slow reply, didn't get notifications like I thought I had set.
Also, I've gotten it to boot up, but the launcher seems to have been erased and so I get a black screen. Status bar still appears but I can't pull it down to access settings. Navigation buttons respond to input but are still useless without a launcher.
On another note, I've tried flashing a few zips via stock recovery's adb sideload mode, everything from cwm to an entire (stock and otherwise) rom, even just a launcher since that should be all I need, but every time I tried to sideload, it would get to 49% and suddenly "Installation Aborted!" Not sure why that doesn't work... *sigh*
FalloutState said:
Sadly yes, I'm already on JB.. My apologies for the slow reply, didn't get notifications like I thought I had set.
Also, I've gotten it to boot up, but the launcher seems to have been erased and so I get a black screen. Status bar still appears but I can't pull it down to access settings. Navigation buttons respond to input but are still useless without a launcher.
On another note, I've tried flashing a few zips via stock recovery's adb sideload mode, everything from cwm to an entire (stock and otherwise) rom, even just a launcher since that should be all I need, but every time I tried to sideload, it would get to 49% and suddenly "Installation Aborted!" Not sure why that doesn't work... *sigh*
Click to expand...
Click to collapse
Got yourself a tricky one here.
http://forum.xda-developers.com/showpost.php?p=37320624&postcount=88
Use that modded stock recovery to have proper adb access in recovery, and do: adb install launcher.apk (non /system version with that command, and launcher.apk can be named anythingyouwant.apk)
I kind of think that isn't going to be enough though.
If that doesn't work, it might be worth trying to fastboot boot a version of CWM, have the rom you need on the SD card and use that to flash. CWM won't stay, but if you boot and all is well, that can be re-added easily. Let's get the easy option out of the way first though.
es0tericcha0s said:
Got yourself a tricky one here.
http://forum.xda-developers.com/showpost.php?p=37320624&postcount=88
Use that modded stock recovery to have proper adb access in recovery, and do: adb install launcher.apk (non /system version with that command, and launcher.apk can be named anythingyouwant.apk)
I kind of think that isn't going to be enough though.
If that doesn't work, it might be worth trying to fastboot boot a version of CWM, have the rom you need on the SD card and use that to flash. CWM won't stay, but if you boot and all is well, that can be re-added easily. Let's get the easy option out of the way first though.
Click to expand...
Click to collapse
I saw that first link while searching for solutions, however that dropbox link is dead. @timmythanoob, do you still have this file available?
As far as your second idea of using "fastboot boot xxx.img" or whatever have you, the issue with that is that the "boot" command is one of the Fastboot commands I mentioned in the OP that gives the "Remote: Not Support!!" error, which from what I can find is an issue with "aboot" in the JB update...
If I can get ahold of timmythanoob's recovery image with ADB access, then even if adb install'ing a launcher doesn't work, I could still have WAY more options to work with and I'm confident that with full ADB access I could restore the device to working order... IF someone can get me that recovery w/ adb :|
EDIT: Actually I don't think even timmythanoob's recovery image will work since I don't have access to the "fastboot boot" command... I really think my only options are PDL mode and sideloading a zip in recovery. PDL won't work because of the lack of PDL's for our device (and Pantech refusing to give me one), and sideloading a zip in recovery, for whatever reason, always seems to fail with an Installation Aborted... -_-
Anyone have any ideas?
Sorry, a lot of the info for this phone is mixed and matched between instructions for ICS and JB. So, basically, it seems you are boned. Only way to properly get fastboot to work would be to downgrade the aboot, which you can't do because you have to be rooted and booted while on JB to do so. Same thing with CWM on JB. Have to be rooted and booted. :/ Sorry man.
Last resort I can see would be trying to flash the JB OTA zip via stock recovery:
http://forum.xda-developers.com/showpost.php?p=46025559&postcount=164
But even that guy who obviously knows these devices a bit better than we do says it probably wouldn't work for someone in your situation a bit later in that thread:
http://forum.xda-developers.com/showpost.php?p=46209691&postcount=174
But that's pretty much your last option at this stage other than sending it into Pantech so they can use their firmware flashing tool since they won't share it with anyone.
I tried that JB OTA, didn't work. 49% and then Installation Aborted. I was going to send it to Pantech but I imagine they won't help since thanks to my recovery attempts, in the bootloader screen it shows as being rooted and tampered with.
Sucks man. One of the downsides of their being so many different devices out there. Only so many developers to go around and that combined with little to no support from Pantech... :/
I'm going to claim OP resurrection rights and bring this back up in hopes that someone can help. Anyone know anything?
Sent from my YP-G1 using Tapatalk
So my phone works fine but I decided to try my first rooting job on it a few months back and I screwed up somewhere. My intent of rooting was to install a custom rom like Lineage OS. I decided not to flash Lineage OS at the time because I wanted to use the phone rooted right away and I was not patient enough to go through that process so I put it off but I intended to eventually get off stock. Then a new update came out for stock and would continually throw me out of apps and could not install because of the unlocked bootloader (I didn't know about turning off auto-updates in developer options. Must have skipped past it.) so I decided to finally flash Lineage. I got a new computer in the mean time since first root and decided to try and flash Lineage on my phone from it and realized that my TWRP was no longer installed so putting a custom rom had to wait until I reinstalled TWRP. I then tried to re-flash TWRP and realized that only two fastboot commands would NOT freeze up or throw up an error: fastboot devices and fastboot reboot bootloader. So then I realized I am stuck. I cannot, at least as far as I know, flash custom roms OR stock ones without those fastboot commands.
I first thought the issue was my new computer which had only USB 3.0 ports and the original root happened from a USB 2.0 port so I assumed it was an incompatibility with the ports but my old computer threw up the same errors so that wasn't it. I then thought it was an issue with the drivers and that wasn't it either because I must have tried 10 different configurations with the same exact error. So my new thought was to look at the error signs again. Almost all "fastboot flash recovery recovery.img" with TWRP nash img file gave an error similar to max-download-size exceeded. Or just froze. The most common error was "remote: unknown command" but one error was interesting and is why I decided to post here. I don't have it logged because I forgot to paste it out of my clipboard but it went along the lines, "Warning: Device A/B support is outdated. Bootloader update required."
What can I do about this? Buy another phone? Send it to a repair shop? I am exhausted trying all the advice I found online and I am extremely frustrated that I messed up and I don't know how to fix it. This phone was relatively inexpensive but I would love to spend that money elsewhere.
I know there's some other threads about this already but my situation seems to be somewhat unique and the other solutions I've found haven't worked so I'm hoping someone may have other ideas.
When I boot my Pixel 6 which has unlocked bootloader and rooted with Magisk, I'm getting the RED message saying "your device is corrupt. it cant be trusted and may not work properly" and requiring me to push the power button a second time to continue booting. This is different than the YELLOW warning about unlocked bootloader, which comes after this.
This error started when I tried to install the April update the way I usually do, by downloading the factory image, and using flash-all.bat without the -w to avoid wiping. I was using a new computer though and so I downloaded the latest platform-tools (34.0.1) without realizing that version apparently has an issue. The update failed with the error about "FAILED (Sparse file is too large or invalid)" so I downgraded to platform-tools 33.0.3 and updated successfully. Except now that error is happening on boot.
Googling about the error I find that the main solution is factory reset and reinstall using the Pixel Flash Tool online and let it lock the bootloader and everything. I tried this and the error went away! But as soon as I unlocked the bootloader (NO other modification yet whatsoever, just unlocked the bootloader, the error is back.
I can't find anything about this online where it comes back from just unlocking the bootloader after a fresh stock install and everything back to factory.
Any ideas? It is still under warranty so if this seems like a hardware fault, I can probably get it replaced. Google support assured me that the factory reset would help, and when it didn't, they told me to take it to the local UBreakIFix store. I just want to see if I have any other course of action before doing that.
Thanks!
Oh, and the other solution I found which was this adb command: "
adb reboot "dm-verity enforcing" doesn't seem to help either. If I try to run the command I get this error "/system/bin/reboot: too many arguments". This is being run on Windows 11 and I am including the quotes around dm-verity enforcing so I don't see why that should be too many arguments.
ms4sman said:
I know there's some other threads about this already but my situation seems to be somewhat unique and the other solutions I've found haven't worked so I'm hoping someone may have other ideas.
When I boot my Pixel 6 which has unlocked bootloader and rooted with Magisk, I'm getting the RED message saying "your device is corrupt. it cant be trusted and may not work properly" and requiring me to push the power button a second time to continue booting. This is different than the YELLOW warning about unlocked bootloader, which comes after this.
This error started when I tried to install the April update the way I usually do, by downloading the factory image, and using flash-all.bat without the -w to avoid wiping. I was using a new computer though and so I downloaded the latest platform-tools (34.0.1) without realizing that version apparently has an issue. The update failed with the error about "FAILED (Sparse file is too large or invalid)" so I downgraded to platform-tools 33.0.3 and updated successfully. Except now that error is happening on boot.
Googling about the error I find that the main solution is factory reset and reinstall using the Pixel Flash Tool online and let it lock the bootloader and everything. I tried this and the error went away! But as soon as I unlocked the bootloader (NO other modification yet whatsoever, just unlocked the bootloader, the error is back.
I can't find anything about this online where it comes back from just unlocking the bootloader after a fresh stock install and everything back to factory.
Any ideas? It is still under warranty so if this seems like a hardware fault, I can probably get it replaced. Google support assured me that the factory reset would help, and when it didn't, they told me to take it to the local UBreakIFix store. I just want to see if I have any other course of action before doing that.
Thanks!
Click to expand...
Click to collapse
Two things you can try to get rid of the message:
1. Flash the previous month's boot image (your device likely won't boot but that's ok), then flash the boot image of your current month's build.
or
2. Flash the factory image of the previous month and then flash the current factory image.
The message is quite innocuous. You can also safely ignore it and wait until May's security patch is released, install that and the message should go away.
In a nutshell, the bootloader is looking for a new/updated OS without corruption errors so it will go back to restart mode rather than being stuck in the RED eio mode which displays that message.
Verifying Boot | Android Open Source Project
source.android.com
Boot Flow | Android Open Source Project
source.android.com
Lughnasadh said:
Two things you can try to get rid of the message:
1. Flash the previous month's boot image (your device likely won't boot but that's ok), then flash the boot image of your current month's build.
or
2. Flash the factory image of the previous month and then flash the current factory image.
The message is quite innocuous. You can also safely ignore it and wait until May's security patch is released, install that and the message should go away.
In a nutshell, the bootloader is looking for a new OS without corruption errors so it will go back to restart mode rather than being stuck in the RED eio mode which displays that message.
Verifying Boot | Android Open Source Project
source.android.com
Boot Flow | Android Open Source Project
source.android.com
Click to expand...
Click to collapse
Thanks for the suggestions! I'll give it a try.
I'm curious though, is there a known issue with the April update or something?
Otherwise, since I completely factory reset it and installed the latest image using the Pixel Flash Tool and let it lock the bootloader and everything, wouldn't that have replaced any corrupt images? Why does JUST unlocking the bootloader trigger that warning now when it didn't used to?
Thanks!
ms4sman said:
Thanks for the suggestions! I'll give it a try.
I'm curious though, is there a known issue with the April update or something?
Otherwise, since I completely factory reset it and installed the latest image using the Pixel Flash Tool and let it lock the bootloader and everything, wouldn't that have replaced any corrupt images? Why does JUST unlocking the bootloader trigger that warning now when it didn't used to?
Thanks!
Click to expand...
Click to collapse
Not sure why just unlocking the bootloader caused that message (I haven't seen that before), but there really wasn't a need to re-lock your bootloader in the first place as far as I'm aware of.
The error was likely originally caused by using Platform Tools 34 and encountering the error you did. I've seen plenty of people update to April without a problem.
Lughnasadh said:
Not sure why just unlocking the bootloader caused that message (I haven't seen that before), but there really wasn't a need to re-lock your bootloader in the first place as far as I'm aware of.
The error was likely originally caused by using Platform Tools 34 and encountering the error you did. I've seen plenty of people update to April without a problem.
Click to expand...
Click to collapse
Yeah it's very strange indeed. I just did some more testing. Just to confirm things, I just used the Pixel Flash Tool and flashed the latest stock image for the phone onto both slots just to be safe, then locked the bootloader. At this point, the phone should be EXACTLY as it was from the factory, right?
But as soon as I unlocked the bootloader and rebooted, it goes right back to the corrupt message. I locked it again, and bang, error gone. Unlocked, error back.
JUST unlocking the bootloader shouldn't cause any issue or trigger this error right?
ms4sman said:
Yeah it's very strange indeed. I just did some more testing. Just to confirm things, I just used the Pixel Flash Tool and flashed the latest stock image for the phone onto both slots just to be safe, then locked the bootloader. At this point, the phone should be EXACTLY as it was from the factory, right?
But as soon as I unlocked the bootloader and rebooted, it goes right back to the corrupt message. I locked it again, and bang, error gone. Unlocked, error back.
JUST unlocking the bootloader shouldn't cause any issue or trigger this error right?
Click to expand...
Click to collapse
As I stated earlier, the bootloader is looking for a new/updated OS without corruption errors. So try doing one or both of the two things I suggested earlier. Sounds like you are just flashing the same factory image which isn't actually updating to a new/updated OS.
All this locking and unlocking is causing factory resets.
Why bother?
Easiest way to make the red corruption message go away is to extract the vbmeta image from the factory image zip and do this -
Code:
fastboot --disable verity flash vbmeta vbmeta.img
Voila! Red warning gone and no factory reset.
Next month continue flashing as you usually do.
No need to disable verity next time because the corruption message is gone and an updated OS will be installed.