Sensors files missing from Persist. Fixed - Google Pixel 4 XL Questions & Answers

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.

Related

All data intact even after factory reset (unable to perform full factory reset)

So, I installed PA 4.6 Beta 2 for locked bootloaders on my Xperia SP yesterday. To install the rom I performed all necessary wipes via recovery twice. Now there's this big problem. After I opened my gallery I noticed mutliple similar folders, after checking details of individual images and going to the directories mentioned in image details using root explorer I noticed the following -
1) storage/emulated/0 leads to the current internal storage directory being used by the PA rom
2) There's another 0 directory this directory i.e. storage/emulated/0/0 which contains empty DCIM/pictures/ringtones folders
3) Same as 2, storage/emulated/0/0/0
4) Finally going to storage/emulated/0/0/0/0 leads to the old interal storage which is used to be on the stock rom. All files are intact.
This is quite weird. Can someone please explain what's going on and how can I fix this? This never happened on nexus 4 after installing new roms.
EDIT- Nevermind. Fixed it myself. Although an explanation on why this is happening will be appreciated.

[Q] Questions regarding compressed recovery img and data on note 4

Hey Everyone,
I am new to XDA forums,(have used it for troubleshooting in the past but just registered today)
I am also new to android and linux, personally i don't use my phone for anything other than calls or games(i mostly do pc's), however my wife does a lot, she has written her own code, does mods, etc...., and we are both stumped. I am asking this on her behalf, due to a terminal illness she has lost the ability to do several things. On April 30th the lollipop update was pushed to her Note 4 (T-mobile US branded) and it wiped out all of her app data as well as her entire SD card. My question is in 2 parts one regarding the TWRP backup for this phone, and another regarding recovering the SD data from this phone(please let me know if i need to break this out into multiple sections of the site).
We have a TWRP backup that was compressed and loaded onto her cloud storage on 4/27/15, and we are unable to figure out how to get TWRP to recognize it without giving an error about the binary code or just not working period. Here is what we have tried(On advice not just from other XDA posts but various android forums as well)
Using TWRP(7zip for unpacking and repacking)
1. Downloaded the TWRP back up into windows
2. Renamed all files of the back up to be .tar, with the exception of boot which was converted to .img
3. Added Meta-Inf file from what was suppose to be stock ROM( she was not running a custom on this phone)
4. Re-archived everything back into Zip and sideloaded.
result : Error in binary code
Using Odin
1. Converted recovery (file only from backup) to md5 using Cygwin
2. Flashed using Odin
Result: Gained back a few programs but no app data or text histories
We have also tried varying versions of this, i.e. converting extra files or renaming extra files and receive the same issue. I am wondering if it is just an issue with the cloud stored compressed backup(or more likely i dont know what im doing)?
Second question comes from above, I was able to recovery all of the data from the SD card(everything was stored here, app data, recovery files, imgs, everything). When recovering the data it split everything up so all the sub peices of each recovery file are spread out is there a way to combine the individual file parts that were recovered from the SD card into functional android files again?
As i mentioned before i have never really dealt with this type of thing before but i want to try and fix this for her as between the 2 issues she has lost 5 years of data.
Thank you so much for your responses.
Hi, what you need to do is put the backup back into the exact same form it was before, an uncompressed, unzipped folder, then put it into the exact directory where TWRP puts backups when it makes them, and then in TWRP choose the option to restore. If you put the backup in the correct directory, TWRP will see it and allow you to choose it to restore it. Basically you just wanna put the backup back where it was before and then restore it in TWRP.
I wasn't sure if you had done this or not. If you have the backup folder with all the contents in their original form, it should work. I've even moved a backup from one phone onto another phone, exact same model of course, and then restored that backup onto the new phone!
I've never converted a backup into another form to be flashed another way, like Odin or as a zip in TWRP. Although I guess it could be possible it seems like it could be pretty messy.
Also if the TWRP backup was for a kit at build it will not restore on the lollipop baseband. You will need to Odin back to the kitkat NK4 build them you should be able to take the data.
Sent from my SM-N910T using XDA Free mobile app
ShrekOpher said:
Also if the TWRP backup was for a kit at build it will not restore on the lollipop baseband. You will need to Odin back to the kitkat NK4 build them you should be able to take the data.
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
YrrchSebor said:
Hi, what you need to do is put the backup back into the exact same form it was before, an uncompressed, unzipped folder, then put it into the exact directory where TWRP puts backups when it makes them, and then in TWRP choose the option to restore. If you put the backup in the correct directory, TWRP will see it and allow you to choose it to restore it. Basically you just wanna put the backup back where it was before and then restore it in TWRP.
I wasn't sure if you had done this or not. If you have the backup folder with all the contents in their original form, it should work. I've even moved a backup from one phone onto another phone, exact same model of course, and then restored that backup onto the new phone!
I've never converted a backup into another form to be flashed another way, like Odin or as a zip in TWRP. Although I guess it could be possible it seems like it could be pretty messy.
Click to expand...
Click to collapse
Thank you both for the suggestions i will give them a try shortly and i will provide an update on how things go.
Yeah, if you put the backup folder in the right directory, which is either internal or external sdxard/TWRP/BACKUPS/serial #/, you could restore just the data at least and it ought to be mostly ok. You ,might need to clear data in an app here or there if they force close.... or if it's too much then yeah, Odin back to KitKat and restore the desired components of the backup.
YrrchSebor said:
Yeah, if you put the backup folder in the right directory, which is either internal or external sdxard/TWRP/BACKUPS/serial #/, you could restore just the data at least and it ought to be mostly ok. You ,might need to clear data in an app here or there if they force close.... or if it's too much then yeah, Odin back to KitKat and restore the desired components of the backup.
Click to expand...
Click to collapse
Thank you for this, i double checked we had it in the right directory, but it still failed. At first it said something about a missing md5, but i tried again and i was able to get the log for the failure though. (attached below)
Hmm, I looked at the logs trying to make sure you chose to Restore in TWRP and not Install. If so it's possible the backup could have gotten altered or corrupted in the transferring back and forth. If you get it intact as it was, it SHOULD work, but I'm but sure what else to do at the moment. I hope you get it working
Sorry for the delay
Hey Everyone,
Sorry for the delay its been a long week, bad thing after bad thing kept happening. I was able to try your suggestions and i put together some additional information in hope this might help us try and figure it out.
*I must figure out how to recover, texts, contacts, call locks. My default texting app was google messenger.
So I figured I would start with the phone
I am using a Samsung SM-910T on 4.4.4 (build *ANK4) It was pretty Vanilla -> rooted, but running the stock ROM
1. The phone was set to do a full internal backup nightly using the online nandroid backup (by H3r3T1L)
2. Backups were set to be in TWRP backup format and to save to an external SD card, then to compress before being uploaded to google drive
3. Backups were set to delete from SD card after the upload was finished.
What happened
1. When stock 5.0.1 firmware OTA came out i was trying to dismiss the notification but apparently hit "accept" by mistake, causing the system to crash.
2. While restoring the phone, i attempted to download the most recent backup from the google drive and flash the zip to restore my data.
3. This Zip would not install, and i noticed all of the backups uploaded had the same anomally-a few of the files were 0 bytes
4. I downgraded the phone to ANK4 based on the above recommendation but it has made no difference.
5. I still get updated binary error and each time i flash the zip, my OS gets wiped.
6. I have tried instructions to just unzip and flash , to put zips in twrp backup folder, to build new file with meta-inf, etc. and nothing seems to work.
When the SD card got deleted I was able to retrieve some data from the deleted SD card, but don't know where the text messages are located or how to combine them back into a usable format. Or at the very least be able to extract the SMS/MMS history.
I hope this extra information helps. In any way im am desperate to try and fix this for my wife.
I believe you can use Titanium Backup to extract files from a TWRP image. If you can't extract anything from the backup it's either corrupted, in the wrong place, or in the wrong form - that is due to the compression decompression not being compatible (all zip programs are not equal). Best of luck.
BTW, you must restore TWRP files not install them.
Sent from my SM-N910T using XDA Free mobile app

