[ROOT] PingPongRoot ***S6 & S6 Edge Root Tool*** Android 5.0.2 OC3/OE2 Only!!!

[ROOT] PingPongRoot ***S6 & S6 Edge Root Tool*** Android 5.0.2 OC3/OE2 Only!!! - Galaxy S6 General

Just another party by Keen Team
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I'm getting increased queries and replies in this post/PM recently, so I'll try to make this clear (hopefully) for 99% of people. Short version of OP which you must read:
1. Don't install 5.1.1 for now if you ever want to root without tripping Knox warranty.
2. No new ROM can be supported as bug has been fixed.
3. If you don't know how to check a kernel's build date, DO NOT submit FPTAG.
Full story:
New bootloader blocks downgrading, be careful installing 5.1.1 OTA! More details: http://forum.xda-developers.com/tmobile-galaxy-s6-edge/general/psa-odin-5-1-1-t3136151
Kernel built after May 15th (including some 5.0.2 and all 5.1.1) have this bug fixed. Be cautious when installing OTA these days and FlashFire might be your best shot of upgrading systems. Use Odin to unroot and receive OTA if you want.
Current version: Beta 6 (HTC One (M9) SUPERSU VERSION! Check updated Usage section!)
Since Beta 5.2: Should be more "stable" on devices with more application installed, but I'm not 100% sure. If it doesn't work, roll back to beta 5.1
I'm getting too many queries about Note 4. Two things to clarify: 1) No device data needed to root Note 4, try KingRoot 4.0. 2) Unless you have KNOX warranty bit tripped already, there is no perm-root for Note 4 yet.
If you have decent bandwidth and experience with ROM files, please see this: http://forum.xda-developers.com/galaxy-s6/general/root-pingpong-root-rom-workshop-thread-t3104639. Volunteers needed to speed up adding new ROMs.
Big THANK YOU to all helped collecting ROMs. Now we have 91+2 ROM versions supported!
Everyone please do me a favor. If you want a ROM (S6 or S6E) get supported, please confirm it is not yet supported and post a reply in this thread like:
FPTAG fingerprint here
So I can quickly filter FP out of the replys by using search. Thanks.Only submit if you know what a kernel build date is.
Supported devices
Samsung Galaxy S6 with following ROM versions:
G9200ZCU1AOD5
G9200ZHU1AOD3
G9200ZHU1AOD9
G920R4TYU1AOD3
G920IDVU1AOD1
G920FXXU1AOCV
G920PVPU1AOCF
G920TUVU1AOCG
G920VVRU1AOC3
G920FXXU1AOBN
G920FXXU1AODG
G9209KEU1AOCI
G9209KEU1AODA
G9208ZMU1AOD5
G9208ZMU1AOCI
G920FXXU1AOD9
G920AUCU1AOCE
G920FXXU1AODE
G9200ZCU1AOD9
G920W8VLU1AOCG
G920FXXU1AOD4
G920R4TYU1AOCB
***new*** Use Download Data!
G920FXXU1AOCY
G920IDVU1AOC4
G920FXXU1AODI
G9209KEU1AOD5
G920IDVU1AOBQ
G9208ZTU1AOD9
G920FXXU1AOE3
G920IDVU1AOE3
G920FXXU1AOD8
G920FXXU1AOE4
G920AUCU1AOE2
G920T1UVU1AOCH
G9208ZTU1AOCI
G920IDVU1AOC6
G920IDVU1AOD3
G920FXXU1AOCZ
G920AZTUU1AOD1
G9200ZHU1AOE4
G9200ZCU1AOE4
G920KKKU1AODC
G920IDVU1AOE4
G920LKLU1AODC
G920SKSU1AODC
G920IDVU1BOE2
G9208ZTU1AOE4
G920PVPU1AOE2
G920W8VLU1AOE1
G920VVRU1AOE2
SC04GOMU1AOE1
Samsung Galaxy S6 Edge with following ROM versions:
G9250ZCU1AODC
G925VVRU1AOC3
G925FXXU1AOD9
G925PVPU1AOCF
G925FXXU1AOCV
G925AUCU1AOCE
G925TUVU1AOCG
G925W8VLU1AOCG
G925IDVU1AOD1
G925SKSU1AOD5
***new*** Use Download Data!
G925FXXU1AOD4
G925R4TYU1AOD3
G925FXXU1AODG
G925FXXU1AOCZ
G925IDVU1AOD3
G925LKLU1AOD8
G925SKSU1AOD8
G925FXXU1AOE3
G925PVPU1AOE2
G925FXXU1AOD8
G9250ZTU1AODC
G925FXXU1AOE4
G925AUCU1AOE2
G925TUVU1COE6
G925FXXU1AOCY
G9250ZTU1AOE4 (5/11 kernel, seems not fixed yet, please test)
G925R4TYU1AOE2
SCV31KDU1AOCP (Japan version of S6E?)
G9250ZCU1AOCH
G9250ZCU1AOE4
G925IDVU1AOE4
G925IDVU1BOE1
G925LKLU1AODC
G925IDVU1AOE3
G925IDVU1AOE2
G925KKKU1AODC
G925SKSU1AODC
G925W8VLU1AOE1
G925VVRU1AOE2
G925R7WWU1AOE3
HTC One (M9) -- EXPERIMENTAL, UNLOCKED BL REQUIRED
htc/himauhl_htccn_chs_2/htc_himauhl:5.0.2/LRX22G/516731.9:user/release-keys
Verizon 1.33.605 (?)
New ROM and device support are coming~~
If your ROM version is not listed here, please check if any ROM with the same variant is already supported. If the supported one is newer, I suggest go and grab it instead of waiting.
Known Issues:
None
Todo:
Coming next release: (will come after SuperSU version)
TBD
In queue:
Check the workshop thread: http://forum.xda-developers.com/galaxy-s6/general/root-pingpong-root-rom-workshop-thread-t3104639 but DO NOT REPLY UNLESS YOU ARE WORKING ON ROMS. Thank you for keeping that post clean!
Usage
OK, since manual switch is too complex and there are some compatibility issue of Kinguser, I'm making a SuperSU version now.
Note that due to the natural that SuperSU su doesn't ask for permission when SuperSU apk is missing, root will only happen when SuperSU apk has been installed. Read instrucitons below CAREFULLY!
0. Read Q&A section and BACKUP your data.
1. If you already have Kinguser installed please:
a. Open Kinguser, go to Settings -> Root authorization setting -> Remove Root permission. Click to remove root permission
b. Uninstall Kinguser2. Download pingpongroot_<ver>.apk. Install & open it.
3. It will automatically install SuperSU 2.46 for you. Follow the instructions on screen. You may need to enable unknown source for this step.
a. Once install is finished, click “Open" and run it once to "activate" it. It will prompt an error message (unless you already rooted) and exit automatically, bring you back to PingPong root.4. Click "Download Data" button to update device data if you have Internet connection.
5. Open it and click "Get Root!" button
6. If prompted for app permissions, allow them and continue. If it reboots, just retry.
7. Once finished, please make sure to reboot.
8. You can uninstall PingPong root app once finished.
Credits
Vulnerability: memeda, wushi
Original idea of exploit: memeda
Exploit: idl3r, Qoobee
Special thanks to:
Kingroot team (@Kingxteam) for help testing and great root manager
Q&A
Q: How to root 5.1.1 then since PingPong root will never work?
WARNING: User report that fingerprint sensor and incoming call stop working after using the engineering sboot.
A: The classic recovery root method. You shall find details in many other posts. If you are T-Mobile user, lucky for you that there is a leaked engineering bootloader which make root a piece of cake without tripping Knox warranty bit:
http://forum.xda-developers.com/gal...-root-tool-t3103016/post61684664#post61684664
Q: It just keeps rebooting, what can I do?
A: The exploit may panic the kernel and reboot your device. If the data is off, same could happen as well. When issue happens, try these:
a. Clean up background process before running root.
b. Turn on airplane mode after clicking "Download Data".
c. Backup your data and run factory reset.
d. Definitely avoid doing anything else when "wait!!!" appears.If these doesn't help after 5 retries, there could be some issue, please collect the information in /proc/last_kmsg and send it to me.
Note: User reporting installing My Knox or enable other Knox feature (like enterprise provision or KNOX active protection) may cause reboot loop. Be cautious!
Q: My ROM is not yet supported?
A: Since I have limited bandwidth to download ROMs, I have to prioritize ROM requests and focusing on new variants/models first. And currently recruiting volunteers to help download/shrink ROMs.
If you see your ROM FP is not listed, but a very similar one (may be just the last digit or character is different) exists, please see if you can flash that version of ROM. I'm sure you can find someone helping you in corresponding forum.
Q: Will Samsung Pay/My Knox work?
A: To be honest I can't tell for sure. Indeed this root does not trip warranty bit. But it still leaves SU files, which is inevitable, on system partitions. And a lot of root features actually make change to system partition, so let's say it can be detected. If Samsung makes the decision that there will be no certain feature for presence of a su file, then there will be no fun. IMHO this is very bad idea since even Apple doesn't disable anything on jailbreak devices. Let's see what will be the outcome. This makes sense to enterprise uses but for consumers at least a choice should be given.
Q: Note4/Z3/Old Samsung/etc?
A: We also wrote the rooting engine in KingRoot 4.0 for generic 32-bit devices. Give it a try. Note that for some devices like Note4, only temp root is achievable.
Q: Why "PingPong" root?
A: Because the vulnerability affects ping socket and we are Chinese
Q: What's the current status of this tool?
A: Beta. We've thoroughly tested it on ROMs for G9200, but not other variants. You are the 1st batch of beta testers!
Q: Is my device supported?
A: You can check the version of your ROM in "About this phone" page. It shall read LRXxxx following by the ROM version.
This tool checks your ROM version as well. If you read "Your device data is still not supported." after clicking "Get Root!", your device data has not been collected yet. Please reply with your ROM version plus keyword "FPTAG" in this thread.
Q: Will this root trip KNOX warranty bit or disable OTA?
A: No, it won't trip KNOX warranty bit and YES, it will disable OTA. It doesn't require odin to flash in a custom recovery, so the warranty bit will remain intact.
Q: I'd like switching to SuperSU, what shall I do?
A: Kinguser does not have a "swtich" function. Follow these steps to do so manually: (if you are not familiar with adb, see this version: http://forum.xda-developers.com/showpost.php?p=60632150&postcount=269)
1. Download supersu.7z and extract it. You will get the files needed to install Supersu.
2. Using adb to push su and busybox (if not installed) to /data/local/tmp.
Code:
adb push su /data/local/tmp
adb push busybox /data/local/tmp
3. Start a su session and run the following commands:
Code:
mount -o remount,rw /system
cat /data/local/tmp/su >/system/xbin/daemonsu && chmod 0755 /system/xbin/daemonsu
cat /data/local/tmp/busybox >/system/bin/busybox && chmod 0755 /system/bin/busybox
daemonsu -d &
Then keep the session running.
4. Open Kinguser, go to Settings -> Root authorization setting -> Remove Root permission. Click to remove root permission. Your su session should be still running.
5. Uninstall Kinguser app.
6. Go back to the su session and run following commands to replace su and cleanup:
Code:
cat /data/local/tmp/su >/system/xbin/su && chmod 0755 /system/xbin/su
busybox chattr -ia /system/bin/ddexe
busybox chattr -ia /system/bin/ddexe_real
cat /system/bin/ddexe_real >/system/bin/ddexe
busybox chattr -ia /system/xbin/ku.sud
rm /system/xbin/ku.sud
rm /system/xbin/pidof
rm /system/xbin/supolicy
7. Install Supersu apk
8. Open Supersu apk to update files.
9. Reboot.
Q: S6 Edge/G Flex 2/M9/other arm64 devices?
A: We will look into them soon
S6 Edge: Done
M9: WIP
G Flex 2/others: pending
Q: I need a video to guide me through
A: Check out this one: https://youtu.be/_Ezh7Oi-jyM
(Note: these are for earlier version)
https://www.youtube.com/watch?v=gNdWX31Sqd8
and this one: http://youtu.be/eAQ4WBg9xj0
To all sent me PM: I'm sorry that the reply could be delayed. Currently we are busy working on supporting of new ROMs and fixing bugs. To all those providing useful info/suggestion, thanks a ton!

nice work
great！

Holy crap man!!! GREAT WORK!!!!

great work! knox 0x0

You guys are awesome! Patiently waiting for G920FXXU1AODG to be incorporated

Any chance of the ATT variant being rooted?

Japultra said:
You guys are awesome! Patiently waiting for G920FXXU1AODG to be incorporated
Click to expand...
Click to collapse
Downloading the ROM now, mate Will be included in the next Beta which will happen soon enough

Kokorone said:
Any chance of the ATT variant being rooted?
Click to expand...
Click to collapse
Yes, they are waiting for an ATT rom to appear first though.

Wow...can't believe! [emoji33]
Nice work! [emoji106]
Now switched from beta1 to beta5 and SuperSU...worked like a charm!
Titanium Backup is now running how it should.
Yeah...root access until next Update to 5.1.1 [emoji7]

and Knox says 0x0?

Hoping for g920fxxu1a0cw to be included great job mate!

is it possible with G920FXXU1AOD9 french region

G920FXXU1AODG here, will it work for that firmware? (Vodafone Germany)

Joern85 said:
G920FXXU1AODG here, will it work for that firmware? (Vodafone Germany)
Click to expand...
Click to collapse
It's coming in the next update!
---------- Post added at 10:44 AM ---------- Previous post was at 10:43 AM ----------
tutti9372 said:
and Knox says 0x0?
Click to expand...
Click to collapse
You should really read the OP
Q: Will this root trip KNOX warranty bit?
A: No. It doesn't require odin to flash in a custom recovery, so the warranty bit will remain intact.
Click to expand...
Click to collapse

I'm wondering if the vulnerability used here exists on the S6 Edge. Because I don't see anyone posting a SM-925xx Rom and to my understanding SM-920 is normal S6, where as SM-925 is the edge version.

Fantastic work, Idler! Will you publish the source code for this?

cpfeifer said:
I'm wondering if the vulnerability used here exists on the S6 Edge. Because I don't see anyone posting a SM-925xx Rom and to my understanding SM-920 is normal S6, where as SM-925 is the edge version.
Click to expand...
Click to collapse
Oh, I shall update the Q&A section. S6E (and may be other arm64 devices) will be investigated. And vulnerability should still be there for any kernel before 5/3.

idler1984 said:
Oh, I shall update the Q&A section. S6E (and may be other arm64 devices) will be investigated. And vulnerability should still be there for any kernel before 5/3.
Click to expand...
Click to collapse
That's good to hear. My current kernel is from April 10th and I've got the latest ota. Hopefully I can get root before a forced ota is pushed out with a kernel update.

That is truly great work....
and my FAVOURITE
After switching to SuperSU, aps like TitanumBackup, RootExplorer and many probably more works great.
I just edit my "others.xml" and just the begin of having true FUN with my phone
BIG THANKS for ROOT

idler1984 said:
Oh, I shall update the Q&A section. S6E (and may be other arm64 devices) will be investigated. And vulnerability should still be there for any kernel before 5/3.
Click to expand...
Click to collapse
Thanks for your great tool. For us who have tripped knox will it untrip or not.:

Related

[Q&A/T] - [AOSPA 4.4.4 KTU84P] ParanoidAndroid 4.4+ G2

[SIZE=+2]This thread has been created
for
Questions & Answers/Troubleshooting[/SIZE]
[SIZE=+2]Specific to[/SIZE]
[AOSPA 4.4.4 KTU84P] ParanoidAndroid 4.4+ G2
Click link here>> http://forum.xda-developers.com/showthread.php?t=2502789 <<Click link here
Please feel free to share issues, questions and offer help
It is always best to thank a ROM OP, in lieu of simply posting "Thank you".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please keep discussion focused, on the topic described in the OP
Please use this thread to assist each other and help provide useful tips and tricks you have implemented to modify and suite PA 4.4+ to your needs. Please, be polite, courteous, and helpful.
Finally, if you have a useful link, PM it to me and I can try to consolidate anything that will help others in the OP here for easy finding.
ParanoidAndroid Website and changelogs
ParanoidAndroid Github
Official TWRP Recoveries: Download here and select your model in the top right dropdown
D802 is somehow missing from their webpage. Broken link on page or some other error, here it is: Download
KK basebands/modems: thanks to @Cloudyfa for this nicely Consolidated download list.
http://www.androidfilehost.com/?w=files&flid=12880
Troubleshooting and Pulling LogCats
For anyone who isn't really comfortable pulling dmsg or last_kmsg logs from their phones needs to download and use this app: SysLog
https://play.google.com/store/apps/details?id=com.tortel.syslog
One button click and it will pull 4 logs for you and zip them all up in one small package:
dmsg
last_kmsg
logcat
Modem log
You can then get that to the dev to go through and look for errors.
Known issues for each variant:
Reported Issues:
All Variants:
- All games should be working fine, even touch based games
D800:
-
D801:
D802:
D803:
LS980 & VS980
- a few report issues with in-call volume (echo bug fixed)
Links:
Gravity Box 2.7.5
Xposed Beta for 4.4
LG Camera
For USB/OTG, try root Stickmount @Alex0901 pointed to this app from Chainfire
Screen Off App - If you're missing the knock off functionality, @bhc112 highlighted this app
Quick Remote IR Blaster - Thanks @sefnap
Signature Banner can be downloaded here:
https://db.tt/yM8N3UfQ
Bootanimation Attachments Below: (If you have any to add, send them to me and I'll include them)
- The one I made, Houston converted to a flashable zip so no need to push to system / media, just flash in recovery: Here's a video so you can see it first: http://youtu.be/DBbYnDLRauI

[Q&AT] - [AOSPA 4.4.4 KTU84P] ParanoidAndroid 4.4+ G2
FAQ's....coming soon!
I need some time (after work) to try to review the most common and recent issues/resolutions. Stay tuned, thanks for your patience!

[Q&AT] - [AOSPA 4.4.4 KTU84P] ParanoidAndroid 4.4+ G2
Judgment Passed....

The Xposed link isn't working
Link Xposed

D801: wireless display isn't working. The WiFi module seems to flip out half way through the connection process.

crazy talk said:
D801: wireless display isn't working. The WiFi module seems to flip out half way through the connection process.
Click to expand...
Click to collapse
try to collect logcat and post it in the dev thread please

D800
- Dialer screen wont tag on instantly when removing from face during call (ie dialed into Voicemail, and moved phone away to bring up dialer to delete message)

I am now getting an issue with WiFi saint "failed to connect to network". It was working fine earlier.
Sent from my LG-G2 using Tapatalk

BlackHoleSlam said:
I am now getting an issue with WiFi saint "failed to connect to network". It was working fine earlier.
Sent from my LG-G2 using Tapatalk
Click to expand...
Click to collapse
What have you done to try to fix? Have you reset your router at all? Are there any other networks you can try to connect to in order to rule out some issues? Are you still able to get Network Data if you turn off wifi? We need more info when you post these issues in order to help you.

Jank4AU said:
What have you done to try to fix? Have you reset your router at all? Are there any other networks you can try to connect to in order to rule out some issues? Are you still able to get Network Data if you turn off wifi? We need more info when you post these issues in order to help you.
Click to expand...
Click to collapse
What I am seeing is the MAC address is getting changed every reboot. I have verified this. This may be causing other issues as well with Wifi related modules.
I wonder if this would work?
http://forum.xda-developers.com/show....php?t=2347060
For mac address:
- In /persist directory create wifi directory. In the new directory create a file named .macaddr (don't miss the dot!)
Edit the file and put 12 random hex numbers in it (0-9, A-F), save.
- Set execute and read permissions for everybody on /persist/wifi directory and change owner of .macaddr to wifi:wifi and permission to 660 (read/write for owner and group and nothing else).
In command line:
Code:
chown root:root /persist/wifi
chmod 755 /persist/wifi
chown wifi:wifi /persist/wifi/.macaddr
chmod 660 /persist/wifi/.macaddr
- run /system/bin/conn_init program. Can be run in root explorer(choose Linux Script Handler when you open it), or in adb shell:
Code:
su
/system/bin/conn_init
Then reboot and check if the changes got applied in settings
I cant get my original one back but at least I have a static MAC.

Jank4AU said:
What have you done to try to fix? Have you reset your router at all? Are there any other networks you can try to connect to in order to rule out some issues? Are you still able to get Network Data if you turn off wifi? We need more info when you post these issues in order to help you.
Click to expand...
Click to collapse
I have forgot the connection reconnected to the ssid. No change has taken place WiFi seems borked now. Will try a restart. Network data is working fine.
Sent from my LG-G2 using Tapatalk

sublimejosh2000 said:
What I am seeing is the MAC address is getting changed every reboot. I have verified this. This may be causing other issues as well with Wifi related modules.
I wonder if this would work?
http://forum.xda-developers.com/show....php?t=2347060
For mac address:
- In /persist directory create wifi directory. In the new directory create a file named .macaddr (don't miss the dot!)
Edit the file and put 12 random hex numbers in it (0-9, A-F), save.
- Set execute and read permissions for everybody on /persist/wifi directory and change owner of .macaddr to wifi:wifi and permission to 660 (read/write for owner and group and nothing else).
In command line:
Code:
chown root:root /persist/wifi
chmod 755 /persist/wifi
chown wifi:wifi /persist/wifi/.macaddr
chmod 660 /persist/wifi/.macaddr
- run /system/bin/conn_init program. Can be run in root explorer(choose Linux Script Handler when you open it), or in adb shell:
Code:
su
/system/bin/conn_init
Then reboot and check if the changes got applied in settings
I cant get my original one back but at least I have a static MAC.
Click to expand...
Click to collapse
What model G2 do you have? I'll throw this in the OP until resolved

BlackHoleSlam said:
I have forgot the connection reconnected to the ssid. No change has taken place WiFi seems borked now. Will try a restart. Network data is working fine.
Sent from my LG-G2 using Tapatalk
Click to expand...
Click to collapse
Update: WiFi is back after rebooting.
Sent from my LG-G2 using Tapatalk

Jank4AU said:
What model G2 do you have? I'll throw this in the OP until resolved
Click to expand...
Click to collapse
It is D800 AT&T. I remember Nexus 4 having a similar issue. The link I posted was a fix for that. I doubt I will get my Origional MAC back, but I did backup my EFS. So, once a fix is in place, I should be able to restore.
Oh, Thank Goodness for Reserved MAC address in my router, I was able to get my old MAC from there. So, if need be, I can change it back.

D800 mute not functioning?
Hi, thanks to everyone involved in developing this custom ROM. It generally works really well.
I wondered if someone that has an AT&T G2 and has the ROM installed could verify whether the phone mute works?
It currently highlights and acts as if it works, but doesn't actually mute the microphone.
Thanks!

AT&T D800 - GPS not working either...
Couldn't get a location in Google Maps.

sublimejosh2000 said:
Couldn't get a location in Google Maps.
Click to expand...
Click to collapse
FWIW, I'm able to get one without a problem.

Since I have no desire to clog the enormous Dev thread, I will ask here:
Anyone know if there will be any plans to port this work over to CM11?

sublimejosh2000 said:
Couldn't get a location in Google Maps.
Click to expand...
Click to collapse
Mine is flawless...I had this one time on an earlier build. Flashed back to a stock nandroid, got GPS lock, then reflashed the ROM with clean install. Been perfect, accurate and fast since.

dawkpaul said:
Hi, thanks to everyone involved in developing this custom ROM. It generally works really well.
I wondered if someone that has an AT&T G2 and has the ROM installed could verify whether the phone mute works?
It currently highlights and acts as if it works, but doesn't actually mute the microphone.
Thanks!
Click to expand...
Click to collapse
Mute button works fine for me. Just cussed out a fellow employee who heard none of it and I'm still gainfully employed!

[Q&A] [ROM][29Jan][GNU/Linux] Sailfish OS (community port)

[SIZE=+2]This thread has been created
for
Questions & Answers/Troubleshooting[/SIZE][SIZE=+2]Specific to[/SIZE]
[ROM][29Jan][GNU/Linux] Sailfish OS (community port)
Click link here>> To jump to Development thread <<Click link here[/COLOR]
Please feel free to share issues, questions and offer help
It is always best to thank a ROM OP, in lieu of simply posting "Thank you".
-----------------------------------------------------------------------------------------------
Hi guys,
i've started a general Q&A thread for n4 and others. Everything related to sailfish and of course n4 can be posted here.
1. Which HW components are working?
A: take a look at the spreadsheet libhybris: https://wiki.merproject.org/wiki/Adaptations/libhybris
2. Can I run my android apps?
A: atm = no. due to licensing issues the dalvik runtime is not included in android ports. Join community efforts in this XDA thread. The jolla phone run android apps.
3. What about playing videos and music
A: new ports with gstreamer1.0 (Nexus 5) play MP3, MP4, H264 out-of-box.
Install gstreamer1.0-libav for more codecs.
For old gst0.10 ports:
MP3: install gst-fluendo-mp3-0.10.23-1.armv7hl.rpm via rpm -i fluendo
Video: Install gst streamer plugins and ultimate codec support. detailed instructions: http://forum.xda-developers.com/showpost.php?p=53552092&postcount=424
4. I'm able to install apps?
A: On Nexus 4 and Nexus 5 yes. But expect glitches because Jolla Store is going under maintenance until Tablet comes out. Known issues:
* "Essential Apps from Jolla" is not visible. Find them one by one via Seach
* Newly added apps might not show up for SFE devices
Alternatively, try Warehouse (openrepos.net):
* Navigate via your phone's browser to https://openrepos.net/content/basil/warehouse-sailfishos
* Download latest RPM
* Either run devel-su pkcon refresh in terminal, or download at least one app from Jolla Store
* Ensure Settings->System->Untrusted software is allowed
* Go to Settings->System->Transfers, click on downloaded file, and it will be installed
5. whatsapp?
A: Beware of WhatsApp temporary banning 3rd party app users. You can try WhatsUp: http://forum.xda-developers.com/showpost.php?p=60264278&postcount=137
Next Mitäkuuluu version is rumoured to be unbannable, lets all wayt
6. How to access the device?
A: Via ssh or sftp. Take a look on @Daycrawler thread: http://forum.xda-developers.com/jolla-sailfish/general/sailfish-android-devices-release-t2696409. He released the ea mail where everything is described.
7. How to install sailfish on my device (other than n4)?
A: You will be able to install when an image is available. Check "Downloadable Image" column in https://wiki.merproject.org/wiki/Adaptations/libhybris .
Porting Sailfish OS by yourself is possible via following the HADK: https://sailfishos.org/hadk
For Nokia N9: http://wiki.maemo.org/Sailfish#Sailfish_Images
9. What about multirom?
A: MultiROM is supported on Nexus 4, Nexus 5, and OnePlus One (possible Nexus 7 too): Follow up: http://forum.xda-developers.com/jolla-sailfish/general/09-06-sailfishos-multirom-how-to-set-t2869096
10. Why I have to flash so much to get sailfish on my device?
mmmmmhhhh. Answer question by yourself and try
E.g. for Nexus 4 please do all steps you'll find in: http://forum.xda-developers.com/nexus-4/development/rom-sailfish-os-community-port-t2969823 . It's necessary to have the right baseband / modem firmware. Maybe wifi won't work if you haven't.
11. How to take a screenshot?
A: Install screenshot app by lbt, from Jolla Store.
A1: This can be done on the phone via terminal and also on a remote SSH PC client.
su-devel grabscreen /home/nemo/Pictures/Test.png
If you need a times then use the 'sleep' command. e.g. below is a timer for 5 seconds.
sleep 5 && grabscreen /home/nemo/Pictures/Test.png
The picture can be accessed in the Gallery or via Filetug.
12. How to get files from/to device, because USB Mass Storage mode and SD card are not available ?
A1: ssh + scp combo (windows[putty] & linux)
This combo is a set of linux standard tools. You can connect to the phone via secure socket shell from your pc and transfer files to your phone and vice versa.
A2: sftp + filezilla (windows & linux)
You can access the files via filezilla. You can transfer files like you're doing with an ftp server.
A3: Gnome Desktop Environment
The gnome filemanager nautilus has an build in option for accessing sftp / ssh servers or devices easily.
A4: WinSCP (windows)
To connect via these methods, enable developer mode, set a new password and take a look what ip you've get. Behind the wlan symbol. Then choose one of the above methods:
username = nemo
password = the one you entered in developer mode section
[ssh]= ssh [email protected]_ip
[filezilla] = sftp://device_ip
[nautilus] = select: Connect to server (on the left side) and enter: ssh://device_ip
13. How can I use the Backup app when there's no (working) SD Card?
A: Launch Settings->System->Backup to save all the settings you want to preserve
Perform
Code:
tar cf $HOME/backup.tar -C $HOME .vault
scp backup.tar onto your PC (other ways of how pull files, see FAQ #12 above)
Install new Sailfish OS.zip, put the tarball back onto device (say at $HOME), then perform:
HTML:
cd $HOME && tar xpf backup.tar
Go to Settings->System->Backup and restore your content from a chosen backup
14. How can I provide another radio.img only for Sailfish OS?
Put radio.img onto Sailfish OS rootfs somewhere safe.
Edit /lib/systemd/system/firmware.mount and replace "What=/dev/mmcblk0p1" with "What=/path/to/firmware.img"
Be careful with that and always do backup (i.e. comment the first What out )
15. How can I skip tutorial?
On first screen, tap on corners in sequence: top-left, top-right, bottom-right, bottom-left
16. How can I mount android's virual sdcard partition (Nexus4,5) with all my goodies?
Try:
Code:
devel-su
mkdir /android
mount /dev/mmcblk0p28 /android
# User data is then available in /android/media/0/
# You can update your fstab file by adding the following line at the end:
/dev/mmcblk0p28 /android ext4 rw,relatime,data 0 0
# And for media to be tracked:
ln -s /android/media/0 /home/nemo/android_sdcard
17. Filemanager?
Install File Browser by Kari from Jolla Store.
For root access add on https://openrepos.net/content/schturman/startasroot-file-browser (See question #4 on how to access openrepos via Warehouse app)
This thread should be a collection for sailfish on devices and I will update frequently if news or tipps & tricks are available.
-----------------------------------------------------------------------------------------------
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please keep discussion focused, on the topic described in the OP

Arabic Keyboard
Is there a way to enable Arabic keyboard layout in SailfishOS?

Upgrade Sailfish
Today I am upgraded my Nexus 4 to Sailfish OS 1.1.2.16 and I don't noticed any (new) bugs. I done upgrade on fresh install of Sailfish OS 1.1.1.27 from that thread.
Below I will write procedures to successfull upgrade Sailfish from 1.1.1.27 to 1.1.2.16.
[Procedure to add locks - without that camera will not work after upgrade]
[[email protected] ~]$ devel-su zypper al jolla-camera jolla-camera-settings sensorfw-qt5 qt5-qtsensors-plugin-sensorfw
[Fix problem with adaptation0 after upgrade]
[[email protected] ~]$ devel-su zypper al ssu ssu-network-proxy-plugin ssu-vendor-data-jolla
[Change release version to 1.1.2.16]
[[email protected] ~]$ devel-su ssu re 1.1.2.16
[Refresh package list and install updates]
[[email protected] ~]$ devel-su zypper refresh
[[email protected] ~]$ devel-su zypper update
[Accept updates and wait. After update restart your phone]
[Your Nexus 4 should now run Sailfish 1.1.2.16!]

Niyoru said:
Today I am upgraded my Nexus 4 to Sailfish OS 1.1.2.16 and I don't noticed any (new) bugs. I done upgrade on fresh install of Sailfish OS 1.1.1.27 from that thread.
Below I will write procedures to successfull upgrade Sailfish from 1.1.1.27 to 1.1.2.16.
[Procedure to add locks - without that camera will not work after upgrade]
[[email protected] ~]$ devel-su zypper al qt5-qtmultimedia-plugin-mediaservice-gstcamerabin jolla-camera jolla-camera-settings nemo-qtmultimedia-plugins-gstvideotexturebackend sensorfw-qt5
[Change release version to 1.1.2.16]
[[email protected] ~]$ devel-su ssu re 1.1.2.16
[Refresh package list and install updates]
[[email protected] ~]$ devel-su zypper refresh
[[email protected] ~]$ devel-su zypper update
[Accept updates and wait. After update restart your phone]
[Disable repository adaptation0]
[[email protected] ~]$ devel-su ssu dr adaptation0
[Refreshing package list]
[[email protected] ~]$ devel-su zypper refresh
[Your Nexus 4 should now run Sailfish 1.1.2.16!]
Click to expand...
Click to collapse
Thank you for your instruction.. I just have one problem...
I get the below error message when trying to refresh the repositories. Even after doing "zypper clean -a".
"Retrieving repository 'adaptation0' metadata ---------------------------------------------------------------------------------[-]
Timeout exceeded when accessing 'http ://repo.merproject.org/ obs/sailfishos: /testing: /hw:/mako/sailfish_latest_armv7hl/repodata /repomd.xml'."
I'm running sailfish OS with Multirom.
I hope you can help me.
Kind regards,
Edit: I know what the problem is. I have to authenticate but I don't have any credentials. Is there a way how I can register for that repository? Many thanks

That repository probably don't exist for 1.1.2.16.
Try use devel-su ssu rr adaptation0 and devel-su ssu dr adaptation0.
I will try to stop the repo adaptation0 on 1.1.1.27. If I do this I will write here how to fix this repository.
Edit. adaptation0 is a repository for packages like droid-hal, what comunicate with hardware. Now you have installed these packages and Sailfish will work without this repository avaible. However I will try to fix it.
Thanks for feedback.

Niyoru said:
That repository probably don't exist for 1.1.2.16.
Try use devel-su ssu rr adaptation0 and devel-su ssu dr adaptation0.
I will try to stop the repo adaptation0 on 1.1.1.27. If I do this I will write here how to fix this repository.
Edit. adaptation0 is a repository for packages like droid-hal, what comunicate with hardware. Now you have installed these packages and Sailfish will work without this repository avaible. However I will try to fix it.
Thanks for feedback.
Click to expand...
Click to collapse
No, Thank YOU!
I did the update as you proposed, but the UI is not the same as the sailfish 2.0 Hammerhead version. It's probably because of the missing adaptation0 repo and the fact the official images aren't out there, yet.
Thank you for looking at the problem and your time! Let me know if it works

btrdossantos said:
No, Thank YOU!
I did the update as you proposed, but the UI is not the same as the sailfish 2.0 Hammerhead version. It's probably because of the missing adaptation0 repo and the fact the official images aren't out there, yet.
Thank you for looking at the problem and your time! Let me know if it works
Click to expand...
Click to collapse
This will not look like Sailfish 2.0, becouse this is not Sailfish 2.0. This is Sailfish 1.1.2.16, you can read more about that release on Sailfish Website. (Sorry for no links, but I can't put any into post, becouse I have less than 10 posts :c)

sailfish-weather is not found in jolla app store.
When i can get rpm package with weather?)

dimon2242 said:
sailfish-weather is not found in jolla app store.
When i can get rpm package with weather?)
Click to expand...
Click to collapse
If you upgraded Sailfish to 1.1.2.16, you can use command "devel-su zypper install sailfish-weather".
This work for me

Niyoru said:
If you upgraded your Sailfish to 1.1.2.16, you can use just "devel-su zypper install sailfish-weather".
This work for me
Click to expand...
Click to collapse
What is about mp3 codec?
After installing flurence and bad-extras i can't play music(

dimon2242 said:
What is about mp3 codec?
After installing flurence and bad-extras i can't play music(
Click to expand...
Click to collapse
In my phone this one work well: d-h.st/nkS8

Hi all,
we're working on the next official community release. Great you're figured out how to update. But be aware. If a bigger patchset is applied to the kernel this method won't work. But maybe one of you can help us out with a little information if you have upgraded the way from first post. If you open the messages app and looking at the background what do you see? Are there little quarters or or little diamonds?
Thx in advance!
ahoi

carepack said:
Hi all,
we're working on the next official community release. Great you're figured out how to update. But be aware. If a bigger patchset is applied to the kernel this method won't work. But maybe one of you can help us out with a little information if you have upgraded the way from first post. If you open the messages app and looking at the background what do you see? Are there little quarters or or little diamonds?
Thx in advance!
ahoi
Click to expand...
Click to collapse
Definitely little quarters. However I think screenshot can say everythink and I attach one.
Thank you for your interest in this update solution.
I hope that you will be able to make stable build for Nexus 4

Browser is closed if i play online music or youtube video!
Hope, what this will be fixed in next update!)

Niyoru said:
Definitely little quarters. However I think screenshot can say everythink and I attach one.
Thank you for your interest in this update solution.
I hope that you will be able to make stable build for Nexus 4
Click to expand...
Click to collapse
We're doin' our best :fingers-crossed:! Hope you enjoy the beloved sailfishos and thank you for sharing the information about quarters or not!
ahoi

Bug - Untrusted software installation
I am now running on v1.1.2.16 based on the tutorial provided in the thread (thanks Niyoru) and would like to report a bug.
I went into Setting -> System -> Untrusted software
and enabled "Allow untrusted software" option in there. However, I can't install any .rpm files. When I go back into settings, the setting is disabled. Not sure if this is caused by the upgrade or is also a problem in v1.1.1.27 as well in the Nexus 4 port.
The workaround was to go into terminal, do a devel-su and typing in:
zypper in package.rpm
Hope this helps...
PS. Looking forward to this build having the "Sailfish OS Updates" working instead of a manual upgrade process. Happy sailing! :fingers-crossed:

Installing sailfish via multirom with over kitkat primary rom
Hi. ive read all the posts i can find. Any pointers
Running up to date multirom on nexus 4 v31
Kitkat primary (beanstalk)
Lollipop secondary (Tamasek)
Downgraded kitkat radio from .98 to .84 to allow me to install sailfish
Downloaded Cm 10.1.3 and sailfish 1.1.2.16 beta 4
Installed both using sailfish "add rom" multirom option
All i get is bootloop after choosing sailfish from multirom list. Get to "google" screen and then it reboots back to multirom selection , Cant get past Google
Checked md5s, tried 4 or 5 times now
reread threads etc
Am i missing anything obvious..??
Any suggestions?

Updated to v1.1.4.28 and all seems fine thus far...
Looks like latest update is screen resolution aware.
Sent from my Note 2 using Tapatalk...

mikerog said:
Hi. ive read all the posts i can find. Any pointers
Running up to date multirom on nexus 4 v31
Kitkat primary (beanstalk)
Lollipop secondary (Tamasek)
Downgraded kitkat radio from .98 to .84 to allow me to install sailfish
Downloaded Cm 10.1.3 and sailfish 1.1.2.16 beta 4
Installed both using sailfish "add rom" multirom option
All i get is bootloop after choosing sailfish from multirom list. Get to "google" screen and then it reboots back to multirom selection , Cant get past Google
Checked md5s, tried 4 or 5 times now
reread threads etc
Am i missing anything obvious..??
Any suggestions?
Click to expand...
Click to collapse
You got to use cm10.1.3 as primary ROM, too.
ajack2001my said:
Updated to v1.1.4.28 and all seems and fine thus far...
Looks like latest update is screen resolution aware.
Click to expand...
Click to collapse
Did you update via OTA? Does it work now?
Hello, I'm buying a N4 today and am happy to join the community. I love Sailfish OS.
Regards

keenofhiphop said:
Did you update via OTA? Does it work now?
Hello, I'm buying a N4 today and am happy to join the community. I love Sailfish OS.
Regards
Click to expand...
Click to collapse
Yes, I update OTA using a combination of ssu and zypper commands... I guess it also helps that my account allows me to use early release software.

[7.1.2][UNOFFICIAL] LineageOS 14.1 for Lenovo P2

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 6 (marshmallow), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
What's working :
Boots
Touch
RIL [Calls, Mobile Data]
Wi-Fi
Wi-Fi Hotspot
Bluetooth
Camera
Audio
Sensors
Fingerprint
Flash
GPS
NFC
Known issues:
VoLTE doesn't work.
LED.Note: You can use LED with this awesome method: https://forum.xda-developers.com/lenovo-p2/themes/lenovo-p2-rooted-custom-led-t3589859
This is the one of the first builds for p2a42, so minor bugs are expected.Please report them if any.
Instructions :
Flash Twrp :- LINK
Download the latest build and GApps
Reboot to recovery
Flash the latest build and GApps
Reboot
Downloads :
Latest build [19/06/2017]: https://mega.nz/#!KgcS1boY!f1veK_D-kw_8WYDMD9Id0qytacZuHVN3xvQzB7t0SP0
Google Apps: http://opengapps.org/
Credits :
One Team Forum
XDA:Rom Information
LineageOS 14.1,p2a42, ROM for the Lenovo P2
Contributors
wzedlare
ROM OS Version: 7.1.x Nougat
Version Information
Status: Stable
Created 2017-03-18
Last Updated 2017-06-19

#rezerved for me

How to install Root for Apps on Android Nougat Custom Rom
Download and transfer the Lineage SU addon zip file from the download link above to your device’s storage.
Boot your device into TWRP recovery.
Tap on Install and select the Lineage SU addon zip file that you transferred to your device in Step 1.
After selecting the .zip file, do Swipe to Confirm Flash on the bottom of screen to begin the flashing process.
Once Lineage SU addon is flashed, you’ll get Reboot System option, select it.
How to Enable Root for Apps on Lineage OS
Once you’ve installed the Lineage SU addon zip, do the following to enable root for Apps on Lineage OS:
Enable Developer options: Go to Settings » About phone » Tap seven times on Build number.
Go back to Settings main menu and open Developer options from there.
Look for Root access setting, and set it to Apps and ADB or Apps only, as per your need.
That’s all. Your Android device running on Lineage OS should have full root access for apps now.
If you ever need to disable root access, just go to Settings » Developer options » Root access and select the Disabled option from there.
Download;
addonsu-arm64-signed.zip

Great job, no idea how you build new kernel 3.18.31 for lineage14.1

Thank You!

i want to Root LOS 14.1
is it the same way?? or should i do anything more??? !!
i am thinking of SystemRoot..
please give your suggestions ..

nandakis4 said:
i want to Root LOS 14.1
is it the same way?? or should i do anything more??? !!
i am thinking of SystemRoot..
please give your suggestions ..
Click to expand...
Click to collapse
LineageOs AdeenSu
Download And Flashing
Developer Setting>Root

@wzedlare kindly you fix framework folder, it look so ugly with boot oats and boot arts, i have file folder framework to manage throw thems, but make home button not wake up the screen light when it pressed, i hope it will be fix for next release

Thanks! Very good job. It may be crazy but I think I stay with Android 6, because I love the led notifications.
But maybe I will flash it, because who give a F?
Do you need to format as ext4 or other filesystem?...
Will my SD work, it's exfat??
---------- Post added at 13:27 ---------- Previous post was at 13:16 ----------
hendibudi said:
@wzedlare kindly you fix framework folder, it look so ugly with boot oats and boot arts, i have file folder framework to manage throw thems, but make home button not wake up the screen light when it pressed, i hope it will be fix for next release
Click to expand...
Click to collapse
Why not fix it yourself?

hendibudi said:
@wzedlare kindly you fix framework folder, it look so ugly with boot oats and boot arts, i have file folder framework to manage throw thems, but make home button not wake up the screen light when it pressed, i hope it will be fix for next release
Click to expand...
Click to collapse
They(boot.oat) are being generated automatically if you compile any custom rom.Home button wakes up the device, I won't disable that feature.It is useful for everyone.
ilmervanhattem said:
Thanks! Very good job. It may be crazy but I think I stay with Android 6, because I love the led notifications.
But maybe I will flash it, because who give a F?
Do you need to format as ext4 or other filesystem?...
Will my SD work, it's exfat??
---------- Post added at 13:27 ---------- Previous post was at 13:16 ----------
Why not fix it yourself?
Click to expand...
Click to collapse
You don't have to format anything.Just make your wipes and flash it.

ilmervanhattem said:
Thanks! Very good job. It may be crazy but I think I stay with Android 6, because I love the led notifications.
But maybe I will flash it, because who give a F?
Do you need to format as ext4 or other filesystem?...
Will my SD work, it's exfat??
---------- Post added at 13:27 ---------- Previous post was at 13:16 ----------
Why not fix it yourself?
Click to expand...
Click to collapse
I am sorry, i just junior member on xda, i didn't mean that, i just want to give little contribution to revive our community user p2 experience

WiFi is not working here...
When I turn on WiFi it turns off instantly...
Fawk
I've used the 'super' version of gapps for 7.1 (64bits) btw. Also tried it with TWRP 3.0.2.0 and the aroma installer of gapps, same WiFi error.

Hi there, i am thinking of buying this device for my gf because she needs something with a ****load of battery power. So this device seems the obvious choice. But i have a question:
i noticd that on every rom there is no led and no fingerprint. Is this something that will be added in the future or is it not possible due to unavailabe firmwares?
Kind regards

DDQW said:
Hi there, i am thinking of buying this device for my gf because she needs something with a ****load of battery power. So this device seems the obvious choice. But i have a question:
i noticd that on every rom there is no led and no fingerprint. Is this something that will be added in the future or is it not possible due to unavailabe firmwares?
Kind regards
Click to expand...
Click to collapse
I couldn't fix them, that's my fault.It is not caused by firmware or something.I don't know what will happen in the future.
ilmervanhattem said:
WiFi is not working here...
When I turn on WiFi it turns off instantly...
Fawk
I've used the 'super' version of gapps for 7.1 (64bits) btw.
Click to expand...
Click to collapse
Flash stock rom and use it for ten minutes, wipe data,system,cache,dalvik cache (don't wipe your internal storage, wiping it causes bugs.), then flash the rom.

wzedlare said:
Flash stock rom and use it for ten minutes, wipe data,system,cache,dalvik cache (don't wipe your internal storage, wiping it causes bugs.), then flash the rom.
Click to expand...
Click to collapse
OK my friend.
Got some error and passcode error when restoring. Will try some things and talk to you later.
UPDATE: wifi is working but have to root.
UPDATE: Rooted with version 2.79
UPDATE: Now restoring 484 apps with Titanium Backup
UPDATE: ROM is working smooth af, for how much I experienced by now

i was wondering why i couldnt get gapps to install , then realised i was trying to install the wrong version lol

The Mero said:
i was wondering why i couldnt get gapps to install , then realised i was trying to install the wrong version lol
Click to expand...
Click to collapse
7.1 > arm64 > choose whatever you want, pico is the smaller zip.

cpu-z is saying governor is stuck on performance .. constantly running at 2016mhz on all cores .
Is it possible to change it to dynamic ?

The Mero said:
cpu-z is saying governor is stuck on performance .. constantly running at 2016mhz on all cores .
Is it possible to change it to dynamic ?
Click to expand...
Click to collapse
Use a kernel editor?

which one would be safe / recommend to use ilmervanhattem ?
I wouldnt have a clue where to start ,

[ROM] Flyme OS 6 (G) Global Stable for Chinese Pro 6 Plus devices

How To Install Flyme OS 6.1.0.0G Global Stable on Chinese Pro 6 Plus devices
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is a Guide to install the Global ROM Flyme OS 6Global on the Meizu Pro 6 Plus Chinese version.
Note: This is also a way to install Any custom ROM made in the future. If someone wanna Customize the ROM( Integrate Xposed and other stuff) feell free to do it.
What does this mean:
Meizu released two versions of the Pro 6 Plus, a chineese version (A) for china and an International version (G) for the devices sold in other countries (International). If you bought your Pro 6 plus from official meizu store on your country, it will come with the G version, but if you bought it from Aliexpress or any other Chinese store, you will buy a Chinese version, some seller may send you the international version if you are lucky but the majoritynot.
Global / International version:
No bloatware, chinese apps..
Multilanguage ( all languages available)
Stock apps optimized for International use (Weather....)
seems to be smoother and faster than the chinese version.

Disclaimer
*** As always - Read everything carefully and Flash on our own risk! ***
I can and will not take any responsibility for bricked phones or lost data.What do we need:
Rooted Device
FlashFire app from playstore
Flyme 6.1.0.0G _Global_Stable_Pro 6 Plus for Flashfire

Instructions:
Its recomnended to back up your data (Titanium backup, your fotos etc)in case of disaster.
Update to a newer version:
Copy the new version to Internal storage
Open Flashfire, click on the + button and choose Flash Zip / OTA
Select the Downloaded ROM from the file explorer and select Mount system read write.
Now you will see a screen with all the actions that will be done, select the action called Reboot and un-thick the option Preserve recovery, leave Normal selected.
Finally click on FLASH and wait until the process ends.
Enjoy...
Note: In case of any problems and you want a clean installation, add the wipe action from the + button before flashing. But it should not be needed.
Note: it seems to be a problem with supersu if you don't wipe data before update. so to avoid problems, you should wipe before flash.
If you want to keep your apps and data, you should make a data (data partition only) backup from flashfire before updating. then wipe and update, follow instructions to root and to have super su. After that you can use flshfire to restore data backup (only data partition) .
also you can use kingroot but its not compatible with flashfire.
If you already updated, you can use titanium backup(give root permision from system root in settings, security root permissions)make a backup of your apps and then follow the guide below How to go back to stock chinese ROM in case of disaster, after that follow the instruction of new installation and when you have the that done, you can rstore your apps with titanium backup.
[/LIST]

First Time Installation:
Root:
Go to Meizu page and create and account. Enter a valid email as its needed to activate the account. if you already have an account, just skip this step.
Now go to Settings on your device and Select Meizu account, Log in with your new created account.
Go back and select Fingerprint & security , then select Root permission, scroll down and confirm. The device will reboot. Now its rooted but i recommend installing supersu because the built int root some times has failed for me.
Install SuperSu from playstore, open it and select Update su binary, choose Normal. wait until it finishes and reboot.
Now you have Root
Note: if you dont have Google Playstore, open meizu app store and search for supersu.
Install ROM:
Root your device
Install Flashfire from Playstore
Download This modified Flyme 6.1.0.0G _Global_Stable_Pro 6 Plus for Flashfire
[*]Copy the downloaded ROM to Internal storage
[*]Open Flashfire, give root permissions and click on the + button,
[*]Select Wipe and then ok
[*]Click again on the + button and choose Flash Zip / OTA
[*]Select the Downloaded ROM from the file explorer and select Mount system read write. See these screens for more information:
[*]Now you will see a screen with all the actions that will be done, select the action called Reboot and unthick the option Preserve recovery, leave Normal selected.
[*]Finally click on FLASH and wait until the process ends.
[*]Enjoy...

Turn off the device （hold power button until it turns off.
Hold Volume + button and power button at the same time until the phone vibrates. it will enter recovery mode.
Connect your device to your PC by usb, you will have access to a folder named Recovery. Copy the update.zip to this folder and wait for it to finish.
Go back to the device and select the options Upgrade System and Clear data.
Hit Start and wait until it finishes.

Older Versions:
Flyme OS 6.7.4.11_beta_Global_Pro 6 Plus for Flashfire

Thanks for this tutorial! It was very detailed and easy to follow.
In the future when I want to perform an update, do I need to go through FlashFire in order for it to work correctly on a Chinese version of the device? Also, where do you download the "G" versions of the beta firmware? I know their next release is a stable version and I know it comes out after the A version; just wondering where you go to download it. Cheers!

ShaolinMilk said:
Thanks for this tutorial! It was very detailed and easy to follow.
In the future when I want to perform an update, do I need to go through FlashFire in order for it to work correctly on a Chinese version of the device? Also, where do you download the "G" versions of the beta firmware? I know their next release is a stable version and I know it comes out after the A version; just wondering where you go to download it. Cheers!
Click to expand...
Click to collapse
For future update you can download the stable from http://www.flymeos.com/firmwarelist?modelId=46&type=1. Or the betas from flyme forum. You will have to edit the installation script to be able to flash through flashfire and don't get error and avoid firmware problems. Anyway i will upload the future updates modified for flashfire.

bihariel said:
For future update you can download the stable from http://www.flymeos.com/firmwarelist?modelId=46&type=1. Or the betas from flyme forum. You will have to edit the installation script to be able to flash through flashfire and don't get error and avoid firmware problems. Anyway i will upload the future updates modified for flashfire.
Click to expand...
Click to collapse
Thanks!!! I tried looking through the zip file to see what you changed, but didn't know which file to go into. I assume it's not as easy as opening up a file in notepad and changing some data on there.

ShaolinMilk said:
Thanks!!! I tried looking through the zip file to see what you changed, but didn't know which file to go into. I assume it's not as easy as opening up a file in notepad and changing some data on there.
Click to expand...
Click to collapse
Its not hard to do but yes, i you dont know what are you doing is dangerous. Dont worry i will upload future updates.

bihariel said:
Its not hard to do but yes, i you dont know what are you doing is dangerous. Dont worry i will upload future updates.
Click to expand...
Click to collapse
Thanks dude! Looking forward to it.

im surprised at how small the response to this phone is....just stumbled upon it while looking for a new device.
this is rather off-topic but this seems to be the most active thread

thanks for that.
i have question,i can flash the Flyme 5.2.7.0G by this method?

@bihariel Hey I have a question for you. Have you ever experienced a sudden change in battery life out of nowhere? When I first installed this firmware, the battery was perfect. All of a sudden after charging my phone, the battery is draining at an unprecedented rate especially on standby. I charged the phone to 100%, disabled all notification/wifi/cellular network and left it on overnight to activate the battery calibration. The problem still exists however. It's draining about 1% every 2 minutes on standby which is ridiculous.
I'm just wondering if you ever encountered this issue before.
Sent from my PRO 6 Plus using XDA-Developers Legacy app

mr.mgmg said:
thanks for that.
i have question,i can flash the Flyme 5.2.7.0G by this method?
Click to expand...
Click to collapse
You can but you have to modify the script to avoid firmware files and recovery.img to be flashed, which would end in an installation abort,

ShaolinMilk said:
@bihariel Hey I have a question for you. Have you ever experienced a sudden change in battery life out of nowhere? When I first installed this firmware, the battery was perfect. All of a sudden after charging my phone, the battery is draining at an unprecedented rate especially on standby. I charged the phone to 100%, disabled all notification/wifi/cellular network and left it on overnight to activate the battery calibration. The problem still exists however. It's draining about 1% every 2 minutes on standby which is ridiculous.
I'm just wondering if you ever encountered this issue before.
Sent from my PRO 6 Plus using XDA-Developers Legacy app
Click to expand...
Click to collapse
Not really, the battery is surprising me on this ROM. Maybe you sould use a battery monitoring app and see whats draining it. If not, do a factory reset and see if it still prsists.

bihariel said:
You can but you have to modify the script to avoid firmware files and recovery.img to be flashed, which would end in an installation abort,
Click to expand...
Click to collapse
so,how we can do that?
i think the 6.7.4.11_beta_Global no stable yet
u can edit the Flyme 5.2.7.0G?

bihariel said:
How To Install Flyme OS 6.7.4.11 Global on Chinese Pro 6 Plus
This is a Guide to install the Global ROM Flyme OS 6.7.4.11 on the Meizu Pro 6 Plus Chinese version.
Note: This is also a way to install Any custom ROM made in the future. If someone wanna Customize the ROM( Integrate Xposed and other stuff) feell free to do it.
What does this mean:
Meizu released two versions of the Pro 6 Plus, a chineese version (A) for china and an International version (G) for the devices sold in other countries (International). If you bought your Pro 6 plus from official meizu store on your country, it will come with the G version, but if you bought it from Aliexpress or any other Chinese store, you will buy a Chinese version, some seller may send you the international version if you are lucky but the majoritynot.
Global / International version:
No bloatware, chinese apps..
Multilanguage ( all languages available)
Stock apps optimized for International use (Weather....)
seems to be smoother and faster than the chinese version.

Instructions:
Its recomnended to back up your data (Titanium backup, your fotos etc)in case of disaster.
Root:
Go to Meizu page and create and account. Enter a valid email as its needed to activate the account. if you already have an account, just skip this step.
Now go to Settings on your device and Select Meizu account, Log in with your new created account.
Go back and select Fingerprint & security , then select Root permission, scroll down and confirm. The device will reboot. Now its rooted but i recommend installing supersu because the built int root some times has failed for me.
Install SuperSu from playstore, open it and select Update su binary, choose Normal. wait until it finishes and reboot.
Now you have Root
Note: if you dont have Google Playstore, open meizu app store and search for supersu.
Install ROM:
Root your device
Install Flashfire from Playstore
Download This modified Flyme OS 6.7.4.11_beta_Global_Pro 6 Plus
Copy the downloaded ROM to Internal storage
Open Flashfire, give root permissions and click on the + button,
Select Wipe and then ok
Click again on the + button and choose Flash Zip / OTA
Select the Downloaded ROM from the file explorer and select Mount system read write. See these screens for more information:
Now you will see a screen with all the actions that will be done, select the action called Reboot and unthick the option Preserve recovery, leave Normal selected.
Finally click on FLASH and wait until the process ends.
Enjoy...

Optional:
You can Install gapps from flashfire along with the rom, just select Flash zip/ota and select Gapps zip, this way it will be installed after rom. Or you can use Google Installer which you can find in meizu appstore after reboot.
Note: For future updates, do not update the device from the Updates app included as it will donload the Gobal version of Flyme but it will fail because your device is still a chinese version.
How to go back to stock chinese ROM in case of disaster:
Download the latest version of chinese Flyme from: http://www.flyme.cn/firmwarelist-101.html#3
Turn off the device （hold power button until it turns off.
Hold Volume + button and power button at the same time until the phone vibrates. it will enter recovery mode.
Connect your device to your PC by usb, you will have access to a folder named Recovery. Copy the update.zip to this folder and wait for it to finish.
Go back to the device and select the options Upgrade System and Clear data.
Hit Start and wait until it finishes.

Click to expand...
Click to collapse
Hello everyone, thanks a lot bihariel for this guide.
I have successfully installed the beta with flashfire and it's all ok!
Some people say flashfy is not a very safe method, what do you think? I'm not an expert.
However, I did not go to the flymex account synchronization, now I've installed the closed beta apps yesterday and it works perfectly well!
We wait for the stable then!
Can you explain how you modified the update for the future? Thanks so much.
Are Alternative Methods to Flashfire? Type ADB?
In Italy a seller on his blog posted this guide, but I could not install it:
"The tutorial for installing firmware G in the Asian Meizu Pro 6 Plus smartphone is really very simple and does not require solid modding basics, you just have to be careful about installing ADB drivers correctly.
Load the battery completely before you begin the procedure and save all your important data
On your PC or on a Cloud as you will need to make the full factory reset.
Prerequisites Preinstalling Firmware G in Meizu Pro 6 Plus:
1-Smartphone fully charged
2-Any antivirus and / or firewalls disabled
3-Driver ADB properly installed, restart your PC after installation!
4-Enabled Root permissions through Flyme account (Fingerprint and Security Menu)
5-USB Debug Mode Enabled in Developer Options (Accessibility Menu)
G Firmware Installation in Meizu Pro 6 Plus:
Decompress the Meizu_Pro6plus_Flyme 5.2.7.0G.zip archive and copy it to the root folder
Of Meizu Pro 6 Plus the file system-i.img
Decompress the archive adb_tool.zip and in the folder obtained we select the file
Cmd.exe to open the command window
Write in the command window:
Adb shell
We give Send and permission to ADB through the pop-up that will appear on the Meizu Pro 6 Plus display
We will read in the shell @ Pro6Plus command window
WARNING: If the pop-up display does not appear, ADB drivers have not been installed correctly!
Write in the command window:
su
We give Send and permission of ADB SHELL root permissions through
The pop-up that will appear on the Meizu Pro 6 Plus display
We will read in the command window the symbol #
WARNING: If the pop-up display does not appear, root permissions are disabled!
Write in the command window:
Dd if = / sdcard / system-i.img of / dev / block / platform / 155a0000.ufs / by-name / system
We give Enter, we will see the cursor blink, we do not touch anything until the flash procedure
The system will not be completed and the screenshot message below will appear
Meizu pro 6 plus 01
Disconnect the usb cable from the Meizu Pro 6 Plus and restart it by holding down the button
Power for a few seconds, the startup process will take a few minutes, do not alarm and we start booting.
When the terminal is started we go in
Settings> About phone> Storage> Factory data reset>
We see Factory reset and Format internal storage>
Select START RESET"
I put into google translate, if you want the original in italian language let me know.

mr.mgmg said:
so,how we can do that?
i think the 6.7.4.11_beta_Global no stable yet
u can edit the Flyme 5.2.7.0G?
Click to expand...
Click to collapse
I read in some chinese forum that we cant downgrade but...
Download the ROM 5.2.7.0G, open the zip and editthis file \META-INF\com\google\android\updater-script
You can use this picture as a guide, delete the red lines:

Tony72 said:
Hello everyone, thanks a lot bihariel for this guide.
I have successfully installed the beta with flashfire and it's all ok!
Some people say flashfy is not a very safe method, what do you think? I'm not an expert.
However, I did not go to the flymex account synchronization, now I've installed the closed beta apps yesterday and it works perfectly well!
We wait for the stable then!
Can you explain how you modified the update for the future? Thanks so much.
Are Alternative Methods to Flashfire? Type ADB?
In Italy a seller on his blog posted this guide, but I could not install it:
"The tutorial for installing firmware G in the Asian Meizu Pro 6 Plus smartphone is really very simple and does not require solid modding basics, you just have to be careful about installing ADB drivers correctly.
Load the battery completely before you begin the procedure and save all your important data
On your PC or on a Cloud as you will need to make the full factory reset.
Prerequisites Preinstalling Firmware G in Meizu Pro 6 Plus:
1-Smartphone fully charged
2-Any antivirus and / or firewalls disabled
3-Driver ADB properly installed, restart your PC after installation!
4-Enabled Root permissions through Flyme account (Fingerprint and Security Menu)
5-USB Debug Mode Enabled in Developer Options (Accessibility Menu)
G Firmware Installation in Meizu Pro 6 Plus:
Decompress the Meizu_Pro6plus_Flyme 5.2.7.0G.zip archive and copy it to the root folder
Of Meizu Pro 6 Plus the file system-i.img
Decompress the archive adb_tool.zip and in the folder obtained we select the file
Cmd.exe to open the command window
Write in the command window:
Adb shell
We give Send and permission to ADB through the pop-up that will appear on the Meizu Pro 6 Plus display
We will read in the shell @ Pro6Plus command window
WARNING: If the pop-up display does not appear, ADB drivers have not been installed correctly!
Write in the command window:
su
We give Send and permission of ADB SHELL root permissions through
The pop-up that will appear on the Meizu Pro 6 Plus display
We will read in the command window the symbol #
WARNING: If the pop-up display does not appear, root permissions are disabled!
Write in the command window:
Dd if = / sdcard / system-i.img of / dev / block / platform / 155a0000.ufs / by-name / system
We give Enter, we will see the cursor blink, we do not touch anything until the flash procedure
The system will not be completed and the screenshot message below will appear
Meizu pro 6 plus 01
Disconnect the usb cable from the Meizu Pro 6 Plus and restart it by holding down the button
Power for a few seconds, the startup process will take a few minutes, do not alarm and we start booting.
When the terminal is started we go in
Settings> About phone> Storage> Factory data reset>
We see Factory reset and Format internal storage>
Select START RESET"
I put into google translate, if you want the original in italian language let me know.
Click to expand...
Click to collapse
I can tell you that for now the safest method is flashfire because it install the ROM in same way that the Recovery does, that is: it wipes the system partition and installs the ROM with correct permissions.
The method you mention is more risky( to get a bootloop) because it overwrites the ROM files directly over the System partition with the OS still running on phone. This drives into a system hang freeze. of course you have to turn it of by holding power button until it restarts. Then you have to go recovery and do a factory reset if you get bootloop.
I tried this method before Flasfire but it gave me bootloop so then i used Flashfire because it do the same job that Recovery does.
About the modifications, its really simple. Just open \META-INF\com\google\androidupdater-script and delete all the lines in red in this picture (these lines check if your phone is Chinese version or global and update the firmware files.)
Also you can delete the files related to those lines just for safety (boot.img, recovery.img, logo.bin, ldfw, bootloader..)

bihariel said:
I can tell you that for now the safest method is flashfire because it install the ROM in same way that the Recovery does, that is: it wipes the system partition and installs the ROM with correct permissions.
The method you mention is more risky( to get a bootloop) because it overwrites the ROM files directly over the System partition with the OS still running on phone. This drives into a system hang freeze. of course you have to turn it of by holding power button until it restarts. Then you have to go recovery and do a factory reset if you get bootloop.
I tried this method before Flasfire but it gave me bootloop so then i used Flashfire because it do the same job that Recovery does.
About the modifications, its really simple. Just open \META-INF\com\google\androidupdater-script and delete all the lines in red in this picture (these lines check if your phone is Chinese version or global and update the firmware files.)
Also you can delete the files related to those lines just for safety (boot.img, recovery.img, logo.bin, ldfw, bootloader..)
Click to expand...
Click to collapse
Thanks a lot!, I'll read all as soon I could

BE Careful
Removed

bihariel said:
I read in some chinese forum that we cant downgrade but...
Download the ROM 5.2.7.0G, open the zip and editthis file \META-INF\com\google\android\updater-script
You can use this picture as a guide, delete the red lines:
Click to expand...
Click to collapse
i flashed the 6.7.4.11 but i have problem when i open the front camrera and close the camrea not open again
now i want back to the 5.2.7.0G but when i want edit the script is Different about your picture.
u can edit the just script and upload and then i will add to zip

mr.mgmg said:
i flashed the 6.7.4.11 but i have problem when i open the front camrera and close the camrea not open again
now i want back to the 5.2.7.0G but when i want edit the script is Different about your picture.
u can edit the just script and upload and then i will add to zip
Click to expand...
Click to collapse
Salam,
The camera bug is weird, i don't have that bug, i open the camera ( front and back) many times and it works perfectly, maybe you changed something in camera setting ( erasing camera app data should help)
Anyway, the script is exactly the same as mine, its just you are using and editor with Arabic orientation.
Just use the app Notepad++( google it) and open it in English lang.
If not, just upload the script for me and i will edit it.

bihariel said:
Salam,
The camera bug is weird, i don't have that bug, i open the camera ( front and back) many times and it works perfectly, maybe you changed something in camera setting ( erasing camera app data should help)
Anyway, the script is exactly the same as mine, its just you are using and editor with Arabic orientation.
Just use the app Notepad++( google it) and open it in English lang.
If not, just upload the script for me and i will edit it.
Click to expand...
Click to collapse
ealaykum alssalam
thanks bro for help
i flashed the rom without change anything in script and its work
u know when the stable rom will out?

[How-To] GSI Definitive Guide (ROM+GApps+Bluetooth+GCam+90HZ+V4A)

Hello everybody:
GSI ROMS finally have Fingerprint on display (fod) support, so I decided to try it today.
It was quite difficult to make everything work, since there are a lot of guides in X2 Pro forum and XDA, so I decided to create this thread to make things easier to other users that want to use GSI ROMS.
My device is a Realme X2 Pro Chinese, but this should work on any X2 Pro.
The guides I used as references are these ones:
https://forum.xda-developers.com/realme-x2-pro/how-to/how-to-flash-aosp-android-10-gsi-realme-t4036825
https://forum.xda-developers.com/realme-x2-pro/how-to/how-to-flash-havoc-evolution-gsi-t4040607
https://forum.xda-developers.com/realme-x2-pro/how-to/how-to-flash-aosp-android-10-gsi-realme-t4036825
https://forum.xda-developers.com/project-treble/trebleenabled-device-discussion/guide-fix-bluetooth-audio-a2dp-aptx-gsi-t3950938
And probably other ones I found at internet that I can't remember at this point
1. Pre-requisites
- Unlocked bootloader
- TWRP Installed (I use Orange Fox)
- Color OS Firmware A08+ or A13+ (chinese)
Don't do it being on Realme UI, there are some features that won't work with the new firmware/vendor, FP included (Ironically, bluetooth gets fixed).
- Any software that can uncompress .xz files (most of GSI comes in this format)
2. Choosing your ROM
The first step is to find any rom that you like, it must has these features:
- It has to be based on phh's AOSP v214 or newer.
- It must be A/B ARM64.
You can look for one here:
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-%28GSI%29-list
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I would suggest to pick phh's AOSP ROM or LOSQ Project which is really close to phh's source.
https://github.com/phhusson/treble_experimentations/releases
https://github.com/eremitein/treble-patches/wiki/LOSQ-Project
Bugs as of March 03, 2020
At this time, every phh's based rom has the following bugs:
- In-call bluetooth
- Bluetooth media playback (can be solved)
- Auto brightness
- Securize (I tried to use it but never done anything)
And there may be more bugs included on the rom you're using (lineage, havoc, evo, losq, posp, etc)
3. GApps (Optional)
Note: many roms has 2 variants, one with GApps included and one vanilla, depending on the one you choose, you'll have to do this step.
If you need Google Services and the ROM you downloaded does not include them, you need to pick a Gapps package.
Personally, I like BitGapps, but you can choose any you like as long as they are made for ARM64 Android 10.
BitGApps
FlameGApps
OpenGApps
4. Bluetooth fix
Before flashing the ROM, you have to delete the file BluetoothResCommon.apk from your vendor. You may want make a copy of it.
For this, you can do this action in the following ways:
- using a file explorer
Search in the root (/) the path /vendor/overlay
Search the file BluetoothResCommon.apk
Make a backup of the file
Delete the file
- adb and root
Connect your phone to your PC and run these commands from terminal or cmd:
adb pull /vendor/overlay/BluetoothResCommon.apk
adb shell
su
rm /vendor/overlay/BluetoothResCommon.apk
- adb and twrp
Enter in recovery mode
Mount vendor partition
Connect your phone to your PC and run these commands from terminal or cmd:
adb pull /vendor/overlay/BluetoothResCommon.apk
adb shell
rm /vendor/overlay/BluetoothResCommon.apk
This section is based from this guide. Only the first step is needed, X2 Pro build.prop has already some working configurations.
5. Flashing ROM and Gapps
- Download the ROM file (if you haven't)
- If ROM it's compressed (xz), then uncompress the file and copy the rom_name.img file to your phone
- Copy GApps to your phone (optional)
- Enter in TWRP
- Choose the file rom_name.img
- Flash it as "System image"
- If you're flashing GApps, follow this steps:
- Go to Partitions
- Select system
- Resize partition
- Flash GApps package
If this steps shows you errors, you can reboot to recovery and try again- Format data
- Reboot system
Note: according to many guides and people, certain roms like havoc won't boot if you don't set your selinux to permissive.
I tried havoc some weeks ago and I didn't needed to do that, but in case the rom you picked doesn't boot, flash Permissiver_v5 from this thread:
https://forum.xda-developers.com/realme-x2-pro/how-to/how-to-flash-havoc-evolution-gsi-t4040607
6. Magisk
As of March 15, 2020, phh's Magisk works, yes, but it has the following issues:
- App installation becomes slower
- Internal storage becomes read and append only, you can't modify files or delete them.
For those reasons I do not recommend to install it at this moment. Whenever it gets fixed, I'll update the guide with the proper links.
7. First steps in your new ROM (including 90hz)
Now that your rom has booted (I think), there are some basic configs that you may want to do:
- Get LTE working:
In my case, by default the ROM were locked on WCDMA, which is 3G+ in my operator, follow this steps to change it
- Go to Settings
- Open Network & internet
- Select Mobile network
- Look for Preferred network type
- Choose the one that works better for you. I selected global.
- Enable device features:
By default, some of our device features come disabled, lets change it
- Go to Settings
- Open Phh Treble Settings
- Open Oppo features
- Select Enable DT2W
- Select Enable Game Mode
- Select Enable USB OTG- Open Misc features
- Select Expose Aux cameras
- Select Force Enable Camera2API HAL
- Enable 90HZ!
And finally, for enabling 90HZ:
- Go to Settings
- Open Phh Treble Settings
- Open Misc features
- Select Force FPS
- Choose 90.0 (or 60.0 if you don't want it)
- Nice
8. Google Camera (GCam)
Get a funcional GCam was really hard, I tried several versions like Urnyx, Tiger, BSG and Arnova. They didn't work, whenever I made a picture or video the app closed, even loading the config.xml
After a lot of effort, I found one that is working pretty well, including features like night mode! It's a very specific version, GCam_5beta6.200105.0445build-7.2.018.apk others didn't work
Just download and install it:
https://www.celsoazevedo.com/files/android/google-camera/f/changelog955/
Note: You probably will need to download Google Photos app, I already use it, so it worked from the first run.
9. Viper4Android (V4A)
And last but not least, for people that uses V4A, these are the steps to making it work without Magisk.
1. You will have to set your selinux to permissive, if you haven't, flash Permissiver_v5
2. Go to this site https://zackptg5.com/android.php#viper and download Rootless Driver Installer
3. Flash the file
4. Reboot and install Viper4Android 2.7.0.1 or newer
5. Profit!
There are some screenshots at the attachments
Many thanks to all the devs, contributors and XDA Users that made possible to have AOSP GSI in X2 Pro, some of them:
@phhusson @natedogg20050 @ospeto @SrCDA @Jerry08 @mauronofrio

Auto brightness and aptx hd also not working out of the box . But aptx hd can be enable with a magisk module. Thanks for this guide.

is volte working?

@EdgardoSchiffer Good stuff, did you use a specific config for the Gcam?
Also you could add Youtube Vanced to your guide I've found that the non-root works best https://vanced.app/

Does Google Pay work? How to get root access like magisk stable?

onlyoneaamir said:
is volte working?
Click to expand...
Click to collapse
Can't tell, no VoLTE in my country
exadeci said:
@EdgardoSchiffer Good stuff, did you use a specific config for the Gcam?
Also you could add Youtube Vanced to your guide I've found that the non-root works best https://vanced.app/
Click to expand...
Click to collapse
I ran GCam with stock config, It does a great Job
Aj.GaLaxY aCE said:
Does Google Pay work? How to get root access like magisk stable?
Click to expand...
Click to collapse
GPay probably not, by default even Netflix does not appear on Play Store
You can get root with Magisk, but you will have the bugs I wrote on thread. I don't know if there is any other root method

I just use latest magisk from official website and have no bugs like you mentioned. I am on phh latest gsi.

ospeto said:
I just use latest magisk from official website and have no bugs like you mentioned. I am on phh latest gsi.
Click to expand...
Click to collapse
There is a root, but system files cannot be changed or deleted, check for yourself through the file manager

Ah yes, it become read only file system. But magisk modules working OK right? We can use twrp for deleting or modifying system file.

This is cool, though LOSQ tends to freeze and reboot from time to time. It's happened to me 4-6 times since yesterday.

How to go to stock. Do we need any Bluetooth fix?

Aj.GaLaxY aCE said:
How to go to stock. Do we need any Bluetooth fix?
Click to expand...
Click to collapse
Flash stock ozip from recovery, you don't need any fix since the it will override the changes you've done in vendor

EdgardoSchiffer said:
Flash stock ozip from recovery, you don't need any fix since the it will override the changes you've done in vendor
Click to expand...
Click to collapse
U need to flash vbmeta.img if it stuck at bootlogo.

Don't forget that all those ROMs that we can use on our phones are because of one guy and he just added fingerprint reading on Realme phones a few days ago, so go and Sponsor him on Github!
https://github.com/sponsors/phhusson
I just did and for a year Github matches the donation:
To supercharge community funding, GitHub created the GitHub Sponsors Matching Fund, which matches up to $5000 USD total per sponsored developer in their first year, or 12 months, of sponsorship.
Click to expand...
Click to collapse

exadeci said:
Don't forget that all those ROMs that we can use on our phones are because of one guy and he just added fingerprint reading on Realme phones a few days ago, so go and Sponsor him on Github!
https://github.com/sponsors/phhusson
I just did and for a year Github matches the donation:
Click to expand...
Click to collapse
Wonderful suggestion, just did the same

Great work guys!!!
ist it possible to fix the Bluetooh Audio issue (Headphones are connected, but music is played with the speakers of the phone) after installation of the ROM?
Furthermore, left swipe does not show the Google Discover feed and 'o.k. Google' doesn't respond to my voice.

runner2003 said:
Great work guys!!!
ist it possible to fix the Bluetooh Audio issue (Headphones are connected, but music is played with the speakers of the phone) after installation of the ROM?
Furthermore, left swipe does not show the Google Discover feed and 'o.k. Google' doesn't respond to my voice.
Click to expand...
Click to collapse
Read the guide, mount Vendor in TWRP or OrangeFox and you'll be able to find it in the file manager in the recovery.
Can't help with the last part though.

Thanks, that works
Anyone else, who has an idea why 'O.K. Google' isn't working? It's not possible to set it up in the Google App.

For me, Bluetooth for media audio didn't work. I've remove Bluetoothres.apk before flashing. How to do? Flash last version 215, is it value to do?

Many thanks for the great effort, OP.
I haven't had any luck in installing any GSI on my Gloabl X2 Pro and I have been trying for a week now. I noticed every thread has different method, which got me very confused. I would like to thank you for stating the system Pre-requisites, not many HOW-TO guides state the firmware requirement.
Before i ask my question, i didn't have any luck with your method either. The question is, in the reference links you provided, they talk about vbmeta and pushing fstab.qcom, but you didn't mention anything about them in the steps. Am i missing something?
i just want to install a GSI, i don't care about any fix. I just want a GSI to boot because after SUCCESSFULLY installing the image then wiping data, i get into a bootloop. So my priority is just getting a GSI to boot.
I am on RMX1931EX_11_A.10
I appreciate anyone's input into solving my issue

Database Users

welcome