Who knows?!?!
I soft bricked mine too the first try.
With that said, I attempted to also flash a custom kernel at the same time.
Surmise to say, flashing the Pix 3 with all the caveats that are associated with it can be challenging.
[ROM][10.x][OFFICIAL] 家 BootleggersROM 5.1 Shishufied [Google Pixel 3 - blueline]
- Thread starter slothdabski
- Start date
I soft bricked mine too the first try.
With that said, I attempted to also flash a custom kernel at the same time.
Surmise to say, flashing the Pix 3 with all the caveats that are associated with it can be challenging.
Also make sure that your in the same building that the rom is on (if your in March patch and rom is still in February patch or vice versa) that could make a difference as well.
hmmmm, I was on the stable build with the latest factory image. Should I try the newest version of the ROM???
You want to be on whatever patch the rom is on that your flashing. Sometimes the patch may not be a huge difference and sometimes it could be major changes. Plus the dev can't really help troubleshoot your issues if your basebands and patches don't match the roms.
Edit: looking at post 3, it don't look like he has updated the rom March image yet, or at least he hasn't updated that post. One or the other.
Last edited:
Yep - no march yet. Sorry guys. I'm stuck at a crossroad, that will take maybe a day or two to overcome. I have an official build ready, that in theory is perfect. Only problem -> vendor thinks it's mismatched. It's not, but theres something in Dirty Unicorns' kernel causing it. Other than that, everything is fine.
Sorry to keep you all waiting!
Same soft brick was a pain in the ass, but you guys should check "tool all in one" really streamlines the process of restoring factory images and flashing twrp
https://forum.xda-developers.com/pixel-3/development/tool-tool-one-driversunlocktwrpfactory-t3877486
In the parent forum of this thread
Once I have taken the post over, I will tweak the instructions so that they are very easy to understand. Let me recap here.
Download the builds from comment #195 for my builds (I'm the new maintainer).
Make sure that the build number matches the monthly security patch (ie. 20190228 is the 28th of February).
Flash the factory image corresponding to the month defined above (so flash February)
In order to flash, follow these steps;
- load TWRP through the bootloader, so
- go to wipe, and wipe all but "internal storage" and "storage" (so wipe Dalvik, System and Data)
- Flash the ROM and TWRP zips. (DO NOT flash custom kernel or Magisk prior to first boot. This causes a mess. Trust me.)
- AFTER you have completed standard setup, and you can access the launcher, then reboot to twrp and do what you like.
Simple as. Only ROM and TWRP should be flashed first time round. Only after the first boot is when you should make modifications like that.
Good luck. I'm ironing out March, so you should have a build soon.
I also encounter the softbrick issue and internal storage unavailability every time i clean flash or update the rom, i have abs no clue whatsoever what might be causing that. I can temporarily transfer files to the device in this weird state when in recovery via the all in one tool and then resolve it all. Really weird, my suspicion is that is has something to do with the dual slot architecture somehow
Is this ROM : BootleggersROM-Pie4blueline.4.0-Stable-Unshishufied-20190306-164613.zip is one with march patch ?
Don't download from the first post. Those builds are broken. Go to page 20 of this thread and get the latest stable build from comment #195
Thanks! I saw that post and all I could see is Feb ROM, waiting for March build
Does this ROM support Substratum theming? Specifically, aospUI? Also the post is inaccurate, ActiveEdge is supported on Pixel 2 as of January build. HavocOS has it.
Substratum theming works on this rom just fine.
Active edge doesn't work on the Pixel 3 builds of this rom, regardless of what other roms have on other devices.
Have there been any new releases then ? Or is this rom dead?
---------- Post added at 05:24 PM ---------- Previous post was at 04:32 PM ----------
Trying to use latest on sourceforge and getting auto reboot to stock recovery "BootleggersROM-Pie4blueline.4.1-Stable-Shishufied-20190331-002240"
---------- Post added at 05:24 PM ---------- Previous post was at 04:32 PM ----------
Trying to use latest on sourceforge and getting auto reboot to stock recovery "BootleggersROM-Pie4blueline.4.1-Stable-Shishufied-20190331-002240"
Last edited by a moderator:
I think its probably that the rom got flashed to a different slot? try doing the whole flash process again to see if it works.
I had bootloop with that build probably because i was on april security patch already and the rom was build on March security till 31/03 build.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone