Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

[Q] Missing folders/ Possible 1/2 SDS/ access files

OP general.email

24th May 2014, 03:26 PM   |  #1  
OP Junior Member
Thanks Meter: 0
 
3 posts
Join Date:Joined: Sep 2011
Hi

I wonder if someone could advise me.

I have been having a problem with my Galaxy S3 9300. FW 4.0.4
The problem started with the phone rebooting randomly only when on charge at night..
This happend several time until yesterday when I found the phone powerred off in the morning.
When I tried powering the phone up it went into a continuous loop of samsung logo the 3 splash screen and so on.
I was able to get it to boot into download mode sometimes but could not get it to boot into recovery mode even after many attempts.

Eventually it booted up but it appeared to perform a system/factory reset (un asked for).
Now the phone will boot but all my files are missing.
When i look at the used space (via task manager) there is approximately 6GB free of 11GB.
When I calculate how much data is in all the visible directories visible there is ony about 100 MB.

I have spoken to Samsung and they have agreed that I can send it back for repair.
I would like to be able to retrieve my data (if possible) before i send it back to samsung.

The data i have lost may now be in a directory called "data" in the root of the device but I cannot access it without rooting (and risking warranty)

I have tried to backup the entire phone (hopeing that this would be a complete backup) using the Java/abd method and have managed to create backups varying in size from 120mb to 282mb.

Using the method below I have then tried to unpack the backup.ab file to a tar file but the process keeps failing with warnings

http://forum.xda-developers.com/show....php?t=2011811

such as

C:\Users\Admin\Downloads\android-backup-extractor-20130526-bin\android-backup-ex
tractor-20130526-bin>java -jar abe.jar unpack backup.ab backup.tar titts
Strong AES encryption enabled
Magic: ANDROID BACKUP
Version: 1
Compressed: 1
Algorithm: AES-256
Exception in thread "main" java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknow n Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Un known Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.jdt.internal.jarinjarloader.JarRsrcLoa der.main(JarRsrcLoa
der.java:58)
Caused by: java.lang.RuntimeException: javax.crypto.BadPaddingException: Given f
inal block not properly padded
at org.nick.abe.AndroidBackup.extractAsTar(AndroidBac kup.java:320)
at org.nick.abe.Main.main(Main.java:58)
... 5 more
Caused by: javax.crypto.BadPaddingException: Given final block not properly padd
ed
at com.sun.crypto.provider.CipherCore.doFinal(CipherC ore.java:966)
at com.sun.crypto.provider.CipherCore.doFinal(CipherC ore.java:824)
at com.sun.crypto.provider.AESCipher.engineDoFinal(AE SCipher.java:436)
at javax.crypto.Cipher.doFinal(Cipher.java:2121)
at org.nick.abe.AndroidBackup.extractAsTar(AndroidBac kup.java:247)
... 6 more

C:\Users\Admin\Downloads\android-backup-extractor-20130526-bin\android-backup-ex
tractor-20130526-bin>

I guess my quetsions are

Would this type of backup ever backup the entire 11 or 16GB of the internal memory or just select parts?
The largets backup file is only 280 mb?

Is it likely that my data is lost? (currently seems to be occupying space but is not visible)

Are ther any other options that I should try?

Thanks for any help recieved
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes