Develop Bugs

How do you do a nandroid backup with the Desire?

I have a rooted desire and never really tried restoring a backup and when I finally did I came across this error message:
No SD ext found. skipping backup of SD EXT
Generating MD5 sum
error while checking md5 sum!
chcking md5 sum....
MD5 mismatch!
My SD card has no partition whatsoever and I'm using fake flash by paul. My old phone was a N1 and I had no problem whatsoever doing this before. Is making a backup and restoring in the Desire an entirely different process?
Also how do you automatically backup apps in the Market? Meaning if I switch roms and just logged into my Google account the market would automatically "restore" my old apps. I used to be able to do this once in a while with my old N1 but I couldn't do it consistently. With my Desire I can't do it at all.
Thanks

It will give that error if you have no ext partition on your sd card. If you're not using apps 2 sd then you need not worry about it.
Other than that, try the latest clockwork recovery (2.0.1.4) and try a nandroid backup and restore.
Sent from my HTC Desire using XDA App

Nandroid backup seems to work and I do get to see the file but when I try to restore it fails! Do I need to make an extension for it to work?
What about restoring apps from the marketplace via the internet? Like I said, I've done it a few times with my N1 wherein it automatically restores everything once I log in my Google account.
Thanks

Try creating an ext partition, convert ext2 to ext3. If it fails again, try backing up and restoring using the Nand using the latest Clockwork Recovery (2.0.0.7).
Your apps are linked to your Google account so when you sign in, they should be available for manual download.
You could also backup and restore your apps and data to your sd card using Titanium backup or MyBackup Pro (available from the Marketplace).
Sent from my HTC Desire using XDA App

Apps are indeed linked but how do they become restored automatically? Like I said, I've done it before on my N1 with "applications restored" showing up on the notification bar.
Where do I get the latest clockwork recovery? Tried looking at the forums and came up empty. I just followed Paul's guide for rooting. Still don't understand why I can't restore from a nandroid.
thanks

I am not aware of any method to restore apps automatically from the Marketplace, i do it manually unless using a backup and restore app.
Try reading the fake flash thread on MoDaCo as i remember people had reported the same issue you are experiencing. What version of fake flash are you currently using?
You will find the Clockwork Recovery as an option in the ROM Manager app, which you can download from the Marketplace.
Sent from my HTC Desire using XDA App

kingofthebraves said:
Where do I get the latest clockwork recovery? Tried looking at the forums and came up empty. I just followed Paul's guide for rooting. Still don't understand why I can't restore from a nandroid.
Click to expand...
Click to collapse
The easiest method is to use unreEVOked (link).
The earlier version of unreEVOked installed a much earlier version of clockwork recovery, and I found that the nandroid backup didn't work properly - it would seem to backup (albeit too quickly), but you couldn't restore due to the MD5 problem. I think it didn't actually ever complete the backup and generate the MD5s.
Version 2 hopefully fixes that problem - certainly Nandroid backups take a lot longer!
Regards,
Dave

Thanks guys.
Will look into unrevoked and try to get it to work. I'll also try to update my fake flash. I have been using the very first version when it came out and never really updated it lol

Updated my fake flash and it worked! Thanks guys!
Didn't know that the clockwork recovery was embedded into fake flash. I thought it was just an enabler or something.
Thanks again!

If you use unrEVOked you don't need Fake Flash, or vice versa.
Regards,
Dave

Have still yet to try unrevoked, what exactly does it do when I plug it into my desire? Does it make me run Amon Ra's N1 recovery image? No more screen with the red triangle?

kingofthebraves said:
Have still yet to try unrevoked, what exactly does it do when I plug it into my desire? Does it make me run Amon Ra's N1 recovery image? No more screen with the red triangle?
Click to expand...
Click to collapse
No problem bud, glad it worked out for you
When you enter Recovery, it loads the recovery image straight away, so you get a permanent custom recovery image when you hold power + home.

Will try it out thanks again! Currently experimenting with the Rom manager application. It's pretty neat and u can update the recovery image instantly. I take it as something like an app inside ur phone? Always there in the background waiting to be used?

Hi, is anyone else having the problem that ClockWorkMod 2.5.0.1 just hangs after "Backing up system..." when trying to do a Nandroid backup?
Backup worked fine with 2.0.x.x (the one that came with Unrevoked3), but now I can't seem to complete a backup. Haven't even tried restoring yet...

Trying to run a ROM backup using ROM Manager and Nandriod Backup but both go to a screen with a red triangle
Phone is rooted and running Defrost
I want to update to defrost 6.1
Any other way of backing up the ROM ?
Thanks

BorgCymru said:
Trying to run a ROM backup using ROM Manager and Nandriod Backup but both go to a screen with a red triangle
Phone is rooted and running Defrost
I want to update to defrost 6.1
Any other way of backing up the ROM ?
Thanks
Click to expand...
Click to collapse
Boot in to recovery manually and back up or clear the download cache in rom manager and reflash clockworkmod. If it still fails try to disable signature verification in recovery (under install zip form sd)

I can't get to recovery though thats the problem.
How do you reflash clockworkmod ? Through ROM Manager ?

yes, first option when you open rom manager

Cashe cleared, then I tried to run the update ROM option selected back up and clear data etc.
Went straight to a red triangle, will now try and see about changing this clockworkmod
Thanks.

Ran the re-flash clockwork option, first one on the list, still gets the red triangle of noness.

HELP NEEDED with CWM "error while restoring /data!"

