yashsingh1/xdaforums huggingface dataset:
[One (M9) Original Android Development] miggsr:
I get that error on my M8 when making a backup to internal storage. Idk if I get it now that I ruu'd to mm and haven't rooted it yet
[One (M9) Original Android Development] migascalp:
Backup/restore to/from µSD work fine.

SD-EXT I mistaken AND-SEC causes a reboot during backup

And therefore no ability to backup .android_secure
[One (M9) Original Android Development] Captain_Throwback:
There shouldn't be anything in there anyway for 6.0+. I'll probably just remove the Android Secure option - I don't think it's compatible with Adopted Storage.

Not sure what you're saying about SD-Ext. Is there an error for that? Do you have any log?
[One (M9) Original Android Development] migascalp:
With my reboot problem during the backup I wondered if SD-EXT really corresponded to .android_secure or referred to the 2nd partion in μSD

I remade a test with SD-EXT enabled and screen timeout disabled.

no reboot this time?! But .android_secure content is not saved. There are 2 apps in.

sd-ext.info:

Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F 20 21 22 23 24 25 26 27 28 29 2A 2B 2C 2D 2E 2F 30 31 32 33 34 35 36

00000000 0C 00 62 61 63 6B 75 70 5F 73 69 7A 65 00 02 00 30 00 0C 00 62 61 63 6B 75 70 5F 74 79 70 65 00 02 00 31 00 0B 00 66 69 6C 65 5F 63 6F 75 6E 74 00 02 00 30 00 ..backup_size...0...backup_type...1...file_count...0.

recovery.log

Edit:

I think I understood. SD-EXT=Adopted Storage. correct?
[One (M9) Original Android Development] deledav:
Hi,

I installed TWRP and it works but when I reboot my phone stuck on the white page HTC one. I tried any TWRP and it 's always the same .

Can you help me please?
[One (M9) Original Android Development] miggsr:
That doesn't sound like a TWRP related issue... Did you flash anything else?
[One (M9) Original Android Development] hallstevenson:
Yeap, don't think that can be a TWRP problem. It doesn't run during boot unless you initiate it.
[One (M9) Original Android Development] Captain_Throwback:
No. SD-Ext and Adopted Storage cannot coexist. And unless you physically created a second partition on your SD card, then SD-Ext wouldn't apply. I'm not sure why you're so concerned about it, tbh.
[One (M9) Original Android Development] migascalp:
I do have a 2nd partition ext4 for MultiROM.

Simply, I like to understand
[One (M9) Original Android Development] Captain_Throwback:
Then you should probably visit the IRC channel and ask your questions to the people that actually coded it.
[One (M9) Original Android Development] Roobwz:
anyone got an idea why my twrp file got all messed up after downloading it from the official site?? after putting it on my desktop the .img disappears and then i cant flash it in fastboot. the "file" is a burning disc file... thanks in advance for answers

Skickat från min iPad med Tapatalk
[One (M9) Original Android Development] miggsr:
That sounds like a pc problem. Your pc is reading the .img extension as a disc. Kinda like if you had Nero for burning cds/dvds
[One (M9) Original Android Development] Roobwz:
I think I've found a solution.. I opened the file with notepad and suddenly it's a IMG file :) I guess it's gonna work now. Just rename the file to recovery.img

Skickat från min HTC One M9 via Tapatalk
[One (M9) Original Android Development] miggsr:
Sounds about right.
[One (M9) Original Android Development] jollywhitefoot:
This thread has become extremely amusing. One of my favorite reads on the internet right now.
[One (M9) Original Android Development] sanvich collector:
Hello! I have TWRP 2.8.7.1 and the newest supersu, yet every time I try to flash it TWRP crashes midway through the instillation. I do have my bootloader unlocked, and I have used the "mount" console command. What should I do?
[One (M9) Original Android Development] Captain_Throwback:
Not sure why you're using console commands or that "old" TWRP. See if the newer one does it and if so, read the OP about what you should do in order to receive help.
[One (M9) Original Android Development] miggsr:
You need to post the recovery log for experienced users to be able to provide you some sort of assistance... Have you considered maybe you have a bad download from the su zip
[One (M9) Original Android Development] sanvich collector:
I was following a rooting guide and saw that I needed to use the "mount -t ext4 /dev/block/bootdevice/by-name/system /system" command.... What should I do?
[One (M9) Original Android Development] blocka:
You using Winbloze? Do you have the option to show file extensions in windows explorer?
[One (M9) Original Android Development] deledav:
Hi,

