yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] alecxs:
you can't root Android 5+ like that. the only nurse fairy tale is post #4 as discussed here.

even with root access it's impossible to recover deleted files from FBE file-based encryption (which is enforced on devices shipped Android 10+)

you can try to recover files from Kingston MicroSD Card with card reader on PC

https://www.z-a-recovery.com
[General Questions and Answers] alecxs:
"For new devices running Android 10 and higher, file-based encryption is required."

(that means if device shipped on Android 9 it may receive update to Android 10 but is still running FDE btw)

while on FDE the DEK is ciphered with TEE static master key, FBE encryption keys are ciphered with random generated DEK in TEE keystore (which is flushed on factory reset). what you see in file metadata is KEK + DEK ciphered per-file-key (hash), where KEK is ciphered with lock screen credentials.

each files metadata is deleted when file is deleted, so the key is gone forever. as of the nature of encryption, file carving methods cannot understand what's left on disk and cannot restore any deleted files.

Now imagine, FBI forensics do a full dump of disk and find a method to magically restore each single byte of inode + dentry (for one single file), still they cannot decrypt that file without DEK.

FDE is encrypted with default_password without any lock screen pin at all (even if you set pin), which is common for most devices. that allows to bypass screen lock (impossible on FBE).

further the whole block partition is decrypted at once, so undeleting files (at least on ext4) is (in theory) possible.

if userdata and crypto-footer is dumped off the phone, that backup (on PC) will even survive factory reset, it can be restored afterwards and still it's possible to decrypt (online), as the static master key is burned to chip.

if one of the encryption methods is significantly more insecure then it's clearly FDE. to overcome this one should enable Secure Start-up.

btw modern devices (like OnePlus) combine both encryption methods FBE + FDE = metadata encryption (devices launched with Android 11+)
[General Questions and Answers] alecxs:
the answer is NO. Moto E40 uses metadata encryption.

Obviously you don't.

I pay you 100 € if you show any proof. just rm a file and try to recover on FBE encrypted flash storage.

or explain in what way retrieving of deleted files differs from restore?
[General Questions and Answers] alecxs:
wait... so you're the same guy who don't understand how SUID bit works and still claim we can place "suitable" SU-binary in /data/local/tmp?

well we shouldn't expect any proof then lol :LOL:(y)
[Samsung Galaxy S9+ Questions & Answers] Diablo6:
I have a galaxy s9+ with magisk root and Noble ROM 1.7 installed. I cannot use in-app payments in galaxy store (or any payment at all). I'm getting "Couldn't complete purchase" error:B7002/P/10FSV I do not want to Odin back to normal version.

ALSO paypal is not available in my country so that's not an option.
[Samsung Galaxy S9+ Questions & Answers] Debarslemani6:
Same
[Samsung Galaxy S9+ Questions & Answers] daaktursaab:
Don't know if this is useful to yoy anymore but try adding galaxy store and samsung billing/wallet in zygisk denylist
[Touch HD General] jospo:
Hi guys,

I am facing very annoying problem. Every time I dial somebody's number and cancel the call by tapping on red button, after short while the phone redials the number again. I cancel it again and after a while phone redials the number again. This is repeating until a) I reset the phone or b) the person I am calling to answers the phone call.

I do remember I saw some settings related to redialing when playing with phone, but I went thru all config dialogs and cannot find anything. Maybe a change somewhere in registry could help?

Also I did not find anywhere how to disable the notification after you receive a new text message or got a missed phone call. Woman voice is keeping saying: "you got a new message" or "you got a missed call". This is anoying as well especially when you sleep and you receive a new msg and even your ring tone is set to something very polite to keep you sleeping, that woman's voice is trying to wake you up telling you - hey "you got a new msg", wake up!

My ROM ver is 1.14.401.3 WWE, I did some changes with Advanced Config and I am using tools like AEButton, SecondToday and some other tweaks, but I don't think this has something to do with the above described issues.

