Database Users

Sony.Z2.D6503.PreRooted.Customized.AU.1281-9715.23.5.A.1.291 (Root+Recovery)(LB/UB)

Info :
Greetings and Welcome. Here's the latest firmware update for Sony Z2(D6503) Build23.5.A.1.291_R4D with (Recovery + Root)
Enjoy!
How To Flash :
Method 1 Clean Flash :
1. Download Prerooted Rom + Bootloop Fix and place them on ur device storage,
2. Reboot to Recovery,
3. Do A Full Wipe Except the storage partition where u put Prerooted Rom + Bootloop Fix,
4. Flash Prerooted Rom and then Bootloop Fix
5. Reboot.
Method 2 Dirty Flash Over Previous Build Of Android MM :
1. Download Prerooted Rom + Bootloop Fix and place them on ur device storage,
2. Reboot to Recovery,
3. Flash Prerooted Rom and then Bootloop Fix,
4. Wipe Cache And Dalvik/Art
5. Reboot.
6. After Finishing booting process wait a few mins,
7. Now go to app drawer and check if supersu is there or not, If not then simply download it from google play store and install it and open it and select SU Binary install normal & Click Reboot,
8. Enjoy!
Stuff Used to Create This Pre-rooted Room :
D6503_Customized AU_1281-9715_23.5.A.1.291_R4D
PRFCreator_v1.3
UPDATE-SuperSU-v2.76-SYSTEMMODE
RecRootV4_combined
My Dell Laptop,
A Keyboard + Mouse,
My Experiences With This Build Of Android MM :
Now We can transfer apps to "EXTSDCARD" using "Transfer data to SD card"
STAMINA mode is back
Multi Tasking Is better than Previous Build Of Course XD
Significantly faster & smoother than previous build (23.5.A.0.575)
Screen Recording Error still exist
Anything Else? :good:
Download Links :
Rom : Click On ME
Bootloop Fix : Click On ME
Screenshots :
http://imgur.com/a/i7icA
Instead of Typing Thanks, You can simply press on it :good:, Try not to spam this thread, If u have any Question regarding my upload Ask here.

First Comment
Keep Up Bro (Y)

Thank you. ?

Thanks!

I'll try to build the same file but for Customized FR (my country) !

Why bootloop fix from 570 build need to flashed too ?
Sent from my D6503 using Tapatalk

itsnie said:
Why bootloop fix from 570 build need to flashed too ?
Sent from my D6503 using Tapatalk
Click to expand...
Click to collapse
Because that's a life saver for Z2 with Prerooted rom. That's the only bootloop fix exist here on xda for now. Can you try flashing without it at see if it boots? And report back here! Unless u wanna waste some times on re-flashing LP rom and rooting it again to get back on a rooted mm rom

Will previous D6502 patches work?

RICdefeat & byeselinux
Have you used byeselinux & RICdefeat in the firm compilation??
Or only the bootloopfix?
Thank you

supercfc said:
Will previous D6502 patches work?
Click to expand...
Click to collapse
Can't say since I don't have a D6502 Model. Try and let me know if it works

LunaFree said:
Have you used byeselinux & RICdefeat in the firm compilation??
Or only the bootloopfix?
Thank you
Click to expand...
Click to collapse
"RecRootV4_combined" Include all of those stuff as well as recovery

@op
Will dummy_flashable.zip works as well making the ZIP? im on .575 with root and recovery. i have already downloaded the ftf before seeing this post

Thank you so much!!!!

So I finally made the same thing for the french firmware !
https://www.wetransfer.com/downloads/9d69b9f8a30da16970abc3f5655fa01720160804144653/d99f41

Dilesh Perera said:
@op
Will dummy_flashable.zip works as well making the ZIP? im on .575 with root and recovery. i have already downloaded the ftf before seeing this post
Click to expand...
Click to collapse
As I already said "RecRootV4_combined" Includes Root + Recovery. So u don't need anything else. Except Bootloop Fix

rakeshbro said:
"RecRootV4_combined" Include all of those stuff as well as recovery
Click to expand...
Click to collapse
I've do my compilation with 23.5.A.1.291 firmware using the ITALIAN customized and SUPERSU with PRF creator.
I've install busybox from appstore and DUAL recovery with the install.bat from pc and then in RECOVERY MODE i´ve flashed byeselinux+RICdefeat without bootloopfix, and works too!!
Thank you Rakeshbro!! :good::good:

LunaFree said:
I've do my compilation with 23.5.A.1.291 firmware using the ITALIAN customized and SUPERSU with PRF creator.
I've install busybox from appstore and DUAL recovery with the install.bat from pc and then in RECOVERY MODE i´ve flashed byeselinux+RICdefeat without bootloopfix, and works too!!
Thank you Rakeshbro!! :good::good:
Click to expand...
Click to collapse
Yeah I saw some feedback on "23.5.A.0.575" build as well that some ppl didn't flashed bootloop fix and they got it boot.
But for me I'd to flash bootloop fix to get into os. I remember Last time when I was on MM build "23.5.A.0.570_R4D" I've like 350+ apps installed on my z2 and after a few weeks later Build "23.5.A.0.575" came out. And guess what I've flashed it without the bootloops fix and that's it, I got stucked on lockscreen and whenever I unlock my device it just reboot again & again, And I can't even boot to recovery. With a broken heart I've to flash LP rom again and root it and then flash the latest MM build. I just did't want to take that risk again this time, since I've now more than 360+ apps installed on my Z2. So It's upto All of u guys. U want to flash the old bootloop fix or not. Try and let us know Good Luck!