Hey guys,
I have kind of a serious issue right now. I used Touch Recovery 5.8.0.2 and made a full backup today of my whole ROM (2.5GB) before trying out some mods which eventually didn't work. So I decided to wipe and restore the backup I made. No matter what I do I cannot get it to restore my data partition properly. I keep getting "Error while restoring /data!" message, however it does the boot image and system fine but doesn't continue to cache and sd-ext because of the failed data. Whenever I boot it up, some of my apps are missing from the home screen and practically all of them are not working when I launch them (force close). I also get boot up error of Google+ force close, among a bunch of other issues. This is happening even when I try to restore an older backup as well. My device is not working state right now and although I can just restore the stock images to get it working again, it is urgent that I restore my data ASAP! I tried wiping several times and even using the non-touch 5.5.0.4 recovery to restore and same thing keeps happening.
Any help would be highly appreciated!
Please don't tell me my backup is corrupt
Update 1: Eventually I gave up and started from scratch but I have confirmed already this happened on a fresh backup as well, at this time we are trying to figure out what is causing this so I can go back to safely backing up and restoring backups.
Update 2: We have test builds of TWRP Recovery that may have resolved this issue! We need testers!
Please see this post: Link Here
Update 3: We have test builds of ClockworkMod Recovery 6 that may have resolved this issue as well! We need testers!
Please see this post: Link Here
***Always see last few posts on the thread for updates on what we discovered just in case I don't update the OP***

Unfortunately I also have the same error today!
Please help us out.

JayantSparda said:
Unfortunately I also have the same error today!
Please help us out.
Click to expand...
Click to collapse
is your phone encrypted?
are you running stock recovery?
are you running a stock Rom?
have you done a factory reset yet?

Hi Spectre85,
My phone did fine yesterday, I was running AOPK Milestone 3 with FAUX123 kernel.
But when I woke up, my phone looked like it's battery was emtpy.
- When I plugged the phone with the charger, I started the phone again.
- Unfortunately my phone keep looping at the Google screen over and over.
So I pulled the battery and put the battery back again in the phone.
- I went to the bootloader and went to CWM recovery.
Deleted Data, Cache and Dalvike cache.
- Tried to retrieve my backup rom, but keep getting this "Error while restoring /data!" message.
I've tried to install other roms as well, but I still keep getting the bootloop at the Google screen.
Have you guys have any advice for me?

spectre85 said:
is your phone encrypted?
are you running stock recovery?
are you running a stock Rom?
have you done a factory reset yet?
Click to expand...
Click to collapse
For me, no, no (CWM Touch 5.8.0.2), yes (stock rooted 4.0.4), no but my goal is to restore my data not erase it.

I had this happen to me before, what I did was flash a factory image through fast boot and it was fine after.
Sent from my Galaxy Nexus using xda premium

Thanks guys..I flashed the factory image through Fastboot mode and the phone works perfectly again! Too bad I lost all my data, but I'm happier that I have my phone fully functional again

You can't access your backup right? There's no way you can copy the file to your desktop?

mohitrocks said:
You can't access your backup right? There's no way you can copy the file to your desktop?
Click to expand...
Click to collapse
I did copy it. I have full access to the file. Also, just fyi my goal here is not just to get to working state (I'm aware of the stock images) but to actually recover my data. My phone is currently on stock images completely blank and working now.

Fast boot flash the nand images just like u did the stock ones.
Sent from my Galaxy Nexus

bwcorvus said:
Fast boot flash the nand images just like u did the stock ones.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Nanadroid files can be flashed in fastboot? Are you sure? First time I'm hearing this. Doesn't fastboot need .img files? These are .tar files.

Open it up and see if its image...sorry all my recoveries use images.
Sent from my Galaxy Nexus

bwcorvus said:
Open it up and see if its image...sorry all my recoveries use images.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I guess it depends on the recovery version you use. I remember older versions actually had .img files. However 5.5.0.4 and Touch 5.8.0.2 both have ext4.tar files.
Which version of recovery do you use?

If you have root, you can restore your data partition using Titanium Backup. Use "Export from Nandroid Backup" within TB, select the nandroid backup and then select all apps that you want to restore

Immix said:
If you have root, you can restore your data partition using Titanium Backup. Use "Export from Nandroid Backup" within TB, select the nandroid backup and then select all apps that you want to restore
Click to expand...
Click to collapse
Interesting...will this include settings as well like my home screen icon/widget layout, wallpaper, etc?

open1your1eyes0 said:
Interesting...will this include settings as well like my home screen icon/widget layout, wallpaper, etc?
Click to expand...
Click to collapse
Yes. Titanium Backup can restore all your system apps as well as downloaded apps from a nandroid backup. Not as clean as a nandroid restore from CWM but essentially the same thing. But try to see if Titanium Backup can extract your nandroid backup. It all depends on what exactly went wrong with your nandroid backup to begin with. I don't think it restores cache. So not sure about wallpaper.

Immix said:
Yes. Titanium Backup can restore all your system apps as well as downloaded apps from a nandroid backup. Not as clean as a nandroid restore from CWM but essentially the same thing. But try to see if Titanium Backup can extract your nandroid backup. It all depends on what exactly went wrong with your nandroid backup to begin with. I don't think it restores cache. So not sure about wallpaper.
Click to expand...
Click to collapse
You're right. This works great for restore data to select apps (got my notes and game saves back). I think the icon layout is held in the launcher settings, I'm about to try and restore the data to the launcher app and see what happens. I'm making a CWM backup of first of my current state (that's assuming this backup will actually work).
EDIT: Yes! That did it! Widgets position weren't saved but it's ok I only had a few so I manually put them back. Thank you! I never knew TB had the ability to work with nandroid backups.