I solved my problem by flashing a ROM.

I had flacher anything before . If was my first installation. So I do not know why I had that problem .
[One (M9) Original Android Development] Adromir:
Mmh I still have the problem with 2.9.0.1 when i try to format my cache Partition in f2fs. Sadly i didnt find a recovery log for that. I guess it's stored on the cache partition?
[One (M9) Original Android Development] Captain_Throwback:
Did you read the OP?
[One (M9) Original Android Development] Adromir:
Okay i havent read carefully enough. But both ways don't work for me sorry, because TWRP doesnt boot anymore, so no chance to copy the logcat and strangley adb is not working on my computer, although fastboot does
[One (M9) Original Android Development] Captain_Throwback:
Tester Needed

Can someone please flash (or boot) this TWRP and provide me with the recovery log? It's very likely things will be completely borked (but possibly not), but I need the log to know for sure. Thanks!
[One (M9) Original Android Development] efrant:
Attached. (I edited out my serial number.)
[One (M9) Original Android Development] Captain_Throwback:
That's good news. I was expecting it to be completely borked, but it seems to be working fine. Surprisingly, I know what I'm doing :confused:.
[One (M9) Original Android Development] BR7fan:
Red

Here u go
[One (M9) Original Android Development] efrant:
I'm not surprised.:good: :D :cool:

Yeah, the few things I played around with (clock, brightness, etc.) seem to be working fine. I obviously didn't try flashing/wiping/etc though.
[One (M9) Original Android Development] weinberk:
So does that mean that remote wipe from google device manager will never work for an encrypted phone either? Mine seems to get stuck prompting for password.

And a related question: TWRP for the M8 was updated to support decryption, so why not for the M9? Aren't they remarkably similar?
[One (M9) Original Android Development] Captain_Throwback:
I don't know the answer to this, but if it uses recovery and requires a password to be entered, then it will not work. TWRP cannot decrypt /data.

They might be physically similar, but from a hardware perspective, they aren't (M8 is arm and M9 is arm64). The most important difference in this case, however, is that I have an M8, but I no longer have an M9. So, I don't have the ability to add this.
[One (M9) Original Android Development] weinberk:
OK, so it works on the m8, but not m9.... how long do you think you'd need an M9 for in order to get this working and would you have any time/interest? I might be able to get a loaner to you and maybe round up some donations.
[One (M9) Original Android Development] Captain_Throwback:
I don't know - guess I'd have to think about this. I suppose I'd be willing to do it, but I'm not sure how long it would take since I have a real job, lol.

EDIT: But this only applies to decryption on CM/AOSP-based ROMs. It's not possible on stock/Sense, no matter how long I have a device.
[One (M9) Original Android Development] weinberk:
Fair enough, though I don't understand what you mean by "real job." What else is there besides phone tinkering :)

AOSP here.

Would you instead consider at least modifying TWRP for the hima / himawl (verizon) to detect those phones and the regardless of if they're encrypted, just completely skip password prompting? No point in prompting if it's not going to work, then maybe remote wipe would work??? I think remote wipe is more important to us than accessing the data in TWRP.

THANK YOU
[One (M9) Original Android Development] Captain_Throwback:
When you said before that yours gets stuck at the password prompt, did you mean that recovery freezes? Are you talking about with one of the versions I just posted? If not, can you confirm that one of the ones I posted doesn't work, and if not, pull a recovery log for me?

I might be able to have someone in this thread debug the issue for me, if someone is willing.
[One (M9) Original Android Development] c3drik 67:
Hello everybody,

I have twrp in read only how can i change this one. I would twrp in read/write thanks for your help.
[One (M9) Original Android Development] Captain_Throwback:
Go to the "Mount" page and uncheck the read-only box.
[One (M9) Original Android Development] Captain_Throwback:
If someone that is encrypted on CM/AOSP and using the default password would like to help me debug the issue with hardware keymaster decryption, I just built a TWRP version to assist with that. Whoever volunteers will need to be good with adb (and be using Linux, preferably - Windows may or may not work).

Otherwise, I can't help without a device in my hands. This will require having multiple adb windows open.
[One (M9) Original Android Development] Captain_Throwback:
I guess my last post scared everyone away, lol.

I might even be willing to trade my M8 for an M9, to help out with this effort. But someone would have to be willing to trade. And of course my M8 is on Sprint, so that makes the group of users it'll work for much smaller.
[One (M9) Original Android Development] blocka:
Hi everyone