Yeah you need bootloop fix. The same thing happened to me but I just pressed volume button during the bootloop, I entered TWRP, connected to USB, copied bootloop fix and flashed it without reinstalling everything

rakeshbro said:
Yeah I saw some feedback on "23.5.A.0.575" build as well that some ppl didn't flashed bootloop fix and they got it boot.
But for me I'd to flash bootloop fix to get into os. I remember Last time when I was on MM build "23.5.A.0.570_R4D" I've like 350+ apps installed on my z2 and after a few weeks later Build "23.5.A.0.575" came out. And guess what I've flashed it without the bootloops fix and that's it, I got stucked on lockscreen and whenever I unlock my device it just reboot again & again, And I can't even boot to recovery. With a broken heart I've to flash LP rom again and root it and then flash the latest MM build. I just did't want to take that risk again this time, since I've now more than 360+ apps installed on my Z2. So It's upto All of u guys. U want to flash the old bootloop fix or not. Try and let us know Good Luck!
Click to expand...
Click to collapse
I think we have do the same, but i dont use the bootloop fix...
I will flash recroot v4 next time without bootloop fix and i tell you. Thank you!!

Thanks for your work
flashing without a probleme

Cant open play store or connect to any google account

After installing MedroM I got this problem and couldn't connect to google account and every google app would crash if I tried to log in, so I flashed b161 and I still have this problem, even after numerous factory resets, has this ever happened to anyone ?

Yes, it is happening to other guys around here...
In fact is happening to all who flash B160/B161 firmware...
Is not possible to flash any firmware previously to B160/B161.
Workaround is to unlock bootloader, flash twrp, root it, reflash oeminfo for your device,
and after that you can flash another firmware again.

gtdaniel said:
Yes, it is happening to other guys around here...
In fact is happening to all who flash B160/B161 firmware...
Is not possible to flash any firmware previously to B160/B161.
Workaround is to unlock bootloader, flash twrp, root it, reflash oeminfo for your device,
and after that you can flash another firmware again.
Click to expand...
Click to collapse
i'm in the same situation, i tried to do what you've said, but twrp says that the installation failed. how can I have play store working again? please help, this situation is driving me crazy!
i'm on c900 b161.

