I backed up the OOS 9.0.5 Android Pie via TWRP 3.3.1, but I failed to restore it, about 10% of recovery process, extractTarFork() process ended with ERROR: 255 prompted out. I have searched for possible solutions but in vain, I already wiped the system before restoring, so there wasn't any user 999 exists. Any idea to fix the recovery issue?
mkcs said:
I backed up the OOS 9.0.5 Android Pie via TWRP 3.3.1, but I failed to restore it, about 10% of recovery process, extractTarFork() process ended with ERROR: 255 prompted out. I have searched for possible solutions but in vain, I already wiped the system before restoring, so there wasn't any user 999 exists. Any idea to fix the recovery issue?
Click to expand...
Click to collapse
Don't double post. Answered in your q&a post.
Sent from my OnePlus 3T using XDA Labs
mkcs said:
I backed up the OOS 9.0.5 Android Pie via TWRP 3.3.1, but I failed to restore it, about 10% of recovery process, extractTarFork() process ended with ERROR: 255 prompted out. I have searched for possible solutions but in vain, I already wiped the system before restoring, so there wasn't any user 999 exists. Any idea to fix the recovery issue?
Click to expand...
Click to collapse
THREAD CLOSED as duplicate of https://forum.xda-developers.com/oneplus-3t/help/twrp-restore-extracttarfork-process-t3986011
Despite of closure moved to Q&A as the thread doesn't belong into "Guides etc."!
XDA Forum Rules (excerpt):
...
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.
...
15. Keep threads / posts on-topic
Whilst a minor amount of off-topic posting may be overlooked, the general rule is that your posts / threads must be relevant to the Forum / thread in which you are posting.
General Forums - For news and announcements relating to your device.
Q&A Help & Troubleshooting Forums - For all question / request threads and posts. If there is no Q&A Help & Troubleshooting forum, use the General Forum of the relevant device
Accessories Forum - For posts related to accessories relevant to the device
Development Forums (ones with the word development in the title) - For Developers to post release threads e.g. ROMs and Kernels including modifications to kernels, bootloaders, ROMs, etc., as well as R&D development discussion threads designed with an end goal
Themes and Apps Forums - For the posting of Themes and / or Apps as well as announcements & discussions including modifications made to Themes and Apps.
...
Click to expand...
Click to collapse
Related
The forum doesn't allow me to post on that thread. and it doesn't allow me to send private message. I am getting very frustrated!
Below is my original message. Anybody please kindly forward it to the page. I am hoping it is useful for the devs.
http://forum.xda-developers.com/showthread.php?t=2542793
Thanks
.-------.----
Hi Cars,
I can't post to the thread (the forum doesn't welcome new users?).
Some fiddling suggests to look at the the block device IO / ext filesystem.
With CM11 0106(yours and the one on the first post) and 0105, I experience a lot of reboots / random FCs(like many others reported).
logcat records exceptions for writing files for FC'ed processes. Turns out /data is mounted ro.
In dmesg, I see a lot of block IO errors ( can't find superbloocks etc) in dmesg. /data is remounted io after these IO errors.
The hardware seems to be OK. I checked the devide (/dev/block/mmc0blk0p17) with dd, zeroing the entire partition / read out the entire partition to /dev/null in adb recovery (.5 version not the latest .6). no IO errors is reported durng these full-partition tests. Also no IO error with 10.1 (latest on your all cm thread, the one from last december).
Strongly pointing to block device/flash IO module. The difference in the kernel between recovery and the kernel in CM11 0106(all versions) or even maybe just the difference between 0106 and last reported working build(1225? I didn't test it) may help us to pin it down. What changes were in the upstream cm source between these dates?
Thanks for working on these roms!
Yu
Thanks for the info, I will forward your message. I remember having some helpful things to post and being frustrated by the 10 post requirement.
http://webchat.freenode.net/?channels=ancora_tmo
Q&A for [ROM][4.4.4][22-Oct] [Spirit ROM v1.5] [VS980]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][4.4.4][22-Oct] [Spirit ROM v1.5] [VS980]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
The rom keeps rebooting occasionally when i hit the voice text button, using stock messaging habemt tried others. Happens about 1 in 10 times. Anybody else getting this?
Reply to Murphy71984 2-3 second delay after pressing power button
I am trying to post a reply to Murphy71984 question, but I have not made enough posts yet. Please move to the correct post, thanks.
Murphy71984: Love this ROM, only problem I'm having is turning the screen on. It always takes a good 2-3 seconds after pressing the power button, anyone else getting this?
I am also having the delay with the power button and knock on (double tap to wake). I have conducted several tests to try and isolate the problem. What I found out was while using the Tasker app in a combination that bypassed the lock screen (keyguard off in Tasker or Secure Settings app), I would get a delay of 2-3 seconds (regardless of the lock screen type, slide, face, pin...). Once I disabled the keyguard off setting, the phone would respond immediately without delay, using both the power button or knock on.
The first thing I tried was Lawlrus suggestion to use Art vs Dalvik. I switched to Art but still had the same delay. Using Art, the phone seems to respond faster to some things, but did not affect the wake delay. I followed that up with a series of tests changing the lock screen type and keyguard on/off in Tasker and Secure Settings. The keyguard setting was the problem with my phone. I was using the keyguard disable feature as a convenience while using certain bluetooth devices. Hopefully this info can help you isolate your problem.
---------- Post added at 12:48 PM ---------- Previous post was at 12:16 PM ----------
Awesome ROM, thanks for all your hard work. Congrats on your engagement too!
1.5 is working great for me on 26A bootstack. Tethering working without modifying settings and shows connected devices. Heads up includes simple directions to get it working (probably worked fine before, I just didn't know how to properly enable it). GPS working without replacing the GPS.conf file or additional software.
Thanks again!
I cant flash it!
I was trying to flash this Rom with TWRP but it gave me this error:
ApplyParsedPerms: removexattr of /system/etc/install-cm-recovery.sh to 0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/sdcard/Download/SpiritRomv1.5-vs980.zip'
Error flashing zip '/sdcard/Download/SpiritRomv1.5-vs980.zip'
I dont know what it means, please help!!
Lollipop and Spirit ROM?
Any chance we see a 5.0.1 version of Spirit or should i look elsewhere. Any recommendations for stable Lollipop Roms?
Hi,
is there a mod with android 5.1.1 with working encryption?
i actually have a more specific question about the kernel used in the latest CM12.1 novafusion rom for this devicebut since i have fewer then 10 posts i have to ask here :/.
and i checked the forum for related threads and i found a few, but nothing in regard to that specific mod and device. (i found questions, no answers)
there is enough room at the end of partition for encryption and the fs is ext4 which seems to be needed for device encryption.
Still i get the error:
E/Cryptfs ( 2221): Cannot load dm-crypt mapping table.
which stems from "static int load_crypto_mapping_table" in cryptfs.c
which may be because CONFIG_CRYPTO_SHA256 isnt enabled in kernel.
any way to check that on running kernel?
best regards,
Hello.
I have flashed my smartphone Asus Rog 2 Tencent Edition
raw firmware WW_ZS660KL_16.0622.1907.33_M3.13.33.26-ASUS_1.1.134_Phone-user
The process was successful. The device passes the Safety Test.
But the serial number of the device turned into C4ATAS000000
I tried to make a hard cut and flash the device again, but the result remained the same
in log file "fastboot.log" i see my real SN
##################################################################
######################### DEVICE INFO ##########################
##################################################################
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Device authorized: false
(bootloader) Device authorized2: false
(bootloader) ABL : AC-ES-15-WW-user
(bootloader) SSN : MyRealSerialNumber
I intentionally did not indicate the real serial number, but I can send a log to private messages if this can help
A smartphone cannot receive a root and cannot be updated with firmware in the root partition. An error occurs. I ask the community for help
Sorry for poor English
he11fire_ua said:
Hello.
I have flashed my smartphone Asus Rog 2 Tencent Edition
raw firmware WW_ZS660KL_16.0622.1907.33_M3.13.33.26-ASUS_1.1.134_Phone-user
The process was successful. The device passes the Safety Test.
But the serial number of the device turned into C4ATAS000000
I tried to make a hard cut and flash the device again, but the result remained the same
in log file "fastboot.log" i see my real SN
##################################################################
######################### DEVICE INFO ##########################
##################################################################
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Device authorized: false
(bootloader) Device authorized2: false
(bootloader) ABL : AC-ES-15-WW-user
(bootloader) SSN : MyRealSerialNumber
I intentionally did not indicate the real serial number, but I can send a log to private messages if this can help
A smartphone cannot receive a root and cannot be updated with firmware in the root partition. An error occurs. I ask the community for help
Sorry for poor English
Click to expand...
Click to collapse
After the move of this thread from the non-suitable general sub-forum to Q&A, this thread has been closed as a thread of this subject already exists (where this post has also been made): https://forum.xda-developers.com/rog-phone-2/help/help-help-how-to-change-serial-to-root-t4015453
XDA Forum Rules (excerpt):
...
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.
...
15. Keep threads / posts on-topic
Whilst a minor amount of off-topic posting may be overlooked, the general rule is that your posts / threads must be relevant to the Forum / thread in which you are posting.
General Forums - For news and announcements relating to your device.
Q&A Help & Troubleshooting Forums - For all question / request threads and posts. If there is no Q&A Help & Troubleshooting forum, use the General Forum of the relevant device
Accessories Forum - For posts related to accessories relevant to the device
Development Forums (ones with the word development in the title) - For Developers to post release threads e.g. ROMs and Kernels including modifications to kernels, bootloaders, ROMs, etc., as well as R&D development discussion threads designed with an end goal
Themes and Apps Forums - For the posting of Themes and / or Apps as well as announcements & discussions including modifications made to Themes and Apps.
...
Click to expand...
Click to collapse
I have busybox and magisk hideprops config modules installed. When I open terminal emulator and run su and magisk --applets, only su and resetprops come up. Any fix for this or am i doing something wrong?
What you did wrong was post in the wrong section. We have a Magisk section which is the appropriate place for your question. Your post will be moved there shortly.
Remember to search before posting:
1. Search before posting.
Use one of our search functions before posting or creating a new thread. Whether you have a question or just something new to share, it's very likely that someone has already asked that question or shared that news.
Use our search function to find the best forum for your device.
Click to expand...
Click to collapse
I can only see two applets in documentation. the other commands were used to be separate binaries up to Magisk v21.4
https://topjohnwu.github.io/Magisk/tools.html