Hello,
I have an LG G3 rooted with towelroot downloaded titanium backup with pro key, nandroid as well as nandroid online... And all my backups so far get saved to my phone memory... /mnt/sd... However i need the path to be going to my sd card witch is /storage/external_SD. When i try to change path nandroid tells me i have to use twrp or clockworkmod folder and will not let me change file path... Titanium backup saves to same sd folder but that is my phone memory... Im not very knowledgeable so please be as basic as possible. Thank you
Hi!
As towelroot is not a full root, write protection is likely still enabled on the device, it has limitations and some things simply don't work. Here is a thread on towelroot in your device section.... You can ask the members there for help....
LG G3G3 Themes and Appstowelroot - untethered root - confirmed working
Good luck!
KJ said:
Hi!
As towelroot is not a full root, write protection is likely still enabled on the device, it has limitations and some things simply don't work. Here is a thread on towelroot in your device section.... You can ask the members there for help....
LG G3G3 Themes and Appstowelroot - untethered root - confirmed working
Good luck!
Click to expand...
Click to collapse
So what should i do? I could uninsrall towelroot and start over?
Discipl said:
So what should i do? I could uninsrall towelroot and start over?
Click to expand...
Click to collapse
As I've said, asking the people with the experience on your device in the link I have gave you would probably help. ?
Related
Hi,
I rooted my phone because I wanted to use an application called FolderMount, so I could store big chunks of data from apps onto my SD card.(it seems as though the SD card is useless on Android)I am using an HTC Desire 601, with Android version 4.2.2. Now my problem is that, I'm having an error with FolderMount because of something to do with external SD card r/w permissions.(no this is not specific to the app, it's a software wide problem, that's why I'm posting here.) So I found a "fix" that involved editing platform.xml and adding a line. However, everytime I try to edit it, either the phone just reboots, or no changes are made. Basically, the system folder is denying me r/w access. In root explorer there is a feature to mount it temporarily as r/w, but then if I reboot my changes are lost. This is a problem which I think is also not allowing me to install Busybox. Please help me with this. Thank you.
Jason1712 said:
Hi,
I rooted my phone because I wanted to use an application called FolderMount, so I could store big chunks of data from apps onto my SD card.(it seems as though the SD card is useless on Android)I am using an HTC Desire 601, with Android version 4.2.2. Now my problem is that, I'm having an error with FolderMount because of something to do with external SD card r/w permissions.(no this is not specific to the app, it's a software wide problem, that's why I'm posting here.) So I found a "fix" that involved editing platform.xml and adding a line. However, everytime I try to edit it, either the phone just reboots, or no changes are made. Basically, the system folder is denying me r/w access. In root explorer there is a feature to mount it temporarily as r/w, but then if I reboot my changes are lost. This is a problem which I think is also not allowing me to install Busybox. Please help me with this. Thank you.
Click to expand...
Click to collapse
Stock rom?
Which root app do you use?
LS.xD said:
Stock rom?
Which root app do you use?
Click to expand...
Click to collapse
I'm using the default version of Android that came with my phone, if that's what you mean. And umm what do you mean by which root app did I use?
Jason1712 said:
I'm using the default version of Android that came with my phone, if that's what you mean. And umm what do you mean by which root app did I use?
Click to expand...
Click to collapse
You said you "ROOTED" your phone. That means you have some kind of "SUPERUSER" app installed. I hope so at least
LS.xD said:
You said you "ROOTED" your phone. That means you have some kind of "SUPERUSER" app installed. I hope so at least
Click to expand...
Click to collapse
Oh okay I have the SuperSU app it's SuperSU v1.93 I don't know if it's the latest version. Sorry, I'm new to this rooting stuff. I only got this phone this Monday, and I only got to know about rooting the day after.
Jason1712 said:
Oh okay I have the SuperSU app it's SuperSU v1.93 I don't know if it's the latest version. Sorry, I'm new to this rooting stuff. I only got this phone this Monday, and I only got to know about rooting the day after.
Click to expand...
Click to collapse
Open SuperSU and check if access is granted for "FolderMount"
Do you use free FolderMount? Thats limited to 3links at all.
What type of sd card do you use?
LS.xD said:
Open SuperSU and check if access is granted for "FolderMount"
Do you use free FolderMount? Thats limited to 3links at all.
Click to expand...
Click to collapse
Yes, of course access is granted. I have only tried to create one link so far...so it can't be anything to do with the number of links permitted in FolderMount. I mean, I haven't been able to create a single working link. Precisely, the error I'm getting in FolderMount has something to do with sd card r/w permissions(I've linked a screenshot;maybe you've had this problem before and you solved it?)
The only possible fix I can find is the edit to platform.xml. I've contacted the developer; notice how it says "Attempt to patch my ROM"? Well the developer told me that when the patch is applied and when I reboot, the patch is erased because of the reboot(he said that seems to be the case) so I need to find a way to ensure that it isn't erased. I'm having the same problem here; when I make an edit, it's erased either immediately or after reboot. So that's why I need to find a way to fix this. Thanks, if you have a possible fix.
I've tried using DirectoryBind, but it doesn't work and I hear it's been broken since 4.2. I don't know how to revert back to a previous Android version for my device, so I'm stuck.
Jason1712 said:
Yes, of course access is granted. I have only tried to create one link so far...so it can't be anything to do with the number of links permitted in FolderMount. I mean, I haven't been able to create a single working link. Precisely, the error I'm getting in FolderMount has something to do with sd card r/w permissions(I've linked a screenshot;maybe you've had this problem before and you solved it?)
The only possible fix I can find is the edit to platform.xml. I've contacted the developer; notice how it says "Attempt to patch my ROM"? Well the developer told me that when the patch is applied and when I reboot, the patch is erased because of the reboot(he said that seems to be the case) so I need to find a way to ensure that it isn't erased. I'm having the same problem here; when I make an edit, it's erased either immediately or after reboot. So that's why I need to find a way to fix this. Thanks, if you have a possible fix.
I've tried using DirectoryBind, but it doesn't work and I hear it's been broken since 4.2. I don't know how to revert back to a previous Android version for my device, so I'm stuck.
Click to expand...
Click to collapse
Some files e.g. related to kernel will be generated on every boot. In that case you can't change em permanently. BUT you can try another solution so far Create a ext2/ext4 partition on your external sd and use Link2SD or APP2SD pro
In the superSU setting, try enabling option allow apps requesting root permission at start up(on boot).
Sent from my G610-U00 using xda app-developers app
LS.xD said:
Some files e.g. related to kernel will be generated on every boot. In that case you can't change em permanently. BUT you can try another solution so far Create a ext2/ext4 partition on your external sd and use Link2SD or APP2SD pro
Click to expand...
Click to collapse
Um..how do I do that?
Jason1712 said:
Um..how do I do that?
Click to expand...
Click to collapse
Do you have a custom recovery installed?
LS.xD said:
Do you have a custom recovery installed?
Click to expand...
Click to collapse
Yes.Philz-Touch Modified, Advanced CWM Recovery. At least, that's whats stated in the Desire 601 root guide.
Jason1712 said:
Yes.Philz-Touch Modified, Advanced CWM Recovery. At least, that's whats stated in the Desire 601 root guide.
Click to expand...
Click to collapse
This recovery has a built-i feature to parttition sd-card. Pls keep in mind that all data on sd will be deleted during the process. i look out for a guide.
Your recovery / Rom (Kernel) has to support this feature. I can't find this information. So pls be patient. I'll pm you as soon as i found a safe solution.
LS.xD said:
This recovery has a built-i feature to parttition sd-card. Pls keep in mind that all data on sd will be deleted during the process. i look out for a guide.
Click to expand...
Click to collapse
So I just have to do that? Just boot into recovery, then use the partition sd-card feature in my recovery, and then that's it? My sd card will be partitioned? Ok, then I download..Link2SD?
LS.xD said:
This recovery has a built-i feature to parttition sd-card. Pls keep in mind that all data on sd will be deleted during the process. i look out for a guide.
Your recovery / Rom (Kernel) has to support this feature. I can't find this information. So pls be patient. I'll pm you as soon as i found a safe solution.
Click to expand...
Click to collapse
Oh sorry, I didn't see this post before I posted my reply. OK, thanks a lot.
Hello,
I'm Using a Rooted Starmobile Up has an MediaTek MT6582M
well, it started when i was changing the bootanimation of my phone with an marvelboot.zip using ES File Explorer, i forgot to set the permissions so after i restart it, my phone stucked at boot animation.
i copied the marvelboot.zip at the /Device > system > media folder as far as i can remember.
i think it will be solved if i am able to delete the bootanimation.zip from that media folder using computer or something else.
i am wondering how can i delete that file from the system folder, or perhaps change permission? and is there a way to browse the system folder from android to computer?? i just wonder if theres such, but i will go with your answers.
i have no CWM installed and i dont know how, i dont know ADB, or SDK and all
when i tried installing CWM from recovery menu, it says installation aborted and thats my only way.
can someone help me?
another thing is i forgot to backup the firmware, and ofcourse warranty is voided as it is rooted, i cannot get it's firmware anywhere.
thanks again
I need your help, thank you.
OK so you can post your question here: http://forum.xda-developers.com/showthread.php?t=2257421&page=1
However, I urge you to keep searching for the stock firmware. This is a rare device that has practically no support.
If you had adb support which is highly unlikely you could use the command "adb push bootanimation.zip/system/media"
But I very much doubt you will be able to get adb to communicate.
I wish you all the best in searching, but I think you may have just learned a very costly lesson on always having a backup before tinkering.
Good luck
hello, hmm what if i buy a new unit of this model? lets say another starmobile up, and i backup its firmware, is it possible to do that?
and is it possible to copy the back up on this device?
whateverwhenever said:
hello, hmm what if i buy a new unit of this model? lets say another starmobile up, and i backup its firmware, is it possible to do that?
and is it possible to copy the back up on this device?
Click to expand...
Click to collapse
I honestly don't think it would work. You really need a custom recovery or a way to access your bootlooping phone's system.
You can check this thread out on adb http://forum.xda-developers.com/showthread.php?t=2588979
If you're successful in getting adb to work you may have a shot at fixing it. But the odds are against you.
This is why we are all encouraged to read and be careful.
Hello folks, i have Galaxy Core 2 SM-G355H and i have rooted my phone and installed the CWM recovery, which i think has done good.
Even the phone after being rooted hasn't done me any good.
I had initially started a topic here: http://forum.xda-developers.com/galaxy-core/help/copy-to-ssd-samsung-galaxy-core-2-sm-t3033178
But the OP hasn't been able to give me some working solutions.
So i am asking to anyone who knows about this stuff. I have rooted and installed CWM recovery, that still given me authority
over my SD-Card, i cannot copy/paste/delete/rename basically access it fully.
The only way i can do is, remove the SD-Card and insert in a Card reader and copy/paste/delete etc.
But i cannot directly do from phone itself.
I already have fX Explorer, Solid explorer and ES File Explorer.
Nothing has worked, so i am asking can anyone show me how to do that.
I would be grateful for your suggestion.
Awaiting reply.
desktopuser said:
Hello folks, i have Galaxy Core 2 SM-G355H and i have rooted my phone and installed the CWM recovery, which i think has done good.
Even the phone after being rooted hasn't done me any good.
I had initially started a topic here: http://forum.xda-developers.com/galaxy-core/help/copy-to-ssd-samsung-galaxy-core-2-sm-t3033178
But the OP hasn't been able to give me some working solutions.
So i am asking to anyone who knows about this stuff. I have rooted and installed CWM recovery, that still given me authority
over my SD-Card, i cannot copy/paste/delete/rename basically access it fully.
The only way i can do is, remove the SD-Card and insert in a Card reader and copy/paste/delete etc.
But i cannot directly do from phone itself.
I already have fX Explorer, Solid explorer and ES File Explorer.
Nothing has worked, so i am asking can anyone show me how to do that.
I would be grateful for your suggestion.
Awaiting reply.
Click to expand...
Click to collapse
Have you flashed new firmware ?
New kernels (boot.img) have default ro acess to sdcard !
Please state your infos :
Model
Modem
Core build ...
The workaround I provide for this type won't work after update !!!
You will have to flash previous boot or recompile the new boot
Regards.
StratOS_HTC said:
Have you flashed new firmware ?
New kernels (boot.img) have default ro acess to sdcard !
Please state your infos :
Model
Modem
Core build ...
The workaround I provide for this type won't work after update !!!
You will have to flash previous boot or recompile the new boot
Regards.
Click to expand...
Click to collapse
My Mobile is Galaxy Core 2 SM-G355H , please see the snapshot to see the version number.
desktopuser said:
My Mobile is Galaxy Core 2 SM-G355H , please see the snapshot to see the version number.
Click to expand...
Click to collapse
This is still old release, donno why U can't access the extSdCard with current provided infos.
StratOS_HTC said:
This is still old release, donno why U can't access the extSdCard with current provided infos.
Click to expand...
Click to collapse
Its ok, i totally lost interest in it.
desktopuser said:
Its ok, i totally lost interest in it.
Click to expand...
Click to collapse
Have U read my last reply ?
http://forum.xda-developers.com/showpost.php?p=59071633&postcount=11
The FS /system and other too is/are readonly (ro) in device, so if u want to delete or copy inside this partition u must change it to rw (readwrite), it's better for you to use some Explorer root based application like FX Explorer with root addon ...
If u have copied the update zip to extSdCard and run the update procedure in stock recovery U should be able to copy/edit/delete files on your extSdCard - Card if the install were sucessfull.
For a check: Install app https://play.google.com/store/apps/d...=nextapp.sdfix and check again things now U'r rooted. Regards
Click to expand...
Click to collapse
StratOS_HTC said:
Have U read my last reply ?
http://forum.xda-developers.com/showpost.php?p=59071633&postcount=11
Click to expand...
Click to collapse
I have already installed at least a dozen of explorer, most promising was fx explorer with it free root access add-on, the other was ES File
explorer. They both can't copy/paste files to Memory card.
My device is Galaxy Core 2 SM-G355H, Android 4.4.2. I have already rooted and installed CWR mode, but i havn't flashed my firmware.
I am searching now for a possible firmware update, that could access memory card.
Could you do a small part from your side and find a firmware that can be flashed in my device, i will try from my side. :good:
Will update , if i find some solution.
KK SDCard fix
desktopuser said:
I have already installed at least a dozen of explorer, most promising was fx explorer with it free root access add-on, the other was ES File
explorer. They both can't copy/paste files to Memory card.
My device is Galaxy Core 2 SM-G355H, Android 4.4.2. I have already rooted and installed CWR mode, but i havn't flashed my firmware.
I am searching now for a possible firmware update, that could access memory card.
Could you do a small part from your side and find a firmware that can be flashed in my device, i will try from my side. :good:
Will update , if i find some solution.
Click to expand...
Click to collapse
The users in this forum don't know how to read posts. U'r among them too. Sorry for my statement, but it's true.
It's not only the explorers,apps or managers that can copy files from/to. The KitKat have a fix for KitKat SDCard ro access.
For a check: Install app https://play.google.com/store/apps/details?id=nextapp.sdfix and check again things now U'r rooted. Regards
Click to expand...
Click to collapse
.
Check and recheck the posts again, U'll find that you too fast jump to miss.. conclusions ... same as sometimes me too.
I am searching now for a possible firmware update, that could access memory card.
Click to expand...
Click to collapse
All of the stock firmwares uses KK RO acess for SdCard unless U install some custom & fixed ones.
Have also provided many tutorials in the subforums detaily how to fix it for GC2 models.
Latest firmwares uses some extra functionality regarding SDCards, fix will not work unless ...
Enjoy.
Read your start thread : http://forum.xda-developers.com/galaxy-core/help/copy-to-ssd-samsung-galaxy-core-2-sm-t3033178
Regards
OK, thanks for the statement. I accept, i am a newbie here. I can figure my way through most of the other forum out there.
But one pertaining to Mobile device require's little more knowledge, because its tricky, since there are a huge number of devices.
I am not a regular visitor.
Anyways, i found a firmware for my device.
Link:
http://www.sammobile.com/firmwares/database/SM-G355H/
http://samsung-updates.com/details/42605/Galaxy_Core_2/SM-G355H/INS/G355HXXU0AOC1.html
The second link to the firmware matched the hashes to the link in the first link.
Did the Odin thing, and all the necessary steps. But still i am not able to copy/paste/delete etc function.
So i technically give up for this device, i'll use it as it is.
@StratOS_HTC: I tried the KitKat access app from Google Play store, a number of them. But they all showed similar results.
But i'll be open to your opinion.
Thank you.:good:
desktopuser said:
Hello folks, i have Galaxy Core 2 SM-G355H and i have rooted my phone and installed the CWM recovery, which i think has done good.
Even the phone after being rooted hasn't done me any good.
I had initially started a topic here: http://forum.xda-developers.com/galaxy-core/help/copy-to-ssd-samsung-galaxy-core-2-sm-t3033178
Awaiting reply.
Click to expand...
Click to collapse
As said and will said again :
Please read carefully !
Hope your phone works ok and everything else on phone is ok.
If you can't access your extSdCard throught phone do a low level format ( and hope you don't use 64 GB ).
Hope also you don't use any other EXT partition on your sdcard. or any other sd linkage or swap options on your sdcard
Format the sdcard as only extFAT or FAT on any other comp card reader and reformat it on the phone !
Now you should be able to access the sdcard on your phone if every thing else on phone is ok.
If U'r rooted on stock ( KitKat sdcard restriction ) and if U have installed nextapp.sdfix and grant su access to it the app will change this permissions for you and you will be able to aceess rw to sdcard now.
Hi, so some background, it has been a long time since I have touched custom ROMs or root access on an android device (back when the Nexus 2 released) so I don't really remember anything and know nothing about how the android environment has changed.
The reason for my post is that I was "hiding" sentimental/sensitive material in a folder associated with the Google Drive application using a file manager app (cut and paste into Drive folder) so that it wouldn't appear in Gallery scans, and when my drive app wasn't working as expected I (stupidly) uninstalled the update (can't actually uninstall the app on stock ROM) causing the folder to be wiped. Now I'm trying to find a way to recover the files but all the solutions recommended by a google search that I've tried require root and from what I know, correct me if I'm wrong, unlocking my bootloader to gain root access will wipe my internal storage which would probably defeat the whole purpose(?) of trying to recover information as it will overwrite the sectors. So does anyone know of anyway that I can recover this data from my device? I am willing to root as long as it will yield results.
tl;dr - need to recover files on stock P20 Pro (locked bootloader, no root), please help I am lost and a noob now
Thanks in advance!
P.S. This was (incorrectly) posted in the discussion forum before and I have requested it to be deleted
BUMP
bump!
Bump! Can anyone please help?
Bump? :fingers-crossed:
toushingo said:
Bump? :fingers-crossed:
Click to expand...
Click to collapse
Stop bumping. You are simply in the wrong section. None of us has a Pro model. This is the P20-Forum. Not Pro, not lite. I can not understand why people see 3 different devices as one. Ask here. Good luck!
Hi, first of all, thank you for reading me.
I think i messed up big time.
I had Havoc OS 4.1 installed since more than a year and it was kinda messy e.g. the sim card card wasnt recognized anymore so wasnt able to make calls because i played to much in the settings.
Having some stupid but incredibly addictive games on this smartphone i decided to keep it like this and since i'm a complete n00bs and being afraid of security risk of rooting my device i never rooted it.
Big mistake.
So, recently, one games needed an update (like they all do at least once a week) and since i'm anti-google/f***book (no comment please) i nvever saved my progress in the cloud and "that" game required absolutely an update.
I installed the update from an alternative apk source and , (applause if you want and laugh), it screwed up the game.
Now the nightmare begin.
Since the device isnt rooted i made a backup of /data partition. Gone crazy and before i might explode in an uncontrollable fury and madness i used LMSA to rescue the phone. And myself, lol.
Now i have stock android and i am googled to the bone. My butt hurts. My head too.
THE (first) simple question is : how can i restore this backup because i have the error 255?
Notes and observations; logically i would say because the device is back with stock rom and doesnt have the same os/rom installed and/or the partition and whatever is not the same wich may explain the error 255.
SECOND QUESTION: can i extract/uncompress this backup and take the precious data wich is my games progresses and restore it somehow?
I know i have to give as much information possible but i dont what else to give. If you need logs, or everything else just say it nicely and i will give it to you with immense pleasure.
Oh yeah, model : XT2113-2 5g Kiev RETCA 128gb a/b type and maybe was crypted before because twrp asked me the password to make backup or else.
Thank you in advance and i really hope somebody would help, if not i just loosed 1.5 years of stupid gaming because i messed up like an idiot. (A lesson well learned, the hard way...)
Thank you so much for not answering this simple question.
Kerplunk83 said:
Thank you so much for not answering this simple question.
Click to expand...
Click to collapse
The problem is it's a Motorola with a Qualcomm chip.
If you find a solution I would love to see it.
Finally a sign of life from someone here.
Thank you sd_shadow
sd_shadow said:
The problem is it's a Motorola with a Qualcomm chip.
If you find a solution I would love to see it.
Click to expand...
Click to collapse
These precious brief and concise 2 lines of a simple answer is immensely welcomed.
Wich point me to reply that to my knowledge i interpret it as a security chip with big chances that its in relation to the knox technology.
It also point me to ask WHY, if i cant back up because of that, why/how is it possible to install a custom rom or gsi (sorry i still dont make the difference because i dont understand it) on this very protected smartphone?
That must explain why i had problems trying to root it and fail each time.
Finally i think that i should use another device for android gaming since i dont want to depend on f***book and google.
Thanks again sd_shadow. Even if it was a very simple answer it enlightens me alot.
Note: sorry for my bad english.
Kerplunk83 said:
how can i restore this backup because i have the error 255?
Click to expand...
Click to collapse
This error code means that at some point your backup of /data could not be extracted further. But for more detailed infos you must provide a recovery.log which will be generated when doing a backup of e.g. /boot.
>>> Please DO NOT copy+paste it here!! <<<​Rename it (recovery.log > recovery.log.txt) to be able to upload it within "Attach files".
Kerplunk83 said:
can i extract/uncompress this backup and take the precious data wich is my games progresses and restore it somehow?
Click to expand...
Click to collapse
Yes, use Titanium Backup (TB). Although it's very outdated it still features a restore of single apps out of a TWRP backup. Here's how you do it:
1. IMPORTANT: TB will only search for TWRP backup files on internal storage!! Use the default path created by TWRP, e.g.: /sdcard/TWRP/BACKUPS/ZY322V8K28/2023-04-08--06-53-20/
2. Install and open Titanium Backup.
3. In the upper right corner tap
MENU > scroll down to "Extract from Nandroid backup" > choose your backup folder
##############
Notes:
- Usually a TWRP backup of /data consists of several parts (data.ext4.win000, ~win001, ~win002 etc). TB requires all of them (or at least those ones with the /data/data/ path inside).
- If you are facing this error message:
Could not find any data in this TWRP backup
then your TWRP backup is compressed with gzip. To decompress it you must rename the file
data.ext4.win001 > data.ext4.win001.gz
and extract it with any archiver tool, e.g.:
- ZArchiver (Android)
- 7zip (Windows)
- Problems finding any TWRP backup data with Titanium Backup? Then please check your path!! (see above section)
Good luck!!
Thank you very much WoKoschekk i'll do it as soon i'll have the time for since i'm working today.
Thank you so much again, i'll keep you posted with logs and such.
I'm sorry i didnt gave news since, i'm not doing very well.
there's those 2 question i still have in my head;
1-With all the instructions you gave me is it worthy to continue because when i did the backup i wasnt rooted?
2- i'm sure i read many time to use Titanium Backup (wich is a paid app?) i have to be rooted or have root access.
Ultimately, how can i be rooted if there's a chip preventing me to do so?
I'll keep you posted when i'll be of better health, thank you.
Kerplunk83 said:
-With all the instructions you gave me is it worthy to continue because when i did the backup i wasnt rooted?
Click to expand...
Click to collapse
TWRP backup = *.tar archive
TB unpacks the needed app's data and nothing else. You must be rooted to have access on /data for restoring your apps. But for the backup process it doesn't matter if you were rooted. Root is part of your boot.img.
Kerplunk83 said:
2- i'm sure i read many time to use Titanium Backup (wich is a paid app?) i have to be rooted or have root access.
Click to expand...
Click to collapse
TB is for free. But a paid version unlocks additional features (not related to the TWRP restoring feature).
And yes... root is mandatory for TB. As I said before you must have r/w access on /data/*.
Kerplunk83 said:
if there's a chip preventing me to do so?
Click to expand...
Click to collapse
Which chip?? You already have root access via TWRP. Magisk is only needed in system and just a patched boot.img (custom kernel).
Get well soon!
WoKoschekk thank you for this insanely fast reply.
All those answers and infos have now a gigantic value for me, if only i knew that before.
To describe a bit more my situation i slept only few hours since 5 days, vomiting, heavy coughs and fever.
I'm sure i'm not supposed to but i will anyway, i engage myself and promise to reward you (in particular) and others for the help you're bringing me. It wont be much but very important to me.
I'll go try to get (again) some rest. Just before i go, why was there a mention about my device;
"
The problem is it's a Motorola with a Qualcomm chip.
If you find a solution I would love to see it.
"
I dont ask you (WoKoschekk) or other to explain in the most explicit and endless details of what is exactly this "chip" and all the history that goes with it cause i dont want to be a pain but just why it was mentionned. Only, why?, it has ben mentionned.
I cant wait to get better since i finally see possibilities to get back those files.
Have a nice week-end and thanks again.
@Kerplunk83 To reveal the mystery behind "the chip": Motorola released two variants (Snapdragon/Mediatek CPU) of this model. Since the CPU largely determines the system structure, building a functional TWRP for both of them is very challenging. It seems that TWRP for the SD's variant got some bugs while the MT's variant runs more smooth. Due to this fact the error 255 is caused by something that you weren't be able to fix.
Regarding your problem: To restore an app and its specific app data you need the proper permissions to write in /data/data and /data/app. For this permissions you either need TWRP or Magisk installed. TWRP seems to be unable to write in that specific directory. On the other hand you don't want to install Magisk. I'm sorry but with this setup your problem can't be fixed.
Just out of curiosity, could you provide me a recovery.log showing error 255 during the restore process?
Please DO NOT copy/paste the whole log and post it here!! Instead of this you should rename the file (recovery.log => recovery.txt) because a file called *.log isn't allowed for upload. But a *.txt file is.
Options to create a recovery.log:
1. adb pull /tmp/recovery.log
=> copies a recovery.log into your ADB/fastboot folder
2. Do a backup of sth. like "boot" because the backup process will create a recovery.log by default
3. TWRP mainscreen > advanced > create log (kernel log isn't needed here)
=> log is stored on the default storage (internal or external) that you have choosen for backups etc.