I had the same issue. I did a clean flash of the new 161 update and that made my device a C900. I have a Eurpoean model (T-Mobile Germany).
After 2 days of trying different stuff, here's what gave me a functional device with TWRP and Root back:
-Back up any data you want to keep, obviously.
-Reflash stock ROM (put UPDATE.APP on your dload/ folder on the separate SD card, then boot into the update function by turning the phone off and then holding Vol+, Vol-, Power. Just wait until it's finished.
-Unlock Bootloader again
-Download the Toolkit: http://forum.xda-developers.com/huawei-p9lite/development/europe-vns-l31-toolkit-bootloader-t3432873
-Flash TWRP through the toolkit
-Boot TWRP and root
-In Android, enable ADB
-In the Toolkit, go to Dual Sim>Individual and select the appropriate custom.bin and oeminfo.img from the thread of the toolkit. For my European one it was L31 SS C432. Press flash and grant Root permissions on your phone.
-Turn off your phone and flash the stock ROM again like in step 1.
-If you want root, you need to unlock the Bootloader again, flash TWRP and then root it from there.
DON'T WIPE ANYTHING IN TWRP OR YOU WILL HAVE TO START ALL OVER AGAIN!
Don't ask me how I know.
Hope this saves someone from wasting their time with this nonsense like I have.

No need to touch the oem stuff, just extract the boot.img and system.img and flash through adb, for dat you need bootloader unlocked and fastboot drivers then you can downgrade firmware and fix your sign problem or just wait for a new firmware

raffabraz said:
No need to touch the oem stuff, just extract the boot.img and system.img and flash through adb, for dat you need bootloader unlocked and fastboot drivers then you can downgrade firmware and fix your sign problem or just wait for a new firmware
Click to expand...
Click to collapse
That would be much simpler, I didn't consider that. Would you mind writing up a guide?

I've had the same issue and have resolved it pretty easily,
i did the following steps ;
- download both medrom versions
- do full factory reset
- install medrom v1
- do all settings of google etc
- reboot recovery and install v2
- wipe dalvik and reboot
-- all works now except for the forceclose on facebook
ps : this answer is also in the thread ( not as extended as this but it's there )
Edit : some other apps are Force closing to, my guess is that there's a shared resource of some kind that's corrupted or something..

sirlex said:
I've had the same issue and have resolved it pretty easily,
i did the following steps ;
- download both medrom versions
- do full factory reset
- install medrom v1
- do all settings of google etc
- reboot recovery and install v2
- wipe dalvik and reboot
-- all works now except for the forceclose on facebook
ps : this answer is also in the thread ( not as extended as this but it's there )
Edit : some other apps are Force closing to, my guess is that there's a shared resource of some kind that's corrupted or something..
Click to expand...
Click to collapse
Force closing is caused by the oeminfo in my experience. Can you check in the "About Phone" section which build number your phone currently has? Should be something along the lines of "VNS-L31C432B161" where C432 indicates the region code.

since I am Running MEDROM v2 it shows just that. However , I do know it is based on b161

HeavyHDx said:
I had the same issue. I did a clean flash of the new 161 update and that made my device a C900. I have a Eurpoean model (T-Mobile Germany).
After 2 days of trying different stuff, here's what gave me a functional device with TWRP and Root back:
-Back up any data you want to keep, obviously.
-Reflash stock ROM (put UPDATE.APP on your dload/ folder on the separate SD card, then boot into the update function by turning the phone off and then holding Vol+, Vol-, Power. Just wait until it's finished.
-Unlock Bootloader again
-Download the Toolkit: http://forum.xda-developers.com/huawei-p9lite/development/europe-vns-l31-toolkit-bootloader-t3432873
-Flash TWRP through the toolkit
-Boot TWRP and root
-In Android, enable ADB
-In the Toolkit, go to Dual Sim>Individual and select the appropriate custom.bin and oeminfo.img from the thread of the toolkit. For my European one it was L31 SS C432. Press flash and grant Root permissions on your phone.
-Turn off your phone and flash the stock ROM again like in step 1.
-If you want root, you need to unlock the Bootloader again, flash TWRP and then root it from there.
DON'T WIPE ANYTHING IN TWRP OR YOU WILL HAVE TO START ALL OVER AGAIN!
Don't ask me how I know.
Hope this saves someone from wasting their time with this nonsense like I have.
Click to expand...
Click to collapse
Thank you so much , you saved my phone !!
Fllashing stock rom again isnt necessary , just flash the oeminfo, reboot, they will tell you an encryption password, so you have to do a factory reset AND DONE !

simo255 said:
Thank you so much , you saved my phone !!
it doesn't need to reflash stock rom again, just flash the oeminfo, reboot, they will tell you an encryption password, so you have to do a factory reset AND DONE !
Click to expand...
Click to collapse
Interesting, when I tried to do a factory reset after that screen, it always failed.

HeavyHDx said:
Interesting, when I tried to do a factory reset after that screen, it always failed.
Click to expand...
Click to collapse
You have to flash the stock recovery to do a Factory reset

medRom v2 fix
Hi all.
I think i found solution for Google login issue.
I use European VNS-L21-C432B161 dual sim phone with lattest rom.
I flashed medRom v2 with full wipes.
Ofcourse i Can not log in Google Services.
Today i download 3 Google apk files. Installed and it works.
Sorry. I cant post ling on XDA now.im newbie
Link in My profils.
There is instruction how i do:
1. Installed Gmail apk and login.
2. Installed Android System Web Wiev apk.
3. Installed Google Play Service apk
Proof: in My profils description in Youtube
Download Files: watch in YOUTUBE description.
Hope helps for someone.

Could someone provide me the correct oeminfo and custom.bin for a European/German model? C432? The images inlcuded in the toolkit don't work for me, it still crashes or can't communicate with the google server

Deddline said:
Hi all.
I think i found solution for Google login issue.
I use European VNS-L21-C432B161 dual sim phone with lattest rom.
I flashed medRom v2 with full wipes.
Ofcourse i Can not log in Google Services.
Today i download 3 Google apk files. Installed and it works.
Sorry. I cant post ling on XDA now.im newbie
Link in My profils.
There is instruction how i do:
1. Installed Gmail apk and login.
2. Installed Android System Web Wiev apk.
3. Installed Google Play Service apk
Proof: in My profils description in Youtube
Download Files: watch in YOUTUBE description.
Hope helps for someone.
Click to expand...
Click to collapse
Installing Android System Web View apk from apkmirror solved the problem for me (arm + x86 package). Thank you

HeavyHDx said:
I had the same issue. I did a clean flash of the new 161 update and that made my device a C900. I have a Eurpoean model (T-Mobile Germany).
Click to expand...
Click to collapse
I got my P9 Lite from Congstar in Germany. I didn't knew, that the device would be branded by Telekom. I flashed the B161 and couldn't connect to any google account. Thankfully updating the webview apk via apk mirror solved this problem. But this leaves me with 2 questions and maybe you could answer these...?
1) Do you know which stock rom would work the best with my device (VNS-L31 without the possibility to use two sim cards ) and where I could download this stock rom.
2) Is the B161 supposed to work fine after solving this issue or are there other problems with it?
I would be really happy if someone of you could help me. :good:

MartinMo said:
1) Do you know which stock rom would work the best with my device (VNS-L31 without the possibility to use two sim cards ) and where I could download this stock rom.
2) Is the B161 supposed to work fine after solving this issue or are there other problems with it?
Click to expand...
Click to collapse
1) The best stock ROM would either be, well, the stock ROM, or the Revolution ROM.
2) I've had some strange behavior with Relay for Reddit and frequent crashes of WhatsApp when sending messages. Right now I'm on Lineage OS 14.1 and it's really great. Camera's a bit slow, but otherwise I love it. I missed stock Android.

