Can I install it on blueline changing just the kernel ?Yes, Android 10 factory image must already be installed.
I'm not maintaining but will build unofficially until there's an official maintainer
Can I install it on blueline changing just the kernel ?Yes, Android 10 factory image must already be installed.
I'm not maintaining but will build unofficially until there's an official maintainer
Maybe, Platform-tools r29.0.5?After flashing this, flashing TWRP and then rebooting, my phone stays on the AOSiP splash/bootup screen for 10+ minutes. Any ideas what's going on and how to fix? After this happened the first time, I flashed the factory image and then restarted by flashing TWRP and the custom ROM again. So it's now done this to me twice. Below was my chain of installation.
Install platform-tools_r29.0.4-windows to Win7
Bootloader unlock
OEM Unlock
USB Debugging
ADB devices
Allow USB Debugging from computer
reboot into bootloader
fastboot devices (confirmed device showed up)
fastboot boot twrp-3.3.1-3-crosshatch.img (after confirming md5)
From recovery, flash twrp-installer-3.3.1-3-crosshatch.zip (after confirming md5)
Reboot to recovery
wipe system/data/cache
flash AOSiP-9.0-Official-crosshatch-20190722.zip (after confirming md5)
flash twrp-installer-3.3.1-3-crosshatch.zip
reboot system
system stuck on AOSiP splash/bootup/loading screen for 10+ minutes.
Where did I go wrong? Any help is greatly appreciated. Thank you.
After flashing this, flashing TWRP and then rebooting, my phone stays on the AOSiP splash/bootup screen for 10+ minutes. Any ideas what's going on and how to fix? After this happened the first time, I flashed the factory image and then restarted by flashing TWRP and the custom ROM again. So it's now done this to me twice. Below was my chain of installation.
Install platform-tools_r29.0.4-windows to Win7
Bootloader unlock
OEM Unlock
USB Debugging
ADB devices
Allow USB Debugging from computer
reboot into bootloader
fastboot devices (confirmed device showed up)
fastboot boot twrp-3.3.1-3-crosshatch.img (after confirming md5)
From recovery, flash twrp-installer-3.3.1-3-crosshatch.zip (after confirming md5)
Reboot to recovery
wipe system/data/cache
flash AOSiP-9.0-Official-crosshatch-20190722.zip (after confirming md5)
flash twrp-installer-3.3.1-3-crosshatch.zip
reboot system
system stuck on AOSiP splash/bootup/loading screen for 10+ minutes.
Where did I go wrong? Any help is greatly appreciated. Thank you.
I'll give that a shot. Thanks.
What do you mean by "vendor"? Thx.You need to flash the July vendor image, should do the trick :good:
I'll give that a shot. Thanks.
What do you mean by "vendor"? Thx.
Ah, I understand now. I had done that already after my first failed attempt to flash AOSiP, but not with the July factory image, the August one: crosshatch-pq3a.190801.002-factory-15db810d.zip (md5 confirmed). I was able to successfully return to factory. After going back to factory I tried flashing AOSiP with my first post's directions again and got the same result. I was more asking for where I went wrong flashing AOSiP than how to return to the factory image. Sorry for my miscommunication. I do appreciate your help though.Download July factory images from Google, link
You want: 9.0.0 (PQ3A.190705.003, Jul 2019), extract the zip, there will be another zip inside of it, extract it too. This is where you will find the vendor.img. You can flash it with TWRP or fastboot
After further consideration, I don't think this is my problem because I was able to successfully fastboot boot twrp on my phone. I was also able to successfully flash TWRP from TWRP to my phone. AOSiP is where I'm failing. I will try updating to that platform tools instead when I get home, but I really don't think that'd be what's causing my issue. Either way, I appreciate the help.
Ah, I understand now. I had done that already after my first failed attempt to flash AOSiP, but not with the July factory image, the August one: crosshatch-pq3a.190801.002-factory-15db810d.zip (md5 confirmed). I was able to successfully return to factory. After going back to factory I tried flashing AOSiP with my first post's directions again and got the same result. I was more asking for where I went wrong flashing AOSiP than how to return to the factory image. Sorry for my miscommunication. I do appreciate your help though.
After further consideration, I don't think this is my problem because I was able to successfully fastboot boot twrp on my phone. I was also able to successfully flash TWRP from TWRP to my phone. AOSiP is where I'm failing. I will try updating to that platform tools instead when I get home, but I really don't think that'd be what's causing my issue. Either way, I appreciate the help.
EDIT: I'm going to try the July image and the r29.0.5 platform tools, just to rule those two items out. Thanks for the help guys. Will post back as soon as I get a chance to try those solutions tonight.
EDIT 2: One of these worked. I'm guessing it was the July image, but I don't know, could have been either one. I'm not sure why it worked, but I'm happy it did. Thank you to both of you guys for helping.
Thank you for clarifying. I appreciate the help. I'll add that note to my files for future reference.It was the vendor image, the ROM fingerprint and the vendor image need to match, that's why you were stuck at the logo.
After failing to get root, I made some alternative attempts that dug me into a deeper hole.
I took the boot.img out of crosshatch-pq3a.190705.003-factory-e59cf7a4.zip and had Magisk Manager add root to the boot.img then went into bootloader and "fastboot flash boot magisk_patched.img". After that, the system now only booted into bootloader. I then tried to restore the boot.img from crosshatch-pq3a.190705.003-factory-e59cf7a4.zip and still stuck only booting into bootloader. I looked for a boot.img in AOSiP-9.0-Official-crosshatch-20190722.zip but couldn't find one. Do I have to restore to factory and reflash AOSiP to get back to where I was or is there a boot image somewhere that I can restore to avoid doing that? Also, still can't seem to get root even though Magisk Manager is telling me I have it if anybody has any thoughts on that. Thanks.
Thank you for the tip, however it did not work. Below were my command attempts.Although some people claim it's not necessary, In the past when this happened to me ,I fixed it by flashing the image to both slots. Perhaps this will work for you.
Thank you for the tip, however it did not work. Below were my command attempts.
fastboot devices
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
fastboot reboot
when it rebooted, it rebooted back into bootloader. Then I did:
fastboot devices
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
again, when it rebooted, it booted into bootloader. Any other suggestions? Thx.
fastboot boot twrp-3.3.1-3-crosshatch.img (after confirming md5)
Twrp isn't compatible with Android 10I have december on crosshatch rooted / magisk, no issues, but when I try to boot that twrp just as you are indicating here I get:
fastboot boot twrp-3.3.1-3-crosshatch.img
Sending 'boot.img' (65536 KB) OKAY [ 0.525s]
Booting FAILED (remote: 'Error verifying the received boot.img: Invalid Parameter')
fastboot: error: Command failed
md5 works. everything else, including magisk_patched.img boot image works - just cant boot twrp. ..
[B][CENTER]**** Disclaimer: I'm not responsible if you destroy your device. Use at your own risk!!! ****[/CENTER][/B]