Search results

I'm listing some potential solutions I've come across that may help others in this same situation. I'd still like a cleaner solution that can be done without another device. - Use an old phone. Remove all other Google accounts from it except the one you want to use. - Use an emulator. Same...

I have a device with multiple Google accounts ([email protected], [email protected]). They are registered to different countries in Google Play. I need to install Some Amazing App and once installed, do an in-app purchase using the Google Play balance from...

Nice! Worked perfectly for me. Didn't even install TWRP, just booted it using "fastboot boot". Now Magisk Manager shows all of its features.

I'm using WW_16.1220.1908.191_0. When I flash the pre-magisk-patched 191 and reboot, I'm able to enter my password and get into the OS. The screen is mainly black but I'm able to open the notifications and quick launch tiles.. sometimes.. sort of. It locks up pretty quickly and I'm not able to...

Yep. I verified that system_a and system_b just had "lost+found" before the flash/sideload.

As someone who just spent a week trying to get LOS installed and is going back to stock, I can testify that custom ROMs are not ready yet. All of the necessary elements (recovery, ROM, gapps, etc.) have multiple showstopper issues. Add on to that the confusion caused by A/B partitions. I've...

Just an unhelpful bug report: when I install LOS (either through LOS recovery + adb sideload, or using TWRP), I get stuck at the LOS boot animation looping forever. Tried LOS 20190907 and 20190910. I've never found a way of debugging a phone when it's stuck at the boot animation, so there's not...

Try: pip3 install -r requirements.txt instead of: pip install -r requirements.txt

I think the instructions at https://twrp.me/asus/asuszenfone62019.html should say to use Install -> Install Image -> Install Recovery Ramdisk. I keep choosing "Boot" because that's what I've always chosen on other (non a/b) phones. Took me a while to figure out why it wasn't working.

Once you remove the PIN and Pattern you will be able to boot into the system and set up the PIN and Pattern however you'd like. No need to mess with the files directly.

Phone: Oneplus 3T Recovery: TWRP 3.3.0-1 OS: LOS 16.0 Flashed a bad emmc_appsboot.mbn and now my phone loops as soon as it gets to the 1+ logo. Cannot get into recovery. Can get into fastboot. Bootloader has been unlocked for years. After getting the "not allowed" error, I did a "fastboot...

Ok, one last round of tests. This is probably it for me. 5.0.8 -> 9.0.5 -> 5.0.8 in one TWRP session Same session Decryption works Reboot to recovery Decryption works Reboot to system Decryption works Flashing 9.0.5 firmware with 5.0.8 keymaster.mbn Recovery...

There's no problem flashing LOS itself on the 3T. The conditions that cause data loss are: upgrading 5.0.x -> 9.0.x firmware, with an unlocked bootloader, and encrypted userdata. If you avoid that situation you should be fine (but make a backup of course). If you can't avoid that situation then...

"I will have no comment until the investigation is complete." -- A Very Smart Person Previous test: Upgraded firmware 5.0.8 -> 9.0.5 Rebooted to recovery Results: 4K of first 10MiB of userdata was modified I was not expecting userdata to be modified so I wasn't tracking precisely what the...

Ok, results from my continued testing. The news isn't great but at least it's damn interesting. 9.0.5 firmware with LOS 16.0-2019042(8? 9?): Does not produce the same keymaster_blob 5.0.8 firmware with LOS 14.1-20170727: Does not produce the same keymaster_blob In both cases I did a (wipe...

Thanks for the crypto footers. I'd still like to see a clean 5.0.x one, but I'll have one myself soon once I reset my device. My thinking thus far is: 1) There is nothing wrong with the crypto footer post 5.0.x -> 9.0.x, except the keymaster_blob may have been overwritten (see below). 2)...

This is getting stranger. Your keymaster_blob is exactly like mine. A full qcom keymaster blob is: struct qcom_km_key_blob { uint32_t magic_num; uint32_t version_num; uint8_t modulus[KM_KEY_SIZE_MAX]; uint32_t modulus_size; uint8_t public_exponent[KM_KEY_SIZE_MAX]; uint32_t...

Ok, more from my research into the 'Password correct but data is corrupt' error. 1) I verified that CRYPT_DATA_CORRUPT was set in the crypto footer flags. The flags were actually 0x00001008. 0x00000008 is CRYPT_DATA_CORRUPT. 0x00001000 has no meaning here so I don't know why that was set. 2) I...

I spent a few hours tracing through the Android source code that generates the 'Password correct but data is corrupt' error, and I'm more convinced than ever that the data is recoverable. I had thought Android was doing some sophisticated corruption checking. Nope. It tries to mount the...

So like a zillion other people I flashed the 9.0.x firmware and borked my encryption. I have come to terms with having to wipe all of the data. I'm still curious exactly what the firmware did to ruin the encryption though. Android FDE uses a randomly generated master key that is encrypted with...

My encryption is borked after flashing the 9.0.5 firmware on my 3T. My process was: 1) Flashed TWRP 3.3.1-0 using the official TWRP app. 2) Booted into recovery, entered password and decrypted storage. 3) Flashed 9.0.5 firmware (Stable9.0.5 Firmware+Modem_OnePlus 3T.zip) using Install button...

If you mean the ones with the long wires, then yes, I checked those. Actually I checked pretty much everything inside the phone. According to this excellent disassembly video: youtube dot com/watch?v=OPuCmfhzgbg , there are lots of antennas and antenna contacts. So many that he doesn't get to...

I'm having this same issue. Three weeks now, unable to make or receive calls. SMS and data work fine. Wifi works. LTE works. When I switch to 3G or 2G there is no connection and T-Mobile doesn't appear in the list of networks. The SIM card works fine in another phone so it must be an issue...

Fixed! What I did: - I was using TWRP 2.8.4.0. While doing the restore I was getting the error message "E: error sending message to add storage 65537". Doing Mount > Disable MTP after booting into MTP got rid of that error message. - I updated to TWRP 2.8.7.0. After those two changes (and...

Nexus 5 Running CM 12.1 (5.1.1 LMY48B) Did a TWRP backup (all boxes checked) (3.7GB) Did a TWRP wipe Did a TWRP install of CM 12.1 (booted, played around a bit) Did a TWRP install of stock 4.4.2 radio (booted, played around a bit) Did a TWRP wipe Did a TWRP restore (all boxes checked) After...