Question Fixed fastboot loop, Now fingerprint sensor wont read

[Decree]

As the titles states, I recently recovered my Nothing phone 1 from a fastboot loop after trying to go back to stock, locked bootloader from the latest android 13 PE rom.

I ended up somehow "seemingly" deleted all the partitions on the phone. While using most of THIS unbrick method. Although i supplied my own 1.1.4 full ROM, and matching super image.
I manually flashed all of the partitions for Slot A and they all completed with no issues.
I manually flashed all of them again on Slot B and got a few partition errors.

I set slot A as active and the phone booted up fine and booted into Nothing OS, However my finger print reader doesnt read my finger now and i cant boot slot B into recovery/fastbootd. it just reboots back into bootloader.

I found that i needed to flash the persist.img partition but ive done that and it still does the same thing, and i still cannot get Slot b into recovery/fastbootd.

I am both unlocked and Critical unlocked.
Verified that I used the correct global ROM and super.img for both 1.1.4 and 1.5.1
Ive tried re-doing everything, Flashing all the images before the super.img. After the super.img, the persist.img before and after as well.
Ive tried re-flashing everything but using the 1.5.1 Beta 2 hotfix, and matching boot.img and the same issue.
i tried re-flashing everything from the bootloader screen instead of fastbootd and same issue.

All my other sensors seem to work fine, including SIM Data, gyroscope, light sensors, camera flash, wifi. Everything except fingerprint.

Can anyone help me get this figured out? Ill try to answer any questions the best i can.
Thanks!

 

[Decree]

Tested all the sensors with a couple applications all of which aren't recognizing the fingerprint sensor as being in the phone at all.

Can anyone tell me when the persist image is supposed to be flash and possibly upload their persist image here so I can try it?

1.5.1 global version.

 

[Ofdas23]

Hey, did you by chance change the kernel?

 

[Decree]

Hey, did you by chance change the kernel?

Not as far as I know. At least not manually, unless they were part of one of the batch files that ran.

 

[Ofdas23]

Not as far as I know. At least not manually, unless they were part of one of the batch files that ran.

Hmm, no, that's not the problem then

I don't know, flashing persist.img can have implications if not done properly and by no means am I any expert on this at all

I read that doing so improperly might end your device lose widevine L1 forever, which has impacts on DRM protected content, such as Netflix streams etc.

 

[Ofdas23]

You could also try to recalibrate, I don't know the implications of that though, as it goes deeper into the system

I don't know if I would mess with that

 

[Decree]

You could also try to recalibrate, I don't know the implications of that though, as it goes deeper into the system

I don't know if I would mess with that

I have no clue how I would do that unfortunately

 

[Ofdas23]

I have no clue how I would do that unfortunately

I think for that, you would have to be on stock ROM

also, how did you flash the images? In bootloader or fastbootd?

Fastbootd should be used

Edit:
Also I know, I am sending mixed signals, but when it comes to your slot b, maybe a recovery of a custom rom could fix it?

 

[Decree]

I think for that, you would have to be on stock ROM

also, how did you flash the images? In bootloader or fastbootd?

Fastbootd should be used

Edit:
Also I know, I am sending mixed signals, but when it comes to your slot b, maybe a recovery of a custom rom could fix it?

I am on stock 1.5.1 beta now

I flashed all images on slot a in fastbootd I tried to do that for slot B as well but I was unable to boot into it before. I would try to boot to recovery to do that and it would just loop back into bootloader.

Tonight, I flashed the PE room again per their instructions and then reflashed stock everything as if I was going back to stock with unlocked, and critical unlocked bootloader

Flashed boot and vendor boot for slot a, rebooted into fastbootd, flashed super.img, (which shows 25) then flashed all other images. Rebooted to bootloader and then flashed super again (this time it shows only 9) and then persist.

Did the same for slot B BUT this time I was actually able to boot to slot B recovery/fastbootd.

Phone boots up to stock Nothing OS again but still no working fingerprint.

Im honestly not sure if super should be flashed in fastbootd or bootloader or what order it should be flashed either. And the same for persist.Img

 

[Ofdas23]

I am on stock 1.5.1 beta now

I flashed all images on slot a in fastbootd I tried to do that for slot B as well but I was unable to boot into it before. I would try to boot to recovery to do that and it would just loop back into bootloader.

Tonight, I flashed the PE room again per their instructions and then reflashed stock everything as if I was going back to stock with unlocked, and critical unlocked bootloader

Flashed boot and vendor boot for slot a, rebooted into fastbootd, flashed super.img, (which shows 25) then flashed all other images. Rebooted to bootloader and then flashed super again (this time it shows only 9) and then persist.