Thanks for your advices!
[Touch HD General] jospo:
I have just found out that it is caused by REDIAL.EXE application which is stored in \Windows directory so I am not able to rename it or delete it. Is there any way how to get rid of this file? Thanks!
[Touch HD General] jospo:
I have finally found out what caused the issue. It was application HTCExtFun and I forgot that there are such settings. I use it for switching different keyboard layouts when stylus is in or out.

So to disable automatic redial, I needed to edit [HKCU\Software\HTCExtFun] registry and sent RedialTime to zero.

Also in the same registry you can disable that sound notifications for incomming text message or missed call.
[Touch HD General] Mr.Wolf:
You can rename any WM aplication to "REDIAL.EXE" and then copy this renamed redial.exe to \windows, it will take the place of the rom redial.exe.

Posted here: http://xdaforums.com/showthread.php?t=473371
[Touch HD General] LordDeath:
Thx for this thread. Now my HD doesn't redial anymore. :)
[Touch HD General] DrBasem:
well, this might bea bit out of the subject but.. isn't there any registry fix that prolongs the default vibration time of the HTC Touch HD when the call is connected?

i feel it is very short and often passes unnoticed.

I understand that the "Redial" application does so but i'm very obssessive about battery life and background programs so i much prefer to have a registry fix if possible.

any help?
[Vivo X80 Pro] aaserodio:
Hello

Does anyone know a way to do Backups on the Phone X80 Pro?

I'm in Brazil with OriginOs 3 installed.

Google backup fails at all.

And on Vivo Cloud it says it's not available in my country. Any solution?
[Vivo X80 Pro] morpheus620:
There is EasyShare from Vivo. Check this out.
[Samsung Galaxy S22 Ultra] mmafighter077:
So I use OfferUp and Mercari a lot. (Buying and selling apps, like craigslist and eBay). I've noticed after the most recent Samsung November update, when I have a private message with someone in either one of those apps the swiping feature on both Gboard and Samsung keyboards doesn't work. I have to peck at the keyboard to type.

It still works on other apps, for example when I'm swiping here. I've checked all kinds of settings and I don't see anything that would fix it. It seems to be similar how you can't swipe when entering a password. The keyboards can detect when it's a password field and disabled swipe but it's now doing it within these apps for private messages. I hope this makes sense.

I'm just looking for a fix below I cannot stand typing on a keyboard without swiping.
[Samsung Galaxy S22 Ultra] notnola:
Works for me. lol

View attachment 5771379
[Samsung Galaxy S22 Ultra] jedei80:
I'm having the same issue. Did you ever find a solution?
[Samsung Galaxy S22 Ultra] postulio:
I have the same problem. No solutions. Another annoying feature from the update is that in all messaging apps i see completely random words and phrases underlined as a maps link. Wtf
[Nothing Phone 1] jhonnytable:
Long story short, I bricked my device very hard, very many times while trying out different ROMS and getting accustomed to handling fastboot and adb. At some point along the journey I must've broken something to do with the fingerprint sensor (or the security authentication method)? The sensor doesn't pick up anything when I have my finger on it, as if I had replaced the screen or something. This happens with all ROMS, including after doing a full reset to factory images and running Nothing OS. Maybe a driver or something?

I was using NOS 1.1.6 and and reset to the image that I found on https://reindex-ot.github.io/

There is now also a 1.1.7 ROM but I haven't tried updating to it yet, though I will at some point.

I have no idea how this actually works so any help would be appreciated. If there is a fingerprint calibration method, a piece of software to help or a certain stock img file that is needed then please leave a reply!

For now I have been using Face Unlock as a drop in replacement, although the algorithm and sensors don't provide for as quick and reliable authentication as the fingerprint sensor, so I would really like to get this fixed.