Help.. phone bricked, deleted /carrier applications

I was trying to cleanup carrier bloatware off my phone and I think I deleted some apps that were critical.
I deleted ItsOnService.apk (NetworkSystemProvider) and ItsOnUID.apk. Unfortunately I didn't make a backup of them. Then, wifi and LTE/3g stopped working (even if Wifi is connected, internet is permanently not available).
The worst part of this is that the issue persists after reflashing back to stock. The problem is I don't think the stock roms contain the /carrier directory. And now I cannot complete the setup wizard because at first boot, I'm forced to select a wifi network and once I connect internet is not available, so the wizard won't proceed.
Is there anything I can do? If someone were to send me the missing APKs could I use recovery mode and sideload them?
Chanman said:
I was trying to cleanup carrier bloatware off my phone and I think I deleted some apps that were critical.
I deleted ItsOnService.apk (NetworkSystemProvider) and ItsOnUID.apk. Unfortunately I didn't make a backup of them. Then, wifi and LTE/3g stopped working (even if Wifi is connected, internet is permanently not available).
The worst part of this is that the issue persists after reflashing back to stock. The problem is I don't think the stock roms contain the /carrier directory. And now I cannot complete the setup wizard because at first boot, I'm forced to select a wifi network and once I connect internet is not available, so the wizard won't proceed.
Is there anything I can do? If someone were to send me the missing APKs could I use recovery mode and sideload them?
Click to expand...
Click to collapse
do you still have the rooted system image on ur sdcard?? just reroot
Google~Android said:
do you still have the rooted system image on ur sdcard?? just reroot
Click to expand...
Click to collapse
I do have the rooted image, as well as the stock image, I have applied both, the problem still exists. I think when I reroot or reflash it's not writing the /carrier directory, that must have come from somewhere else. I confirmed this by unpacking the TOT file and looking inside, it has all the apps, but it does not have the /carrier directory. Do you have ItsOnService.apk and ItsOnUID.apk? Maybe I could try sideloading them?
Chanman said:
I do have the rooted image, as well as the stock image, I have applied both, the problem still exists. I think when I reroot or reflash it's not writing the /carrier directory, that must have come from somewhere else. I confirmed this by unpacking the TOT file and looking inside, it has all the apps, but it does not have the /carrier directory. Do you have ItsOnService.apk and ItsOnUID.apk? Maybe I could try sideloading them?
Click to expand...
Click to collapse
nope i don't have a g4 as of now...shud be here in a week
Chanman said:
I was trying to cleanup carrier bloatware off my phone and I think I deleted some apps that were critical.
I deleted ItsOnService.apk (NetworkSystemProvider) and ItsOnUID.apk. Unfortunately I didn't make a backup of them. Then, wifi and LTE/3g stopped working (even if Wifi is connected, internet is permanently not available).
The worst part of this is that the issue persists after reflashing back to stock. The problem is I don't think the stock roms contain the /carrier directory. And now I cannot complete the setup wizard because at first boot, I'm forced to select a wifi network and once I connect internet is not available, so the wizard won't proceed.
Is there anything I can do? If someone were to send me the missing APKs could I use recovery mode and sideload them?
Click to expand...
Click to collapse
You need to know exactly what you deleted. The itsonuid is in the system/priv-app directory. I didn't see the itsonservice but didn't spend much time looking. You need to know if you deleted things out of carrier partition or vendor partition or both... Get a list together...
Agimax said:
You need to know exactly what you deleted. The itsonuid is in the system/priv-app directory. I didn't see the itsonservice but didn't spend much time looking. You need to know if you deleted things out of carrier partition or vendor partition or both... Get a list together...
Click to expand...
Click to collapse
Thanks, I can confirm what you're saying, I did find ItsOnUID in system/priv-app, so at least I can restore that one. However, I am pretty sure ItsOnService is in /carrier and I deleted it using ES File Explorer. I had deleted ItsOnUID with Titanium Backup. Titanium Backup was not able to find ItsOnService, so that's why I had used ES File Explorer, which confirms that ItsOnService must have been in /carrier.
Since it looks like there is no /carrier directory in these TOT files, is there some other way I can get ItsOnService.apk? Can anyone out there send it to me?
Chanman said:
Thanks, I can confirm what you're saying, I did find ItsOnUID in system/priv-app, so at least I can restore that one. However, I am pretty sure ItsOnService is in /carrier and I deleted it using ES File Explorer. I had deleted ItsOnUID with Titanium Backup. Titanium Backup was not able to find ItsOnService, so that's why I had used ES File Explorer, which confirms that ItsOnService must have been in /carrier.
Since it looks like there is no /carrier directory in these TOT files, is there some other way I can get ItsOnService.apk? Can anyone out there send it to me?
Click to expand...
Click to collapse
Might be a little late but here ya go.
2348z said:
Might be a little late but here ya go.
Click to expand...
Click to collapse
Thanks a lot!!!
Chanman said:
Thanks a lot!!!
Click to expand...
Click to collapse
No problem buddy. ?