I guess this now just leaves me figuring out what went wrong with the CWM backup. It happened twice (I have two backups from the same day that won't restore). Does anyone else use CWM Touch 5.8.0.2 and have successful backups? I would experiment to see if it works now but I don't want to end up with a corrupt backup and redo everything again.

Yes with me its the same thing my data its corrupt is even worse every time I do a nanobackup and restarted my phone the phone freezes on the boot logo and I have to go back to recovery trying to use my backups but I can't so I have to flash a new from again and start from the beginning again!!!! Anybody here has the same experience with that ???

So AGAIN, I'm having the same issue. This time on a recovery 5.5.0.4 that used to work for me when I originally got my phone. I think either my data partition might be too big or something but this really needs to fixed pronto. Anyone know how to contact Koush directly in regards to this matter?

Restoring stock nandroid taken from 1.29 Sense problem...

Guys please don't harangue me over the fact there is probably another topic out there. This works PC hasn't got Java enabled and search won't work...
OT: I've had my phone booted and rooted running AOKP IceColdJelly by the right honourable Lord Clockan but as dipstick here forgot to run SMS Backup before doing so I lost a whole tonne of messages I wanted to keep. However I had nandroided my stock rom and as I'm presuming those messages will have been saved as part of that process.
I decided while I am waiting for the next build of IceColdJelly to be released to try restore that nandroid and backup the messages ready to restore to IceColdJelly when I come to flash it again.
On restoring the nandroid this is where my problem lies I rebooted my handset but the phone failed to display the HTC One bootanimation and stuck at a blank screen after the HTC logo where it vibrates.
Have I missed a step? Is the problem due to a conflict somewhere?
I'd appreciate your help and thanks in advance to anyone offering anything constructive.

SB13X said:
Guys please don't harangue me over the fact there is probably another topic out there. This works PC hasn't got Java enabled and search won't work...
OT: I've had my phone booted and rooted running AOKP IceColdJelly by the right honourable Lord Clockan but as dipstick here forgot to run SMS Backup before doing so I lost a whole tonne of messages I wanted to keep. However I had nandroided my stock rom and as I'm presuming those messages will have been saved as part of that process.
I decided while I am waiting for the next build of IceColdJelly to be released to try restore that nandroid and backup the messages ready to restore to IceColdJelly when I come to flash it again.
On restoring the nandroid this is where my problem lies I rebooted my handset but the phone failed to display the HTC One bootanimation and stuck at a blank screen after the HTC logo where it vibrates.
Have I missed a step? Is the problem due to a conflict somewhere?
I'd appreciate your help and thanks in advance to anyone offering anything constructive.
Click to expand...
Click to collapse
Did you flash the boot.img for your nandroid backup?
Sent from my HTC One X using Tapatalk 2

What did you have before the AOKP? if another rom, did you flash the boot.img that you have also in the nandroid?
Try to use the ARHD Super Wipe before restoring, but flash first the kernel thats used in ur nandroid.

PAGOT said:
What did you have before the AOKP? if another rom, did you flash the boot.img that you have also in the nandroid?
Try to use the ARHD Super Wipe before restoring, but flash first the kernel thats used in ur nandroid.
Click to expand...
Click to collapse
Frakking doh, so used to the old DHD I forgot the boot.img requires flashing, how do I extract that from the nandroid of the stock rom?

SB13X said:
Frakking doh, so used to the old DHD I forgot the boot.img requires flashing, how do I extract that from the nandroid of the stock rom?
Click to expand...
Click to collapse
No idea, but if you go to the directory of your backup, what files do you have there? Isnt one of them a boot.img? Btw I am not sure you can flash this . Never did.
But the stock kernel is here arround the forum. Search for user called Vladnosferatu and his threads.

SB13X said:
Frakking doh, so used to the old DHD I forgot the boot.img requires flashing, how do I extract that from the nandroid of the stock rom?
Click to expand...
Click to collapse
You can mount your sdcard in CWM. There should be a folder called CWM or recovery or something similar on the sdcard. Copy the backup to your computer and extract the boot.img from there.
Sent from my HTC One X using Tapatalk 2

PAGOT said:
No idea, but if you go to the directory of your backup, what files do you have there? Isnt one of them a boot.img? Btw I am not sure you can flash this . Never did.
But the stock kernel is here arround the forum. Search for user called Vladnosferatu and his threads.
Click to expand...
Click to collapse
Done it big thanks to you all, you legends!

Galaxy Nexus Toolkit Backup

Hello again.
Since I am under 10 posts and not allowed to participate in the relevant thread plus searching didn't yield any results I am posting here.
After one month of using my nexus I want to play with it and try some custom things that all people talk so much about.Fact is I first want to backup current state where everything works fine in case something goes wrong.
I 've already backed up my apps and their data with Titanium Backup.
Now I need current OS state bootloader, etc.Am I right to believe this is the NANDROID backup? Is this the backup that can bring the phone back to its current state?
Second thing is that the Galaxy Nexus Toolkit v7.8.0 I am using recommends backing up the EFS partition.Did some research that revealed this hidden partition is about the IMEI - I can't understand how such a valuable data isn't hardcoded inside the phone.But nevertheless I would like to know where are those backups (NANDROID and ESF partition) stored (already checked backups folder in toolkit).
My phone's current state is: unlocked bootloader, CWM recovery, rooted and on stock 4.1.1.No mods or any other custom file.
Another question regarding the CWM recovery.How is it possible to go back to the stock recovery? By flashing the stock ROM?
Also from GN Toolkit I flashed CWM Touch but after trying an update through CWM ROM Manager I got the manual version (both 6.0.1).Can I reflash the touch version from Toolkit?
Sorry if some of those questions sound silly but I am new in Android and prefer the safe path.
Thank you in advance.

TR-909 said:
Hello again.
Since I am under 10 posts and not allowed to participate in the relevant thread plus searching didn't yield any results I am posting here.
After one month of using my nexus I want to play with it and try some custom things that all people talk so much about.Fact is I first want to backup current state where everything works fine in case something goes wrong.
I 've already backed up my apps and their data with Titanium Backup.
Now I need current OS state bootloader, etc.Am I right to believe this is the NANDROID backup? Is this the backup that can bring the phone back to its current state?
Second thing is that the Galaxy Nexus Toolkit v7.8.0 I am using recommends backing up the EFS partition.Did some research that revealed this hidden partition is about the IMEI - I can't understand how such a valuable data isn't hardcoded inside the phone.But nevertheless I would like to know where are those backups (NANDROID and ESF partition) stored (already checked backups folder in toolkit).
My phone's current state is: unlocked bootloader, CWM recovery, rooted and on stock 4.1.1.No mods or any other custom file.
Another question regarding the CWM recovery.How is it possible to go back to the stock recovery? By flashing the stock ROM?
Also from GN Toolkit I flashed CWM Touch but after trying an update through CWM ROM Manager I got the manual version (both 6.0.1).Can I reflash the touch version from Toolkit?
Sorry if some of those questions sound silly but I am new in Android and prefer the safe path.
Thank you in advance.
Click to expand...
Click to collapse
toolkit is not a safe path for you.
read these:
http://forum.xda-developers.com/showthread.php?t=1812959
http://forum.xda-developers.com/showthread.php?t=1626895
http://forum.xda-developers.com/showthread.php?t=1529058
http://forum.xda-developers.com/showthread.php?t=1420351
learn how to troubleshoot and search, you'll be a whole lot happier. don't use toolkits.
TR-909 said:
Now I need current OS state bootloader, etc.Am I right to believe this is the NANDROID backup? Is this the backup that can bring the phone back to its current state?
Click to expand...
Click to collapse
nandroid doesn't backup the bootloader. if you ever need to go back to a specific bootloader version (which you won't), it is available online.