It also kinda forces me into using Paranoid Android right now as it has best Face Unlock that I've come across so far, and being able to authenticate quickly is worth most of the downsides that come with using it at this stage of development.
[Nothing Phone 1] ot_inc:
Calibrating the fingerprint sensor may improve the situation. The site introduced here is in Japanese.

Relife RL-071Bで光学式画面内指紋認証センサーの動作を修正する方法 - AndroPlus

画面内指紋認証センサーを搭載したAndroidスマホで指紋を登録できなくなったときの対処法を紹介します。 キャリブレーションし直しで解決できる場合あり 画面内指紋認証センサーを搭載したAndroidスマートフォンでは、特にBootloader

androplus.org
[Nothing Phone 1] jhonnytable:
I read through the article and tried all the methods but I couldn't get anything to happen when I dialled. Thanks so much for the help though!

I think the reason my sensor is not working is because I flashed a persist partition when I was unbricking my phone, maybe if i flash a recent persist partition it will fix the fingerprint issue? Maybe it wont, not sure if something like that needs to be calibrated at the factory?

Either way, I am willing to try...

If anyone has a factory persist.img for Phone 1 that might help?

Ideally Nothing OS 1.1.6 full factory setup, but 1.1.7 will also help a lot as I can update.

Any post is appreciated!
[Nothing Phone 1] ot_inc:
I will put out a persist.img. I hope this fixes it.

NothingPhone(1)_Persist.zip

Nothing Phone(1) persist

drive.google.com
[Nothing Phone 1] jhonnytable:
Can I ask what version this is from?
[Nothing Phone 1] ot_inc:
v1.1.7
[Nothing Phone 1] dahare60:
Bhai chalu hua kya tumhara fingerprint sensor?
[Nothing Phone 1] Gratis4ever:
Still no solution ?
[Nothing Phone 1] lucy1983:
This fixes the missing ("unknown") serial number in phone settings, but not the fingerprint enrollment problem.
[Nothing Phone 1] ayed78:
any fix regarding fingerprint
[Nothing Phone 1] ayed78:
latest persist img 2.0.4?
[Nothing Phone 1] BunTiz96:
how to flash
[Nothing Phone 1] ayed78:
yes use this tool fix my issue after flash edl
[Nothing Phone 1] lucy1983:
În fastboot mode type "fastboot flash persist persist.img".
[Nothing Phone 1] BunTiz96:
can be fix??
[Nothing Phone 1] lucy1983:
Not the fingerprint. Only the "unknown" build number.
[Nothing Phone 1] ayed78:
need use calibration tool
[Nothing Phone 1] BunTiz96:
how to use tool
[Nothing Phone 1] D4rkKn1ght:
Hey I'll caveat this with I'm quite new to Android Modifications, if you reset the phone and re-flash stock firmware using Mark332's EDL Flashing Tool it may fix to the issue and afaik NOS_2.05 adds improvements for the facial recognition algorithm.
[Nothing Phone 1] BunTiz96:
how to use tool when software conflicts
[Nothing Phone 1] ayed78:
what you means conflict?
[Nothing Phone 1] BunTiz96:
indisplay finger apk

and i try hw software that conflict
[Nothing Phone 1] ayed78:
i use that apk provide by tool
[Nothing Phone 1] BunTiz96:
how

thank
[Nothing Phone 1] BunTiz96:
that in qr code??
[Nothing Phone 1] ayed78:
i have another
[Nothing Phone 1] BunTiz96:
can i get that
[Nothing Phone 1] BunTiz96:
can i get apk plsss??
[Nothing Phone 1] BunTiz96:
that conflict
[Nothing Phone 1] ayed78:
you need setup on 1.1.7 os version..there will no conflict..if upper version os will conflict,it kind nothing issue,even use default app,it become forcestop.
[Nothing Phone 1] BunTiz96:
I got that

Thank sir
[Nothing Phone 1] BunTiz96:
i try but get error unknow
[Nothing Phone 1] ayed78:
have many try
[Nothing Phone 1] BunTiz96:
that dont work for me
[Nothing Phone 1] ayed78:
weird
[Nothing Phone 1] greatpatel007:
Finally Figured out steps to fix the fingerprint.

