Develop Bugs

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!

backup question

i just wanted to know since a nandroid backup backs up the boot.img of a rom as well as the data, could i make different "stock" backups of roms and just format the system and factory reset and restore roms from backups? like say i back up pacman rom, then go to stock. can i just reflash pacman without the boot.img (say i dont have a computer) and restore the backup? would that make the boot.img work? cause if so i could have one backup of each rom on my 16gb sd card and just reflash when i need it. thanks guys

sneakysnake16 said:
i just wanted to know since a nandroid backup backs up the boot.img of a rom as well as the data, could i make different "stock" backups of roms and just format the system and factory reset and restore roms from backups? like say i back up pacman rom, then go to stock. can i just reflash pacman without the boot.img (say i dont have a computer) and restore the backup? would that make the boot.img work? cause if so i could have one backup of each rom on my 16gb sd card and just reflash when i need it. thanks guys
Click to expand...
Click to collapse
Which recovery are you on and are you primoc or primou?..... I don't think the recovery will actually backup the boot.img even though it says it does... someone else might be able to answer better though

Sorry forgot that but I'm primoc with twrp 2 recovery on Pac man 19.3
Sent from my HTC One V using xda premium

sneakysnake16 said:
i just wanted to know since a nandroid backup backs up the boot.img of a rom as well as the data, could i make different "stock" backups of roms and just format the system and factory reset and restore roms from backups? like say i back up pacman rom, then go to stock. can i just reflash pacman without the boot.img (say i dont have a computer) and restore the backup? would that make the boot.img work? cause if so i could have one backup of each rom on my 16gb sd card and just reflash when i need it. thanks guys
Click to expand...
Click to collapse
No it wont..... U have to flash boot.img again.....even though its backed up, it is not restored due to S-on

rohov said:
No it wont..... U have to flash boot.img again.....even though its backed up, it is not restored due to S-on
Click to expand...
Click to collapse
Damn thanks!
Sent from my HTC One V using xda premium

[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!

Can't properly restore a nandroid backup HELP!!!

Hi,
I'm trying to restore a nandroid backup I did with TWRP 2.3.3.0 but I'm not being successful and it's bothering me because now I have an unstable system and didn't really wanted to reinstall everything from scratch...
I don't understand what I'm doing wrong but after restoring the backup and rebooting the phone, I can boot but MOST of my apps are not "installed". Shortcuts I had on the home screen are there with their respective icons, I click on them and I get "Applications is not installed". I also get a notification saying that phone storage is running low, and it is hitting the 2GB limit, but it never was like this before, I had lots of of free space for apps. Looking at the nandroid backup, it seems I have data.ext4.win000 and data.ext4.win001 both with around 1.5GB, which goes above the 2GB limit. Not sure if this means anything...
Why isn't this backup working and what can I do to attempt to solve it?
Any other info I can give you so you can better try and help me, just let me know what you need to know...

Wrong section..
Hmm full wipe before restore??
Sent from my HTC One X using xda app-developers app

basti2909 said:
Hmm full wipe before restore??
Click to expand...
Click to collapse
Already tried that...

I updated to TWRP 2.5.0.0 and now I get "restore failed"... :'(
There's no way to get around this is there?

not sure if your recovery is corrupt, maybe worth making a titanium backup of apps and system data, flashing a new rom and then restoring via titanium?

exocetdj said:
not sure if your recovery is corrupt, maybe worth making a titanium backup of apps and system data, flashing a new rom and then restoring via titanium?
Click to expand...
Click to collapse
Can I make a titanium backup out of the nandroid backup? Cause that's all I have right now, my current ROM is not even working properly... I'll have completely reinstall a new ROM.

Nazgulled said:
Can I make a titanium backup out of the nandroid backup? Cause that's all I have right now, my current ROM is not even working properly... I'll have completely reinstall a new ROM.
Click to expand...
Click to collapse
what do you mean titanium backup out of the nandroid? normally the data backup should be there too...to be sure i always make tit backup's for my apps...

One-X-master said:
what do you mean titanium backup out of the nandroid? normally the data backup should be there too...to be sure i always make tit backup's for my apps...
Click to expand...
Click to collapse
The only backup I have is a Nandroid backup and nothing else. I don't even have a running/working ROM at the moment.

Nazgulled said:
The only backup I have is a Nandroid backup and nothing else. I don't even have a running/working ROM at the moment.
Click to expand...
Click to collapse
Normally the nandroid backup should also save the data which means the apps and their data, hm.....due that it isn't working you have to install from beginning
Gesendet von meinem HTC One X mit Tapatalk 2

Nazgulled said:
Hi,
I'm trying to restore a nandroid backup I did with TWRP 2.3.3.0 but I'm not being successful and it's bothering me because now I have an unstable system and didn't really wanted to reinstall everything from scratch...
I don't understand what I'm doing wrong but after restoring the backup and rebooting the phone, I can boot but MOST of my apps are not "installed". Shortcuts I had on the home screen are there with their respective icons, I click on them and I get "Applications is not installed". I also get a notification saying that phone storage is running low, and it is hitting the 2GB limit, but it never was like this before, I had lots of of free space for apps. Looking at the nandroid backup, it seems I have data.ext4.win000 and data.ext4.win001 both with around 1.5GB, which goes above the 2GB limit. Not sure if this means anything...
Why isn't this backup working and what can I do to attempt to solve it?
Any other info I can give you so you can better try and help me, just let me know what you need to know...
Click to expand...
Click to collapse
Nazgulled said:
I updated to TWRP 2.5.0.0 and now I get "restore failed"... :'(
There's no way to get around this is there?
Click to expand...
Click to collapse
It's your fault cuz the app data is not being restored , 1stly when you made the backup with TWPR you should've selected to backup the CACHE , you skipped that step since by default TWPR skips that step = no apps data anymore, tho there are shortcuts and in manage all apps you can see those apps installed but with grey collor like when being removed from lets say rom cleaner , theres still the APP IMAGE but not the app it'self , you could try this:
1. Flash old recovery ( the one you used to make the back up 2.3 or which ever you used ) . full wipe , restore nand backup ( don't forget to flash the boot.img in the bootloader if you used different kernel in that time or flash the modules via recovery for the kernel you use atm )
after you boot up re-download those apps that are there with shortcuts but not apps itself and hope for the saves from those apps to be there.
Next time if you don't wanna risk it you titanium back up and save the apps that matter to you , when restoring them back : download the app , go to titanium and restore only the DATA.
or simply check in TWPR when making nand backup to save the CACHE as well in the backup.

Yeah, I know it was my fault... I was at work doing other stuff at the same time and didn't focus on what I was actually doing with my phone and I messed up. I was used to an old recovery on my old phone where a nandroid backup would backup everything needed and didn't really look at the partition options.
I'm doing exactly what you mentioned and so far seems to be working. All the data seems to be there, I just have to reinstall all the apps...
One thing though, since the nandroid restore process didn't work correctly, I was left with a full /data partition and my phone started reporting "low storage" and didn't allow me to do install anything. I looked into the /data partition and found out that the folder lost+found was filling up the partition, I erased everything in it and restored 1.2Gb of free space. I can now install all my apps.
Thank you all.

Nazgulled said:
Hi,
I'm trying to restore a nandroid backup I did with TWRP 2.3.3.0 but I'm not being successful and it's bothering me because now I have an unstable system and didn't really wanted to reinstall everything from scratch...
I don't understand what I'm doing wrong but after restoring the backup and rebooting the phone, I can boot but MOST of my apps are not "installed". Shortcuts I had on the home screen are there with their respective icons, I click on them and I get "Applications is not installed". I also get a notification saying that phone storage is running low, and it is hitting the 2GB limit, but it never was like this before, I had lots of of free space for apps. Looking at the nandroid backup, it seems I have data.ext4.win000 and data.ext4.win001 both with around 1.5GB, which goes above the 2GB limit. Not sure if this means anything...
Why isn't this backup working and what can I do to attempt to solve it?
Any other info I can give you so you can better try and help me, just let me know what you need to know...
Click to expand...
Click to collapse
Your rom is ok but i think your sdcard were you install your app has been modified. Just do a factory reset and install apps again it happened to me too).

Nazgulled said:
I updated to TWRP 2.5.0.0 and now I get "restore failed"... :'(
There's no way to get around this is there?
Click to expand...
Click to collapse
Flash the recovery from the backup and then try to restore nandroid and if you have empty spce in the name change with _

I have different problem about nandroid back up, everytime i transfer my back up to pc and back again to my phone, the custom recovery cannot detect my back up. What should i do?

harrymason37 said:
I have different problem about nandroid back up, everytime i transfer my back up to pc and back again to my phone, the custom recovery cannot detect my back up. What should i do?
Click to expand...
Click to collapse
Make sure you make no changes in the folder structure and folder naming. It has to be exact the same as it was.......and when you want to restore a nandroid you always flash the boot.img and recovery.img from the nandroid and then do the rest of the procedure

Mr Hofs said:
Make sure you make no changes in the folder structure and folder naming. It has to be exact the same as it was.......and when you want to restore a nandroid you always flash the boot.img and recovery.img from the nandroid and then do the rest of the procedure
Click to expand...
Click to collapse
thanks! Thats what i'm doing wrong, i just transfer the folder were the files is locate, i ignore the twrp folder. Thanks again.

[Q] Nandroid (Agat) backup/restore problems

So... I flashed AGAT_Recovery tREC_v0.2.2 and was intending to restore a "nandroid" backup from before I wiped my phone. First of course I made a backup (just Stock Rooted ROM I used to flash the recovery partition). I then tried to restore the previous image of my custom ROM and the restore failed. Investigated and found that the filenames in the nandroid backup folder were named differently from previous nandroid backups I had taken:
system.ext4.tar (0 bytes)
system.ext4.tar.a (large)
data.ext4.tar (0 bytes)
data.ext4.tar.a (large)
I'm not sure how the backup format changed as I don't recall updating the recovery partition, I'm wondering if some ROM I installed did this for me (if so thanks a lot). Looks like this:
http://forum.xda-developers.com/showthread.php?t=2194171
So trying to be clever, I deleted the 0 byte files and renamed all of the stupid .a files to the original (I had no .b, .c files etc.) Then I did a restore.
The restore completed successfully but com.android.Phone was crashing on startup repeatedly, the launcher wasn't working properly and basically the image wasn't usable.
I then decided that it wasn't worth all the trouble and I would just restore to the backup I had taken of the Stock Rooted ROM immediately prior to this whole mess starting (using AGAT_Recovery tREC_v0.2.2). The restore completed successfully but the O/S didn't boot at all (it just showed a black screen after POST of the Samsung logo).
For now I've reflashed stock using ODIN.
So basically my question is: why is this so complicated? Am I missing something here? Is AGAT_Recovery 0.2.2 not a good choice for a recovery partition?

Is the recovery you are trying to restore the sane recovery you are currently running.
I've gotten stuck by being in a different version of the same recovery and it just didn't work. I had to be in the same recovery in order to do a restore.
Just a thought

Bt is right. You should always use the same cwm to restore that you used on the backup. And the latest Agat recovery is essentially bugfree, which is 0.3.5. So I would use that. And it's not difficult, at all . Just takes a few "oh craps" to get it down pat!
Sent from my SPH-D710 using xda premium

thanks
jdsingle76 said:
Bt is right. You should always use the same cwm to restore that you used on the backup. And the latest Agat recovery is essentially bugfree, which is 0.3.5. So I would use that. And it's not difficult, at all . Just takes a few "oh craps" to get it down pat!
Click to expand...
Click to collapse
I suspect part of the reason I couldn't restore the one backup image was because I wasn't using the same version, or perhaps even product. Doesn't explain why the older version of Agat couldn't restore its own backup though. I'll try the newer version out. Thanks!
It's too bad the utilities don't write out some metadata about the format used, what product/version did the backup, etc.

philipdl71 said:
I suspect part of the reason I couldn't restore the one backup image was because I wasn't using the same version, or perhaps even product. Doesn't explain why the older version of Agat couldn't restore its own backup though. I'll try the newer version out. Thanks!
It's too bad the utilities don't write out some metadata about the format used, what product/version did the backup, etc.
Click to expand...
Click to collapse
That was an earlier kernel that probably still had bugs. Could have been a bad backup. It happens. The latest kernel will do solid backups/restores and serve as a very dependable dd. Good luck.
Sent from my SPH-D710 using xda premium