yashsingh1/xdaforums huggingface dataset:
[One (M8) Original Android Development] blackbuffalo:
Can not automatic unmount partition after backup or restore rom
[One (M8) Original Android Development] Captain_Throwback:
I don't know what this means. There are no details,, no mention of a version number, and no logs (not even a screenshot). Please don't post about an issue without the previously mentioned items.
[One (M8) Original Android Development] blackbuffalo:
Sorry, I talking about your newest version of twrp 2.8.8.3 but I forget log.

I will post log when I restore or backup rom nexttime
[One (M8) Original Android Development] Captain_Throwback:
Alright, one last test version:

https://basketbuild.com/devs/Captain_Throwback/One (M8)/ALL/Recovery

This one should work for everyone, and I'm not sure what features it includes so don't even ask, lol. Just do what you would normally do with it and confirm everything is working. I assume Adopted Storage is still working as it was.
[One (M8) Original Android Development] Isotopes:
when will this new twrp official comes out :confused:
[One (M8) Original Android Development] Captain_Throwback:
When it's ready ;).
[One (M8) Original Android Development] Isotopes:
hopefully soon ... looks very good :good:
[One (M8) Original Android Development] nkk71:
What exactly do you mean by official vs not official?
[One (M8) Original Android Development] Isotopes:
i can nothing find the new 2.8.9.0 on twrp site ... that's means for me this is not official released from twrp team
[One (M8) Original Android Development] Captain_Throwback:
Correct.

But I am the maintainer for the M8, so there's that . . . ;)
[One (M8) Original Android Development] Isotopes:
yes I know ... but it may be a beta version ;)
[One (M8) Original Android Development] Isotopes:
[MENTION=1162986]Captain_Throwback[/MENTION]

after flashing the latest version i become this failure "Failed to mount '/carrier' (Invalid argument)"

what is wrong ... Have that never seen before :confused: ... on twrp 2.8.7.0 all ok :eek:

here i have the logfile

EDIT: I see that this /carrier partition is only used on sense rom but not on gpe ... can you skip the mount when the partition unavailable :confused:
[One (M8) Original Android Development] Imotep95:
Thats super weird, just flashed lyapotas sense 003 rom with latest twrp. All good, no errors.
[One (M8) Original Android Development] blackbuffalo:
Confirm, latest version TWRP 2.8.9.0 work fine, flash and backup without any error
[One (M8) Original Android Development] Captain_Throwback:
Not all M8s have it. It's not really an error. Nothing to worry about.
[One (M8) Original Android Development] Isotopes:
thx ... I've been thinking ;)

i make a quick&dirty fix for me and removed/uncomment the partition from recovery.fstab :good:
[One (M8) Original Android Development] mrrocketdog:
[MENTION=1162986]Captain_Throwback[/MENTION] , finally was able to DL 2.8.9.0 flashed (have no PC so had to zip) through recovery twice and once by extSD/0P6BIMG method. each time recovery reported successful but twrp version remains 2.8.7.0. tried to catch log. maybe useful ?

https://www.dropbox.com/sh/rcs02bm49phq1le/AADgbTyy6WNX_Z1G98IxTL_ca?dl=0

thank you again for sharing your work.

[tp_noparse]W2NlbnRlcl1baW1nXWH0dHBzOi8vZGwuZHJvcGJveHVzZXJjb25OZW50LmNvbS91LzlzNjl3OTl3L0ltYWdlcy9TaWduYXR1cmVzL3ZhcmlvdXMvcmRiLmdpZlsvaW1nXVsvY2VudGVyXQ==[/tp_noparse]
[One (M8) Original Android Development] Captain_Throwback:
I don't understand what you're doing in that log. How are you flashing the image as a zip? Why not just flash the image file directly via TWRP?
[One (M8) Original Android Development] mrrocketdog:
flashed image as zip by using 'zip me' which creates a zip file from img.

dang. ok. guess i truly am a noob. did not know twrp could flash image files. thought they had to be .zips.

will try again.

[tp_noparse]W2NlbnRlcl1baW1nXWH0dHBzOi8vZGwuZHJvcGJveHVzZXJjb25OZW50LmNvbS91LzlzNjl3OTl3L0ltYWdlcy9TaWduYXR1cmVzL3ZhcmlvdXMvcmRiLmdpZlsvaW1nXVsvY2VudGVyXQ==[/tp_noparse]

