Hello everyone,
Can someone help me with fixing my Persist Partition?
My Fingerprint Scanner doesn't work, and I found out it might be due to a corrupt /Persist.
I've tried extracting a Payload.bin (from the latest OTA Firmware) but it doesn't contain any Persist Images.
Can anyone either send me their Persist.img or help me find a original Persist.img from the Stock ROM?
Thanks in advance!
Fatal_Scythe said:
Hello everyone,
Can someone help me with fixing my Persist Partition?
My Fingerprint Scanner doesn't work, and I found out it might be due to a corrupt /Persist.
I've tried extracting a Payload.bin (from the latest OTA Firmware) but it doesn't contain any Persist Images.
Can anyone either send me their Persist.img or help me find a original Persist.img from the Stock ROM?
Thanks in advance!
Click to expand...
Click to collapse
Here you go...
Andrologic said:
Here you go...
Click to expand...
Click to collapse
Thank you!
If I may ask, is this your Persist, or is this from an Official ROM?
Fatal_Scythe said:
Thank you!
If I may ask, is this your Persist, or is this from an Official ROM?
Click to expand...
Click to collapse
It's mine. Persist is not part of the ROM, that's why you can extract it from there. It's factory installed in its own partition.
Andrologic said:
It's mine. Persist is not part of the ROM, that's why you can extract it from there. It's factory installed in its own partition.
Click to expand...
Click to collapse
That makes sense.
Though I kinda think that it's dumb that it's kind-of-impossible to obtain an "official" Persist Image from Asus since others like Xiaomi just put it into their Firmwares too, but alrighty I guess.
Will flash tomorrow and hopefully it helps.
Andrologic said:
It's mine. Persist is not part of the ROM, that's why you can extract it from there. It's factory installed in its own partition.
Click to expand...
Click to collapse
Well, kind of expected that but it doesn't work.
The Contents of my Persist Partition don't seem to change no matter how often I "erase" and "flash" the Persist.img. Calibrating with the "Factory Test" Tool also gives me an "get calibrate failed" error again so yeah.... Guess I'll go with Face Unlock for now.
Thank you very much though for your quick help.
Fatal_Scythe said:
Well, kind of expected that but it doesn't work.
The Contents of my Persist Partition don't seem to change no matter how often I "erase" and "flash" the Persist.img. Calibrating with the "Factory Test" Tool also gives me an "get calibrate failed" error again so yeah.... Guess I'll go with Face Unlock for now.
Thank you very much though for your quick help.
Click to expand...
Click to collapse
How do you flash it? Try using TWRP and if that doesn't work you should be able to flash it with the device in EDL mode.
Andrologic said:
How do you flash it? Try using TWRP and if that doesn't work you should be able to flash it with the device in EDL mode.
Click to expand...
Click to collapse
I tried all of that actually. It flashed just fine, but that's pretty much it.
Related
I went to codeworks page:
There are 4 files for the x522 in firmware and 4 in modems. I am assuming the "19s" firmware is for India so is the "20s" for the US?
But the 4 files in the modem section is confusing, which one/one's are for the US model x522? here is the link for the modems https://host.llamasweet.tech/codeworkx/lineage/s2/
Thanks
S2_x522-na-op-ifxnaop5802102141s-5.8.021s
leo221 said:
S2_x522-na-op-ifxnaop5802102141s-5.8.021s
Click to expand...
Click to collapse
Thanks but there is no file with that name listed in codeworks page is there? I have provided a link in the OP.
veda1 said:
Thanks but there is no file with that name listed in codeworks page is there? I have provided a link in the OP.
Click to expand...
Click to collapse
find here
https://forum.xda-developers.com/le-2/how-to/le-s3-20s-21sofficial-ota-lock-t3634079
leo221 said:
find here
https://forum.xda-developers.com/le-2/how-to/le-s3-20s-21sofficial-ota-lock-t3634079
Click to expand...
Click to collapse
Oh you mean flash that entire rom? And will that install the bootloader and modem? In any case, i tried flashing those files but they won't flash, any suggestions?
Since those roms won't flash i had to look for individual bootloader and modem and stumbled into those files by codeworks, and i am assuming you are saying that those aren't the correct files?
veda1 said:
Oh you mean flash that entire rom? And will that install the bootloader and modem? In any case, i tried flashing those files but they won't flash, any suggestions?
Since those roms won't flash i had to look for individual bootloader and modem and stumbled into those files by codeworks, and i am assuming you are saying that those aren't the correct files?
Click to expand...
Click to collapse
I just flashed 21S today on my 522. what recovery do you have right now? that's pure stock. flashing will erase everything and restore factory rom. https://youtu.be/v_aohNnvT_Q
leo221 said:
I just flashed 21S today on my 522. what recovery do you have right now?
Click to expand...
Click to collapse
twrp-3.2.1-0-s2, can't remember if i had the same one or one version older than the current one; when i tried it. Should i try it again? But the question is will it install the origibnal boot loader and modem? because i was playing with those in the past and flashed the wrong ones i think, and it will be great if i can go back to the original ones.
leo221 said:
I just flashed 21S today on my 522. what recovery do you have right now? that's pure stock. flashing will erase everything and restore factory rom. https://youtu.be/v_aohNnvT_Q
Click to expand...
Click to collapse
Yep its still happening. Tried to flash it right now and it says "can't read" error.
veda1 said:
twrp-3.2.1-0-s2, can't remember if i had the same one or one version older than the current one; when i tried it. Should i try it again? But the question is will it install the origibnal boot loader and modem? because i was playing with those in the past and flashed the wrong ones i think, and it will be great if i can go back to the original ones.
Click to expand...
Click to collapse
it certainty restores boot. not sure about modem, I never touched it. you have nothing to loose flashing it. it supposed to be bone stock. just delete two lines in the script and re-save zip. you have to do wipe, wipe data, then mount, copy zip, flash, reboot. in that order, I wasted hours today finding out that order is required. otherwise, it won't load.
https://forum.xda-developers.com/le-2/help/help-restoring-s3-x522-to-stock-rom-t3809619
leo221 said:
it certainty restores boot. not sure about modem, I never touched it. you have nothing to loose flashing it. it supposed to be bone stock. just delete two lines in the script and re-save zip. you have to do wipe, wipe data, then mount, copy zip, flash, reboot. in that order, I wasted hours today finding out that order is required. otherwise, it won't load.
https://forum.xda-developers.com/le-2/help/help-restoring-s3-x522-to-stock-rom-t3809619
Click to expand...
Click to collapse
Updated script according to the video, still not flashing, says "cannot read error"
veda1 said:
Updated script according to the video, still not flashing, says "cannot read error"
Click to expand...
Click to collapse
then you have a more complicated problem than mine. I had stock fastboot, and twrp.
leo221 said:
then you have a more complicated problem than mine. I had stock fastboot, and twrp.
Click to expand...
Click to collapse
Unbelievable! It actually worked after the 2nd attempt. Even got the 21s update. Thanks :good:
The original question is still unanswered about which one is the correct firmware for the US model amng the firmware provided by codeworks, hopefully someone knows that and will share in interest of others that might have the same problem.
Thanks again @leo221 for providing a clear and easy solution.
How is Huawei handling root? Is it suspected to work or will this be a problem?
I guess the rooting process may be a bit similar to the Mate 20s. It took a while before root became available for Mate and the process relies on a somewhat compilicated procedure involving FunkeyHuawei and buying credits. If you really want to have root then probably better to wait or to buy a phone which is easier to root.
Hi,
Somewhat agree. Root might take time.
What I can confirm is that oem unlock is not greyed out.
P30 Pro dev options https://imgur.com/a/unJy0ZX
So do you think that someone will cook TWRP and magisk?
I already extracted the ram disk and tried patching it with Magisk.
It didn't boot.
Any other bright ideas?
JazonX said:
I already extracted the ram disk and tried patching it with Magisk.
It didn't boot.
Any other bright ideas?
Click to expand...
Click to collapse
Hope that someone will find a solution, maybe on chinese forums. I can't buy a non-rootable phone.
JazonX said:
I already extracted the ram disk and tried patching it with Magisk.
It didn't boot.
Any other bright ideas?
Click to expand...
Click to collapse
Is not ramdisk that you need to patch, try patch stock Recovery, at least works with EMUI 9.
kilroystyx said:
Is not ramdisk that you need to patch, try patch stock Recovery, at least works with EMUI 9.
Click to expand...
Click to collapse
Yeah, It was called Ramdisk_recovery
That's the one, isn't it?
JazonX said:
Yeah, It was called Ramdisk_recovery
That's the one, isn't it?
Click to expand...
Click to collapse
Is "RECOVERY_RAMDIS.img", in the tool is missing the "K". You can rename it to "RECOVERY_RAMDISK.img"
If you need to flash in the fastboot use this command:
fastboot flash recovery_ramdisk recovery_ramdisk.img
My p30 pro arrive today and i thought i can root it with this tutorial
https://myphoneupdate.com/root-huawei-p30-pro-unlock-bootloader-install-twrp-recovery/
And now i read here that its not possible? That is very Bad if this is so :/
Sorry for Bad English
Edit: oh... Yes now i See no Service sells this Codes at the Moment..
kilroystyx said:
Is "RECOVERY_RAMDIS.img", in the tool is missing the "K". You can rename it to "RECOVERY_RAMDISK.img"
If you need to flash in the fastboot use this command:
fastboot flash recovery_ramdisk recovery_ramdisk.img
Click to expand...
Click to collapse
Yeah, I figured it. Output was patched_boot img. It flashed without any issues. But couldn't reboot afterwards. Went into bootloop, and then back to eRecovery. Normal boot is fine. Patched boot didn't work.
JazonX said:
Yeah, I figured it. Output was patched_boot img. It flashed without any issues. But couldn't reboot afterwards. Went into bootloop, and then back to eRecovery. Normal boot is fine. Patched boot didn't work.
Click to expand...
Click to collapse
:crying::crying::crying:
JazonX said:
Yeah, I figured it. Output was patched_boot img. It flashed without any issues. But couldn't reboot afterwards. Went into bootloop, and then back to eRecovery. Normal boot is fine. Patched boot didn't work.
Click to expand...
Click to collapse
Unfortunately this means that Magisk is not ready to patch EMUI9.1
Has anyone tried the process ?
I might be doing it wrong, Please give it a try from your end as well!
JazonX said:
Has anyone tried the process ?
I might be doing it wrong, Please give it a try from your end as well!
Click to expand...
Click to collapse
Can you upload your stock img RECOVERY_RAMDISK?
I'll patch for you and then if the CRC/SHA is different you can try mine.
kilroystyx said:
Can you upload your stock img RECOVERY_RAMDISK?
I'll patch for you and then if the CRC/SHA is different you can try mine.
Click to expand...
Click to collapse
I have uploaded it here.
JazonX said:
I have uploaded it here.
Click to expand...
Click to collapse
Patched by me is different from yours.
Link:
https://mega.nz/#!ZZgHgapa!NO5_2VxavqN7v9RNwTlxjNTmKR40rOyWIW6k18LRJ-w
You can check the MD5, first is one that you patched and second is the one patched by me
Enclosed you can find the Magisk version used by my.
Check mine and let me know if it works.
kilroystyx said:
Patched by me is different from yours.
Link:
https://mega.nz/#!ZZgHgapa!NO5_2VxavqN7v9RNwTlxjNTmKR40rOyWIW6k18LRJ-w
You can check the MD5, first is one that you patched and second is the one patched by me
Enclosed you can find the Magisk version used by my.
Check mine and let me know if it works.
Click to expand...
Click to collapse
How to flash? Don't we need to unlock the bootloader first, if so I have to buy a unlock code right? I'm om 0.124
Puksom said:
How to flash? Don't we need to unlock the bootloader first, if so I have to buy a unlock code right? I'm om 0.124
Click to expand...
Click to collapse
Yes, to flash you need bootloader unlocked.
Don't waste your money yet, let's first JazonX test the recovery_ramdisk.img patched by me.
JazonX, have you tried? I hope it works
I'm planning to buy the K20 Pro from Aliexpress with the Chinese Rom and then flash the global ROM.
I've searched the forum but couldn't find anything regarding IMEI repair incase something goes wrong.
Is it possible to repair the IMEI on the K20 Pro? has anyone tried it?
redvern said:
I'm planning to buy the K20 Pro from Aliexpress with the Chinese Rom and then flash the global ROM.
I've searched the forum but couldn't find anything regarding IMEI repair incase something goes wrong.
Is it possible to repair the IMEI on the K20 Pro? has anyone tried it?
Click to expand...
Click to collapse
In ten years of flashing a hundred phone's I've never experienced an IMEI issue. It's so extremely rare you almost never see it mentioned in any forum of any phone. It's really the last thing you need to worry about with this extremely fickle phone.
954wrecker said:
In ten years of flashing a hundred phone's I've never experienced an IMEI issue. It's so extremely rare you almost never see it mentioned in any forum of any phone. It's really the last thing you need to worry about with this extremely fickle phone.
Click to expand...
Click to collapse
Can you help me too? I am getting Nv data corrupted error on Redmi-Recovery 3.0 screen. It's all because of WriteDualIMEI. My main thread is here. Thanks...
Dentrax said:
Can you help me too? I am getting Nv data corrupted error on Redmi-Recovery 3.0 screen. It's all because of WriteDualIMEI. My main thread is here. Thanks...
Click to expand...
Click to collapse
If you can boot TWRP, then use LR team's TWRP, get the persist partition from the stock fastboot rom and flash the persist.img.
theincognito said:
If you can boot TWRP, then use LR team's TWRP, get the persist partition from the stock fastboot rom and flash the persist.img.
Click to expand...
Click to collapse
Thanks, I don't quite understand the second one. How can i get the persist partition? And where can I find the persist.img?
Dentrax said:
Thanks, I don't quite understand the second one. How can i get the persist partition? And where can I find the persist.img?
Click to expand...
Click to collapse
persist.img is inside the fastboot rom.
Dentrax said:
Thanks, I don't quite understand the second one. How can i get the persist partition? And where can I find the persist.img?
Click to expand...
Click to collapse
Fixed, see here.
i have the same problem. how do u do to recover your phone dude? help pls :c
Can someone please send me a backup of persist file because the ROM does not that and I bricked my device without a backup now orientation sensor is In a loop from 0 to 360. Any help would be highly appreciated.
dequr said:
Can someone please send me a backup of persist file because the ROM does not that and I bricked my device without a backup now orientation sensor is In a loop from 0 to 360. Any help would be highly appreciated.
Click to expand...
Click to collapse
we are not wizards to know what version of firmware your are using to send you the respective file
tutibreaker said:
we are not wizards to know what version of firmware your are using to send you the respective file
Click to expand...
Click to collapse
Lol I've got miui 13.6 global and miui 12.5 on which the device came with both global and running pixel experience plus so will help man.
There you go Persist data form MIUI 13.0.5ID
tutibreaker said:
There you go Persist data form MIUI 13.0.5ID
Click to expand...
Click to collapse
Have been searching for a long time hopes it fixes my problem tho any way to flash it without wiping data maybe fastboot will work ?
dequr said:
Have been searching for a long time hopes it fixes my problem tho any way to flash it without wiping data maybe fastboot will work ?
Click to expand...
Click to collapse
is a twrp back up
tutibreaker said:
is a twrp back up
Click to expand...
Click to collapse
Using pixel experience can't run twrp or orange fox
tho if anyone has the persist for Model: M2101K7BG AKA Redmi note 10s 6/128 non-NFC please send it here
tutibreaker said:
There you go Persist data form MIUI 13.0.5ID
Click to expand...
Click to collapse
I'm on global and I tried installing this zip but it says that "ERROR installing zip file.
any suggestions on what I could do?
dequr said:
I'm on global and I tried installing this zip but it says that "ERROR installing zip file.
any suggestions on what I could do?
Click to expand...
Click to collapse
you are supposted to extract it to /sdcard/TWRP/BACKUPS/(serialnumber) not flash it
if someone has a persist.img please send it so I can flash it using
./fastboot flash persist location/of/persist.img
would help a lot.
J6idot said:
you are supposted to extract it to /sdcard/TWRP/BACKUPS/(serialnumber) not flash it
Click to expand...
Click to collapse
ok, let me try.
J6idot said:
you are supposted to extract it to /sdcard/TWRP/BACKUPS/(serialnumber) not flash it
Click to expand...
Click to collapse
serialnumber of? I'm glad you're helping me. got it I'm sorry devices serial numb
J6idot said:
you are supposted to extract it to /sdcard/TWRP/BACKUPS/(serialnumber) not flash it
Click to expand...
Click to collapse
Okay so I directly placed its contents in the serialnumber folder and now I restore?
J6idot said:
you are supposted to extract it to /sdcard/TWRP/BACKUPS/(serialnumber) not flash it
Click to expand...
Click to collapse
Okay, so what I did was that I created a persist backup of mine delete its content and then replaced then with the contents of the one @tutibreaker sent me here and now still the compass is constantly ramping up in a loop but slower.
any solutions. I think the device is making its own when it needs it as it asked for unlocking but then changed back to normal without me unlocking it.
dequr said:
Okay, so what I did was that I created a persist backup of mine delete its content and then replaced then with the contents of the one @tutibreaker sent me here and now still the compass is constantly ramping up in a loop but slower.
any solutions. I think the device is making its own when it needs it as it asked for unlocking but then changed back to normal without me unlocking it.
Click to expand...
Click to collapse
are you using miui 13? because i thought miui 13 had an issue with the compass
J6idot said:
are you using miui 13? because i thought miui 13 had an issue with the compass
Click to expand...
Click to collapse
I flashed the persist on miui 13 then from the past some days I've been shifting from miui 12.5 to 13 to custom ROM tho it shouldn't change the persist. And at first the raise to wake-up also glitched but now it's working fine so idk there was an issue of compass it skipped points and jumped to some instant and after I sent it to the company then it came back and was working fine before I bricked it.
Hi,
I have a question about my OnePlus 10 pro. Some guy helped me revive my OnePlus through MSM tool after I bricked it flashing konabess overclock. It got me into crashdump. After a reboot, I got a fingerprint registration problem and wasn't able to register one ever since. As soon as I try to register one, it vibrates and doesn't show up any fingerprint icon at all. What can I do about this??
Phone used to be NE2213.
nothing. you may have lost your persist.img file. i don't believe that is recoverable using MSM. only if you have a backup.
g96818 said:
nothing. you may have lost your persist.img file. i don't believe that is recoverable using MSM. only if you have a backup.
Click to expand...
Click to collapse
What happened to OnePlus seriously never experienced this in all their generation phones until this one. Are there any thing we can do reversing the problem?
NinoLatif said:
What happened to OnePlus seriously never experienced this in all their generation phones until this one. Are there any thing we can do reversing the the problem?
Click to expand...
Click to collapse
It's quite normal for people to lose it. Oneplus was bought out by OPPO. Oneplus as you knew it no longer exists.
g96818 said:
It's quite normal for people to lose it. Oneplus was bought out by OPPO. Oneplus as you knew it no longer exists.
Click to expand...
Click to collapse
NinoLatif said:
Hi,
I have a question about my OnePlus 10 pro. Some guy helped me revive my OnePlus through MSM tool after I bricked it flashing konabess overclock. It got me into crashdump. After a reboot, I got a fingerprint registration problem and wasn't able to register one ever since. As soon as I try to register one, it vibrates and doesn't show up any fingerprint icon at all. What can I do about this??
Phone used to be NE2213.
Click to expand...
Click to collapse
I've had the same thing occur.
Unfortunately there's no recovery so you can't reset file that controls these items.
The only thing you can do now is perform a Local re-flash or update.
Reply to this if you need the files to do so.
Savio Dantes said:
I've had the same thing occur.
Unfortunately there's no recovery so you can't reset file that controls these items.
The only thing you can do now is perform a Local re-flash or update.
Reply to this if you need the files to do so.
Click to expand...
Click to collapse
Thanks for the reply, I'd be glad to, pls let me know, greetings!
you will need a persist.img file from another NE2213(identical storage specifications) to restore the fingerprint.
Cyanide_zh said:
you will need a persist.img file from another NE2213(identical storage specifications) to restore the fingerprint.
Click to expand...
Click to collapse
I'd gladly even pay for one, thanks for the info!
NinoLatif said:
Thanks for the reply, I'd be glad to, pls let me know, greetings!
Click to expand...
Click to collapse
Install this file OP_LocalUpdater_For_Android12.apk
This will allow you to install the update locally.
This is the latest update: NE2215_11_C.21 Stable (full).zip
If for some reason you get stuck in a boot loop follow this guide I wrote:
https://forum.xda-developers.com/t/oneplus-10-pro-android-13-stock-update-rom-root-and-recovery.4525451/post-87806713
I have same problem on my OP9, and I can fix it with this video. Its 100% work, but need to buy calibration tool. I buy this one on the aliexpress.
Savio Dantes said:
Install this file OP_LocalUpdater_For_Android12.apk
This will allow you to install the update locally.
This is the latest update: NE2215_11_C.21 Stable (full).zip
If for some reason you get stuck in a boot loop follow this guide I wrote:
https://forum.xda-developers.com/t/oneplus-10-pro-android-13-stock-update-rom-root-and-recovery.4525451/post-87806713
Click to expand...
Click to collapse
One thing I forgot to mention is that you need to have your ROM version correct
- India ROM
- EU Rom
- World ROM
If the version I've provided ( World ROM) does not work for you, simply download the correct one, and follow the same steps.
NinoLatif said:
I'd gladly even pay for one, thanks for the info!
Click to expand...
Click to collapse
Try the following command: dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img.
Savio Dantes said:
Try the following command: dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img.
Click to expand...
Click to collapse
Thank you brother for the help, nothing works, i have flashed, rolled back and forth every region and update, even flashed manually through fastboot enhanced, still no luck. Never should've flashed konabess, this would never happened
Sounds like its time to perform a:
Google back-up
What's app back-up
Format/Wipe Device
Restore Google and WhatsApp
Savio Dantes said:
Sounds like its time to perform a:
Google back-up
What's app back-up
Format/Wipe Device
Restore Google and WhatsApp
Click to expand...
Click to collapse
Trust me brother, this issue is on a whole other level. I'm sure someone will have the same problem (hope not), and that there will be a fix one day. I also did all on the list here multiple times. I've got to know a guy on Telegram, he says he can fix it. I'll update soon if something good is up. Greetings bro
NinoLatif said:
Trust me brother, this issue is on a whole other level. I'm sure someone will have the same problem (hope not), and that there will be a fix one day. I also did all on the list here multiple times. I've got to know a guy on Telegram, he says he can fix it. I'll update soon of something good is up. Greetings bro
Click to expand...
Click to collapse
Sounds good, let us know if and when you get things sorted.
Savio Dantes said:
Sounds good, let us know if and when you get things sorted.
Click to expand...
Click to collapse
Savio Dantes said:
Sounds good, let us know if and when you get things sorted.
Click to expand...
Click to collapse
I know what the issue is now, the persist.img is corrupted due to konabess overclock installation. This can only be recovered through another OnePlus 10 pro of the same model it's persist.img file you need to extract and flash it on the corrupted OnePlus to get it working again, the guy is going to share me a file soon. As soon as I'll get it, i might be the first one with the file for the OnePlus 10 pro. I'll share it here
NinoLatif said:
Hi,
I have a question about my OnePlus 10 pro. Some guy helped me revive my OnePlus through MSM tool after I bricked it flashing konabess overclock. It got me into crashdump. After a reboot, I got a fingerprint registration problem and wasn't able to register one ever since. As soon as I try to register one, it vibrates and doesn't show up any fingerprint icon at all. What can I do about this??
Phone used to be NE2213.
Click to expand...
Click to collapse
I now read again and find out malfunction of your device is not caused by konabess overclocking but by MSM tool downloading. Konabess overclocking will only modify the boot partition so it has nothing to do with the persist partition. The latter was broken as you downloaded a full rescue package with a invalid persist image.
Cyanide_zh said:
I now read again and find out malfunction of your device is not caused by konabess overclocking but by MSM tool downloading. Konabess overclocking will only modify the boot partition so it has nothing to do with the persist partition. The latter was broken as you downloaded a full rescue package with a invalid persist image.
Click to expand...
Click to collapse
This is the file, I fixed it finally! In case someone needs it