Develop Bugs

Twrp and Titanium backup question

First I'm wondering why with almost half the files i want to flash with twrp make it crash and reboot? Using the latest version. Flashed it from zip. I'm stumped. I end up flashing cwm to flash what i want then flash back to twrp. I would just use cwm because I'm more familiar with it but its not making my backups right for some reason.
Also was wondering being that alot of the apps I have uninstalled on tb are for my stock ROM which I have a backup of, can I delete them from my tb? So i don't have what feels like a thousand apps scroll to get what I want? Or will that mess something up? Most i will never use but i don't want to ruin my backup
Thanx

zombielion said:
First I'm wondering why with almost half the files i want to flash with twrp make it crash and reboot? Using the latest version. Flashed it from zip. I'm stumped. I end up flashing cwm to flash what i want then flash back to twrp. I would just use cwm because I'm more familiar with it but its not making my backups right for some reason.
Also was wondering being that alot of the apps I have uninstalled on tb are for my stock ROM which I have a backup of, can I delete them from my tb? So i don't have what feels like a thousand apps scroll to get what I want? Or will that mess something up? Most i will never use but i don't want to ruin my backup
Thanx
Click to expand...
Click to collapse
What version of TWRP are you using?
Also, I don't see any problem in deleting old stock backups from TB, as long as you have a nandroid backup of your stock ROM. Even if you do delete something, and don't have a nandroid, you can always flash back to stock.
Alternatively, you can use the search function in TB to avoid having to scroll through the really long list.

MeetMyBackhand said:
What version of TWRP are you using?
Also, I don't see any problem in deleting old stock backups from TB, as long as you have a nandroid backup of your stock ROM. Even if you do delete something, and don't have a nandroid, you can always flash back to stock.
Alternatively, you can use the search function in TB to avoid having to scroll through the really long list.
Click to expand...
Click to collapse
I'm on twrp 2.3.3.0 but i was having the problem on 2.2.2.0 the zips seem fine they flash in cwm it just makes it a hassle to go through all that trouble.

zombielion said:
I'm on twrp 2.3.3.0 but i was having the problem on 2.2.2.0 the zips seem fine they flash in cwm it just makes it a hassle to go through all that trouble.
Click to expand...
Click to collapse
I have both cwm and twrp in flashable zips could i be not flashing it right or something. I do it the way i do everything else and never have problems? I'm getting used to twrp and the backups work for me where cwm doesn't since first backup just the reboot is such a pain. Should i go to stock and start all over could it be I've messed singing up alone the way? I can't find a postof anyone having the same problem

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

How do you disable OTA updates on the m9?

Everyday my m9 asks me to install the new OTA update and I am sure I can't because I am rooted. Have TWRP, and have an unlocked bootloader. While my rom is the default rom the phone came with, I have modified a couple things in /system. Is there way to permanently disable OTAs without installing a custom rom? If not, is there a way to install this update without doing any data wipes or anything overly complicated? Any help would be EXTREMELY appreciated!!

wrozengfx said:
Everyday my m9 asks me to install the new OTA update and I am sure I can't because I am rooted. Have TWRP, and have an unlocked bootloader. While my rom is the default rom the phone came with, I have modified a couple things in /system. Is there way to permanently disable OTAs without installing a custom rom? If not, is there a way to install this update without doing any data wipes or anything overly complicated? Any help would be EXTREMELY appreciated!!
Click to expand...
Click to collapse
All you need is an untouched System and stock recovery to take the OTA.
their are many threads that explain how to do it. Just look around you'll figure it out.

clsA said:
All you need is an untouched System and stock recovery to take the OTA.
their are many threads that explain how to do it. Just look around you'll figure it out.
Click to expand...
Click to collapse
Like I said, my system isn't untouched, I have edited permissions.xml and removed some bloatware. And if I can do this, Will I still be rooted if I update or at least still S-off?

wrozengfx said:
Like I said, my system isn't untouched, I have edited permissions.xml and removed some bloatware. And if I can do this, Will I still be rooted if I update or at least still S-off?
Click to expand...
Click to collapse
Once s-off, you will stay that way unless you manually change it.
You can't be rooted and take an OTA anyway. You have to be 100% stock. You can root again once it's updated.

iElvis said:
Once s-off, you will stay that way unless you manually change it.
You can't be rooted and take an OTA anyway. You have to be 100% stock. You can root again once it's updated.
Click to expand...
Click to collapse
But that other guy just said all I need is a stock recovery. So which is it? 100% stock or just stock recovery

