[CLOSED]TSOFF5NOW-70OFF - macOS

@Beta13 Thread closed as it's not related to macOS and simply just a copy of this thread by @viva virus
redmi 9 blur effect
hi all i try every thing to get the blur effect and edited the systemui.apk (android11 - 12.0.3) cant flash the apk 1 my twrp dont show /system in backup option 2 try flash with magisk using old zip from note 8 and replaced my new apk and...
forum.xda-developers.com
Please review the XDA Forum Rules with special emphasis on rules no. 5 and no. 15 and post only ONCE, do NOT create duplicates and do NOT just copy/paste a post. Thanks for your cooperation!
Regards
Oswald Boelcke
Senior Moderator
#1
hi all i try every thing to get the blur effect and edited the systemui.apk (android11 - 12.0.3)
cant flash the apk
1 my twrp dont show /system in backup option
2 try flash with magisk using old zip from note 8 and replaced my new apk and flash and nothing
3 mount system in twrp it is show but get error when i try copy and past manually in twrp
any help plz i want the blur

The all things first thing is I need fix my errors can you fix it error
I need the Android 11 in my phone
And best future colours because I am hair stylist I want to be the best colour and futures and the best camera thing possible if you if you are send me the link of that process I will click and you I just see the all things

Related

[MOD] PRL Write Enabler for Sprint Galaxy S4 [MDC][MDL][MJA]