HeavyHDx said:
1) The best stock ROM would either be, well, the stock ROM, or the Revolution ROM.
Click to expand...
Click to collapse
Isn't Nougat still a beta...? I'm looking for a stable stock version of EMUI...
HeavyHDx said:
2) I've had some strange behavior with Relay for Reddit and frequent crashes of WhatsApp when sending messages. Right now I'm on Lineage OS 14.1 and it's really great. Camera's a bit slow, but otherwise I love it. I missed stock Android.
Click to expand...
Click to collapse
Thank you, tomorrow I'll test if Whatsapp working fine or not, that's important for me. Is Lineage 14.1 the most stable Lineage version?

Nougat is still in beta, yes. The full version is expected to come out within the next few weeks.
14.1 refers to the Android version which is 7.1.1. They adopted CyanogenMod's naming scheme. You'll still need to update LineageOS to get bugfixes and such. The dev releases a new update every 2 or 3 days, just check their website periodically.

Deddline said:
Hi all.
I think i found solution for Google login issue.
I use European VNS-L21-C432B161 dual sim phone with lattest rom.
I flashed medRom v2 with full wipes.
Ofcourse i Can not log in Google Services.
Today i download 3 Google apk files. Installed and it works.
Sorry. I cant post ling on XDA now.im newbie
Link in My profils.
There is instruction how i do:
1. Installed Gmail apk and login.
2. Installed Android System Web Wiev apk.
3. Installed Google Play Service apk
Proof: in My profils description in Youtube
Download Files: watch in YOUTUBE description.
Hope helps for someone.
Click to expand...
Click to collapse
Installed Android System Web Viev .apk did the trick for me, too. muchos gracias.

Custom Rom For Samsung J2 (J200H) S7 Experience Custom Build

Hey There ...........
Introducing My New Rom : S7 Experience Custom Build
Built V1
Based On Stock 5.1.1 Lollipop Rom
Warnings :
1. You are now Void your Warrenty …….
2. Backup all your personal apps and important data to avoid loosing them …
3. Do all steps perfectly And carefully ……
4. I am not responsible for any mistake and Brick your phone ….[/SIZE]
Features :
1. Only For J2 2015 3G Variants
2. Android 5.1.1 Lollipop
3. Based on latest J200HDDU0APE1/APJ3 firmware
4. Deodexed
5. Medium Deboalted
6. Zipaligned
7. Signed
8. PreRooted
9. Added Busybox,SU.d and Init.d Support
10. S7 Style Statusbar
11. S7 Music Player
12. S7 Themed Apps
13. Xposed Enabled Zip Added
14. All Apps Are Updated
15. Fx Root Explorer
16. Sony Movies Added
17. S7 Wallpaper
18. S7 Icons
19. S7 Sound And Bootanimation
20. And More ...
How To Install :
1. Download Zip file Of the Rom From Link Given Below
2. You Mast Have TWRP Recovery on your device.(Letest TWRP is Given In attachments)
4. Copy the S7 Experience Custom Build.zip toYour SD card
5. Turn off Your Phone And press home button+power+Volume up button at a same time
6. Aftar apearing TWRP recovery go to install and install S7 Experience Custom Build.zip file from sd card you downloaded before
7. Now reboot system and wait for approximately 5 minutes.
9. Now you are good to use this rom ......
[For Xposed Install xposed-v78.0-sdk22-arm-custom-build-by-wanam-20151116.zip after installing rom given in the attachments]
Downloads :
https://drive.google.com/open?id=0B0rTXdhaTd2MV2szTEYtQWVIeVU
Credits :
@ASSAYYED –for his best ever kitchen.
@ashyx - for his Twrp
@me - For building Rom
Contact Me :
On Facebook Only Send Massages
www.facebook.com/almamun512

Thanks
Nice rom the rom like realy galaxy s7 I very like this

Great work . I will soon test it By the way is there theme support and if not are you planning to do it????

ad. said:
Great work . I will soon test it By the way is there theme support and if not are you planning to do it????
Click to expand...
Click to collapse
Actually Theme Option Is Enabled But Its Not Change Everything, I Dont Know Why, But thing Is Our Framework Doesn't Suppot That.

almamun512 said:
Actually Theme Option Is Enabled But Its Not Change Everything, I Dont Know Why, But thing Is Our Framework Doesn't Suppot That.
Click to expand...
Click to collapse
ok but my phone stick in bootlogo when i tried to install xposed it said unable to mount system ?????? what to do

