I broke face unlock on my Pixel 4 XL.. it says enrollment error. Certificate expired
Now How I did it??
Well, i was doing some experiment on my Pixel 3 XL i copied cdt.img from it, modified it and mistakenly flash it to my Pixel 4 XL because both were connected to adb at the same time. Then it went full black no signs of life. But when I did fastboot devices it showed up. So I downloaded twrp booted into it still no display on screen but I could see it as an adb device i took cdt.img backup from my friends pixel 4 xl and restored it and my phone boot up but face unlock is not working... Front camera is fine...and so do the IR camera I saw them through an app
Recovery methods currently tried... I totally removed cdt.img from my phone from
/Dev/block/bootdevice/by-name
/dev/block/by-name/
Not working I removed face unlock and Pin totally then tried to activate same response
Haven't tried factory flash yet
Related
- Android P
- Magisk 16.7
- Pixel 2 XL
- whenever avb/dm-verity is preserved or not (all tried / will be patched automatically whether checked or not)
I don't know it's limited to Pixel Series or not,
but I think dtbo.img may be related to this when I found the PIN became uncorrected suddenly after reboot and I tried to flash factory dtbo.img again and it becomes normal.
And it becomes every time when I restart the phone (the reason is dtbo will be patched automatically).
And I found,
if there's no PIN or password set before flashing Magisk,
PIN and password can't be set forever after the Magisk was flashed.
When PIN or password or pattern is set, the system will still shows that the screen lock is none.
Do any one met the same problem ?
IIRC that's mainly a Pixel 2 XL specific issue that should be fixed in code but not officially released yet. You could try the unofficial snapshots by @kantjer or @ianmacd
https://github.com/kantjer/MagiskFiles
https://github.com/ianmacd/MagiskBuilds
Didgeridoohan said:
IIRC that's mainly a Pixel 2 XL specific issue that should be fixed in code but not officially released yet. You could try the unofficial snapshots by @kantjer or @ianmacd
Click to expand...
Click to collapse
Many Thanks!
I've installed https://github.com/ianmacd/MagiskBuilds <- this one and it works!
Why dont you just boot in TWRP and delete the locksettings.db in data/system/
Then you have no more Pin and can reboot normally
So my redmi note 3 stopped charging and the charge was finished.
During this lockdown, I found a shop that was open so I decided to give it there. The guy told that the charging board got short and needed it to be replaced. He replaced it and charged me 10USD.
But he said that, while replacing the board the software was gone and phone was stuck in a bootloop. I said I can fix that myself and I brought it home.
I tried installing the latest available stock ROM MIUI 10.2.1 global ,also tried MIUI 9.6.
But I encountered the same problem everywhere.
Back camera doesn't work, says can't connect to camera.
SIM card does not get detected.
Loudspeaker doesn't work.
WiFi works but you need to wait a while after rebooting the phone.
Brightness sensor doesn't work.
So I decided to give the phone back to the shop, he told me today that there is an error and he needs 15$ to repair it but it can't be done currently in this lockdown.
What might have happened to the device? I don't trust the shop person.
I’ve had some of the issues before. Brightness sensor and all other sensors didn't work, camera didn't work, WiFi didn't work. But for me the loudspeaker and SIM card worked.
All I had to do is flash the persist.img file.
- You should have an unlocked bootloader.
- The persist.img file should be located in the images folder of the zip file of the fastboot ROM.
- Copy it to the desktop.
- Run fastboot flash persist persist.img command in your PC while your phone is in fastboot mode and check if everything gets fixed.
Samip12 said:
So my redmi note 3 stopped charging and the charge was finished.
During this lockdown, I found a shop that was open so I decided to give it there. The guy told that the charging board got short and needed it to be replaced. He replaced it and charged me 10USD.
But he said that, while replacing the board the software was gone and phone was stuck in a bootloop. I said I can fix that myself and I brought it home.
I tried installing the latest available stock ROM MIUI 10.2.1 global ,also tried MIUI 9.6.
But I encountered the same problem everywhere.
Back camera doesn't work, says can't connect to camera.
SIM card does not get detected.
Loudspeaker doesn't work.
WiFi works but you need to wait a while after rebooting the phone.
Brightness sensor doesn't work.
So I decided to give the phone back to the shop, he told me today that there is an error and he needs 15$ to repair it but it can't be done currently in this lockdown.
What might have happened to the device? I don't trust the shop person.
Click to expand...
Click to collapse
Ur charging board will burn diode if u use 9v or 12v QC charger. Only 5v is safe for kenzo.
U dont need to throw that board. Just use tiny flat screw driver and scratch and remove the burnt diode from the board. Phone wil start charging again.
Local repair shops give cheap quality charging board. I bought 2 boards from ebay and aliexpress. One is HMFS and CTFS. both works fine with network.
Ya_SG said:
I’ve had some of the issues before. Brightness sensor and all other sensors didn't work, camera didn't work, WiFi didn't work. But for me the loudspeaker and SIM card worked.
All I had to do is flash the persist.img file.
- You should have an unlocked bootloader.
- The persist.img file should be located in the images folder of the zip file of the fastboot ROM.
- Copy it to the desktop.
- Run fastboot flash persist persist.img command in your PC while your phone is in fastboot mode and check if everything gets fixed.
Click to expand...
Click to collapse
I'll collect the phone and try this.
Ya_SG said:
I’ve had some of the issues before. Brightness sensor and all other sensors didn't work, camera didn't work, WiFi didn't work. But for me the loudspeaker and SIM card worked.
All I had to do is flash the persist.img file.
- You should have an unlocked bootloader.
- The persist.img file should be located in the images folder of the zip file of the fastboot ROM.
- Copy it to the desktop.
- Run fastboot flash persist persist.img command in your PC while your phone is in fastboot mode and check if everything gets fixed.
Click to expand...
Click to collapse
Just collected my phone, dude told that my IMEI is erased and that is the reason why my phone is behaving like this ,
should I first flash persist.img or try something else?
The persist.img did not solve anything.
I'm trying to restore IMEI using different methods but I'm getting some problem.
What would be the best method to restore IMEI?
I have already unlocked bootloader and rooted my device.
Samip12 said:
What would be the best method to restore IMEI?
I have already unlocked bootloader and rooted my device.
Click to expand...
Click to collapse
I'm pretty sure that I used this or a similar approach to restoring note 3 IMEIs in the past.
https://************/fix-lost-imei-xiaomi-redmi-note-3/
Edit: I guess that that URL is banned or something so you'll have to Google it.
dalyer said:
I'm pretty sure that I used this or a similar approach to restoring note 3 IMEIs in the past.
https://************/fix-lost-imei-xiaomi-redmi-note-3/
Edit: I guess that that URL is banned or something so you'll have to Google it.
Click to expand...
Click to collapse
I tried a method in which i had to flash modem file using fastboot,
after that my device doesn't go past MI logo.
It goes to MI logo then turns off.
I tried installing stock ROM through edl mode, fastboot mode, recovery mode but same result, device doesn't go past MI logo
I got two brand new Pixel 4a (5G) for my girlfriend and me. Mine worked perfect, hers was freezing and rebooting all the time. To solve this, I wanted to reflash the factory image.
I messed up the two devices and didn't notice, that the bootloader on hers wasn't unlocked yet. So I ran flash-all.sh on locked bootloader. Now the Pixel says "Can't find valid operating system." and I'm stuck in fastboot-mode with locked bootloader. Neither can start Rescue-, nor Recovery mode.
After I'm not able to unlock bootloader (because I never allowed it on her phone), I will bring it back to the shop tomorrow and ask for an exchange/repair.
But how can that be? Shouldn't a locked bootloader protect the device from a brick like that? I mean the flash-all.sh runs some "fastboot flash" and a "fastboot update" command, and they should just fail on locked bootloader, shouldn't they?
Weltraumpenner said:
I got two brand new Pixel 4a (5G) for my girlfriend and me. Mine worked perfect, hers was freezing and rebooting all the time. To solve this, I wanted to reflash the factory image.
I messed up the two devices and didn't notice, that the bootloader on hers wasn't unlocked yet. So I ran flash-all.sh on locked bootloader. Now the Pixel says "Can't find valid operating system." and I'm stuck in fastboot-mode with locked bootloader. Neither can start Rescue-, nor Recovery mode.
After I'm not able to unlock bootloader (because I never allowed it on her phone), I will bring it back to the shop tomorrow and ask for an exchange/repair.
But how can that be? Shouldn't a locked bootloader protect the device from a brick like that? I mean the flash-all.sh runs some "fastboot flash" and a "fastboot update" command, and they should just fail on locked bootloader, shouldn't they?
Click to expand...
Click to collapse
Try fastbooting the newest ota instead of the full factory image. Also, try going to Android recovery and hitting the factory reset inside the menu there. I believe to access the recovery through fastboot you wait for the dead Android guy and then press volume up and power at the same time.
Sent from my Pixel 4a using Tapatalk
Did you ever figure this out? Google had a chrome extension flag tool. Instead of cmd/cli adb.
Hey all, Just got Redmi note 10 pro. I'm trying to unlock, but can't get it to show up in unlock tool. I followed all the steps here:
XiaomiWiki.github.io
Resources for Xiaomi devices, formerly hosted on r/Xiaomi
xiaomiwiki.github.io
Nothing showing up, even after refresh. Developer options is enabled and everything. I hold Vol Down + Power to get into fastboot flash screen, but no recognition. What is wrong?
Thanks.
EDIT: FIXED
I just noticed, my device says SIM card not installed or activated, even though it uses phone data fine. How do I fix this?
I fixed it, this was an issue with my google USB drivers. closed
Hey folks! I have an OG Pixel XL - Stock ROM and locked bootloader.
Yesterday my phone just rebooted - no warning, and is now stuck on the Google logo screen. I can get the bootloader up by holding PWR + Volume Down, but when I go into recovery mode, I just get the Google Logo again - not what is expected with the broken Android icon, and the "No command" message.
I'd love to be able to flash the ROM back onto it - either stock or third-party since the phone is still in good condition from a hardware perspective.
Any other ways to flash a phone that seems to be soft-bricked?
Thanks!
UPDATE: When I try to use fastboot flashing unlock or similar commands, I get an error "FAILED (remote: 'oem unlock is not allowed')"
Kevingwpg said:
Hey folks! I have an OG Pixel XL - Stock ROM and locked bootloader.
Yesterday my phone just rebooted - no warning, and is now stuck on the Google logo screen. I can get the bootloader up by holding PWR + Volume Down, but when I go into recovery mode, I just get the Google Logo again - not what is expected with the broken Android icon, and the "No command" message.
I'd love to be able to flash the ROM back onto it - either stock or third-party since the phone is still in good condition from a hardware perspective.
Any other ways to flash a phone that seems to be soft-bricked?
Thanks!
UPDATE: When I try to use fastboot flashing unlock or similar commands, I get an error "FAILED (remote: 'oem unlock is not allowed')"
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/...ck-twrp-factory-image-stock-recovery.3730229/
spiral777 said:
https://forum.xda-developers.com/t/...ck-twrp-factory-image-stock-recovery.3730229/
Click to expand...
Click to collapse
Doesn't seem to work. I get the same error that OEM Unlock is not allowed - I cannot flash TWRP