yashsingh1/xdaforums huggingface dataset:
[One (M9) Original Android Development] Captain_Throwback:
Can you do a fresh boot into recovery and Wipe Data and then navigate to /data using the File Manager and take a screenshot of the contents? And also post that log? Thanks!
[One (M9) Original Android Development] Captain_Throwback:
In your log I notice this:

I:Unable to unlink '/data/data/com.facebok.kata/databases/qe_db: Operation not permitted'

When trying to restore that file, the job fails. The solution (unfortunately) is to use "Format Data" from the TWRP wipe menu to permanently delete that file. This will also wipe out your internal storage, so back that up either to your external SD or to a PC. I wouldn't restore that backup once you format data either - I'd start setting up clean/from scratch. I don't know what that file is, but I doubt it's supposed to be there. Probably best to delete the backup containing it as well.
[One (M9) Original Android Development] 2WildFirE:
Thanks for your reply, i will backup my data and try it.
[One (M9) Original Android Development] Captain_Throwback:
Can you do what I asked in my first reply before you do that?
[One (M9) Original Android Development] 2WildFirE:
yes, i try it before.

here is the log https://drive.google.com/file/d/0B8j9OdHN69y6Zl9jQ0o1ZmV2Wjg/view?usp=sharing

the last screenshot is after wiping DATA.

EDIT: Thanks Captain_Throwback you save my Day! All works fine here now! your'e my hero!
[One (M9) Original Android Development] antolfredo:
But the extsd card was formatted as FAT32 or NTFS for working backup

Inviato dal mio HTC One M9 utilizzando Tapatalk
[One (M9) Original Android Development] jollywhitefoot:
I can't get over how fast backup and restore is now. Thanks [MENTION=1162986]Captain_Throwback[/MENTION]
[One (M9) Original Android Development] Captain_Throwback:
Official 2.8.7.0 is live.
[One (M9) Original Android Development] migascalp:
Thank.

later the test. A new base is output :)
[One (M9) Original Android Development] osiedacz:
Sorry to quote myself, but I would love some input on this. Thank you.
[One (M9) Original Android Development] jollywhitefoot:
When you made your original system image backup, you didn't backup the stock recovery (recovery.emmc.win)?

You can get a stock recovery from Sneakyghost's spreadsheet here: http://xdaforums.com/one-m9/development/firmware-t3068243

Just download the stock, full-wipe 1.32.502.31 firmware, unzip it and use the recovery_signed.img file in there.

But, I'm curious...you're s-off, so why would you possibly wait around for AT&T to offer a significant update? I'm AT&T as well and I don't think they updated the M8 to lollipop until February!
[One (M9) Original Android Development] osiedacz:
Thanks for the reply. No, I couldn't backup my stock recovery, because the only way to install and use TWRP was to replace the stock recovery. In previous versions of Android (on my M8 for example) you could "boot to twrp" and root the phone prior to replacing recovery. By doing this, you could use adb to backup the recovery image.

So on the M9 I followed the instructions in the OP to get TWRP on the phone, then make an untouched system backup image prior to modifying it.

I'm not saying I will wait around, but I want to be prepared now for any future OTA in order to avoid having to use the RUU.
[One (M9) Original Android Development] jollywhitefoot:
Gotha..yeah, my question about backup of recovery was a brain cramp on my part. Anyway, you can get stock recovery from sneakghost's thread.
[One (M9) Original Android Development] hgoldner:
For future reference, and only if you are already rooted, following the instructions in this thread, you can save images of recovery, boot and system so that you can return to stock any time you want. I routinely backup my stock image files then reroot, and when an OTA comes out roll back.

If you keep a FAT32 formatted 16g or 32g sdcard available, you can roll them into a flashable update zip via download mode. (I actually keep them as Nandroids and have a Nandroid of stock recovery as well). I think this is also discussed elsewhere in this thread, but I don't regularly monitor this thread.

UPDATE - Captain pointed out to me that "if you're already rooted" on the M9, then your system partition has been modified, thereby killing OTA. (Doh!) I've got a UT device which has "root" even when unrooted running stock (for the diagnostic software to run), so I have the ability to pull this stunt without actually "rooting." It made ever so much sense to me until Captain pointed out that most devices aren't like mine. Apologies for the hijack.
[One (M9) Original Android Development] Captain_Throwback:
Maybe I don't understand, but why would you do that manual procedure when that's exactly what recovery does for you?
[One (M9) Original Android Development] osiedacz:
I appreciate the note, that is exactly how I used to do things on my M8. But if you notice in the thread, the first part says a prerequisite is a rooted device. This turns into a chicken and the egg race. To root the M9, you need to replace the stock recovery with TWRP. So at that point you can no longer back up the stock recovery. I've dug and dug and I don't see a new way to backup the stock recovery of an unrooted device or how to root the M9 without replacing the recovery.

