Related
I rooted and put on a screen lock pattern and want to go back to normal screen. I can't get back into the options. I might do another Titanium BU and try to do a factory reset or preferable a return to stock to get the value package then reroot. Suggestions as to get it back normal are gladly accepted.
PS...googled this subject but nip real help.
Sent from my LG-E980 using xda premium
Why can't you get back into options? What happens when you click "Select screen lock"? Can't select swipe?
Kriggs said:
Why can't you get back into options? What happens when you click "Select screen lock"? Can't select swipe?
Click to expand...
Click to collapse
Nope. Goes to the pattern screen and wants me to do a new pattern. Been flashing (Samsung Infuse 4G) for two years but I can't figure the LG out. I have everything ready to use LGFlash and go back to the April tot. Then I am thinking of flashing the value package and then re-rooting. Not sure that is the correct procedure and was looking for a little guidance here.
psal217050 said:
Nope. Goes to the pattern screen and wants me to do a new pattern. Been flashing (Samsung Infuse 4G) for two years but I can't figure the LG out. I have everything ready to use LGFlash and go back to the April tot. Then I am thinking of flashing the value package and then re-rooting. Not sure that is the correct procedure and was looking for a little guidance here.
Click to expand...
Click to collapse
I would probably just do a factory reset from settings first.
MrDSL said:
I would probably just do a factory reset from settings first.
Click to expand...
Click to collapse
I will try. I do want to use the LG Flash Tool but not sure what is wrong with it and me... Every time I load it, it starts up Republic of Korea, asks for id and password, I use wbr and tejaram and it doesn't work. Not sure if I did something wrong there.
Tried factory reset, it went to TWRP, so I just rebooted at that point. Wasn't sure what to do and I don't want to brick the phone.
If you replaced the factory recovery then just wipe user data in twrp and reboot.
Wiping user data shouldn't brick your device.
MrDSL said:
If you replaced the factory recovery then just wipe user data in twrp and reboot.
Wiping user data shouldn't brick your device.
Click to expand...
Click to collapse
Okay that worked. Thanks. Now I have to figure out the LG Flash Tool and why it won't work.
I keep getting the enter id and password screen and can't get past that.
Finally figured it out. Had to replace csmg_reg_key.dll with the megalock.dll
Went to stock, then flashed the value package. Said it was at 100% but said download failed. Not sure what happened but the phone boots and it says Software version is E98010k. Do I need to reflash?
Anyone know if I can recover from this? TWRP is gone and I cannot reinstall it. Tried fastboot but got this:
(bootloader) permission denied!
FAILED (remote failure)
finished. total time: 0.234s
I've been searching for answers for a while and have tried several different things, but nothing worked so I'm giving up for today. Hopefully someone can offer some advice. For now, its back to my Nexus 6.....too bad cause I was enjoying this phone......
...... :crying:
That almost sounds like your bootloader is locked again. If so, you can try unlocking again from fastboot with the fastboot oem get_unlock_data command the Motorola site
I ran into this. Do a flash all. It will work. Then boot to system and allow unlocking then reuse the code Moto gave you in bootloader. This is a known issue when you slot swap to a slot that has nougat after going to Oreo.
artlan said:
That almost sounds like your bootloader is locked again. If so, you can try unlocking again from fastboot with the fastboot oem get_unlock_data command the Motorola site
Click to expand...
Click to collapse
Thanks! But how the heck did the bootloader lock itself? That did help with the fastboot error messages, but I tried flashing twrp which seemed to work but I still cant enter twrp. It keeps bootlooping to white TMO screen for about a minute then its gets stuck at this message:
Failed to boot linux, falling back to fastboot
Fastboot Reason: Fall-through from normal boot mode
Do you know how to flash the factory image? I downloaded the image found in this forum but it is a .xml.zip file which had some .img and a bunch of other files inside. I really dont want to brick this thing, so I am afraid to experiment flashing random files. I really want to make sure I am doing the right thing!
..
Uzephi said:
I ran into this. Do a flash all. It will work. Then boot to system and allow unlocking then reuse the code Moto gave you in bootloader. This is a known issue when you slot swap to a slot that has nougat after going to Oreo.
Click to expand...
Click to collapse
Argh....these dual slots are ridiculous.
I am not familiar with the flash-all command. Can you elaborate? I searched a bit, but again I REALLY want to make sure I know what I am doing first. I just bought this phone a month ago and would hate to lose it.
Thx!
ianmck said:
Argh....these dual slots are ridiculous.
I am not familiar with the flash-all command. Can you elaborate? I searched a bit, but again I REALLY want to make sure I know what I am doing first. I just bought this phone a month ago and would hate to lose it.
Thx!
Click to expand...
Click to collapse
What carrier do you have?
Uzephi said:
What carrier do you have?
Click to expand...
Click to collapse
TMO. I was rooted on Oreo for a few weeks until TWRP crapped out on me during a flash and caused this mess. I suddenly kept getting TWRP errors about /system and /cache not found. I never decrypted my phone if that matters.
Is this flash-all just batch flashing multiple files to make it easy? I'll gladly do it the hard way if need be. I just want to make sure I flash the right files. I have downloaded the following zip:
XT1789-04_NASH_TMO_C_8.0.0_OCX27.109-36_subsidy-TMO_regulatory-DEFAULT_CFC
ianmck said:
TMO. I was rooted on Oreo for a few weeks until TWRP crapped out on me during a flash and caused this mess. I suddenly kept getting TWRP errors about /system and /cache not found. I never decrypted my phone if that matters.
Is this flash-all just batch flashing multiple files to make it easy? I'll gladly do it the hard way if need be. I just want to make sure I flash the right files. I have downloaded the following zip:
XT1789-04_NASH_TMO_C_8.0.0_OCX27.109-36_subsidy-TMO_regulatory-DEFAULT_CFC
Click to expand...
Click to collapse
That would be fine to flash. There is also a 27.1 zip joemossjr made that's floating around
Uzephi said:
That would be fine to flash. There is also a 27.1 zip joemossjr made that's floating around
Click to expand...
Click to collapse
Well, that seemed to work but no wifi/baseband. Any idea where this 27.1 version is? I thought I found it at one point, but the zipped files did not look correct to me.
ianmck said:
Well, that seemed to work but no wifi/baseband. Any idea where this 27.1 version is? I thought I found it at one point, but the zipped files did not look correct to me.
Click to expand...
Click to collapse
There's a zip in the "here" link in this post that will allow you to flash 27.1 but it will not pass safetynet (which you'll see me discuss toward the end of that thread):
https://forum.xda-developers.com/showpost.php?p=75810018&postcount=21
Uzephi said:
I ran into this. Do a flash all. It will work. Then boot to system and allow unlocking then reuse the code Moto gave you in bootloader. This is a known issue when you slot swap to a slot that has nougat after going to Oreo.
Click to expand...
Click to collapse
How did you get to flash it? I'm stuck on that! Tried many solutions on here and I can´t get to flash it
what do i do if my phone says its in fastboot but the computer doesnt see it? ive tried different cords, downloaded the usb drivers everything nothing works help please????!!!!!
thegreeknicholas said:
what do i do if my phone says its in fastboot but the computer doesnt see it? ive tried different cords, downloaded the usb drivers everything nothing works help please????!!!!!
Click to expand...
Click to collapse
try restarting the phone back to fastboot
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 flashed my RM5 with the CN ROM shortly after receiving the phone due to the software limitations of the NA ROM shipped on the device. With the CN ROM I successfully used face unlock. Now after flashing to the newly released global (v3.11) I get an error when trying to register my fingerprint (attached).
Steps taken:
1. Re-flashed CN ROM and attempted to register fingerprint and got the same error
2. Re-installed the new global v3.11
3. Flashed global recovery, boot, splash, parameter, then wiped data & cache. Factory reset. Still get the same error
Interesting to note that upon setup the phone said the fingerprint sensor was on the back.
JerryYin said:
You should find the person who gives you the phone. The fingerprint calibration data will lost only when you try to unlock the bootloader
Click to expand...
Click to collapse
Looks like the community is solving the problems again: https://forum.xda-developers.com/nu.../guide-calibration-finger-print-loss-t4132961
terrapin4 said:
I flashed my RM5 with the CN ROM shortly after receiving the phone due to the software limitations of the NA ROM shipped on the device. With the CN ROM I successfully used face unlock. Now after flashing to the newly released global (v3.11) I get an error when trying to register my fingerprint (attached).
Steps taken:
1. Re-flashed CN ROM and attempted to register fingerprint and got the same error
2. Re-installed the new global v3.11
3. Flashed global recovery, boot, splash, parameter, then wiped data & cache. Factory reset. Still get the same error
Interesting to note that upon setup the phone said the fingerprint sensor was on the back.
Click to expand...
Click to collapse
You need to lock the bootloader to make it work, this will wipe your phone however. It says the fingerprint is on the back because the devs didn't bother fixing the typo in the setup.
rat7lol said:
You need to lock the bootloader to make it work, this will wipe your phone however. It says the fingerprint is on the back because the devs didn't bother fixing the typo in the setup.
Click to expand...
Click to collapse
Same thing after BL unlock/wipe. Same thing after BL relock/wipe
Are you sure you're using the correct command? There's "fastboot oem nubia_lock NUBIA_NX659J" and "fastboot flashing lock".
"fastboot flashing unlock" breaks the fingerprint
rat7lol said:
Are you sure you're using the correct command? There's "fastboot oem nubia_lock NUBIA_NX659J" and "fastboot flashing lock".
"fastboot flashing unlock" breaks the fingerprint
Click to expand...
Click to collapse
Yup I'm using "fast boot flashing (un)lock". I've unlocked and relocked now.
Sent from my NX659J using Tapatalk
terrapin4 said:
Yup I'm using "fast boot flashing (un)lock". I've unlocked and relocked now.
Sent from my NX659J using Tapatalk
Click to expand...
Click to collapse
Have you tried "fastboot flashing relock"
relock not lock
zayidhs said:
Have you tried "fastboot flashing relock"
relock not lock
Click to expand...
Click to collapse
Yes, it only accepts "fastboot flashing lock".
In any event, no matter if I unlock/relock the bootloader on the CN Rom or switch to the global ROM and do the same the fingerprint error persists. I even installed TWRP again and formatted data and did everything all over again.
Looks like I'm stuck with either face unlock only on CN or no fingerprint on global.
Really appreciate all the help though!
terrapin4 said:
Yes, it only accepts "fastboot flashing lock".
In any event, no matter if I unlock/relock the bootloader on the CN Rom or switch to the global ROM and do the same the fingerprint error persists. I even installed TWRP again and formatted data and did everything all over again.
Looks like I'm stuck with either face unlock only on CN or no fingerprint on global.
Really appreciate all the help though!
Click to expand...
Click to collapse
We need @JerryYin to supply an unbrick tool. Sounds like a partition has been wiped permanently. Only an unbrick tool will reflash all proper partitions.
VZTech said:
We need @JerryYin to supply an unbrick tool. Sounds like a partition has been wiped permanently. Only an unbrick tool will reflash all proper partitions.
Click to expand...
Click to collapse
No, the unbrick tool won't help. you need re-calibration the fingerprint sensor.
JerryYin said:
No, the unbrick tool won't help. you need re-calibration the fingerprint sensor.
Click to expand...
Click to collapse
Do you have any suggestions on how to fix this?
terrapin4 said:
Do you have any suggestions on how to fix this?
Click to expand...
Click to collapse
Like Jerry said, the fingerprint sensor needs to be re-calibrated.
In the factory
With nubia
Sorry
terrapin4 said:
Do you have any suggestions on how to fix this?
Click to expand...
Click to collapse
For now you have to send the phone back to service center to perform the fingerprint recalibration.
I thought it's software issue not hardware issue , yesterday I checked my friend rooted phone it was work excellent but when I updated it and rooted again it want work again
@JerryYin
Currently I'm getting the "Loss of fingerprint calibration data" message when I try to add a fingerprint. This advises me to contact Nubia's after-sales service via the number "4007006600". This device is provided to me directly by Nubia engineers.
I've just tried to run the calibration and have gotten two errors - one being that the number of bad pixels is abnormal (even though the results are below the threshold), and the other being an "Unknown Error" message
Screenshots of results here: https://photos.app.goo.gl/NpfpDUDgSkMmAc187
gamebenchjake said:
@JerryYin
Currently I'm getting the "Loss of fingerprint calibration data" message when I try to add a fingerprint. This advises me to contact Nubia's after-sales service via the number "4007006600". This device is provided to me directly by Nubia engineers.
I've just tried to run the calibration and have gotten two errors - one being that the number of bad pixels is abnormal (even though the results are below the threshold), and the other being an "Unknown Error" message
Screenshots of results here: https://photos.app.goo.gl/NpfpDUDgSkMmAc187
Click to expand...
Click to collapse
You need to relock tge bootloader. Or send back to customer for re calibration
JerryYin said:
You need to relock tge bootloader. Or send back to customer for re calibration
Click to expand...
Click to collapse
Hi @JerryYin, The bootloader is locked (never unlocked). The device was sent directly by Nubia Engineering, so I can't send it back (no purchase receipt etc).
The issue seems to be that the device never passes the "CALBRATE_CHECKBOX" test, though everything else passes. If you could provide some insight into what this test is checking, I can finish calibrating it myself
gamebenchjake said:
Hi @JerryYin, The bootloader is locked (never unlocked). The device was sent directly by Nubia Engineering, so I can't send it back (no purchase receipt etc).
The issue seems to be that the device never passes the "CALBRATE_CHECKBOX" test, though everything else passes. If you could provide some insight into what this test is checking, I can finish calibrating it myself
Click to expand...
Click to collapse
You should find the person who gives you the phone. The fingerprint calibration data will lost only when you try to unlock the bootloader
Can someone help me, I need better clarification on some things.
So the first set of steps involve:
1) 'call' *#9959* and turn off the 'performance'
2) click 'start' and leave to phone/screen alone aka no touching it whats so ever, then I get the following text in image 1.
Now the steps after that have me confused on some things:
Step 2
3) Click 'Next' and the screen will dim abit
Do I have to leave the screen alone or do I have to put my finger immediately after hitting 'next'?
Cause I saw posts about leaving it alone and others saying to put my finger(thumb).
If I put my finger on the screen it gives me an error '0x3A self-exposure abnormal' (as in image 2);
but if I leave it alone it'll give me 'Auto_Exposure' & 'Flesh' tests succeeded (image 3)
I NEED clarification here, am I doing this part wrong by not having my finger on the Fp scanner.
Now for step 3, I have to:
4) click on 'Next' and the phone will do the 'Dark' and 'Dark-Base' tests. The should be left alone here as well. (Image 4)
I need to be in a dark room for this, correct?
Now for the final step
6) Click 'Next' and put my finger back to the screen on the blue FP scanner(?)
When I do this; I end up with '0x14 the number of bad pixels....' (image 5)
Any help is very up appreciated.
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.