wiped stock rom without rooting - Moto E4 Plus Questions & Answers

I installed twrp , and then flashed the phss superuser and the no-verity-opt-encrypt files, but then when I went to check root status it said it wasn't rooted. I then tried to do it all over again by wiping the system but forgot that I am not rooted so I cannot install a custom ROM. Now I'm stuck at the Motorola logo and it won't boot. Please help

What model of phone do you have?

JUSTINMARMER said:
What model of phone do you have?
Click to expand...
Click to collapse
moto e4 plus xt1771, sorry for not mentioning.
I have solved the problem of the rom, I installed the resurrection remix rom : https://forum.xda-developers.com/mo...-resurrection-remix-5-8-5-unnoficial-t3784884
Now I have another issue if you can help me out with, the security options are not working, by that I mean that settings app crashes when I set up any security lock. Also, fingerprint crashes because it needs a security lock with it.
I've rooted the phone using this method: https://forum.xda-developers.com/moto-e4-plus/how-to/moto-e4-plus-guide-to-rooting-mediatek-t3668753

not positive but you flashed nicklaus]Resurrection Remix 5.8.5 unnoficial ,,,nicklaus and your phone is Chipset: MediaTek you need mediaTek rom then

crackpot360 said:
moto e4 plus xt1771, sorry for not mentioning.
I have solved the problem of the rom, I installed the resurrection remix rom : https://forum.xda-developers.com/mo...-resurrection-remix-5-8-5-unnoficial-t3784884
Now I have another issue if you can help me out with, the security options are not working, by that I mean that settings app crashes when I set up any security lock. Also, fingerprint crashes because it needs a security lock with it.
I've rooted the phone using this method: https://forum.xda-developers.com/moto-e4-plus/how-to/moto-e4-plus-guide-to-rooting-mediatek-t3668753
Click to expand...
Click to collapse
this build is based on the january security patch vendor files, just flash stock rom again with any security patch before april, you can apply the security patch of january then unlock bootloader again, flash twrp and flash custom rom and all should work
---------- Post added at 11:39 PM ---------- Previous post was at 11:39 PM ----------
jefffrom said:
not positive but you flashed nicklaus]Resurrection Remix 5.8.5 unnoficial ,,,nicklaus and your phone is Chipset: MediaTek you need mediaTek rom then
Click to expand...
Click to collapse
the nicklaus code name means that is for all mediatek variants
-_-

Related

Read before flashing any Roms based on the official cm trees