---------- Post added at 03:44 PM ---------- Previous post was at 03:36 PM ----------

success :thumbup::D !

[tp_noparse]W2NlbnRlcl1baW1nXWH0dHBzOi8vZGwuZHJvcGJveHVzZXJjb25OZW50LmNvbS91LzlzNjl3OTl3L0ltYWdlcy9TaWduYXR1cmVzL3ZhcmlvdXMvcmRiLmdpZlsvaW1nXVsvY2VudGVyXQ==[/tp_noparse]
[One (M8) Original Android Development] JensL76:
I flashed TWRP with TWRP instead of Flashify. I have a HTC One M8 Dual Sim, no GPE. No such error. I have this Carrier partition, but it is empty.
[One (M8) Original Android Development] fyarf:
[MENTION=1162986]Captain_Throwback[/MENTION] not sure why but in 2.8.7.0 the os line in bootloader gets wiped by a system wipe. I've RUU'd 3 times and when wiping system, 2/3 the os line gets erased. Maybe that can be double checked in the upcoming update.
[One (M8) Original Android Development] Captain_Throwback:
I'm pretty sure that's related to Marshmallow, not TWRP. That being said, try the test version I posted and confirm whether that wipes it.
[One (M8) Original Android Development] fyarf:
Have the slow flash speeds been resolved from 2.8.8.3? I saw a lot of ppl saying 45 min flash times. None has mentioned one way or the other on 2.8.9.0.
[One (M8) Original Android Development] Captain_Throwback:
I post test versions because I need them tested. So, test.
[One (M8) Original Android Development] fyarf:
Starting RUU, will run some tests and report back.

Edit: Thanks for keeping the m8 up to date. Its approaching EOL from HTC, so the ppl like you in the community are a godsend.
[One (M8) Original Android Development] fyarf:
[MENTION=1162986]Captain_Throwback[/MENTION] flash times seem faster than 2.8.7.0, no os wipe, and restore from nandroid seemed to move faster than usual. seems like you have done some commendable work on the new version. I'll let you know if i run into any problems, but I wiped, changed file systems, flashed from scratch, wiped again, restored nandroid, and ran into no issues. Thanks for the work.

Edit: the new graphics (splash, unlock bar, etc) are all a welcome update.
[One (M8) Original Android Development] mrrocketdog:
+1 on speedy mo' fo'. did a back of 2 GB in 89sec. ! never has twrp worked so fast. complete wipe , new rom , etc etc was very noticeably faster.

no hiccups on my end.

very much appreciated [MENTION=1162986]Captain_Throwback[/MENTION].:good:

[tp_noparse]W2NlbnRlcl1baW1nXWH0dHBzOi8vZGwuZHJvcGJveHVzZXJjb25OZW50LmNvbS91LzlzNjl3OTl3L0ltYWdlcy9TaWduYXR1cmVzL3ZhcmlvdXMvcmRiLmdpZlsvaW1nXVsvY2VudGVyXQ==[/tp_noparse]
[One (M8) Original Android Development] JensL76:
It is faster for me, too.

I had system image verify errors when flashing CM13, wiping the partition did not help, but restarting TWRP. I will try again with some more Nighties, then get back with logs.
[One (M8) Original Android Development] mrrocketdog:
another report. [MENTION=1162986]Captain_Throwback[/MENTION] just restored a backup in 89sec. 2.8.7.0 took around 320sec. to restore.:good:

[tp_noparse]W2NlbnRlcl1baW1nXWH0dHBzOi8vZGwuZHJvcGJveHVzZXJjb25OZW50LmNvbS91LzlzNjl3OTl3L0ltYWdlcy9TaWduYXR1cmVzL3ZhcmlvdXMvcmRiLmdpZlsvaW1nXVsvY2VudGVyXQ==[/tp_noparse]
[One (M8) Original Android Development] kazavfr:
Can anyone explain how to flash TWRP .img file?

This TWRP, I will be with Marshmallow root?

Thanks.
[One (M8) Original Android Development] Imotep95:
I can't understand your question. You already have TWRP or what?

