Damn you data! Problem with creating a backup. - Desire HD Q&A, Help & Troubleshooting

Hello. As a happy owner of a DHD, I thought that I could try Kitkat, for one day or two, as I use my phone daily and a stable rom is a must.
For now I'm stuck with CM10.1, but I'm looking forward to the new release.
Anyway, I wanted to create a backup and neither CWM 5.8 Touch or TWRP 2.6.3 go past creating a backup of /data.
CWM just says Error: Could not back up image of /data or something like that, and TWRP says Backup Complete and Failed in red, below it.
Any ideas?
No, I don't have too much apps, TWRP says the ones I want to back up are as following:
Boot (4 MB)
Cache (76 MB)
Data (371 MB)
Android Secure (75 MB)
System (343 MB)
Over 10GB of free space on my microsd card (32GB, class 10), so it's not lack of space.
Help, I'd love to check out Kitkat and Ubuntu Touch...

Fix permissions
maltazar1 said:
Hello. As a happy owner of a DHD, I thought that I could try Kitkat, for one day or two, as I use my phone daily and a stable rom is a must.
For now I'm stuck with CM10.1, but I'm looking forward to the new release.
Anyway, I wanted to create a backup and neither CWM 5.8 Touch or TWRP 2.6.3 go past creating a backup of /data.
CWM just says Error: Could not back up image of /data or something like that, and TWRP says Backup Complete and Failed in red, below it.
Any ideas?
No, I don't have too much apps, TWRP says the ones I want to back up are as following:
Boot (4 MB)
Cache (76 MB)
Data (371 MB)
Android Secure (75 MB)
System (343 MB)
Over 10GB of free space on my microsd card (32GB, class 10), so it's not lack of space.
Help, I'd love to check out Kitkat and Ubuntu Touch...
Click to expand...
Click to collapse
First fix permissions in TWRP recovery advanced tab.. then try backing up again.. If u can boot use backup software like titanium backup to backup app data and settings... You can restore the settings too..

gkprashu said:
First fix permissions in TWRP recovery advanced tab.. then try backing up again.. If u can boot use backup software like titanium backup to backup app data and settings... You can restore the settings too..
Click to expand...
Click to collapse
I know about the possibility of using Titanium Backup, don't worry, the thing is that I wanted to see if I can just use the nand backup once, to make everything simpler.
I'll try the permissions and see, thanks for the tip
Edit:
Fixed permissions without problems, didn't work, same thing.

Related

[Q] Custom MTD Partitions: nothing done ?

As I often have problem of internal memory (not enough),
I tried to apply on my Wildfire the Custom MTD Partitions, as explained here:
http://forum.xda-developers.com/showthread.php?t=1233340
(and which seems very interesting)
But even all steps seems to do something, it doesn't have any impact on the size of the memory...
I tried to apply this size of memory: 145 10 (mtdpartmap.txt)
In order, I did this:
backup, reboot to CMW Recovery, Nandroid Backup, copy the 3 files needed on the SDCard,
format /cache, then format /data, then format /system, then perform a Wipe Data / Factory Reset, then flashed recovery zip, then Reboot Recovery, then Restore the nandroid backup
=> Remark: at the end of the retore of backup, I had an error: "Error while formatting /sd-ext!" (don't know if it's normal)
Then I flashed the boot zip, and finally reboot the Wildfire.
But when I'm checking the memory, sizes are the sames: 183 interal (including 40 for cache).
What I did wrong ?
HTC Wildfire S-Off, CM7 n215
Recovery: 4.0.0.2
S2E used
Make sure your not naming the txt mtdpartmap.txt.txt only have 1 .txt at end.
Sent from my HTC Wildfire using XDA App
Yes, as I saw that someone did it, I verified it.
I tested without any extension too (only mtdpartmap), but result was the same.
I will try again, by changing the values-number in the file...
Maybe an additional question: inthe topic is written:
"When you flash a new ROM, you WILL lose the new settings ("partially"). To overcome this, after flashing your new ROM, flash the boot-v1.5.8-Beta-CustomMTD_S attachment immediately after flashing the ROM before restarting your device."
Does it mean that I should do these operations each time I want to install the last build of cm7 ?
Yes, you have to flash the 'boot' attachment only everytime you flash a new nightly (or a new ROM, or even restore an old ROM, for that matter). If you don't, the device will not boot. (This is applicable even if you do not wipe before flashing a new nightly)
For your issue, although I can't really seem to figure out what the issue is, I would say try flashing a fresh install once just to check whether the procedure itself works or not.
If it still doesn't work after a fresh ROM install, try with the older version of the Custom MTD Script: (Although this shouldn't really be the problem)
http://db.tt/JjGxneZD
http://db.tt/C5noTQl9
this happened to me, but i realized rooted phone doesn't mean s-off, double check it has s-off?
I can solve this issue lol i think. Do this order instead
:backup, reboot to CMW Recovery, Nandroid Backup, copy the 3 files needed on the SDCard
Wipe Data / Factory Reset
Flash bravo-recovery-v1.5.8-CustomMTD.zip
format /cache, then format /data, then format /system
Reboot Recovery, then Restore the nandroid backup
BEFORE REBOOT:Flash bravo-boot-v1.5.8-CustomMTD.zip
Now should work. Well this is how i do it and works. I did the order you said the first few times
I hope this helps
Thx to all for your help.
Yes, my wildfire is S-OFF, I verified again.
About the version v1.5.8, I got it, and will install it quietly in the order you indicated below, I will inform you if it's ok by this ;-)
I just tested in this order, and I'm blocked at the end on the blank screen HTC.
But, little question: I used the files recovery-v1.5.8-Beta-CustomMTD_S.zip et boot-v1.5.8-Beta-CustomMTD_S.zip (so tagged as beta). Are they the sames files than the ones you used ?
HTC Wildfire S-Off
HBOOT 6.01.1002, CM7 n228
S2E used
Just for info:
finally I just tested again the same order, but I flashed an new build instead of to restore my last backup.
It booted correctly, and as I can see, I have now more memory available.
Many thx
Now, I have to restore my apps and data (thx titanium )
flippy12 said:
Just for info:
finally I just tested again the same order, but I flashed an new build instead of to restore my last backup.
It booted correctly, and as I can see, I have now more memory available.
Many thx
Now, I have to restore my apps and data (thx titanium )
Click to expand...
Click to collapse
Damned, I talked too quickly.
This didn't impact the memory, even I flashed MTD for 145 10, I still have the sotck format memory
Only once have I had problems loading custom mtd values,I tried for hours and figured out it was the cwm 2.5.0.7 version which was causing problems cos as soon as I tried with 3.2.0.0 it applied 1st time. Have you tried different cwm?
sent from my wilderbeast:buzz
Which cmw are u using? I used version 5.0.2.0
Sent from my HTC Wildfire using xda premium
Ah yes, interesting point...
On ROM Manager (4.7.0.5), I see that CWM is 5.0.2.0.
In recovery mode (used to backup/restore for this operation) , CWM is v4.0.0.5.
Does this version a correct one, or should I upgrade it to the 5.0.2.0 ?
flippy12 said:
Ah yes, interesting point...
On ROM Manager (4.7.0.5), I see that CWM is 5.0.2.0.
In recovery mode (used to backup/restore for this operation) , CWM is v4.0.0.5.
Does this version a correct one, or should I upgrade it to the 5.0.2.0 ?
Click to expand...
Click to collapse
In order to ignore (solve I mean) this problem of CWM version, I flashed directly the version 5.0.2.0 by the terminal: now it's ok in recovery mode too.
So, I will start again this afternoon the MTD update..
Many thx, I think this time I'm in a good way to success the update
I will give you news...
Mtd certainly works with cwm 5.0.2.0 so you shouldn't have any problems.
sent from my wilderbeast:buzz
Finally, yesterday, I started all since the beginning:
downloaded again the files, installed CM7.1.0.1, followed the described procedure for MTD, and it's ok, I have the Power of ... my wildfire
Again, thx for your help, and I don't forget to thank 3xeno for the guide
Same problem with Custom MTD Partitions
I have flash the boot and recovery files. I have made a nandroid backup i restore it. The mtd file looks like : mtd 170 22 . The rom memory is 512 /system & /cache partitions have only 192 mb. Memory for my applications is only 274 mb. In "About Phone" says i have 118/310 (free/avail).Where it's manager of application i have 245 used and 29 free.I should have 55 mb free.. bot no. Rest of my memory to 512 where it is? Should i delete the nandroid backup? Danke!
amNezic# said:
I have flash the boot and recovery files. I have made a nandroid backup i restore it. The mtd file looks like : mtd 170 22 . The rom memory is 512 /system & /cache partitions have only 192 mb. Memory for my applications is only 274 mb. In "About Phone" says i have 118/310 (free/avail).Where it's manager of application i have 245 used and 29 free.I should have 55 mb free.. bot no. Rest of my memory to 512 where it is? Should i delete the nandroid backup? Danke!
Click to expand...
Click to collapse
Its 512MB and not 512MIB/MO. Hence, the actual usable capacity is actually 483MB instead of 512MB (If I am not mistaken). (The analogy is similar to any flash drive / hard disk you buy - the actual formatted capacity is lower than the rated capacity)

[Q] Desire GSM / CM7.1 / App2SD / Market issues

Hi all.
I've been running CM7.1 on my Desire GSM for a couple of weeks without any issues. Tonight I tried partitioning my SD card to get more app space and I seem to have come unstuck.
Here's the process I used...
Full nandroid backup using ClockworkMod recovery
Wipe data & cache, install CM7.1 stable and GApps from zip on SD
After first run, reboot into recovery
Partition SD card from ClockworkMod Recovery menu - partition size 1024 MB, swap size 0 MB
Reboot & attempt to access Market
At this point I get a host of errors - Google Talk begins to complain that it can't login to my account (never used Google Talk so this is the first time it's even come to my attention), and anything I try to download from the Market gives me a "[app name] could not be downloaded due to an error" message.
At this point I copied the .apk file I had backed up for Titanium Backup to my SD card and attempted to install manually - the install claimed to work, but Titanium Backup was not then available from my app drawer, as though it hadn't been installed at all.
My suspicion is that somehow I've cocked up the partitioning and the system is unable to read or write sd-ext. But I can't see that I've done anything wrong - though I'm new to all this, so there's every chance that I've missed something obvious.
Right now I'm restoring from my last Nandroid backup since, well, I need my phone and this can wait for the time being.
Any help that anyone can offer is appreciated.
Miz.
Flash this DarkTremor A2SD Script - http://box.net/files#/files/0/f/121132533/1/f_981313987
Then install A2SD Gui from market and set everything you like.
Cheers. Can't access that script though - "The item you are trying to access has either been deleted or is unavailable to you."
Will install A2SDGUI next chance I get.
A2SD Gui will not work without the script.
Try this link: http://www.box.net/shared/y9m9qap51mekqvl2kk29
Thanks, will give it a shot and report back on the results.
Worked like a charm. Thanks for the info, all looking great now - including oodles of app space.
Miz.
Sent from my HTC Desire using XDA App
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Much appreciated, but we're done now.

[Q] [CM10] Bootloop just after startup

I hope this is the right subforum, there are _so_ many q-q
Hello,
Yesterday I was up to surfing on my GNex running CM10 nightly 2012-08-2?, but it just hung, vibrated, showed me the Google logo and booted up again. This is not unusual since it is a very early build, but when it was up again and demanded my PIN, I could hardly enter 3 digits when it hung and rebooted again. After 6 times it really annoyed me and I pulled out the battery.
I tried booting in Safe Mode, but that didn't work either. So I wiped system and both caches, flashed the same build again, same problem
I can imagine that wiping data would help, but my last backup is quite a few weeks old and I don't want to lose my data so this would be the very last solution.
I hope someone will be able to help me
qsuscs
Oh, maybe this could be important: I use ClockworkMod Touch 6.0.1.0
You could try to flash the newest nightly and see if that works, but in the end I think you are going to have wipe your data. You could make a backup from cwm and try wiping than restoring the backup. I don't know if that would help any but it could be worth a shot.
And dont restore app/system data.
Sent from my i9250
If you can still get into the recovery, you can run a backup and then restore apps/data from a nandroid via titanium backup once you get it up and running.
Nandroid does not really work.
Code:
ClockworkMod Recovery v6.0.1.0
SD Card space free: 7426MB
Backing up boot image...
Backing up recovery image...
Backing up system...
Freeing space...
Done freeing space.
Backing up data...
Error while making a backup image of /data!
Does anyone know why it doesn't, or maybe another backup solution?
Could I do a backup with another recovery? Or could flashing anotherr recovery even cause data loss?
Triple post hope you can forgive me
So I flashed TWRP. Nandroid didn't work there, too, but I think I know the reason: /data needs to be mountet read-only for the backup, but this is impossible when it is written to the internal storage (/data/media). And since neither TWRP nor ClockworkMod have a TCP stack, I'll need an USB-OTG-adaptor and an USB flash drive. Luckily, I know someone who has one, gonna ask him tomorrow...