First off this work is based on Digiblur's PRL Write Enabler from the Sprint Galaxy S3 forum. I simply modified it & packaged it for our Sprint Galaxy S4 devices.
Here is the original S3 post that this was found in... http://forum.xda-developers.com/showthread.php?t=2159054
Also, post #8 below provides additional info.
I tested it by flashing with TWRP and it worked on my stock, rooted S4 with the MDC and MDL releases.
If you're on a stock rooted Rom and not using TWRP, you can just copy the HiddenMenu.apk from inside the zip file downloaded into /system/app/ and overwrite the one that's there. (You'll need a root enabled file browser to do this of course).
Thanks to Unknownforce here is a version for MJA...
http://www.androidfilehost.com/?fid=23212708291676468
Enjoy!!
This certainly will save me from having to use CDMA WS to switch like I just did yesterday. 55014 was not working well for me in my market so I switched back to 25014.
What is write enabler?
Keeps aborting for me
THEGAMEPLAY94 said:
Keeps aborting for me
Click to expand...
Click to collapse
You mean the install of the zip?
If so, you can pull the APK out of the zip and replace HiddenMenu.apk in the system folder (make a backup first). You may want to also set the permissions to rw-r-r after replacing the system app. Reboot, then you should be good to go.
@ChadH42,
I know it seems like I'm harping on you but I'm really not..
You need to update the OP on - 1. What is this? 2. What does this do? 3. Why is this in the Development Section.. ?
A good OP leads to less questions.. Development Sections aren't for information. That would be considered a Discussion Thread that belongs in General.
Let's keep the Dev section clean from the start.
My suggestion - Edit the OP on the What's/Why's?/How To's and you won't get posts like mine.
To the OP, updated your title as [WIP], and I suggest you provided additional information so that folks aren't bricking their new devices.
I will check in, if you need anything, let me know.
What this MOD does (in case the OP takes a little while to chime in)
What this MOD does is modifies our ##DATA# (select View) menu to allow for the PRL Write option to appear and function. With this menu option, the user can change their PRL on the fly from the device itself by placing a copy of the desired PRL in the root directory of Internal Storage and name it "test.prl" (no quotes), dial ##DATA# (choose View), tap Write PRL, tap the sub-menu option Write PRL ---wait--- and then the device reboots with the test.prl PRL applied upon reboot. Not every PRL works and sometimes it takes a couple of tries.
A tip for multiple PRL options is to, of course, keep a folder of the PRLs you like and keep them labeled in there. Copy the desired PRL to proper place as needed and just remember to rename the copy to "test.prl". Switch back and forth as you please. I hope this helps clear some confusion and helps some find purpose with the MOD like I have.
For a clear set of instructions that I did not want to just copy verbatim, check the link below. Also, if you are having issues with the zip not installing in CWM, just extract the APK from the ZIP (inside the system/app folder), use Root Explorer or your favorite root-access file explorer to place the APK in the APP folder, apply the proper permissions and reboot.
Ref from the GS3: http://forum.xda-developers.com/showthread.php?t=1748516
So I unzipped the file, replaced the hidden menu original apk with the new one, then set permissions, rebooted, then tried ##3282# and the view and edit options do not appear.. .. It just blanks out the items I just entered
Sent from my SPH-L720 using Tapatalk 2
jayjay7411 said:
So I unzipped the file, replaced the hidden menu original apk with the new one, then set permissions, rebooted, then tried ##3282# and the view and edit options do not appear.. .. It just blanks out the items I just entered
Sent from my SPH-L720 using Tapatalk 2
Click to expand...
Click to collapse
Did you clear Cache when you rebooted?
What ROM are you using?
ChadH42 said:
Did you clear Cache when you rebooted?
What ROM are you using?
Click to expand...
Click to collapse
+1...same thing is happenening to me...Im on force rom. when i type in the dialer code it just blanks out.
lilmikeyv said:
+1...same thing is happenening to me...Im on force rom. when i type in the dialer code it just blanks out.
Click to expand...
Click to collapse
I just tried this mod with the Force ROM and it did the same thing (blank options). The only thing I can think of is that it works with the odex version of the stock ROM so maybe its a problem with deodex ROMs of which Force is one.
O okay. Its currently not a necessary thing for me at the moment, just nice for when I travel to Alabama. Hopefully later on someone gets it working on deodex.
Sent from my Nexus 4 using Tapatalk 2
ChadH42 said:
I just tried this mod with the Force ROM and it did the same thing (blank options). The only thing I can think of is that it works with the odex version of the stock ROM so maybe its a problem with deodex ROMs of which Force is one.
Click to expand...
Click to collapse
I am actually running it on the Rooted Stock DeOdexed ROM. So I don't think it is an Odex/DeOdex issue...might be a Force ROM issue.
Also, moot point for Force ROM (1.0+) anyway because the PRL Write mod is already included with that.
I'm also having this problem and I'm pretty sure it was working this morning. I haven't flashed anything since then.
edit-- I tried:
1. wiping both cache's
2. killing background process "OIThiddenmenu"
neither fixed it.
I reinstalled the stock odex ROM and flashed this again and it worked.
Just an FYI, OP, I get Error Status 6 when trying to flash this via recovery, which indicates one of two things. Either the format of the file is incorrect or there is a syntax error. The syntax looks fine, but opening in basic Notepad shouldn't "look pretty" like it currently does. So it's likely it was edited with a non-Unix-compatible text editor like Notepad or MS-Word...
To make modifications to an updater-script (or just about any Android/Linux files like this) you need something like Notepad++ or gVim.
Anyways, I did a quick test with this, and it does in fact not work on my ROM as it is, but I see why it's failing, but I don't know what exactly it's trying to reference yet. (It fails with an id number instead of a name, so I'll have to de-compile some things to find it.)
I'm not sure it's a ROM issue or a MOD issue yet. (meaning it might have to be updated for each custom ROM, depending on how they are configured) But I'll track it down and update when I can.
Unknownforce said:
Just an FYI, OP, I get Error Status 6 when trying to flash this via recovery, which indicates one of two things. Either the format of the file is incorrect or there is a syntax error. The syntax looks fine, but opening in basic Notepad shouldn't "look pretty" like it currently does. So it's likely it was edited with a non-Unix-compatible text editor like Notepad or MS-Word...
To make modifications to an updater-script (or just about any Android/Linux files like this) you need something like Notepad++ or gVim.
Anyways, I did a quick test with this, and it does in fact not work on my ROM as it is, but I see why it's failing, but I don't know what exactly it's trying to reference yet. (It fails with an id number instead of a name, so I'll have to de-compile some things to find it.)
I'm not sure it's a ROM issue or a MOD issue yet. (meaning it might have to be updated for each custom ROM, depending on how they are configured) But I'll track it down and update when I can.
Click to expand...
Click to collapse
Thanks for all your help here..
I had the error status 6 problem in the beginning and thought I fixed it. You are correct that I used MS WordPad to edit the files.
ChadH42 said:
Thanks for all your help here..
I had the error status 6 problem in the beginning and thought I fixed it. You are correct that I used MS WordPad to edit the files.
Click to expand...
Click to collapse
I think TWRP can read the non Unix type characters, which is why it works on a different recovery.
I'm hoping it's a mod issue and I can just modify the mod to work universally regardless of the rom. But we'll see.
Sent from my SPH-L720 using xda app-developers app
fails in recovery for me.
says error executing updater binary in zip
in stock rooted...