p.s. Fastest twrp recovery so far(twrp-2.8.9.0), should be official imho.
[One (M8) Original Android Development] dragontology:
Root's ROM based, it's independent of recovery. But, TWRP can root. If it detects the ROM isn't rooted, it will offer to do so (this isn't always the good choice).

To flash a .IMG recovery, just flash in TWRP (if you have TWRP now) like you normally would. Browse to the folder. You won't see the .IMG file. There should be an option, in the lower right corner, I think, to change the view from .zip to .img. Then you can flash the .img. I suspect that's how a lot of people are updating TWRP. The other way is with fastboot, but you need a PC for that. And I don't know the exact command off the top of my head, so I'm not going to guess (I'm probably right, but I don't want to steer anyone wrong).
[One (M8) Original Android Development] kazavfr:
I have a One M8 Dual Sim updated Marshmallow with TWRP 2.8.7.0 and I can’t root.
[One (M8) Original Android Development] Imotep95:
Send me your boot.img in pm, we'll continue there since it's not topic releated.
[One (M8) Original Android Development] sceryavuz:
[MENTION=912474]Dees_Troy[/MENTION] hi, is it possible to integrate TWRP Materialised Theme with TWRP M8? Some people merge theme and recovery, and create new .img file.

Thanks.

Edit : http://xdaforums.com/android/themes/theme-twrp-materialised-dark-light-play-t2915584
[One (M8) Original Android Development] hova1888:
What need select? 2.8.9.0 twrp first entered?

View attachment 3621109

Отправлено с моего HTC One_M8 через Tapatalk
[One (M8) Original Android Development] Captain_Throwback:
The latest TWRP already has an updated theme, made by the creator of the Materialised theme. If you want to use the Materialised theme, you are free to do so. That will not be integrated into the official TWRP - that would defeat the purpose of the theme engine. It's trivial to use a custom theme with TWRP.

---------- Post added at 08:03 PM ---------- Previous post was at 08:00 PM ----------

Just swipe - it should be fine.
[One (M8) Original Android Development] _purple_:
It should be mentioned though that TWRP's root should not be used in Marshmallow as it soft bricks the device.
[One (M8) Original Android Development] Captain_Throwback:
If using the latest version I posted, TWRP won't prompt for root if you're running Marshmallow ;).
[One (M8) Original Android Development] _purple_:
I know that and thank you for your work, but I had to mention just in case the person dragontology replied to was trying to use the version in post #1.
[One (M8) Original Android Development] dragontology:
Wow, thanks for the heads up. So do not allow TWRP to root the device on its own. But the new one (beta?) fixes it?

I've had such bad luck with this phone (the rare TWRP data encryption bug, Titanium not working, etc), I think I'm just gonna stick with what I have until I get a Nexus. Love my phone but it's crazy opposed to modification. Love what people have done for it though.
[One (M8) Original Android Development] Captain_Throwback:
New TWRP seems to fix quite a few problems - maybe it'll work better for you ;). I haven't seen the bug come up since the Marshmallow GPE ROMs came out, actually. I think you should give one of them a try :).

I'm a fan of my Sensified GPE ROM, personally . . . :o
[One (M8) Original Android Development] dragontology:
You haven't seen the bug come up? I thought you couldn't do anything since it didn't happen on your device? Have you been able to track it another way?

I heard something about SELinux support in TWRP or maybe I read it in the logs or whatever (when you flash a ROM). I wonder if SELinux being set to Enforcing in the ROM might have contributed. Or I could be completely full of it. But there are apps to change that (and terminal commands I suppose).

Where is your Sensified ROM? And does it work on Verizon?

I'm planning on doing a RUU once Verizon updates us in the next couple weeks anyway. Willing to screw up my device then since I'll be starting from scratch anyway.
[One (M8) Original Android Development] Captain_Throwback:
I said I'd seen that bug a couple of times - I just couldn't reproduce it, as it was random. I only ever had it on dh's ROM, though. SELinux shouldn't have anything to do with it - SELinux is permissive in TWRP, and that has nothing to do with SELinux in Android.

