yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Q&A, Help & Troubleshooting] TheLMGN:
Will my phone work properly after doing that?

UPDATE:

Renamed it to addon-dee in my prefered Filemanager (ES) and it's backing up now.

(thank god I decided to use a USB3 stick this time)

UPDATE 2:

Phone backed up and now is working fine! thanks.
[Nexus 6P Q&A, Help & Troubleshooting] Colchiro:
I was having the same error until I updated TWRP to the unofficial 3.0.2-3
[Nexus 6P Q&A, Help & Troubleshooting] m890:
I have this problem and l have 17g free space in my internal storage but receive error 255 and i don't find addon in my storage plz help me for fixing this error
[Nexus 6P Q&A, Help & Troubleshooting] Fe Mike:
Should be under /system/ . Are you rooted? I don't know if you can see that part of system if you're not rooted.
[Nexus 6P Q&A, Help & Troubleshooting] m890:
My device is rooted but this file isn't there.
[Nexus 6P Q&A, Help & Troubleshooting] rchtk:
It's not always the same file. Look at your log to see which file/dir is problematic.
[Nexus 6P Q&A, Help & Troubleshooting] 1gnc:
SOLVED createTarFork() process ended with ERROR=255

SOLUTION

This solution worked on my Zenfone 3, running lineage Android 7.1.2.

I tried many other things, like flashing different versions of TWRP, deleting the recovery directory, renaming files and all the like.

You may deselect compression, change the TWRP-date / time : nothing works !

You need an PC / Notebook with adb installed.

- start your phone in recovery-mode (TWRP)

- connect to PC and get the recovery.log with following adb command

adb pull /tmp/recovery.log

You will find a copy of the file recovery.log in the directory, from which you started the command

- open an editor or choose your favourite file viewer to open recover.log

- search for the last entry of the word "Error"

- in the line before that, the recovery.log states the name of the file that causes the problem

(in my case it was /system/addon.d)

- disconnect phone from PC.

- restart your phone in "normal" restart (do NOT boot to recovery mode)

- use a root file browser (I used ES-explorer with root enabled) and navigate to that directory/file

- delete the file (which I did not do - I tried some other steps)

- restart phone

This took 3-4 minutes, but I did not delete the file addon.d right away. Instead, I did this:

step 1

navigated to /system/addon.d and copied addon.d to SD-card

step 2

in /system/ , I renamed addon.d "addon_BU.d".

This was successful. In /system/ , the only file visible was now "addon_BU.d"

step 3

tried to create a directory named addon.d inside /system/ because my recovery.log said quote\ ... system/addon.d (not a directory) ... \unquote

FAILED. The directory could not be created by ES-explorer

step 4

copied my backup file addon.d from SD-card back into its original location /system/.

This, I though, would work just fine, because I had renamed the original addon.d to addon_BU.d.

So after restoring addon.d , the only thing left to do would be delte addon_BU.d.

ES-explorer reported no error, but - surprise - there was no file "addon.d" present in /system/

The only file still there was "addon_BU.d"

well, let's go to

step 5

rename addon_BU.d back to it's original name "addon.d" using ES-explorer

FAILED.

addon_BU.d could not be renamed - this file really was screwed up big time !!!

I ended up with no addon.d - so I could have deleted it right away istead of starting my trial with step 1 ...

step 6

Anyway. Shut dowm my phone.

Rebooted my phone normally (not to recovery mode !!!)

This took considerably longer than normal - my heart rate had began to increase slightly if not to say I began to feel like a squirrel on red bull...

After roughly 3 minutes, I had a successful reboot to my OS (lineage Android 7.1.2)

step 7

Reboot again, this time to recovery mode (=TWRP)

and: backups work again.

Don't ask me why this worked and if it will work for you, but hey, give it a triy and let me know...
[Nexus 6P Q&A, Help & Troubleshooting] SlimSnoopOS:
Hi, thank you for a fix but this is an 10 month old thread. The issue was with TWRP 3.0.2-2. Along with an EFS issue that plagued TWRP 3.0.1-2, both issues have long since been resolved.
[Nexus 6P Q&A, Help & Troubleshooting] coolvipcandy:
simple and working solution :

by [MENTION=4843441]yannick818[/MENTION]