Ultra Debloater for Samsung J7 2016 devices

Hi friends,
As we all know, sammy devices comes with lots of junks and bloats which hardly we use.
So, i was looking for a thread where i could find a way to debloat/remove excess system files from J7/6 but i was quite depressed when i found no link for my device. Although some nice techies have posted zip from other sources, i mean some debloater zips are directly posted here from s6 groups. And as we know that not all devices have same bloats or junks or having different names of same bloats.
That's why i tried to do some changes on a zip made by @TENN3R (Originally made by @ambasadii . Thanks both of you man) and finally come here with this work. Hope you'll love it.
Before flashing this zip, my device system part was showing 118mb space. After flashing zip modded by me, i got whopping 1.19gb free space in system.
All i can say is, your device system will have a great amount of space to breath which will surely show you result in battery life + performance (as per my experience I'm getting +15/20% battery life and performance is superb)
So, let's come to the point. There's attached zip, download it & move it to device internal storage/sdcard/usbotg. Reboot to recovery (your device must be rooted with TWRP recovery preinstalled). Flash this zip and wipe dalvik/cache. Reboot to system and you'll see that almost all junks is removed.
To know which apps it removes and if you want to keep some system apps, open zip, copy updater script on your pc, open updater script with notepad++, check all apps names one (takes hardly few minutes) and if you want to keep any app in system and don't want to remove it, just remove that whole line. For example, if you want to keep "GoogleContactsSyncAdapter", remove line contains that app name ? runs ("/sbin/rm", "-rf", "system/app/GoogleContactsSyncAdapter"); ? including semicolon same as shown here.
I suggest you to take backup of all apps (system/app & system/priv-app) so in case you want to restore any app, you can do it. It will remove some unwanted junk apps from csc folder also, (Yes it will remove bike mode too)
I have tested this zip few times on my device (SM-J710GN) and on one another device (SM-J710FN) and there's no any fc or issues. So i think it's worth trying.
But as we all say here, I'm not responsible if your device get bootloops, your wife hits you or your dog bites you for some reasons.
Do not forget to hit thanks button. :fingers-crossed::fingers-crossed:
Link:
http://www.filehosting.org/file/details/624732/Modded_J7_DeBloater_MMv1.zip
Good work bro
i did not succeeded with installation of this zip. TWRP just said that it failed.
Good work! I must try it out.
Excellent! Works like a charm! Thank you a lot. I've done a video guide (sub Eng). Hope this can be helpful.
can we use an script like this to restoring or adding new apps to the system?
(instead of -rm -mv to another folder and restoring with -cp )
Hello can i use this firmware to my J700H?
bro can u tell me how can i remove s bike mode from my j7 2016
I get so mad when i see that s bike mode logo i didn't even use it plzz tell me
i can't download the file....can u upload here???
thanks
matrixrio said:
can we use an script like this to restoring or adding new apps to the system?
(instead of -rm -mv to another folder and restoring with -cp )
Click to expand...
Click to collapse
ryu091 said:
Hello can i use this firmware to my J700H?
Click to expand...
Click to collapse
someone can upload the file zip in another place? Thanks, is impossible to download there!
best regards
dacorsa said:
someone can upload the file zip in another place? Thanks, is impossible to download there!
best regards
Click to expand...
Click to collapse
Here is the original zip file attached.
You should edit the script according to your needs before flash.
Because it also remove sbrowser, nfcui,sbike etc. etc.
matrixrio said:
Here is the original zip file attached.
You should edit the script according to your needs before flash.
Because it also remove sbrowser, nfcui,sbike etc. etc.
Click to expand...
Click to collapse
Thanks you're a gentleman
Lost Network
I lost my sim networks, both Sim 1 and Sim 2 after flashing the zip file. Bad part is, I didn't make a back up before doing the process.
Can't not open ' Setting '
I know this thread was old thread,but I'm just want to asking why my J7 2016 can't open setting after i flash the debloater?

[CLOSED][STOCK] [10.3.2] RESTORE TO STOCK - EASYPEASY!!

Are you having nightmares trying to restoring your Oneplus 7T to stock? This is for you.
This package will restore your Oneplus 7T to 10.3.2 stock. Make sure you have backed up the data, stock restore will wipe everything.
*Disclaimer* I am not the owner of these files nor have I in any way modified any of these files. I have however restored my Oneplus 7T (Indian variant) several times using this. Use at your own risk and discretion.
Instructions
1. Install 7-zip
2. Download and Extract the zip (*.7z file)
3. open Command prompt into the extracted folder
4. reboot your phone into fastboot (power off > press power button+both volume buttons)
3. Run "flash wipe both all everything.bat"
4. Lock the bootloader by typing "fastboot oem lock"
@tantry2002 Thread closed as duplicate of
[STOCK] [10.3.2] RESTORE TO STOCK - EASYPEASY!!
Are you having nightmares trying to restoring your Oneplus 7T to stock? This is for you. This package will restore your Oneplus 7T to 10.3.2 stock. Make sure you have backed up the data, stock restore will wipe everything. *Disclaimer* I am not...
forum.xda-developers.com
Usually I'd closed that one because you created that thread 7 minutes later. Another duplicate has been deleted. And this thread has been moved out of the development section, for which your threads don't qualify:
Device Forum Rules (Please Read before Posting)
In this thread, we will provide a short Q&A for your stay on this forum. Please read thoroughly and act accordingly. While most that is needed to know is pointed out in the Forum Rules, history shows that some points of these rules are not...
forum.xda-developers.com
XDA Forum Rules
Spoiler: Rule No. 5
5. Create a thread topic or post a message only once, this includes external links & streaming media.
As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer.
You can bump your unanswered question once every 24 hours
Duplicate threads and posts will be removed
Always post in an existing thread if a topic already exists, before creating a new thread.
Use our search function to find the best forum for your device.
Links to an external source are only allowed if relevant to the topic in hand. A description must be included, no copy & pasting from the original source.
Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.

Sensors files missing from Persist. Fixed

I have lost all sensor calibration files and reg files for all sensors, screen, sound, rotate, brightness ect.
Can someone with a 4xl and a root explorer please go to /mnt/vendor/persist .
Please archive the directory in .tar or zip, twrp backup.
There have been a few requests on the 4XL forum for the files or for persist.img if you're able to /dd it.
I cannot find them for the Pixel 4XL anywhere.
I know which files to skip when replacing and have a backup, I take full responsibility.
Attach the file to a reply it's small enough when archived.
You would be helping me and others out, judging from search.
Thanks.
--------------------------------------------------------------------------------------------------------
EDIT: FIX
---------------------------------------------------------------------------------------------------------------
To clear up any confusion the symptoms are all sensors stop working not one or two.
The IMEI is not lost or changed with this method nor any MAC addresses on the "Google Pixel 4 XL".
I managed to fix all sensors failed with another users persist backup from a .zip file.
You should check the attachment file verses your current Persist, if you have all the files excluding the duplicate data folders don't even bother Instead start at the factory image install, relock boot loader stage.
Check it's not a software problem before doing this.
Get sensor toolbox.apk and check there is no data output from the sensors first.
If you are going to try this before you start back up all the files in /mnt/vendor/persist to a .tar file.
There is a camera certificate in camera directory that is unique to your camera module if you lose that you cannot use face unlock ever again. Same if you replace the hardware.
I had to manually restore all permissions because they were not in .tar format I've attached the fixed persist.tar.
I performed all operations from lineage 19.1 with magisk 25.1 full root and used mixplorer.apk root enabled.
Some steps may not be necessary.
Copy the files you need across from a root browser, if any duplicate files & folders are in there don't replace them merge and skip duplicate files instead.
There is a folder in the data directory named something like (DdHdVQd1FIOARksZgXG27GJ1A5UjYCGhP-ZoGvseqsY_)
I copied all files in each folder to all the others, so every folder had the same number of files in. (if they already exist then skip them.)
Install a stock factory image it should be a version below the latest OTA so A12 factory image- to A13 OTA. (I used A12 -coral-sq3a.220605.009.a1)
I then relocked the boot loader, disabled OEM unlocking, added an account to the phone on the phone setup dialogue and added a pin.
I let it update the apps made sure it was listed as my device in security settings and checked safety net all pass.
Tried face unlock(failed), started wallet setup then stopped at add card.
Rebooted a few times in between app updates then allowed the OTA to A13 install. (it was slow to finish install)
Then on first reboot it got into OS and said finishing setup let it finish then rebooted again and BishBashBosh all sensors functional.
It's might be titan security chip anti tamper or qualcomm chain of trust?
If you want to understand how this can be triggered with all files still intact and why replacing them won't instantly work check NPJOHNSON's excellent article.
https://lineageos.org/engineering/Qualcomm-Firmware/
Thanks to YKS_Gaming for providing a copy of Persist for the Pixel 4XL.
I hope this helps someone else.
doesnt the factory images contain the files?
i can give you the files but i dont know if it is safe to do it or not (what information does it provide, etc. im not familiar with these kind of stuff)
YKS_Gaming said:
doesnt the factory images contain the files?
Click to expand...
Click to collapse
No they are stored on /mnt/vendor/persist.
pls?
Pixie 4 XL said:
No they are stored on /mnt/vendor/persist.
pls?
Click to expand...
Click to collapse
Thank you so much.
As for your concerns, official updates have broken sensors before and users have shared these files with no consequences to the author.
See this thread as an example.
FIXED - Android 10 - Sensors Bug
EDIT 5 In addition to the two methods highlighted below, I'm sharing a third method which was brought up in the thread. This one is much easier, however, root is required. This method works for many, however, it is not confirmed by me. Again, no...
forum.xda-developers.com
Pixie 4 XL said:
I have lost all sensor calibration files and reg files for all sensors, screen, sound, rotate, brightness ect.
Can someone with a 4xl and a root explorer please go to /mnt/vendor/persist .
Please archive the directory in .tar or zip, twrp backup.
There have been a few requests on the 4XL forum for the files or for persist.img if you're able to /dd it.
I cannot find them for the Pixel 4XL anywhere.
I know which files to skip when replacing and have a backup, I take full responsibility.
Attach the file to a reply it's small enough when archived.
You would be helping me and others out, judging from search.
Thanks.
--------------------------------------------------------------------------------------------------------
EDIT: FIX
---------------------------------------------------------------------------------------------------------------
To clear up any confusion the symptoms are all sensors stop working not one or two.
The IMEI is not lost or changed with this method nor any MAC addresses on the "Google Pixel 4 XL".
I managed to fix all sensors failed with another users persist backup from a .zip file.
You should check the attachment file verses your current Persist, if you have all the files excluding the duplicate data folders don't even bother Instead start at the factory image install, relock boot loader stage.
Check it's not a software problem before doing this.
Get sensor toolbox.apk and check there is no data output from the sensors first.
If you are going to try this before you start back up all the files in /mnt/vendor/persist to a .tar file.
There is a camera certificate in camera directory that is is unique to your camera module if you lose that you cannot use face unlock ever again. Same if you replace the hardware.
I had to manually restore all permissions because they were not in .tar format I've attached the fixed persist.tar.
Some steps may not be necessary.
Copy the files you need across from a root browser, if any duplicate files & folders are in there don't replace them merge and skip duplicate files instead.
There is a folder in the data directory named something like (DdHdVQd1FIOARksZgXG27GJ1A5UjYCGhP-ZoGvseqsY_)
I copied all files in each folder to all the others, so every folder had the same number of files in. (if they already exist then skip them.)
Install a stock factory image it should be a version below the latest OTA so A12 factory image- to A13 OTA. (I used A12 -coral-sq3a.220605.009.a1)
I then relocked the boot loader, disabled OEM unlocking, added an account to the phone on the phone setup dialogue and added a pin.
I let it update the apps made sure it was listed as my device in security settings and checked safety net all pass.
Tried face unlock(failed), started wallet setup then stopped at add card.
Rebooted a few times in between app updates then allowed the OTA to A13 install. (it was slow to finish install)
Then on first reboot it got into OS and said finishing setup let it finish then rebooted again and BishBashBosh all sensors functional.
It's might be titan security chip anti tamper or qualcomm chain of trust?
If you want to understand how this can be triggered with all files still intact and why replacing them won't instantly work check NPJOHNSON's excellent article.
https://lineageos.org/engineering/Qualcomm-Firmware/
Thanks to YKS_Gaming for providing a copy of Persist for the Pixel 4XL.
I hope this helps someone else.
Click to expand...
Click to collapse
i was finding this thread goona try it now hope it helps
Pixie 4 XL said:
I have lost all sensor calibration files and reg files for all sensors, screen, sound, rotate, brightness ect.
Can someone with a 4xl and a root explorer please go to /mnt/vendor/persist .
Please archive the directory in .tar or zip, twrp backup.
There have been a few requests on the 4XL forum for the files or for persist.img if you're able to /dd it.
I cannot find them for the Pixel 4XL anywhere.
I know which files to skip when replacing and have a backup, I take full responsibility.
Attach the file to a reply it's small enough when archived.
You would be helping me and others out, judging from search.
Thanks.
--------------------------------------------------------------------------------------------------------
EDIT: FIX
---------------------------------------------------------------------------------------------------------------
To clear up any confusion the symptoms are all sensors stop working not one or two.
The IMEI is not lost or changed with this method nor any MAC addresses on the "Google Pixel 4 XL".
I managed to fix all sensors failed with another users persist backup from a .zip file.
You should check the attachment file verses your current Persist, if you have all the files excluding the duplicate data folders don't even bother Instead start at the factory image install, relock boot loader stage.
Check it's not a software problem before doing this.
Get sensor toolbox.apk and check there is no data output from the sensors first.
If you are going to try this before you start back up all the files in /mnt/vendor/persist to a .tar file.
There is a camera certificate in camera directory that is is unique to your camera module if you lose that you cannot use face unlock ever again. Same if you replace the hardware.
I had to manually restore all permissions because they were not in .tar format I've attached the fixed persist.tar.
Some steps may not be necessary.
Copy the files you need across from a root browser, if any duplicate files & folders are in there don't replace them merge and skip duplicate files instead.
There is a folder in the data directory named something like (DdHdVQd1FIOARksZgXG27GJ1A5UjYCGhP-ZoGvseqsY_)
I copied all files in each folder to all the others, so every folder had the same number of files in. (if they already exist then skip them.)
Install a stock factory image it should be a version below the latest OTA so A12 factory image- to A13 OTA. (I used A12 -coral-sq3a.220605.009.a1)
I then relocked the boot loader, disabled OEM unlocking, added an account to the phone on the phone setup dialogue and added a pin.
I let it update the apps made sure it was listed as my device in security settings and checked safety net all pass.
Tried face unlock(failed), started wallet setup then stopped at add card.
Rebooted a few times in between app updates then allowed the OTA to A13 install. (it was slow to finish install)
Then on first reboot it got into OS and said finishing setup let it finish then rebooted again and BishBashBosh all sensors functional.
It's might be titan security chip anti tamper or qualcomm chain of trust?
If you want to understand how this can be triggered with all files still intact and why replacing them won't instantly work check NPJOHNSON's excellent article.
https://lineageos.org/engineering/Qualcomm-Firmware/
Thanks to YKS_Gaming for providing a copy of Persist for the Pixel 4XL.
I hope this helps someone else.
Click to expand...
Click to collapse
hello thnx for sharing
i had also missing files so merge them as you instructed from root explorer apk but when i restart all the files removed again and back to previous condition
pls help!
rooman1803 said:
hello thnx for sharing
i had also missing files so merge them as you instructed from root explorer apk but when i restart all the files removed again and back to previous condition
pls help!
Click to expand...
Click to collapse
i press on r/w but not mounted
how i can mount it as r/w
rooman1803 said:
i press on r/w but not mounted
how i can mount it as r/w
Click to expand...
Click to collapse
Are you still stuck?
Pixie 4 XL said:
Are you still stuck?
Click to expand...
Click to collapse
yup can you give me the backup of persist.img of 4xl i think restoring will fix it thnx in advance
Pixie 4 XL said:
I have lost all sensor calibration files and reg files for all sensors, screen, sound, rotate, brightness ect.
Can someone with a 4xl and a root explorer please go to /mnt/vendor/persist .
Please archive the directory in .tar or zip, twrp backup.
There have been a few requests on the 4XL forum for the files or for persist.img if you're able to /dd it.
I cannot find them for the Pixel 4XL anywhere.
I know which files to skip when replacing and have a backup, I take full responsibility.
Attach the file to a reply it's small enough when archived.
You would be helping me and others out, judging from search.
Thanks.
--------------------------------------------------------------------------------------------------------
EDIT: FIX
---------------------------------------------------------------------------------------------------------------
To clear up any confusion the symptoms are all sensors stop working not one or two.
The IMEI is not lost or changed with this method nor any MAC addresses on the "Google Pixel 4 XL".
I managed to fix all sensors failed with another users persist backup from a .zip file.
You should check the attachment file verses your current Persist, if you have all the files excluding the duplicate data folders don't even bother Instead start at the factory image install, relock boot loader stage.
Check it's not a software problem before doing this.
Get sensor toolbox.apk and check there is no data output from the sensors first.
If you are going to try this before you start back up all the files in /mnt/vendor/persist to a .tar file.
There is a camera certificate in camera directory that is unique to your camera module if you lose that you cannot use face unlock ever again. Same if you replace the hardware.
I had to manually restore all permissions because they were not in .tar format I've attached the fixed persist.tar.
I performed all operations from lineage 19.1 with magisk 25.1 full root and used mixplorer.apk root enabled.
Some steps may not be necessary.
Copy the files you need across from a root browser, if any duplicate files & folders are in there don't replace them merge and skip duplicate files instead.
There is a folder in the data directory named something like (DdHdVQd1FIOARksZgXG27GJ1A5UjYCGhP-ZoGvseqsY_)
I copied all files in each folder to all the others, so every folder had the same number of files in. (if they already exist then skip them.)
Install a stock factory image it should be a version below the latest OTA so A12 factory image- to A13 OTA. (I used A12 -coral-sq3a.220605.009.a1)
I then relocked the boot loader, disabled OEM unlocking, added an account to the phone on the phone setup dialogue and added a pin.
I let it update the apps made sure it was listed as my device in security settings and checked safety net all pass.
Tried face unlock(failed), started wallet setup then stopped at add card.
Rebooted a few times in between app updates then allowed the OTA to A13 install. (it was slow to finish install)
Then on first reboot it got into OS and said finishing setup let it finish then rebooted again and BishBashBosh all sensors functional.
It's might be titan security chip anti tamper or qualcomm chain of trust?
If you want to understand how this can be triggered with all files still intact and why replacing them won't instantly work check NPJOHNSON's excellent article.
https://lineageos.org/engineering/Qualcomm-Firmware/
Thanks to YKS_Gaming for providing a copy of Persist for the Pixel 4XL.
I hope this helps someone else.
Click to expand...
Click to collapse
I meet same problem, I cannt use fingerprint in Mi 12 Pro. Where to find persist img? I tried to install firmware but it can't. Please help me.

Question [CLOSED] Accidentally erased "Camera" folder and no way to try data recovery without Rooting. What should I do?

I posted a detailed description of the problem here:
How to recover accidentally erased Camera folder from Samsung S21 Ultra - Data Recovery Android 12 / Root?
Problem: My mum has an Android-based Samsung phone and unfortunately, when the main folder with photos ("Camera") was moved from the Phone to PC via USB cable, it was made using Cut and Paste. By accident the files were pasted into Recycle Bin...
forum.xda-developers.com
I understand I need to somehow root the phone / get access to deleted (hidden) folder with my deleted (hidden) photos WITHOUT wiping the data. Is this at all possible on this phone? What are my options?
even professional software was of no use, because no root access.
Please help!
samsungs21 said:
I posted a detailed description of the problem here:
Click to expand...
Click to collapse
@samsungs21 Thread closed as you've already created a subject matter related thread, which I've moved into this device forum.
Welcome to XDA by the way! I hope you'll always get the support you require. However, I suggest to read the XDA Forum Rules, to which you agreed to adhere when you registered a few hours ago, to currently focus on tule no. 5 and to post only ONCE! Thanks for your cooperation.
Regards
Oswald Boelcke
Senior Moderator

Categories

Resources