Hello XDA,
I have my nexus 5 and before i start hacking, I would like your advice on what to do first.
For example, save the EFS folder (I did a full backup with TWRP) .
What else?
The most important thing to do is read the pinned (stickies) threads in the general forum. That way if something does go wrong you'll know what to do. Sounds like you've already made a nandroid, good
Related
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!
Hey there,
not sure if this is the right forum but I'll try.
Before unlocking the Bootloader I created a backup using PC Companion and MyPhoneExplorer.
Please take a look at the Filesystem and let me know if there is a chance to get the TA.img out of this.,
Thanks and best regards,
Oliver
Pretty sure there's no way to do so. Otherwise the whole "root - backup TA"-procedure would've been obsolete.
I guess your DRM keys are lost.
PS: This is a question so next time please post in Q&A (even if you're unsure about that, a dev section is nearly never the right place )
I've used twrp a couple times now don't understand the basic file structure of Android and what folders contain what.
If someone direct me to explanation of this it would be greatly appreciated.
I want to know the folder structure and be explained there basic content.
When using TWRP, to backup up or restore, I'm not sure what folders to select to be backed up or to restore and the concequence of selection the wrong ones.
I am Currently using Lg G3 T-Mobil d851
Hi,
Every device is different, so you must keep that in mind when reading anything. But here is a general Android info guide....post 2 talks about recovery,
http://forum.xda-developers.com/android/general/guide-everything-want-to-t2914047
And this thread explains more, including what each partition is,
http://forum.xda-developers.com/galaxy-s2/general/ref-cwm-clockworkmode-menu-options-t1542857 (A Galaxy S2 thread...)
Good luck!
Edit: Do not flash anything not made for your specific device. Always keep that in Mind.
Hi Everyone,
I am new to XDA, and I am really proud to be in this community.
I have created this thread to discuss about the current situation with backup of data in Android, as I did not find any thread which covers my specific concerns. This is meant to be part discussion, part rant, part guide, etc.
Now to the actual scenario. I have a Moto G (2014), which used to run stock unrooted 6.0, and I used a combination of Helium (free version), manual file backup, and import/export options from various apps to back up my data. I recently flashed the official 14.1 Lineage OS ROM with GApps Pico and Lineage OS su package to root. All went well, and I could restore the backups as planned. SMS restore did not work, but I did not bother much about that.
Now, if I try to use Helium to backup my apps, it shows me an error. No detail is provided about the error. On digging further into the ADB backup feature (which is the underlying technique for Helium), I found that I can not even backup the data to the .ab files everyone talks about. I came by a blog which advised creating the backup using .adb extension, and it worked for one or two apps. In all probability, .ab has been replaced by .adb files - experts can suggest, I can not find anything online.
Now came the second twist. I wanted to backup a game which does not support cloud save. And it apparently saves the app data in /data/app, which ADB backup probably does not support - again, experts can enlighten me on this. I noticed that apps saving in /data/data were getting backed up, while the /data/app one was not.
Now the question may arise that since I am rooted, I can easily access these backups through file system or Titanium, without the need for ADB backup. But I am really worried about a scenario when I have to buy a new phone (the current one is already running for 3+ years). I am really wary of rooting a new phone and losing the warranty in the process. In such cases, root based backups can not be restored to the new phone. To validate this, I tried to restore a specific save file to my unrooted tablet, but could not get in even using ADB shell (this may seem foolish, but I thought since ADB backup can access /data/data, may be ADB shell too can access the protected partitions).
So, after this long exercise, my finding is that, unless we are rooted, better forget the backup. It makes me very uneasy to know that I can not carry over my progress in a game to another phone because the developer does not support cloud save (even cloud saves are not full proof, but I will rant about that some other day).
Is there something I am missing? Or is this the scenario all over? And if it is, why can't a ten year old platform provide such a basic feature? And finally, if there is some tool/technique which lets me backup/restore data on an unrooted device, please point me to that.
I believe XDA is the only place I can put these questions/rants forward. Thanks for reading.
Please ask your question only in one place :good: I answered you here https://forum.xda-developers.com/showthread.php?t=2717159&p=75474972
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.