AOSiP 9.0 [Official][Crosshatch/Blueline][OTA]

Search This thread

thex2

Senior Member
Jul 21, 2014
73
7
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.
 
Last edited:

Homeboy76

Senior Member
Aug 24, 2012
3,170
1,730
Google Pixel XL
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.
Maybe, Platform-tools r29.0.5?
 

NepoRood

Recognized Contributor / Retired Forum Moderator
Jan 26, 2016
2,940
3,915
Bugtussle
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.

You need to flash the July vendor image, should do the trick :good:
 
  • Like
Reactions: thex2

NepoRood

Recognized Contributor / Retired Forum Moderator
Jan 26, 2016
2,940
3,915
Bugtussle
I'll give that a shot. Thanks.

What do you mean by "vendor"? Thx.

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
 
  • Like
Reactions: thex2 and nick491

thex2

Senior Member
Jul 21, 2014
73
7
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
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.

Maybe, Platform-tools r29.0.5?
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.
 
Last edited:

thex2

Senior Member
Jul 21, 2014
73
7
I rebooted into TWRP, flashed Magisk-v20.1(20100).zip, rebooted back into AOSiP. Went into Magisk Manager, MM shows MM is up-to-date along with Magisk is up-to-date. However, I cannot verify root with root checker. Any ideas? Thx.
 

NepoRood

Recognized Contributor / Retired Forum Moderator
Jan 26, 2016
2,940
3,915
Bugtussle
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.

It was the vendor image, the ROM fingerprint and the vendor image need to match, that's why you were stuck at the logo.
 
  • Like
Reactions: thex2

thex2

Senior Member
Jul 21, 2014
73
7
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.
 

Eudeferrer

Senior Member
Aug 27, 2012
717
251
Miami
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.

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.
 
  • Like
Reactions: thex2

thex2

Senior Member
Jul 21, 2014
73
7
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.
 

sliding_billy

Senior Member
Apr 23, 2012
1,787
621
North Texas
Google Pixel 3
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.

Maybe do a flash-all of the same factory image as the security version you were on with AOSiP but with the -w removed. That will not completely fix your issue, but it may make that slot bootable and keep user intact. Then, you would probably have to change slots and do the same thing since installing AOSiP again is going to install to the other slot. In reality though, I would probably do a flash-all with -w and then switch slots and do it again.
 
  • Like
Reactions: thex2

mickrussom

Member
Aug 3, 2012
40
5
fastboot boot twrp-3.3.1-3-crosshatch.img (after confirming md5)

I 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. ..
 
I 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. ..
Twrp isn't compatible with Android 10
 
  • Like
Reactions: nick491