"looks like it's an error with parallel apps oder multiple users. since i do not use something like that, i just removed this user with the android terminal emulator:

su

pm remove-user 999

everything was fine after that"
[Nexus 6P Q&A, Help & Troubleshooting] larpoux:
I could resolve my nandroid /data backup error on my EMUI 8.0 Mediapad M5 device with those following steps:

1 - Use a correct TWRP implementation

TWRP need to access the uncyphered partition /data.

There no possibility to backup it, if TWRP does not implement deciphering user data partition.

2 - Remove all users except user 0 (the administrator)

You can verify that there is no unwanted users, looking at directory /data/user : the only subdirectory should be "0".

To remove the others users :

Remove the PrivateSpace if you have one (Settings > Security & Privacy > PrivateSpace, and tap on the garbage can).

Remove all the secondary users (Settings > Users & accounts > users, and tap on each users to delete them). Keep just the main administrator user.

On EMUI, remove all twins applications (Settings > Apps & Notifications > App Twin, and disable all twin apps).

On OxygenOS, remove all parallel apps (Settings > Apps > Parallel Apps, and disable all parallel apps).

On MIUI, remove all dual apps (Settings > Dual Apps, and disable all dual apps)

On others devices ... you must find all parameters that create those unwanted users.

If you are not able to get the correct settings to suppress those users, in last resort you can try this command : "pm remove-user user-no. (For example "pm remove-user 999").

3 - Do not forget to protect your backups by a password

This would be stupid to cipher your /data partition and keep backups of this partition unprotected.

These steps fixed the nandroid backup problem for /data partition on my Huawei Mediapad M5 device.

I post on this forum because I hope that this will be helpful for others devices owners.
[Galaxy Note5 Q&A, Help & Troubleshooting] jdq1412:
Im trying to install stock firmware on my note 5 and it keeps failing. Yes i do have the correct firware for my model and carrier. Hope some1 can help me out

<ID:0/005> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/005> Odin engine v(ID:3.1205)..

<ID:0/005> File analysis..

<ID:0/005> SetupConnection..

<ID:0/005> Initialzation..

<ID:0/005> Get PIT for mapping..

<ID:0/005> Firmware update start..

<ID:0/005> SingleDownload.

<ID:0/005> sboot.bin

<ID:0/005> cm.bin

<ID:0/005> FAIL!

<ID:0/005>

<ID:0/005> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)
[Galaxy Note5 Q&A, Help & Troubleshooting] MrMike2182:
Who is your carrier and which firmware are you trying to use? Are you trying to downgrade/Update or something? Has the phone ever been rooted? Did you enable oem unlock in developer settings? It's kind of hard to just guess or help you with the information you've given us.
[Galaxy Note5 Q&A, Help & Troubleshooting] jdq1412:
T-mobile and im trying to use stock note 5 firmware. Yes i was rooted and with a custom rom. Im trying to unroot the phone and put it back to stock but now it wont get past samsung note 5 logo and im still getting the fail from odin when trying to install the firmware.
[Galaxy Note5 Q&A, Help & Troubleshooting] MrMike2182:
That's because you rooted the phone and it tripped your Knox counter so the only way to fix this is to reinstall TWRP and then flash the rom again and after it's working go into SU and select remove root or whatever and then you'll need to extract the firmware you downloaded from T-Mobile and you'll need to put the files in the correct spot in Odin so they flash one at a time I.E. Boot, CM, RECOVERY etc etc... You should also try unzipping the firmware and then delete only cache.img and then repack/rezip it and try flashing it like that before trying all the other stuff.
[Moto G4 Play Questions & Answers] tttony:
Hey,

This "feature" is from Android, but having pattern to unlock the phone, why I have to swipe to unlock to see the pattern to unlock the phone? :silly:

Any hack for this?
[Huawei Mate 9 Questions & Answers] swordstool:
Just activated my Mate 9 in the US a few hours ago on AT&T. Seems like calls and texts are being sent/received fine. However, when I start a new text, start typing a contact that is in my Contacts (that I synced to the phone via Google), the contact comes up, but when I select it I get an error message: "Invalid Recipient <(732) 283-0192)> He or she will not receive the message", without the quotes. Not sure if it's related, but I am also not seeing all recipients on group texts that I confirmed had multiple recipients that are in my Contacts.

