Please guide me for Nandroid backup.
I am using HTC HD2.
Thank you.
ajsam4u said:
Please guide me for Nandroid backup.
I am using HTC HD2.
Thank you.
Click to expand...
Click to collapse
Your best bet is probably to use Clockworkmod / Clockworkrecovery... If you check this thread you can get that installed and do a full NAND backup/restore. If you don't already have CWM/CWR installed and you want to backup your current ROM then you won't want to run DFT and flash anything until AFTER you backup from CWR. To do this, copy the files in the copy_to_sd_root to your SD card root and boot into MAGLDR. Then select the option to boot AD SD and it should boot into CWR. You can then do a full NAND backup.
Thank you
I did the backup finally
Digital Outcast said:
Your best bet is probably to use Clockworkmod / Clockworkrecovery... If you check this thread you can get that installed and do a full NAND backup/restore. If you don't already have CWM/CWR installed and you want to backup your current ROM then you won't want to run DFT and flash anything until AFTER you backup from CWR. To do this, copy the files in the copy_to_sd_root to your SD card root and boot into MAGLDR. Then select the option to boot AD SD and it should boot into CWR. You can then do a full NAND backup.
Click to expand...
Click to collapse
Please help I cannot find copy_sd_root folder? I think I'm missing something, sorry if being thick...
direkt auf die Karte kopieren es ist keine Ordner
[QUOTE = magicianhumphrey; 18747823] Bitte Helfen Kann Ich nicht Finden copy_sd_root Ordner? Ich Glaube, ich bin Etwas fehlt, sorry, WENN zu **** ...[/ QUOTE]
Related
Hello,
ich have the backupstore from Titaniumbackup on my external micro-sdcard. Titaniumbackup cannot write in this folder. When i move the backupstore to the internal sdcard i have no problems with TB. With a filemanager (root explorer, es exploerer) i have no problems with the external sdcard.
Is this a bug in TB, Tiamat or Android 3.2?
with best regards
Michael
atamig said:
Hello,
ich have the backupstore from Titaniumbackup on my external micro-sdcard. Titaniumbackup cannot write in this folder. When i move the backupstore to the internal sdcard i have no problems with TB. With a filemanager (root explorer, es exploerer) i have no problems with the external sdcard.
Is this a bug in TB, Tiamat or Android 3.2?
with best regards
Michael
Click to expand...
Click to collapse
You have the wrong version of Clockworkmod Recovery installed. You have v4.0.0.x, which is not working with external sdcard.
You need to flash Tiamat v3.2.0.0 R4c--this is especially for the Xoom.
Hello,
is this a recovery Rom? have you a link for me?
Thank you for your help
okantomi said:
You have the wrong version of Clockworkmod Recovery installed. You have v4.0.0.x, which is not working with external sdcard.
You need to flash Tiamat v3.2.0.0 R4c--this is especially for the Xoom.
Click to expand...
Click to collapse
atamig said:
Hello,
is this a recovery Rom? have you a link for me?
Thank you for your help
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1074979
thanks, i have found this file an flashed it. But i think you have understand me.
I do my backups online with titaniumbackup. When i move the backupfolder to the erternal sdcard the backupsoftware cannot writes on this card. Only on the internal sdcard.
greetings
michael
okantomi said:
http://forum.xda-developers.com/showthread.php?t=1074979
Click to expand...
Click to collapse
Not sure exactly what your problem is. My Titanium backups are on my sdcard and have no problems backing up or restoring from the sdcard. On Titanium go to preferences and change your back up folder location to /mnt/external1/TitaniumBackup.
ggrant3876 said:
Not sure exactly what your problem is. My Titanium backups are on my sdcard and have no problems backing up or restoring from the sdcard. On Titanium go to preferences and change your back up folder location to /mnt/external1/TitaniumBackup.
Click to expand...
Click to collapse
Exactly. If you can't find the mnt/external1 folder, just hit the back button once or twice.
If TB sees it a read only, use this first to mount sd as writable
http://forum.xda-developers.com/showthread.php?t=1173195
Hello,
thank you the problem is fixed...
ed.dark said:
If TB sees it a read only, use this first to mount sd as writable
http://forum.xda-developers.com/showthread.php?t=1173195
Click to expand...
Click to collapse
hello guys i tried to install rom manager from market and flashed but it is not compatible with magdlr and now when i go on magdlr option 8 (ad recovery) it says Invalid Boot Header Image
i don't want to re install the rom again (typhon) and i don't have a backup, how can i fix the cwm?
thanks for your help
erick3000 said:
hello guys i tried to install rom manager from market and flashed but it is not compatible with magdlr and now when i go on magdlr option 8 (ad recovery) it says Invalid Boot Header Image
i don't want to re install the rom again (typhon) and i don't have a backup, how can i fix the cwm?
thanks for your help
Click to expand...
Click to collapse
You cant.
Get Titanium backup pro (backup user/system apps/data)
Get SMS Backup Pro (Backup sms)
etc etc
Repartition magldr to get CWM back, flash rom and then restore.
TheATHEiST said:
You cant.
Get Titanium backup pro (backup user/system apps/data)
Get SMS Backup Pro (Backup sms)
etc etc
Repartition magldr to get CWM back, flash rom and then restore.
Click to expand...
Click to collapse
wow so there is no way ha....
Thanks for your help buddy
edit - oops, my bad, corrected
In the android nand section, titled something like "clockworkrecovery, nand,SD, ver 5.0.2 yes/no stable" or something, (currently top post
Get both
recovery_5.0.2.6_leo_sd.zip
and
recovery_5.0.2.6_leo_CWR.zip
Extract and copy the SD card ver onto SD card (copy the two files to SD, done)
And then copy the whole cwr.zip to SD card too.
Then, into magldr, "ad SD" will boot into the cwm files you placed on SD, and choose instal zip from SD,,, choose zip,, and select the cwm.zip you also placed on SD.
This will write the cwm image into the recovery partition without reflashing the cwm partition layout, so nothing lost.
[02 Nov][RECOVERY][NAND|SD][cLK|MAGLDR] ClockworkMod Recovery 5.0.2.6 "YES/NO" STABLE
download the first two links
flash_image.zip
and
recovery_5.0.2.6_leo_sd.zip
unpack teh two files from recovery_5.0.2.6_leo_sd.zip onto your sd card, and copy the whole flash_image.zip to sd card.
enter magldr
select 'boot ad sd' which will start cwm but from your sd card, from there you choose 'instal from zip - select zip' and select the flash_image.zip, which will reinstall cwm into the recovery partition on your nand, and now you should find that magldr 8 - ad recovery now works, and your rom hasnt been touched. plus you now have the latest cwm.
samsamuel said:
yes there is a way, go to the thread
[02 Nov][RECOVERY][NAND|SD][cLK|MAGLDR] ClockworkMod Recovery 5.0.2.6 "YES/NO" STABLE
download the first two links
flash_image.zip
and
recovery_5.0.2.6_leo_sd.zip
unpack teh two files from recovery_5.0.2.6_leo_sd.zip onto your sd card, and copy the whole flash_image.zip to sd card.
enter magldr
select 'boot ad sd' which will start cwm but from your sd card, from there you choose 'instal from zip - select zip' and select the flash_image.zip, which will reinstall cwm into the recovery partition on your nand, and now you should find that magldr 8 - ad recovery now works, and your rom hasnt been touched. plus you now have the latest cwm.
Click to expand...
Click to collapse
You Made my Day buddy!!!
.*takes a bow*.
i did everything but on cwm when i try to install the flash image zip it says installing update.... installation aborted....
help
perhaps recovery_5.0.2.6_leo_CWR.zip should work?
yea sorry, you are right, its the 2nd and 3rd images you download, , you boot to the sd one (like you have ) and flash the cwm one. My mistake.
see also http://forum.xda-developers.com/showthread.php?t=1337663&
samsamuel said:
yea sorry, you are right, its the 2nd and 3rd images you download, , you boot to the sd one (like you have ) and flash the cwm one. My mistake.
see also http://forum.xda-developers.com/showthread.php?t=1337663&
Click to expand...
Click to collapse
it worked!
aaaaaand relax.
Please, confirm if I get this right - the only way to make Rom manager work with HD2 is to use CLK bootloader, is that right. I had similar troubles to these decribed in the above posts and solved them in similar manner. I dont want to go all the way and install CLK and rom, restore back-ups and see it is too not working with Rom manager.
hi,
I have ClockworkMod Recovery v4.0.0.0 on it and would like to test some Roms.
However, I would like to return any time to my present rom.
i want to know how "powerful" is the recovery function.
Here are my questions:
-everything is stored ... only files on the SD(fat) I have to safe by myself?
-the Ext3 or Ext4 partition will backed up?
-make it problems that I have a swap partition?
-what is with the layout of the NAND. can i chang it for a other rom?
-how can I check what NAND layout currently on it?
-Can I import a backup that was created with a older version of ClockworkMod Recovery ?
-where the backup is saved?
a lot of questions
Hier meine "fragenwürdige" punkte
-wird wirklich alles gespeichert... Ich geh davon aus das alles was auf der SD(fat) ist ich selber sichern muß.
-wird die Ext3 oder Ext4 partition mit gesichert.
-macht es probleme das ich eine Swap partition habe
-wie schaut es mit der Partitionierung des NAND aus. Ich muß wahrscheinlich vor den wiederherstellen das selbe Layout aufspielen welches ich auch beim flashen drauf hatte.
-wie kann ich rausfinden welches NAND-layout ich momentan drauf habe
-Kann ich mit einer neueren Version von ClockworkMod Recovery ein backup was mit einer ältern Version erstellt worden ist einspielen
-wo wird das Backup gespeichert?
CWM Backs up everything including SD-EXT partition. It even goes so far as to have backed up the last score I was on in Fruit Ninja, whilst I was in the middle of a game. I can only assume it can be restored on different versions of CWM. The backup is stored in a folder on your SD card called 'clockworkmod' with the name of the zip being the date of the backup. They take up a lot of space (depending on the number of apps. Mine took up 0.8Gb each) so if you have a small SD you might need to delete old backups before making a new one.
As for your NAND partition size, why not just check the OP of the ROM you flashed? To change it for other ROMs just flash a new partition size over the old one, although this will delete all of your data.
Hi. I'm using latest kernel merruk 2.5 developer edition and i can't get link2sd work. The problem is the link2sd says error when i'm select partition format ext2, 3 or 4. Doesnt matter do I format second partition as ext2, 3 or 4.
Error is: "mount script cannot be created. mount: mounting /dev/block/vold179:2 on /data/sdext2 failed: invalid argument ext4 may not be supported on your device. Try FAT32 on the second partition."
I deleted some files from root (that was named "...a2d...' or "...app2sd..." and form init.d 00banner and 1 other script) but still problem.
Tryed on jellyblast v3 and hyperion (now hyperion)
Help pleaseeeeeeeee
I use a2sdx on merruk v2.5 dev 5 edition work fine :thumbup:
Sent from my GT-S5360 using xda premium
How u did ur partion ....???
With cwm or any other method...???
Sent from my GT-S5360 using xda app-developers app
I tried with cwm from merruk and it formated to ext4 and via mini tool from pc (ext3 & ext4) and i repartition sd card via pc and result the same
Sent from my GT-S5360 using xda premium
Don't use minitool to partion ur sdcard.....format it and partion it using cwm....then link2sd will nt create problem....
Sent from my GT-S5360 using xda app-developers app
Use a2sdx its a good one and easy to use :thumbup:
Sent from my GT-S5360 using xda premium
Yep, use CWM to partition, its simple and works perfect.
And BTW, you are NOT supposed to format as ext4 in mini tool, you should format as ext2/3 and it auto mounts as ext4
Ok. I see it was problem with sdcard. Now it is good formated.
So what i must do to have second partition as sd-ext4 on merruk 2.5?
Select ext4 in Link2sd but format only ext2/3 in minitool or by using CWM
Solved!
All works. I fomatted sdcard by other way.
Problem Solved
kael2404 said:
Hi. I'm using latest kernel merruk 2.5 developer edition and i can't get link2sd work. The problem is the link2sd says error when i'm select partition format ext2, 3 or 4. Doesnt matter do I format second partition as ext2, 3 or 4.
Error is: "mount script cannot be created. mount: mounting /dev/block/vold179:2 on /data/sdext2 failed: invalid argument ext4 may not be supported on your device. Try FAT32 on the second partition."
I deleted some files from root (that was named "...a2d...' or "...app2sd..." and form init.d 00banner and 1 other script) but still problem.
Tryed on jellyblast v3 and hyperion (now hyperion)
Help pleaseeeeeeeee
Click to expand...
Click to collapse
Ok, so i had the same problem as you, I searched around the net, and I found the solution. You just need to set your 2nd partition to fat 32 and you're set. I hope you understood that.
Pls give me a thanks, thank you
I used ext2 on merruk 2.5 before,
Try partitioning to ext2
this post is approved by the national potato safety regulation
cant mound sd-ext
hallo und frohes neues jahr ich hoffe mir kann jemand helfen. wenn ich merruk 2.5 via odin installiere habe ich zwar link to sd aber nicht das oc-uc support. wenn ich via cwm installiere habe zwar oc-uc support aber linkt to sd mountet nicht die partition egal wie formatiert. ext2 ext3 ext4 und fat32 ich habe keine lust schon wieder irgendwas zu flashen wie installiere ich init d wenn merruk 2.5 auf stock rom bererits läuft?
danke im vorraus
Hi folks,
I recently upgraded my rooted Galaxy S4 (I9505) from CM12.1 to CM13, so I now have Marshmallow installed. Before the upgrade I made a backup on my external sd card with TWRP 3.0.2. Upgrading to Marshmallow went smooth and so I made another backup after installing CM13.
Yesterday I tried to make a backup but the backup on the external sd card failed. I tried it at least ten times. Most of the time I had some errors but sometimes there was no error shown in the log but the backup files were not saved on the external sd card. I've attached the complete recovery.log, here is an excerpt from the log:
Code:
* MD5 erstellt.
Durchschnittliche Sicherungsgeschwindigkeit für Dateisysteme: 13 MB/sek
Durchschnittliche Sicherungsgeschwindigkeit für abgebildete Laufwerke: 10 MB/sek
Fehler beim Öffnen: '/external_sd/TWRP/BACKUPS/a19a120c/2016-07-27--20-28-45_cm_jfltexx-userdebug_6.0.1_MOB30R_251a6113e//�?�Q?^??.?E�' (
I:Real error: Unable to stat '/external_sd/TWRP/BACKUPS/a19a120c/2016-07-27--20-28-45_cm_jfltexx-userdebug_6.0.1_MOB30R_251a6113e//�?�Q?^?
Fehler beim Öffnen: '/external_sd/TWRP/BACKUPS/a19a120c/2016-07-27--20-28-45_cm_jfltexx-userdebug_6.0.1_MOB30R_251a6113e//"�F?�&EQ.|??' (
I:Real error: Unable to stat '/external_sd/TWRP/BACKUPS/a19a120c/2016-07-27--20-28-45_cm_jfltexx-userdebug_6.0.1_MOB30R_251a6113e//"�F?�&E
Fehler beim Öffnen: '/external_sd/TWRP/BACKUPS/a19a120c/2016-07-27--20-28-45_cm_jfltexx-userdebug_6.0.1_MOB30R_251a6113e//����[email protected]?E)
I:Real error: Unable to stat '/external_sd/TWRP/BACKUPS/a19a120c/2016-07-27--20-28-45_cm_jfltexx-userdebug_6.0.1_MOB30R_251a6113e//����[email protected]
Fehler beim Öffnen: '/external_sd/TWRP/BACKUPS/a19a120c/2016-07-27--20-28-45_cm_jfltexx-userdebug_6.0.1_MOB30R_251a6113e//?rG?????.\N�' (
I:Real error: Unable to stat '/external_sd/TWRP/BACKUPS/a19a120c/2016-07-27--20-28-45_cm_jfltexx-userdebug_6.0.1_MOB30R_251a6113e//?rG????
Fehler beim Öffnen: '/external_sd/TWRP/BACKUPS/a19a120c/2016-07-27--20-28-45_cm_jfltexx-userdebug_6.0.1_MOB30R_251a6113e//k�?�p?�!.?e<' (
I:Real error: Unable to stat '/external_sd/TWRP/BACKUPS/a19a120c/2016-07-27--20-28-45_cm_jfltexx-userdebug_6.0.1_MOB30R_251a6113e//k�?�p?�
Fehler beim Öffnen: '/external_sd/TWRP/BACKUPS/a19a120c/2016-07-27--20-28-45_cm_jfltexx-userdebug_6.0.1_MOB30R_251a6113e//-)
"Fehler beim Öffnen" is German for I guess "Error while opening…"
The sd card works in the way that I can put photos and music on it. It is mounted as follows:
Code:
[email protected]:/mnt/sdcard # mount | grep 2015-1707
/dev/block/vold/public:179_33 on /mnt/media_rw/2015-1707 type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/fuse on /mnt/runtime/default/2015-1707 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/read/2015-1707 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/write/2015-1707 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/2015-1707 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other
Yesterday I tried to change permissions on the sd card by setting write permissions like this:
Code:
[email protected]:/mnt # chmod g +w media_rw/
Nothing changed.
Furthermore I tried the app "SDFix: KitKat Writable MicroSD" to fix the permission problem. If I had read the description more carefully I would have saved some time. The app had no effect and said that it couldn't fix the permission problem so I uninstalled it immediately. Today I tried the Xposed module "Marshmallow SD fix" and gave permission for Nandroid Manager but that didn't help either. But that was what I expected because I think (!) that this has nothing to do with TWRP.
So my question is: What do I have to do to make TWRP backup my data on the external sc card?
Your help is very much appreciated. If you need further information just let me know.
Greeting, Jens
Whatever you do in the ROM won't have any effect on the recovery.
My suggestion is to make the backup on the internal and then move it to the external.
Okay, that would work but space is limited on the internal card.
I'm wondering why it worked with the first backup. So I hope there's another way to get it working directly.
Thanks, Jens
jenzuslongus said:
Okay, that would work but space is limited on the internal card.
I'm wondering why it worked with the first backup. So I hope there's another way to get it working directly.
Thanks, Jens
Click to expand...
Click to collapse
Are there any other ideas to get the backup working on the external card?
Maybe downgrade twrp?
audit13 said:
Maybe downgrade twrp?
Click to expand...
Click to collapse
I've tested with TWRP 2.8.7.0 with no success. It says something like:
Code:
E:dd if=/dev/block/mmcblk0p20 of='/external_sd/TWRP/BACKUPS/a19a120c/2016-09-12--07-30-26_cm_jfltexx-userdebug_6.0.1_MOB30R_251a6113e//boot.emmc.win' bs=2097152 cout=5
process ended with ERROR=1
E:backup file size for '/external_sd/TWRP/BACKUPS/a19a120c/2016-09-12--07-30-26_cm_jfltexx-userdebug_6.0.1_MOB30R_251a6113e//boot.emmc.win' is 0 bytes.
Looks like still the same error. Any other hints?
jenzuslongus said:
I've tested with TWRP 2.8.7.0 with no success. It says something like:
Code:
E:dd if=/dev/block/mmcblk0p20 of='/external_sd/TWRP/BACKUPS/a19a120c/2016-09-12--07-30-26_cm_jfltexx-userdebug_6.0.1_MOB30R_251a6113e//boot.emmc.win' bs=2097152 cout=5
process ended with ERROR=1
E:backup file size for '/external_sd/TWRP/BACKUPS/a19a120c/2016-09-12--07-30-26_cm_jfltexx-userdebug_6.0.1_MOB30R_251a6113e//boot.emmc.win' is 0 bytes.
Looks like still the same error. Any other hints?
Click to expand...
Click to collapse
The only other option I have is to change the format of your microSD card.
Mine is vFAT, if I'm not mistaken, and it works great.