Database Users

[Q] Nandroid backup error / Wildfire

Hi guys,
Once again, thanks to MartinEve and the whole unrevoked team for the work they've made on Wildfire rooting.
I've just used unrevoked to root my wildfire. Seems alright cause :
> id cmd tells I'm root
> titanium backup tells root permission is given
Cool
But... I try to do a nandroid backup from the clockworkmod recovery and it says : "Error while dumping boot image!"
Do you have any idea ?
Thx a lot

Solved...
It was due to a problem on my sdcard (was not able to write in the /sdcard folder even from windows). I had to delete some files and then nandroid backup was available.

mmr41 said:
Solved...
It was due to a problem on my sdcard (was not able to write in the /sdcard folder even from windows). I had to delete some files and then nandroid backup was available.
Click to expand...
Click to collapse
Why dont you post your problem and its solution here for others to benefit from it
http://forum.xda-developers.com/showthread.php?t=742518

Unable to restore backup.

I backed up 4.1.2 using cwm. I flashed eclipse 3.0 and now trying to restore backup. Cwm is not able to find clockworkmod folder. When I search for a zip file I only see 3 directories. 0, legacy and some obb.
Sent from my SAMSUNG-SGH-I747 using xda premium

have a look here:
http://forum.xda-developers.com/showthread.php?t=1991657
i had the same problem but I haven't done that fix, i did the lazy thing and manually moved my backup from /data/media to the clockworkmod/backup on my sdcard. then CWM was able to find it.

Thanks but how do I restore everything to pre 4.2 CWM and directory structure and not this 0/ and legacy/ stuff.

metaldood said:
Thanks but how do I restore everything to pre 4.2 CWM and directory structure and not this 0/ and legacy/ stuff.
Click to expand...
Click to collapse
do you have the wifi-only version? i'm a little new to this device, but i believe restoring your 4.1.2 nandroid will take you back to where you wanna be? otherwise if you wanna do a complete factory restore, you can reflash the factory image:
http://forum.xda-developers.com/showthread.php?t=1907796

Yea wifi only. I am doing a factory reset now. Sucks that 4.2 messed up the directory structure.

Backup to computer

I have a rooted nexus 7 and I know how to do a nandroid backup and a Titanium Pro Backup for the apps. But all these would be useless if the tablet is lost or stolen. So, what does one need to copy to a separate computer to be able to restore in case of disaster?
I imagine copying the nandroid and Titanium backups should be the minimum (assuming I can find where these files are located in the nexus..... ), but what else should be copied to a different computer? Are the nandroid and Titanium backups alone enough to restore everything or do I need to copy more of the root, sdcard, other folders, etc?
Appreciate advice from the experts.
Sent from my Nexus 7 using Tapatalk 2

I make regular backups of my devices by just running:
adb pull /data/media
That pulls in all nandroids, titanium backups, pictures/videos, etc

AW: Backup to computer
I would backup all apps+data using titanium and then
Code:
adb pull /sdcard/
for all your music etc
Sent from my Nexus 7 running Android 4.2.2

I had the same "problem" and so I am currently writing a Java application which enables a remote backup, i.e. you can either backup whole images of the different partitions, or backup filesystems as tar files. Some days ago I wrote a small blog entry. The sources you can find on my GitHub account, but I can also provide some binaries.

Thank you all. But I am a newbie and come from the windows world and the device I would backup to is a windows laptop. So where do I enter the adb command?
Can I manually copy the sdcard contents to a folder in the windows laptop? If so, should this manual usb file copy to the laptop include the root?
Sent from my Nexus 7 using Tapatalk 2

AndDiSa said:
I had the same "problem" and so I am currently writing a Java application which enables a remote backup, i.e. you can either backup whole images of the different partitions, or backup filesystems as tar files. Some days ago I wrote a small blog entry. The sources you can find on my GitHub account, but I can also provide some binaries.
Click to expand...
Click to collapse
I read your blog entry and you are talking exactly about what I need. But because I am a newbie from the windows world the rest is over my head.
I have TWRP on my Nexus, so the OTG nandroid sounds simpler for me. I have read elsewhere that nandroid backups copied manually to a windows device via usb frequently fail when used to restore. Is that why you are uncomfortable with the TWRP OTG nandroid?
Thanks.
Sent from my Nexus 7 using Tapatalk 2

Anderson2 said:
Thank you all. But I am a newbie and come from the windows world and the device I would backup to is a windows laptop. So where do I enter the adb command?
Can I manually copy the sdcard contents to a folder in the windows laptop? If so, should this manual usb file copy to the laptop include the root?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
You can't manually copy over 'root'
You can use windows, you know windows has a command prompt too right?
Sent from my Galaxy Nexus

I have Titanium Backup upload the backups to Dropbox after they run on a scheduled basis. I occasionally copy nandroids over but those aren't as important.
Sent from my SGH-I777 using xda premium

korockinout13 said:
I have Titanium Backup upload the backups to Dropbox after they run on a scheduled basis.
Click to expand...
Click to collapse
This
Then copy contents of /sdcard to your computer using any method you are comfortable with. If you have the drivers installed your device will show up as a storage device in my Computer.
Note 2 - Nexus 7 - Charge - Player 5.0 - Fascinate
Read twice, flash once

Pirateghost said:
You can't manually copy over 'root'
Click to expand...
Click to collapse
Aha! I didn't know I could not manually copy root. That explains things. I had assumed that if I was rooted and mounted root I could manually copy and paste it. Now I understand.
Thank you.
Sent from my Nexus 7 using Tapatalk 2