Top Liked Posts

  • There are no posts matching your filters.
  • 44
    http%3A%2F%2Fi.imgur.com%2FDr6rSI1.png

    Code:
    [B][CENTER]**** Disclaimer: I'm not responsible if you destroy your device. Use at your own risk!!! ****[/CENTER][/B]

    Android Open Source illusion Project

    About us:

    AOSIP is a quality custom rom based purely on Google AOSP source since 6.0 release. Twisted with the latest features and blended with stability. We strive for perfection and it shows.​

    Team Illusion:

    Josh Fox (xlxfoxxlx)
    Akhil Narang
    Brett Montague
    Sri Harsha
    Harsh Shandilya

    Bug reporting:

    • DO NOT Report bugs if you're running a custom kernel or you installed Xposed
    • Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
    • If it is a random reboot, grab dmesg . (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
    • If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
    • Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.


    Latest Downloads:


    Blueline
    Crosshatch

    Gapps are included.

    FAQ and Install instructions:


    Install instructions:
    getting twrp going is discussed many places so i wont do that here but assuming you have twrp installed
    boot twrp
    wipe system/data/cache
    flash rom
    flash twrp installer
    reboot system

    Current Issues/Information:


    * Squeeze features doesnt work on aosp

    Credit/Thanks:


    Mike Williams(founder and creator of AOSiP)
    Huge props to Josh Chasky, Spaceman860, Alex Cruz and the rest of DU teams work on 3/3xl
    Google
    LineageOS
    AICP
    ABC Rom
    Omni
    ChainFire (SuperSU)
    Beanstown106
    Cory Collins
    Sultanxda
    flar2
    ---------
    Any others i may have forgotten
    All our testers


    XDA:DevDB Information
    AOSiP, ROM for the Google Pixel 3 XL

    Contributors
    xlxfoxxlx
    Source Code: http://www.github.com/aosip

    ROM OS Version: 9.x Pie
    ROM Kernel: Linux 4.x
    ROM Firmware Required: 9.0
    Based On: AOSP

    Version Information
    Status: Stable
    Current Stable Version: 9.0
    Stable Release Date: 2019-01-28

    Created 2019-01-29
    Last Updated 2019-05-11
    30
    Current Features:

    StatusBar:
    Battery settings
    Clock settings
    Custom carrier label
    Configure status bar icons
    Custom Status bar icon
    Net traffic activity meter
    roaming indicator
    old style(oreo) mobile signal indicators
    hide notch(blacks out area of notch but keeps statusbar icons in same place)
    VoLTE icon

    Quick Settings:
    brightness slider customization
    Quick pulldown
    Smart Pulldown
    tile animations
    show/hide information header
    show/hide qs footer

    Notifications:
    Ambient music ticker
    Battery LED custimization
    Heads up tweaks
    Toast icon switch
    Mute notifications while screen on

    Navigation:
    SmartNav
    Custom P pill nav
    Swype navigation gesture
    Pulse

    Hardware Buttons:
    Advanced reboot menu
    Backlight options
    Volume button customization

    Recents:
    Clear all button/location
    Oreo/Pie recents switch
    Recent app icon

    Lockscreen:
    Lockscreen shortcuts
    Charging info
    Media cover art
    Music Visualization
    Ambient Music Visualization
    Fingerprint authentication vibration
    Lock Weather
    Clock widget styles
    Hide lockscreen elements
    Fingerprint vibration
    Quick unlock
    Scramble Layout
    Face unlock

    Gestures:
    Double tap to sleep ( Lockscreen/Status bar)
    Three finger screenshot
    AOSP Gestures
    Statusbar brightness

    Misc:
    Fruity Pebbles
    BlackAF
    Smart Pixels
    Night Light brightness modes
    NoCutoutOverlay
    Link Volume & Notification
    Increase Ringing volume

    A bit of misc things as well flash and see
    18
    New update has been released :)

    Kernel now using clang 8.0.8
    Merge February security patch
    Screenrecorder updates:
    - Don't show tmp file in some apps
    - Add support for 18:9 devices
    Bring back scrolling effect in carrier label
    Add Digital Wellbeing dark/black theme
    Add dark theme for inbuilt file manager
    Materalise the delete icon in wallpaper picker
    Add some priv-app permissions to included apps
    Kill teal colour in print service icon
    Use region based decision making for temperature units for Battery temperature
    Fix crash in visualiser in certain edge cases
    Translation fixes and additions
    Fix backup and restore of system settings
    Fix some logspam by SystemUI
    Improve dark theme in telecomm
    Switch to a new default wallpaper (thanks to @WizPer88 for the sexy wallpaper)
    Fix battery icon being grey at times
    Add dark google feed to launcher
    Fallback to default icons when applied icon pack is uninstalled
    Add dark/black theme to Updater and use accent for actionbar items
    ome SEPolicy fixes
    Expose hardcoded colour in Storage Summary Settings page
    Fix icon tinting in power details page
    Add animation slider to developer options instead of fixed values (0.1x accuracy)
    Fix disappearing home/recents button
    Fix behaviour of lockscreen bounce in an egde case
    Some performance improvements to Window Manager
    Fix memory leak in Input Method Manager
    Fix cases when activities refuse to enter PiP mode
    Some QSTile fixes
    Performance improvements in Resolver Activity
    Some crashes have been addressed
    Fix check for lockscreen in edge gestures
    Fix unlinked ringtone and notification volume panel
    Fix LED Light not showing for some apps like Dialer
    Ensure battery temperature preference is always updated
    Make sure settings shortcut icons follow system accent
    Fix soft-reboot when AlarmManagerService is called
    Fix network traffic indicators not hiding on lost connection
    Optimize background activity of network traffic indicators
    Launcher3 Updates:
    - Add option to allow app names to be 2 lines
    - Add option to lock desktop layout
    - Remove widget and foldername edit buttons when desktop is locked
    - Minor hotseat icon fixes
    - Add swipe-up gesture
    14
    so will be doing weeklies for a release schedule but this last one was skipped as i was trying to get an issue figured and was waiting on feb update so will have that out in the next day or so. until now i see that jan firmware is needed for current build as feb had some changes. also good new... looks like DU team has gotten squeeze to work on aosp roms so that should be added in the near future.
    13
    ok so there was some issues with the latest build have most of it all straightened away working on a few more things and will have a Beta build ill share later on.