Any ideas?
[Huawei Mate 9 Questions & Answers] papped:
It's a bug in the SMS messaging stock app. Try installing another like Google Messenger and it'll work
[Huawei Mate 9 Questions & Answers] swordstool:
Oh okay, thanks! I actually just installed Chomp SMS and it seems like it's working there, but maybe I'll check out Google Messenger too. Is it better, in your opinion?
[Huawei Mate 9 Questions & Answers] aknotts415:
Textra is really great too
[Huawei Mate 9 Questions & Answers] opasha:
Textra is the best period
[Huawei Mate 9 Questions & Answers] swordstool:
Damn. I just imported like 6 years of texts that I keep transferring from phone to phone with SMS Backup into Chomp. I guess I have to do it again to get them into Textra now =(
[Huawei Mate 9 Questions & Answers] taphius:
I had the same error on my Mate 8 (on att) when i moved to one of the international roms, it was always the number format that caused issue on mine. Ended up downloading an app to make all phone numbers the standard US format
[Huawei Mate 9 Questions & Answers] Quizo:
country code. use the number 1 first. it should work
[Huawei Mate 9 Questions & Answers] swordstool:
Supposedly it's a bug in the stock SMS app. I'm using Chomp now and no issues. And there's no way I'm changing the country code in every one of my Contacts LOL!
[Huawei Mate 9 Questions & Answers] Quizo:
test it out. and see if that fixed that issue. then you would know for sure
[Huawei Mate 9 Questions & Answers] TechDro2:
I know this is late but is this a known bug in all international versions? Or is it just the way the stock app is programmed in all international versions. My brother has this and it works with country code added but is a hassle and wants to know if he should get an exchange or if it'll be the same with the new one.
[Huawei Mate 9 Questions & Answers] p51d007:
Another vote for Textra...I'm still using a Mate8, textra is perfect.
[Huawei Mate 9 Questions & Answers] cuti7399:
having same issue with stock message. tried textra and android mms same result, any other suggestion?
[Huawei Mate 9 Questions & Answers] bdcrim:
Try Pulse. Works for me on Cricket.
[Huawei Mate 9 Questions & Answers] bdcrim:
I used tetra for awhile and I had to change a MMS setting to legacy to make it work.
[Huawei Mate 9 Questions & Answers] swordstool:
Mine works fine with ChompSMS.
[Huawei Mate 9 Questions & Answers] cuti7399:
I tried Pulse but still not working, will give ChompSMS a try. I have tmobile
[Samsung Gear S3] Gamemaster1379:
After working with it for about a day or so, I seem to be at a loss as to how to connect my Gear S3 with my Note 4 Smartphone. It is running CM13. I am unable to use the Gear App from the play store as it tells me my device has been modified in an unauthorized way.

I attempted the Android Wear app as well. I modified my build.prop from userdebug to user and it let me connect, but the watch doesn't do anything different--it still remains on the samsung gear screen.

I realized there'll be limited connectivity if I manage it, but is there a way to connect the two?
[LG G5 Questions & Answers] JTrocks:
I decided to downgrade from Android 7.0/Nougat back to Marshmallow, so I flashed the H850 .kdz file using LG UP to downgrade. Unfortunately it failed and now my phone only boots to download mode.

I have tried to boot normally and into recovery mode, but I am taken into download mode each time. Any help?

Edit: Fixed by plugging into LG Bridge. Bridge detected that it was running Marshmallow and updated it to Nougat, correctly restoring the software.
[LG G5 Questions & Answers] meilbox:
to downgrade follow

http://xdaforums.com/showthread.php?t=3511930
[Tilt, TyTN II, MDA Vario III General] the_Dark:
My kaiser has just arrived.

But it is simlockt.

I looked through this forum but didn't find a way to get rid of the simlock.

So there is no way to get rid of the simlcok for the kaiser?
[Tilt, TyTN II, MDA Vario III General] sherpa:
I don't know how you searched but there is a person doing it for a small fee. There is no freeware program yet to sim unlock Kaisers.
[Tilt, TyTN II, MDA Vario III General] the_Dark:
Thnx sherpa,

now 2 find that person
[Tilt, TyTN II, MDA Vario III General] sherpa:
I'll help you out! :D http://xdaforums.com/showthread.php?t=314547
[Fire HD 6 and 7 Q&A, Help & Troubleshooting] jpr9845:
My Fire HD 6 running TWRP 2.8.6.0 gives me the following error when I try to do a restore.

E:extractTarFork() process ended with ERROR=255

I have two backups

1) CM11

