Related
Hello,
I'm coming from a HTC Desire, and when reading the guides how to install roms on the HOX, the neccesity to flash a separate boot.img for every rom via fastboot was new to me.
Is this always the case? And lets say I have a stable 4.0.4 installation and want to mess around with CM10 - I get that have to flash the CM10 boot.img before installing the ROM, but would I then also have to re-flash my old boot.img before rstoring my old nandroid backup, or is the boot image included in the backup?
Thanks aheasd for an answer,
saxelfur
i guess yes.. you have to re-flash the boot.img of the rom that you are restoring...
faiz02 said:
i guess yes.. you have to re-flash the boot.img of the rom that you are restoring...
Click to expand...
Click to collapse
Okay, thanks - so I suppose right now there is now way to restore a backup from a different rom on the go. Oh well, I should be able to live without that
saxelfur said:
Okay, thanks - so I suppose right now there is now way to restore a backup from a different rom on the go. Oh well, I should be able to live without that
Click to expand...
Click to collapse
You do not have to flash the boot.img before restoring a nandroid backup...Y
ou restore everything, boot.img included.
panooos said:
You do not have to flash the boot.img before restoring a nandroid backup...Y
ou restore everything, boot.img included.
Click to expand...
Click to collapse
Great, even better!
panooos said:
You do not have to flash the boot.img before restoring a nandroid backup...Y
ou restore everything, boot.img included.
Click to expand...
Click to collapse
Not true; if you're restoring a backup which used a different boot.img than the one you already have installed, you need to manually flash the boot.img from your nandroid backup in fastboot.
The reason we have to use fastboot to flash the boot.img is that, thanks to HTC's security policies, it is not possible to write to the boot partition from recovery. Hence when you flash a ROM the boot.img isnt written, and has to be manually flashed. This also means that when you restore a backup in recovery it is still unable to write to the boot partition, so the boot.img from your backup is not written and must also be flashed manually.
hopscotchjunkie said:
Not true; if you're restoring a backup which used a different boot.img than the one you already have installed, you need to manually flash the boot.img from your nandroid backup in fastboot.
The reason we have to use fastboot to flash the boot.img is that, thanks to HTC's security policies, it is not possible to write to the boot partition from recovery. Hence when you flash a ROM the boot.img isnt written, and has to be manually flashed. This also means that when you restore a backup in recovery it is still unable to write to the boot partition, so the boot.img from your backup is not written and must also be flashed manually.
Click to expand...
Click to collapse
Really? I once flashed a kernel and could not pass the loading screen...everything got fixed as soon as i restored my backup...
Lucky for you. But these guys are correct. The only way to flash boot is through fastboot.
Recovery restore cannot restore a boot.img
Sent from my HTC One X using xda app-developers app
panooos said:
Really? I once flashed a kernel and could not pass the loading screen...everything got fixed as soon as i restored my backup...
Click to expand...
Click to collapse
Yep. Boot partition simply isn't writable from recovery (without s-off). There's no difference between recovery trying to write a boot.img from a zip on /sdcard and recovery trying to write a boot.img from a folder on /sdcard (if there was we would just need to modify recovery to treat new flashes as restores to get around the problem).
I'm not saying it won't work if you don't; if you're switching between Sense ROMs or restoring an earlier version of the ROM you're using then there's a good chance that the ROM will still boot and run fine, but you'll be running with the kernel & ramdisk you had before the restore.
Always learning sth new... Ty
Sent from my HTC One X using xda app-developers app
Well shoot. How do I get the boot.img from the stock rom that came with it. It wasn't exactly in standard .zip format for me to extract the .img......
If you did a nandroid backup it's there in plain sight.
Hi
I have a HTC one X rooted phone with stack 4.1.1
I get a message that there is a new update 3.20.401.1
After download it tells me to reboot. My phone then goes to ClockWorkmode (CWM)
It stoops there. I do not find any zip file to install.
Any tips for this, or should I just ignore this?
Thanks
Jotne said:
Hi
I have a HTC one X rooted phone with stack 4.1.1
I get a message that there is a new update 3.20.401.1
After download it tells me to reboot. My phone then goes to ClockWorkmode (CWM)
It stoops there. I do not find any zip file to install.
Any tips for this, or should I just ignore this?
Thanks
Click to expand...
Click to collapse
To install official updates u need to have stock recovery which comes with phone, but u have CWM
Jotne said:
Hi
I have a HTC one X rooted phone with stack 4.1.1
I get a message that there is a new update 3.20.401.1
After download it tells me to reboot. My phone then goes to ClockWorkmode (CWM)
It stoops there. I do not find any zip file to install.
Any tips for this, or should I just ignore this?
Thanks
Click to expand...
Click to collapse
You just need to flash stock recovery through fastboot again mate then on booting up you should be able to install the update. Or you could install a custom rom with that base without having to flash recovery :good:
Thanks for quick reply.
If I go for a custom room, what is the best out there?
Do I loose anything by not upgrading the stock room?
Jotne said:
Thanks for quick reply.
If I go for a custom room, what is the best out there?
Do I loose anything by not upgrading the stock room?
Click to expand...
Click to collapse
they are all pretty damn good roms mate! too hard to choose really, just best to flash em, and see remember to make a nandroid backup also
u shouldn't loose anything apart from bloatware
If you want a custom based on stock, i suggest Android revolution, Viper Rom, or SD ROM.
Sent from my HTC One X using xda premium
CM10.1 ROM
Click to expand...
Click to collapse
UFFFFF
I did try out Cyanogen lastest image, that do work fine.
But I have to look long for how to find out that I needed to extract boot.img from the cyanogen zip file and install this with flashboot.
But now I like to go back to my original rom. I did take a nandroid backup, and also have an older nandroidbackup.
Its not possible to make the phone go back. When I start restor, all looks ok MD5 etc, but then gets this message
Error while restoring /system!
Do I have to do more flashboot stuf to go back?
I am still able reinstall Cyanogen from zip file. But my Cyanogen backup also fail.
Why
Edit. The Cyanogen Image is 4.2.2 and Orginal image is 4.1.1. Could that be any problem?
Jotne said:
UFFFFF
I did try out Cyanogen lastest image, that do work fine.
But I have to look long for how to find out that I needed to extract boot.img from the cyanogen zip file and install this with flashboot.
But now I like to go back to my original rom. I did take a nandroid backup, and also have an older nandroidbackup.
Its not possible to make the phone go back. When I start restor, all looks ok MD5 etc, but then gets this message
Error while restoring /system!
Do I have to do more flashboot stuf to go back?
I am still able reinstall Cyanogen from zip file. But my Cyanogen backup also fail.
Why
Edit. The Cyanogen Image is 4.2.2 and Orginal image is 4.1.1. Could that be any problem?
Click to expand...
Click to collapse
Are you sure you've made the backup with the same recovery as you are attempting to restore it with?
The Android version shouldn't really matter, but there may be exceptions for some things.
Sent from my HTC One X using xda premium
Jotne said:
UFFFFF
I did try out Cyanogen lastest image, that do work fine.
But I have to look long for how to find out that I needed to extract boot.img from the cyanogen zip file and install this with flashboot.
But now I like to go back to my original rom. I did take a nandroid backup, and also have an older nandroidbackup.
Its not possible to make the phone go back. When I start restor, all looks ok MD5 etc, but then gets this message
Error while restoring /system!
Do I have to do more flashboot stuf to go back?
I am still able reinstall Cyanogen from zip file. But my Cyanogen backup also fail.
Why
Edit. The Cyanogen Image is 4.2.2 and Orginal image is 4.1.1. Could that be any problem?
Click to expand...
Click to collapse
If you are using CWM recovery u should be able to go into the backup file (under clockwork mod/backup on sd) and take the boot.img u need to flash via fastboot there. Put it in your fastboot file and then flash using "fastboot flash boot boot.img"
So I should take the boot.img from the backup, run fastimage and restore it?
Then try to restore the backup using clockworkmod?
I am not user if the backup was made with
recovery-clockwork-touch-5.8.2.7-endeavoru.img or
recovery-clockwork-touch-5.8.3.1-endeavoru.img
Is it important to restore with correct version? If so how to see what version that was used?
I am not able to go back to my old image
Not sure why, but the Cyanogenmod does not give me any Mobil data (3G etc)??
I tried to restore the boot.img from correct backup using flashboot flash boot boot.img and then try to restore.
But still I get Error while restoring /system!
Some note:
I made a backup of my working Cyanogenmod, this I am able to restore without getting the restoring error.
No I also have tried recovery-clockwork-touch-5.8.4.0-endeavoru.img
But there are some different thing going on.
When I first tested to restore my original image, I get menu like this when trying to restore:
Code:
Yes-Restore
No
Go-Back
Now I do get:
Code:
No
No
No
No
No
Yes-Restore
No
No
No
*** Go back
Have I used another clockworkmode to make the backup?
If you want to be sure you use the same recovery as where the nandroid is made with ? Flash the recovery.img from the nandroid folder.
Then flash the boot.img from the nandroid folder, go into recovery :
Factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts & storage - format cache, data, system
Then restore the nandroid.
Thanks
You saved my day.
It seems that the backup was done with CWM based v6.0.2.7
Not sure where I have got this version.
Latest version listed here: http://www.clockworkmod.com/rommanager is 5.8.4.0 and not 6.0.2.7 that I have used
Here http://forum.xda-developers.com/showthread.php?t=1941630 is 6.0.3.2 listed
What is the latest version of CWM for HTC ONE x and where to get it?
And last, what is the best to use
Yeah well after all the replies i thought i chip in give my 2 cents
This is one of the latest i use now.
http://db.tt/SPXdFfPw
Everything is working fine and I start to understand how its connected together.
But there are one thing that still puzzle me, the boot.img
When and why do I need to change that when I go to and from CM 10.1.2 (4.2.2) and Original image 4.1.1
What trigger the need of the change?
Should not this be restored correctly when I restore a backup. (In Clockwork mode)?
Does this work automatically whit Philz recovery 5.6.1.img?
I do like to change image in my phone without need a PC to run fastboot !!
When you change rom you need to flash the corresponding boot.img from that particular rom or nandroid backup.
We can't flash boot.img files via recovery because we have s-on devices so fastboot is a must.
Wilts panttsic
Ok, thats some sad, but thanks a lot for you help here
No problem.
CASE CLOSED !
Mr Hofs said:
No problem.
CASE CLOSED !
Click to expand...
Click to collapse
Another one for the Hof!!! :good:
exocetdj said:
Another one for the Hof!!! :good:
Click to expand...
Click to collapse
1 for Hofs = 1 for everybody mate.....we all are helping here !
Hey guys, just a quick question about restoring from a nandroid backup. Let's assuming I'm using custom rom A and made a nandroid backup of it. Then later on, I change to custom rom B and made another nandroid backup of that.
Well, assuming the boot.img from both custom rom A and B are different, then say if I were to restore back to custom rom A, I would have to re-flash the boot.img for that rom correct? OR, will restoring custom rom A from the nandroid backup also flash the boot.img for me automatically?
I came from other phones where flashing a new rom or from a nandroid backup is simply a one-step process. HTC One X is the first phone I've used where I have to deal with flashing the boot.img as an additional step as well, so just wanna confirm if this is the case for a nandroid restore as well.
chaoscreater said:
Hey guys, just a quick question about restoring from a nandroid backup. Let's assuming I'm using custom rom A and made a nandroid backup of it. Then later on, I change to custom rom B and made another nandroid backup of that.
Well, assuming the boot.img from both custom rom A and B are different, then say if I were to restore back to custom rom A, I would have to re-flash the boot.img for that rom correct? OR, will restoring custom rom A from the nandroid backup also flash the boot.img for me automatically?
I came from other phones where flashing a new rom or from a nandroid backup is simply a one-step process. HTC One X is the first phone I've used where I have to deal with flashing the boot.img as an additional step as well, so just wanna confirm if this is the case for a nandroid restore as well.
Click to expand...
Click to collapse
You have to flash the boot.img for the ROM you're restoring through fastboot. Recovery cannot flash boot.img for you since you need S-OFF, which impossible to achieve (let's not go there).
tomascus said:
You have to flash the boot.img for the ROM you're restoring through fastboot. Recovery cannot flash boot.img for you since you need S-OFF, which impossible to achieve (let's not go there).
Click to expand...
Click to collapse
yup got it. Thanks!
Hi guys,
Before I rooted and flashed new roms on my M8, I took a nandroid backup of my phone as it came out of the box. However, I can't seem to restore this anymore. I'm not sure if it's a problem with the backup I took or if it's just not possible. I have restored backups of other custom roms and they have been fine.
I'm not that fussed as I'm hopeful an RUU will come out eventually. I'd just like to understand why.
I have an International unlocked M8 bought in the UK.
Thanks!
leongwengheng said:
Hi guys,
Before I rooted and flashed new roms on my M8, I took a nandroid backup of my phone as it came out of the box. However, I can't seem to restore this anymore. I'm not sure if it's a problem with the backup I took or if it's just not possible. I have restored backups of other custom roms and they have been fine.
I'm not that fussed as I'm hopeful an RUU will come out eventually. I'd just like to understand why.
I have an International unlocked M8 bought in the UK.
Thanks!
Click to expand...
Click to collapse
Which recovery did you backup with, which are you running now, and at any point did you do the GPE conversion?
Sir-Fix-a-Lot said:
Which recovery did you backup with, which are you running now, and at any point did you do the GPE conversion?
Click to expand...
Click to collapse
Hi, mate. I did the back up in TWRP 2.7.0.2 - although now I am on TWRP 2.7.1.0. Not sure if that makes a difference?
Yes I did convert to GPE at the beginning. Here's how I got to where I am today:
1) Flashed TWRP 2.7.0.2
2) Did a nandroid backup of factory state
3) Converted to GPE using Graffixnyc RUU
4) Flashed Skydragon GPE
5) Then I wanted to try Skydragon Sense, so I changed CID to 11111111, flashed stock recovery and did factory reset
6) Flashed TWRP 2.7.1.0 to replace stock recovery
7) Now I am currently using Skydragon Sense
I thought I would be able to restore the backup from step 1 after doing step 5. It would be nice to know I can still go back to the phone in that state if I ever decide to sell.
Thanks for your help!
leongwengheng said:
Hi, mate. I did the back up in TWRP 2.7.0.2 - although now I am on TWRP 2.7.1.0. Not sure if that makes a difference?
Yes I did convert to GPE at the beginning. Here's how I got to where I am today:
1) Flashed TWRP 2.7.0.2
2) Did a nandroid backup of factory state
3) Converted to GPE using Graffixnyc RUU
4) Flashed Skydragon GPE
5) Then I wanted to try Skydragon Sense, so I changed CID to 11111111, flashed stock recovery and did factory reset
6) Flashed TWRP 2.7.1.0 to replace stock recovery
7) Now I am currently using Skydragon Sense
I thought I would be able to restore the backup from step 1 after doing step 5. It would be nice to know I can still go back to the phone in that state if I ever decide to sell.
Thanks for your help!
Click to expand...
Click to collapse
You need to undo the GPE conversion since it has resized your system partition. Follow this guide:
Going back to Sense from [RUU] Google Edition Conversion.Graffixync UPDATE 12th May
In the last part where it says to flash a ROM, just restore your backup, but have a ROM handy just in case.
Sir-Fix-a-Lot said:
You need to undo the GPE conversion since it has resized your system partition. Follow this guide:
Going back to Sense from [RUU] Google Edition Conversion.Graffixync UPDATE 12th May
In the last part where it says to flash a ROM, just restore your backup, but have a ROM handy just in case.
Click to expand...
Click to collapse
Thanks for the quick reply!
I have followed this procedure already (that's how I'm running Skydragon Sense rom now). Before I flashed the Skydragon rom, I tried to restore the first backup I did, but it failed. I have successfully flashed ViperOne and Skydragon Sense though, so I'm sure I have successfully re-converted it away from the GPE partition. I'll try to restore it again now and see what happens.
leongwengheng said:
Thanks for the quick reply!
I have followed this procedure already (that's how I'm running Skydragon Sense rom now). Before I flashed the Skydragon rom, I tried to restore the first backup I did, but it failed. I have successfully flashed ViperOne and Skydragon Sense though, so I'm sure I have successfully re-converted it away from the GPE partition. I'll try to restore it again now and see what happens.
Click to expand...
Click to collapse
You could try loading TWRP 2.7.0.2 and restoring from there, but it shouldn't be an issue with 2.7.1.0
leongwengheng said:
1) Flashed TWRP 2.7.0.2
2) Did a nandroid backup of factory state
Click to expand...
Click to collapse
Shouldn't you boot recovery and then do a nandroid backup before flashing recovery?
If you've flashed recovery and then made a nandroid backup i guess you won't have a backup of your factory settings.
Niorun said:
Shouldn't you boot recovery and then do a nandroid backup before flashing recovery?
If you've flashed recovery and then made a nandroid backup i guess you won't have a backup of your factory settings.
Click to expand...
Click to collapse
Stock recovery won't make a backup, only a custom recovery. He did right, flashed TWRP, and make a backup of the stock ROM it was loaded with. He's having issues restoring it.
That's a damn good point. I've only ever backed things up using custom recoveries. Never thought of using the stock recovery. I guess I can never get back to factory stock then.
I should be able to get back to the factory ROM though (albeit rooted and with flash recovery)?
Sent from my HTC One_M8 using XDA Free mobile app
leongwengheng said:
That's a damn good point. I've only ever backed things up using custom recoveries. Never thought of using the stock recovery. I guess I can never get back to factory stock then.
I should be able to get back to the factory ROM though (albeit rooted and with flash recovery)?
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Read my post above, the stock recovery cannot backup, only a custom recovery can. Your steps were proper. Is there an RUU available for your model, or a .zip to be flashed with fastboot?
Let me rephrase:
Shouldn't you boot custom recovery and then do a nandroid backup before flashing custom recovery?
If you've flashed custom recovery and then made a nandroid backup i guess you won't have a backup of your factory settings.
Sir-Fix-a-Lot said:
Read my post above, the stock recovery cannot backup, only a custom recovery can. Your steps were proper. Is there an RUU available for your model, or a .zip to be flashed with fastboot?
Click to expand...
Click to collapse
As far as I was aware, there are no stock RUU's available for any M8 at the moment?
Niorun said:
Let me rephrase:
Shouldn't you boot custom recovery and then do a nandroid backup before flashing custom recovery?
If you've flashed custom recovery and then made a nandroid backup i guess you won't have a backup of your factory settings.
Click to expand...
Click to collapse
leongwengheng said:
1) Flashed TWRP 2.7.0.2
2) Did a nandroid backup of factory state
Click to expand...
Click to collapse
That's what he did. He wouldn't have been able to make the backup without booting the custom recovery, so append his steps like this:
1) Flashed TWRP 2.7.0.2
1a) Booted recovery
2) Did a nandroid backup of factory state
---------- Post added at 02:50 AM ---------- Previous post was at 02:50 AM ----------
leongwengheng said:
As far as I was aware, there are no stock RUU's available for any M8 at the moment?
Click to expand...
Click to collapse
There is. What is your model? The intl unlocked?
Niorun said:
Let me rephrase:
Shouldn't you boot custom recovery and then do a nandroid backup before flashing custom recovery?
If you've flashed custom recovery and then made a nandroid backup i guess you won't have a backup of your factory settings.
Click to expand...
Click to collapse
Generally you should boot custom recovery and mare a nandroid backup.Philz allows you to backup your stock recovery.But twrp doesnot.Yes if he has flashed custom recovery without taking the bkup of stock recovery he wont have full 100% stock rom.Also if the op provides details of what version on stock rom and cid he is using then we might be able to get a stock recovery for him.
Sir-Fix-a-Lot said:
That's what he did. He wouldn't have been able to make the backup without booting the custom recovery, so append his steps like this:
1) Flashed TWRP 2.7.0.2
1a) Booted recovery
2) Did a nandroid backup of factory state
---------- Post added at 02:50 AM ---------- Previous post was at 02:50 AM ----------
There is. What is your model? The intl unlocked?
Click to expand...
Click to collapse
Yeah, International unlocked (bought in UK).
leongwengheng said:
As far as I was aware, there are no stock RUU's available for any M8 at the moment?
Click to expand...
Click to collapse
Please provide what version of stock rom u r using.Also give the output of the following: fastboot getvar all
We wnat to know if u r s-off and whai tis your cid and mid.
Sir-Fix-a-Lot said:
That's what he did. He wouldn't have been able to make the backup without booting the custom recovery, so append his steps like this:
1) Flashed TWRP 2.7.0.2
1a) Booted recovery
2) Did a nandroid backup of factory state
---------- Post added at 02:50 AM ---------- Previous post was at 02:50 AM ----------
There is. What is your model? The intl unlocked?
Click to expand...
Click to collapse
Booting to and flashing are different things.
I mean:
1: fastboot boot recovery <recovery.img>
2: nandroid backup
3: fastboot flash recovery <recovery.img>
Only that way you are able to perform a nandroid of your factory settings. I believe...
Niorun said:
Booting to and flashing are different things.
I mean:
1: fastboot boot recovery <recovery.img>
2: nandroid backup
3: fastboot flash recovery <recovery.img>
Only that way you are able to perform a nandroid of your factory settings. I believe...
Click to expand...
Click to collapse
Yep u r right.
Jyotirdeb said:
Generally you should boot custom recovery and mare a nandroid backup.Philz allows you to backup your stock recovery.But twrp doesnot.Yes if he has flashed custom recovery without taking the bkup of stock recovery he wont have full 100% stock rom.Also if the op provides details of what version on stock rom and cid he is using then we might be able to get a stock recovery for him.
Click to expand...
Click to collapse
Thanks for your input. I foolishly didn't take a note of the CID before I changed it to GOOGL01 the first time, but I'm definite it began with HTC followed by some numbers.
Before doing a factory reset when switching away from GPE, I flashed the firmware 1.54.401.5.
Jyotirdeb said:
Please provide what version of stock rom u r using.Also give the output of the following: fastboot getvar all
We wnat to know if u r s-off and whai tis your cid and mid.
Click to expand...
Click to collapse
Once this info is provided, he can look here for a ROM
http://forum.xda-developers.com/showthread.php?t=2701376
and this thread may be of some help:
http://forum.xda-developers.com/showthread.php?t=2694600
I'm still looking for the RUU thread
So I've been trying out a bunch of roms and I've decided I want to go back to a previous nandroid backup on TWRP that I made. I wipe everything, restore the backup and reboot, but it never boots past the stock Google animation (4 spinning dots, running CleanRom). Does anybody know how to fix this? Am I improperly restoring the backup, and if so how should I do it?
tannerrblake said:
So I've been trying out a bunch of roms and I've decided I want to go back to a previous nandroid backup on TWRP that I made. I wipe everything, restore the backup and reboot, but it never boots past the stock Google animation (4 spinning dots, running CleanRom). Does anybody know how to fix this? Am I improperly restoring the backup, and if so how should I do it?
Click to expand...
Click to collapse
Restoring a nandroid backup is as easy as it gets. More than likely your backup nandroid is corrupt. You probably just have to install the basic ROM and start new.
That's what I ended up doing. Is it just bad luck on my end that it ended up like that? I don't want to continue making backups that won't work haha.
tannerrblake said:
That's what I ended up doing. Is it just bad luck on my end that it ended up like that? I don't want to continue making backups that won't work haha.
Click to expand...
Click to collapse
germanguy is correct, you will need to start afresh
may be prudent to reflash a fresh recovery also
and if you have no rom or working backup on your internal sd, see my sig
exocetdj said:
germanguy is correct, you will need to start afresh
may be prudent to reflash a fresh recovery also
and if you have no rom or working backup on your internal sd, see my sig
Click to expand...
Click to collapse
How would I go about flashing a new recovery? Thanks for the replies, appreciate it.
tannerrblake said:
How would I go about flashing a new recovery? Thanks for the replies, appreciate it.
Click to expand...
Click to collapse
get your custom recovery img and place it in your fastboot (or adb or whatever you called it) folder on your pc, for ease, rename it recovery.img
boot phone into fastboot
open up cmd and then type "fastboot flash recovery recovery.img"
then "fastboot erase cache"
then you should have a fresh recovery without any issues installed
exocetdj said:
get your custom recovery img and place it in your fastboot (or adb or whatever you called it) folder on your pc, for ease, rename it recovery.img
boot phone into fastboot
open up cmd and then type "fastboot flash recovery recovery.img"
then "fastboot erase cache"
then you should have a fresh recovery without any issues installed
Click to expand...
Click to collapse
Thanks so much. Now that I think about it I don't know for sure if I'm on the latest version of TWRP, so I'll try that.
tannerrblake said:
Thanks so much. Now that I think about it I don't know for sure if I'm on the latest version of TWRP, so I'll try that.
Click to expand...
Click to collapse
always best to be on latest version, i use philz but its down to personal preference, they all do the same thing well lol
What version of TWRP?
I had the same thing happen on my M8 back when I got it in early May. Couldn't get the nandroid to restore, so I ended up just flashing the desired ROM again and setting up the phone manually.
I've since updated TWRP and the restore works (new nandroid). Not sure if it was just a random thing, or a bug with that particular version of TWRP. But updating TWRP is a good place to start.
when you enter tw you make a factory reset
thats clear
but what with this clear dalvik and restore boot option
here must be the troubleshooting solution