You must downgrade to 1.1.7. else it will give a package conflict error as nothing has locked/removed access to CIT/Engineering mode.

Downgrade the firmware to OS v.1.1.7 using mark332's tool

here is the link to the post

unbrick tool- EDL Flash-Read-Repair Region Change tool

unbrick tool Now available for Nothing Phone1.. other unbrick tool by Me Redmi Note 8/8T, Redmi 9T/9 Power, Poco M3,Mi A2/6x,Mi A3,Redmi Note 7/ Note 7s,Note 6 Pro Features: Read Firmware (EDL) (locked bootloader) Flash Firmware (EDL) (locked...

xdaforums.com

Use the fingerprint calibration APK provided here. and use a calibration tool (rubber). (Thanks to ayed78 for APK)

IMPORTANT: Make sure you are in a dark room or have very little light. While calibration cover the phone with your hands or object so all the tests pass.

Step 1: Run the application and Choose the first option. By default sensor box location is very close to the bezels. You need to change the Y axis and move it up a bit so the calibration box location matches the actual location of the scanner.

Step 2: Go back to the main menu and select SPMT mode.

Step 3: Press start and wait till the initial test passes.

Step 4: You will see red text above which might be in Chinese and reads "PUT THE FLESH FLAT AND TAP NEXT" Use the Pink Rubber (or human skin color) and Press Next (Make sure you cover the phone with no light or room has no visible light)

Step 5: Put the black rubber and click next

Step 6: IMPORTANT. Use the Skin (FLESH) Color or Yellow Color rubber with grooves. You will feel straight lines on the rubber make sure that part faces the screen and lines should be in the horizontal direction (if placed vertically it will show an error). Once the rubber is placed click Next.

if you can't see any lines on your rubber tool then disassemble the tool take the rubber out and check it again. .

When all the test passes, congratulations you have successfully calibrated your fingerprint sensor.

Here is the link I found online which demonstrates the same for Nothing phone 1. Audio is in Hindi Language but good enough to understand the process.

Let me know if anyone faces any issues. Will try to resolve it.
[Nothing Phone 1] AnotherM1m:
I've made 06. BACK TO NOS -> RECOVERY to perform downgrades:

Nothing Phone (1) - Repo [ NOS ][ OTA ][ IMG ][ GUIDE ][ ROOT ]

Note: This is not a support thread for issues you may have with Nothing OS ROMs. If you need help installing or updating, feel free to ask here. If you have any other issues, please ask in another thread. Regarding problems with PHONE(1), you...

xdaforums.com

It may be simpler for some users.
[Nothing Phone 1] tekmor:
How much did you set the Y axis to? Does 1945 look right?

EDIT

: 1940 seems to be the correct value (see post #41).

View attachment 6056228
[Nothing Phone 1] greatpatel007:
I have started fingerprint lock enrollment from settings app (device lock settings) and marked the location of the sensor using masking tape and used that as reference to set the green box. It was similar to what you had. Unfortunately I don't remember the exact value of Y axis.
[Nothing Phone 1] tekmor:
I hadn't thought of using fingerprint lock enrollment. I tried this technique and had to adjust again the axis value.

For those who wish to set the axis, Y: 1940 seems to be the correct value.

Thanks for these explanations.
[Nothing Phone 1] dying_sun:
Hello, I've the same problem. I tried everything, without success. I've brought Relife RL-071B but I have error using the tool provided in this group and I also tried the app integrated (with adb, opening com.goodix.fingerprint.settings). Of course the first thing I've done it's to reflash persist.img partition.

There's anything I can do to fix this? Thanks in advance
[Nothing Phone 1] tekmor:
I've been trying for days and I'm still unsuccessful.

I've received help from greatpatel007 but unfortunately we still haven't managed to get my fingerprint sensor working again.

I bought the Relife RL-071 A and B model, neither of which has worked so far.

What error do you get with the application? something like 0x35 or 0x37 followed by the final message unknown error?

I think 0x37 TouchDiff of flesh flat rubber abnormal could be due by excessive brightness. So try in a darker room.
[Nothing Phone 1] BunTiz96:
same
[Nothing Phone 1] AnotherM1m:
Are there news about this? was anyone able to fix their issue?

Is it possible to make a guide for this?
[Nothing Phone 1] Style2010:
НYou need to calibrate the fingerprint sensor with a special device.
[Nothing Phone 1] tekmor:
So here's a summary of what we know about how to fix the fingerprint sensor problem.

​

Case 1: @greatpatel007's solution (post #37)​

This solution could work, at least it worked for author of the post. However, you'll need the following:

- the phone must be running NothingOS 1.1.7 (if you need to downgrade use @mark332's tool)

- you'll need to buy a calibration tool (Relife RL-071B, for example. Look like this)

Details and steps are described in post #37.

The Y-axis value in the first step is 1940 (see post #39 for screenshot).

Steps 3 to 6 will have to be repeated several times.

We don't know much about the meaning of the errors that occur during the process.

So far, here's what we do know:

0x37 TouchDiff of flesh flat rubber abnormal = could be caused by the room being too bright. Try again in a darker room.

If after several attempts, you don't get the success message then you're in case two.

​

Case 2: @greatpatel007's solution doesn't work for you​

For the moment, no solution has yet been found.

​

​

Let's brainstorm:​

What we do know is that this problem is due to the loss of the persist partition, and that flashing another device's persist partition doesn't solve the problem*. This problem could also occur after unlocking CRITICAL_PARTITIONS.

Don't hesitate to share your ideas. Maybe together we'll find the solution.

*this however fixes the serial number problem (see post #4).​
[Nothing Phone 1] hitech24sw:
do u have the Engineering mode Code For NP1.?
[Nothing Phone 1] ayed78:
nope..it need os 1.1.7 or 1.1.8..i just use apk that provide
[Nothing Phone 1] ayed78:
here some tutorial but in indian..im not indian
[Nothing Phone 1] tekmor:
@ayed78 can I ask you to detail the steps you took?

Did you flash edl with mark332's tool? Then once the phone was rebooted, you installed the apk and used the tool directly afterwards?

Did you flash the persist.img file provided?

Did you have any problems with the application? (errors, attempts, instructions to report)

Do you have any information or corrections to make to greatpatel007's guide (post #37)?

Sorry for all the questions. Maybe there's something we've missed that causes us to be unable to recalibrate with the application.

We're quite a few stuck and your answers could really help.
[Nothing Phone 1] ayed78:
yes after flash edl fp broken also serial number..im fix with tool but im not enable performance...im following that video and some tutorial,it same method only have other noted that it take couple times to fix
[Nothing Phone 1] ayed78:
and yes post 37 same as i use and only not follow step 1
[Nothing Phone 1] innoxentraheel:
I also try the same method but facing "unknown error" message .please help me.
[Nothing Phone 1] innoxentraheel:
Some please guide and help me this method not worked for me
[Nothing Phone 1] heartbreakkid58:
CIT/Engineering Mode code is *#*#0#*#*
[Nothing Phone 1] tipu1122:
Stil not working ,, plz help me ,
[Nothing Phone 1] heartbreakkid58:
@BunTiz96 , @tekmor, @innoxentraheel

are you guys able to fix the issue?
[Nothing Phone 1] tekmor:
Nothing at all... and to be quite honest, I'm getting a little desperate. The only clue we've been given doesn't seem to work all the time, or we're missing something. I really don't know what to do, we're in a bit of a pickle...
[Nothing Phone 1] AnotherM1m:
Tbh i remember someone talking about this working only on 1.1.3 or 1.1.4 (i would try with 1.1.3) and bootloader locked (or maybe it doesn't make any difference)

Are you able to check?

It had something to do with the engineering mode blocked since a certain NOS version
[Nothing Phone 1] tekmor:
I can confirm that the application (whose apk is available on this thread) will refuse to launch if the bootloader is not locked.

However, I have no information about the NOS version required.

I haven't checked whether there's a solution for downgrading to 1.1.3/4.
[Nothing Phone 1] AnotherM1m:
To downgrade to 1.1.3 the bootloader needs to be unlocked: download the full ota, extract the payload.bin then extract all the partitions with payload dumper from payload.bin

Use fastboot flasher from spike's archive to correctly flash all the partitions and wipe data.

Lock the bootloader then one can try again.
[Nothing Phone 1] heartbreakkid58:
@tekmor I'm not able to find FLESH Colored Rubber with "Grooves". So, I'm going to purchase it through AliExpress, but before that want to make sure that it will work.

The APK is recommended for the NOS 1.1.7 (or 1.1.8) and the bootloader should be locked. Anyhow, I'm just waiting for a go-ahead from the "affectees", so I can buy the tool online.
[Nothing Phone 1] tekmor:
The solution seemed to work for some people. If you read the replies in this thread, some users have said that the recalibration solution would have worked.

So the situation is simple: if you can afford to buy the tool on aliexpress, you've got to give it a try. No guarantee that it will work, though.

So either you can buy the tool, or you'll have to wait until the situation is clearer and we find a solution that works every time.

I'll try what AnotherM1m suggests and downgrade to 1.1.3 or 1.1.4, to see if it can come from there.
[Nothing Phone 1] innoxentraheel:
No
[Nothing Phone 1] AnotherM1m:
Do you all still got the box Phone 1 came with? it should have your phone's data about imei 1/2 and serial number
[Nothing Phone 1] tekmor:
I still have the phone box (and its crappy opening). After checking, the IMEI 1/2 are identical to those on the box.

The serial number, however, is different. The one on the box and the one in the settings don't match.

AnotherM1m do you have an idea?
[Nothing Phone 1] AnotherM1m:
yes i do, do you want to be a tester for it? We can write on discord or telegram depending on what you prefer
[Nothing Phone 1] tekmor:
ok to test your solution. I'll send you my telegram in dm
[Nothing Phone 1] heartbreakkid58:
I'm getting this error (see screenshot SPMT.jpg) while going through SPMT test..

while Dual Rubber Calibrating Test gives different errors, like "rawData check failed" or "Self-Exposure abnormal". (screenshot Dual-Rubber-Calibrating-Test.jpg)

Please advise what to do next?
[Nothing Phone 1] AnotherM1m:
When you used the unbrick tool, did you noticed if any error was displayed on the tool's console? like payload too big or something like that?
[Nothing Phone 1] heartbreakkid58:
@AnotherM1m Yes, I got few errors which went unnoticed, but I recovered my phone (from Brick mode) . Then I did updates and reached the NOS 2.5.x. Later, I noticed the fingerprint sensor was not working. So for this, then again I used the Unbrick tool to go back to NOS 1.1.7, but there was "no error" this time.. Clean flash done without warning or errors. Now, i'm on NOS 1.1.7 and have no plan to update the software unless I fix the fingerprint sensor.
[Nothing Phone 1] AnotherM1m:
Were your critical_partitions unlocked when you used edl? how did you brick your phone?
[Nothing Phone 1] heartbreakkid58:
Yes, "critical_partitions" was unlocked, I deleted "system partition" (maybe) via EFT PRO tool, which causes the phone bricked. Actually, I was repairing/chaning IMEI through EFT PRO tool, which I didn't know how to use, but I deleted something that should not be deleted, and it made it Brick. And you know I used unbrick tool to make it work (and critical_partition unlocked).
[Nothing Phone 1] AnotherM1m:
Thank you, im still searching for a solution.