I know this is a bit off-topic, but where better to ask the question?

since upgrading to MM, my google (gmail) contacts aren't syncing. I've removed/added google in accounts and sync, wiped the cache via TWRP and still no syncing. Anyone else seen this/fixed this?

Cheers
[One (M9) Original Android Development] Adromir:
Since I got my ADB Working yesterday (sorry for not giving logcats) I am willing to help with the encryption
[One (M9) Original Android Development] Captain_Throwback:
Q&A forum. Definitely not here.
[One (M9) Original Android Development] Captain_Throwback:
Are you currently running an AOSP-based ROM, and encrypted with the default password?
[One (M9) Original Android Development] Adromir:
I have an AOSP-Based Rom (AICP, CM13 based) but not encrypted yet. I was planning on doing though when TWRP worked again. But if I can help making that work, I will do that today. What is the default password though, so I can set it up
[One (M9) Original Android Development] Captain_Throwback:
Just don't choose the "use your password to unlock your device at boot" option or whatever it is, and it'll automatically use the default password.

However don't do it just yet - there's still some local debugging I'm doing to try and resolve all the dependencies for the keystore file to get it working right first.
[One (M9) Original Android Development] Adromir:
Okay, just drop me a note somehow, when you think it's ready
[One (M9) Original Android Development] Rogi1997:
Some issues on twrp-2.9.0.2-hima.img

1. Self shut down while flashing zip file (after screen off)

2. Batery Status switches allways between 66% and the real percentage
[One (M9) Original Android Development] Captain_Throwback:
1. I don't understand what you mean. Did you try pressing the Power button to turn the screen back on?

2. That's already listed in the bugs on the first page, since, forever.

P.S. I didn't ask for a bug report on that version - I just needed a recovery.log, which I got.
[One (M9) Original Android Development] Rogi1997:
1. Yes, I tried, but I had to restart

2. Sorry I have not seen it
[One (M9) Original Android Development] Captain_Throwback:
Did you still have adb access? Did you try pulling a recovery log?
[One (M9) Original Android Development] Captain_Throwback:
Look in the Mount screen and confirm whether system shows up there. If not, mount it manually per the instructions linked in Post 2 and try flashing it again. Just make sure you have a backup of stock system first.

The beta versions are fixing minor issues unrelated to root or OTA. Nothing has changed regarding the situation of how an OTA will or will not apply to the device. You CANNOT apply an OTA to a system that has been modified in ANY WAY.

What has changed is the ability to root after taking the initial, fully stock backup. The new SuperSU BETA will now root the device successfully, even with system being mounted read-only, meaning system no longer has to be mounted manually. That's all that has changed. The first beta is the most important one because it fixed the ability to backup system and added detection for a stock system to determine whether to mount read-write or read-only. The following betas retain that functionality but also add minor "under-the-hood" fixes which probably only I care about.
[One (M9) Original Android Development] DroidShift79:
Thanks mate. That cleared it. Plus, I did everything, right. [emoji2]
[One (M9) Original Android Development] Bikegeek:
Thanks for all the hard work. Unlocked, installed 2860 and SU no problem. Cannot do a backup for some reason. Error to E:/?
[One (M9) Original Android Development] Captain_Throwback:
Are you running the official, or the beta version? Because it sounds like you didn't read post #2.
[One (M9) Original Android Development] Bikegeek:
Seems like the official. Go to 2.8.6.3 to allow the write?

2.8.6.3 did the trick. Thank you for the clarification and direction.
[One (M9) Original Android Development] barleysoda:
Does this include installing TWRP and root? I am running stock but I installed your beta 3 recovery and the new SU beta for root. With other phones like LG G2 no OTA could be taken with any type of modification including root or recovery but I am confused with this thread as well. For instance above you say "system" and to me that means partition not phone.
[One (M9) Original Android Development] Captain_Throwback:
Installing SuperSU modifies the system block. You will not be able to take an OTA while rooted. ANYTHING that modifies the system partition in ANY WAY (this includes even simply mounting it read-write) will prevent an OTA from applying.

Here's some reading material: https://source.android.com/devices/tech/ota/block.html
[One (M9) Original Android Development] iggdawg:
I flashed your beta 2.8.6.3 and the new beta of SuperSU you linked here (BETA-SuperSU-v2.48.zip) and upon booting up I got "system UIDs are inconsistent". Should I start looking at TWRP or SuperSU do you suppose? I changed nothing else.

EDIT - a quick googling indicated "fix permissions" in TWRP would probably fix this. it seems to have gotten rid of the issue. leaving this here in case anyone else has the same problem.
[One (M9) Original Android Development] Slusho:
So if I'm reading the second post correctly, if I flash the beta of TWRP (there are three, so I'm guessing the one with the biggest number), and backup the system, I can root and/or install custom ROMs, and all I'll have to do to accept a future OTA is restore the system backup image. Is this correct?
[One (M9) Original Android Development] jauhien:
You need to successfully accomplish TWRP 2.8.6.3 backup BEFORE any thing else had been done to the phone.. (including even before flashing any other versions of TWRP for HIMA - i.e. absolutely and completely virgin system image..) :)
[One (M9) Original Android Development] dratsablive:
I didn't take a system backup before rooting, so would I be able to flash a stock.img file if one was available?
[One (M9) Original Android Development] Slusho:
Wait so I an flash TWRP 2.8.6.3 and then backup the system and be fine, but if I flash any other version of TWRP I won't ever be able to get an OTA again?
[One (M9) Original Android Development] Captain_Throwback:
No. You can't just restore the backup. You have to fastboot flash the system image.
[One (M9) Original Android Development] Slusho:
So backup from TWRP but restore from adb?
[One (M9) Original Android Development] Captain_Throwback:
I said fastboot, not adb.
[One (M9) Original Android Development] Slusho:
Sorry, didn't realize they were separate programs.
[One (M9) Original Android Development] migascalp:
I confess not to understand.

Restore a backup + recovery stock is not enough?

You could explain the method to return to stock in detail please.
[One (M9) Original Android Development] Captain_Throwback:
The reason you can't just restore the stock system while in TWRP is because the system in TWRP is mounted read-write. As soon as you restore it, it'll be compromised again. So, you have to flash the system image while in fastboot to ensure it keeps its integrity. Then if you reboot into TWRP, system will be mounted read-only again. That'll allow you to take a full system image backup again after taking the OTA.
[One (M9) Original Android Development] migascalp:
thank for your explanations.

'fastboot flash system system.img' was not working on older HTC if I remember correctly.

It now works on the m9? Even with the S-ON?
[One (M9) Original Android Development] Captain_Throwback:
If a signed image (which it will be) and flashed in download mode, yes, it should work fine.
[One (M9) Original Android Development] weinberk:
Sorry, was travelling most of yesterday...

With my VZ M9, running a variant of CM 12.1 (Candy 5), if I encrypt the phone, it works.

But if I go into TWRP, it asks for the password and that fails (you know that).

With Google's Device Manger, if I request a remote wipe, the phone does restart and goes into TWRP and that's good. BUT, and here's the problem, the first thing it shows is the password prompt. Obviously that doesn't work. Hitting cancel, which is the way out, brings up TWRP, but no wipe is done.

I want BOTH the ability to mount encrypted volumes and the ability to remote wipe, but if we can't have both, remote wipe, I believe, is significantly more important. So that's what I mean by hanging up on the password prompt.

I'm running 2.8.7.0 from TWRP.me Should I be trying a different version?
[One (M9) Original Android Development] Captain_Throwback:
Look on the Downloads tab and try one of the more recent versions posted there. And then pull a recovery.log please.
[One (M9) Original Android Development] Rogi1997:
After that I reflashed the rom+gapps.

Is that a problem?

Because I think the log had changed since the problem
[One (M9) Original Android Development] weinberk:
Hey now would you look at that!

Flashing as soon as I can get fastboot working on this PC.

