Database Users

Nandroid backup question

i just flashed a rom and forgot to backup nandroid.
but i backed it up straight away after flashing it , will it be ok?
also how does all this nandroid backup thing work what does it really do,
last time i flashed a rom i still got that backed up if it will be any use.
thanks

A Nandroid backup backs up the entire state of your phone apart from its SD card. You should do one when you have a fully working (and rootable) phone, so that if you screw up flashing it in future you can get back to a working phone with it set up how it was before.
It's not enough just to do the backup, you need to ensure that you can restore from it too. I had to do a restore recently and realised I couldn't use fastboot because I didn't have the right SPL (part of the bootloader) installed. Luckily the recovery image I had let me manipulate it via adb etc. I learned a lot of things the hard way and I suspect I came very close to having a bricked phone.

I don't understand..hopefully I don't mess up my phone, when do I have to restore.nandroid

When flashing a ROM goes wrong (usually unlikely), you can end up with a phone that won't boot. If you do a nandroid backup before you Flash, you have a backup of your entire phone's state before you flashed. There are ways to restore Nandroid backups (or flash other images) even if your phone won't boot normally. You really have to research this and make sure you have everything right before you flash any ROM.
If you don't understand these concepts, you probably shouldn't be flashing ROMs. Just use the official updater provided by HTC in your country.

how can i restore nandroid then if my phone gets messed up thats the main question

hawwy said:
how can i restore nandroid then if my phone gets messed up thats the main question
Click to expand...
Click to collapse
Google is your friend. Seriously, there are thousands of resources on this around the web - frankly if you are not willing to do the research into this, just don't flash any ROMs. Doing so is only for technically minded people who know how it all works or are willing to go off and learn about it thoroughly. It doesn't sound like that is you.
This stuff isn't easy, for the same reason flying a 747 isn't easy: it shouldn't be attempted by novices.
I can't just explain it in a couple of sentences.

Error: "nandroid-mobile.sh restore" from console!

Hello everyone,
(Note, I did do a nandroid backup before I did ANYTHING, right after rooting)
I was having some issues with Modaco 1.0 when it was first put out, and like everyone else, got trapped in a reboot loop. Once I saw that the fix was repartitioning to FAT32, I did so, re-flashed the ROM, and I was back in. All was good.
But when 1.1 came out, I really wanted to restore to my backup to start fresh with the new ROM, but it did not work out. When I tried to do so in the recovery console, I got this error - Error: "nandroid-mobile.sh restore" from console! -
What am I supposed to do with that? I went ahead and went through with 1.1, but I am worried I accidentally closed my backdoor at some point. I noticed I lost some things from the basic ROM (such as the default wallpapers, and I had issues with Google Maps), and I am just generally worried something is fishy in there.
Any suggestions?

lorsoblu said:
Hello everyone,
(Note, I did do a nandroid backup before I did ANYTHING, right after rooting)
I was having some issues with Modaco 1.0 when it was first put out, and like everyone else, got trapped in a reboot loop. Once I saw that the fix was repartitioning to FAT32, I did so, re-flashed the ROM, and I was back in. All was good.
But when 1.1 came out, I really wanted to restore to my backup to start fresh with the new ROM, but it did not work out. When I tried to do so in the recovery console, I got this error - Error: "nandroid-mobile.sh restore" from console! -
What am I supposed to do with that? I went ahead and went through with 1.1, but I am worried I accidentally closed my backdoor at some point. I noticed I lost some things from the basic ROM (such as the default wallpapers, and I had issues with Google Maps), and I am just generally worried something is fishy in there.
Any suggestions?
Click to expand...
Click to collapse
Your Nandroid backup was on that SDcard...I don't suppose you saved it before formatting it?

lorsoblu said:
Hello everyone,
(Note, I did do a nandroid backup before I did ANYTHING, right after rooting)
I was having some issues with Modaco 1.0 when it was first put out, and like everyone else, got trapped in a reboot loop. Once I saw that the fix was repartitioning to FAT32, I did so, re-flashed the ROM, and I was back in. All was good.
But when 1.1 came out, I really wanted to restore to my backup to start fresh with the new ROM, but it did not work out. When I tried to do so in the recovery console, I got this error - Error: "nandroid-mobile.sh restore" from console! -
What am I supposed to do with that? I went ahead and went through with 1.1, but I am worried I accidentally closed my backdoor at some point. I noticed I lost some things from the basic ROM (such as the default wallpapers, and I had issues with Google Maps), and I am just generally worried something is fishy in there.
Any suggestions?
Click to expand...
Click to collapse
nah. The happens sometimes. Could be your nandroid backup got corrupted or you are low on battery power. Two most common causes. I would make sure the nandroid backup is on the sd card. if so, simply try plugging it in to a power supply. Let us know if you get it working.

