Develop Bugs

[Q] Easiest way to get out of this boot loop?

Specs: I had Galaxy Nexus LTE 4.0.4 w/ unlocked bootloader and root access. I have the GN toolkit if that helps.
Cause: I used the Font Installer app to change system font. I now know that not all of the fonts are working properly and emailed the developer about it. However, I am currently stuck in a boot loop after changing to one of the fonts.
I would prefer to not lose everything and if I didn't care about that, then I would just go for it and I think that I could get it working again. But since it was just a font change, I thought it might be possible to fix it without going through all of that. I am hoping I can just change some system files or something and get it to boot then select a different .tff font that I know works. THANKS!
If I reload the 4.04 update.zip that I still can access, will that wipe everything/will I have to re-setup a bunch of things? Is it OK to clear cache partition and Dalvik Cache? Thank you.

Did you take a nandroid backup of this ROM at any point? If so, you could do an advanced restore of system only.
Sent from my Galaxy Nexus using Tapatalk

cmstlist said:
Did you take a nandroid backup of this ROM at any point? If so, you could do an advanced restore of system only.
Click to expand...
Click to collapse
No, unfortunately I did not, but I will look into that once I am back up and running.
**EDIT: I have CWM Recovery v5.5.0.4 running now. Is it possible to do a backup at THIS point in time and then restore everything but system?

Druas said:
No, unfortunately I did not, but I will look into that once I am back up and running.
**EDIT: I have CWM Recovery v5.5.0.4 running now. Is it possible to do a backup at THIS point in time and then only restore system?
Click to expand...
Click to collapse
Okay. In that case, flashing the ROM's update.zip should work and shouldn't wipe your data. Best to take a nandroid backup first, just in case of trouble.
Sent from my Galaxy Nexus using Tapatalk

cmstlist said:
Okay. In that case, flashing the ROM's update.zip should work and shouldn't wipe your data. Best to take a nandroid backup first, just in case of trouble.
Click to expand...
Click to collapse
Ok I made the backup first. When I try to load the update.zip though, it says, "assert failed: appy_patch_check("/system/fonts/Roboto-Regular.ttf" <then a whole BUNCH of numbers and letters which I can type out if they will actually be helpful> "E:Error in /sdcard/Download/update.zip (Status 7) Installation aborted."

Is that an incremental update.zip for upgrading? What you need is a zip containing the entire ROM.
Alternately use fastboot to flash system.img from the stock ROM if you were already using stock.
Sent from my Galaxy Nexus using Tapatalk

cmstlist said:
Is that an incremental update.zip for upgrading? What you need is a zip containing the entire ROM.
Click to expand...
Click to collapse
Yeah I used: http://forum.xda-developers.com/showthread.php?t=1481044 So I need to install 4.0.2 first? Unfortunately that is the only upgrade.zip I have on my phone and I don't know how to load new ones on there without booting into Android.
cmstlist said:
Alternately use fastboot to flash system.i mg from the stock ROM if you were already using stock.
Click to expand...
Click to collapse
What? Can you explain further? I was using stock 4.0.4