bk201doesntexist said:
toolkit is not a safe path for you.
read these:
http://forum.xda-developers.com/showthread.php?t=1812959
http://forum.xda-developers.com/showthread.php?t=1626895
http://forum.xda-developers.com/showthread.php?t=1529058
http://forum.xda-developers.com/showthread.php?t=1420351
learn how to troubleshoot and search, you'll be a whole lot happier. don't use toolkits.
nandroid doesn't backup the bootloader. if you ever need to go back to a specific bootloader version (which you won't), it is available online.
Click to expand...
Click to collapse
That's a lot of reading.
Anyway thanks for pointing me to those threads (I don't mind reading hehe) but still I don't understand why toolkit is so bad.In my view the toolkit just automates a set of commands which otherwise I would have to give through a command prompt.Only good thing I can find avoiding a toolkit, is getting a deeper knowledge on the subject but maybe the risks of doing something wrong are increased (say a typo)?
Anyway let me read those and I may be back.

TR-909 said:
That's a lot of reading.
Anyway thanks for pointing me to those threads (I don't mind reading hehe) but still I don't understand why toolkit is so bad.In my view the toolkit just automates a set of commands which otherwise I would have to give through a command prompt.Only good thing I can find avoiding a toolkit, is getting a deeper knowledge on the subject but maybe the risks of doing something wrong are increased (say a typo)?
Anyway let me read those and I may be back.
Click to expand...
Click to collapse
Toolkit is a automated set of other people's command, programme are coded by humans and human errors are bound to happen, not to mention if something went wrong somewhere, you won't know what went wrong. By doing the steps yourself, you will know exactly what went wrong, and it will simplify things should you have to ask questions here, which you most likely don't have to once you know how to use adb and fastboot, trust me.

Typos while doing your commands won't hurt because it simply will fail and not do anything. Immediately you will know you typed something incorrectly and know you have to do it again. With the kit you will not know at which step it failed so figuring out something will become a task. Doing it yourself sounds like it's longer and difficult but once you do it you will see how easy and simple it is plus you will understand what you did and why.
Sent from my Galaxy Nexus

TR-909 said:
[snip]
Now I need current OS state bootloader, etc.Am I right to believe this is the NANDROID backup? Is this the backup that can bring the phone back to its current state?
Click to expand...
Click to collapse
Yes and yes.
TR-909 said:
Second thing is that the Galaxy Nexus Toolkit v7.8.0 I am using recommends backing up the EFS partition.Did some research that revealed this hidden partition is about the IMEI - I can't understand how such a valuable data isn't hardcoded inside the phone.But nevertheless I would like to know where are those backups (NANDROID and ESF partition) stored (already checked backups folder in toolkit).
Click to expand...
Click to collapse
I won't comment on the toolkit, but nandroid backups are stored in /sdcard/clockworkmod/backup/ on your device.
As for the efs partition, you could back it up, but I don't really see what the necessity of it is. That partition is never written to by any ROM (stock or otherwise), so the only way it will get messed up is if you do something to it.
If you want to back it up on your device, just open a terminal window and type:
su
dd if=/dev/block/platform/omap/omap_hsmmc.0/by-name/efs of=/sdcard/efs.img
That will store it in /sdcard, and then just copy it off your device.
TR-909 said:
Another question regarding the CWM recovery.How is it possible to go back to the stock recovery? By flashing the stock ROM?
Click to expand...
Click to collapse
Just pull the recovery.img file out of the version of the stock factory image that you are currently using, place it in the same directory where you have your fastboot.exe file, reboot your device into fastboot mode and type:
fastboot flash recovery recovery.img
Or, just save it to /sdcard on your device and type the following in a terminal:
su
dd if=/sdcard/recovery.img of=/dev/block/platform/omap/omap_hsmmc.0/by-name/recovery
TR-909 said:
Also from GN Toolkit I flashed CWM Touch but after trying an update through CWM ROM Manager I got the manual version (both 6.0.1).Can I reflash the touch version from Toolkit?
Click to expand...
Click to collapse
Can't help you out with any toolkit, sorry.

Hello efrant.
Seems you are the n00bs hero in here! I was reading your FAQ and threw some basic ADB commands through cmd to see how it feels ,lol.
Well reading made some good, I backed up through CWM but the backup size baffles me - only 21.4MB in total.Is this normal?
Also took a fresh backup with Titanium for all apps and data - this is a lot bigger 728MB in total.Still Storage (in Settings) reports that applications and their data hold 3.54GB.Is there some kind of ultra compression involved?
As for the stock bootloader I found that image (recovery-stock-jro03c-maguro) which I think is for my GN (GSM).I am asking in case something bad happens and go for a warranty claim.In that case I believe I 'll need to flash the stock bootloader, stock ROM and finally lock the bootloader.
As for the EFS partition is it impossible to be harmed? Say File System corruption, sdcard bad blocks, etc?
It's ok.I clearly understand your position on the toolkit and any similar programms out there.It's just they are so "convenient" and "time savers".Still you 're all right that most of the time you do not understand what you are doing when using toolkits.
Thanks to all of you for your great help. :good:
PS - to test my progress I am going to flash stock recovery through flashboot.I just hope I won't mess it up. :fingers-crossed:

To clear a few things:
TR-909 said:
As for the stock bootloader I found that image (recovery-stock-jro03c-maguro) which I think is for my GN (GSM).I am asking in case something bad happens and go for a warranty claim.In that case I believe I 'll need to flash the stock bootloader, stock ROM and finally lock the bootloader.
Click to expand...
Click to collapse
we don't have any custom bootloaders, as of yet.
TR-909 said:
As for the EFS partition is it impossible to be harmed? Say File System corruption, sdcard bad blocks, etc?
Click to expand...
Click to collapse
not impossible, but many many users never had any issues. to be on the safe side, back it up.
TR-909 said:
It's ok.I clearly understand your position on the toolkit and any similar programms out there.It's just they are so "convenient" and "time savers".Still you 're all right that most of the time you do not understand what you are doing when using toolkits.
Thanks to all of you for your great help. :good:
Click to expand...
Click to collapse
glad you understand. just because something is convenient doesn't mean that it's the best for you.
TR-909 said:
PS - to test my progress I am going to flash stock recovery through flashboot.I just hope I won't mess it up. :fingers-crossed:
Click to expand...
Click to collapse
easy. you can't fail with fastboot. like said before, if you type it wrong, it won't go through. :good:
'fastboot flash recovery recovery.img'
done.

Regarding the nandroid, copy off the whole clockworkmod folder.
Will the next nexus have a longer screen?

@bk201doesntexist: yes you 're right I was reffering to the stock recovery image.Thanks for correcting me
@Mach3.2: I 've read just the backup folder is needed (the one with the date and time).
For the sake of learning, I started in ADB then:
adb devices : to check I am online
adb reboot-bootloader: to get into fastboot
fastboot devices: check again status
and then
fastboot recovery recovery-CWM-touch-6.0.1-maguro
blah...
blah...
blah...
Finished and voila CWM touch recovery installed. :victory:
I am going to try with stock recovery but I am trying to find an official source to download it (if any).
EDIT: I see the only way to find the original recovery img is to extract it from the official ROM.So I am downloading from Google a .tgz and will continue from there.
Any comments for my backup sizes?
Now with my backups in hand what is the possible way to verify them? In theory with nandroid (from CWM recovery) and Titanium, I can restore phone in today's state.Right or wrong?
I am thinking of going a bit further flashing the stock ROM again (wiping everything) and then recovering from the backup archives as my next learning exercise.I should obviously backup photos, music, etc but I was wondering if SMS history is taken care by Nandroid or have to use a seperate application.Contacts are in google's server so np on that.
Thanks again.

TR-909 said:
[snip]
Well reading made some good, I backed up through CWM but the backup size baffles me - only 21.4MB in total.Is this normal?
Also took a fresh backup with Titanium for all apps and data - this is a lot bigger 728MB in total.Still Storage (in Settings) reports that applications and their data hold 3.54GB.Is there some kind of ultra compression involved?
Click to expand...
Click to collapse
If you are using the 6-series CWM, it does backups a little differently (incrementally), and stores the backup in two locations in /sdcard/clockworkmod. I personally use 5.5.0.2, which does a full backup and stores it in one location.
TR-909 said:
As for the stock bootloader I found that image (recovery-stock-jro03c-maguro) which I think is for my GN (GSM).I am asking in case something bad happens and go for a warranty claim.In that case I believe I 'll need to flash the stock bootloader, stock ROM and finally lock the bootloader.
Click to expand...
Click to collapse
As was mentioned above, all bootloaders available are stock bootloaders. A list can be found in the bootloader thread (link in my signature).
TR-909 said:
As for the EFS partition is it impossible to be harmed? Say File System corruption, sdcard bad blocks, etc?
Click to expand...
Click to collapse
But if you have bad blocks in the efs partition, you would probably need to get a new device, at which point you have no need for the backup, no? But I guess yes, better safe than sorry.
TR-909 said:
In theory with nandroid (from CWM recovery) and Titanium, I can restore phone in today's state.Right or wrong?
Click to expand...
Click to collapse
With a nandroid alone you can return to today's state.
TR-909 said:
I am thinking of going a bit further flashing the stock ROM again (wiping everything) and then recovering from the backup archives as my next learning exercise.I should obviously backup photos, music, etc but I was wondering if SMS history is taken care by Nandroid or have to use a seperate application.Contacts are in google's server so np on that.
Click to expand...
Click to collapse
Wiping from CWM does not wipe the data you have on /sdcard, so no need to backup photos, music, etc.
SMS will get wiped, but both Titanium and a nandroid will back them up. However, you can use a third-party app (there are many of them) to do it as well, which is simpler actually.

TR-909 said:
@bk201doesntexist: yes you 're right I was reffering to the stock recovery image.Thanks for correcting me
@Mach3.2: I 've read just the backup folder is needed (the one with the date and time).
For the sake of learning, I started in ADB then:
adb devices : to check I am online
adb reboot-bootloader: to get into fastboot
fastboot devices: check again status
and then
fastboot recovery recovery-CWM-touch-6.0.1-maguro
blah...
blah...
blah...
Finished and voila CWM touch recovery installed. :victory:
I am going to try with stock recovery but I am trying to find an official source to download it (if any).
EDIT: I see the only way to find the original recovery img is to extract it from the official ROM.So I am downloading from Google a .tgz and will continue from there.
Any comments for my backup sizes?
Now with my backups in hand what is the possible way to verify them? In theory with nandroid (from CWM recovery) and Titanium, I can restore phone in today's state.Right or wrong?
I am thinking of going a bit further flashing the stock ROM again (wiping everything) and then recovering from the backup archives as my next learning exercise.I should obviously backup photos, music, etc but I was wondering if SMS history is taken care by Nandroid or have to use a seperate application.Contacts are in google's server so np on that.
Thanks again.
Click to expand...
Click to collapse
The backup is just a shell, it's backed up in blobs, so you will need to copy the whole thing off.

You 're both right that in that the CWM recovery "image" is incremental and the base backup is the blops folder - now the total size is 1.75GB which is logical.
@efrant: thanks for clarifying on backup now it all starts making sense.I 've read Titanium Backup can pull individual files (may I call it selective restore) from a Nandroid backup, say a single app and its data.If that is so then the Titanium Backup could be used as a reserve app and that could save me some precious space.
efrant said:
SMS will get wiped, but both Titanium and a nandroid will back them up. However, you can use a third-party app (there are many of them) to do it as well, which is simpler actually.
Click to expand...
Click to collapse
I prefer to use less apps for doing the job so if Nandroid has the data it is fine with me.I hope it isn't that complicated to pull the data out.
@Mach3.2: You were right, my bad.The article I read was about CWM recovery 5.5.0.2 so now I copied the whole thing on PC. :good:

TR-909 said:
[snip]
I prefer to use less apps for doing the job so if Nandroid has the data it is fine with me.I hope it isn't that complicated to pull the data out.
Click to expand...
Click to collapse
The issue is that SMS's are stored as data for a specific system app (I can't remember which one at the moment). If you change ROMs, it is generally not a good idea to restore system apps or system app data via Titanium Backup, as those apps/data could cause some instability. You may get lucky, you may not.

efrant said:
The issue is that SMS's are stored as data for a specific system app (I can't remember which one at the moment). If you change ROMs, it is generally not a good idea to restore system apps or system app data via Titanium Backup, as those apps/data could cause some instability. You may get lucky, you may not.
Click to expand...
Click to collapse
Point taken.:good:
A bit more on the backup subject...
As I can see CWM recovery backups boot image, recovery image and the /system partition.I also saw in one of efrant's posts about different bootloaders but honestly I fail to comprehend the need for flashing a bootloader.
*In your "convert to latest yakju" post you recommend flashing it "5) Optional (NOT optional for n00bs) -- Flash the bootloader: fastboot flash bootloader bootloader-maguro-primela03.img (or whatever the name of the bootloader image that you downloaded)."
** Also the radio partition is a mystery so far.And I 've read a lot of guys talking of better connectivity (be it GSM, 3G, WiFi) through flashing custom (?) radio images.On list to be explored...
The recovery image is pretty straight and the system partition is the one with the OS - now all this can't be 1.7GB unless it backups the userdata partition too.
EDIT: It seems it also backups the data folder (hence the apps) so the size now makes sense.I reverted to 5.5.0.2 because incremental backup is fast and slick but brings two issues: first the "blops structure" gives me problems when I want to transfer those thousands of files via MTP and second it is much more practical when I want to backup completely different "builds" (that is my guess).
Also in between flashing ROMs a standard procedure is recommended about wiping data, clearing dalvik cache, etc
Could you please give me in details the series of tasks needed (or point me to a thread) for properly preparing a custom ROM installation when unlocked and rooted?
About restoration in the "new enviroment" I read this:
"If your bootloader is unlocked: yes, you can root (if you haven't done it already) and use TiB to backup apps + app data. Installing a ROM will not wipe your /sdcard. It's always a good idea to back it up though before a flash. Use TiB to restore apps + appdata to your new ROM. Be careful with system apps and settings, restoring such data can lead to issues."
Am I right in that "illegal" system apps are those painted with red colour in TiB?
Final steps I am going to backup SMS history and find a custom ROM to install.Any ROM recommendations for a "novice user" are welcome...
Off Topic: what would be the adb commands to push/pull folders (or files) from /sdcard to PC (eg. \sdcard\clockworkmod --> C:/Nexus) .Right now I am doing MTP transfers but would prefer the "adb way" if possible.
Thanks a lot for your support and sharing of knowledge!
PS - So much reading!