wrozengfx said:
But that other guy just said all I need is a stock recovery. So which is it? 100% stock or just stock recovery
Click to expand...
Click to collapse
Here > http://forum.xda-developers.com/one-m9/general/best-unlocking-bootloader-rooting-guide-t3087354
Steps 3 - 5
and the "other guy" said Untouched System + Stock Recovery
Also worth reading >> http://forum.xda-developers.com/one...ery-twrp-touch-recovery-t3066720/post59745198
6. So what's the proper procedure to root without breaking OTA?
There is no way to take an OTA after you root. However, prior to rooting, you can take a fully untouched system image backup with TWRP, which can be used to restore a fully stock system to the device in order to take an OTA.
7. How do I backup stock recovery prior to flashing TWRP?
You can't. The "fastboot boot" command appears to be disabled on the M9's ABOOT, so TWRP must be fastboot flashed over stock recovery. The firmware zip included in the OTA will include a usable stock recovery image. That can be extracted and flashed after stock system is restored so that the OTA can be applied.
8. How do I restore stock system so that I can accept an OTA?
Check the "Mount system as read-only" box in the Mount menu.
Restore stock "System Image" backup (This will only work if you've made a System Image backup prior to making any modifications to /system). As of the official 2.8.6.1 version, it is no longer necessary to fastboot flash the stock system image.
NOTE: If you made a stock system backup with one of the Beta TWRP versions, you will have to rename the backup file in the backup folder manually from "system.emmc.win" to "system_image.emmc.win" for the new official TWRP to see it as a "System Image" backup rather than a "System" backup. Otherwise, you'll get an error that the backup can't be restored because system is read-only.
Fastboot flash stock recovery (fastboot flash recovery recovery_signed.img)
NOTE: It is also possible to restore stock recovery via the TWRP GUI. Rename the stock recovery file to "recovery.emmc.win" and place in the backup folder with the stock system image. Recovery will then show as a restore option. MAKE SURE YOU REALLY WANT TO DO THIS, AS TWRP WILL BE GONE WHEN YOU REBOOT OUT OF RECOVERY!!
Reboot to system, install OTA.
Click to expand...
Click to collapse

If you want to disable, try freezing HtcDm.

mike.s said:
If you want to disable, try freezing HtcDm.
Click to expand...
Click to collapse
This helped me out nearly a year later. I am rooted and have a custom stock rom loaded but was still able to download the system update somehow and needed a way so that it would quit bugging me every day to not install it. By using Titanium Backup I was able to freeze 3 HtcDM processes.

OTA update to N

Hello everybody, it is time to update to Nougat and I'm ready to do it.
According to this thread https://forum.xda-developers.com/showpost.php?p=59745198&postcount=3
I need a system_image and stock recovery backup for being able to do an OTA.
I did it and I must restore the system_image and the stock recovery as written in point 8.
But according to this other thread https://forum.xda-developers.com/showpost.php?p=64299835&postcount=4
in Hidden Content point 13, I must backup the system_image, the stock recovery and the boot image.
I have only backupped system_image and recovery and I can download boot.emmc.win from the second thead, but I wish to ask:
Is it really necessary to restore boot.emmc.win? Now I'm on ViperOneM9 4.3.0
Why @Captain_Throwback didn't mention it in his official TWRP thread?
I thank you in advance anyone may help me to get the OTA in the right way

Balteck said:
Hello everybody, it is time to update to Nougat and I'm ready to do it.
According to this thread https://forum.xda-developers.com/showpost.php?p=59745198&postcount=3
I need a system_image and stock recovery backup for being able to do an OTA.
I did it and I must restore the system_image and the stock recovery as written in point 8.
But according to this other thread https://forum.xda-developers.com/showpost.php?p=64299835&postcount=4
in Hidden Content point 13, I must backup the system_image, the stock recovery and the boot image.
I have only backupped system_image and recovery and I can download boot.emmc.win from the second thead, but I wish to ask:
Is it really necessary to restore boot.emmc.win? Now I'm on ViperOneM9 4.3.0
Why @Captain_Throwback didn't mention it in his official TWRP thread?
I thank you in advance anyone may help me to get the OTA in the right way
Click to expand...
Click to collapse
If I didn't mention it, then you don't have to do it .

@Captain_Throwback can you maybe explain that a little further? I made the experience that people are facing problems if they return from a custom rom to a stock rom and don't wipe their phone. That's why I added the wiping step to my instructions. After that several users reported that their phones didn't boot after they restored the first version of my backups (which lacked the boot.img). Therefore, I thought the boot.img is needed as well and all backups got replaced over a year ago with the current version which includes the boot.img.
However, all this is based on the reports of users who had problems with returning back to stock. I've never faced these issues myself. So if there is anything wrong with my instructions I'll correct them, of course.
Sent from my HTC One M9 using XDA Labs

I thought it's impossible to backup the stock recovery seeing as twrp is needed to be flashed to make the backup..
Beamed in by telepathy.

shivadow said:
I thought it's impossible to backup the stock recovery seeing as twrp is needed to be flashed to make the backup..
Beamed in by telepathy.
Click to expand...
Click to collapse
Since firmware 3.x you can boot TWRP via fastboot from the bootloader without overwriting the currently installed stock recovery.

Flippy498 said:
@Captain_Throwback can you maybe explain that a little further? I made the experience that people are facing problems if they return from a custom rom to a stock rom and don't wipe their phone. That's why I added the wiping step to my instructions. After that several users reported that their phones didn't boot after they restored the first version of my backups (which lacked the boot.img). Therefore, I thought the boot.img is needed as well and all backups got replaced over a year ago with the current version which includes the boot.img.
However, all this is based on the reports of users who had problems with returning back to stock. I've never faced these issues myself. So if there is anything wrong with my instructions I'll correct them, of course.
Click to expand...
Click to collapse
Not sure what to explain - OTA does no verification on boot.img. So it doesn't have to be stock for an OTA to install. It's that simple.

Captain_Throwback said:
Not sure what to explain - OTA does no verification on boot.img. So it doesn't have to be stock for an OTA to install. It's that simple.
Click to expand...
Click to collapse
OK. I guess there was a little misunderstanding.
The current version of my instructions is meant to be used if you want to return to a clean stock system. (In other words the ability to install OTAs, again, is only a side effect.) I never was talking about the boot.img being necessary for being able to install the OTA. I thought you were saying that the boot.img wouldn't be needed inside a backup if you do a full wipe before the restoration and that the phone would still boot.
Sent from my HTC One M9 using XDA Labs

I'm little confused now.
For installing an OTA update I MUST have an untouched system partition and stock recovery.
But the steps I need to do are:
1) backup apps and settings
2) restore untouched system partiton and stock recovery partition from TWRP, doing a factory reset (wipe data, dalvik and cache)
3) boot the original stock OS, configure wifi and go to Software Update
4) download OTA(s)
5) apply update and reboot phone
6) with ADB start TWRP recovery and backup the new stock recovery and the new stock system_image
7) flash TWRP and new custom ROM
8) restore apps and settings from point 1)
So, is it possible that at step 3 my HTC cannot boot because I didn't restore the boot partition (I'm coming from ViperOneM9 4.3.0)?
Or is there a simpler method, without backuping, wiping, restoring?