2) Test-Keys

same result on either

I was able to switch back and forth between them until today

What has happened, please?
[Fire HD 6 and 7 Q&A, Help & Troubleshooting] OrphanedPixel:
I need to know if any progress has been made on rooting a 2014 Kindle Fire HD 7 on Fire OS 5.3.1.1. I would prefer if I didn't need to use ADB as I don't have a computer to run it with. Thanks!
[Fire HD 6 and 7 Q&A, Help & Troubleshooting] rxwookie:
Just wanted to second this request. I was able to find a used 2014 Kindle Fire HD 7 for a REALLY great price. Unfortunately, it was already upgraded to Fire OS 5.3.1.1 and factory reset. I would love to be able to root it, but there are no instructions on how to proceed with this firmware version. :confused:

I'm willing to use Windows, Linux, or files on the Kindle itself. I'm familiar with general rooting, mostly with the Samsung line of devices.

Any help would be greatly appreciated. :highfive:

Sincerely,

Wookie
[Fire HD 6 and 7 Q&A, Help & Troubleshooting] olliebean:
You'll need to use ADB, and downgrade to 4.5.3 before rooting, but you can flash back to 5.3.1.1 afterwards and still be rooted - this is the tutorial to follow: http://xdaforums.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950 (you can get the 5.3.1.1 firmware from https://www.amazon.co.uk/gp/help/customer/display.html?nodeId=201596850)
[Android Q&A, Help & Troubleshooting] polartux:
Hello, I have a question regarding strange behaviour after running TWRP on BP2 (Blackphone 2).

TWRP image: twrp-3.0.2-0-bp2.img

System version: Silent OS 2.0.8 RC4 (Lollipop 5.1.1, LMY47V)

Device model: BP2H001RW1

When I boot TWRP for a first time, it asks me "Keep System Read only?" and I always choose "Keep Read only".

When I mount /system in a ro mode, reboot and have my system working fine as previously.

But once I remount /system with rw privileges and unmount it even without touching files, I reboot and have a forever bootloop.

I even tried this to test:

mount /system -o remount,rw && umount /system && reboot

Yes, it goes bootloop after that.

So, everytime I mount /system with rw flag, there is something in the stock ROM that is tracking ext4 flags for mount count or last mount time and preventing the system from booting.

The only way to fix it is to write original system.img again using dd or TWRP "Install image".

I reproduced it multiple times and confirm that you don't need to modify any files, only a mount with rw permissions and unmount is enough in order to break it.

Is it some kind of protection? Any thoughts how to bypass this issue?
[Android Q&A, Help & Troubleshooting] bastard81:
In the end the problem was solved?

how? It can also be useful for other users :)
[Android Q&A, Help & Troubleshooting] androidblue:
Hi there

a simple google search always helps:

System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.

I think that it means is that when you try to re-boot the system the OS check and when it discovers it does not match the checksum it stops from loading.
[Android Q&A, Help & Troubleshooting] polartux:
Could someone elaborate about that checksum script? Where is it usually kept , which block device, how to bypass it? Any info could be useful there.
[Android Q&A, Help & Troubleshooting] chape199:
A litle guide to increase bp2 performance

https://xdaforums.com/android/development/guide-make-bp2-t3735815/post75218344#post75218344
[Android Q&A, Help & Troubleshooting] kch79624:
Maybe It's because of the dm-verity (verified boot). I also had the same issue.
[Samsung Gear S3] tids2k:
Hello friends,

Please find attached below PIT file and information for the new Samsung Galaxy Gear S3.

My watch is from Gear S3 Frontier without LTE version. ( Be careful not to be used with AT & T model )

Also Note : Go to Settings -> Gear Info -> About Device -> Tap Software version ( 5 times ) -> Magic

Codes you can use in hidden menu

Check All Hardware ( Sensor, speaker, Echo Test, Camera) – *#0*#