[DEV] Recover of EFS without Backup

Hi Folks,
well i've just managed to recover a Galaxy S3 /EFS without JTAG and without ANY backup other than a dd of the damaged EFS partition which is /dev/block/mmcblk0p3
I am looking for other users with the following conditions
you must have a copy of you efs partition before any modifications , eg. as soon as you efs went wrong you dd'ed /dev/block/mmcblk0p3 and kept a copy before trying anything else. If you worked on the /efs before or select efs clear in oding then this wont work.
I am not going to post the solution yet, it requires more research but it's a possible solution, may even transfer to other devices with exynos and a /efs partition.
Possible ways to confirm efs damage
1. system stays on Galaxy s3 logo and does not show animated boot logo
2. cwm wont mount /efs
3. e3 recovery wont list csc files
if the above is the same as here then let me know.
No PM's please, i want to keep the work public.
darkspr1te
Sorry MODS, please move to Samsung Galaxy SIII , general, miss-post i was tired

darkspr1te said:
Hi Folks,
well i've just managed to recover a Galaxy S3 /EFS without JTAG and without ANY backup other than a dd of the damaged EFS partition which is /dev/block/mmcblk0p3
I am looking for other users with the following conditions
you must have a copy of you efs partition before any modifications , eg. as soon as you efs went wrong you dd'ed /dev/block/mmcblk0p3 and kept a copy before trying anything else. If you worked on the /efs before or select efs clear in oding then this wont work.
I am not going to post the solution yet, it requires more research but it's a possible solution, may even transfer to other devices with exynos and a /efs partition.
Possible ways to confirm efs damage
1. system stays on Galaxy s3 logo and does not show animated boot logo
2. cwm wont mount /efs
3. e3 recovery wont list csc files
if the above is the same as here then let me know.
No PM's please, i want to keep the work public.
darkspr1te
Sorry MODS, please move to Samsung Galaxy SIII , general, miss-post i was tired
Click to expand...
Click to collapse
hi this same problem has happened to me on my s4.
i have all your above listed problems.
However i do have a backup of my efs folder.
please help, thanks

I'm curious with the solution..
Cause many people had problem with efs and not having efs backup...
Sent from my GT-N7100 using xda app-developers app

starscream0 said:
hi this same problem has happened to me on my s4.
i have all your above listed problems.
However i do have a backup of my efs folder.
please help, thanks
Click to expand...
Click to collapse
I've only just got my first bricked S4 in yesterday and only completed it's screen replacement today. The screen is only damged due to owner giving up on it and litting it sit on his desk util something was dropped on it.
Anyway, my point of this is I am not ready to do S4 debrick as I 'am still working on S3.
The key behind my 'possible' recovery method is my solution involves searching for certain MAGIC's in the /EFS backup and also knowing exactly where in the efs image data would be.
For example, key areas of a EFS are in the same sector of the memory each time when looking at a mmcblk0p3 backup image,
i will use mac address as a example.
in the 5 so far efs backups i've examined the mac address is at offset 0x30000, so even if you cannot read the actual efs partition and using fsck on the mmcblk0p3 fail, my part one trick involves just going to 0x30000 and reading the data back. without the efs file system being involved. The same trick i used to recovery the blown boot sector and partition table of the SHV-E160L.
the second trick is to look for keywords within the backup img, example lets say the IMEI always had 0xAA 0xAA 0xAA before it, and the data required was 400 byte, we simply look for 0xAA 0xAA 0xAA in the file and copy it and the next 400 bytes.
the final trick I wont release yet, jumping the gun (as people do) will result in a JTAG brick, it's not perfect, its not a one click solution that we all want, but it's early days yet, but the method does work, i've 5 sammy's in front of me to prove it.
My rep in the Korean galaxy note section should prove I am not threading for likes too
Final note, Its a work in progress and I am using the forum to post my thoughts and look for Guinea pigs and attract other developers to documents the Samsung /efs system.
I am aware that parts are hashed and encrypted, the goal is not decrypting it but to recover the information to revive the device.
I am expecting users to share their /EFS backups with me, but I will not share those files with others to protect the users IMEI,
my issue is i don't have enough differing /efs files to build a bigger picture, what if the file locations was just luck ?
oh, if anyone has a copy of testdisk for arm, please share, i am fighting to get it to compile for arm-eabi-none- grrrrrr.
darkspr1te

Another note: I've not taken into account fragmentation of data in my above post, i was keeping that out of it for now, but i am aware of the EXT2/3 file table setup, how nodes can be split up.

[QUEST] CWM backup from Nexus 4 to System

Hello guys ,
How do i copy the backup created using CWM to my system(laptop) ?
As i understand the latest CWM backups are stored in locations which cannot be accessed by users . Is there any other way it can be achieved ?
Also please do provide the restore procedure for the same.
On nexus 4 running stock kitkat.
CWM version : 6.0.4.3
Any help would be greatly appreciated .

they can be acesses by users, at /data/media/clockworkmod or /sdcard/clockworkmod, u can use root explorer or adb to get them.
₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢₢

Just plug your phone to your system(laptop) and look for the biggest by size folder. That should be your cwm backup. Also mind the name. I am not talking about /Android!!! Just copy it somewhere the regular way and then delete it. The restore is simple but you have to have it back on the same place in the phone's memory. The restore process is carried out from the recovery. GL.
Sent from my Nexus 4 using xda app-developers app