My Sensified ROM is in my (Sprint) GPE thread, but it will definitely boot on Verizon. I'm not sure if LTE works, but I haven't had enough Verizon users try it to tell me. If it doesn't, there's just a few build.prop edits that would be needed to enable it. So, give it a try - let me know :).
[One (M8) Original Android Development] dragontology:
Ah. It wasn't random for me. And it happened to me on AOSP ROMs as well, not just DH's. I got it every time. Thanks for the clarification on SELinux — I didn't know.

Fun fact: DH is on the Nexus 6P now, and is continuing his ROM over there. HTC apps and all. I do like the HTC camera app more than the Google Camera app, so it's tempting to try.

I'll try your ROM, just as soon as I can get my current setup Nandroid'd. And I'll report any issues and successes over there.
[One (M8) Original Android Development] evoholik:
Can someone mirror please. I keep getting 404 error. Thanks
[One (M8) Original Android Development] linar10:
Link working

HtcOneM8 & Tapatalk
[One (M8) Original Android Development] Captain_Throwback:
There is 100% nothing wrong with the link. Try a different browser, or try disabling your ad blocker or something.
[One (M8) Original Android Development] doomscooter:
Because in xda aplication ur link change with icon.
[One (M8) Original Android Development] Captain_Throwback:
Ah. That's helpful. I have a solution for that.

https://goo.gl/QAlDkZ

Same link, shortened :)
[One (M8) Original Android Development] JensL76:
I used TWRP 2.8.9.0-m8 for several days without any issues now.
[One (M8) Original Android Development] mrrocketdog:
+1

[tp_noparse]W2NlbnRlcl1baW1nXWH0dHBzOi8vZGwuZHJvcGJveHVzZXJjb25OZW50LmNvbS91LzlzNjl3OTl3L0ltYWdlcy9TaWduYXR1cmVzL3ZhcmlvdXMvcmRiLmdpZlsvaW1nXVsvY2VudGVyXQ==[/tp_noparse]
[One (M8) Original Android Development] smeejaytee:
Hi I'm just wondering but guessing they're isn't but is there a full materialised theme available for this version thanks for any info on this.
[One (M8) Original Android Development] Captain_Throwback:
No. But if you go read the Materialised thread you'll see what [MENTION=2719389]z31s1g[/MENTION]'s plans are for that.
[One (M8) Original Android Development] smeejaytee:
Thanks mate I did read that earlier that's actually why I said I'm guessing the isn't,

No problem anyway I can live with stock theme this time it's much nicer than the old version anyway.
[One (M8) Original Android Development] c5satellite2:
After flashing 2.8.9.0 I have an issue to report. I am unable to browse the SD card from my PC in recovery. The device shows up under my computer, but when I open the external SD card in windows explorer, only about half the folders show up properly, the other half show up with a strange icon(not folder icon) with no names and I am unable to open any of them or read any files. 2.8.7.0 did not exhibit this issue.
[One (M8) Original Android Development] fyarf:
[MENTION=1162986]Captain_Throwback[/MENTION]

In backup, the name for the backup says (Auto Generate). In older versions, when you tapped this to change the name, it showed the auto generated name. In 2.8.9.0 when you tap to change the backup name, it still says (Auto Generate). I haven't tried the auto generated name, but will the backup taken be named (Auto Generate)? Or is this just the new way of doing things?
[One (M8) Original Android Development] linar10:
Was that the possibility of converting these two options. With this setting, it is easy to go wrong and you can remove the internal memory

HtcOneM8 & Tapatalk
[One (M8) Original Android Development] dragontology:
I've actually done this, on a Nexus 7. It's a cruel joke to swap those two, but then again, one should not flash when one needs sleep.

To get a ROM on my phone, I just needed a flash drive and a USB OTG cable. Fortunately, I had both on hand. You can get both for around ten bucks on Amazon, but sitting on a wiped tablet for the three or more days would be... educational.

To be clear, even though it's cruel of the developer to swap them, responsibility ultimately lies with the user. And maybe the developer has a different reason for swapping them.
[One (M8) Original Android Development] Captain_Throwback:
"The developer" wasn't trying to be cruel.

I updated the fstab to reflect what's in stock recovery, in which case the order of some items may have been changed. I didn't look at how that affected the list in the Advanced Wipe page, because every partition is named on the page. If people are wiping their devices without looking, then it certainly isn't my fault if you wipe something you shouldn't.

