Search results

Nope, I've abandoned the project, as I've mentioned elsewhere.

Maybe (from the U11 Life forum) : T-Mobile completely stock Oreo rom & Oreo firmware zip And I'm sure there's a *how to* root guide around there too.

to be honest, I'm in no mood for any of this. BeauBs if you wish to answer them, I'll leave it at your discretion.

Did you guys get S-OFF + LOCKED using sunshine?

Seriously? I really don't understand your problem, what's so difficult of looking in the General or Q&A forum on "How to root your device", and if there is no such thread you can create one. You can even get people's attention by using mentions. I never said anything about doing it by yourself...

I'm not saying you shouldn't post here when you have relevant information regarding the current TWRP version, and feel free to post all over the place if you wish, but may I invite you to read: Device Forum Rules (Please Read before posting) I think the different forums are clearly explained in...

I think you may already have it, but just in case https://github.com/CaptainThrowback/android_kernel_htc_ocn/commits/master HTC disables touch when in recovery mode, Captain_Throwback always renenables it when source is available. If source is not available he unpacks the stock kernel and...

No offence guys, I'm just a casual visitor here, but Isn't this supposed to be a development thread About TWRP in particular So I fail to see the point of all the random questions in here, like where do I get stock recovery X how do I root this device where can I find OTA how do I patch...

Wish you well buddy, it's been a pleasure. Even the endless kicks ;) PS: Can you please fix non-working radio, add some colors to something completely insignificant, add some completely silly tweak because I don't want to google something that exists for the last decade or so. And since I'm...

j ^ 4n, my point was just proven :P

You're starting to sound like Marco, and that's scary ;) ... then again, you could pass by IRC and see some really scary stuff :p:silly: oh and if you do, and encounter any network or communications engineers then you may need: 3REoHshZvf4

Doubt it would matter whether it's static or dynamically linked. In hosd they're probably using a static build because the linker (/system/bin/linker[64]) isn't available. Also qseecomd & co aren't really the problem, TWRP is able to decrypt properly, both the first time and subsequent times. As...

Try these: Though, I'm not sure they will work, stuff in here is *tough* :rolleyes:

If you mean the *no longer decryptable data partition in booted ROM*, then it still eludes me, but seems to get triggered any time twrp tries to decrypt it (doesn't matter whether successful or failed). Though TWRP is able to decrypt it successfully (even when the ROM no longer *wants*), so the...

Thanks, can you please also send me a backup of your boot.img (the exact one from your device, just make a backup in twrp of boot only, and send it over)

can you do a getprop actually 3: 1- during booted ROM 2- on twrp decryption prompt 3- after decryption

goodman_east Just want to reconfirm one thing: When ROM fails to accept PIN or default password, when you reboot to TWRP it is still able to decrypt properly right?

Doubt it, all this is very strange however. The normal U11 is using the same method (same files and services) except it lacks a vendor partition, and the only other device I've seen that is using vold_decrypt + FDE Keymaster 3 and also has a vendor partition is some mediatek device that I don't...

well try restoring extra to it's original _0 one and see if it works.

We could try something, not sure how much difference it will make. 1- Set PIN, make sure it's properly working in ROM 2- Enter TWRP, at the decrypt prompt let's make a backup before decrypting: adb shell dd if=/dev/block/bootdevice/by-name/extra of=/tmp/extra_0.img dd...

Unfortunately I'm out of ideas for the moment :( I'll let you know if anything comes to mind, but all this is very weird.

Can you try the second method (setting the date and time correctly, before trying any decryption).

Thanks for the feedback, a couple more tests please (you'll need to be connected to the PC for the second test): Boot ROM, make sure PIN works Reboot to TWRP Enter a wrong PIN and let decryption fail Reboot ROM, check if PIN still works If it still works Reboot to TWRP While TWRP is waiting...

fastboot boot <img> doesn't work on all devices, so never mind, just flash it as usual. But can you please try the instructions from my previous post https://forum.xda-developers.com/showpost.php?p=74836915&postcount=80

Honestly guys, no logs, no nothing :rolleyes::(:mad: I have no idea why I just did that, because it's an epic waste of time, but since I'm not wasting yours I guess it's ok. 1) Screenshot of a format data on an encrypted device: I:operation_start: 'Format' I:sending message to remove 65539...

^^ Number 3 --> BAD, incorrect process. ^^ Number 7 --> expected, after 30 failed attempts your device is supposed to wipe itself (google security). Let's try again, if you can, please follow the exact procedure mentioned: Normally booting ROM Set a PIN on boot Reboot normally and make sure...

Okay, all this is very confusing, so if I understand correctly: Normally booting ROM Flashed TWRP Entered TWRP, and let it decrypt properly Reboot, and ROM asks for password Nothing else was done right? If yes, can you test one last thing (using same TWRP): Normally booting ROM Set a PIN on...

So both of you have the same problem, possibly every other human being on the planet has it, but I can't say since I'm in no mood to format my data partition at the moment to test something that may or may not be true. I'm even willing to concede to the fact that it may be not working properly...

Here's a new build, for whoever want's to give it a try: twrp-3.2.1-0_TEST1212_ocm.img I cannot say whether something will change or not (error messages in the log, password prompt on boot), and since I have no way to even possibly try to understand what's going without the device, that's the...

Official TWRP 3.2.1-0 is out, you can download it from https://dl.twrp.me That is the most up to date version, includes the restore bugfix, and is the recommended version. Enjoy

Not related to TWRP, unless if you flashed TWRP to your boot partition instead of your recovery partition. Dirty flash your ROM.

It's not the same method, LeeDroid chose to flash the partitions themselves, where as I did not, and still refuse to. As per my first post regarding this subject: "without having to flash anything" <- referring to partition flashing. And as per that same post, it should be *stashed* more...

TWRP 3.2.0-1 (unofficial) has been uploaded to the Downloads Tab Should fix your restore issue. Thanks to jason (not sure what your xda nick is) for uploading a patch. It works for me :) The build is by the Captain_Throwback in case anyone is wondering. Though he may have decided to retire...

Here is the stock recovery extracted from the RUU 1.03.1405.1 RUU U11+_stock_recovery_from_2Q4DIMG_OCEAN_M_DTWL_O80_SENSE90GP_HTCCN_CHS_2_1.03.1405.zip I've been looking at the ruu to see if I could find anything obvious, but with the exception of the different / additional property/selinux...

There's really no point in quoting my entire post, long posts shouldn't be quoted, or at least add a hide tag. Here knock yourself out: U11_Flash_DualSIM_2.31.400.6_RADIO_straight_into_system_BETA_0.1c.zip Still think it should be done more properly.

My apologies for asking for logs (again :confused:) Next time just link me the previous ones, seems I must have missed them. Won't need them your previous statement is enough for me. Thanks for the bug report though.

You won't have Wi-FI (needs OREO firmware), you can get mobile data my entering your APN. -> Check here for a way to get WIFI working on nougat fw, ... As mentioned in said post, not the best of ideas, it's a POC (proof of concept), that it can work, there are any number of ways to deal with...

Screenshot is not the same as a recovery.log, so while it's *sitting* there, connect it to your PC and get the logs: adb pull /tmp/recovery.log adb pull /tmp/adb.log and finally reboot to recovery: adb reboot recovery or just reboot: adb reboot I'm actually restoring a system_image backup as...

I'm not a "big" developer (maybe a little fat, but that is beyond the scope of the thread). However, I was just trying to make a point, yours is actually a valid question / post. Considering what was done a few days ago, considering it was confirmed earlier today by someone other. I consider...

Sorry everyone is too busy saying: Wow Thanks Amazing Great Waiting for the next version Woop woop Etc. To actually actually answer you. And you'll probably only get a "you did not read" post, and although mostly correct also perhaps incomplete. Sent from my HTC 10 using XDA Labs

wow excellent. <- yet another useless post, pages and pages of them :good::good:

can you guys get me a listing from the booted ROM (you'll need su access) adb shell su ls -laZ /dev/__properties__

I'm using that device tree as well, just need to add an empty vendor folder in recovery/root so that the vendor partition can get mounted properly. (oh and the android-8.0 branch, not master) It builds fine, but I did (still do) have to make some modifications to vold_decrypt due to the error...

Cray/mad yes :cyclops: genius not so sure about that :o mjCRUvX2D0E Confucius says: If jit compiler broken, fix it :) (well he didn't really say that, but sounds nice) It wasn't me, I promise :p But yeah Oreo (and I mean android-8.0 in general) is just a nightmare, so many weird bugs, it's...

No need to quote my entire post, it's a bit on the long side so just eating up space ;) Yes, you are probably correct about the radio flash, but the point of my exercise was to do it without flashing anything. IMHO, the best course of action is to have your entire firmware updated to 2.x.xxx.x...

No it's not the same build as previously, it's a new clean build, which *allows* for the error in libc: libc: Access denied finding property "persist.vendor.dpm.feature" not to be interpreted as part of the return codes (the info that decryption is waiting for). Having that *text* being seen as...

So it decrypted fine? I still need a recovery.log (and if you can a dmesg) from both you, and goodman_east (and/or whoever is testing for him). As mentioned earlier, we've moved on from debug builds, but the output is unexpected and should not be there. I'd rather have both (errors and proper...

It's a new build, with plenty of repo changes, so no worries if it doesn't work right (actually last time I said that, it did :p), but it's all still a bit messy especially for Oreo + OEM + Omni ++ on a device we cannot test on. Thanks for testing.