After successfully S-Off'ing my desire I had problems booting the phone after restoring my nandroid backup. A full restore would result in bootloops.
I originally thought this was because the custom Oxygen table I had applied was too small, but on trying others, I had the same result.
In recovery, under advance restore options, I only restored the following elements of the nandroid backup:
sd-ext
system
data
cache
I didn't restore 'boot'.
This prevented the boot-loops and I seem to have my phone functioning as before with nothing missing...
So, my question is, what data was in 'boot' and did I need it?!
If anyone cares to tell me why the full nandroid caused these issues, then please do!
Finally, if the above is answered, I assume I'm ok to flash the custom Oxygen hboot and restore all again other than 'boot'? Users were checking the 'size' of their nandroid backups, but I could work out how to do this?
Thanks in advance.
Data stored in '/boot' is used help in the process of loading the Android OS when you turn on your phone. The '/boot' partition is used to set up all the other partitions (i.e. /data, /cache, /system...). S-OFF just suspends a security feature and puts a new S-OFFed bootloader(this is not in /boot). You have to do a FULL WIPE after performing the S-OFF before doing the full restore.
If you flashed the custom Oxygen HBOOT, then you have to install a new ROM that will fit inside the '/data' or '/system' partition (can't remember which one exactly...I think it's /system). Restoring your previous ROM will cause problems as it may not be able to fit in.
As for checking the size of the nandroid backups, connect the phone to a PC and mount it as the USB Drive. Go into the SD card and under your recovery folder (which will be named as 'ClockworkMod' or to the one you are using) you'll be able to find all your backups. Check their properties....
Appreciate the info, thank you. I think I only flashed a new ROM after my nandroid restore failed... I'll have another go and install fresh ROM straight after the custom hboot.
Thanks again.
Sent from my HTC Desire using XDA Premium App
No worries...
This was extremely valuable info. It restored back to the Backup with out a hitch. Thanks alot. Dude you Rock! Very clever!
Related
I recently upgraded my Amon RA to the latest build (2.3)
I like all the new choices but I'm confused about what I should be backing up when making a Nandroid.
I made one that backed these parts up:
[x] boot
[x] system
[x] data
[x] wimax
Is that good enough? Should I backup recovery too? I understand sd-ext and .android-secure backups will take more space and time to create. But are the ones I listed above pretty much the only essential things if I ever need to flash a backup?
yep...
I would make a backup of just wimax, then there would be no need to back it up again.
Depends on your amount of paranoia about being able to recover. I backup my entire phone, including my SD card, prior to flashing any ROM. So far I haven't had any issues recovering. Granted I'm new to rooting and flashing ROMs...so haven't had enough time to really bork things up.
I know my b/u is over kill, but I'd rather spend the few extra minutes getting everything than find out I missed something if I need to recover.
HTC Evo
Rooted, but still stock...for now
----------------------------------------
The program is designed to work, if it's not, we have a problem.
You are good to go with your backup scheme.
You don't need to backup WiMax every time. Just back it up once, separately, then backup boot, data, and system regularly.
i have four or five nands on my card that i checked every option for. cant hurt...
Thanks for all the replies guys.
I'll take it all into account and do an "in case of catastrophic data loss" backup (in other words, full on backup, full checks)
And keep it to the OP scheme i had for future backups.
@n00bhackin
I'm the same way. Better safe than sorry.
Yep, wimax is a seperate backup.
Before backup, wipe cache and dalvik cache (reduces size of backup file and forces dalvik to be rebuilt when recovered).
At a bare minimum: boot, system, data
If you use apps2sd, backup .android.secure also unless you want to reinstall some apps.
If you use apps2sd to a ext3 partition on your SD, backup SD:ext for the same reasons above.
If your not sure which apps2sd you are using;
1) check on your SD the folder .android.secure, got apps there then its option 1.
2) if you use dark tremors apps2sd, then you know what it does and you back up option 2.
It would be awesome to have a .ini file on the sd with various defaults already enabled.
Maybe next in the next version
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)
Hi !
i have a ROM with A2SD+ on EXT3 partition
1- First i'd like to know if Nandroid Backup make a copy of the EXT3 content .and if so does it restore the EXT3 content as it was ?
2- when i make a Nandroid restore do i have first to make a data,cache, dalvik,sd-ext wipe ?
3- Do i need to flash the ROM before flashing nandroid restore ?
4- if i have changed Radio or partition table does nandroid restore puts everything like at the moment of backup ?
thanks
Hi,
1 yes
2 I do wipe
3 no
4 no
LukenBoy said:
2- when i make a Nandroid restore do i have first to make a data,cache, dalvik,sd-ext wipe ?
Click to expand...
Click to collapse
In fact, it depends. There are few constellations where you don't need to wipe. But, to be on the safe side, just do it. Cause Nandroid restore doesn't restore an image, but files, thus w/o wiping you may end up with unneeded files.
This possibly answers your 4), too.
Greets, Magpie
I got the message like (when backup) sd-ext did not gone with restored files..?
Does anyone knows why..?
Thanks
petar17 said:
I got the message like (when backup) sd-ext did not gone with restored files..?
Click to expand...
Click to collapse
Please post the error message _literally_, cause the one you cited, makes no sense at all. At least for me ...
Greets, Magpie
petar17 said:
I got the message like (when backup) sd-ext did not gone with restored files..?
Does anyone knows why..?
Thanks
Click to expand...
Click to collapse
I think this means, when the nandroid backup is taken, it doesnot include ext backup file. Same thing happend to me.
I did some research on the problem and found a solution which seems to have worked for few people. However I have not tried it myself. I am going to do that though.
Summary of the solution
1.) Download Root Explorer
2.) Enable Root Mode/Mount System
3.) Navigate to /system/
4.) Create a new folder called 'sd'
5.) Ensure you're phone has at least 50% of battery
6.) Reboot and try the backup again.
link: http://android.modaco.com/topic/347662-error-backup-nandroid-ext-with-recovery-22/
When I perform a backup from recovery (or via a front-end such as ROM Manager), what exactly is saved?
Is it like a clone of a hard drive in the PC world?
Does it contain only data, and not the actual ROM?
How should I go about using such a backup when doing a restore? Should a ROM be installed first, followed by the restore? If so, must the ROM match the backup exactly -- that is, must it be the ROM under which the backup was performed in the first place?
kirkers said:
When I perform a backup from recovery (or via a front-end such as ROM Manager), what exactly is saved?
Is it like a clone of a hard drive in the PC world?
Click to expand...
Click to collapse
That's a pretty close analogy. Only difference is I don't think it captures partitions...but I'm not sure about that. (It's not clear to me, for instance, if you did a nandroid of a phone with the EXT4 mod implemented and tried to install it on a phone without the EXT4 mod, exactly how that would play out.)
As an example, though, I took a nandroid of my stock phone immediately after I rooted it and got S-off. I then played around with various CM7, CM9, and JB ROMs for a weekend, but reloaded the stock nandroid Sunday night before going back to work on Monday. (I need a reliable phone for work.)
My phone was restored to exactly the way it was when I took the nandroid snapshot. I had to re-download a handful of app updates and email that had arrived since the time I took the nandroid to "catch up" to the present time, but that's all.
kirkers said:
When I perform a backup from recovery (or via a front-end such as ROM Manager), what exactly is saved?
Is it like a clone of a hard drive in the PC world?
Does it contain only data, and not the actual ROM?
How should I go about using such a backup when doing a restore? Should a ROM be installed first, followed by the restore? If so, must the ROM match the backup exactly -- that is, must it be the ROM under which the backup was performed in the first place?
Click to expand...
Click to collapse
It is everything on your phone at the current time when you made a backup. Including your rom, apps, files, boot animation and e.t.c.
Sent from my EVO using Tapatalk 2
Impact of EXT4 partition on nandroid backup + restore?
sully9292 said:
It is everything on your phone at the current time when you made a backup. Including your rom, apps, files, boot animation and e.t.c.
Click to expand...
Click to collapse
MysticCobra said:
[The PC clone image is] a pretty close analogy. Only difference is I don't think it captures partitions...but I'm not sure about that. (It's not clear to me, for instance, if you did a nandroid of a phone with the EXT4 mod implemented and tried to install it on a phone without the EXT4 mod, exactly how that would play out.)
Click to expand...
Click to collapse
Thanks for the clarifications and the personal experience story. It helps calm my nerves. :fingers-crossed: Now it is clear that the nandroid is a full snapshot, close to being a clone image.
Can anyone address MysticCobra's point about the EXT4 partition?
As a rule, I have followed ROM Manager app's recommendation to partition the sdcard to allow apps to be stored on it. This is what the EXT4 partition is designed to do, as far as I understand such things.
If I format the sdcard with EXT4 (which in my experience wipes out all data on the card), and then restore a nandroid that came from an older EXT4-formatted sdcard of the same size or smaller than the new sdcard, would the nandroid restoration go smoothly?
What would happen if the new sdcard did NOT have an EXT4 partition?
Thanks in advance for further advice.
:good: Cheers!
kirkers said:
Thanks for the clarifications and the personal experience story. It helps calm my nerves. :fingers-crossed: Now it is clear that the nandroid is a full snapshot, close to being a clone image.
Can anyone address MysticCobra's point about the EXT4 partition?
As a rule, I have followed ROM Manager app's recommendation to partition the sdcard to allow apps to be stored on it. This is what the EXT4 partition is designed to do, as far as I understand such things.
If I format the sdcard with EXT4 (which in my experience wipes out all data on the card), and then restore a nandroid that came from an older EXT4-formatted sdcard of the same size or smaller than the new sdcard, would the nandroid restoration go smoothly?
What would happen if the new sdcard did NOT have an EXT4 partition?
Thanks in advance for further advice.
:good: Cheers!
Click to expand...
Click to collapse
Nandroid backup/restores don't touch the sdcard. They backup to the sdcard but the nandroid only handles /system, /data, /data/data, /cache, boot, and recovery.
The ext4 partition is not the same as the ext4 mod that MysticCobra mentioned. The mod converts /data, and /cache to ext4 and changes the ramdisk to mount them as ext4. The no data limit one also disables the mounting /data/data so the phone will share the apps and app data with a 750MB. Your app data is intact with the no data limit mod but a backup is still advised. No wipe updates don't touch the filesystem in /data or /cache but the mod may need to be flashed again for the ROM to boot correctly as the ramdisk is overridden on all updates. Technically with the normal data one you are good on later cm7 and ICS/JB ROMs as it's already ext4.
If you want to undo the mod the best thing is to wipe /data and /cache and reflash the ROM.
For further reading check the first link in the link below:
http://forum.xda-developers.com/showthread.php?t=1623038
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...