---------- Post added at 02:31 PM ---------- Previous post was at 02:28 PM ----------

I agree. The current version of TWRP allows you to backup everything to img, except the stock recovery.

When a phone replaces the aftermarket recovery with the stock one, where does it get the stock recovery from? Another hidden partition? Or buried in the system files?
[One (M9) Original Android Development] Captain_Throwback:
I don't know. No devices that I have (all HTC) do that.
[One (M9) Original Android Development] yardi4life:
What happen to the theme from 2.8.6.4 ?
[One (M9) Original Android Development] liam_davenport:
The theme is in the beta recovery only, 2.8.7.0 is official
[One (M9) Original Android Development] Captain_Throwback:
It's not done. Still in review. That theme isn't supposed to be rolled out until TWRP 3.0. You can track the progress here: [WIP] gui: stock theme rework

P.S. And the version of the theme that was in 2.8.6.4 has since changed. I guess you didn't see the Beta versions that followed that one . . .
[One (M9) Original Android Development] Jhonys:
Just a noob question here,

Is there a quicker way to update my recovery (coming from 2.8.6.1) than all that ADB and such? Like flashing it through TWRP it self?

Cheers
[One (M9) Original Android Development] iElvis:
Flashify

There are other apps that will do it, but I've been using this one a long time and it works great.
[One (M9) Original Android Development] Captain_Throwback:
Yes, you should be able to update TWRP from within TWRP. Just download the image file, boot to recovery, and press the "Images..." button at the bottom of the page after selecting the Install option. Navigate to the image, select it, indicate it's a recovery image, and swipe. That easy ;).
[One (M9) Original Android Development] Captain_Throwback:
Not that this isn't a good option . . . but a separate app hasn't been necessary to flash TWRP for several versions now :).
[One (M9) Original Android Development] iElvis:
I did not know this! Thanks. :D
[One (M9) Original Android Development] osiedacz:
Got it. I have never had a device do this either, I only asked because it was mentioned in the OP under the changlog for 2.8.7.0
[One (M9) Original Android Development] yardi4life:
Ok. A well designed recovery is pleasing to the eyes, just like the rest of the UI on the phone. So hurry with good work :good:

Thanks! Any possibility for a 2.8.7.1 beta with new proposed theme ?:fingers-crossed: I did notice the screenshots in first post.
[One (M9) Original Android Development] Captain_Throwback:
There will not be a 2.8.7.1 Beta with the new theme, at least not unless there's an official 2.8.7.1 update necessary and then some subsequent reason to do an unofficial/beta update after that.

If you want a pretty recovery, just use the Materialised theme.
[One (M9) Original Android Development] Captain_Throwback:
If anyone really wants the updated stock theme to use on the latest official, I uploaded the latest version here: http://xdaforums.com/devdb/project/dl/?id=13238

Just follow the instructions here for how to install the theme (unless you see something there you like better ;)).
[One (M9) Original Android Development] joshuaw84:
You forgot [MENTION=2256702]Zanzibar[/MENTION] here...

Sorry for derail lol. But I had too.

Don't worry guys captain knows what's up!
[One (M9) Original Android Development] Captain_Throwback:
https://jenkins.twrp.me/job/hima-test/6/console

@Zanzibar

The above build fixes the broken offmode charging when powering off from within recovery. Most people wouldn't even notice it, tbh. I rarely turn off my device :eek:
[One (M9) Original Android Development] alhuang69:
I am going to try it now.

Thanks a lot.
[One (M9) Original Android Development] kinkiyo:
hello guys i have this problem , i'm noob on htc flashing please help me , i have unlocked my bootloader , but i have this error when i try to flash a twrp recovy for my htc m9 international please how i can solve this error ?
[One (M9) Original Android Development] Anzinger:
Perhaps you have to type Recovery instead of Recovry?
[One (M9) Original Android Development] Spegeli:
I have made a full backup:

Now im searching for the /storage/emulated/0/WhatsApp directory inside this backups files because this contains all my WhatsApp Images.

In which Files is this stored?

I hope someone can help me.

Mfg
[One (M9) Original Android Development] Captain_Throwback:
That's on your emulated storage, /sdcard. If you want that backed up, use MTP to copy it to your PC or copy it to an external storage device (Micro SD, USB-OTG).