Did the same for slot B BUT this time I was actually able to boot to slot B recovery/fastbootd.

Phone boots up to stock Nothing OS again but still no working fingerprint.

Im honestly not sure if super should be flashed in fastbootd or bootloader or what order it should be flashed either. And the same for persist.Img

Hold on, is your persist.img a functional one? If so, then that will fix your fingerprint issue

I am on stock 1.5.1 beta now

I flashed all images on slot a in fastbootd I tried to do that for slot B as well but I was unable to boot into it before. I would try to boot to recovery to do that and it would just loop back into bootloader.

Tonight, I flashed the PE room again per their instructions and then reflashed stock everything as if I was going back to stock with unlocked, and critical unlocked bootloader

Flashed boot and vendor boot for slot a, rebooted into fastbootd, flashed super.img, (which shows 25) then flashed all other images. Rebooted to bootloader and then flashed super again (this time it shows only 9) and then persist.

Did the same for slot B BUT this time I was actually able to boot to slot B recovery/fastbootd.

Phone boots up to stock Nothing OS again but still no working fingerprint.

Im honestly not sure if super should be flashed in fastbootd or bootloader or what order it should be flashed either. And the same for persist.Img

Hold on, is your persist.img a functional one? If so, then that will fix your fingerprint issue


Als, could you please run this code in the phone dialer?

*#*#0#*#

Also, super is supposed to be flashed in fastboot, as far as I am concerned, no Guanajuato

Edit:
Also, do you have Telegram or something, for easier messaging?

 

[Decree]

Hold on, is your persist.img a functional one? If so, then that will fix your fingerprint issue

Hold on, is your persist.img a functional one? If so, then that will fix your fingerprint issue


Als, could you please run this code in the phone dialer?

*#*#0#*#

Also, super is supposed to be flashed in fastboot, as far as I am concerned, no Guanajuato

Edit:
Also, do you have Telegram or something, for easier messaging?

It should be. Although I found it posted in one of the threads I'll have to find. It's literally the only one I could find, I'm unsure of how to extract a working one from a ROM.

From what I read it stores the calibration for most of not all the sensors on the device, but literally ALL of mine work except the fingerprint.

I'll do the dialer thing in a couple minutes.

So in what order should someone be flashing the images?
Super, images, persist?
Or
Persist, super, images?

And everything should be flashed via fastbootd?

I Don't have telegram but Ill set one up!

 

[Decree]

Hold on, is your persist.img a functional one? If so, then that will fix your fingerprint issue

Here is the persist I've used. I did also flash this on 1.1.4 like the post says but now since slot B goes into fastboot I'll try it again tomorrow?

Post in thread 'How to unbrick Nothing Phone 1 fastboot bootloop' https://forum.xda-developers.com/t/...one-1-fastboot-bootloop.4501439/post-87527709


I also just made a telegram. Not sure what you need to add me or start a chat but my username is Anfurnyy

 

[Ofdas23]

Here is the persist I've used. I did also flash this on 1.1.4 like the post says but now since slot B goes into fastboot I'll try it again tomorrow?

Post in thread 'How to unbrick Nothing Phone 1 fastboot bootloop' https://forum.xda-developers.com/t/...one-1-fastboot-bootloop.4501439/post-87527709


I also just made a telegram. Not sure what you need to add me or start a chat but my username is Anfurnyy

Use this app to restore it!

Partitions Backup & Restore - Apps on Google Play

Backup your important partitions to avoid any data or IMEI corruption

play.google.com

But use 1.1.4, as you said ^^

 

[Decree]

Use this app to restore it!

Partitions Backup & Restore - Apps on Google Play

Backup your important partitions to avoid any data or IMEI corruption

play.google.com

But use 1.1.4, as you said ^^

So you're saying use that app to put the persist. Img back into the file system and not flash it through fastboot?

 

[Ofdas23]

So you're saying use that app to put the persist. Img back into the file system and not flash it through fastboot?

Yes, exactly, but it requires root!

 

[Decree]

Yes, exactly, but it requires root!

Shouldn't be a problem. Plenty of patched boots for 1.1.4 lol I'll give it a go tomorrow. Thanks for the idea!

 

[Decree]

Yes, exactly, but it requires root!

So I was able to get it back to 1.1.4 today with root, and restore the 1.1.4 persist.img from that post using that app and still doesn't work. Only thing left I can think of is try to extract one from another ROM file and after that try to send it back to Nothing.

 

[Decree]

Just wanted to add a bit of closure to this post. I ended up having to send the phone back to Nothing for an RMA and they just flat replaced it with a new device. There was no fix for the fingerprint sensor that they told me.

Of course, everything is up and working great now.