ad. said:
ok but my phone stick in bootlogo when i tried to install xposed it said unable to mount system ?????? what to do
Click to expand...
Click to collapse
Did You clean Insall It ?
Do Wipe/Advance Wipe/system,data,delvik,catch
Then Install
Make Sure Your Device Is J200H 3g

almamun512 said:
Did You clean Insall It ?
Do Wipe/Advance Wipe/system,data,delvik,catch
Then Install
Make Sure Your Device Is J200H 3g
Click to expand...
Click to collapse
I tried both clean and dirty flash but no sucess ...
I got where the problem is...
system is not being fully extracted . There lacks many folders like priv-app in system partition .
I installed another zip file and noted that every thing is working well the system got fully extracted.
Maybe the problem is in updater-script Hope you can fix it soon

Will it wrk on j200g?

ad. said:
I tried both clean and dirty flash but no sucess ...
I got where the problem is...
system is not being fully extracted . There lacks many folders like priv-app in system partition .
I installed another zip file and noted that every thing is working well the system got fully extracted.
Maybe the problem is in updater-script Hope you can fix it soon
Click to expand...
Click to collapse
Can you send me a picture of the error or something.
There Should be no problem in updater-script
Also send me your about devices screenshot

almamun512 said:
Can you send me a picture of the error or something.
There Should be no problem in updater-script
Also send me your about devices screenshot
Click to expand...
Click to collapse
http://imgur.com/GYMLjJL
here's the ss about phone and i cant send picture of error but I'm sure the problem was caused due to the problem in system
The flashing had went smoothly but when i tried to boot to system i got atuck at samsung galaxy j2 screen and on checking system via twrp file manager i gound ther lacked different things.
I don't know if its the problem of my twrp or else I'm thinking of giving one try to flashify

ad. said:
http://imgur.com/GYMLjJL
here's the ss about phone and i cant send picture of error but I'm sure the problem was caused due to the problem in system
The flashing had went smoothly but when i tried to boot to system i got atuck at samsung galaxy j2 screen and on checking system via twrp file manager i gound ther lacked different things.
I don't know if its the problem of my twrp or else I'm thinking of giving one try to flashify
Click to expand...
Click to collapse
What Rom Are U Using Stock ?
I Dont think so.
Anyway Its strongly Recommended to be on letest Stock Rom Before Flashing My Custom Rom.
Nobody Having this Problem Like You.
And Use the TWRP I gave in attachment.

Not working....
Sent from my SM-J200H using XDA Free mobile app

wow this rom is better than i expected

in twrk recovery i got msg regarding it succeeded. but after that my mobile is still booting showing samsung j2 android. pl help me.

finally got it
Best rom out till date.
thanks @almamun512

No superuser access
I flashed this custom rom today and i like the new UI. But there is no superuser preinstalled although it said installing superuser when flashing the rom. I also installed supersu later using twrp but it says " Your device is unrooted."
How can i install superuser and gain root access ?

Nikeshsml said:
I flashed this custom rom today and i like the new UI. But there is no superuser preinstalled although it said installing superuser when flashing the rom. I also installed supersu later using twrp but it says " Your device is unrooted."
How can i install superuser and gain root access ?
Click to expand...
Click to collapse
I didn't experienced that problem. The phone was rooted only SuperSU app was missing which I installed.

Good day sir. I appreciate your hardwork creating the rom. :good: Will it work on a j200bt rom?

GREAT ROM
Beautiful Rom and fast but the problem i faced was the wifi reconnecting every 2 minutes and cant customize the rom by apps like gravity box ....
battery is friendly and i hope to make update for this vertion of S7 because the S8 Randomly restart without any reason
thanks a lot from my heart .

Rom can be flash in samsung J200GDDUZAQF6
PLEASE REPLY ME

[ROM-sGSI] [ZUI 10.0]/[ZUI 5.0] From Z5 FOR Z2 Plus [Oreo]

