Related
Today I flashed Pixel Experience GSI on my whyred after much trouble so here is a guide to make things clear.
if you are coming from MIUI you have to format data from twrp. this is a must to disable encryption.
after you are done formatting data. just do factory reset from twrp and then go to advanced wipe and then do the regular dalvik, cache, system, data and then swipe to wipe.
now the thing is whyred officially supports treble but the implementation is shoddy according to XDA folks. so if you flash GSI over miui's vendor there will be many bugs. like brightness slider not working and many things. so they(all credit goes to them) created a vendor zip which makes things really good. there are no bugs and it also supports volte. here is the download link .
https://www.androidfilehost.com/?w=files&flid=273660
now flash this zip file in twrp.
after that download the GSI of your choice from here.
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
remember to download arm64 A only system image.
here is pixel experience GSI which I prefer:
https://download.pixelexperience.org/treble_gsi/
now extract the zip and you will get a single .IMG file which is your system image. now go to twrp and then go to install then go to select install image downward. (don't flash directly, it's an .IMG file) then select the extracted .IMG file and then choose system and then flash.
then reboot system. that's it. you should boot fine.
download latest official twrp from here: https://dl.twrp.me/whyred
if you want root you will have to flash magisk beta 16.6 which works better on GSI. download here.
https://github.com/topjohnwu/Magisk/releases/download/v16.6/Magisk-v16.6.zip
to use Google camera you will have to enable camera2api. arnova's gcam doesn't work on this build. you will have to use BSG's gcam. here is the link. enable nexus style and active portrait mode from settings.
https://www.celsoazevedo.com/files/android/google-camera/f/MGC_5.2.022.apk
few tips: if your device is not booting and going to fastboot, flash magisk. it will definitely boot up.
if your device shows decryption failed, just format data from twrp. it will delete all user data btw.
no need to flash lazyflasher.
there are no uncertified device pop up from Google. so no need to worry.
playstore shows uncertified btw and magisk shows CTS false.
all the links that I have linked here, the credit goes to the creators. I am a normal user of XDA. thanks to them.
happy flashing and all hail the XDA lords.
How is Pixel experience gsi though?....faced any bugs till now?
it's good but there where few bugs. anyway pixel experience rom specifically for whyred has been released. you can flash that. it's great and bug free. download it here. it's not GSI though. normal ROM.
https://download.pixelexperience.org/whyred/
mr._.nobody said:
How is Pixel experience gsi though?....faced any bugs till now?
Click to expand...
Click to collapse
mr._.nobody said:
How is Pixel experience gsi though?....faced any bugs till now?
Click to expand...
Click to collapse
I was on the June build, I had issues with bluetooth audio (didn't work) and USB connection to computer (did not work). I think the USB issue was due to Magisk but I never did figure out the bluetooth issue.
No issues with the whyred version of Pixel Experience.
I also faced the same issue. But I see July build of GSI is up so those bugs might be fixed. anyway the PE ROM for whyred is excellent.
btw GSI will help us when P will release next month.
goofball2k said:
I was on the June build, I had issues with bluetooth audio (didn't work) and USB connection to computer (did not work). I think the USB issue was due to Magisk but I never did figure out the bluetooth issue.
No issues with the whyred version of Pixel Experience.
Click to expand...
Click to collapse
mearjunsha said:
I also faced the same issue. But I see July build of GSI is up so those bugs might be fixed. anyway the PE ROM for whyred is excellent.
btw GSI will help us when P will release next month.
Click to expand...
Click to collapse
So should I flash the ROM or the gsi?....are there any differences?
you should flash the ROM as it's specifically for whyred. its flashing instruction is different than GSI. but easy. just wipe and then flash the ROM. and reboot. that's it.
you may have to format data to disable encryption.
here is the forum discussion: https://forum.xda-developers.com/redmi-note-5-pro/development/rom-pixel-experience-t3816099
mr._.nobody said:
So should I flash the ROM or the gsi?....are there any differences?
Click to expand...
Click to collapse
Thanks mate for your experience, no detailed information in PE thread about wipes to do, before or after, can help with it? May be also with magisk release to install and best gcam to use?
remove all security like fingerprint, pattern etc.
go to twrp
go to wipe
do factory reset
go to advanced wipe
select dalvik, cache, system and data and then wipe
go to install
flash the pixel experience rom
reboot to system
that's it
if you get a prompt to enter password to start android then you will have to go back to twrp and go to wipe and format data and type yes. it will delete all your files btw. so backup everything. then reboot it will boot up fine.
after you have done booting and set up, go back to twrp and flash magisk v16. reboot to system. all done.
I have already given details of gcam in my OP. Kindly check that. The same works great on this ROM.
ask me if you face any problem. happy to help ?
trazalca said:
Thanks mate for your experience, no detailed information in PE thread about wipes to do, before or after, can help with it? May be also with magisk release to install and best gcam to use?
Click to expand...
Click to collapse
You are the man!!! 10 hours remaining for unlock bootloader, i'm ready and now, with your help, more confident... Thanks a lot!!
I understand your excitement but do check your build whether you are on Anti rollback. if you are on 9.5.19 you should absolutely not proceed right now.
read about it on XDA.
trazalca said:
You are the man!!! 10 hours remaining for unlock bootloader, i'm ready and now, with your help, more confident... Thanks a lot!!
Click to expand...
Click to collapse
I'm on global 9.5.6... never used phone and upgraded, i think that i can do it, i'm wrong?
you can go ahead. happy flashing! ?
trazalca said:
I'm on global 9.5.6... never used phone and upgraded, i think that i can do it, i'm wrong?
Click to expand...
Click to collapse
[dupe sorry]
You should by all means read about antirollback to be sure, but my understanding is that the antirollback refers to the firmware, not the rom. MIUI roms all include different firmware, so you can't rollback a MIUI rom (unless it's been modded to be firmwareless). But as far as I know, no custom roms include firmware, so you should be fine even if your firmware is ARB triggered if all you're doing is installing custom roms.
Hi, someone flashed latest Pie Phh GSI? I tried with PE CAF, AOSIP, and Mokee vendors but doesn't boot, always stuck at the Mi logo, even I flashed the permissiver patch without luck.
Is GSI better than respective Rom (say Havoc GSI as compared to Havoc OS rom)?
ShadowFax said:
Is GSI better than respective Rom (say Havoc GSI as compared to Havoc OS rom)?
Click to expand...
Click to collapse
Nope.
lets make this very clear:
I HAVE NOT DEVELOPED THIS, IT WAS LINKED IN ANOTHER FORUM BY ANOTHER MEMBER WHO ALSO DID NOT DEVELOP IT
this is actually developed by a member over at the Chinese website '7to' http://www.7to.cn, so its a recovery based on TWRP 3.2.1 but seems to have its own UI and feature set.
WORKING
Code:
[COLOR="Black"][LIST]
[*]Boots to TWRP!
[*]Can flash images to system (MUST BE ON SD CARD!!!!)
[*]ADB
[*]Mount system R/W
[/LIST][/COLOR]
NOT WORKING
Code:
[COLOR="Black"][LIST]
[*]Decryption
[*]Data backup
[*]Flash from internal storage (since it cant be decrypted)
[/LIST][/COLOR]
I am not responsible if you brick your device, flash with caution and ONLY on an 8.1 GSI where your current TWRP doesn't work.
This does not do anything to capacitive keys, if they work before flashing they will work after flashing
INSTALLATION
'fastboot flash recovery_ramdisk recovery.img
DOWNLOAD
https://drive.google.com/file/d/1RgerdkXY-B-8XV5buloeCyKYrA2B3Bvf/view?usp=sharing
Credit to whoever the creator of this is!
it boots up with TWRP, but flashing Gapps was failure.
UPDATE: I used Open Gapps, better try Ground Zero GZR Gapps...
TASON42 said:
it boots up with TWRP, but flashing Gapps was failure.
Click to expand...
Click to collapse
GZR apps 180313 works good.
GZR-GaPPs-arm64REv4-Zero-8.1-20180628 worked. thx.
UPDATE: HuRUpdater_0.4, Magisk 16.7 worked.
Flashed a kernel, magisk and xposed with this. Seems to be working great.
olishadyx said:
Flashed a kernel, magisk and xposed with this. Seems to be working great.
Click to expand...
Click to collapse
I haven't flashed anything with this yet, but at least it can do the basic stuff. Also, what kernel did you flash, I know there's the proto8 kernel (or whatever it's called) but I'm not too keen on it.
ambitiousButRubbish said:
I haven't flashed anything with this yet, but at least it can do the basic stuff. Also, what kernel did you flash, I know there's the proto8 kernel (or whatever it's called) but I'm not too keen on it.
Click to expand...
Click to collapse
Proto8 is what I installed. Haven't made my mind up on it yet. Battery drain is definitely worse so far but apparently it takes a few cycles to adapt.
So the A/B structure of the Pixel (I came from Nexus 5X) took some getting used to, not having a recovery partition was a new wrinkle, and the jimmy jammy required to unlock the bootloader (I bought a Verizon Pixel apparently) was a neat trick. So I got the Pixel bootloader unlocked, booted with TWRP, installed Lineage, rebooted to bootloader, fastboot booted to TWRP, installed TWRP and OpenGapps.. Excellent! Setup the phone, booted to TWRP and installed Magisk. eveything works! great phone!
Then, a week later there is an update to Lineage. So I copy the ZIP file to my phone, flash it and OpenGapps and reboot. Boom. all screwed up. no problem, I'll restore from the backup I made in TWRP. nope. bootloop. then I read that you restore BOOT,SYSTEM IMAGE,VENDOR IMAGE, and DATA. NOT all the partitions as I had naively thought. Turns out I boned the backup and didn't backup the DATA partition so the Restore works but all my setup stuff is gone. My fault.
I went through the entire process again. Phone is working fine. All is well. Heres the question: What is the appropriate method to upgrade Lineage when a new one is released? So that I end up with new lineage, updated OpenGapps, TWRP working, and Magisk keeping me rooted? I can just keep trying to figure it out but I dont want to keep starting at zero with my phone.
Thanks in advance. I searched diligently on the forums but it looks like not that many Pixel users use Lineage.
Cheers
d.
130 views and no one knows how you upgrade LineageOS? is anyone using Lineage on their Pixel? Really?
I just discovered Lineage OS for my VZW Pixel. What build did you use? If I can figure out how to install, I'll try playing with updating, too.
Where did you end up downloading LineageOS from? I'd be curious to try it as well.
SkinnyT said:
Where did you end up downloading LineageOS from? I'd be curious to try it as well.
Click to expand...
Click to collapse
Probably here: https://download.lineageos.org/sailfish
post-mortem said:
Probably here: https://download.lineageos.org/sailfish
Click to expand...
Click to collapse
I probably should have looked there. I didn't even realize they supported the pixel. It's been a while since I've messed with things.
I've been using LineageOS and it's great. Super stable compared to most of the other ROMs I've tested. These are the steps I take when upgrading to a newer build.
- reboot to recovery (TWRP)
- install lineage-15.1-xxx-nightly-sailfish-signed.zip (no wipe or anything beforehand)
- install twrp-pixel-installer-sailfish-xxx.zip
- return to TWRP main menu and select reboot, then Recovery (whenever it prompts me to install TWRP app I just hit "Do Not Install")
- once back in TWRP, install MindTheGapps-8.1.0-arm64-xxx.zip
- reboot to system (again, I always decline the TWRP app installation)
- once you've booted to system, reboot to recovery one last time.
- install Magisk-v17.x.zip
- reboot to system and you should be good to go.
I always have a recent backup from TitaniumBackup stored on my computer so if anything goes wrong I can do a clean install and reload all my apps.
awesome. I'll try that. I'm using 15.1 10/23/2018 version and I have backed up so I'll do it. one question, do you reboot between installing lineage zip and twrp installer?
SkinnyT said:
Where did you end up downloading LineageOS from? I'd be curious to try it as well.
Click to expand...
Click to collapse
yeah I got it from lineage website. have you managed to update using Crawdads method?
dcarrco said:
awesome. I'll try that. I'm using 15.1 10/23/2018 version and I have backed up so I'll do it. one question, do you reboot between installing lineage zip and twrp installer?
Click to expand...
Click to collapse
No. Install TWRP immediately after installing the Lineage zip, before rebooting. Otherwise when you reboot to recovery it'll be the Lineage recovery and then you'll need a computer to send any other files you want to flash.
Also, they just started releasing builds every 24 hours. You might want to check the changelog every few days to see if there is anything new that's worthwhile. Some days there may actually not be any changes at all.
@CapriciousCrawdad
well I tried it today, just as you have it written in your post (other than what I assume was a typo where you say "return to lineage" in step 4 where I think you meant TWRP) and what it looks like is my working installation is on partition A and after installing as you specified it tried to boot on B and couldnt get past the Google screen. so I finally got it to reboot into TWRP and switched back to A and got my phone going again with my old October revision. the only difference is that I use OpenGApps and not MindTheApps. so tomorrow I'll try it with those.
CapriciousCrawdad said:
No. Install TWRP immediately after installing the Lineage zip, before rebooting. Otherwise when you reboot to recovery it'll be the Lineage recovery and then you'll need a computer to send any other files you want to flash.
Also, they just started releasing builds every 24 hours. You might want to check the changelog every few days to see if there is anything new that's worthwhile. Some days there may actually not be any changes at all.
Click to expand...
Click to collapse
dcarrco said:
@CapriciousCrawdad
well I tried it today, just as you have it written in your post (other than what I assume was a typo where you say "return to lineage" in step 4 where I think you meant TWRP) and what it looks like is my working installation is on partition A and after installing as you specified it tried to boot on B and couldnt get past the Google screen. so I finally got it to reboot into TWRP and switched back to A and got my phone going again with my old October revision. the only difference is that I use OpenGApps and not MindTheApps. so tomorrow I'll try it with those.
Click to expand...
Click to collapse
Whoops. Indeed, that was a typo in step 4. I edited the post.
Not sure about your problem though... I do remember specifically reading that opengapps can cause some issues but I can't find the source of that info and I don't think that it had anything to do with updating the system. I'm on mobile now but I might have time to check it out tomorrow.
If you haven't already, I suggest you check out the official LineageOS thread for the Pixel and Pixel XL. There might be some helpful info there.
CapriciousCrawdad said:
Whoops. Indeed, that was a typo in step 4. I edited the post.
Not sure about your problem though... I do remember specifically reading that opengapps can cause some issues but I can't find the source of that info and I don't think that it had anything to do with updating the system. I'm on mobile now but I might have time to check it out tomorrow.
If you haven't already, I suggest you check out the official LineageOS thread for the Pixel and Pixel XL. There might be some helpful info there.
Click to expand...
Click to collapse
yes thats where i ended up. tried to update and got bootlooped, my backup didnt work for some reason (do i backup EFS partition also?) so i started again with the instructions in that post. i used the Gapps package from @razorloves and it all worked. setup my phone again and now it upgrades fine using the Lineage updater although i have to reinstall TWRP and reroot (using SuperSU from Lineage) when that happens. razorloves hasnt updated his google FI compatible Gapps package yet so i will see how/if i can update those when the times come. on a side note, im getting really good at setting up my pixel. got to look at the upside.
thanks for your suggestions.
Hi all,
I'm presenting here my ROM for S10e (whose main thread is https://forum.xda-developers.com/pr...vice-development/aosp-9-0-phh-treble-t3831915 ).
It is generic, but it doesn't mean anything bad!
Pretty much every works, and this is my daily driver (Exynos variant).
What works:
- Camera
- Wifi
- 2G/3G/4G, including signal level
- Phone calls
- Fingerprint sensor
- Encryption
- Proximity sensor
What doesn't work
- VoLTE
- stock OneUI camera app
- MTP
You can install some modded Google Camera on it for acceptable Camera quality.
Download links:
- With included gapps
- Without included gapps
How to flash:
- Flash back latest stock ROM
- Extract the img.xz into .img
- Flash it to system partition using Heimdall: https://glassechidna.com.au/heimdall/
- Flash this to vbmeta partition https://dl.google.com/developers/android/qt/images/gsi/vbmeta.img (also using Heimdall)
- Boot once. The device will reboot into recovery, that's okay! Just do a factory reset and boot to system again.
- If it didn't reboot into recovery on its own, that's not normal (perhas you have magisk installed?), but still reboot into recovery and do a factory reset.
- Enjoy!
Recommended after installing:
- Default Launcher is AOSP's. It sucks. You should really install another Launcher. I recommend and use Lawnchair
- Pretty much no Google app is preinstalled, only Play Store and Chrome. You'll probably want to install Google, Google Assistant apps, Gmail, ...
free post for me and myself
Support for G9700?
Could system.img possibly be flashed through recovery? And you could've made it a flashable zip, we have a pretty ok recovery when you flash multidisabler
DeHuMaNiZeD said:
Could system.img possibly be flashed through recovery?
Click to expand...
Click to collapse
Yes
And you could've made it a flashable zip, we have a pretty ok recovery when you flash multidisabler
Click to expand...
Click to collapse
TBH I recommend not to flash any disabler, they bring more issues than they fix.
Android security is already not ideal, disabling encryption sounds like a very bad idea
(And disabling dm-verity is totally useless, because when flashing a GSI it already is)
NisseGurra said:
Support for G9700?
Click to expand...
Click to collapse
Yes G9700 is supported, though bear in mind that since it's not the same device, you don't really have the same guarantees. I'll help you through your issues either way.
Ok, tested on G9700, latest stock rom installed (android 9).
TWRP with multidisabler installed, format data, reboot recovery. Install V120 gsi, reboot.
Boots nicely.
Findings: no autobrightness, slider ok tho. Wifi/BT/NFC ok. No MTP (as stated)
Dual sim ok, voice calls ok, data ok. 3.5 output ok
Edit: Best way to root?, addonsu-16.0-arm64-signed.zip?
im gonna try this right away
i have one simple question before trying does magisk work with this and can i just use a magisk pachted system
---------- Post added at 07:32 AM ---------- Previous post was at 07:16 AM ----------
To my knowledge s10e is A-only and you linked A/B. What's up with that?
Edit:// It seems it is not, I have no idea why treble testing app from app store does not detect, that it is A/B
mikk150 said:
To my knowledge s10e is A-only and you linked A/B. What's up with that?
Edit:// It seems it is not, I have no idea why treble testing app from app store does not detect, that it is A/B
Click to expand...
Click to collapse
In the true sense, it is A-only, it doesn't have seamless update.
The difference between A-only and A/B was that A/B included the init, while A-only didn't.
But since Pie, A-only also includes init, like A/B. I didn't update the naming convention (because it just gets even messier).
Hackintosh5 developed Treble Info ( https://play.google.com/store/apps/details?id=tk.hack5.treblecheck&hl=en_US ) to make things clearer.
Do you have PHH for Android 10 for this device?
vlubosh said:
Do you have PHH for Android 10 for this device?
Click to expand...
Click to collapse
It is still unstable, that's why I haven't shown it in this forum yet.
Do these steps apply to any devices? Or only specific models? I have an Elephone Soldier, and I notice different website have different procedures. Not sure which one is right. Thanks.
"How to flash:
- Flash back latest stock ROM
- Extract the img.xz into .img
- Flash it to system partition using Heimdall: https://glassechidna.com.au/heimdall/
- Flash this to vbmeta partition https://dl.google.com/developers/and...gsi/vbmeta.img (also using Heimdall)
- Boot once. The device will reboot into recovery, that's okay! Just do a factory reset and boot to system again.
- If it didn't reboot into recovery on its own, that's not normal (perhas you have magisk installed?), but still reboot into recovery and do a factory reset."
I just installed AOSP 9.0 v119 for my Elephone Soldier. I can confirm the system boots up, but there is no sound. (ie. ring tone, media, notification) None of these sound work.
One question guys. If i root my s10e and flash custom rom, and then if i want to back to full 100% stock rom, o just need to flash it with odin and everything will be same like before? All apps will work like samsung health and pay? Thanks
BratoMo225 said:
One question guys. If i root my s10e and flash custom rom, and then if i want to back to full 100% stock rom, o just need to flash it with odin and everything will be same like before? All apps will work like samsung health and pay? Thanks
Click to expand...
Click to collapse
No as I have heard. The knox fuse is a physical fuse which can never be reset so these apps will not work.
Project Treble For Xperia X Compact
Based on Sony Open Devices
I am not responsible for bricked devices, dead SD cards,.
Big thanks to Sjll member and his tuto to go treble
Suitable for F5321, A-ONLY GSI ROM
Required files:
[SODP Kernel version]
All necessary files
[OEM-File]
Download Link
[SYSTEM-File]
Tested with some system gsi files, these work properly :
Pixel experience
/e/
POSP
ArrowOS
[SYSTEM-File WITH FixZygote installed via twrp]
Android Q developer preview
Find all GSI system image here and here
How to go Treble ?
First: Flash recovery
Code:
fastboot flash recovery < Path of recovery.img >
Second: Flash boot image
Code:
fastboot flash boot < Path of boot.img >
Third: Flash vendor file
Code:
fastboot flash cache < Path of vendor.img >
Fourth: flash SW_binaries provided by Sony.
You can download it from Sony official website.
Code:
fastboot flash oem < Path of OEM.img >
Fifth: Flash a GSI compatible System image (arm64 A-ONLY) and boot !
Code:
fastboot flash system < Path of GSI-System.img >
Look here first for questions resolving Xperia X thread
Source Codes
Sjll
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Version Information
Status: Testing
Created 2020-05-09
Last Updated 2020-05-23
Hello mate. It's interesting to see different options come up when we started to think that development for XC come to an end. Thanks for this valuable effort. I want to ask a few things.
1- What is your opinion about dreaded problems with 4.9 kernel like random reboots and some reported Wi-Fi issues (although I don't remember I ever had this) etc.
2- recovery is independent of this setup right? I mean can I use twrp as recovery?
3- I suppose we'll be stuck with this boot.img unless personally build another one with synced sources right?
4-One of your cautions was about dead sd card? Is there a predicted risk or was it a general warning?
Again thanks a lot for this. I think I'll give it a try tomorrow may be.
PS: I also would like to know what to look for compatible GSIs. (I tried Phhs' and some other Android 10 GSIs with zygote and permissiver patches but they didn't past the sony logo. Stuck at sony logo or bootloop)
Update: Question 2 answered. No problem with twrp. Erfan's generic 10 gsi booted with zygote and permisiver patches. But stuck at setup screen.
maluus said:
Hello mate. It's interesting to see different options come up when we started to think that development for XC come to an end. Thanks for this valuable effort. I want to ask a few things.
1- What is your opinion about dreaded problems with 4.9 kernel like random reboots and some reported Wi-Fi issues (although I don't remember I ever had this) etc.
2- recovery is independent of this setup right? I mean can I use twrp as recovery?
3- I suppose we'll be stuck with this boot.img unless personally build another one with synced sources right?
4-One of your cautions was about dead sd card? Is there a predicted risk or was it a general warning?
Again thanks a lot for this. I think I'll give it a try tomorrow may be.
PS: I also would like to know what to look for compatible GSIs. (I tried Phhs' and some other Android 10 GSIs with zygote and permissiver patches but they didn't past the sony logo. Stuck at sony logo or bootloop)
Update: Question 2 answered. No problem with twrp. Erfan's generic 10 gsi booted with zygote and permisiver patches. But stuck at setup screen.
Click to expand...
Click to collapse
1 - I don't know about these problems, I was with 3.x kernel before but you can rebuild the kernel of your choice (it doesn't take too much time) by changing the .dtsi file corresponding to our device
2 - Yes but do not wipe the cache, as the vendor image is in it
3 - Yes, but it doesn't take too much time to build it, share if you do
4 - Just a general warning, not experienced
maluus said:
Hello mate. It's interesting to see different options come up when we started to think that development for XC come to an end. Thanks for this valuable effort. I want to ask a few things.
1- What is your opinion about dreaded problems with 4.9 kernel like random reboots and some reported Wi-Fi issues (although I don't remember I ever had this) etc.
2- recovery is independent of this setup right? I mean can I use twrp as recovery?
3- I suppose we'll be stuck with this boot.img unless personally build another one with synced sources right?
4-One of your cautions was about dead sd card? Is there a predicted risk or was it a general warning?
Again thanks a lot for this. I think I'll give it a try tomorrow may be.
PS: I also would like to know what to look for compatible GSIs. (I tried Phhs' and some other Android 10 GSIs with zygote and permissiver patches but they didn't past the sony logo. Stuck at sony logo or bootloop)
Update: Question 2 answered. No problem with twrp. Erfan's generic 10 gsi booted with zygote and permisiver patches. But stuck at setup screen.
Click to expand...
Click to collapse
1 - I don't know about these problems, I was with 3.x kernel before but you can rebuild the kernel of your choice (it doesn't take too much time) by changing the .dtsi file corresponding to our device
2 - Yes but do not wipe the cache, as the vendor image is in it
3 - Yes, but it doesn't take too much time to build it, share if you do
4 - Just a general warning, not experienced
Normally I set the selinux to permissive so no need to apply the permissiver patch
PS : sometimes it goes into bootloop but if you reboot it starts like a charm (test that with POSP 10)
PS2 : Mobile network does not work with Q roms, if you success to make it work please share
PS3 : POSP Pie works fine
Tell me if I'm thinking of installing Project Treble.
1.Flash all sections through the fastboot?
2.Ask for recovery what is in the link on the github?
3.Ask for a boot link on github?
4.Select vendor.img in the cache section?
5.What to ask for?
6.Select a suitable GSI image and boot again?
If somewhere I am wrong correct me. I'm sorry I'm new to this.
bioshp said:
Tell me if I'm thinking of installing Project Treble.
1.Flash all sections through the fastboot?
2.Ask for recovery what is in the link on the github?
3.Ask for a boot link on github?
4.Select vendor.img in the cache section?
5.What to ask for?
6.Select a suitable GSI image and boot again?
If somewhere I am wrong correct me. I'm sorry I'm new to this.
Click to expand...
Click to collapse
You can get twrp as recovery but do not wipe cache, as vendor img is flashed in it
Good news that /e/ is working correctly, I was about to try to build a e variant on Chippa's build.
I do have one question. Really new to trebble.
If we wanna root it, we apply usual procedure*? flash the root zip(magisk) in recovery
This is amazing!! Breathing new life in to my XC. Thank you for sharing. Just flashed /e/ and it's working really well so far. Although I see that selinux is not enforced, anyone know why?
can't boot any FW excluding /e/, but /e/ don't satisfy me at all.
bootloops miui
bootloops PE
bootloops native xperia gsi
anybody know's why?
all of needed img's are flashed: boot, vendor, oem. Only recovery left TWRP
zetchonok said:
can't boot any FW excluding /e/, but /e/ don't satisfy me at all.
bootloops miui
bootloops PE
bootloops native xperia gsi
anybody know's why?
all of needed img's are flashed: boot, vendor, oem. Only recovery left TWRP
Click to expand...
Click to collapse
Xperia UI GSI also does not start for me. What could be?
zetchonok said:
can't boot any FW excluding /e/, but /e/ don't satisfy me at all.
bootloops miui
bootloops PE
bootloops native xperia gsi
anybody know's why?
all of needed img's are flashed: boot, vendor, oem. Only recovery left TWRP
Click to expand...
Click to collapse
I tried a lot of them to both android 9 and 10 only /e/ boots and works as 9. For the 10 erfans boots but it includes gapps and that stucks at setup. You can leave it as it s but didn't thoroughly tested it.
zetchonok said:
can't boot any FW excluding /e/, but /e/ don't satisfy me at all.
bootloops miui
bootloops PE
bootloops native xperia gsi
anybody know's why?
all of needed img's are flashed: boot, vendor, oem. Only recovery left TWRP
Click to expand...
Click to collapse
Try to flash userdata also
bioshp said:
Xperia UI GSI also does not start for me. What could be?
Click to expand...
Click to collapse
Q or Pie ROM ?
maluus said:
I tried a lot of them to both android 9 and 10 only /e/ boots and works as 9. For the 10 erfans boots but it includes gapps and that stucks at setup. You can leave it as it s but didn't thoroughly tested it.
Click to expand...
Click to collapse
POSP boots as much of the Pie Gsi, 10 are more capricious (POSP 10 boots for example, but sim is not detected)
betacrypt said:
This is amazing!! Breathing new life in to my XC. Thank you for sharing. Just flashed /e/ and it's working really well so far. Although I see that selinux is not enforced, anyone know why?
Click to expand...
Click to collapse
To avoid SELinux policy errors and fail to boot
nervousapp said:
POSP boots as much of the Pie Gsi, 10 are more capricious (POSP 10 boots for example, but sim is not detected)
Click to expand...
Click to collapse
Then probably erfans 10 is better. Because sim Wi-Fi camera etc works. Just didn't tested thoroughly. Only downside setup doesn't complete. Personally I don't use Google services so no problem for me but setup notification persists like it tries to complete setup but doesn't actually progress.
I flashed /e/ and it's pretty stable and smooth but my device is overheating when charging and even when it's idle and the display is off. I'm getting severe battery drain from it.
EDIT: Wiping all the partitions and flashing from scratch seems to have done the trick.
I've been using Arrow OS and it's pretty stable and smooth so far. Comes with GApps built-in and Jan 2020 security patch:
https://sourceforge.net/projects/arrow-os/files/arrow-9.x/GSI/27_Jan_2020/
maluus said:
Then probably erfans 10 is better. Because sim Wi-Fi camera etc works. Just didn't tested thoroughly. Only downside setup doesn't complete. Personally I don't use Google services so no problem for me but setup notification persists like it tries to complete setup but doesn't actually progress.
Click to expand...
Click to collapse
Hello! You can describe in detail how you installed it, how many have not tried to get further Sony does not work.
mister-13x said:
Hello! You can describe in detail how you installed it, how many have not tried to get further Sony does not work.
Click to expand...
Click to collapse
I didn't anything extraordinary follow the steps in the first post. (Since android version would change I formatted data) use erfanoabdis' unofficial Q gsi which you can find a link at phhusson' gsi images link list. (You can also find the link to phussons list in the first post)