USB Config – *#0808#
[Samsung Gear S3] tids2k:
Please click on thanks button if helpful to anyone. Please check my other thread for rom and bootloader.
[Samsung Gear S3] michaeldanielbourke:
Gear Pay SM-R760

G'day, I bought my watch from eglobaldigital.com.au, due to no stock in Sydney. Have an s7 edge Aussie variant. I cannot get gear pay on my watch, do you know what I need to do?

Michael
[Samsung Gear S3] highaltitude:
Wrong forum area. This is for development. Check the Question and Answer area.
[OnePlus 3 Questions & Answers] Lolteee:
all is in the title can we install custom rom on it ? or i need to downgrade ?
[OnePlus 3 Questions & Answers] Explorer23:
Um ... What?

Your question doesn't make sense.

Open Beta 8 is a ROM. You don't install ROM "on" another ROM ... You can overwrite it though (in this case you won't have OB8 any more).
[OnePlus 3 Questions & Answers] m4manusraj:
May be take a look at Multirom thread. That's what you may be looking. AFAIK
[OnePlus 3 Questions & Answers] Lolteee:
No i mean like do we need to downgrade to MM for having the possibility to install custom rom beacause if we downgrade without the help of oneplus support or something like that it might brick the devices
[OnePlus 3 Questions & Answers] Hw4ng3r:
The only thing you need is an unlocked bootloader with the correct version of a custom recovery (ie. TWRP) to install custom (and stock) ROMs. You may want to take a look at http://xdaforums.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733 for more information.
[OnePlus 3 Questions & Answers] Lolteee:
Thx but its not this i already know how to install custom rom and everything its just i dont know if we can install custom rom on OP8 beacause of bootloader who have change beacause oneplus said to not downgrade to MM without their help so if i install cm 13 or cm 14 i dont know if it will work and not brick my op3 ( even if we can recover it )
[OnePlus 3 Questions & Answers] simcax:
It's not the bootloader, it's the f2fs /data that can be problematic if you downgrade.
[OnePlus 3 Questions & Answers] Hw4ng3r:
And this issue can be resolved by following http://xdaforums.com/oneplus-3/how-to/guide-downgrade-to-mm-flashing-ob8-t3511161.

I believe most people will recommend that you go back to an MM ROM before flashing anything else as [MENTION=4042950]simcax[/MENTION] has mentioned the issue with the data partition.
[OnePlus 3 Questions & Answers] Lolteee:
Thanks for taking time respond to me and for your answer !
[Moto Z Questions & Answers] Porcelainfog:
Hey XDA, I haven't been on here since my Samsung S2 years ago. I picked up a new moto Z for daydream, (amazon 499 special, 64 gb luna grey unlocked, retus software, 650-03). I bought it from the american amazon, and I am in canada. I popped in my Sasktel sim card and it works perfectly.

My questions are:

How do I manually flash nougat?

If I flash to the rogers 45 firmware, will I still be able to use my Sasktel sim?

How long until nougat comes out regardless? Should I just wait?

If I do flash to this "rogers 45 nougat", can I go back to my "vanilla" stock later? ( i just want daydream now, i bought the headset already. then when my area gets nougat, ill flash back to my phones nougat.. or does it make a difference?)

Sorry for the really random questions. I couldn't find the answers to these on the forums or on google. (reddit has been saying just wait, and don't flash)
[Moto Z Questions & Answers] pixelens:
You can try this thread here: http://xdaforums.com/moto-z/how-to/easy-flash-to-nougat-tutorial-unlocked-t3514245 - I had success flashing the Rogers 45 firmware (am on retca software channel) but for the life of me couldn't get the Nougat update to install. I'm on Telus and had no issues with my SIM card working after I flashed to the Rogers 45. Flashed back to the retca official firmware (http://xdaforums.com/moto-z/development/moto-z-official-firmware-downloads-t3449837) this morning with no problems.

Another issue I'm running into is that I unlocked it and for the life of me I can't seem to get the phone locked again. Minor issue but that "your phone is unlocked/untrustworthy" message when you boot up is annoying ;)
[Moto Z Questions & Answers] enetec:
Just flash the patched bootlogo you can find here... (or, better, make one as I liked more and asked for... :p)
[Moto Z Questions & Answers] pixelens:
Going to start a new thread so as not to hijack this one :)