If you have flashed any Roms based on sathosh's sir's trees I.e unofficial RR,Aicp,Aokp and cm. Your bootloaders have been updated to mm bootloaders which are based on a leaked build. This bootloader is not officially supported by cm trees, thus if you flash a ROM when you are in this bootloader that is based on official cm trees,then you will get bugs like settings and security FC.
How do I fix this?
The fix is simple. Backup all your stuff.
1) If you have unlocked officially.
Then flash a miui recovery rom. Boot into fastboot, open mi unlock and unlock your bootloader.
2)If you have unlocked unofficially
Then flash via fastboot with patched emmc appsboot file. And type fastboot OEM unlock-go .
Do this if some bugs persist then post on the respective ROMs thread.
You will never walk alone
Keep it brah
Much needed guide. Thanks
Sent from my kenzo using Tapatalk
Thanks Mate
I hope users will read these instructions Before flashing
Sent from my Redmi Note 3 using Tapatalk
Tell me if i am wrong
I am officially unlocked
Flashed unofficial rrremix 8th june build afterwards unlocked bootloader via mi unlock tool
Yesterday made a full wipe flashed unofficial rr remix 20th june built which i guess is based on custom cm sources as after flashing i checked if the bootloader was locked thru adb and it wasnt but i did not have any app fcs or any problems with the rom
Conclusion if i am right with my statement
If u r unlocked officially flash any rom based on miui sources after flashing unlock bootloader again if ur bootloader is locked
Then u can flash any rom with cm13 based kernel without flashing miui rom
Correct me if i am wrong
I have done it and the latest unofficial rr build built on 20th june is based on cm13 sources not on miui sources
My way will work only if u r officially unlocked
ashwaa said:
Tell me if i am wrong
I am officially unlocked
Flashed unofficial rrremix 8th june build afterwards unlocked bootloader via mi unlock tool
Yesterday made a full wipe flashed unofficial rr remix 20th june built which i guess is based on custom cm sources as after flashing i checked if the bootloader was locked thru adb and it wasnt but i did not have any app fcs or any problems with the rom
Conclusion if i am right with my statement
If u r unlocked officially flash any rom based on miui sources after flashing unlock bootloader again if ur bootloader is locked
Then u can flash any rom with cm13 based kernel without flashing miui rom
Correct me if i am wrong
I have done it and the latest unofficial rr build built on 20th june is based on cm13 sources not on miui sources
My way will work only if u r officially unlocked
Click to expand...
Click to collapse
If you have unlocked your bootloader officially , when you install cm13 roms with locked bootloader you can directly unlock them using Mi-unlock tool . But if you have unlocked your bootloader unofficially and after installing a rom if your bootloader is locked then, you would have to flash miui rom via MiFlash tool then unlock the bootloader using that rom(so you will loose your cm13 rom).
Manoj Rocker said:
If you have unlocked your bootloader officially , when you install cm13 roms with locked bootloader you can directly unlock them using Mi-unlock tool . But if you have unlocked your bootloader unofficially and after installing a rom if your bootloader is locked then, you would have to flash miui rom via MiFlash tool then unlock the bootloader using that rom(so you will loose your cm13 rom).
Click to expand...
Click to collapse
Sir i know that
I was only refering to op that if u officislly unlocked and flashed a custom rom with miui resources and want to flash a custom rom with cm13 sources u dont have to flash miui rom again u can only unlock the boot loader on exsisting rom and flash a cm13 sources based custom rom and it will run bugless
:good:
ashwaa said:
Sir i know that
I was only refering to op that if u officislly unlocked and flashed a custom rom with miui resources and want to flash a custom rom with cm13 sources u dont have to flash miui rom again u can only unlock the boot loader on exsisting rom and flash a cm13 sources based custom rom and it will run bugless
Click to expand...
Click to collapse
Even Santhosh's CM can be unlocked via Mi Flash without going back to MIUI ROM.
You people have'nt realized the existence of two bootloaders. Unlocking is diffrent. both bootloaders can be unlocked. But Roms based on official cm trees onlu support the lollipop boot loader and not the bootloader from the leaked build.
simplyme2908 said:
1) If you have unlocked officially.
Then flash a miui recovery rom. Boot into fastboot, open mi unlock and unlock your bootloader.
Click to expand...
Click to collapse
I was on AOSP 5.1, backed up using twrp Alka before flashing Santhosh CM13. Then I wiped and flashed Bliss, wiped and flashed unofficial Resurrection Remix. Can I just flash a Xiaomi.eu ROM through twrp and unlock it through MiUnlock after and that's it?
SkinCoffin said:
I was on AOSP 5.1, backed up using twrp Alka before flashing Santhosh CM13. Then I wiped and flashed Bliss, wiped and flashed unofficial Resurrection Remix. Can I just flash a Xiaomi.eu ROM through twrp and unlock it through MiUnlock after and that's it?
Click to expand...
Click to collapse
Yes , if you had unlocked your bootloader officially in the first place .
Manoj Rocker said:
Yes , if you had unlocked your bootloader officially in the first place .
Click to expand...
Click to collapse
Yes, it's officially unlocked, thanks.
simplyme2908 said:
You people have'nt realized the existence of two bootloaders. Unlocking is diffrent. both bootloaders can be unlocked. But Roms based on official cm trees onlu support the lollipop boot loader and not the bootloader from the leaked build.
Click to expand...
Click to collapse
Man cm based bootloaders need not be unlocked they r originally unlocked only the miui based bootloaders r locked all the latwst roms except i guess by santosh m sir r miui based so u know better only issue is that all latest roms r nightly if u flash updates only do a clean install and when ur rim boots up set up as new device and dont restore frm back up
ashwaa said:
Man cm based bootloaders need not be unlocked they r originally unlocked only the miui based bootloaders r locked all the latwst roms except i guess by santosh m sir r miui based so u know better only issue is that all latest roms r nightly if u flash updates only do a clean install and when ur rim boots up set up as new device and dont restore frm back up
Click to expand...
Click to collapse
Man. Punctuation. Please.
Is the new RR unofficial ROM based on cm source or xiaomi?
OK, so if I am understanding OP correctly, what we need to do is re-unlock our bootloaders and then do a clean install of the rom containing the CM-based bootloader.
No , once you install a ROM for example cm13 by Mr Santosh , then your bootloader will be automatically locked , therefore you need to unlock the bootloader and then install cm based bootloader ROMs for example RR official .
---------- Post added at 05:41 AM ---------- Previous post was at 05:40 AM ----------
filthyrich77 said:
Is the new RR unofficial ROM based on cm source or xiaomi?
Click to expand...
Click to collapse
Cm
Yes. That's what I meant.
If we took a backup using Alka TWRP while our bootloaders were unlocked before flashing a rom based on Santosh's trees, can we just restore that backup and then flash a CM based bootloader ROM?
Currently I am on RR (Unofficial 20th June Build). I unlocked my bootloader officially. Now i am trying to unlock bootloader again with MiUnlocker but it gets stuck at 99% with unknown error. If I want to switch to another rom (based on CM), should I require unlocked bootloader??