(can't remember if I need the HTC Sync drivers or not)
[One (M9) Original Android Development] Captain_Throwback:
You don't need fastboot. Just flash from within your current TWRP.
[One (M9) Original Android Development] weinberk:
You can flash an .img from TWRP!?!?

EDIT: FOUND IT. Goto flash zip, then lower right click "images" Never knew that - in all the years!
[One (M9) Original Android Development] Captain_Throwback:
Imagine if you actually read the OP? :eek:
[One (M9) Original Android Development] weinberk:
Yeah, yeah. Touche. edit, and to be fair, I did, just not the changelog for versions older than what I was already running.

---------- Post added at 02:18 PM ---------- Previous post was at 01:32 PM ----------

Okay, I have 2.9.0.2 did a clean wipe.

Did a remote erase from Google Dev Manger without encryption. Worked as expected.

Then encrypted. Did another remote wipe, and it's still asking for the password.

I looked in the recovery folder, but I don't have a recovery.log file - could this be a catch 22 because it's encrypted? Suggestions?

How hard would it be for the time being to have TWRP for the m9 simply not prompt for the password until such time as AOSP encryption on this device can be figured out?

Thanks
[One (M9) Original Android Development] Captain_Throwback:
If you just select Micro SD as your storage, you can use the "Copy Log" feature. Or, you can do as stated in the OP and adb pull /tmp/recovery.log.

Relax about removing the password. I already know that's an option, but it won't solve the decryption problem I'm currently trying to fix. If I can't figure it out, I will do that.

However, I need someone to try the version I just uploaded and get me a log from that after trying to decrypt.
[One (M9) Original Android Development] Captain_Throwback:
[MENTION=4804493]Adromir[/MENTION]

I'm ready for you to test if [MENTION=360274]weinberk[/MENTION] isn't able to confirm whether the latest version is working.

Also, if someone else could just boot the last one I posted and upload a log, that would also be helpful. I had to update the kernel so I want to make sure everything still works. I'm worried exfat might not be working.
[One (M9) Original Android Development] liam_davenport:
Here you go bro, If you need anything else just quote or mention me View attachment 3634238
[One (M9) Original Android Development] Captain_Throwback:
Ah, you don't have an exFAT-formatted card, so the log isn't as useful as I would've liked. But at least I know it boots!
[One (M9) Original Android Development] liam_davenport:
Damm :crying: Is their a way to format as exFAT without PC? Don't have Micro-SD Card reader on hand :crying::mad:
[One (M9) Original Android Development] blocka:
Fair enough.

Could I ask an on-topic question.

When restoring backup with TWRP, what the reason behind keeping system as Read Only?

Thanks :)
[One (M9) Original Android Development] donmarkoni:
Here you go, mate.
[One (M9) Original Android Development] Adromir:
Going to test as soon as possible
[One (M9) Original Android Development] Captain_Throwback:
Brilliant.

So I was able to update the f2fs support to the latest version and not taint the kernel so that the texfat module still loads. Fantastic.

Now I just need someone to test encryption . . .
[One (M9) Original Android Development] Adromir:
Encrypting my phone right now

---------- Post added at 11:23 PM ---------- Previous post was at 10:54 PM ----------

Looks like encryption on the software i have is broken :/
[One (M9) Original Android Development] Captain_Throwback:
So you can't even encrypt to test? That sucks. Guess we need [MENTION=360274]weinberk[/MENTION] after all . . . :rolleyes:
[One (M9) Original Android Development] Adromir:
Sadly no, it got stuck in a bootloop when I tried to. And the newest twrp 2.9.1.0 was totally unresponsive to touch. Sadly wasnt able to pull a log it says it doesnt exist. Stupid day. Sorry
[One (M9) Original Android Development] Captain_Throwback:
Was it? That's interesting . . . no one else mentioned that. I thought I fixed that.
[One (M9) Original Android Development] Adromir:
Maybe it was because of the recent trying to encrypt before i rebooted into it. But I couldnt click any option o unlock the screen because it apparently didnt recognise the touch
[One (M9) Original Android Development] Captain_Throwback:
I actually found a spot in the kernel source I missed, so perhaps that's why touch wasn't working for you. I'm rebuilding the kernel and will rebuild the recovery after that and you can test whether it's working. Thanks. If not, then I'm not sure what I can do.
[One (M9) Original Android Development] Captain_Throwback:
Try this one: http://xdaforums.com/devdb/project/dl/?id=16647
[One (M9) Original Android Development] HC4Life:
So after i unlock bootloader, i proceed and flash the latest TWRP recovery and rooted the device with the latest superSU beta version, however everytime i got to recovery and reboot system it keeps saying to install root and the device is already rooted i suppose...:rolleyes:
[One (M9) Original Android Development] Aldo101t:
just select do not install, that's normal.
[One (M9) Original Android Development] Captain_Throwback:
You're not using the TWRP I posted, it seems. That's been updated.
[One (M9) Original Android Development] Captain_Throwback:
[MENTION=4804493]Adromir[/MENTION] - did it work?
[One (M9) Original Android Development] HC4Life:
I'm using the current stable version 2.8.7.0
[One (M9) Original Android Development] Captain_Throwback:
What makes you think the ones I posted aren't stable?