That won't be included in a TWRP backup.

P.S. You shouldn't ever need to backup /cache, and you only need to back up either system or system_image, not both. That's just a waste of time.
[One (M9) Original Android Development] Spegeli:
bad ;-(
[One (M9) Original Android Development] Captain_Throwback:
Feel free to add your grievance here if you disagree with this approach: https://github.com/TeamWin/Team-Win-Recovery-Project/issues/276

Better yet, since TWRP is open source, please implement a solution and submit it to gerrit ;).
[One (M9) Original Android Development] Zanzibar:
Thanks [MENTION=3005003]joshuaw84[/MENTION] :D
[One (M9) Original Android Development] migascalp:
UMS seem broken with this build
[One (M9) Original Android Development] Captain_Throwback:
It appears to be mounting in the log just fine. You may need to reinstall the driver on your PC, as an adjustment was made to "fix" mass_storage in init.rc to match the proper protocol name. I had to go into Windows Device Manager and uninstall then reinstall the driver for it to load properly. After you do that, it should work fine again.
[One (M9) Original Android Development] nik3r:
And so I did ;) This happened after flashing 1.40 RUU, I thought I had a nice backup... well thank the cybergods for Titanium backup (that actually backs up this storage up to a certain size limit) or I would have been ****ed :D
[One (M9) Original Android Development] migascalp:
But with 2.8.7.0 from TeamWin UMS work fine?
[One (M9) Original Android Development] Captain_Throwback:
That's because this change hadn't been applied: https://github.com/omnirom/android_bootable_recovery/commit/f846cac3783914fc1bf905bd82769506b1a36f8b

which fixes an "error" in the init.rc, but seems to make it more difficult for USB function to switch to Mass Storage mode. It seems you just have to wait a bit longer for it to pop up, but mine did, eventually.
[One (M9) Original Android Development] migascalp:
Thank you for the clarification
[One (M9) Original Android Development] shokouhi:
Power and Volume Up got me out of recovery. Can I run the old recovery with the new base for the M9?

Shokouhi
[One (M9) Original Android Development] Captain_Throwback:
Can you try this version and see if it works any better?
[One (M9) Original Android Development] Captain_Throwback:
You don't need to downgrade your recovery (if anything, I'd upgrade it). Just battery-pull reset your device (Power+Volume Up for about 10 seconds) and it'll reboot.

The unresponsive touch screen happens occasionally. Rebooting fixes it. It's random and rare.
[One (M9) Original Android Development] shokouhi:
Yeah Volume Up and Power worked. I was under the impression it was volume down and power. Like many old HTC devices. So, i will keep running the new recovery. Thanks for your assistance Captain_Throwback. Thanks for the work on this project! Much appreciated!

Shokouhi
[One (M9) Original Android Development] hallstevenson:
I have an M9 on Verizon, TWRP 2.8.7.0, and only get the unresponsive touch screen when Aroma is running. I'm trying to install Viper v3.0 but can't use the touch screen. This happened with TWRP 2.8.6.4 too. I do have the latest VZW firmware installed. It's happening every time. I have rebooted to download mode, bootloader, back into recovery and round and round with no luck.

Viper 2.3.x works fine and it also uses Aroma.
[One (M9) Original Android Development] shokouhi:
I had an issue similar to this one. You may want to try re-flashing the TWRP recovery. That should take care of it.

Shokouhi
[One (M9) Original Android Development] hallstevenson:
I've went from 2.8.6.1 to 2.8.6.4 (via an RUU from user "dottat"), then used TWRP itself to flash 2.8.7.0, and just now, to 2.8.7.1_CPTB-B1-hima. Still behaves the same.... Just to be clear, in TWRP itself, the touch screen works just fine. It's only when Aroma is launched that it acts up. Sometimes I can check the box for agreeing with the terms, but after that, the "Next" button doesn't respond, nor can I tap any of the choices in the menu that pops up when you press the Power button (About, Back, Quit). I have to use the volume-up/down and power buttons to navigate.
[One (M9) Original Android Development] Captain_Throwback:
That's an AROMA issue. Viper must be using the 3.0 version of AROMA again . . .
[One (M9) Original Android Development] hallstevenson:
Thank you - I'm just trying to clear up where the issue is coming from. By the way, I think they're using 2.7-something of AROMA, but don't hold me to that.
[One (M9) Original Android Development] Captain_Throwback:
Hm, interesting. AROMA might need to blacklist another touch driver, then.
[One (M9) Original Android Development] bzhmobile:
It happend to me when the M9 is warm (more than 40° Celsius).