(ROM) Flyme6 6.7.5.19 by LR.Team Official Flyme

Flyme6 6.7.5.13 by LR.Team Official Flyme
13.6.2017
http://bbs.lenovomobile.cn/z2pro/t848720/
http://www.flyme.cn/firmwarelist-114.html#16
Which languages ​​are available? Chinese and English?
I didnt try yet, just made a mirror: https://mega.nz/#!DYs3QISL!bqZTRHeiFuqvUqrXu19iNcO2vRc-00wfoV5cH7Bpu9Q
der-Andi said:
Which languages ​​are available? Chinese and English?
Click to expand...
Click to collapse
its multilanguage, there is deutsch, i tried it, but vibration*doesn't work. u-touch not implemented.
Odoslané z ZUK Z2121 pomocou Tapatalku
Which Android Version?
toom11 said:
Which Android Version?
Click to expand...
Click to collapse
6.0
Odoslané z ZUK Z2121 pomocou Tapatalku
Does anyone been able to install gapps in this ROM?
Thanks
any installation guide about this rom ? i downloaded and installed with trwp recovery but after android logo then only black screen and waiting ... what is wrong ? my phone bootloader unlocked ...
KaptanHarlock said:
any installation guide about this rom ? i downloaded and installed with trwp recovery but after android logo then only black screen and waiting ... what is wrong ? my phone bootloader unlocked ...
Click to expand...
Click to collapse
This is completely a guess, but since you didn't mention it... What system did you come from? In general, you should use QFIL (part of the Qualcomm QPST tools) to install an appropriate version of stock ZUI & let it boot once before you load TWRP and flash a custom ROM every time you change versions, to make sure you get the appropriate baseband and other hardware drivers in their special little hidden partitions and other strangeness flushed out before turning a custom ROM loose on your phone. Specifically ZUI 2.3 before installing a Marshmallow (Android 6) ROM and ZUI 2.5 before installing a Nougat (Android 7) ROM.
Did you do that already? If not, give it a shot and see if it fixes your problem.
i was have to this rom ''MK60.1-z2pro-170413-RELEASE'' . i wasnt have to stock rom
---------- Post added at 09:24 PM ---------- Previous post was at 08:59 PM ----------
i need to stock rom everytime while installing custom rom ? for example 6.0 stock rom for install 6 based custom rom or android 7 stock rom for install android 7 custom rom ?
KaptanHarlock said:
i was have to this rom ''MK60.1-z2pro-170413-RELEASE'' . i wasnt have to stock rom
---------- Post added at 09:24 PM ---------- Previous post was at 08:59 PM ----------
i need to stock rom everytime while installing custom rom ? for example 6.0 stock rom for install 6 based custom rom or android 7 stock rom for install android 7 custom rom ?
Click to expand...
Click to collapse
That's probably a good idea. I might just be being overly cautious, but I would recommend using QFIL to blow ZUI 2.3 and boot it once before installing TWRP and an android 6-based custom ROM. Just in case the previous custom ROM did something funny to your /persist partition.
im tried lastest flyme rom from this link http://forum.flymeos.com/thread-28211-1-1.html i got 2 errors .
1. mobile data dont working
2. home button dont awake to phone when screen off . u need to push power button...
KaptanHarlock said:
im tried lastest flyme rom from this link http://forum.flymeos.com/thread-28211-1-1.html i got 2 errors .
1. mobile data dont working
2. home button dont awake to phone when screen off . u need to push power button...
Click to expand...
Click to collapse
try this one https://mega.nz/#!BANhTIZZ!OH8QT5WOv...3w1PlExDfSTzNM its from developer Siyang its based on original zui 2.3, everything is working, u-touch, u-health, if you want more languages, install pico gapps, then install more locale 2, and for multicoloured notification led install Light Flow. very good rom.
original post: https://zukfans.eu/community/threads/flyme-6-7-5-15-by-siyang.6126/
lubikem01 said:
try this one https://mega.nz/#!BANhTIZZ!OH8QT5WOv...3w1PlExDfSTzNM its from developer Siyang its based on original zui 2.3, everything is working, u-touch, u-health, if you want more languages, install pico gapps, then install more locale 2, and for multicoloured notification led install Light Flow. very good rom.
original post: https://zukfans.eu/community/threads/flyme-6-7-5-15-by-siyang.6126/
Click to expand...
Click to collapse
i hope he can update it from lastest flyme rom ...
new version look on the main page
flyme 6 roms still have to mobile data problem...
new version look on the main page

