Dear devs, I have been trying so hard to flash Phusson's Treble GSI image into my Sailfish and I managed to do it without any problem. But, when it boots, it stayed stuck at the android splash screen and couldn't boot into the system. I've tried flashing Magisk, it didn't work. Tried flashing the AVB for Pixel 2 just to try my luck, no luck in that area as well. I'm not very good with the whole thing and I could only run some basic fastboot and adb commands. So far, if I flash a custom ROM using TWRP, it does work. Just for some weird reason, any Treble GSI image just won't boot on my phone.
Help appreciated.
working GSi Roms
just pushing this up. i recently got a cheap pixel 1 and thought tinker around with it. my xperia 10 camera is really not that good....so i think about using a pixel for snapshots in daily life.
just wonder why i cannot find much informations about sailfish treble supported roms. with my sony its quiet easy. but i have also this problem. all GSi roms i flash stuck at bootlogo...not even reboot....just stuck there. seems weird. i would say i know what i do....but i cannot figure out why there isnt a working GSI rom (android 10)
i read also in wiki of GSI-phh that people got some treble rom running.....but that was 8.1 or so.
just curious if there are people out there running a treble rom for on pixel 1?
Opened a ticket to try to get sailfish supported in the Android 10 Phusson Treble GSI images here: https://github.com/phhusson/treble_experimentations/issues/1161
Related
I'm trying to install LOS 16.0 but it just won't work. I've tried using the TWRP 3.3.1-16 Q Unofficial by mauronofrio and it works that I can get into TWRP and can flash the rom and GApps, but then after that process once I try to boot into the OS it is just forever stuck in either fastboot or stuck on the bootloader unlocked warning screen. I did realize that I had to use fastboot flash boot twrp*.img because they disabled fastboot boot twrp*.img in the Android 10 update, but then am I supposed to reflash something on that boot partition now? The whole process is very confusing and the instructions from the LineageOS seem to not work at all. Is there anything I can do right now or is it just not possible to install this until TWRP, or OOS, or something I'm not knowledgeable enough to know about updates?
It's because you are using OOS 10.1 as a base (android 10) and you are trying to install Lineage OS 16 (android 9), so it's quite obvious why it isn't working. Try lineage OS 17 instead.
TheSproker said:
It's because you are using OOS 10.1 as a base (android 10) and you are trying to install Lineage OS 16 (android 9), so it's quite obvious why it isn't working. Try lineage OS 17 instead.
Click to expand...
Click to collapse
Lineage OS 17 won't work either. The developer intentionally used OOS 9 as base since fastboot boot command doesn't work yet on OOS 10. OP needs to downgrade to OOS 9 first, whichever of the two Lineage OS versions they wish to use.
remewer said:
Lineage OS 17 won't work either. The developer intentionally used OOS 9 as base since fastboot boot command doesn't work yet on OOS 10. OP needs to downgrade to OOS 9 first, whichever of the two Lineage OS versions they wish to use.
Click to expand...
Click to collapse
I tried this. I downgraded to 9.0.9 and still the fastboot boot command is not working. Apparently this has something to do with the bootloader image itself not being downgraded?
I give up now, my temp phone I was using for holding backups for chat data just randomly wiped itself on havocOS and I've just lost years of chats and stuff and it's got me really down right now. They did fix the fastboot boot issue with today's 10.3.0 update but still nothing is working from any tutorial to get this thing to work on lineage, it just won't boot to it and twrp keeps having errors during flashing. This used to be so much easier on my older phones and I've installed this OS on about 5 phones now but OnePlus 6 just doesn't seem to work no matter what. I'm just going to go back to OOS and hope LineageOS 17.0 will get these issues ironed out by the time it releases. Severely disappointing and a waste of 3 days now but oh well
In my opinion, this is the easiest way to downgrade everything to OOS 9, including bootloader https://forum.xda-developers.com/oneplus-6/how-to/op6-collection-unbrick-tools-t3914109
After that, just unlock the bootloader again like usual and follow the LOS16/17 page's install instructions and you should be good to go.
I tried to install Havoc 3.5 while i was on 10 Ob2, unlocked bootloader and installed patched twrp, then rom. Got stuck in fastboot mode. **** hell i messed everything, later i found fastboot recovery rom from xda, flashed it, thank god it saved me. For me, msm tool was not getting connected, got an error like sahara xyz something... Then after refering to multiple xda threads came to know that most of the present 10 custom roms are based on oos android 9. Then again i used downgrade package from community, reverted back to ob 25 oos (pie), then as usual installation process. So if you are interested in custom roms, downgrade to pie. And again i wanted to go back to complete stock from havoc but unfortunately msm was not responding and fastboot roms wont support upgradation (im not sure), i went to twrp and installed stable 9.0.9 to both partitions + twrp installer. Then 10 oos stable to both partitions + twrp. Then booted up and installed Ob2 again from system updater, lost twrp on that process, then locked bootloader, so mow completely stock ? lot of work for nothing ? oos is better for me.. infact i got used to that. maybe i should purchase another phone to continue the momentum of getting latest updates. crazy oos influence ?
I have the GM1910 version of the OnePlus 7 Pro
Ok so I had a stock OOS 10.3 on the 7 Pro I just bought used, went home and was super excited to get a custom rom installed. From my previous experience back in the day, I knew to USB Debug, OEM unlock, Advanced Reboot for convenience and followed the Havoc Custom ROm guide that said to:
1. Download the ROM, TWRP Installer, GApps, Magisk.
2. Wipe Data, Dalvik.
3. Flash the ROM, TWRP Installer (Use Unofficial Q compatible version, starting at 3.3.1.575).
4. Reboot to Recovery.
5. Flash the ROM, TWRP Installer again.
6. Reboot to Recovery.
7. Flash GApps (Optional), Magisk (Optiona).
8. Reboot and Enjoy.
Never Wipe System or Vendor partition.
After doing so, I first ran into an issue with Fastboot Mode being indefinitely stuck, but fixed that with a TWRP 3.3.1-75 version I downloaded, and was able to boot TWRP. After that, and following the guide above, I noticed it was stuck on the Havoc boot animation. I waited a good 20 minutes before realizing its likely never going to boot. I rebooted twice after that, waiting 10 more minutes each for a total of about an hour, thinking "Hey maybe it takes time". Nothing. I then tried flashing NikGapps for Android Q compatibility as latest Gapps on the OpenGapps website allows up to Android 9. I realized afterward that it was a n00b mistake so I downloaded and flashed the Beta Android 10 Beta Pico OpenGapps and Magisk Canary that also failed.
After that, I started searching around for finding a way to return to stock Android 9 to start over, thinking Android 9 had more stable support, so I downloaded and fastboot flashed the Android 9.5..11 GM21AA - Direct Download, but while showing the OnePlus stock boot animation, it freezes and then the device turns off entirely.
I'm currently waiting for the 9.5.13 Repack (taken from the Collection of Unbrick Tools thread) to finish downloading to see if I can use MSM tool to restore stock Android 9 and kind of start over. I would prefer to root / custom rom Android 9. I have no clue what I'm doing now, but honestly recall it being so easy back in the day before this A/B partition stuff and I would have considered myself to be not so much a n00b, but at least quite "experienced" but I guess thats completely irrelevant now hey!. Can someone please guide me on how I can fix this and get a custom rom booting? Thank you very much!
Update: I managed to restore to Android 10 using the Decrypted Oxygen OS 10.3 ZIP from the "Collections of brick tools" linked above, then rooted that stock OOS using the standard guide. I got Havoc Android 9 working prior but ran into tons of bugs so I just decided to stick to stock for now.
imatts said:
Update: I managed to restore to Android 10 using the Decrypted Oxygen OS 10.3 ZIP from the "Collections of brick tools" linked above, then rooted that stock OOS using the standard guide. I got Havoc Android 9 working prior but ran into tons of bugs so I just decided to stick to stock for now.
Click to expand...
Click to collapse
Unless there is something specific you need with a custom ROM, I'd stay stock and root.
I have EdXposed installed and can tweak most things.
I really need ad blocking and some basic customization.
I don't need a full ROM to get what I want.
tech_head said:
Unless there is something specific you need with a custom ROM, I'd stay stock and root.
I have EdXposed installed and can tweak most things.
I really need ad blocking and some basic customization.
I don't need a full ROM to get what I want.
Click to expand...
Click to collapse
I would have agreed with you yesterday, but I've used the phone for a few days and cannot stand the insanely rounded corners so I tried finding a work around. So far reducing screen height and getting rid of Oxygen OS's software rounded corners is the way to go but stock OOS doesnt give you the option, I'm hoping a custom rom will. Currently in the midst of flashing RR Android 9
Which boot slot are you trying to flash the rom on and have you tried flashing other roms? I know I've tried flashing havoc a few times and no go. I'm using blissrom right now and it works great until I get the rom I'm building and configuring and have data and messaging working lol
So I'm pretty new on the whole android customization scene and I've been really wanting to install Android Open Source Project on my Android 10 phone for a while. I've found a video detailing how to go about it, but my problem is that there's not a version of TWRP for my specific phone yet (I have a Blackview BL6000 pro). For the purposes of making a recovery and installing AOSP, I'm wondering if there's another good app that could replace TWRP that functionally does the same things (Or if someone has a TWRP version somehow) that lets me install AOSP.
The video in question I was using as a guide was this one:
Any help would be hugely appreciated!
magermerch said:
So I'm pretty new on the whole android customization scene and I've been really wanting to install Android Open Source Project on my Android 10 phone for a while. I've found a video detailing how to go about it, but my problem is that there's not a version of TWRP for my specific phone yet (I have a Blackview BL6000 pro). For the purposes of making a recovery and installing AOSP, I'm wondering if there's another good app that could replace TWRP that functionally does the same things (Or if someone has a TWRP version somehow) that lets me install AOSP.
The video in question I was using as a guide was this one:
Any help would be hugely appreciated!
Click to expand...
Click to collapse
You not need TWRP for flash GSI (Custom ROMs). You need stock firmware of your device from company or you should make that your self about any problem with your actions.
After you can know how to do have GSI in your device with commands fastbootd: Installing GSI with fastbootd
and/or using this software: Treble Toolkit [A and A/B]
Ofcourse if yourr device is A/B so you need flash the GSI.img in the system_a or system_b so need know what slot is able to that.
I have a problem installing Lineage OS. I have installed it with its official method, but at the time of starting its initial configuration it restarts several times until it goes into recovery mode, with the legend of Corrupt Android.
The same thing happens to me with the Pixel Experience which is being developed to be the official ROM soon. The difference is that before restarting and finishing in the same it appears to me that "com.phone.services" It has stopped.
I have done everything by fastboot and platforms tools as indicated by the official methods and their own provided recovery's.
With the STOCK ROM no problem.
Does anyone know what happens?
The recovery images that come from LineageOS site don't seem to work for me. I had to go here to get LOSRecovery.img for it since that's the only possible way any version of LineageOS will function.
Also, from my experience, the unofficial TWRP has issues when installed, but not when booted up directly from bootloader.
PeeJay Bonobo said:
The recovery images that come from LineageOS site don't seem to work for me. I had to go here to get LOSRecovery.img for it since that's the only possible way any version of LineageOS will function.
Also, from my experience, the unofficial TWRP has issues when installed, but not when booted up directly from bootloader.
Click to expand...
Click to collapse
PeeJay Bonobo said:
The recovery images that come from LineageOS site don't seem to work for me. I had to go here to get LOSRecovery.img for it since that's the only possible way any version of LineageOS will function.
Also, from my experience, the unofficial TWRP has issues when installed, but not when booted up directly from bootloader.
Click to expand...
Click to collapse
I understand, but it is something that also happens to me with the Pixel Experience.
I have not used TWRP. Only the official methods by fastboot and platforms tools
hello folks,
Extreme noob here and I have caused myself a problem to prove it. I was trying to get Lineage OS got to flashing the lineage recovery for bramble specifically "fastboot flash vendor_boot vendor_boot.img" and have been stuck in fastboot mode sense.
What I'm pretty sure has happened is that I...didn't read closely enough and was not the proper Android 13.0.0 firmware it required. I was wondering if there was a link anywhere to the stock img that I can replace this with so as to start again and update the firmware? Only thing I've changed so far is different tries at flashing boot_a boot_b and vendor_boot. So I assume I just need an img that works with an older android version in there?
any help would be appreciated.
thank you