So I recommend you look (and look again) before you swipe to wipe. It's an extra second that'll save you hours of heartache. Who knows, maybe I changed it to see who's actually paying attention . . . (I didn't, though ;))

P.S. "Internal Storage" always comes after "Data" in that list - it's hardcoded that way, since they're part of the same partition.

P.P.S. FYI There's no need to wipe Dalvik/ART Cache, Cache & Data. Just wiping Cache and Data will automatically wipe Dalvik/ART Cache, since that's where they're stored.

P.P.P.S. Just be happy System isn't all the way at the bottom of the list and you have to scroll to find it - what would you do then? :eek:
[One (M8) Original Android Development] mrrocketdog:
[MENTION=1162986]Captain_Throwback[/MENTION] , recovery log. hope it helps.

https://www.dropbox.com/s/nq8o9nr4e4rez8b/recovery.log?dl=0

[tp_noparse]W2NlbnRlcl1baW1nXWH0dHBzOi8vZGwuZHJvcGJveHVzZXJjb25OZW50LmNvbS91LzlzNjl3OTl3L0ltYWdlcy9TaWduYXR1cmVzL3ZhcmlvdXMvcmRiLmdpZlsvaW1nXVsvY2VudGVyXQ==[/tp_noparse]
[One (M8) Original Android Development] Captain_Throwback:
Assuming your device has a carrier partition, it appears to not be readable by TWRP. I don't think that's a particular problem, unless that error message is causing some issue on your device?
[One (M8) Original Android Development] mrrocketdog:
nope , no issue on device. but this is the only version that i've had any error show up on.

thank you for checking.:good:

[tp_noparse]W2NlbnRlcl1baW1nXWH0dHBzOi8vZGwuZHJvcGJveHVzZXJjb25OZW50LmNvbS91LzlzNjl3OTl3L0ltYWdlcy9TaWduYXR1cmVzL3ZhcmlvdXMvcmRiLmdpZlsvaW1nXVsvY2VudGVyXQ==[/tp_noparse]
[One (M8) Original Android Development] old.splatterhand:
Maybe ;)

Can you remember, we both had this discussion some time ago :D

You have changed it afterwards, what was a good move i think :angel:

(Sometimes a simple step can protect people for themselves, lol)

I'll second this :confused:
[One (M8) Original Android Development] Captain_Throwback:
That was forever ago, and back when I wasn't the official maintainer (yes I remember it).

If the "Auto-Generate" thing is still broken when the official comes out, let me know.
[One (M8) Original Android Development] old.splatterhand:
Forever ago, but good ;)

The guide you have posted to change the lines in recovery.fstab is still applicable?
[One (M8) Original Android Development] Captain_Throwback:
I don't remember posting a guide, but moving around lines in a text file hasn't changed, lol.
[One (M8) Original Android Development] old.splatterhand:
Ok, let's call it a "small guide"... :o

(it is a guide for people who never messed around with recovery, even if it is packed into one sentence)

Thanks :good:
[One (M8) Original Android Development] mrrocketdog:
so .... the 'twrp recovery code' is more like "guidlines" ¿

does Captain_Throwback have a parrot on his shoulder and a "really big hat" ¿ maybe should be Commadore_Throwback.

[tp_noparse]W2NlbnRlcl1baW1nXWH0dHBzOi8vZGwuZHJvcGJveHVzZXJjb25OZW50LmNvbS91LzlzNjl3OTl3L0ltYWdlcy9TaWduYXR1cmVzL3ZhcmlvdXMvcmRiLmdpZlsvaW1nXVsvY2VudGVyXQ==[/tp_noparse]
[One (M8) Original Android Development] dragontology:
Yeah, I allowed for that possibility, but this explanation seems circular. Your prerogative, I'm just saying when people are used to doing a thing for years, sometimes several times a week, and then two options get swapped around... try swapping a few of your keyboard keys (somehow, with software, without switching to Dvorak or Azerty, not sure you can) or just reverse your mouse buttons and see if that doesn't throw you off a bit. But a mistake wipes your hard drive.