Wow, that's a lot of questions for one post! I'll try to tackle some of them.
TR-909 said:
As I can see CWM recovery backups boot image, recovery image and the /system partition.I also saw in one of efrant's posts about different bootloaders but honestly I fail to comprehend the need for flashing a bootloader.
*In your "convert to latest yakju" post you recommend flashing it "5) Optional (NOT optional for n00bs) -- Flash the bootloader: fastboot flash bootloader bootloader-maguro-primela03.img (or whatever the name of the bootloader image that you downloaded)."
Click to expand...
Click to collapse
I don't think anyone knows what changes are in each new bootloader revision (given that they are closed source), but some have had issues with running Jelly Bean on bootloaders older than LA03. I guess "newer is better" holds true in this case.
TR-909 said:
** Also the radio partition is a mystery so far.And I 've read a lot of guys talking of better connectivity (be it GSM, 3G, WiFi) through flashing custom (?) radio images.On list to be explored...
Click to expand...
Click to collapse
Again, no one know what changes are made in each radio revision. I personally have not noticed much difference among a lot of the radios, but others have said otherwise. (And no, there are no "custom" radios. All radios are stock -- just from different versions of Android. (A list of radios can be found in the radio link in my signature.)
TR-909 said:
The recovery image is pretty straight and the system partition is the one with the OS - now all this can't be 1.7GB unless it backups the userdata partition too.
EDIT: It seems it also backups the data folder (hence the apps) so the size now makes sense.
Click to expand...
Click to collapse
Yup, it backs up the cache, boot, recovery and system partitions, and everything in /data except /data/media (which is /sdcard).
TR-909 said:
I reverted to 5.5.0.2 because incremental backup is fast and slick but brings two issues: first the "blops structure" gives me problems when I want to transfer those thousands of files via MTP and second it is much more practical when I want to backup completely different "builds" (that is my guess).
Click to expand...
Click to collapse
I also like 5.5.0.2. I found it to be the most compatible, i.e., it has no issues flashing anything (that I have tried anyway), whereas other versions have issues with certain things.
And I personally wouldn't use MTP to transfer files -- it is flaky at best. ADB is much more stable.
TR-909 said:
Also in between flashing ROMs a standard procedure is recommended about wiping data, clearing dalvik cache, etc
Could you please give me in details the series of tasks needed (or point me to a thread) for properly preparing a custom ROM installation when unlocked and rooted?
Click to expand...
Click to collapse
There is not much to do:
1) Download ROM to /sdcard
2) Reboot into recovery
3) Nandroid
4) Wipe /data and /cache
5) Flash ROM
6) Reboot
TR-909 said:
About restoration in the "new enviroment" I read this:
"If your bootloader is unlocked: yes, you can root (if you haven't done it already) and use TiB to backup apps + app data. Installing a ROM will not wipe your /sdcard. It's always a good idea to back it up though before a flash. Use TiB to restore apps + appdata to your new ROM. Be careful with system apps and settings, restoring such data can lead to issues."
Am I right in that "illegal" system apps are those painted with red colour in TiB?
Click to expand...
Click to collapse
I think so. I haven't use TB in a while, so I just checked and it looks like you are correct -- red.
TR-909 said:
Off Topic: what would be the adb commands to push/pull folders (or files) from /sdcard to PC (eg. \sdcard\clockworkmod --> C:/Nexus) .Right now I am doing MTP transfers but would prefer the "adb way" if possible.
Click to expand...
Click to collapse
Have a read of the "basics" link in my signature. ADB is covered there.

