DRM Keys / Files from Backup (not nandroid) - Xperia Z3 Q&A, Help & Troubleshooting

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 )

Related

The important things to do? (like to save the EFS folder)

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

[Completed] Back up help

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. ?

[Completed] is this right place to post new thread?i m really not getting idea where to post.help

hi guys,
first, i m all time thankful to these developer guys, you make mobile world so genius, yeah it was never genius,
second, something i learn and something i want to learn more is about android always, but here is my question below that is really important. i don't know if it really make sense or not but i would like to know your opinion.
question :- i see there is a way to push files into device without rooting it. is it secure? it is safe? i guess yes. than how can i push titanium backup(data only) of particular app into my device?
example : - i myself after learning lot about apk tool and all that, modded "whatsapp" successfully and which is out of this world according to me, lately i cam to know there is already one called whatsapp GB, but mine is mine. (right now i don't have rooted device so couldn't send screenshot), but what i am trying to figure out is, i can install my modded apk on my non-rooted device and can run it either, problem comes when it is about registering number, what i really thought that if i can push titanium backup of my modded whatsapp.apk (data only - taken perviously when i had rooted device) to this non rooted device via ADB, than i didn't need to root my device ever, and so for any other app that is modded by me or any developers can be executed on non rooted device.
pros - if this is possible than i guess People won't need to root device, will not loose warranties, will not loose device by bricking it, will get out of a procedure of root methods, no one will ask more about root method, soft brick, hard brick, boot loader issues and many more questions like that i guess.
there will left only one tutorial than if this is possible and it will be like this - how to use adb?(step by step : beginner to black hat).
if this is possible than what we need? proper method of how to use adb, most of people easily can learn how to use adb but most of tutorial misses some points like how to push file by changing r/w permission, and where to put new data backup or files in device like some tutorial i have seen gives only command line but people actually don't know where to put the file like /data/data and than what?
Developers and Rooted device owner will become God in fact in this case because they can lead the rest in right path.
is this possible? or am i ridiculously making no sense?
This is not the right place.
You were already advised to post in the Ask any Query Newbie Friendly thread last month.
Please post there with all relevant details.
Thanks and thread closed

File/Data Recovery on unrooted stock P20 Pro CLT-L29 [HELP]

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!

Backup problems and questions

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.

Categories

Resources