[ROM][YT-X703L][7.1.x] unofficial crDroid 3.x for Lenovo Yoga Tab 3 Plus LTE

Code:
*** Disclaimer
I am not responsible for any damage you made to your device.
You have been warned. ***
Introduction
This is a port of crDroid 3.8.5 for the Lenovo Yoga Tab 3 Plus LTE (LTE only!).
Credits:
@matshias and @DerEineDa for their excellent work on the LineageOS port to the YT-X703F.
@vladimiroltean for his LineageOS port to the YT-X703L. He did all the work.
Please refer to their thread on the LOS port for more information https://forum.xda-developers.com/thinkpad-tablet/development/unofficial-lineageos-14-1-lenovo-yoga-t3561457.
Source crDroid
Download:
Current version on AFH: crDroid 3.8.5 (crDroidAndroid-7.1.2-20180227-YTX703L-v3.8.5.zip)
Previous versions on AFH:
crDroid 3.8.5 (crDroidAndroid-7.1.2-20180120-YTX703L-v3.8.5.zip)
crDroid 3.8.4
crDroid 3.8.3
Before flashing, always have a full functional backup. Just in case!
Installation:
Install TWRP, wipe system + data, flash crDroid, reboot.
Flash gapps after the first reboot.
Changelog:
2017-02-27: Update to crDroid 3.8.5 (Februar 2018 Lineage OS security fixes)
2017-01-20: Update to crDroid 3.8.5 (Januar 2018 Lineage OS security fixes)
2017-12-14: Update to crDroid 3.8.4 (December 2017 Lineage OS security fixes)
2017-11-21: Update to crDroid 3.8.3
2017-10-31: Update to crDroid 3.8.2
Have crDroid on my S6 phone and its great. Was only looking the other day for a decent custom rom for my tab and this week here one is
Only dont think it will work as not lte but 350 F. What do you think ?
cleverdicky said:
Only dont think it will work as not lte but 350 F. What do you think ?
Click to expand...
Click to collapse
Please do not try this on any other hardware than a YT-X703L.
Update to crdroid 3.8.3, November 2017 security patches.
Download: crdroid 3.8.3 for YT-703L
tab 3 plus wifi
but only wifi development is there anymore?
Renval said:
but only wifi development is there anymore?
Click to expand...
Click to collapse
Sorry - i build and test the LTE version only. :laugh:
Hi friends,
amazingly what you are done. After the last update from lenovo (20170824 or earlier) the sound of this tablet is very bad because dolby is shut down.
With you ROM and the thread of matshias, the lenovo LTE version now is fantastic. Extremely fast, super sound.
What I have done:
with minimal adb (see matshias Thread forum.xda-developers.com/thinkpad-tablet/general/beta-twrp-root-disable-encryption-yoga-t3538017) flased this custom ROM
after that flashed dolby atmos and open gapps (arm64, 7.1, nano)
- and voilà it's running very well - better than before!!! DRM Level is L1 so it should work with Amazon and Netflix (but can't test it)
Thank you again to all the involved guys
---------- Post added at 09:39 PM ---------- Previous post was at 09:34 PM ----------
Renval said:
but only wifi development is there anymore?
Click to expand...
Click to collapse
Have you checked this Thread : forum.xda-developers.com/thinkpad-tablet/development/unofficial-lineageos-14-1-lenovo-yoga-t3561457
Hi, are there any known issues with the rom?
I installed LineageOS on my Tab 3 Plus LTE(experimental version) before. Unfortunately the cam (for skype), screen mirroring and the micro in whatsapp didn`t work. Thats why I uninstalled LOS and current I use stock.
Regards!
Both cameras and the microphone work for me. You did grant the apps access?
Yes, I did! But in LineageOS they didn`nt work
But now I jumped in at the deep end
I installed crDroid without waiting for an answer , of course backup before!
And now, wow, it works very fine. I can use all features, many thx to the author!!
Now crDroid and nova launcher, both are as couple, one of the the finest roms!
Thank you!
Thank you. Worked perfect here!
Thanks for the custom rom. Finally, my xbox one controller connects via bluetooth. Sometimes the connection breaks off.
Maybe you can find a solution.
I am grateful to you now.
Best regards
Gesendet von meinem Moto G4 Plus mit Tapatalk
I have rebuild the rom and updated the files in the first post with an updated crDroid 3.8.4. This includes the December 2017 Lineage OS security patches.
Have fun, stay safe!
Hi, Tribble, thx for the update! Befor flashing I first will backup my system. Can I restore the data section after flashing or is it necassary to reorganize?
launcher20 said:
Befor flashing I first will backup my system. Can I restore the data section after flashing or is it necassary to reorganize?
Click to expand...
Click to collapse
I upgraded with a dirty flash - just clear dalvik and cache. No issues...
Hi Tribble, I meaned the data of previous version 3.83, can i restore them with twrp? If not, then only dirty flash and renew? Clear calvik and cache ok!
launcher20 said:
Hi Tribble, I meaned the data of previous version 3.83, can i restore them with twrp? If not, then only dirty flash and renew? Clear calvik and cache ok!
Click to expand...
Click to collapse
Dirty flashing does not clear data, only system.
That said - with a full backup you can always go back if something went wrong.
(Always have a good and tested backup, preferably stored outside your device!)
Hello everybody.
Can anyone check the operation of the USSD function on this ROM?
pakster67 said:
Hello everybody.
Can anyone check the operation of the USSD function on this ROM?
Click to expand...
Click to collapse
USSD codes do not seem to work. I never used one on the tablet, so i did not notice. Needs investigating...
Tribble said:
USSD codes do not seem to work. I never used one on the tablet, so i did not notice. Needs investigating...
Click to expand...
Click to collapse
Thanks for your answer. Already checked it and USSD function work perfect.
Thanks for a grate ROM.