With all the developers saying to wipe system, data, cache, and dalvik before flashing their ROM, it makes sense to have them all at the top. To change it at the very least invites question. To look at it the other way, what advantage is gained by elevating Internal Storage one level? Is wiping Internal Storage more common than wiping System?
[One (M8) Original Android Development] Captain_Throwback:
Internal Storage didn't get moved up; it's always been after Data. Like I said, I didn't even look at the list when I made this change. I was just aligning the fstab to stock. And I've never said to wipe Dalvik - in fact I just said it's redundant. And as has already been mentioned, my version has had it this way before.

Again, people really need to pay attention to what they're doing with these devices and really know what it is they're selecting. You'd think that as much as I'm in recovery and flashing stuff that I would've accidentally wiped my internal storage by accident, but I haven't, because I read before I swipe. I recommend everyone else do the same.
[One (M8) Original Android Development] mrrocketdog:
could always use CWM recovery. it hasnt changed in years !!

[tp_noparse]W2NlbnRlcl1baW1nXWH0dHBzOi8vZGwuZHJvcGJveHVzZXJjb25OZW50LmNvbS91LzlzNjl3OTl3L0ltYWdlcy9TaWduYXR1cmVzL3ZhcmlvdXMvcmRiLmdpZlsvaW1nXVsvY2VudGVyXQ==[/tp_noparse]
[One (M8) Original Android Development] _that:
Thanks. Bug identified and fixed locally, here is the fix -> https://gerrit.omnirom.org/#/c/16706/
[One (M8) Original Android Development] mrrocketdog:
ok. just to get a feel. and still a WIP. roflma.

[tp_noparse]W2NlbnRlcl1baW1nXWH0dHBzOi8vZGwuZHJvcGJveHVzZXJjb25OZW50LmNvbS91LzlzNjl3OTl3L0ltYWdlcy9TaWduYXR1cmVzL3ZhcmlvdXMvcmRiLmdpZlsvaW1nXVsvY2VudGVyXQ==[/tp_noparse]
[One (M8) Original Android Development] mrrocketdog:
[MENTION=1162986]Captain_Throwback[/MENTION] , question if i may (& not trying to harp on this , just trying to figure it out) according to this list

https://docs.google.com/spreadsheets/d/1uTfhr5sUFpdYKpHMFOOUnb1T5kOBu411_rcEb_Fz37A/htmlview

(and i am GSM) i do have a carrier partion. searched xda & www why i might have gotten the error but without luck. i know you said might be because i dont have carrier partion. any ideas ?

and again no trouble with phone , flashing or restoring just that error after wiping cache and dalvik. IDK¿

p.s. this came from this xda thread http://xdaforums.com/showthread.php?t=2696826

(if needed).

p.p.s. just searched thru es file explorer and did find carrier partition (mmcblkOp36). go figure.

thank you.

[tp_noparse]W2NlbnRlcl1baW1nXWH0dHBzOi8vZGwuZHJvcGJveHVzZXJjb25OZW50LmNvbS91LzlzNjl3OTl3L0ltYWdlcy9TaWduYXR1cmVzL3ZhcmlvdXMvcmRiLmdpZlsvaW1nXVsvY2VudGVyXQ==[/tp_noparse]
[One (M8) Original Android Development] dragontology:
On mine it's Dalvik, Cache, System, Data, Internal Storage, Micro SDcard, Android Secure, USB-OTG, and SD-Ext. So yeah, Internal's after Data... so System got moved down. At least, from the 2.8.7.0 I'm running, to the screenshot posted above.

Not trying to accuse you of any kind of ill intent. Just saying it would make more sense, and be easier, to just tap the top four, than having to hopscotch around. It's a fair point to look before you tap, which is why I made it in the first place, but there's a reason dangerous [physical] tools have safety guards on them. Because while it's not unreasonable to ask people to be at 100% when they use them, it's not always the case, and while a tool without safety guards can be good, a great one has them for sure.
[One (M8) Original Android Development] _that:
You mean, like "swipe to wipe"? ;)
[One (M8) Original Android Development] -Duir-:
There's literally nothing stopping the people who don't like the order the partitions are displayed from unpacking the recovery.img and editing the fstab to list them to their liking.

Either way, this is how stock is, this is how this will be. No point trying to argue it. You should never be blindly wiping stuff on your phone to begin with.