Flippy498 said:
Since firmware 3.x you can boot TWRP via fastboot from the bootloader without overwriting the currently installed stock firmware.
Click to expand...
Click to collapse
Looks liks i used an out of date tutorial then.. What a bugger..
Beamed in by telepathy.

Anyone can confirm me that my previous steps are right?
So I may uodate to Android n without doubt
Thank you very much

Problem with restoring twrp backup

Hi everyone. My phone doesn't boot up after restoring twrp backup. Yesterday I made a Full backup and now if I try to restore that my phone just go into a bootloop. How can I resolve this problem?

mr.banana said:
Hi everyone. My phone doesn't boot up after restoring twrp backup. Yesterday I made a Full backup and now if I try to restore that my phone just go into a bootloop. How can I resolve this problem?
Click to expand...
Click to collapse
It depends on a lot of factors.
What ROM, what TWRP version, what partitions did you back up, etc.
If you want to get your phone working, you can flash any ROM of your choice from TWRP or restore stock image.

indian84 said:
It depends on a lot of factors.
What ROM, what TWRP version, what partitions did you back up, etc.
If you want to get your phone working, you can flash any ROM of your choice from TWRP or restore stock image.
Click to expand...
Click to collapse
TWRP Version is the last one (I think). I backup every partition so I made a full backup of everything. The rom Is the simple aosp. I very want back all my stuff

mr.banana said:
TWRP Version is the last one (I think). I backup every partition so I made a full backup of everything. The rom Is the simple aosp. I very want back all my stuff
Click to expand...
Click to collapse
Backing up all the partitions was the mistake.
Getting your stuff back looks difficult.
If you flash ROM using TWRP, your media files and anything stored on your phone won't be deleted.
But all your apps and stuff will be lost.