What is this?
- sGSI of ZUI 10.0/ 5.0 from Lenovo Z5pro/Z5, based on Android 8.1.0, June 1,2018 security patch.
Since this was requested in some comments, I flashed it and found working for our device flawlessly, with some bugs.
Features?
-All features of ZUI 4 + Soft Charge, gestures, multi space ( dual apps ) etc. Split Screen is also available.
How to flash?
ZUI 10 :
1. Download the flashable zip from the links.
2. Boot to twrp, and wipe dalvik, cache, data, system and vendor.
3. Flash the zip.
4. Reboot.
ZUI 5:
Method 1 : (Recommended)
- 1. Download any treble based 8.1.x rom and ZUI5.0-sGSI.zip (link below).
[Please use MIUI 10 8.11.1 by Narshi Shukla as base ROM, as it seems it's Vendor is most compatible.]
2. Extract the zip in your storage. You will get three files ( two flashable zips and one folder "sGSI.....". [Folder name might differ, there will be only one folder, so no worries])
3. Boot into recovery and take a backup.
4. Clean flash treble based Oreo ROM that you downloaded.
5. From your twrp, use file manager to move " sGSI...." folder to backup folder of Twrp.
6. Mount system and vendor and wipe cache/delvik, data and system.
( Don't wipe firmware and Vendor )
7. Goto restore in your twrp and restore the system from "sGSI....." folder.
8. Flash the remaining two zips.
9. Flash magisk if needed.
10. Wipe cache/delvik and reboot. Done.
Method 2 : https://forum.xda-developers.com/showpost.php?p=78389810&postcount=320
(You need treble based twrp, search if you don't already have).
After following all these steps, if your phone is stuck in Lenovo powered by android screen for long, then force reboot the phone and it will boot up to system.
What works?
-Here:
Call,SMS, VOLTE, Data, play store, Utouch, Fingerprint , Navigation, Double touch to wake, GCAM, Face Unlock, Hotspot, Banking apps, nearly everything.
What doesn't work?
- ROM specific. Bugs depend upon the treble ROM that you used as base. In some ROM, system sounds does not work. In MiUI 10, video recording might not work. Game Mode has some issues with global apps.
*FOR VIDEO RECORDING - see this : https://forum.xda-developers.com/showpost.php?p=78219358&postcount=93 ****
*Update GPU drivers for VULKAN support. Link in the links section.***
Performance?
- Better than ZUI 4, smooth as butter, no stutter playing games like PUBG, notifications on time, decent SOT.
Can it be used as daily driver?
- Yes, if you can live with some Chinese texts in certain apps.
Any other thing?
- Because the ROM is ported from Z5 which has a notch, total area of the notification bar cannot be used. To see things like real time network speed and battery "percentage" you have to pull down the notification bar.
What should I do first after booting the device?
- Install play store from App center. Install magisk to remove bloat wares. Install any music app, since there is none. This will make the system optimal for us.
Also, Turn "True Full Screen Mode" ON in display settings for full screen in Apps.
Install Magisk and download and install "SafteyPatch V2" within Magisk to pass safetynet and hide banking apps in magisk hide to use them.
Open security app and give all important permissions to the apps you use, including system apps. Also include them in autorun/whitelist section.
Links?
-Here
ZUI 10
https://drive.google.com/open?id=17lyWnAl0Kjkv5S89wdtw7HglF2072zP5
ZUI 5
Mega link :
https://mega.nz/#!FyxSiI7Y!iZmmVufR6pipX3mwv_-I3HqI714YAMJN1a2zIysinmc
Gdrive link:
https://drive.google.com/open?id=1F_Ou6x2bj26hhdffw45uo4r9qlJuaDb5
MiUi 10 8.11.1 Narshi Shukla - Full Rom
https://androidfilehost.com/?fid=11410932744536996684
MIUI 10 8.11.1 Narshi Shukla - Vendor for twrp recovery: @(THIS VENDOR isnt compatible with all roms, if facing random reboots, use the complete MIUI 10 ROM for the Gsi)
https://drive.google.com/drive/u/0/folders/15QHEUfLMagMV9jZTmlUHa4hkhkNTF-RC
Working GCAM link :
https://www.celsoazevedo.com/files/android/google-camera/f/MGC_6.1.021_FINAL_V1a_A8.1+.apk
VULKAN enabled open GL 3.2 driver link :
https://drive.google.com/folderview?id=11_atz5CDK9bHG4K_ME2LSRFFnxxKqWw2
Credits:
Not my work, I am just sharing it since I found it working.
All credits goes to this Xiaomi thread and bugrevealingbme.
https://*************/threads/zui-5-0-a-only-treble-rom.226/
******************************** FLASHING ISSUE ******************
While flashing this ROM, try to follow the guide above as strictly as possible. Use the ROM that is recommended.
If you are facing bootloop, download the vendor that is provided and restore it in twrp and then flash patch 1 and 2.
Also remember, during each and every step, your TWRP should have system and Vendor mounted. Check after every step.
Your phone might reboot once or twice during first boot, which is not an issue.
How to know if you flashed it correctly?
-If your phone boots into the system with "Lenovo bootanimation" , you flashed it correctly.
If your phone is stuck in "Lenovo - powered by android" splash image for more than 5 minutes, you got something wrong.
*********************************************************************
Screenshots attached :

what about gcam nd notification bug? and one more doubt, can we flash it over treble pie ROM?

I have one question. If i install a sgsi rom can i back to trenle, non-treble rom just with a simple flash method?

muujeeb said:
what about gcam nd notification bug? and one more doubt, can we flash it over treble pie ROM?
Click to expand...
Click to collapse
gcamera is working on redmi note 5 pro. should work also here.

muujeeb said:
what about gcam nd notification bug? and one more doubt, can we flash it over treble pie ROM?
Click to expand...
Click to collapse
GCAM is working.
Notification bug is not there. Only sometimes, it seems that we get late notification.
You have to flash it over Oreo because the GSI is Oreo based. Flashing over pie should work as well, since treble ROM is required. Take a backup of your system so you can restore easily, if you face any issue.

nonamesry said:
I have one question. If i install a sgsi rom can i back to trenle, non-treble rom just with a simple flash method?
Click to expand...
Click to collapse
Yes, you can get back to the ROM you want with simple flash, no problem.

Custom kernel flashable?

ashwinonm said:
Custom kernel flashable?
Click to expand...
Click to collapse
Haven't tested, but should be flashable.
Edit : Custom kernel might brick the device. Will test and update.
Donot flash custom kernel, it causes self restart of device.
Note: Moxie kernels can be flashed, you should flash patch2 after flashing kernels. But, MIUI 10 comes with moxie R5.1 so no use flashing Moxie again.

link not working

Wow it's so beautiful!

I used Arrow OS 8.1 but it got stuck in bootloop and does'nt boot at all.. I followed all the steps accordingly but it did not boot up even after i kept my phone overnight to let it boot. I don't know where i did wrong.

muujeeb said:
I used Arrow OS 8.1 but it got stuck in bootloop and does'nt boot at all.. I followed all the steps accordingly but it did not boot up even after i kept my phone overnight to let it boot. I don't know where i did wrong.
Click to expand...
Click to collapse
Use MIUI 10 port of Narshi Shukla latest build. It works.
May be Arrow OS cannot be used.
You can also try using Vendor of MIUI 10 once. Restore this vendor and the system image of ZUI.
Here is the vendor:
https://drive.google.com/drive/mobile/folders/15QHEUfLMagMV9jZTmlUHa4hkhkNTF-RC?usp=drive_open

kany1 said:
link not working
Click to expand...
Click to collapse
Link is working fine.

jebish7 said:
Link is working fine.
Click to expand...
Click to collapse
yes it is working with mega app

I used crdroid 8.1 and got stuck in bootloop. then I try restored the vendor but could not flash the patch 2
---------- Post added at 01:19 PM ---------- Previous post was at 01:13 PM ----------
ok i try to flash it again and boot successflly

marclevine said:
I used crdroid 8.1 and got stuck in bootloop. then I try restored the vendor but could not flash the patch 2
Click to expand...
Click to collapse
I think only MIUI 10 rom works flawlessly for this GSI. I will update the main page details and ask to use MIUI 10 only.
You couldnot flash patch 2 because it requires vendor, and may be your vendor is now messed up.
So use MIUI 10 port, it works without any issue.

marclevine said:
I used crdroid 8.1 and got stuck in bootloop. then I try restored the vendor but could not flash the patch 2
---------- Post added at 01:19 PM ---------- Previous post was at 01:13 PM ----------
ok i try to flash it again and boot successflly
Click to expand...
Click to collapse
Glad To hear.

So in whatever rom I am in Oreo , I can use that firmware if I use vendor only from your backup? And shouldn't wipe it?

ashwinonm said:
So in whatever rom I am in Oreo , I can use that firmware if I use vendor only from your backup? And shouldn't wipe it?
Click to expand...
Click to collapse
Well, that's how some people got this working, so yes, it's working that way as well. ( Your ROM should be treble based though )
I will attach the "Vendor" file in the main post as well, so other members can use it too.

custom kernel possible,mine running in moxie

[SOLVED] Phone gets stuck in bootloop if I try to install Magisk ZIP!

From the forum I followed these step to install magisk:
- Patched my boot.img of my current rom using Magisk Manager and flashed via fastboot
- After rebooting from fastboot it got stuck in recovery so had to wipe all data and it booted finally
- After booting up installed Magisk Manager and both Magisk and Magisk manager shows green tick (installed)
But at this stage, whenever I open Magisk, it shows a recommendation to install a ZIP, if I agree to install it, phone gets stuck in recovery again.
If I choose not to install recommended zip and click Install > Direct Install, phone gets stuck in recovery again anyway
Everytime it gets stuck I have to wipe all data and start all over again. Anyone else facing same issue? Any solution?
Really frustrated right now.
My current rom is : DAVINCIIN INDIAN Global_V11.0.2.0
Used latest magisk manager 7.4.0
I have official recovery, not TWRP.
Afraid that flashing TWRP now will brick it for good.
UPDATE: Got the solution here, thanks @pikchu289 !

Twrp up to now is the best way
But check some stuff first
1.unlock the boot loader
2.chech if the magisk zip/img is corrupted or any file
3.does your os support this magisk version
Any way you can flash twrp because many people had already tried it and tested it from installing zips/ROMs/mods etc.. to backup files/data or even fixing some corrupted files that caused boot loops manually
But there are various things that doesn't work usually such as restoring system partition but never worry about this because if any thing failed just use miflash tool to go back to official/stock rom
Edit : I think something's wrong with your magisk version number

I have no idea which rom youre using or why on earth you didn't install TWRP before messing around with the os but some roms dont work with latest magisk and you have to use a specific older version depends on your rom, and you can't update magisk at any point as long as youre on this version of the rom. Ive always used custom recovery and when facing an issue with magisk you just boot to recovery and flash the 'magisk uninstaller' zip (available on magisk xda page) and reboot and you get system. No need to start from scratch

Solve this solution
Dear stone_henge!
I found a method to solve this solution after a lot of days I tried a lot of times! As follows:
1. I back up my Internal storage to my PC
2. Format Data (In TWRP: Wipe -> Format Data)
3. I reboot back into recovery
4. I connected my device to PC via a cable and copy two files: "Magisk-v20.1.zip" and "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" into Internal storage. Then rename "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" to "Disable_ForceEncrypt.zip"
4. I flash "Magisk-v20.1.zip", then I reboot back into recovery again.
5. I flash "Disable_ForceEncrypt.zip" . Reboot to system and setting my phone like after flash a new room, and then I installed "MagiskManager-v7.4.0.apk"
It's working for me!
You can download "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" here: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389

pikchu289 said:
Dear stone_henge!
I found a method to solve this solution after a lot of days I tried a lot of times! As follows:
1. I back up my Internal storage to my PC
2. Format Data (In TWRP: Wipe -> Format Data)
3. I reboot back into recovery
4. I connected my device to PC via a cable and copy two files: "Magisk-v20.1.zip" and "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" into Internal storage. Then rename "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" to "Disable_ForceEncrypt.zip"
4. I flash "Magisk-v20.1.zip", then I reboot back into recovery again.
5. I flash "Disable_ForceEncrypt.zip" . Reboot to system and setting my phone like after flash a new room, and then I installed "MagiskManager-v7.4.0.apk"
It's working for me!
You can download "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" here: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Click to expand...
Click to collapse
Finally someone with an answer!
Thanks... Will try and see if it works...
UPDATE: IT WORKED!

Aserar said:
I have no idea which rom youre using
Click to expand...
Click to collapse
Maybe I should've used font size 72 while writing the rom I'm using above.
Aserar said:
why on earth you didn't install TWRP before messing around with the os
Click to expand...
Click to collapse
Yeah some people prefer to have stock recovery and not mess with the phone that much... But while you seem to be an expert on what to do, maybe you could try be helpful a bit and provide with the guide of flashing TWRP on k20? Yeah i can obviously see there are guides already in the forum but I'm curious to know which one you followed.
Aserar said:
some roms dont work with latest magisk and you have to use a specific older version depends on your rom, and you can't update magisk at any point as long as youre on this version of the rom. Ive always used custom recovery and when facing an issue with magisk you just boot to recovery and flash the 'magisk uninstaller' zip (available on magisk xda page) and reboot and you get system. No need to start from scratch
Click to expand...
Click to collapse
None of these lines actually answer my problem or even help in any way. But thanks for enlightening me. -_-

It's true I did miss the part where you mentioned your rom but let's recap..
I did tell you you should install custom recovery.
I did tell you you should probably stick with the magisk version that works and not to update.
I did tell you you don't need to start over every time you get a problem caused by magisk and you can just flash magisk uninstaller and get your system back.
You don't see any of that helpful??? That's fine bc I got news for you.. THIS FORUM IS FREE! Do I have to research your problem for you and give you a step by step guide or else you whine about it?? Plus this is a public forum. People share the knowledge they have with everyone who reads it now and in the future and might get a piece of information out of it.
If you use the time you waste attacking people who used their time to try and help you (instead of saying thanks anyway like the rest of us do) into doing your research (like the rest of us do too) you'll probably be fine.
stone_henge said:
Maybe I should've used font size 72 while writing the rom I'm using above.
Yeah some people prefer to have stock recovery and not mess with the phone that much... But while you seem to be an expert on what to do, maybe you could try be helpful a bit and provide with the guide of flashing TWRP on k20? Yeah i can obviously see there are guides already in the forum but I'm curious to know which one you followed.
None of these lines actually answer my problem or even help in any way. But thanks for enlightening me. -_-
Click to expand...
Click to collapse

Aserar said:
It's true I did miss the part where you mentioned your rom but let's recap..
I did tell you you should install custom recovery.
I did tell you you should probably stick with the magisk version that works and not to update.
I did tell you you don't need to start over every time you get a problem caused by magisk and you can just flash magisk uninstaller and get your system back.
You don't see any of that helpful??? That's fine bc I got news for you.. THIS FORUM IS FREE! Do I have to research your problem for you and give you a step by step guide or else you whine about it?? Plus this is a public forum. People share the knowledge they have with everyone who reads it now and in the future and might get a piece of information out of it.
If you use the time you waste attacking people who used their time to try and help you (instead of saying thanks anyway like the rest of us do) into doing your research (like the rest of us do too) you'll probably be fine.
Click to expand...
Click to collapse
Sorry for being harsh... I understand you actually tried to help. It's actually really frustrating when facing a problem that has no straightforward solution.
Sorry mate.

finally i founded how to fix this issue without formating data of ur device
--just the flash the same the full custom rom or stock rom that u r using currently on . and boom restart. and ur issue fixed

Install a magisk zip without TWRP. TWRP takes too long. Instead use Aodin to flash a rom specific to your device version. Make sure it is not corrupted as well