All right... I did not want to admit it but I believe what you said is probably true, and I either corrupted or simply deleted the nandroid backup during all the flashing and repartitioning. I am not seeing it at all when I mount the SD card. It crossed my mind a little too late that I should have pulled it off the card.
What are my options here? On the one hand, it is working fine for now. I had just got the Hero earlier that day (did an exchange due to dead pixels and network issues), so it was not like I lost anything important. Is there an easy way for me to go all the way back, such as flashing the original ROM to the phone, and essentially starting over, like I just opened the box and turned the phone on? That way I can do it right from the very beginning. I just worry that in all my partitioning things got scrambled, and I am not seeing the repercussions from it yet, other than Google Maps.

ftp://xda:[email protected]_Hero_C_Sprint_1.29.651.1_signed_release.exe
if at first you try and fail.... try try agian

Thanks for the link.
Is there some process to this? I mean, I understand the whole update.zip concept of flashing the ROM, but would I also need to do a complete wipe of the SD card to achieve the fresh start I am looking for? Should I partition it at only FAT32, or go ahead and setup the ext2 partition before flashing the original ROM?

lorsoblu said:
Thanks for the link.
Is there some process to this? I mean, I understand the whole update.zip concept of flashing the ROM, but would I also need to do a complete wipe of the SD card to achieve the fresh start I am looking for? Should I partition it at only FAT32, or go ahead and setup the ext2 partition before flashing the original ROM?
Click to expand...
Click to collapse
convert sd card to "SDPART:fat32 only" from custom recovery
et the official RUU wipe your phone
enable USB debugging in settings>applications
reroot your phone using asroot exploit
make any partition changes you want
do a nandroid backup
do a nandroid restore to verify it works
backup on your workstation /sdcard/nandroid
DO NOT TOUCH YOUR SD PARTITION TYPE AT THIS POINT
get to modding in confidence

johnsongrantr said:
convert sd card to "SDPART:fat32 only" from custom recovery
et the official RUU wipe your phone
enable USB debugging in settings>applications
reroot your phone using asroot exploit
make any partition changes you want
do a nandroid backup
do a nandroid restore to verify it works
backup on your workstation /sdcard/nandroid
DO NOT TOUCH YOUR SD PARTITION TYPE AT THIS POINT
get to modding in confidence
Click to expand...
Click to collapse
All right, I am having issues already, from the very beginning.
The RUU ROM .exe will not recognize the HTC Hero. It throws an error 170 at the step where it is trying to pull information from the phone. I think this has something to do with ADB, and the fact the computer did not have the SDK on it. (I originally set up the root with my Mac.)
So, where do I go? I have a Boot Camp partition and another computer both running Windows 7, but my attempts to put the SDK on those computers and then have the phone drivers properly recognized failed on both, and the .exe still cannot complete. Is there something I am missing here, or can I somehow do this on the Mac side? I'll take anything!
Edit: Just cause I can see someone asking, yes, I tried to do this on both of my Windows 7 computers, not the Mac. I recognized that the .exe would not run on OSX pretty quickly.

can you put your phone into fastboot (power+vol down) and get to the point where windows basically sees your phone
what you are looking for is when you type adb devices it shows your hero
fastboot might not work because it's a seperate program but try custom recovery main menu.... enable usb.... or something to that extent
I appologize I don't have my main computer in front of me so I can't tell you EXACTLY where to go
once I do, I'll find which one to hit.... it does work though because I had to do the same thing with my godly preaching of backups :blush:
it's one of the recovery areas though i promise
fastboot will see the hero as the same device as adb will in fastboot
adb will see the hero as recovery device in custom recovery
attempt both of these I'm certain one of these work
if absolutely all else fails.... after you "install" sprint ruu search your computer for rom.zip it should be in your START>RUN>%TEMP% in here somewhere
rename rom.zip it to HERCIMG.ZIP and put it at root of your sd card and boot into hboot and it should automatically find it and press action to flash it

I'll give some of that a shot. I can confirm that adb devices was not showing the hero connected cause I tested that, so I have a feeling correcting that is my primary concern. What happened when I connected the Hero the first time was that it applied the drivers, but it could not find the ADB one, even after I added the SDK. So if anyone knows what that means (Windows 7 doesn't really give you an easy way to point and say, "Hey, I know what you are looking for, it's right here!" apparently, at least I haven't found it) it would be appreciated.

lorsoblu said:
I'll give some of that a shot. I can confirm that adb devices was not showing the hero connected cause I tested that, so I have a feeling correcting that is my primary concern. What happened when I connected the Hero the first time was that it applied the drivers, but it could not find the ADB one, even after I added the SDK. So if anyone knows what that means (Windows 7 doesn't really give you an easy way to point and say, "Hey, I know what you are looking for, it's right here!" apparently, at least I haven't found it) it would be appreciated.
Click to expand...
Click to collapse
go to htc's website and get htc sync under support>sprint hero it has the drivers built in.... should fix driver issue

johnsongrantr said:
go to htc's website and get htc sync under support>sprint hero it has the drivers built in.... should fix driver issue
Click to expand...
Click to collapse
Hey, that did the trick! Currently flashing with the official ROM right now. Thanks for all the help! FINALLY, I will get to do this right!

lorsoblu said:
Hey, that did the trick! Currently flashing with the official ROM right now. Thanks for all the help! FINALLY, I will get to do this right!
Click to expand...
Click to collapse
glad to be of assistance

johnsongrantr said:
glad to be of assistance
Click to expand...
Click to collapse
Actually, I do have one more question.
Following your instructions back on page 1, wouldn't I want to make the nandroid backup BEFORE repartition to fat32+ext2, so I could recover it all the way back to the standard ROM without partition alterations? Or is it necessary for me to repartition before creating a backup?

lorsoblu said:
Actually, I do have one more question.
Following your instructions back on page 1, wouldn't I want to make the nandroid backup BEFORE repartition to fat32+ext2, so I could recover it all the way back to the standard ROM without partition alterations? Or is it necessary for me to repartition before creating a backup?
Click to expand...
Click to collapse
you'd think so.... but from my own experience if you do a backup on a partititon then convert it... it screws with the backup and you can't recover from it.... just in case... do 2 backups.... store the normal fat32 nandroid backup on your workstation (the entire nanddroid folder) and copy it back to sd after you convert it to fat32+ext2 .... you'll see what I'm talking about....
I don't quite understand why it does that... but for me I was only successful in recovering from a partition that I made a backup to not copied to (if that makes any sence)
also if you don't want to experiement yet... just leave it fat32... you can always change it later after you see it working (sorta confidence builder before tinkering)

lorsoblu said:
Actually, I do have one more question.
Following your instructions back on page 1, wouldn't I want to make the nandroid backup BEFORE repartition to fat32+ext2, so I could recover it all the way back to the standard ROM without partition alterations? Or is it necessary for me to repartition before creating a backup?
Click to expand...
Click to collapse
Think about it this way, you do a nandroid backup...it places it on the sdcard.
Then you go and change the format of the sd card (potentially blowing away or corrupting any data on it, including the nandroid backup you just made).
Thus why it's better to do it afterwards (besides, nandroid doesn't back up your sd card, just your phone's OS and such)

solved for me
i had that problem its cuz the back up is brocken get anthoer copy of it if u hav 1 then restore it again it worked for me

How to root FRG33?

I did a PaSSIMG FRG33 version, but I can not root with universal androot also can not return to the version of PASSIMG FRF91, indicates that it is old version. Anyone know?

As it stands, if you want root you're back to having to unlock the bootloader.
You could try: http://forum.xda-developers.com/showthread.php?t=726258 and seeing if you can revert to FRF91 afterwards.

Try?
But someone made with good results?

You should have rooted FRF91, installed a custom recovery, and then used an update.zip format of FRG33 to update to update the system and boot.

kam187 said:
You should have rooted FRF91, installed a custom recovery, and then used an update.zip format of FRG33 to update to update the system and boot.
Click to expand...
Click to collapse
No work recovery with update.zip. Android exclamation!
Also, i can not install passimg frf91, indicat that is a old version

Androith said:
No work recovery with update.zip. Android exclamation!
Also, i can not install passimg frf91, indicat that is a old version
Click to expand...
Click to collapse
Android exclamation is STOCK recovery. Kam is saying "custom recovery" like Clockworks or RA.

Ok,
I got it, but unlocking fastboot to install the superboot. Now I have total control
Now we have to wait to close lock
Thanks!!

Which version of superboot should we be using to root this frg33?

The superboot FRF91
http://www.mediafire.com/?4nnez0uddqk519r

Thanks a lot. I opted not to wait for a new 1-click version. Unlocked the bootloader by cmd prompt. It was weird though. I thought when I was reading about superboot that all you had to do was dbl-click it from windows, but I ended up having to run it for cmd prompt, too. Either way, I'm rooted now. My only remaining question has to do with the custom recovery stuff. I flashed the "latest clockwork recovery" in ROM Manager. Then I flashed the modaco rooted/deodexed/busybox/etc. version of frg33. Is that all I need for my phone to be "safe" at this point? I guess ROM manager let's me flash just about any of the custom ROMS, but if one hangs on load, I just wanna make sure everything is restoreable.
BTW....Android clearly has the best and most helpful community of users that I have ever seen!!!

