Recent content by AncientDeveloper

You can either fastboot update without the -w flag or just flash individual partitions manually via fastboot flash <partition goes here>

I wonder which part of AOSP (or LOS) is causing this. According to the logs (without digging deeper), it seems to think the SIM has changed every time it boots. SprintDM seems to only need to verify once upon activation on the stock ROM. It's just a minor annoyance and not a big deal. crDroid...

The keyboard switcher selector icon doesn't show on the status bar even though there are more than 2 keyboards installed/enabled and it's enabled under "Lanugages & input" in Settings. This exact behavior had happened before in a different ROM few months ago, but it was magically fixed in a...

Also forgot to mention it's running latest bootloader, radio, and vendor. Would you happen to know if the baked-in SprintDM is the same one as the Google stock one? Attached & pasted here for your convenience: 11-04 21:49:19.002 1032 1032 W PackageManager: Unknown permission...

I keep getting Configuring your cellular network from SprintDM even though cellular data, voice, and sms are all working fine. Preferred network type is set to Global, and APN is also set correctly. This happens upon every reboot, and it stays on unless canceled manually. Any ideas? My carrier...

Do both Beans Gapps & Open Gapps work or only Beans?

Is 20170831 3.7 the last of N?

If you're certain you flashed the correct modem, then I wouldn't know without more information. I'd recommend checking logcat and see if there are any related errors.

You don't need to install stock boot/system/recovery if you're installing a custom rom. Once you're done with step 3, download & install twrp for your device, wipe the listed on step 5, then download & flash latest RR for your device follow by gapps.

I have no other useful information I can provide you if everything installed without errors; troubleshooting remotely would just be guesses. I would recommend trying a different rom & see if you experience the same issues; if you still do, it could be your hardware that may have issues.

ponyongie try this: 1. Get the latest firmware (if it's ZE550KL, otherwise, search for your device) from Asus (currently WW_21.40.1220.2179) 2. If yours is ZE550KL HD 8939, extract emmc_appsboot_8939.mbn [email protected]@[email protected] [email protected]@[email protected] [email protected]@[email protected]

That's very brave of you. I've been exploring the possibility of using EDL (QDLoader 9008) mode to overwrite the whole eMMC with an already-unlocked image. Pixel is in an unique position to try this as all US versions share the same hardware (except marlin vs sailfish), so there shouldn't be a...

I don't believe the Pixel has dedicated frp & devinfo partitions though, but I can't verify it as I don't have a Pixel. It's been a guessing game for me. The assumption was made based on blocksize = mmc_get_device_blocksize(), and is_allow_unlock is on the last of it. I should also note that...

Yes, in fact, the public aboot.c requires OEM implementation in order for it to work as some functions are merely defined as interfaces where OEM has to implement the actual code. Perhaps I should've been more clear on "assuming the logic is not modified". What I meant was, if the OEM did not...

While I haven't figured out a way to gain the ability to write to the eMMC, it seems that the last byte on the eMMC controls whether the device is unlockable.