I am not a professional but I see many people had this problem but no real solution anywhere. I got this error when restoring data backup in TWRP and I was devastated, however Twrp does not check for space available and thats what happens when theres no available space to restore the backup.
ps: I know this might be obvious for some people or the post may be unprofessional so take it down (move) if you have a reason, I am just trying to help
Related
Lately this error appear a lot in my cm10.1.5. Do you know any way ti fix it? I ask to start trying every solution you post, even that I have already tried a lot of possible ways (all of them wrong) Thanks
As a last resource you could always wipe all your partitions and reflash the ROM.
I never got such an error though, so I don't know what your are talking about. Maybe with you could post some log file about the error, it would be easier for the people here to help you with it.
So I apologize if Im posting in the wrong spot but I noticed yall are still working on the F6...so I figured this made sense...
I thought I knew exactly what I wasdoing but did not....I was lucky enough to find patience enough to read up before flashing...I see the threads posted on how to root, backup, and restore this phone...but all those threads explain it using so0ftware other than I have... Since I made some moves before truly knowing what I was doing...I'd like to just stick wiith what i got for the moment and see if yall, as the experts can guide me down the runway...
Heres What I have so far:
1. I DO have root access
2. I DO have SuperSU and it seems to be working in the sense that it keeps logs...but sometimes it gives me a binary error. (I have NOT et converted SuperSU into a system app...bc im unclear if its necessary after reading a few different threads)
3. I DO have Root Browser' which I use to shuffle things around. (I DO have the /system and /data folders relocated on my external SD)
4. I DO have Titanium Backup which I used to BU my USER APPS/SYSTEM DATA.
5. I DO have Flashify which I also used to BU my STOCK RECOVERY/KERNEL (I cant seem to figure out where that recovery is being default stored though...Ive been searching high and low.
NOTE: Although im happy I have made it this far...I dont wanna go any further until I know exactly what im doing. I fear that I have missed something small. Something that would be a no brainer to you experts.
I'm unclear of storage requirements...I BELIEVE that I must store all my rooted tools on the external bc the goal is to wipe everything NOT on ext SD.
What I THINK I know is that hypothetically since im backed up...or when im 100% certain everything is....I can just click REBOOT TO RECOVERY MODE under the menu using Titanium.
IF I happen to be correct up to that point....I think my next move is using Titanium to put back the things ive stored on my SD.
In my mind that leaves me with the same ROM...but without the fluff...and now the ability to save to ext SD.....
If I underestand right....currently there are no MOD upgrades available due to difficulty of unlocking the bootlag....or something that sounds likethat...
I have ZERO experience with any of this....I hope what I just shared is at least in the ballpark of the right direction..
THANK YOU for any and all help!
I
On a mission to take my LGF6 and make a man outta it!
On a mission to take my LGF6 and make a man outta it!
No one can help me? Am i just completely way off..or am i posting wrong?
On a mission to take my LGF6 and make a man outta it!
Hi,
tl;dr:
Is there a theoretic way to recover data from the phone after:
1. deleting /storage folder
2. and then rooting (which means factory reset?)
If there is a theoretic way to recover it from the bits, is there a way to take a snapshot of the current state of the bit, so I can (in theory) recover the media in the future?
Long version:
First of all I know I'm very stupid..
Yesterday I've deleted my /storage folder since in first glance it looked empty.
Then I figured out what did I do, so I tried to recover the information.
I've searched the web for an application that does that and I found one that required rooting the phone, so I rooted the phone which means I made factory reset.
Then I tried to recover but it didn't manage to recover the photos and videos.. (it did recover whatsapp photos and some other things but not from the dcim folder).
I tried then several different applications that may not ask for rooting the phone so maybe I made a mistake by doing that (not sure that they wouldn't request for rooting either) but no success with that...
I'm willing to pay money to save that data but do you think it's not recoverable anymore?
I also called the 3 biggest recovery companies in my country, 2 of them told me that they don't think it's possible and one agreed to take it to their labs for a small price and then give me an offer.
If there is a theoretic way to recover it from the bits, is there a way to take a snapshot of the current state of the bit, so I can (in theory) recover the media in the future?
I'm very desperate and would be very thankful for your help
PeroPy said:
Hi,
tl;dr:
Is there a theoretic way to recover data from the phone after:
1. deleting /storage folder
2. and then rooting (which means factory reset?)
If there is a theoretic way to recover it from the bits, is there a way to take a snapshot of the current state of the bit, so I can (in theory) recover the media in the future?
Long version:
First of all I know I'm very stupid..
Yesterday I've deleted my /storage folder since in first glance it looked empty.
Then I figured out what did I do, so I tried to recover the information.
I've searched the web for an application that does that and I found one that required rooting the phone, so I rooted the phone which means I made factory reset.
Then I tried to recover but it didn't manage to recover the photos and videos.. (it did recover whatsapp photos and some other things but not from the dcim folder).
I tried then several different applications that may not ask for rooting the phone so maybe I made a mistake by doing that (not sure that they wouldn't request for rooting either) but no success with that...
I'm willing to pay money to save that data but do you think it's not recoverable anymore?
I also called the 3 biggest recovery companies in my country, 2 of them told me that they don't think it's possible and one agreed to take it to their labs for a small price and then give me an offer.
If there is a theoretic way to recover it from the bits, is there a way to take a snapshot of the current state of the bit, so I can (in theory) recover the media in the future?
I'm very desperate and would be very thankful for your help
Click to expand...
Click to collapse
try Undeleter from play store..worked for me on N4..never tried on OPO
atulclassic said:
try Undeleter from play store..worked for me on N4..never tried on OPO
Click to expand...
Click to collapse
Didn't work :crying:
You might give DiskDigger a shot. I never tried it though.
PeroPy said:
Didn't work :crying:
Click to expand...
Click to collapse
are you rooted since undeleter requires root
atulclassic said:
are you rooted since undeleter requires root
Click to expand...
Click to collapse
I'm...
After few weeks of working on that, I didn't make it to recover any of my photos/videos/whatsapp chat history (the things that were most important to me)
I tried several stuff, apperently all of the recovery programs that using the adb to directly connect to the phone through the PC doesn't work well enough, as well as the programs that works from the device...
I tried this article:
http://www.dflund.se/~jokke/androidfilerecovery/
but it didn't work for some reason...
Then I tried that one :
http://forum.xda-developers.com/gal...de-internal-memory-data-recovery-yes-t1994705
I used a centos VM to get a image of the device partiotns the way they suggested (I couldn't make the busybox work).
I mapped that file as hard disk
I tried to use 'Recuva' it seems like it managed to restore files but something apperantly went wrong and the files wasn't helpful...
I tried to use 'easeus data recovery' it worked better, it found around 20k files.. There were alot of directories and I didn't look up at it so much but it recoverd alot of photos which I think were from the whatsapp media.
Incase someone who made the same mistake by deleting the 'storage' folder, get to this post, I recommend to turn off the phone immidietly and find a way to do that without rooting the device.. (although it might be impossible since as far as I know all of the methods I used were depends on a rooted device, but I didn't look up on this since the first thing I done is to root my device - which might be the mistake)...
I've been using TWRP for several years now but am having trouble with the A/B partitioning on the new Android phones like the Pixel 2. I am creating a back up of all the preselected entries. I've created and seen several backups this way but whenever I try to restore them, I wind up with an invalid partition error. I'm sure that I must be missing some simple step but I don't know what it is. Can anyone tell me what I'm doing wrong?
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.