Wow that's some great answers and a big motive for me to continue "digging".:good:
I will leave you in peace for the time being as here it's about to dawn.
Big thanks and have a nice day.
PS - To be continued...

There is a article on the main xda site about running a FTP server on your phone, maybe that will transfer the blobs faster than MTP.

Mach3.2 said:
There is a article on the main xda site about running a FTP server on your phone, maybe that will transfer the blobs faster than MTP.
Click to expand...
Click to collapse
Hey mach3.2.
FTP wouldn't help because WLAN (802.11g) can't beat USB 2.0 speeds.In fact it is quite slow for such file sizes.You 're right though in that through ES File Explorer I can send the whole Clockworkmod folder (and the blobs) normally to my PC without the "invisible files" issue I encountered with Windows Explorer and MTP.
Thanks for suggestion!

TR-909 said:
Hey mach3.2.
FTP wouldn't help because WLAN (802.11g) can't beat USB 2.0 speeds.In fact it is quite slow for such file sizes.You 're right though in that through ES File Explorer I can send the whole Clockworkmod folder (and the blobs) normally to my PC without the "invisible files" issue I encountered with Windows Explorer and MTP.
Thanks for suggestion!
Click to expand...
Click to collapse
With MTP, copying using FTP may just be faster
And just to mention, there's 802.11N on you devices, although it's only single stream w/ 1 antenna..

