Database Info

[Q] task rpcrouter:15 blocked (CDMA)

Same as posted here "I have an HTC [differing: Touch Pro (Alltel CDMA)]. I followed the instruction on forum.xda-developers.com for [FRX*] but it [enters an endless loop] at "task rpcrouter:15 blocked for more than 120 sec". The solution that worked in that link does not solve the same problem with a CDMA RAPH800.
The solution given there (paraphrased from that thread):
Link to the fix. The issue is caused by not having a data plan; the install gets stuck in a loop looking for a signal.
The solution that worked for a GSM phone
download RIL file from http://forum.xda-developers.com/atta...9&d=1302817139 and place in the root of microsd.
download rootfs file from http://www.megaupload.com/?d=1NGCVCTT and place in the root of microso.
add to the end of /conf/froyo.user.conf file "/sdcard/libhtcgeneric-ril.so /lib/froyo/libhtcgeneric-ril.so" before the last "}"
Please help me find a solution for a CDMA phone - next month I'd like to take a dozen of these phones and use them as learning aids in a construction course for laborers, but I cannot start testing construction applications since I cannot get the OS to work.

I'm curious as to what happens when you format your microSD and run FRX7.1MR without anything additional. Could I get you to try this method without the additional stuff?
To be explicit, I'd like you to format your microSD with something other than the Windows method and I'd like you to download THIS (if you haven't already) and THIS. Extract the contents of both files to the root of your microSD. You should see a folder called "FRX07.1" and under that folder, you should see 3 folders and 7 files. Move the contents of that folder up to the root of the microSD. Look under the folder called "STARTUPS" and locate your device type (ie RAPH800) and copy over to the root of your microSD. Once done, run Haret on your phone and let me know what happens.

do you have an application you suggest for "format your microSD with something other than the Windows method"; sourceforge did not turn up anything.

forest.peterson said:
do you have an application you suggest for "format your microSD with something other than the Windows method"; sourceforge did not turn up anything.
Click to expand...
Click to collapse
use SDFormatter

wow that SDformatter link has a lot of popups - this link feels less like I just found a date at the bus-stop sdcard.org/downloads/formatter_3 ; but it will not install on either Server2008R2 x64 or Server2003 R2 SP2 x32.
I reformatted the microSd with the format tool in Server2008R2 as FAT format. Installed the files, and boom - I see little green guys swirling around the screen. After awhile a dialog appeared "Sorry! The process com.android.phone has stopped unexpectedly. Please try again"; the dialog closed and it seems like it works! Thank you. I will try again with the HPtool and as FAT32.
Now I just need to learn how to use Android - and the screen calibration seems off? Deleting ts-calibration and rebooting to calibrate.

Glad to hear using the latest bundle works for you! Yeah, that might be a slight issue with an outdated kernel. The main thing I wanted to do is get you booted up first!
Before we continue, make sure you make a backup of your current configuration by copying the contents of the microSD and either moving it to your computer or some other storage device. This way you know you have a "working" bundle.
Next we update the kernel package from HERE; might I suggest using THIS kernel package. Be sure to delete the old files (should be located under root of the microSD and called modules-xxx and zImage) first! Extract till you see two files then rename zImage-xxx to just zImage and feel free to delete the files you extracted from. I've always created my own ts-calibration file but just wanted you to have it, "just in case".
Additionally, you may also need to update the rootfs by deleting the file called rootfs and downloading THIS file. Extract the file and rename to just rootfs and be sure to place it where the file called Haret is (default location is root of the microSD).

files are downloaded and installed - everything seems to work

[Q] IMEI has gone after wipe

Hello, I have a jiayu G3T ( G3QCT ) with JB Android 4.2.1 installed , but yesterday it occurred to me to look for a custom rom 4.2.2 , I downloaded the rom, and follow the instructions ( wipe data / factory reset wipe cache && && wipe dalvik ) then install the new rom, everything seems to be right , but when the phone rebooted , I noticed that said " INVALID IMEI " and did not detect the SIM card ...
I have no backup of the IMEI ( if I have the sticker underneath the battery)
I reinstalled the rom I had before jiayu , which comes standard rooted ,I have tried uncle tools and the application of jiayu , I entered the engineer mode so I went to connectivity CDS information Radio information, phone 1 & 2 wrote 2 lines (one for each option )
AT + EGMR = 1.7, " IMEI "
AT + EGMR = 1.10 , " IMEI "
but when you click on send command says " command failed to send, even after pressing repeatedly says " command was mSent " but on reboot, nothing has changed, and the IMEI is still not valid .
I tried the mtkdroidtools but says it was all right , the result is the same, nothing changes
I also tested the MAUI META 3G & IMEI and SN WRITER but I have not gotten any results ...
Someone could tell me how to fix it? thanks

I'd suggest you re flash stock rom using SP Tools, then use SN Gen to create a MP0B_001 file. Then place the generated file on your SD card, use root explorer, copy the file you have placed on the SD card and move it to /data/nvram/md/NVRAM/NVD_IMEI/, and set the file's permission to rw-rw----.
Then reboot and enjoy.

stock rom
and where i cant get that stock rom? could you link it to me?

sn_gen
ViKtory36 said:
I'd suggest you re flash stock rom using SP Tools, then use SN Gen to create a MP0B_001 file. Then place the generated file on your SD card, use root explorer, copy the file you have placed on the SD card and move it to /data/nvram/md/NVRAM/NVD_IMEI/, and set the file's permission to rw-rw----.
Then reboot and enjoy.
Click to expand...
Click to collapse
the stock rom could be any of http://www.jiayu.es/software.php?soft&jiayu=G3QCT ?
I have used (4.2.1)ROM Oficial Jiayu.es 20131203-000001 (the latest) and sn_gen to recover my IMEI.... but after copy and set the permissions, and reboot, anything changes, what Im doing wrong?

tdguchi said:
the stock rom could be any of http://www.jiayu.es/software.php?soft&jiayu=G3QCT ?
I have used (4.2.1)ROM Oficial Jiayu.es 20131203-000001 (the latest) and sn_gen to recover my IMEI.... but after copy and set the permissions, and reboot, anything changes, what Im doing wrong?
Click to expand...
Click to collapse
I see that the website is in Spanish, so I may interpret the files incorrectly.
I'm gonna presume that you have already downloaded and installed the required MTK VCOM Drivers, and the device's drivers which are also given on the website. Install both if you haven't already.
I see there is a scatter loading file present under the downloads. Download the scatter loading and the latest ROM. Extract both the ROM files and the Scatter Loading file to a same single folder. Then use SPFlashtool and select the scatter loading file from the extracted folder, and check ALL the boxes.
Then remove the battery from your phone, connect the phone to the PC, and click "Download" on SP Flash Tool. After it finishes, you should see a box with a green circle, which indicates the flashing was successful.
After that, put the MP0B_001 file on your SD card, and follow the steps given by me on post #2.
And don't forget to hit thanks if I have helped. =]

tried.....but no working
ViKtory36 said:
I see that the website is in Spanish, so I may interpret the files incorrectly.
I'm gonna presume that you have already downloaded and installed the required MTK VCOM Drivers, and the device's drivers which are also given on the website. Install both if you haven't already.
I see there is a scatter loading file present under the downloads. Download the scatter loading and the latest ROM. Extract both the ROM files and the Scatter Loading file to a same single folder. Then use SPFlashtool and select the scatter loading file from the extracted folder, and check ALL the boxes.
Then remove the battery from your phone, connect the phone to the PC, and click "Download" on SP Flash Tool. After it finishes, you should see a box with a green circle, which indicates the flashing was successful.
After that, put the MP0B_001 file on your SD card, and follow the steps given by me on post #2.
And don't forget to hit thanks if I have helped. =]
Click to expand...
Click to collapse
Well... that is what I did... was unsucccessful... imei is till missing... i have contacted jiayu support.. they said me that some phone are not able to restore IMEI in a easy way..... the ask me 18€ ( $24) aswell they ask me to pay the Shipping rates... so they could try to fix it...

tdguchi said:
Well... that is what I did... was unsucccessful... imei is till missing... i have contacted jiayu support.. they said me that some phone are not able to restore IMEI in a easy way..... the ask me 18€ ( $24) aswell they ask me to pay the Shipping rates... so they could try to fix it...
Click to expand...
Click to collapse
They want to just rip money off you.. All MTK devices have only that one way of restoring device's IEMI which I have listed above., as far as I know.
You can try doing the following (This is just speculation, I have never tried this but it MAY work, as a MP0B_001 file and a backup generated by Mobileuncle MTK tools have the same output when opened via a text editor.)-
After generating an IEMI file, open it using Notepad. Then copy everything written in it, make a new notepad file and paste it there. Save that file as "IEMI.bak" file, and put that in your sd card.
Then install Mobileuncle MTK tools from Play Store, give it root access and go to IEMI backup/restore option. You should find your saved backup there. Hit restore from SD card, and pray that it works.
If it doesn't work, then I'm sorry. Send the phone over to your manufacturer if all else fails.

ViKtory36 said:
They want to just rip money off you.. All MTK devices have only that one way of restoring device's IEMI which I have listed above., as far as I know.
You can try doing the following (This is just speculation, I have never tried this but it MAY work, as a MP0B_001 file and a backup generated by Mobileuncle MTK tools have the same output when opened via a text editor.)-
After generating an IEMI file, open it using Notepad. Then copy everything written in it, make a new notepad file and paste it there. Save that file as "IEMI.bak" file, and put that in your sd card.
Then install Mobileuncle MTK tools from Play Store, give it root access and go to IEMI backup/restore option. You should find your saved backup there. Hit restore from SD card, and pray that it works.
If it doesn't work, then I'm sorry. Send the phone over to your manufacturer if all else fails.
Click to expand...
Click to collapse
well.... or Im not generaing a valid file... or it doesnt work.....:crying::crying::crying::crying::crying:

I did everything right but when I press "send AT Command" appear An error on my screen "failed to send AT command" what did I do wrong? what can I do to fix it?

How to create that MP0B_001 file ?
ViKtory36 said:
I'd suggest you re flash stock rom using SP Tools, then use SN Gen to create a MP0B_001 file. Then place the generated file on your SD card, use root explorer, copy the file you have placed on the SD card and move it to /data/nvram/md/NVRAM/NVD_IMEI/, and set the file's permission to rw-rw----.
Then reboot and enjoy.
Click to expand...
Click to collapse
How to create that MP0B_001 file please help!

[Q] Lost IMEI (NO SIM) - MTK MT6589M (Intex Aqua i-5)

Hello! I need some genius to find solution for my problem , my phone (Intex Aqua i-5) doesn't recognize any SIM Card and my IMEI is empty. The problem occurred when I flashed wrong recovery, somehow I got it working again by removing battery for 15 minutes, and holding power key for a minute before that, then flashed proper CWM recovery again via MobileUncle Tool., but now phone doesn't charge when its turned off, and doesn't recognize SIM. Everything else works fine.
This is IMPORTANT: Cant recover IMEI via PC (my usb port is broken (charging part is working but cant connect to PC, pins for data transfer are damaged). So IT'S NOT AN OPTION. But can transfer files from PC to Phone - Wifi transfer.
Need to recover IMEI trough phone! (there is numerous methods I've tried, gonna list them below)
- Engineer mode, - CDS info, Radio info, AT COMMAND - AT+EGMR=1,7,"1234567890XXX15" (tried variations with empty space before AT or before + , not working, gives me an error "AT command failed at sent ".
- Tried to generate original IMEI on the computer, write it to MP0B_001 file, transfer to phone, set permissions for it, transfer it to data/nvram/md/NVRAM/NVD_IMEI and replace file at destination with custom one (tried variations: all this but at the and making IMEI backup with MobileUncle Tools and restoring it, also tried different MP0B_001 generators, different permissions, tried deleting original file in NVD_IMEI folder first, then copying new one, etc). --- NO SUCCESS.
- Tried MTK65xx apk software for changing IMEI , NO SUCCESS. - got error msg: "pttycmd1 device NOT found!"
- Installing terminal emulator , writing for SIM 1 line of code: echo ‘AT+EGMR=1,7, “IMEI_NUMBER” ‘ >/dev/pttycmd1 and for SIM 2 this line: echo ‘AT+EGMR=1,10, “IMEI_NUMBER” ‘ >/dev/pttycmd1 - nothing happens , even after reboot..
I'm not allowed to post links for methods above, cause this is my first thread .
My phone is rooted, there is custom ROM on it. (MIUI V5 FOR INTEX AQUA I-5 ). And CWM recovery for this ROM.
Have backup of my STOCK ROM, but couldn't restore it via CWM, It is corrupted or something, but have original folders in it , NVRAM folder for example. (tried coping and flashing MP0B_001 from that folder to phone, but nothing).
Any other ideas guys?

Unless you find what file you need to overwrite. There is not much help any one can offer as editing the IMEI is illegal in many places so that the only approved way is restoring a backup with is hard to do in your case without a pc connection as those files will need to be flashed.

zelendel said:
Unless you find what file you need to overwrite. There is not much help any one can offer as editing the IMEI is illegal in many places so that the only approved way is restoring a backup with is hard to do in your case without a pc connection as those files will need to be flashed.
Click to expand...
Click to collapse
Thank you for your quick reply. I'm just looking the way to restore or flash my origina IMEI , which is written under my battery, or from my probably damaged backup. Pretty sure restoring original IMEI is not illegal and I'm aware that those files need to be flashed, but maybe someone knows how to flash it without usb connection, with CWM, MobileUncle etc..

ImYourMan said:
Thank you for your quick reply. I'm just looking the way to restore or flash my origina IMEI , which is written under my battery, or from my probably damaged backup. Pretty sure restoring original IMEI is not illegal and I'm aware that those files need to be flashed, but maybe someone knows how to flash it without usb connection, with CWM, MobileUncle etc..
Click to expand...
Click to collapse
It depends on the country and the laws. If you already know it needs to be flashed then all you have to do is get the files from the backup (hope it's not coruppted) and then make a zip to flash in recovery. There is not alot of development done with that chip set here so I am out of ideas.

Figured out why my nandorid backup cant be restored, and gives an error "error while flashing boot image". When I made a backup there was no boot.img file in it. (as you cant see below in log file) So I added a file from only stock rom found on the net (that stock Is not made for cwm and cant be flashed via cwm, just via SP Flash Too so I cannot use it). but my logic was that I can borrow missing boot.img and put it in my backup folder). So obviously its not solution.
Log file: (nandroid backup)
Backing up /boot...\c
02:18:25 Backing up /recovery...\c
02:18:25 Backing up /modem...\c
02:18:26 Backing up /system...\c
02:19:59 Backing up /data...\c
02:21:28 Backing up /cache...\c
02:21:30 Backing up /.android_secure...\c
02:21:34 Replacing old backup with new backup...\c
02:21:36 Generating md5sum...\c
02:22:04 Verifying md5sum...\c
02:22:05 Online Nandroid Backup Completed in 3 minutes 43 seconds!
###########################
But after this there is no boot.img at all in backed up files as you can see.
Files Backed-up:
"----rwxr-x 1 11264 Dec 8 02:21 cache.ext4.tar
----rwxr-x 1 530526720 Dec 8 02:21 data.ext4.tar
----rwxr-x 1 1024 Dec 8 02:18 modem.img
----rwxr-x 1 191 Dec 8 02:22 nandroid.md5
----rwxr-x 1 553781248 Dec 8 02:19 system.ext4.tar"
Why I dont have file boot.img in my backup and how can i fix it? :/
Someone said that I make another backup via cwm and keep just boot.img in it, then copy my old files in that new created folder , but i doubt it will work cause Im on custom ROM now (MIUI) and i want to restore stock (Andorid 4.2.1).
I started another thread here http://forum.xda-developers.com/general/help/stock-rom-intex-aqua-5-t3007603 in hope someone will upload stock ROM for my phone that is flashable with cwm.

BLU bricked, SPFlash Read yields encrypted contacts2.db, what next

I have a BLU phone that was my only source of contacts with no Google or backup (yes, I know). It was dropped a significant distance. It won't show any indication of charging or powering up, no lights or sounds. However when I plugged in the USB port I noticed the toggling of the USB driver install, typical for a MTK device so I decided to try to read from it with SPFlash tool.
To try to get at the contacts I downloaded a factory restore ROM and loaded the scatter file to see what location I needed to seek to find the user data for download. I first found userdata.img location from the factory scatter file and set up SPF under the ReadBack tab and used the Add button to specify a range beginning with and including the same numbers where the scatter file indicated the user data was, plus with SPF tool I stated I wanted the user data area read and saved as userdata.img. Now clicking on the read and then plugging the phone in with the read button pre-pushed, the SPF tool took off reading as soon as the dead phone USB was plugged in, operating just like I was flashing or writing to the phone. (Excitement was mounting.)
From here on my Windows machine I installed DiskInternals Linux Reader and mounted the userdata.img with that software and was able to navigate to the db file containing the contacts and the android call list located at
/data/data/com.android.providers.contacts/databases/contacts2.db.
Now the DiskInternals software allowed me to save the contacts2.db as a Windows file anywhere on the laptop but when I tried to open it with SQLite, it said the file is encrypted. I viewed the file using a Linux friendly editor (Context) and saw some names and numbers in readable text, but they were surrounded by tons of formatting and unprintable characters. (Looked something like a MS Word docx file.) I also tried the FireFox plugin for SQLite in addition to the SQLiteManager and the SQLite browser software. All of them said the file had a password that was needed to open it. (Exit excitement.)
Now it looks like my options are to either try to find someone or thing that can hack the password of the contacts2.db, locate the password perhaps hidden somewhere in a system.img that I can attempt to extract via the same method as I did the userdata, or I can try to assemble a working group of restore "parts" which include this userdata.img, adding it to some mix of the restore file and other IMG files I can possibly extract from the "bricked all but for flash tool" mostly dead phone. Theoretically, with such a reassembled package of IMG files I would then go look for an exact same model of this bricked phone and then try to load the new assembly of IMG files onto that good used phone.
I am open for suggestions of how to solve the puzzle. The objective is to get a list of readable contacts from the crashed phone and ideally get them exported into a format that can be input into another phone.
Thanks in advance.
P.S. Android 5.0 on the phone

Help RESTORING backup, "extractTarFork() process ended with ERROR: 255"

NOTE THIS IS NOT "UNABLE TO BACK UP" THIS IS "UNABLE TO RESTORE"
Lots of people on this forum, and lots of people on the internet have errors trying to back up because of this dreaded error 255. But, for me, the backup was fine, but now I can't restore. This is a huge problem because I just tried out a custom ROM (which turned out to be a huge fail), and I want to go back to stock.
So I switched back to the other slot (A/B ftw), wiped all data, formatted SD card, set up the OS to have the same lock pattern as the backup, transferred the backup onto the phone and tried to restore, and, well, fuck.
Code:
[RESTORE STARTED]
Restore folder: '/data/media/0/TWRP/2020-11-08--22-06-46 PRE-RR'
Skipping Digest check based on user setting.
Calculating restore details...
Restoring 4 partitions...
Total restore size is 11276MB
Restoring Vendor Image...
[Vendor Image done (3 seconds)]
Restoring Boot...
[Boot done (0 seconds)]
Wiping Data (excl. storage)
Wiping data without wiping /data/media ...
Done.
Restoring Data (excl. storage)...
extractTarFork() process ended with ERROR: 255
It failed, and there is absolutely nothing I can do about it. TWRP is using buggy commands to extract the backup and I don't know what's triggering the bug.
As a result, right now all my data is in limbo. TWRP cannot restore this backup as-is. I can't just go back in time and use `pm remove-user 999` or `pm remove-user 10` because the backup has already been created. Any solution that has to be done before the backup phase is inaccessible to me now.
My hope is that some smart person here can help me find a way to get this backup back onto the phone. Right now the internet does not have a solution to this problem, no matter how many naive users spam discussion boards with "pm remove-user 999 totally worked". Serious answers only.
Relevant section in the recovery log:
Code:
==> extracting: //data/vendor_de/10/ (mode 40771, directory)
Cannot find key for 10
error looking up proper e4crypt policy for '//data/vendor_de/10/' - 1DE10
tar_extract_file(): failed to extract //data/vendor_de/10/ !!!
I:Unable to extract tar archive '/data/media/0/TWRP/2020-11-08--22-06-46 PRE-RR/data.ext4.win000'
Error during restore process.
I:Error extracting '/data/media/0/TWRP/2020-11-08--22-06-46 PRE-RR/data.ext4.win000' in thread ID 0
I:Error extracting split archive.
Error during restore process.
pigz: write error code 32
pigz: abort: write error on <stdout>
extractTarFork() process ended with ERROR: 255
I suppose the solution is to make it "find a key for 10", but how? Do I just need to somehow recreate the 10 user before restoring the backup?

EDIT NOTICE: THIS DIDN'T WORK, DON'T MAKE IT WORSE BY TRYING
ORIGINAL POST IS BELOW
Alright. Well, I found a solution. That was quick.
The error is triggered by the backup containing a user that isn't present during the restore, I think. One solution is (theoretically) to create the missing user... another solution is to remove the missing user from the backup.
Turns out, backups are not so hard to modify, even in their compressed form. However, it is a little bit unintuitive at first.
You can't use the `tar` command to modify the backup, at all. TWRP's tar doesn't even support the --delete flag, nor does the BSD tar command (what ships with macOS). Even after installing GNU tar, it still refuses to work on a compressed archive (probably for the better).
You either need a Windows system with WinRAR/7zip (allows opening/modifying compressed files without extracting them), or a macOS/Linux system with FUSE and archivemount. If you're on Windows, you will have to manually search every single folder for 10 or 999 folders and delete every single one. If you're on macOS/Linux, the process is a bit more technical but also a bit more automated. And in both cases you will have to do this many times, and it can easily take half an hour or more and many restore attempts.
First and foremost, you need the recovery log to find out where the process failed. Every time it fails you will need to go to Advanced > Copy Log, copy them to the SD card, then use the flipping horrible Android File Transfer program to transfer the recovery.log to your PC, then use the cat/tail command or a text editor of your choice to read the log file.
Somewhere around the end of that file you will find something that looks like this:
Code:
==> extracting: //data/misc_de/10/ (mode 41771, directory)
Cannot find key for 10
error looking up proper e4crypt policy for '//data/misc_de/10/' - 1DE10
tar_extract_file(): failed to extract //data/misc_de/10/ !!!
I:Unable to extract tar archive '/data/media/0/TWRP/2020-11-08--22-06-46 PRE-RR/data.ext4.win003'
This contains all the info you need: the archive where the tar command gave up, and the file it gave up on.
Destroy that file with extreme prejudice.
Make a mount point with `mkdir mnt`, and mount the archive with `sudo archivemount data.ext4.win003 mnt`. (Of course, substitute data.ext4.win003 with the culprit archive file.)
If you're like me and have this problem with 10 folders, or 999 folders, you can find every single one of its kind with `sudo find mnt -name 10`. You can then use `sudo rm -rf` to delete every one of them. If you're brave, try `sudo find data -name 10 -exec sudo rm -rf \{\} \;`. I'm not responsible for any data losses incurred by using powerful commands that don't prompt you for confirmation.
Notice how I'm repeatedly using `sudo` for this: FUSE is kind of quirky and so is the kernel about multi-user filesystems. If you don't use sudo to mount the archive, then the user won't have permission to represent files it doesn't own, even if root is the one asking. You'll get weird "No such file or directory" errors for files and directories that are contained in parent directories' file listings. If you don't use sudo for the find or rm commands, you won't have permission to look inside folders or delete folders. Really, do everything with sudo because it's the only way to do this correctly.
Once you're done scrubbing the problem files away (be careful, do not use a file explorer of any kind, especially macOS's, which generally craps .DS_Store files all over your filesystem), unmount and save the archive with `sudo umount mnt`.
The next part is very important because recompressing files is not instant.
You will need to run `watch -n 1 du -hs data.ext4.win003` and WAIT.
Watch the file size slowly grow; only continue once it has stayed the exact same for at least one minute. Yes, it can definitely stop for 30 seconds at a time and then resume. You will need to give it time to recompress. It's also probably normal for the recompressed file to be about half the size of the initial file; that's just an artifact of TWRP not using very good compression to begin with. archivemount will create a backup of the archive with .orig appended, so you can try again if your backup ends up getting corrupted. (I just created an entirely separate copy of the backup to use archivemount on)
Of course, if you're on Windows you can skip all this and simply delete the problem file from WinRAR/7zip, and it'll be gone instantly and you can just proceed to copy the archive over to your device and retry the backup. You will have to do all the searching manually though, or perhaps you could try your luck with WSL. (Does WSL support FUSE?)
Expect this process to fail multiple times, but all at different points; whenever it fails at a different file, you know it got past the one you just removed. all you need to do is repeat this process over and over, slowly fixing your backup until it restores properly. This is what needs to be done if you can't reproduce the event that created that user in the first place. I'm sure if the user is important, it'll get created again.

Also, looks like user 10 is what happens when Google Play updates Device Personalization Services. Is this the generic "updates for system apps" user or is it specifically for that app?
EDIT: But updating that app doesn't create user 10. Interesting...
EDIT 2: User 10 is the guest user!! All I needed to do was create user 10 and that allowed me to restore my backup!
My post above is still good to see what I tried at first but it actually bricked my device until I factory reset it again, so :/

LoganDark said:
Also, looks like user 10 is what happens when Google Play updates Device Personalization Services. Is this the generic "updates for system apps" user or is it specifically for that app?
EDIT: But updating that app doesn't create user 10. Interesting...
EDIT 2: User 10 is the guest user!! All I needed to do was create user 10 and that allowed me to restore my backup!
My post above is still good to see what I tried at first but it actually bricked my device until I factory reset it again, so :/
Click to expand...
Click to collapse
Glad you managed to get your device back!
I had the same problem on another phone. The reason I got the error was because I tried to restore a decrypted backup on an encrypted device. After choosing the option "Format" in TWRP and typing 'yes' to confirm the decryption process, I was able to restore my backup.

Im having the same error in my realme xt...
sir..please help me.. I have a twrp backup of system image vendor image data boot recovery persist but im unable to recover because it shows an "error extract tar fork process ended up with error 255".during backup i had a pincode for screenlock.
i also have a backup of my internal storage in twrp but im not able to restore because of this error

LoganDark said:
Also, looks like user 10 is what happens when Google Play updates Device Personalization Services. Is this the generic "updates for system apps" user or is it specifically for that app?
EDIT: But updating that app doesn't create user 10. Interesting...
EDIT 2: User 10 is the guest user!! All I needed to do was create user 10 and that allowed me to restore my backup!
My post above is still good to see what I tried at first but it actually bricked my device until I factory reset it again, so :/
Click to expand...
Click to collapse
Hi. Did you create user 10 in Source, or in destination?
How did you do that in source?
If in destination, then is it possible to do it via TWRP?
EDIT: disregard. Mine user in the error path is 0 :-( '//data/system_de/0/'

just use option format data when entering wipe selection

erosman23 said:
just use option format data when entering wipe selection
Click to expand...
Click to collapse
doesnt work
redmi k20 davinci