[Q] help recovering with TWRP after failed ROM flash

I've found myself stuck trying to flash a ROM. I'm a newbie, this was my first attempt at something like this, I though I read enough about the process but I guess I screwed up something. I will try to be to the point.
Phone: Samsung Galaxy S3 AT&T i747
Rooted phone with Casual, installed ROM Toolbox and purchased the pro upgrade.
installed TWRP 2.5 and made a nandroid backup, the only place this backup existed was in internal storage.
used ROM toolbox to backup user apps and user data
selected cyanogenmod 10.1 RC5 from within ROM Toolbox and there was a requester for gapps and a checked the box for that also. When the DL was complete I installed the ROM queue with those two items and I checked the boxes Wipe Data & Cache and Wipe dalvic-cache.
Phone went to recovery mode (i guess) and appeared to clear the memory and load the new rom, the phone rebooted and I got the cyanogenmod boot screen but then it went to a requester saying:
Unfortunately , the process com.google.process.gapps has stopped.
When you hit ok you get:
Unfortunately, setup wizard has stopped.
this requester never goes away, just keeps popping up when you hit ok.
So I removed the battery and booted the phone in recovery mode and try to restore but the restore nandroid file in not shown. If I hit the center button in the restore window it says "updating partition details" but never returns.
Whenever you power it up normally now you end up in this gapps loop.
My searching suggested I may have tried to install the wrong version of google apps somehow. What are my options for trying to recover from this? Does my backup still exist somewhere?
If process.gapps is your only warning you can try to reflash the gapps zip from here. http://goo.im/gapps/gapps-jb-20130301-signed.zip If this does not fix your problem, you will have to head deeper into the rabbit hold
You can look for your back with a file explorer. Should be in sdcard/TWRP/BACKUPS/******** (random number). If you dont see them here, check your ext-sd in the same location. If you don't see them, they are gone. Do a Nandroid backup now just to be sure you have one. You should chose to back it up to external in TWRP. As for your FC problem, it would appear that you have not wiped fully. You will likely need to factory reset. the problem is this will remove everything. Titanium back up is a great product for situations like this. If you have used it, you can transfer your backup from the internal storage while connected to your pc. Also copy your DCIM folder as it will contain your photos. This is why you will need to do another Nandroid, because worst case scenario, you can just restore this one.
Thanks for the reply. I will try to reflash the gapps file from the external as soon I can download it, the site is having some trouble right now. I made another Nandroid of the phones current state and stored it to external. I did also have Titanium backup and had backups of the whole system with it. Unfortunately they are also only on the internal storage.
Re-installing the gapps zip file off the extSD from within TWRP did the trick. All the data and backups I created are also still there and are now backed up in several places.
Something that compounded the problem was the 64GB sd card I have for the phone. I was not able to mount it on either of my linux mint machines or an XP machine. Some oddness with the exFAT file system on it, I used a 4GB card I had laying around and it worked fine.
Thank you for the help, the phone is now running CM which is what I wanted and I learned a few things too.
theaxis695 said:
Re-installing the gapps zip file off the extSD from within TWRP did the trick. All the data and backups I created are also still there and are now backed up in several places.
Something that compounded the problem was the 64GB sd card I have for the phone. I was not able to mount it on either of my linux mint machines or an XP machine. Some oddness with the exFAT file system on it, I used a 4GB card I had laying around and it worked fine.
Thank you for the help, the phone is now running CM which is what I wanted and I learned a few things too.
Click to expand...
Click to collapse
I just bought a 64GB card as well. You may be having troubles mounting it due to a partition that comes factory in the SD. If this is the case, you can look at post #57 on the following page http://forum.xda-developers.com/showthread.php?t=1915385&page=6
It helped me tremendously.

**URGENT** TWRP states NO OS INSTALLED

Hello all-
In the process of trying to upgrade to OOS 5. I made sure to make a backup of the entire system (system image) in TWRP before proceeding. I also backed up the Boot image and Modems. I had the entire OOS 5 rom ready to flash but before doing so I elected t wipe Dalvik/Cache, Cache, Data & System as I always thought you have to do a fresh clean install when changing versions (7.1.1 to 8.0). The first error I encountered was that it couldn't flash the file. Then when I tried to restore my backup...it does the process with no errors yet when I try to reboot I am told no OS installed. What has happened and what can I do since I always make these backups to be safe?
Thanks all!
Plug your phone on a PC (with the phone in recovery mode), move your backup (sdcard/TWRP/backup) on your PC to keep it safe. Next follow the mega unbrick method 2 (just Google it) on OnePlus forum, update your phone to the version that you were and reflash TWRP and copy your backup from your PC to your phone (in the same location than before) and try to restore your backup.
Error installing OOS 5
Thanks all! I thought a System Image backup was all I needed and had no idea I also had to restore my Boot Image backup. Once I restored that backup I was good to go. Oddly though I didn't have all my apps and data on the phone like I thought the system image backup would have. Honestly I don't care as long as I have a phone again.
On a side note, I have the full OOS 5 ROM on my phone and when I try to flash it I receive an error. The error message states as if the file os for a One Plus 3 and that it cant confirm what my device is? I have always downloaded the full ROMS from OP site and nver had issues upgrading in the past. Any ideas? Does the version of my TWRP matter? Please advise.
DroidJay123 said:
Thanks all! I thought a System Image backup was all I needed and had no idea I also had to restore my Boot Image backup. Once I restored that backup I was good to go. Oddly though I didn't have all my apps and data on the phone like I thought the system image backup would have. Honestly I don't care as long as I have a phone again.
On a side note, I have the full OOS 5 ROM on my phone and when I try to flash it I receive an error. The error message states as if the file os for a One Plus 3 and that it cant confirm what my device is? I have always downloaded the full ROMS from OP site and nver had issues upgrading in the past. Any ideas? Does the version of my TWRP matter? Please advise.
Click to expand...
Click to collapse
System image is rarely useful, it's a full Byte by Byte backup of the system partition ( meaning even the empty Bytes are saved). System partition means that boot one isn't concerned. And system partition means that data partition isn't concerned either, so no user apps or data.
Better to stick to /boot /system and /data backup.
You must have latest official TWRP 3.2 for Oreo ROMs. Or blue_spark latest (8.61 version see blue_spark kernel thread OP)
Striatum_bdr said:
System image is rarely useful, it's a full Byte by Byte backup of the system partition ( meaning even the empty Bytes are saved). System partition means that boot one isn't concerned. And system partition means that data partition isn't concerned either, so no user apps or data.
Better to stick to /boot /system and /data backup.
You must have latest official TWRP 3.2 for Oreo ROMs. Or blue_spark latest (8.61 version see blue_spark kernel thread OP)
Click to expand...
Click to collapse
Thanks man! Good information to have moving forward. No sense in backing up partitions that are not useful and only take up space. Can I update to TWRP 3.2 right in the TWRP app or should I download image and flash within TWRP? I am currently on SU 2.82....is that compatible with Android O?
DroidJay123 said:
Thanks man! Good information to have moving forward. No sense in backing up partitions that are not useful and only take up space. Can I update to TWRP 3.2 right in the TWRP app or should I download image and flash within TWRP? I am currently on SU 2.82....is that compatible with Android O?
Click to expand...
Click to collapse
Yes update from within TWRP. I think superSu 2.85 should be good or Magisk 14.0

Categories

Resources