Druas said:
Yeah I used: http://forum.xda-developers.com/showthread.php?t=1481044 So I need to install 4.0.2 first? Unfortunately that is the only upgrade.zip I have on my phone and I don't know how to load new ones on there without booting into Android.
What? Can you explain further? I was using stock 4.0.4
Click to expand...
Click to collapse
You can download another zip to your computer and use adb push to get it onto the GN's internal storage.
I don't have the CDMA version but here's what I am able to find. Check this thread:
http://forum.xda-developers.com/showthread.php?t=1481613
A completely stock 4.0.4 (aside from root, busybox, de-odex) from that thread is here:
http://dev-host.org/uMJ
So you download that to your computer and put it in the same folder as adb. Boot the phone into Clockwork Recovery and then plug it into your computer. (There are other guides to getting adb to work on your phone so I won't cover that here.) Run adb devices to make sure it sees your phone. In Clockwork you also have to go to mounts and storage and make sure /data is mounted.
Then:
adb push GalaxyNexusCDMA-4.0.4-StockRootedNoRadio.zip /sdcard/stock.zip
Subsequently in Clockwork, you will be able to find that stock.zip in the list of zips you can apply. After applying that zip, any damage caused by messing with the fonts should be reverted.
---- or ----
The alternative would be to download the factory 4.0.2 image from here:
https://dl.google.com/dl/android/aosp/mysid-icl53f-factory-65895fa8.tgz
Inside that archive is a system.img file which you can flash to the phone by fastboot over USB. Immediately afterwards, you would then boot into CWM and apply the incremental update.zip you already have on there. This will take you to stock 4.0.4 unrooted and hopefully bootable!

cmstlist said:
The alternative would be to download the factory 4.0.2 image from here:
Inside that archive is a system.img file which you can flash to the phone by fastboot over USB. Immediately afterwards, you would then boot into CWM and apply the incremental update.zip you already have on there. This will take you to stock 4.0.4 unrooted and hopefully bootable!
Click to expand...
Click to collapse
While your instructions were good, I tried some things on my own about 20 min before you made that post and screwed up and erased userdata. So, I cannot say for sure if it would have worked, but I bet it would have and I wish I had been more patient.

Sorry to hear. Is it bootable now at least?
The userdata erase problem is why I now have to remember in every phone recovery situation - adb pull the entire contents of internal storage from within CWM before doing anything risky.
Sent from my Galaxy Nexus using Tapatalk

Yeah the phone has booted, I just have to spend some time recovering what I can. I will hopefully make better backups for the future. At least I learned some stuff. I still can't believe this was all caused by changing a FONT in a program designed to change fonts.

Druas said:
Yeah the phone has booted, I just have to spend some time recovering what I can. I will hopefully make better backups for the future. At least I learned some stuff. I still can't believe this was all caused by changing a FONT in a program designed to change fonts.
Click to expand...
Click to collapse
Right, well this font changer program edits the system partition of your phone, which makes it risky. In the future, the best course of action with any "risky" change is:
- Take a nandroid backup first.
- Copy the nandroid backup out of the phone (it's in a subfolder of clockworkmod on internal storage).
- If you are doing anything that leads you to fear that the whole internal storage could get blanked, copy all of that out of the phone too.
- Now if you can't boot, you can selectively restore the system partition or the whole thing to try and fix it.
- And now if your internal storage gets blanked, your backup is safe.

cmstlist said:
Right, well this font changer program edits the system partition of your phone, which makes it risky. In the future, the best course of action with any "risky" change is:
- Take a nandroid backup first.
- Copy the nandroid backup out of the phone (it's in a subfolder of clockworkmod on internal storage).
- If you are doing anything that leads you to fear that the whole internal storage could get blanked, copy all of that out of the phone too.
- Now if you can't boot, you can selectively restore the system partition or the whole thing to try and fix it.
- And now if your internal storage gets blanked, your backup is safe.
Click to expand...
Click to collapse
Yeah I had no idea that there was a significant risk involved, otherwise I would have been more cautious. Some questions I have:
-With Titanium Backup, the only thing I need to be running batch backups of is all user apps + system data correct? And only restore apps not system data unless I am on the exact same ROM as before?
-Again with TB, is there stuff it consistently misses that I should backup manually?
-I always launched CWM Recovery through the GN toolkit using "6. Flash CWM Recovery, Standard." And sometimes I would select Recovery from the Fastboot menu and it would be back at the regular recovery. Is there a different way I should have been going about getting to the nandroid backup?
-I have now installed ROM Manager and hit "Flash CWM Recovery" and I have a nandroid backup when I reboot into recovery. Does this mean any time I choose Recovery from the Fastboot menu that it will boot into CWM Recovery?
Thanks again for all your help and advice!

[Q] Do I ALWAYS have to flash a new boot image when installing a rom?

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.

[Q] How to add 3.20.401.1 to a rooted phone

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 !

[Q] Help! Rooted 4.3, Backed up, and now cant restore backup

Hello, I recently rooted my wifes Note 2 that was on the latest OTA 4.3. Was not easy BTW. I did a back up in recovery of boot, system, and data. I figured I was good to go and start trying out other roms.
The first one I flashed was Macks Allstar 5.0 rom. Everything was great. Then my wife informed me that she did not have all of her contacts backed up to google and some were only saved to her phone. So then I figure I could just restore the original backup and extract the contacts and be able to install them to any rom.
Thats when everything went wrong. Everytime I tried restoring the back up,it would crash and recovery would do like a reboot. After many attempts I figured id try another version of recovery. After flashing many earlier versions of twrp and trying to restore, I finally was able to complete a restore from version 2.6. I was ecstatic. But then my heart sank again when boot always hangs on samsung logo. And that is where I'm stuck. I am able to flash other roms no problem but cant restore my original backup.
Needless to say my wife is ready to kill me.
Please if anyone could help me I would really appreciate it. I have searched throughout this forum and internet for hours and can not seem to find any help with this issue.
I am thankful to have been able to get this far with the help from the XDA community posts I never needed direct help even with prior phone rootings but this one has got me stumped. Thanks in advance

You need to flash Phil's recovery version 6.0.7.9. If you cant restore your backup with Phil's then I'm thinking you might be sol. Make sure you know where you saved the backup to. It's either on the phone's internal sd or external sd card. Choose the correct location in Phil's recovery and if it isn't corrupt it should work. You may also want to copy your backup onto your pc just in case because that's your only backup and doing a full wipe or odin restore could permanently delete it. Good luck.

tx_dbs_tx said:
You need to flash Phil's recovery version 6.0.7.9. If you cant restore your backup with Phil's then I'm thinking you might be sol. Make sure you know where you saved the backup to. It's either on the phone's internal sd or external sd card. Choose the correct location in Phil's recovery and if it isn't corrupt it should work. You may also want to copy your backup onto your pc just in case because that's your only backup and doing a full wipe or odin restore could permanently delete it. Good luck.
Click to expand...
Click to collapse
Thank you for your reply. I am at work right now and left the phone with my wife with a working rom. I will try phils recovery when I get home. As far as backups, I have two copies. One on my SD card and the other on PC but if they're both fried I guess that negates my efforts in redundancy. It's hard to believe the backup got corrupt so quickly. I have another backup of the 2nd rom I flashed and that one wont install as well.
Is there something I am doing wrong? If the backup file is corrupt, is there a way to extract contacts seperately out of backup?

Method b.
http://forum.xda-developers.com/showthread.php?t=2648855
My wife does that too. Sorry

ColeTrain! said:
Method b.
http://forum.xda-developers.com/showthread.php?t=2648855
My wife does that too. Sorry
Click to expand...
Click to collapse
Life of a married man. Haha!
Well, as my backup file was done with TWRP, I tried method B with TWRP recovery and it wont work so now I'm in the process of trying method A. Will update once I tried it.
I think my problem has to do with TWRP not playing friendly with 4.3 ROMS. If that is the case method A looks like it will work.:fingers-crossed:

alexandnen said:
Life of a married man. Haha!
Well, as my backup file was done with TWRP, I tried method B with TWRP recovery and it wont work so now I'm in the process of trying method A. Will update once I tried it.
I think my problem has to do with TWRP not playing friendly with 4.3 ROMS. If that is the case method A looks like it will work.:fingers-crossed:
Click to expand...
Click to collapse
That's exactly right. Bootloader isn't playing well with TWRP recovery. Phil"s 6.0.7.9 seems to be compatible in most ROM vs bootloader situations. Don't use latest version of Phil's recovery as it doesn't work as well and most people recommend this as well.
If Phil's recovery won't flash your restore then Odin all the way back to stock unrooted LK8 ROM then root it with the Toolkit and flash TWRP from the toolkit at the same time. Then see if you can restore at that point.

Looks like this project has come to an end. My wife likes her new rom and doesn't want to let me work on her phone anymore. She was able to get most of her contacts back I will make sure she backs her contacts to google and I will try to convince her to install Titanium backup to backup all her app data.
Unfortunately all I have is a work issued iphone that I have no interest in jailbreaking. I really don't see the point.
I am still confident that I could have eventually restored her backup successfully with the help here.
Thank you tx_dbx_tx and coletrain for your help.

Bootloop on nandroid backup?

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