makelegs,
Glad you got it all worked out and are truely unlocked and rooted. As long as you nandroid, you are safe on what ever yoy wan to do. The dreaded, botched radio flash is probably the only way to get hurt. At least that is my understanding.

That's the funny thing.... I am completely confused about "nandroid." I can't figure out if nandroid is a general concept or something very specific. I have a couple of complete backups performed with clockwork, but nowhere in my "recovery" area have I seen the word NANDROID. So I'm pretty sure, at this point, that if the fit hits the shan I have a plan-b, but nobody ever says "be sure to 'some other kind of' backup." They always say "be sure to nandroid." Am I taking this too literally??? or have I overlooked a step in this process?
I even paid for the premium Rom Manager upgrade so that I could try out different ROM's, but I have this sneaky suspicion that I oughta get closure on the whole "nandroid" thing before I get too carried away.
You've been a lotta help.

makelegs said:
That's the funny thing.... I am completely confused about "nandroid." I can't figure out if nandroid is a general concept or something very specific. I have a couple of complete backups performed with clockwork, but nowhere in my "recovery" area have I seen the word NANDROID. So I'm pretty sure, at this point, that if the fit hits the shan I have a plan-b, but nobody ever says "be sure to 'some other kind of' backup." They always say "be sure to nandroid." Am I taking this too literally??? or have I overlooked a step in this process?
I even paid for the premium Rom Manager upgrade so that I could try out different ROM's, but I have this sneaky suspicion that I oughta get closure on the whole "nandroid" thing before I get too carried away.
You've been a lotta help.
Click to expand...
Click to collapse
Can't speak for Clockwork but on Anom the backup goes in /sdcard/nandroid/DEVICEID/dated-subdir
Each time you make a backup using nandroid, it's a new directory.
And you can NOT restore a nandroid made from a different recovery from what I've read. If you make it with Clockwork you gotta restore it with Clockwork.

makelegs,
It has become a general term with the advent of Rom Manager/ClockworkMod. If you look at the top of the Clockwork screen when in recovery, it say nandroid. The term generally means a full image backup of your phone as opposed to just backing up apps/data. In the nandroid the OS and all else is backed up. So, I wouldn't give it a second thought.
What khaytsus said is the only important thing. Restore thru whichever recovery you backed up with. Clockwork to Clockwork or Amon to Amon.
Amon is put into the nandroid file on your sd and Clockwork is put into Rom Manager under Backups. Although, you can get to them a couple different ways in Clockwork. Thru Install Rom From SD Card or Manage and Restore Backups. Also by booting into Clockwork Recovery. You probably already know that if you use Clockwork.
Ken

Is it actually probable that 1 click might be made to work for 33? It doesn't seem like there are many other users with stock/33 like myself. I feel like a horses ass for flashing it and screwing up my protected apps. All through the incremental updates that led us from 2.1 to froyo went thru easily with no paid apps issues so I didn't have my guard up for this one. (Unless they all had a modded fingerprint status which I starting to think I may remember them having, whatever, this is a bummer...)

Maybe it will be updated, but the folks on frg22 (i think) have been waiting even longer. I was just too busy and OCD to wait it out.
It was probably only ever a matter of time before I went the unlocked bootloader/root route. This was just the catalyst for me. I learned an awful lot in the process. Alas, my phone is back to "normal", but running modaco's rooted/deod/busy/frf91 finger/etc... version of FRG33. And I now realize that if I had just flashed the clockwork recovery to begin with, when I was 1-click rooted on frf91, then this whole thing would've been substantially less of a PITA for me.
Good luck!

FRG33
I got caught out i had 1 click root with cm6
But then installed FRG33 not realising i would lose root if i reverted to it after i had done a backup of cm6 .
I had a lot of things including adfree working on FRG33 prior to recovery .

I think the universal androot app uses the "exploid" method which indeed was patched in FRG versions. But I believe someone on the forum reported that FRG22 or FRG33 was still vulnerable to the "rageagainstthecage" root exploit.
Can someone here verify whether FRG83 is still rootable using "rageagainstthecage"?

You can try the instructions for rooting FRG33 in the Wiki on FRG83.

[Q] Could I (and should I) copy a stock ROM backup and flash it to a new Note 3?