after a little time in the fridge , it's better...
[One (M9) Original Android Development] donmarkoni:
Finally managed to do a quick test for that version and I can tell you that it switches very fast between MTP and UMS. Didn't move any files, small, nor large, to check functionality, but I guess somebody would already report it.

Thanks! :cowboy:

BTW, do I remember correctly that you tried porting USB mode in booted system from Sprint, some time ago? I was talking to [MENTION=1102297]Sneakyghost[/MENTION] about it, just few hours ago, and I thought it was you trying it.
[One (M9) Original Android Development] BenPope:
...but too long and the condensate will probably kill it. Bad idea.
[One (M9) Original Android Development] hallstevenson:
I checked again after posting and it is v2.70 RC2, as I recall. Thing is, plenty of others (on Verizon, so same firmware and drivers) didn't have any trouble - that I'm aware of.
[One (M9) Original Android Development] Captain_Throwback:
Then I guess it can't be an AROMA or a TWRP issue. Some sort of hardware malfunction? Thermal throttling, perhaps? I honestly have no idea.
[One (M9) Original Android Development] migascalp:
After automatic drivers update ...

UMS finaly work

Great job :good:
[One (M9) Original Android Development] bzhmobile:
It's why i said : a little time :)

and of course in an hermetic bag :p
[One (M9) Original Android Development] yvtc75:
Hi All,

May someone kindly tell me how to configure dd block size in ramdisk or somewhere?

[BACKUP STARTED]
* Backup Folder: /external_sd/TWRP/BACKUPS/xxx/xxx_LRX22G_release-keys/
Backing up Boot...
I:Backup command: 'dd if=/dev/block/mmcblk0p63 of='/external_sd/TWRP/BACKUPS/xxx/xxx_LRX22G_release-keys//boot.emmc.win'[B][COLOR="Red"] bs=16777216[/COLOR][/B] count=4'
4+0 records in
4+0 records out
67108864 bytes (64.0MB) copied, 0.370834 seconds, 172.6MB/s

Backing up Boot...
I:Backup command: 'dd if=/dev/block/mmcblk0p40 of='/data/media/0/TWRP/BACKUPS/zzz/zzz_LRX22G_release-keys//boot.emmc.win' [B][COLOR="Red"]bs=33554432[/COLOR][/B] count=1'
ioctl(): blank: Invalid argument
1+0 records in
1+0 records out
33554432 bytes (32.0MB) copied, 0.268168 seconds, 119.3MB/s
[One (M9) Original Android Development] HC4Life:
This version works great. I saw a little issue. the battery is always stuck in 66% but when i put the phone in charge it changes to the real battery percentage.
[One (M9) Original Android Development] ZeRo2o9:
ok ive been searching all night and can't figure out whats wrong, I have flashed the twrp-2.8.7.1_CPTB-B1-hima.img and rooted my m9, but now it won't let me flash anything, iv'e tried a rom and xposed and nothing will flash it just reboots the recovery again the second it tries to flash. System seems to be mounted so I don't think its that, idk if anyone has had this problem, ive flashed with my m7 and m9 tons of times but the m9 is different now :confused:
[One (M9) Original Android Development] Captain_Throwback:
That usually means bad zips.
[One (M9) Original Android Development] ZeRo2o9:
ok i downloaded them on my pc might be IDM messing with it, will try and download on my phone and try it. thanks :good:
[One (M9) Original Android Development] alhuang69:
The 2.8.7.1_CPTB-B1 is working great, especially the theme in blue.

I don't have the battery issue.
[One (M9) Original Android Development] bzhmobile:
I got it, but never mind, always is fine :D
[One (M9) Original Android Development] scoot0073:
i just flashed 2.8.7.1_CPTB-B1 wanting to make a system image backup b4 i root. So i selected "Backup" and in that menu i select "system image" so the things that are checked is Boot/system/system image/data

is this correct ? or should it be Boot/System image/Data thats checked? thanks

or should "System Image" be only thing selected ?
[One (M9) Original Android Development] clsA:
I may be wrong, but all I backup on first go is system.img
[One (M9) Original Android Development] scoot0073:
HAHA.. System Image it is, that is probably why i keep getting errors with the others checked also.

thanks bro
[One (M9) Original Android Development] scoot0073:
OK only having System Image checked I'm still getting Errors and I'm backing up via otg to a 32 gig flash drive.

I got to be over looking something, I read the OP so many times that I'm now confused /frustrated..