custom Rom or change of 4.4.2.Retail.EU

Hello,
I'm a beginner lost in reading all the useful information on this forum.
I started with the idea to reduce the permissions of applications of my Razr I.
Google pointed to this http://www.xda-developers.com/protecting-your-privacy-app-ops-privacy-guard-and-xprivacy/
And I'm really happy and surprised about all information I can find here, thank you that much for
making this possible to all of you!
As today I feel ready to start playing around with my phone I wanted to ensure I understood the items right.
May be for you it takes only some seconds to verify my guess and can give a short notice
about Step 2 or 3 is easier to become implemented.
Step 1.) I wanted to do a full backup before I start, following this thread:
So I'll install ADB on my PC and run "adb backup -f FullBackup.ab -apk -all"
This works on a Razr I with 990.43.74.xt890.Retail.en.EU - of the shelf and is not risky at all - or?
Could you pls. tell whether it is really true I can switch back to my backup if I'm not happy with my System?
Step 2.) My first intention was to root my device and install Xposed framework
http://forum.xda-developers.com/showthread.php?t=2299428
http://repo.xposed.info/module/de.robv.android.xposed.installer
And to use Permission Master out from google play store
First of all I wanted to ask you whether this is feasible technicaly and esp. for a beginner?
Alternative to Step 2 Step 3?
Step 3.) In general I'm happy with my Razr I Android 4.4.2 (990.43.74.xt890.Retail.en.EU)
But I'm wondering whether it would be easier or has less risk to use a custom ROM instead of implementing Step 2.
By reading in this forum I found out there is a planty of features FM-Radio, enhanced stand-by current ,
to get rid of preinstalled aps and so on.
I'm an embedded developer but do not have the overview about the architecture of Android devices, what I got so far is:
There is a bootloader which needs to be changed from OEM closed to open.
There is a boot partition I flash ROMs in.
I need some tools on my PC combined with SDK and Motorola drivers to allow a USB-Debuging and flashing.
And sure as always once your bootloader is damaged you are lost, so I understand even backup will not help here.
So I'll keep my fingers crossed.
Thanking you in anticipation and pls accept my excuses about my english and stupid beginners questions.
Best Regards
gonso
PS:
As I main entry point I used the
http://forum.xda-developers.com/razr-i/general/index-razr-t2832722
from there I'll try to get ADB, drivers etc.
Hi GonsoXDA,
Step 1: I have never used it. Didn't even know that it existed. On the internet there are numerous people who uses it and it seems to work. Maybe someone else can give some info about this or just try it. U can try it with a non-important app and see if it works. Just backup it, delete it and restore it.
Step 2: This works just fine. But do know 3 things:
1. First root: To get root on stock rom, u need to use kingsdroot methode afaik. And that one sends your IMEI to some rare ip adress. I personnaly don't trust this and stay away from it, but there are many people who use it.
2. Xposed requires a recovery to install the framework. It can be done mannually or by the app i suppose. With only root u don't have a recovery on your device that can perform such action.
3. If something goes wrong only a full restore with RSD-Lite can most of the time help u out. Because u don't have a recovery that works than.
Step 3: We only have 2 full roms. 1 for JB (stock) and a working CM11 rom (kitkat).
Only the Jellybean roms support fm-radio, on every newer rom fm-radio is cut out of the audio firmwares. The risk of going to this is even less as Step 2, because u can do a full backup and restore of ur phone. ( I would chose for this if u want to play a bit with the phone and ur warranty is already out of years)
The gereneral idea about the android architecture is this (it is different for almost every device and the Razr I has many more thing to hold into account, but if u are here only for the roms and xposed, there is no more to know):
Bootloader: Is like an uefi bios for PC, but then for android. It also contains fastboot
Bootimage(boot): Has all the info like kernel and ramdisk to boot the system
Recovery: Is like 'boot', but boots into the recovery partition that lets u change every aspect of the device if u know how. Its mainly used to flash a custom recovery to, backup and restore a nandroid backup and flash/wipe roms, mods, (all/specific) data and packages.
Systempartition: Is the system the boot boots into. It's android.
Datapartition: Where all the user data is stored.
Cachepartition(dalvik): Where all cache is stored and in earlier android versions also dalvik. But not now anymore.
Fastboot: To flash/wipe the above partitions and many more (needs drivers)
Adb: To push, pull, command things in system or recovery (needs drivers)
Sdk: contain the abd and fastboot packages, but aren't needed for adb and fastboot because with the right drivers can work on there own (see the internet)
If u have a custom recovery and only change things on the system, data and cache partition there is almost no way to damage the phone. There is always a backup through recovery. As long as u stick to the things u can do in recovery.
The only thing tha can mesh up your phone beyond repair is doing wrong stuff withint the bootloader and other inner parts in the phone(like i did to get newer kernel working) or u are in bad luck and you internal memory blocks. See 'Super brick samsung phones' (emmc error).
I suggest:
- Unlock your bootloader
- Install custom recovery
- Make a backup with the recovery
- Do what u want, xposed on stock rom, try CM11?
- If things won't boot, restore through recovery
And always, read up before doing anything. There are thousands of articles about android, flashing things, repairing android, using adb and fastboot. AND ALWAYS HAVE A BACKUP PLAN!
Hello,
always having a backup seems not to be that easy.
So I unlocked my boot loader and tried to install twrp2850 and twrp2860 via mfastboot.
The mfastboot with 533.353kB caused the following "(bootloader) Variable not supported!"
I rebooted into bootloader and tried recovery -> horizontal Android man with a red !-rectangle
After reboot to normal power up my phone seems to be in factory reset, all my data is gone :crying:
ok crying dosn't help so I looked around and tried with another mfastboot 186.178kB and recoverycwm6.0.5.1.4.img.zip
http://forum.xda-developers.com/showthread.php?t=2441224
The twrp I tooked from here: http://forum.xda-developers.com/showthread.php?t=2278483 seems not to work.
I did a backup with cwm is there a change to get back my data? I think I know the answer.
In the meanwhile I installed
http://forum.xda-developers.com/razr-i/development/rom-unofficial-cyanogenmod-11-t2966855
And will try to install
http://forum.xda-developers.com/xposed/modules/tool-installer-xposed-installer-zenfones-t2983589
Thank you for the help, work and excuse the stupid beginner posts.
Regards
gonso
gonsoXDA said:
Hello,
always having a backup seems not to be that easy.
So I unlocked my boot loader and tried to install twrp2850 and twrp2860 via mfastboot.
The mfastboot with 533.353kB caused the following "(bootloader) Variable not supported!"
I rebooted into bootloader and tried recovery -> horizontal Android man with a red !-rectangle
After reboot to normal power up my phone seems to be in factory reset, all my data is gone :crying:
ok crying dosn't help so I looked around and tried with another mfastboot 186.178kB and recoverycwm6.0.5.1.4.img.zip
http://forum.xda-developers.com/showthread.php?t=2441224
The twrp I tooked from here: http://forum.xda-developers.com/showthread.php?t=2278483 seems not to work.
I did a backup with cwm is there a change to get back my data? I think I know the answer.
In the meanwhile I installed
http://forum.xda-developers.com/razr-i/development/rom-unofficial-cyanogenmod-11-t2966855
And will try to install
http://forum.xda-developers.com/xposed/modules/tool-installer-xposed-installer-zenfones-t2983589
Thank you for the help, work and excuse the stupid beginner posts.
Regards
gonso
Click to expand...
Click to collapse
Than u know the answer, it is no I think.
Both twrp images should work just fine, but always chose the latest. The message "(bootloader) Variable not supported!" doesn't do anything So don't worry about that one. There should be a lot more in you log that the message if twrp didn't install. U did extract it and flash it with the command: mFastboot flash recovery <recovery-image>. Where <recovery-image> could be C:/users/*/Downloads/recovery.img.
Hello,
yes sure "The secret of health for both mind and body is not to mourn for the past, worry about the future"
So I use CM11 now for about 2 days and I'm really impressed, so far everything works :good: THANK YOU!!!
As I asked already I installed XPosed and Permission Manager, but I found XPrivacy might be the better solution and switched to this.
(Today I do not have all the technical background to judge whether it is technically equivalent, but I'll investigate on it)
Esp. one thing I'm wondering, why XPrivacy is reading my Contacts once I check the permissions of an app?
But the more important thing I recognized differences between CM11 and the Stock ROM. One is the Entry
"Privacy" in the settings. It seems to be more or less the XPosed and XPrivacy, or?
But it seems the Restrictions are not shared, so I can restrict in the one and do not see the restriction in the other tool.
So first is there a risk to use both, is it useful or just doing the same twice.
Thank you
Gonso
gonsoXDA said:
Hello,
yes sure "The secret of health for both mind and body is not to mourn for the past, worry about the future"
So I use CM11 now for about 2 days and I'm really impressed, so far everything works :good: THANK YOU!!!
As I asked already I installed XPosed and Permission Manager, but I found XPrivacy might be the better solution and switched to this.
(Today I do not have all the technical background to judge whether it is technically equivalent, but I'll investigate on it)
Esp. one thing I'm wondering, why XPrivacy is reading my Contacts once I check the permissions of an app?
But the more important thing I recognized differences between CM11 and the Stock ROM. One is the Entry
"Privacy" in the settings. It seems to be more or less the XPosed and XPrivacy, or?
But it seems the Restrictions are not shared, so I can restrict in the one and do not see the restriction in the other tool.
So first is there a risk to use both, is it useful or just doing the same twice.
Thank you
Gonso
Click to expand...
Click to collapse
That's a sentence.
Why XPrivacy needs it i don't have a clue. For that sort of things u need to be by the dev of the app.
CM has a lot of features out of the box compared to stock, but stock is most of the time a bit more optimized in terms of proprietary stuff like camera.
So as u noticed, CM had an inbuilt security app. This app (CM) and XPrivacy don't share there settings, so that's the difference u see. But most likely if u disable something in one of the apps it is disabled even tho the other doesn't say it because it doesn't know of it.
I don't think it will be a risk. They both do the same thing, but they don't know about it. To be on the safe side, just use one and restore the other to default. U can always search on the web if they don't get along.
U can now make a full backup, so everything can be reverted and your data should be relative safe.
Hello,
thank you again - I now find the answer by reading in the development part of the forum. For me as a beginner it is sometimes not easy to interpret the discussions there.
If accepted I will use the thread now as a kind of diary, may be some other users will have similar destinations and my learn from my mistakes.
So to answer my question a little more detailed, but with less background know how than Hazou. Pls. do not trust me I'm a beginner, I have not analyzed the code just the behavior - feel free to correct or contradict my words!
The XPosed is in the area of permissions just a framework which allow other modules to put some code between an app requesting permissions and the Android core granting this permissions. The Xposed it self doesn't handle settings or permissions you did in modules like the CM Privacy, Permission Manager or XPrivacy.
As a result I came to the same conclusion it is not a risk, but an overhead to have more than one pice of code between the app requesting permissions and the Android core. -> My proposal: Do not use more than one of this Permission control apps in parallel.
From the privacy perspective the Permission is just a starting point, it allows you to hide your private information from the app. On the other side many apps will need access to the data to work and most of them are able to connect to the internet.
So I realized the next step would be the restriction of internet usage of apps. Here permissions are sword but we need a scalpel, to separate the necessary from the unwanted connections. This scalpel could be AFWall+ and "Netzwerk Log", this is a firewall and a sniffer.
What I can say to day the apps run on CM11 installed on my Razr I.
So it looks like I see my destination raising on the horizon and I will try to formulate it in the following order:
1.) Hide Contacts, Calls and SMS from Apps who do not need this to work -> XPrivacy
2.) Disable some Android features I think I don't need.
(e.g. Captive Portal Check - settings put global captive_portal_detection_enabled 0)
3.) Restrict the internet access of some apps to servers they need to connect. ( e.g. E-Mail client is restricted to connect to the mail server)
4.) Limit the access to my pictures, stored on SD card. [I have not found a solution so far]
If you read this I think 1 is reasonable for most of you, even if you do not have deep Android or Network know how (as I have), you just restrict the permissions - if app crashes or doesn't do the job you expect you may permit access or uninstall the app. (XPrivacy allows you also to fake data)
3 is a usual task of a network administrator, if you are used with iptables it is just work. I'll try to find out whether there is somewhere a source of "Templates". Usually the network admins share there common settings based on services, once I find out I'll post.
To restrict the access to SD Card I only see the change to extend the sandbox of Android to the SD and to hide files which does not belong to the app. As I would store my pictures on SD as I would store my Navi Data, but neither the Navi app should see my pictures nor the Cam and Gallery my Navi Data. ...
I don't know whether there is an app out there but It should be possible the same way like XPrivacy fakes the other data.
Thank you
Gonso
Hello,
Most of the time I used the numbers to just put in the extension, so if I want to call 0049 9876 54 321 I put the numbers 321 the Motorola dialer will show a list of all contacts where the number contains 321.
Some Numbers of contacts are not shown as well, seems if a contact has more numbers only one or two are shown.
The CM11 dialer doesn't show the number, is there a setting to get this feature?
I tried to get my Stock dialer back, so I copied dialer.apk from stock into the /system/sec-app/ directory of the CM11 and restarted the phone -> doesn't change the dialer ....
Any proposals? I'm terrible sorry for my stupid questions, I read several threads and still no idea about a possible solution
Gonso
PS: CM11 file manager shows a secure storage /storage/emulated/0/storage/secure - what is the algorithm used for the encryption.
gonsoXDA said:
Hello,
Most of the time I used the numbers to just put in the extension, so if I want to call 0049 9876 54 321 I put the numbers 321 the Motorola dialer will show a list of all contacts where the number contains 321.
Some Numbers of contacts are not shown as well, seems if a contact has more numbers only one or two are shown.
The CM11 dialer doesn't show the number, is there a setting to get this feature?
I tried to get my Stock dialer back, so I copied dialer.apk from stock into the /system/sec-app/ directory of the CM11 and restarted the phone -> doesn't change the dialer ....
Any proposals? I'm terrible sorry for my stupid questions, I read several threads and still no idea about a possible solution
Gonso
PS: CM11 file manager shows a secure storage /storage/emulated/0/storage/secure - what is the algorithm used for the encryption.
Click to expand...
Click to collapse
Stock CM dialer doesn't have that function afaik. The moto one doesn't work because it needs the Moto framework to work. Just download a dialer U trust from the playstore.
I don't have any clue about the secure storage, sorry.

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?

Categories

Resources