[DISCONTINUED] [XZ][F8331/2] AOSP Android 10 builds

[DISCONTINUED] Builds at sx.ix5.org in the aosp-10 directory.
Changelog here: https://sx.ix5.org/changelog.html
Install guide: Flashing AOSP on Xperia XZ
You still need the "Pie" Software Binaries version 9. Do not use the Android 10/Kernel 4.14 images.
XDA:DevDB Information
Xperia XZ AOSP Android 10 builds, ROM for the Sony Xperia XZ
Contributors
local__hero
Source Code: https://git.ix5.org/felix/local-manifests-ix5/src/branch/ix5-customizations-10
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Latest stock .184 / .192
Based On: AOSP
Version Information
Status: Nightly
Created 2019-10-20
Last Updated 2019-10-20
Reserved
Reserved
Download gapps from this link: https://www.cyanogenmods.org/downloads/pico-opengapps-for-android-10-arm64/
Instructions to install gapps:
1-Flash rom zip and magisk (optional)
2-Boot the device once (yes don't flash gapps on first boot because of a bug with android setup)
3-After you boot the device once go back to the recovery. If you didn't flash magisk in last step your recovery will be overwriten by aosp recovery. If that happens just reflash twrp using fastboot.
4-Flash gapps
5-Boot the device now you will get error like "Android setup has stopped working". Just click more info and disable android setup from settings.
6-Login to your google account by running play store and follow the simple steps.
Android setup bug may get fixed in stable versions of gapps but for now install it like this.
I tried to follow the procedure updating my OmniRom 9.0 but the phone goes into bootloop.
i've also tried everything several times different species and versions, without gapps it works! (intigriter update button missing?)
Thanks a lotʕっ•ᴥ•ʔっ
F8332
Rom for f8332 Sim 2 not works.
I like this rom but i installed 2 times and all the time cpu could be 55-60 degrees and randomly reboot. I cant fix this.
F8332
Gps not working. I can fix this.
Hope the ROM will grow as mature as daily driver!
XperiaXZ F8331, newest stock Oreo (unlockedBL), TaiChi modules like Xedge
ibondd said:
I like this rom but i installed 2 times and all the time cpu could be 55-60 degrees and randomly reboot. I cant fix this.
Click to expand...
Click to collapse
Disable finger print unlocking and try again. Also uninstall any kernel tweak mods.
---------- Post added at 08:33 AM ---------- Previous post was at 08:30 AM ----------
Bekoll1003 said:
Gps not working. I can fix this.
Click to expand...
Click to collapse
Install "Global Optimized GPS File Replacer" from magisk.
I haven't any tweaks or kernel. I have stock oreo and i using aosp kernel when i installed android 10
My fingerprint hardware is doesn't working. How can i disable this?. My stock rom is doesn't see fingerprint sensor but this rom can see
ibondd said:
I haven't any tweaks or kernel. I have stock oreo and i using aosp kernel when i installed android 10
My fingerprint hardware is doesn't working. How can i disable this?. My stock rom is doesn't see fingerprint sensor but this rom can see
Click to expand...
Click to collapse
Maybe your stock firmware is from the U.S? they have it disabled over there
archie_77 said:
Maybe your stock firmware is from the U.S? they have it disabled over there
Click to expand...
Click to collapse
İ have latest oreo CUSTOMİZED TR
Deleted
f8332
I hope there will be dual sim support for f8332 in the future. Thanks. I really like this rom
What about Android 10 TREBLE rom?
xperia xz f8331 Android 10.0.
LukianX said:
What about Android 10 TREBLE rom?
Click to expand...
Click to collapse
İ am writing this article android 10.0 Nightly.
Very very good. Everything is working right now.
Excelent. Thanks to those who contributed.
Fatih--xz said:
İ am writing this article android 10.0 Nightly.
Very very good. Everything is working right now.
Excelent. Thanks to those who contributed.
Click to expand...
Click to collapse
Which ROM is this? Is this quack treble by phhusson?

[DISCONTINUED] Project Treble for Xperia XZ [F8331/2] [Android 10]

[DISCONTINUED] Project Treble for Xperia XZ
Hey everyone,
I've updated the Project Treble builds for Android 10 and system-as-root.
No repartitioning necessary! This method is re-using the oem partition.
What is Project Treble?
Understanding Project Treble and Android updates
Talkin’ Treble: How Android engineers are winning the war on fragmentation
What are GSIs?
Android Source: Generic System Image (GSI)
Downloads:
ROM: Download the latest aosp_f8331_*-TREBLE-NOSYSTEM-NIGHTLY.zip from sx.ix5.org/files/builds/kagura/treble/
TWRP: Download twrp-kagura-oem-to-vendor.img
How to install:
Back up your stuff
Wipe data and caches
Install the zip via TWRP (or unzip and install just the /boot and /vendor images via fastboot)
Install any GSI via "fastboot flash system your-gsi-image.img"
To use Magisk: Flash twrp-kagura-oem-to-vendor.img as recovery. Reboot into recovery and install Magisk like you usually would. If you want to go back to another ROM, you need to re-flash your old TWRP recovery as well. Note: Magisk is untested at the moment, needs tweaked recovery to accept new system-as-root status I guess.
Bugs: See post #2
DO NOT POST HERE FOR FLASHING HELP OR YOU WILL BE REPORTED. Read everything before posting.
If you have questions, ask them in this thread: Xperia XZ Pie ROMs Questions and Answers Thread​
List of GSIs: phhusson's treble Generic System Image
Important: You need an AB, ARM64, system-as-root GSI! This is different from the Pie Project Treble builds!
GSIs based on phhusson's work offer the best compatibility.
Magisk: For Magisk to work, you need to tweak your TWRP installation, since it doesn't know that we have shuffled /vendor to the oem partition. You need to change /oem to /vendor in TWRP's fstab file.
See above for a tweaked TWRP.
If you want to go back to any other AOSP-based ROM that is not a GSI, simply re-flash the regular oem image and install like you usually would.
For developers:
This method is repurposing the oem partition to hold /vendor and odm(blobs). There's 400mb of space on that partition and we are only using ~260mb for blobs, while vendor is only about 20-30mb.
Re-partitioning can be quite dangerous if you do not know what you are doing. This method should be safe for everyone.
Developer guide to building yourself: sx.ix5.org
Tested:
LineageOS 17
Pixel Experience
Camera should work everywhere
Bugs are the same as the regular AOSP builds, plus some more if the GSI is not built well or doesn't have tweaks for Sony devices.
XDA:DevDB Information
Project Treble for Xperia XZ [F8331/2], ROM for the Sony Xperia XZ
Contributors
local__hero
Source Code: https://sx.ix5.org/info/fake-treble-for-xperia-xz/
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Stock .184 or .192
Based On: AOSP
Version Information
Status: Nightly
Created 2020-01-03
Last Updated 2020-07-22
Reserved
Reporting bugs
Important: Read the bug list before posting. Anyone can add bugs to the list, just follow the rules.
DO NOT REPORT ISSUES WITH GSIs! Ask the GSI maintainer to fix them!
I will repeat the rules again here:
Rules:
New bugs must include version where error popped up and which oem version you are using
Only reproducible errors
Should include adb logcat (linked in a pastebin service like https://del.dog)
Must include clear description what is wrong
If it is a visual/SystemUI bug, only report it here
If it is an internal bug(e.g. fingerprint crashes device), report it to the Sony bugtracker as well!
Always try to fix the bug yourself first! Then submit a pull request to Sony
Must search if error has already been reported (bug tracker, this document, dev buglist)
If you've reported the issue somewhere else already and just want to track it here as well, add a link
Before reporting a bug, always make sure to isolate it. That means, wipe everything, install only the ROM without GApps and Magisk and see if the problem still exists. Only then report the bug!
Reserved
local__hero said:
Project Treble for Xperia XZ
Hey everyone,
I've updated the Project Treble builds for Android 10 and system-as-root.
No repartitioning necessary! This method is re-using the oem partition.
What is Project Treble?
Understanding Project Treble and Android updates
Talkin’ Treble: How Android engineers are winning the war on fragmentation
What are GSIs?
Android Source: Generic System Image (GSI)
Downloads:
ROM: Download the latest aosp_f8331_*-TREBLE-NIGHTLY.zip from sx.ix5.org/files/builds/kagura/treble/
TWRP: Download twrp-kagura-oem-to-vendor.img
How to install:
Back up your stuff
Wipe data and caches
Install the zip via TWRP (or unzip and install just the /boot and /vendor images via fastboot)
Install any GSI via "fastboot flash system your-gsi-image.img"
Fix /dsp labels: See DSP file relabeling for SODP
To use Magisk: Flash twrp-kagura-oem-to-vendor.img as recovery. Reboot into recovery and install Magisk like you usually would. If you want to go back to another ROM, you need to re-flash your old TWRP recovery as well. Note: Magisk is untested at the moment, needs tweaked recovery to accept new system-as-root status I guess.
Created 2020-01-03
Last Updated 2020-01-03
Click to expand...
Click to collapse
Do i have to fix dsp label even if my xz still on stock rom?
I was Rom Oreo .192,,, I want to install ROM GSI pixel experience 10 ... do I have to flash OEM v9? or directly flash treble aosp10 then flash gsi rom
sorry I want to know more?
jhon_bayu said:
I was Rom Oreo .192,,, I want to install ROM GSI pixel experience 10 ... do I have to flash OEM v9? or directly flash treble aosp10 then flash gsi rom
sorry I want to know more?
Click to expand...
Click to collapse
As far as i know, you dont have to flash oem to flash project treble rom
Pixel Experience 10 ROM works great on my Xperia xz
It running very smooth and no random reboot
I will try EvolutionX next
Tonsak5343 said:
Pixel Experience 10 ROM works great on my Xperia xz
It running very smooth and no random reboot
I will try EvolutionX next
Click to expand...
Click to collapse
Nice,i might try it soon
Does fingerprint works?
I've tried EvolutionX.
The phone not boot. Stuck on bootscreen.
I'll try Havoc OS next.
---------- Post added at 11:55 AM ---------- Previous post was at 11:54 AM ----------
Alfaiz_sry said:
Nice,i might try it soon
Does fingerprint works?
Click to expand...
Click to collapse
Yes
Tonsak5343 said:
I've tried EvolutionX.
The phone not boot. Stuck on bootscreen.
I'll try Havoc OS next.
---------- Post added at 11:55 AM ---------- Previous post was at 11:54 AM ----------
Yes
Click to expand...
Click to collapse
Wow i thought fingerprint doesn't work.
Test another gsi too bro!
I've tried Havoc OS
Stuck on boot screen.
I'll try Lineage OS next
---------- Post added at 12:45 PM ---------- Previous post was at 12:44 PM ----------
Alfaiz_sry said:
Wow i thought fingerprint doesn't work.
Test another gsi too bro!
Click to expand...
Click to collapse
The fingerprint works on F8332
but I'm not sure about F8331
Tonsak5343 said:
I've tried Havoc OS
Stuck on boot screen.
I'll try Lineage OS next
---------- Post added at 12:45 PM ---------- Previous post was at 12:44 PM ----------
The fingerprint works on F8332
but I'm not sure about F8331
Click to expand...
Click to collapse
Work...i'm use lineage os
I've tried Lineage 17 from phh github (Andy Yan sourceforge) on my F8331:
fastboot flash recovery twrp-kagura-oem-to-vendor.img
cp aosp_f8331_10.0_2019-12-24-TREBLE-NIGHTLY.zip to phone
flash aosp from twrp
fastboot flash system lineage-17.0-20191231-UNOFFICIAL-treble_arm64_bvN.img
And over 24h, I've noticed:
* wifi is getting lost, must reboot
* battery drain during the night, almost no deep sleep
---------- Post added at 03:38 PM ---------- Previous post was at 03:16 PM ----------
Tonsak5343 said:
I've tried Havoc OS
Stuck on boot screen.
I'll try Lineage OS next
---------- Post added at 12:45 PM ---------- Previous post was at 12:44 PM ----------
The fingerprint works on F8332
but I'm not sure about F8331
Click to expand...
Click to collapse
I've tried HavocOS from phh github (ExpressLuke's sourceforge) on my F8331:
fastboot flash recovery twrp-kagura-oem-to-vendor.img
cp aosp_f8331_10.0_2019-12-24-TREBLE-NIGHTLY.zip to phone
flash aosp from twrp
fastboot flash system Havoc-OS-v3.0-20191225-ARM64AB-Unofficial.img
And I can confirm it's stuck in bootloop.
I think Pixel experience 10 is the best treble rom for now
Tonsak5343 said:
I think Pixel experience 10 is the best treble rom for now
Click to expand...
Click to collapse
Any bug in pixel experience?
I want to confirm that Omni ROM10 works
maricn said:
I've tried Lineage 17 from phh github (Andy Yan sourceforge) on my F8331:
fastboot flash recovery twrp-kagura-oem-to-vendor.img
cp aosp_f8331_10.0_2019-12-24-TREBLE-NIGHTLY.zip to phone
flash aosp from twrp
fastboot flash system lineage-17.0-20191231-UNOFFICIAL-treble_arm64_bvN.img
And over 24h, I've noticed:
* wifi is getting lost, must reboot
* battery drain during the night, almost no deep sleep
---------- Post added at 03:38 PM ---------- Previous post was at 03:16 PM ----------
I've tried HavocOS from phh github (ExpressLuke's sourceforge) on my F8331:
fastboot flash recovery twrp-kagura-oem-to-vendor.img
cp aosp_f8331_10.0_2019-12-24-TREBLE-NIGHTLY.zip to phone
flash aosp from twrp
fastboot flash system Havoc-OS-v3.0-20191225-ARM64AB-Unofficial.img
And I can confirm it's stuck in bootloop.
Click to expand...
Click to collapse
Now I've tried AOSP 10.0 v208 from phh github on F8331:
fastboot flash recovery twrp-kagura-oem-to-vendor.img
cp aosp_f8331_10.0_2019-12-24-TREBLE-NIGHTLY.zip to phone
flash aosp from twrp
fastboot flash system system-quack-arm64-ab-vanilla.img
And after 24h I've experienced:
* random reboot (with fingerprint setup)
* random reboot (without fingerprint setup)
* phone getting stuck in reboot loop on low battery
* wifi drop, unable to see any network until phone is restarted
Working great on Pixel experience, but can't run game smoothly. I don't know why almost trebelized rom can't run game smoothly? I tried PUBGM
Sony Xperia XZ sensors issues!
Except fingerprint sensor, rest of sensors are not working "accelerometer, gyro, proximity, barometer, compass,".
First of all , I flashed "aosp_f8331_10.0_2019-12-24-TREBLE-NIGHTLY.zip" after that flashed "system-quack-arm64-ab-gapps.img.xz" on it.
Everything works fine, as I said above "except sensors".
Generic System Image That I tested ;
1. PixelExperience_ARM64AB-10.0-20191208-1826-UNOFFICIAL.img.xz
2. system-quack-arm64-ab-gapps.img.xz
Both gave me same issue.
elmxx said:
Except fingerprint sensor, rest of sensors are not working "accelerometer, gyro, proximity, barometer, compass,".
First of all , I flashed "aosp_f8331_10.0_2019-12-24-TREBLE-NIGHTLY.zip" after that flashed "system-quack-arm64-ab-gapps.img.xz" on it.
Everything works fine, as I said above "except sensors".
Generic System Image That I used ;
1. PixelExperience_ARM64AB-10.0-20191208-1826-UNOFFICIAL.img.xz
2. system-quack-arm64-ab-gapps.img.xz
Both gave me same issue.
Click to expand...
Click to collapse
On some reboots sensors can be disabled try rebooting it should fix the issue. All of my sensors are working fine.
Why flash gapps over pixel experience? Pixel experience already comes with gapps.
---------- Post added at 08:26 AM ---------- Previous post was at 08:24 AM ----------
kaka35 said:
Working great on Pixel experience, but can't run game smoothly. I don't know why almost trebelized rom can't run game smoothly? I tried PUBGM
Click to expand...
Click to collapse
Because performance is not good as stock. You can try setting min cpu and gpu clock to higher frequency to improve it but if you want to game use stock.

Categories

Resources