So I just dropped my Note 3 of 2 weeks on the floor (with a case on it) and although the glass isn't cracked, the LCD and digitizer is definitely junk since its all warped in color and mostly black. Thank the gods I have insurance.
I have it Rooted and Safestrap installed and luckily made a backup before I installed Xposed when all was still well. I'm familar with Clockworkmod and flashing that way but new to Safestrap. What is the best way to get my new phone back to how the dropped one was like? Not sure of what files to copy onto my PC and back onto the new phone once I get a new one. Would it make a difference if the backup is from another phone?
My main concern is getting all my username and passwords out of the OI Safe app so it's the main reason for wanting to flash my old backup to the new phone. Other than that I'm not to worried about the rest of the phone since it's fairly new and didn't have it long enough for lots of pics and getting it set up the way I really wanted it.
Thanks

That should work with the following big caveat: if you were on the MJ7 kernel (or earlier), and the new phone is on MJE, restoring the full nandroid backup probably won't work at all and is not adviseable. (Remember that Safestrap "ROM"s do not replace the stock kernel).
If the two phones are from the identical release, then what I would do is the following:
- Root and install SafeStrap as usual.
- Immediately make a Nandroid of the Stock Slot using Safestrap. Get it copied off the phone someplace safe (and named in a way that you can remember it) too.
- Make a second slot in Safestrap and restore the backup from the previous phone to this alternate/second slot.
( Note if you were using a ton of the userdata partition on the old phone you will need to right-size the 2nd slot when you create it. Of course, if you were a data-pig on the old phone and there is no room for a sufficiently-large 2nd slot, then this method of rescue is not available to you. In this case you could restore the original nandroid backup directly to the stock slot - only if you were 100% positive of the same kernel release being used on both phones - but if something goes wrong here you might be making a trip to Odin to re-flash stock and then going through the rooting process all over again ).
- You can use it this way for a little while if you like to see if things are working, or rescue critical data from individual apps, or perhaps make TiBu backups of individual apps (that can be later restored into a different ROM). If things seem to be going swimmingly, you can certainly repeat this process, restoring to the stock slot and then destroying the alternate/second slot.
Note that there are other means of rescue of individual apps which do not require a full restore; this is because the Nandroid backups are (concatenated) "tar" archives, and with sufficient command-line knowledge, you could manually splice into place the appropriate folders from /data/data/*, /data/app/*, and /data/lib/* for individual market apps you wanted to rescue from the old backups. Essentially you are doing the same thing that TiBu does, but manually using adb with the phone in Safestrap recovery mode and the command line.
I'm not going to document this, as it is too tedious to do so - either you already have the working knowledge to do this or you don't. The only tricky part to it is getting the user/group ownership of the files correct. (The easiest way to do this is to install the app from the market, then record the owner/group information it used for the new install of the app, restore the /data/data/* files into the correct place, and then as root "chown" them to the correct user ID... either that or run the "Fix Permissions" script of the recovery).
good luck

I am about 99% sure it was on MJE, I remeber checking it before rooting and following the newest root method available for the newest kernel among other things such as installing Safestrap and Xposed framework.
I unfortunately don't have any experience using Odin or adb, which is something I should know how to do seeing I'm always tinkering with all the phones I get. I'm pretty good with figuring things out when someone points me in the right direction such as you did by searching and following guides here on xda so I thank you for that! I'll try your idea of rescuing the individual app such as TiBu would do using adb. Or even restoring the ROM into a second slot, grabbing the data I need, then get rid of that rom.
And for anyone else reading this...it's never too early to use TiBu or any other backup app for all your important data. Never expected my brand new phone to break after only 2 weeks of owning it but lesson learned.
Thanks a lot for the help, I'll let you know how things go once my new phone arrives.

(need) A guide for a full stock P9 Lite backup.

Hi everyone,
I tried to find a solid guide for fully backing up my system before doing anything to it to no avail. I'm currently on stock VNS-L21/VNS-L21C432B380/EMUI 5.0/Android 7.0 and plan to do the following:
1) Unlock bootloader
2) Root
3) Install Elite kernal and Arsenik rom
4) Probably some other modifications later on
I've already got some app from the store for application backup purposes but would like to have a firmware/rom/whatever backup of my current setup in order to safely restore in case anything goes wrong. I've done considerable amount of flashing with my other Android phones previously but any help would be appreciated.
Furthermore, perhaps it's worth to create a guide for this and sticky it to the top? I saw a lot of "help, bricked device" posts in this forum. I bet the guys with know-how are sick and tired of helping. Anyway, if you point me in the right direction I might as well create the guide for others.
Have a good one,
Renārs

Without root I don't think that I can make a backup . I can make apk file but not backup of data :/