[Q] Anyone else having Nandroid restore problems?

HTC One V [CDMA], Virgin Mobile US, original (pre-OTA) radio version, TWRP recovery
Has anyone else experienced flakiness with Nandroid backups on this phone? All of them that I've done with major OS changes—even after factory reset—have failed to produce a working restore even though they were taken from a working state.
I'm also unable to get back my previously-working CM 10.1 ROM even though I followed the exact same procedures (with the same files) that I used to get it working before.
This has been happening since my first failed Nandroid restore trying to go back from CM 10.1 to the HTC Sense Nandroid backup I made before attempting CM 10.1 in the first place. I thought this was due to the Sense Nandroid having been made under the OTA-upgraded radio version (I had to use the stock rom.zip from the RUU to get CM 10.1 working at all), but now I'm not so sure. I get the HTC logo and angry red legal text indefinitely now with those setups.
I can't even get back to the Nandroid I made of the stock HTC Sense ROM right after I restored from the RUU's rom.zip.
Anyone have any idea what I'm doing wrong? Or is this model really just that much of a pain?

Are you flashing the correct kernel in fastboot after completing the restore? The recovery is not able to flash a kernel, that still needs to be done through fastboot, even with a nandroid restore.

riggerman0421 said:
Are you flashing the correct kernel in fastboot after completing the restore? The recovery is not able to flash a kernel, that still needs to be done through fastboot, even with a nandroid restore.
Click to expand...
Click to collapse
That's the boot.img, right? I did try flashing that after the restore didn't work the first time. No joy.
EDIT: Actually, that explains why some of my restores have failed, but not all of them.
EDIT 2: Mystery solved. I think. The Nandroid backup I took yesterday evening must be broken somehow. I noticed a few minutes ago that TWRP wasn't actually telling me that it finished restoring the backup—it was just taking me back to the home screen. I switched to CWM Recovery to grab a backup I took yesterday Morning, and that one worked.
So now I'm just left extremely disconcerted that I can't be certain my backups are reliable.

