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.
Related
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!
So I just received the phone today and as I always like to do with my new phones I downloaded the latest full ota, installed it through local upgrade and when I pressed reboot the phone rebooted normally.
I went an pressed reboot to recovery and boom the phone just died, no recovery it goes to QUALCOMM crash dump and I am able to boot into bootloader but OEM unlock is still off in the developers options, cant unlock boot loader, cant flash anything in fastboot and there are no MSM tools.
Anyone have any ideas??
Be careful I was on stock rom flashed with stock latest rom with locked bootloader and no funny business and the phone just dead.
I would contact oneplus. I had this once happen to me on my oneplus 3t and they were able to fix it using remote access and walking me through a few steps.
Will check that now
Once in fastboot. Try and run the commands for unlocking the bootloader. That's what worked for me.
speakeasy2 said:
Once in fastboot. Try and run the commands for unlocking the bootloader. That's what worked for me.
Click to expand...
Click to collapse
Won't work, I think its due to the OEM unlock toggle in the Developers options. (Was your toggled on?)
awsan said:
Won't work, I think its due to the OEM unlock toggle in the Developers options. (Was your toggled on?)
Click to expand...
Click to collapse
Yes, did you try and adb the stock.img if you can get into fast boot you should have a chance.
speakeasy2 said:
Yes, did you try and adb the stock.img if you can get into fast boot you should have a chance.
Click to expand...
Click to collapse
Tried that, tried flashing and booting from a boot.img and both returned with failed locked
What model do you have? I don't see why your OEM unlock option would be greyed out...
i just did the same thing, cant get past "device is corrupt and will not boot" i can get into fastboot but no commands work and it will not boot into recovery at all. unlocking the bootloader comes back "flashing unlock not allowed"
any fixes?
i just did the same thing, cant get past "device is corrupt and will not boot" i can get into fastboot but no commands work and it will not boot into recovery at all. unlocking the bootloader comes back "flashing unlock not allowed"
any fixes?
Wrssmithjr04 said:
I would contact oneplus. I had this once happen to me on my oneplus 3t and they were able to fix it using remote access and walking me through a few steps.
Click to expand...
Click to collapse
Thanks it worked, they contacted me and started a remote session and fixed the phone
craznazn said:
What model do you have? I don't see why your OEM unlock option would be greyed out...
Click to expand...
Click to collapse
It was not greyed out I just didnt press it before the phone was corrupted
jammin6996 said:
i just did the same thing, cant get past "device is corrupt and will not boot" i can get into fastboot but no commands work and it will not boot into recovery at all. unlocking the bootloader comes back "flashing unlock not allowed"
any fixes?
Click to expand...
Click to collapse
Chat with oneplus and request a remote session repair they will send you the files and one person will get remote access to fix your phone, Worked for me
awsan said:
Thanks it worked, they contacted me and started a remote session and fixed the phone
It was not greyed out I just didnt press it before the phone was corrupted
Chat with oneplus and request a remote session repair they will send you the files and one person will get remote access to fix your phone, Worked for me
Click to expand...
Click to collapse
thank you for the reply, i have been waiting on that remote session for 16 hours, hopefully they will contact me soon, i keep getting a run around from there live chat.
jammin6996 said:
thank you for the reply, i have been waiting on that remote session for 16 hours, hopefully they will contact me soon, i keep getting a run around from there live chat.
Click to expand...
Click to collapse
All you need is to change the active boot slot to that of before it was messed up.
In fastboot type:
fastboot getvar current-slot
This will tell you what (corrupted) slot you're currently booting from (either a or b). Then just change to the other one with the command:
fastboot --set-active=a
or
fastboot --set-active=b
Then reboot with the command:
fastboot reboot
i did something similar (hello, im an idiot) and oneplus just had me send my phone to a licensed repair place and have them send me a brand new one.
3 days later, sure enough, it was just a new phone. coming form op6, i didnt realize the state of rooting since OP8. Since google handles OPs OTA updates, its a lot harder and op8t was only able to root thanks to a generous insider who leaked the code needed to make MSMdownloadTool work.
purpleman2k said:
All you need is to change the active boot slot to that of before it was messed up.
In fastboot type:
fastboot getvar current-slot
This will tell you what (corrupted) slot you're currently booting from (either a or b). Then just change to the other one with the command:
fastboot --set-active=a
or
fastboot --set-active=b
Then reboot with the command:
fastboot reboot
Click to expand...
Click to collapse
I attempted that however OEM Unlock is not turned on in developer settings and fastboot --set-active just returns an error, something like Commands not allowed.
After 16 hours I finally got my remote session, it took almost 2 hours and they attempted to flash the wrong files on to my device, thank god MSM verifies that first. Then after the tech says "I apologize, my bad, I should have checked that first, we will try again in about 24 hours."
That was a bit ridiculous and if a supervisor isn't able to get it fixed soon, I'm just gonna return it and take my business somewhere else.
jammin6996 said:
I attempted that however OEM Unlock is not turned on in developer settings and fastboot --set-active just returns an error, something like Commands not allowed.
After 16 hours I finally got my remote session, it took almost 2 hours and they attempted to flash the wrong files on to my device, thank god MSM verifies that first. Then after the tech says "I apologize, my bad, I should have checked that first, we will try again in about 24 hours."
That was a bit ridiculous and if a supervisor isn't able to get it fixed soon, I'm just gonna return it and take my business somewhere else.
Click to expand...
Click to collapse
Please return the device, there are way too people messing up their device and can't fix it. You are seriously going to blame the manufacturer for something you messed up?
schmeggy929 said:
Please return the device, there are way too people messing up their device and can't fix it. You are seriously going to blame the manufacturer for something you messed up?
Click to expand...
Click to collapse
No I'm not blaming then for that. I'm blaming then for there lack of communication and the fact that they have me a run around for 16 hours and being transferred between 2 remote technicians, because "we apologize but Agnes is new here and wasn't sure what she was doing" just for the 2nd technician, Olivia, to attempt to flash the wrong files, and then says "we will try again this time tomorrow" that shows me how incompetent they are. They ask for a list of information before hand so that they make sure they have the right device and files.
And to further my reason for return, when I placed my pre-order it was listed as Dual-SIM, just to receive a single sim version. And the phone gets much hotter then most, and the battery life is no where near what it should be. With all that they want nearly the same price as all other flagship devices..
Finally got OnePlus to fix my phone using the MSM tool, and was able to keep an unprotected copy of it. what is the best place to upload and host a 3.5gb file so i can share it here?
Install TWRP through Odin and format data,, then flash factory stock ROM with Odin. Done!!!
Faizanbutt907 said:
Install TWRP through Odin and format data,, then flash factory stock ROM with Odin. Done!!!
Click to expand...
Click to collapse
odin is for samsung. you are on OP9 Pro section.
So my phone is stuck on this issue. I haven't done anything wrong. My phone was just peacefully charging then the phone switches off by itself then the bootloop happened.
This showed on the screen:
dm-verity corruption
your device is corrupt.
it can't be trusted and my not work properly.
press enter button to continue.
Or, device will power off in 5s.
(written in white)
Although it does turn off by itself if I ignore it, after I turn it on again and press enter or power button it boot until lockscreen and if I try to do something like unlocking, scrolling down notifs bar, and sliding through different page on home screen it will turn off again. It seem like it's crashing. The thing is I am not trying to root or flash something. I haven't done anything on my phone. I only have one phone and I badly need your help. I hope wiping or reformatting the phone is my last resort. My phone is updated to Android 11 and lateset MIUI (provided by the system itself and not downloaded somewhere). Thank you.
Well seems like something is corrupt.
It reboots when you touches the screen(or do anything)?
LR7875 said:
It reboots when you touches the screen(or do anything)?
Click to expand...
Click to collapse
It's more like it turns itself off again and if I try to press again power button if the problem show again, same thing happen. Sometimes MIUI logo appears and shuts down again it can't even go to lock screen.
Is there any chance you can unlock it?
It seems like your internal storage is corrupted.
LR7875 said:
Is there any chance you can unlock it?
It seems like your internal storage is corrupted.
Click to expand...
Click to collapse
At some point I did manage to unlock it but it happened only once and when I tried to open the notifs by scrolling down or tried to different part of homescreen it just shuts down. After that, it can't even go to the lockscreen after reboot. It's a never ending cycle. I can go to fastboot mode but I don't know if I can do miracle with that.
Well immediately plug into a computer and pull photos amd videos from it if you get it unlocked.
LR7875 said:
Well immediately plug into a computer and pull photos amd videos from it if you get it unlocked.
Click to expand...
Click to collapse
I reformatted it hoping that it will fix the problem. I was wrong. *sigh*
hyung_z said:
I reformatted it hoping that it will fix the problem. I was wrong. *sigh*
Click to expand...
Click to collapse
Well most likely your EMMC internal storage chip went bad R.I.P. (well maybe you sending those emojis will be more appropriate, but, oh well)
Maybe search more on google, I can't help you more
LR7875 said:
Well most likely your EMMC internal storage chip went bad R.I.P. (well maybe you sending those emojis will be more appropriate, but, oh well)
Maybe search more on google, I can't help you more
Click to expand...
Click to collapse
Do you think service center can help me with this or they'll probably just say to replace the phone if a bad chip is the case?
Maybe they will replace the motherboard with some fee. Or they will try to convince you to buy a new fancy phone just purely because xiaomi could earn more.
Thats all about luck (and problem is on xiaomi side, not your fault)
what's the smartphone model?
Redmi note 8 pro is the OP's phone.
Wait Wait just found some interesting lead.
Xiaomi needs a better way to unbrick its devices instead of Authorized Mi Accounts
Xiaomi has locked down the EDL mode on all of its devices, making it nigh impossible to unbrick a device without an Authorized Mi Account. Read on for more!
www.xda-developers.com
Patched SP flash tool!
heh, i have the same phone. reflash yours with the firmware that was on it before everything that happened. but don't flash userdata if you want your data on it
flashing it is simple process
LR7875 said:
Redmi note 8 pro is the OP's phone.
Wait Wait just found some interesting lead.
Xiaomi needs a better way to unbrick its devices instead of Authorized Mi Accounts
Xiaomi has locked down the EDL mode on all of its devices, making it nigh impossible to unbrick a device without an Authorized Mi Account. Read on for more!
www.xda-developers.com
Patched SP flash tool!
Click to expand...
Click to collapse
there is already a way to flash it with SPFT without authorization
also he must try to flash it in fastboot because it's not bricked
AsyJAIZ said:
there is already a way to flash it with SPFT without authorization
also he must try to flash it in fastboot because it's not bricked
Click to expand...
Click to collapse
He probably doesn't have his bootloader unlocked.
Fastboot OEM unlock wont work as oem unlock is probably not enabled in settings dev options.
LR7875 said:
He probably doesn't have his bootloader unlocked.
Fastboot OEM unlock wont work as oem unlock is probably not enabled in settings dev options.
Click to expand...
Click to collapse
ok i got it, then he should somehow put it in download mode...
Do you guys think I need to go to the service center because I don't know what to do. I really don't want to brick my phone. But a while ago my phone booted. I set it up just like buying a new phone but after I finished setting up, I just wait for the phone to catch up because I was afraid the phone will just shut down suddenly. And then, it happened again the phone shut downs without me doing anything. Now I tried to boot it up again but it is currently stuck at Redmi logo (plus "powered by android" at the bottom").
hyung_z said:
Do you guys think I need to go to the service center because I don't know what to do. I really don't want to brick my phone. But a while ago my phone booted. I set it up just like buying a new phone but after I finished setting up, I just wait for the phone to catch up because I was afraid the phone will just shut down suddenly. And then, it happened again the phone shut downs without me doing anything. Now I tried to boot it up again but it is currently stuck at Redmi logo (plus "powered by android" at the bottom").
Click to expand...
Click to collapse
SPFT enables when phone is a brick, so there's no need in service center.
they will flash it like we are going to do
Help, does anyone know how to fix dm-verity corruption? I was using my tab normally, then it suddenly shuts down and this error keeps popping up whenever my device boots. It goes on a loop unless I press the power button again.
deleted
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!
Hello,
In the rush of flashing the january update I've flashed by mistake the Pixel 5 image bootloader (my wife's phone)
Yest that's stupid, I've done this every months for years with several Pixel phones, but I was listening to music at the same time and did dl the wrong image...
Anyway my phone is now hard bricked but I'm sure there must be a way to enter the other bootlader slot and/or entering a special recovery tool.
I cannot enter bootloader anymore
Requesting some help as I'd avoid to send it for a reflash...
Thanks !
Try: https://pixelrepair.withgoogle.com/carrier_selection
(I've never personally used this)
foobar66 said:
Try: https://pixelrepair.withgoogle.com/carrier_selection
(I've never personally used this)
Click to expand...
Click to collapse
Unfortunately the phone is supposed to have a working bootloader
Thibale said:
Unfortunately the phone is supposed to have a working bootloader
Click to expand...
Click to collapse
Ouch ...
Thibale said:
Unfortunately the phone is supposed to have a working bootloader
Click to expand...
Click to collapse
Android Flash Tool
flash.android.com
Also doesn't work?
Morgrain said:
Android Flash Tool
flash.android.com
Also doesn't work?
Click to expand...
Click to collapse
Nope...
Thibale said:
Nope...
Click to expand...
Click to collapse
Can you still access Fastboot Mode?
(pressing and holding both Power and Volume Down simultaneously. You should see a green android on his back)
Morgrain said:
Can you still access Fastboot Mode?
(pressing and holding both Power and Volume Down simultaneously. You should see a green android on his back)
Click to expand...
Click to collapse
No that's the problem.
But there are 2 bootloader slots (a and b) and I'm pretty sure there is way to switch from one to another with a special tool or button sequence.
I've already tried many button combinaison with no luck.
This kind of error is so stupid that I hope there is a way to force a rescue bootloader or something on boot.
yes but you need to be able to communicate with your phone from your pc.....if you cant access fastboot then how will you change partition?
Thibale said:
No that's the problem.
But there are 2 bootloader slots (a and b) and I'm pretty sure there is way to switch from one to another with a special tool or button sequence.
I've already tried many button combinaison with no luck.
This kind of error is so stupid that I hope there is a way to force a rescue bootloader or something on boot.
Click to expand...
Click to collapse
The only special tools we have are either the pixel repair tool or the android flash tool. If both can't get you fastboot / firmware flashing, that's it. Hardbrick. Google Pixels don't have "special" hardbrick solving tools, like older OnePlus had. You need to contact Google.
Ok I'll get in touch with my local reseller on Monday then...
Thibale said:
Ok I'll get in touch with my local reseller on Monday then...
Click to expand...
Click to collapse
Do you remember what went wrong?
EDIT: Uh, never mind. So you accidentally used the P5 fw. Why on hell would the device accept the P5 fw at all?!
Same problem here: downloaded from a blog the latest firmware. They have linked the pixel 5 firmware and named it as Pixel 6 pro full firmware. Just flashed without looking and now the phone wont boot. No reaction at all, no fast boot or whatsoever. Have filled in a repair request in my google account, because I’ve bought it directly in their store.
Do you think they have a way to find out what went wrong? I meant the phone is not giving any signal, regardless of which button combination I press. Worst case: I have to pay for the repair…
Psfanboy88 said:
Same problem here: downloaded from a blog the latest firmware. They have linked the pixel 5 firmware and named it as Pixel 6 pro full firmware. Just flashed without looking and now the phone wont boot. No reaction at all, no fast boot or whatsoever. Have filled in a repair request in my google account, because I’ve bought it directly in their store.
Do you think they have a way to find out what went wrong? I meant the phone is not giving any signal, regardless of which button combination I press. Worst case: I have to pay for the repair…
Click to expand...
Click to collapse
WOW. So even holding volume down and power until you see the fastboot screen wont work? sometimes you have to hold it for a while. I say that because when the December firmware came out I accidentally flashed the wrong region but was able to access bootloader and so was able to rescue myself. So sorry dude. That really sucks.
Psfanboy88 said:
Same problem here: downloaded from a blog the latest firmware. They have linked the pixel 5 firmware and named it as Pixel 6 pro full firmware. Just flashed without looking and now the phone wont boot. No reaction at all, no fast boot or whatsoever. Have filled in a repair request in my google account, because I’ve bought it directly in their store.
Do you think they have a way to find out what went wrong? I meant the phone is not giving any signal, regardless of which button combination I press. Worst case: I have to pay for the repair…
Click to expand...
Click to collapse
Yes worst case we'll have for repair but they could have implemented a simple device id check on their script prior flashing anything, especially for the bootloader.
Anyway, I'm alive, in a good health and it's just a phone
niko26 said:
Do you remember what went wrong?
EDIT: Uh, never mind. So you accidentally used the P5 fw. Why on hell would the device accept the P5 fw at all?!
Click to expand...
Click to collapse
You can flash gobbledygook to your phone if you're not careful. You can flash a non-Google phone's image. Flashing just flashes what you tell it to flash.
Psfanboy88 said:
Same problem here: downloaded from a blog the latest firmware. They have linked the pixel 5 firmware and named it as Pixel 6 pro full firmware. Just flashed without looking and now the phone wont boot. No reaction at all, no fast boot or whatsoever. Have filled in a repair request in my google account, because I’ve bought it directly in their store.
Do you think they have a way to find out what went wrong? I meant the phone is not giving any signal, regardless of which button combination I press. Worst case: I have to pay for the repair…
Click to expand...
Click to collapse
That sucks. I'm sure you know now, always go straight to the source for everything if possible, firmware, platform tools, drivers, BIOS / UEFI (for computer).
SDK Platform Tools
Get the Google USB Driver
Pixel 6 Pro Factory Images
You can also Google for official pixel firmware and the top search result is what the want. I know it doesn't help you now. Good luck with your phone!
Morgrain said:
After having played around with the January patch (came from December Europe A4 firmware that was pulled), it seems that the FP scanner got even faster and more reliable, even though it's not stated in the patchnotes. Maybe it's just placebo.
Click to expand...
Click to collapse
So many folks have reported the exact same thing, I'm really, really curious just how much faster it will seem when I get around to updating.
roirraW edor ehT said:
So many folks have reported the exact same thing, I'm really, really curious just how much faster it will seem when I get around to updating.
Click to expand...
Click to collapse
I noticed how faster it was before I saw everyone else posting about it, so at least no placebo on my end. Hope you find the same.
I know that you tried to get into Fastboot. Pixel 6/6P also has a Recovery mode. I can get to it from a working phone.
I would think that there is someway to boot into Recovery mode from a dead phone via button combos.
Thibale said:
Hello,
In the rush of flashing the january update I've flashed by mistake the Pixel 5 image bootloader (my wife's phone)
Yest that's stupid, I've done this every months for years with several Pixel phones, but I was listening to music at the same time and did dl the wrong image...
Anyway my phone is now hard bricked but I'm sure there must be a way to enter the other bootlader slot and/or entering a special recovery tool.
I cannot enter bootloader anymore
Requesting some help as I'd avoid to send it for a reflash...
Thanks !
Click to expand...
Click to collapse
Hy, how did you flashed? Via adb sideload or?
vrda08 said:
Hy, how did you flashed? Via adb sideload or?
Click to expand...
Click to collapse
factory image with modified flash-all.bat
I'll do the exact same process when I'll get my phone back but this time I'll check the image name at least 3 times