Can someone please advise me as to what I'm doing wrong.

Thanks

---------- Post added at 06:16 PM ---------- Previous post was at 06:06 PM ----------

[IMG="screen shot of the Error"]https://www.dropbox.com/s/p4k2zjabhlvws68/Screenshot_2015-07-04-11-22-04.png?dl=0[/IMG]
[One (M9) Original Android Development] clsA:
Well if the OTG is fat 32 it has a 4gig file size limit

Try saving it to internal storage
[One (M9) Original Android Development] jollywhitefoot:
Can you simplify and try to backup to internal storage?
[One (M9) Original Android Development] scoot0073:
OK thanks man I'll do that.
[One (M9) Original Android Development] Captain_Throwback:
Yup, you overlooked the FAQ, it seems.
[One (M9) Original Android Development] scoot0073:
Thanks guys backing up System Image to Internal storage worked. Captain no sir I read the OP many time's I thought I done formated my Flash drive as it states but nope it wasn't so after the other guy's said it was the format I checked and sure enough it was never reformatted like I thought I had done.. The simple thing.. Haha

Thanks again guy's now I can finally get root again
[One (M9) Original Android Development] jollywhitefoot:
I agree
[One (M9) Original Android Development] l1ttl3z:
I was wondering if any one had a stock recovery and system they post for 1.32.651.30. I made my backups but its been a while and smart me forgot to label them. Thankx in advance if anyone is able to help
[One (M9) Original Android Development] Captain_Throwback:
This isn't the thread in which to post this request. Please move this to Q&A in the forum for your variant (Sprint), or check in the stock backup thread there.
[One (M9) Original Android Development] scoot0073:
Deleted
[One (M9) Original Android Development] nuts77:
Hello,

sorry if this has already been posted but I couldn't find it...

Would anyone have a zip version of TWRP 2.8.7.0 that can be flashed from SD Card with the 0PJAIMG.zip method? (if that is still possible on the M9... I know it was with the M8)...

thank you !
[One (M9) Original Android Development] 2WildFirE:
Idk, but you can use flashify from ps to flash the IMG with your phone

Powered by SkyDragon ROM
[One (M9) Original Android Development] nuts77:
Thanks for your answer - but I'm unrooted atm (ant ad work), that's why I'm looking for an easy, fastboot-free and root-free way of flashing :)
[One (M9) Original Android Development] liam_davenport:
If no root, PC is the only way sorry
[One (M9) Original Android Development] Captain_Throwback:
You can make your own zip version. You just need an android-info.txt file from an RUU (or firmware.zip from OTA). Zip it up with the TWRP image (renamed to recovery.img) and place on the root of your FAT32-formatted SD card in download mode.

You really have to make your own zip, because the android-info.txt has to include your specific CID (unless you're SuperCID), model ID (which varies) and your current main/software version.
[One (M9) Original Android Development] nuts77:
Thanks a lot Captain ! Will try that (doesnt sound too complicated for me)

here's what my android-info.txt looks like. Need to add anything afterwards?

(sorry for the disturbance / Off topic)

edit // just flashed the zip, worked like a charm! thanks again :)
[One (M9) Original Android Development] kokinator02:
Hi, I'm a bit confused. If my system has never been touched, will TWRP back up my stock recovery or not?

The 2.8.7.0 changelog "system read only option feature" says, if one chooses not to allow to mount as r/w, the stock recovery will replace TWRP (on reboot, I guess). Is this mean stock recovery is still somewhere in there and can be backed up with the "raw" system image option?

But then I read in point 7 of FAQ that there's no way to back up stock recovery since TWRP flashed over, and to my total confusion, second note of point 8 says it's possible to restore stock recovery via TWRP's GUI (is this stock recovery refers to the one pulled out from some OTA zip or the original stock recovery?)

I don't want to root nor install custom ROMs, I just want to have a full back up (since there's no RUU for my Telcel, Mex. 1.27.600.1 firmware) in case I have to return it for warranty issues after I convert it to developer edition (which by the way, I think somehow it already is. My MID is 0PJA11000, the AT&T's developer edition I think, but my CID is HTC___332, go figure)
[One (M9) Original Android Development] jollywhitefoot:
You have to replace stock recovery with TWRP, so no it doesn't get backed up anywhere. When restoring stock system image, you also then need to restore stock recovery as the last step.

So for the full backup you want, make the backup in TWRP and also download the stock recovery.img file. Stock recovery images aren't hard to find in this forum. I don't have a direct link at the moment, though.