mynewshiny said:
That's the boot.img, right? I did try flashing that after the restore didn't work the first time. No joy.
EDIT: Actually, that explains why some of my restores have failed, but not all of them.
EDIT 2: Mystery solved. I think. The Nandroid backup I took yesterday evening must be broken somehow. I noticed a few minutes ago that TWRP wasn't actually telling me that it finished restoring the backup—it was just taking me back to the home screen. I switched to CWM Recovery to grab a backup I took yesterday Morning, and that one worked.
So now I'm just left extremely disconcerted that I can't be certain my backups are reliable.
Click to expand...
Click to collapse
I originally thought this was just an isolated incident, but it seems to be recurring. Several of the Nandroid backups I've made more recently, both within TWRP Recovery and via the Online Nandroid Backup app, seem to produce this result. (Fortunately, I have a known good backup that I've been able to use reliably.)
Is there a way to validate a Nandroid backup other than trying to restore from it? I don't mean comparing a hash (which is what I find using Google), but rather making sure that the original, uncorrupted file is valid for use as a backup.
As a side note, every backup I've done with CWM Recovery has been reliable, so my fallback plan is to switch to CWM. I just find TWRP easier to navigate.

mynewshiny said:
I originally thought this was just an isolated incident, but it seems to be recurring. Several of the Nandroid backups I've made more recently, both within TWRP Recovery and via the Online Nandroid Backup app, seem to produce this result. (Fortunately, I have a known good backup that I've been able to use reliably.)
Is there a way to validate a Nandroid backup other than trying to restore from it? I don't mean comparing a hash (which is what I find using Google), but rather making sure that the original, uncorrupted file is valid for use as a backup.
As a side note, every backup I've done with CWM Recovery has been reliable, so my fallback plan is to switch to CWM. I just find TWRP easier to navigate.
Click to expand...
Click to collapse
I've played with recovery files before (se my signature) when cwm wasn't working well.
Basicly if you want to know that the backup is correct, you can only compare the hash codes (nandroid.md5) which is practically useless, because hases are made only for the .img files, so the OS itself is not protected like this, which is somehow ok, because the files are compressed to a .tar file, which also means it has it's own validation algorithms itself. So you can validate it if you can decompress the file (don't ask that how it could be done under windows) without errors, it should be allright.
I personnaly can say only this: use CWM 6. i-don't-know-which version (which is online now). There is a possibility for cache not mounting, and of course a backup to not be full, but as you can see from my signature, it can be "bypassed" so the OS will be backed up, and because we don't have S-OFF, it doesn't really matters. All of my backups from CWM is working (have at least 10 gigs at the time, from stock to EV).

I always use android file verifier by scary Allen (free market download). It has saved me many times!
Sent from my HTC One V using xda app-developers app

so as a conclusion, nandroid backup won't restore boot image? and the option in cwm advance restore>restore boot is useless? Me also always got stuck using nandroid restore

Ken-Shi_Kun said:
I've played with recovery files before (se my signature) when cwm wasn't working well.
Basicly if you want to know that the backup is correct, you can only compare the hash codes (nandroid.md5) which is practically useless, because hases are made only for the .img files, so the OS itself is not protected like this, which is somehow ok, because the files are compressed to a .tar file, which also means it has it's own validation algorithms itself. So you can validate it if you can decompress the file (don't ask that how it could be done under windows) without errors, it should be allright.
I personnaly can say only this: use CWM 6. i-don't-know-which version (which is online now). There is a possibility for cache not mounting, and of course a backup to not be full, but as you can see from my signature, it can be "bypassed" so the OS will be backed up, and because we don't have S-OFF, it doesn't really matters. All of my backups from CWM is working (have at least 10 gigs at the time, from stock to EV).
Click to expand...
Click to collapse
sellersj27 said:
I always use android file verifier by scary Allen (free market download). It has saved me many times!
Sent from my HTC One V using xda app-developers app
Click to expand...
Click to collapse
Confirmed that comparing file hashes isn't helpful for this purpose—I just downloaded scaryalienware's AFV as suggested and ran it against several of my Nandroid backups. It said all of them succeeded, including at least one of which I know will not restore successfully. However, of interest is the fact that it took about half as much time to scan the known "bad" one, and further analysis shows that it's about half the size of the others. I'll have to make some more backups via the various mechanisms to confirm that the size is an indicator; it may be simply that I had fewer apps installed when making those backups.
Too bad there isn't some kind of Nandroid Restore Simulator. But even if there was, this phone probably wouldn't have enough memory to use it. Checking Nandroid backups in a VM would be awesome though!