• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[ROM][OFFICIAL][ginkgo/willow] Pixel Experience [11.0]

do you like it ?


  • Total voters
    169
Search This thread

diegojco

New member
Sep 23, 2021
3
1
Hi, I installed the latest pixel experience rom via twrp but the wifi doesnt work. I've read that i have to flash the latest android ten firmware. I can do that now or i have to flash the fw first and then the pe rom? Thank you, looking foward to using this rom
 

Evil_Hunter

Member
May 22, 2021
16
2
Samsung Galaxy J2
Redmi Note 8
Hi, I installed the latest pixel experience rom via twrp but the wifi doesnt work. I've read that i have to flash the latest android ten firmware. I can do that now or i have to flash the fw first and then the pe rom? Thank you, looking foward to using this rom
firmware first then the pe rom. Otherwise the wifi will not work. I asked many people and they say that to prevent users from going from MIUI ROM xiaomi use broked vendor in Redmi Note 8. So for this after flashing any custom rom in note 8 the wifi doesn't work. Then a solution came that if you flash the MIUI firmware and then the custom rom wifi works. But then the phone stucks at bootloop. Then a solution came that you have to flash the miui firmware first and then custom rom. Then you have to do format data and then reboot the device. The device will actually boot and wifi will also work as a charm
 

diegojco

New member
Sep 23, 2021
3
1
firmware first then the pe rom. Otherwise the wifi will not work. I asked many people and they say that to prevent users from going from MIUI ROM xiaomi use broked vendor in Redmi Note 8. So for this after flashing any custom rom in note 8 the wifi doesn't work. Then a solution came that if you flash the MIUI firmware and then the custom rom wifi works. But then the phone stucks at bootloop. Then a solution came that you have to flash the miui firmware first and then custom rom. Then you have to do format data and then reboot the device. The device will actually boot and wifi will also work as a charm
I did this and it's working great. I'm so happy with this rom, so smooth. Thank you for replying.
 
  • Like
Reactions: Evil_Hunter

veracid

Member
Sep 24, 2016
20
1
Hi, how can i use gpay? Actually It don t accept any card, It view phone as a root decide but i don't have root permission...i don t instal magisk or other
 

LonerPrime

Member
Feb 23, 2014
8
7
Foremost, thank you for this ROM. Even though I wasn't able to install it, I still appreciate it nonetheless.

That being said... I'm lost. Apologies if this was already answered in the 37 page thread here but this is my first time installing a custom ROM on my Redmi Note 8. I'm well accustomed to technology but most of my experience is based around computers with mobile systems not exactly being my strong suit. Hence, I made sure to follow the guide linked in the download section to the letter. Everything was going fine up until it came to booting into the TWRP recovery itself. Everytime I'd tried to boot into it, by holding down VolumeUp+Power button, for the life of me I couldn't get into it. Kept getting greeted by MI Recovery, like the phone was erasing TWRP somehow.

I know I didn't mess up the steps upto copying the recovery into the phone because ADB acknowledged all my steps without errors. Heck I even went a step ahead and erased cache after copying the recovery, but ended up with the same result. After searching other threads, I found "fastboot boot recovery.img" command that would direct the phone to boot into TWRP but somehow that made the phone freeze on REDMI icon for quite some time.

At this point, I'm unsure how to proceed. My MiUI Packages are upto date and unless there is something else outside of the guide that I should be doing, I'd appreciate some troubleshooting if possible please.

Regards,
LonerPrime
 

Zep0th

Senior Member
Feb 7, 2017
287
107
Xiaomi Mi 9
When i turn on wifi UI force closes, help??? It was working the first boot, after a reboot it started doing this.

EDIT: a factory reset worked.

How can i flash magisk on this device? TWRP keeps getting replaced with Pixel Recovery then randomly stops booting or magisk not working.
 
Last edited:

NerdyLlama

Member
May 22, 2012
16
1
It seems like every boot overwrites the recovery partition, so the only way to boot into a custom recovery is tedious and only temporary.

Flashing a custom recovery .img file (.e.g TWRP or manually extracting recovery.img from PBRP .zip):
  1. adb reboot bootloader
  2. fastboot flash recovery path/to/recovery.img
  3. Reboot into recovery using your device's key combination. This is usually holding Power + Volume Up until the device reboots into recovery.
  4. Wait until you've rebooted into your custom recovery tool.
  5. Flash your recovery image again, this time using your custom recovery tool. If you skip this step, your recovery partition may be reverted the next time you reboot.
There doesn't currently appear to be a way to replace the recovery partition from within the Pixel Experience recovery mode. While it is possible to flash a custom recovery .zip file using "Apply updates", it will be reverted no matter how you reboot.

@iamsaalim is the reverting of the recovery partition on every boot intentional or a bug?
Because it currently makes using a custom recovery nearly impossible.
 
Last edited:

LonerPrime

Member
Feb 23, 2014
8
7
you need to use its internal reboot menu to reboot to recovery, otherwise Xiaomi default recovery will re-install itself.

  1. Reboot into recovery using your device's key combination. This is usually holding Power + Volume Up until the device reboots into recovery.
  2. Wait until you've rebooted into your custom recovery tool.

Thank you both for your advice. Unfortunately, things have gone weird now with Mi Recovery no longer showing up either after transferring the recovery in. It's like the phone is trying to execute TWRP by default but neither by button combination nor by adb command can I get it to load any recovery, MI or custom. Screen just freezes on REDMI icon and stays so infinitely. If I boot normally however, the phone smoothly sails past the REDMI icon into the MIUI splash screen and eventually loads the MI OS without any issues.

Is this weird anomaly due to ginkgo firmware that is baked into my country's version? I'm on the Indian version that is probably the oldest compared to the other Note 8 variants according to the MiFirmware website and while others see MI boot icons, I get REDMI and MIUI instead. However, if this is not a factor, then I'm still unsure how to proceed further..
 
Last edited:

yn4v4s

Member
Aug 15, 2021
19
2
Redmi Note 8
OnePlus 8
Thank you both for your advice. Unfortunately, things have gone weird now with Mi Recovery no longer showing up either after transferring the recovery in. It's like the phone is trying to execute TWRP by default but neither by button combination nor by adb command can I get it to load any recovery, MI or custom. Screen just freezes on REDMI icon and stays so infinitely. If I boot normally however, the phone smoothly sails past the REDMI icon into the MIUI splash screen and eventually loads the MI OS without any issues.

Is this weird anomaly due to ginkgo firmware that is baked into my country's version? I'm on the Indian version that is probably the oldest compared to the other Note 8 variants according to the MiFirmware website and while others see MI boot icons, I get REDMI and MIUI instead. However, if this is not a factor, then I'm still unsure how to proceed further..
What fw version are u currently in??? You need to flash latest R firmware
 

s0tix

Member
Jul 20, 2021
12
0
Installed this on my redmi note 10 pro but when using snapchat i get a message "error" opening camera, it is able to open it sometimes but its frustrating having to close the app and open it again and again. any tips?
 

LonerPrime

Member
Feb 23, 2014
8
7
What fw version are u currently in??? You need to flash latest R firmware

My current version is MIUI Global 12.0.2 Stable 12.0.2.0(QCOINXM). Before installation I scanned through this thread lightly and came across this post by a thread member who explained what Ten Firmware is and how it was necessary for installing PE. So, I made sure to compare mine with the Firmware website and confirmed that mine was the latest, atleast for India that is.

I apologize again for being completely new at this flashing business but, is R Firmware different than Ten Firmware? If so, which version is it, where can I find it and how do I install it?
 

yn4v4s

Member
Aug 15, 2021
19
2
Redmi Note 8
OnePlus 8
My current version is MIUI Global 12.0.2 Stable 12.0.2.0(QCOINXM). Before installation I scanned through this thread lightly and came across this post by a thread member who explained what Ten Firmware is and how it was necessary for installing PE. So, I made sure to compare mine with the Firmware website and confirmed that mine was the latest, atleast for India that is.

I apologize again for being completely new at this flashing business but, is R Firmware different than Ten Firmware? If so, which version is it, where can I find it and how do I install it?
Ten firmware means Android 10 firmware, according to the maintainer, Android 11 firmware is mandatory, that's R fw, a10 = Q, a11 = R. You can find last fw (for ginkgo) here: https://xiaomifirmwareupdater.com/firmware/ginkgo/

Installation is done via recovery (TWRP or whatever other your are using)
 

Top Liked Posts

  • There are no posts matching your filters.
  • 6
    Thank you all who gave their valuable input in my quest to troubleshoot my issues. After immense trial and error with tons of google searches, I was finally able to frankenstien enough knowledge to create one final solution. As a sign of my respect for this community, I'll pen my experience down in hopes it saves the trouble for someone else down the line.

    Foremost, the installation guide linked was easy to understand and the ROM itself is light and extremely responsive. Apart from some minor hiccups here and there, this is a good Pixel Experience. Thank you iamsaalim!

    That being said, if you're an unfortunate person like me who lives in India and a victim of Xiomi's "yea I'll think about you last" attitude, there are a few things that the guide does not cover at the time of writing this post. Not the maintainers fault tbh, it's just bad luck. Here are the steps that I followed:

    • Grabbed both the ROM and Recovery from the link in the original post.
    • Followed the guide to the letter up until the point where I flashed the recovery in via adb.
    • Encountered recovery issue where the phone would just freeze trying to go into recovery via Vol+ and Power buttom. Tried "fastboot erase userdata" command. Freezing issue gone but instead of TWRP, MI Recovery showed up. After much trial and error and thanks to yn4v4s's input(you rock dude), I finally realized I'm on Q firmware which is Android 10 whereas the TWRP in the original post is meant for R firmware which is Android 11. Decided to grab the yn4v4s's recommended Global version.
    • Went to TWRP website and grabbed December 2020 recovery and flashed that via adb. Success as TWRP flares to life.
    • Continued on with the guide all excited thinking the worse is behind me as all I need is to install ROM, right? WRONG.
    • Immediately new problem: Factory Reset/Formatting failure/Wiping Failed. reason? Operation not Permitted
    • Selected Mount and spotted a weird anomaly. Cycling through the storage, noticed Internal storage was marked as (0) capacity. Immediately stuck that as odd. Google search intensified.
    • Went to Wipe> Selecting /data > Advance Wipe > Change file system, I saw that the file system was FTFS by default. Changed it to ext4 and formatted it. Now ftfs is supposed to be better but I noticed all other drive partitions were in ext4 format, so for the sake of simplicity I stuck with ext4 instead of reverting to ftfs.
    • Tried Factory resetting again. This time new error while formatting: Invalid Argument. Proceeded to chuck neighbor's cat out of the window and fight imaginary sharks to vent frustration.
    • Calmed down and went back a few steps. Realized, forgot to clear cache. Went back into Advance wipe and cleared Davlik /ART Cache, Cache, Data, System and Vendor.
    • Proceeded to format once again typing "yes" while praying. Finally, success!!
    • Time to flash and upgrade to Android 11 firmware first before the ROM. Placed the global firmware into the SD card via USB cable. Saw folks flashing ROMs from TWRP as well so placed PE ROM too.
    • Selected Install on TWRP and navigated to the firmware file. Executed the firmware and noticed it installing within seconds. A bit worrying sign but since no errors were thrown I continued on.
    • Navigated to the directory again, selected PE ROM image this time and installed it as well. Installation went without any incidents and returned with a success message. Okay...
    • Moment of Truth. Reboot! 1 minute passes, Google Icon spins up. YES! 2 minute passes, Google bar starts running. Encouraging! 3 minute passes, bar continues running. Erm. 4 minute passes, bar still. Uh oh.
    • Yeap, no cigar yet. I'm now stuck in a boot loop. To make matter worse, TWRP recovery gets overwritten by PE Recovery. Sigh.
    • Decide to grab the latest TWRP from their website and flash that instead since there is no point in using old Android 10 TWRP.
    • Aaand I'm frozen again on REDMI screen. WTF?! I flashed Android 11 global firmware so I'm pretty sure I'm on the new one. Flashed old TWRP again and sure enough I'm into the recovery. Confused as hell now. For the heck of it, I erased Cache again.
    • Noticed an odd new console error in red. Unable to decrypt FBE device
    • More google searches later, I come across discussion where community came to the conclusion that "console output Unable to decrypt FBE device was nothing but to tell us that incompatible operating system flashed"
    • OS can't be an issue, it's made for my Redmi Note 8 and I'm plenty sure I'm on ginkgo.
    • Going through this thread I noticed how folks swore by Chinese firmware. Decided to deviate and flash that firmware instead. Wiped everything again including the OS.
    • Went back to following the guide and decided to sideload selecting Advanced on TWRP and select "Side Load" option. Copied the ROM in my ADB directory on the PC and used the "sideload 'ROM NAME'.zip" command.
    • Waited patiently for the message: If the process succeeds the output will stop at 47% and report adb: failed to read command: Success/No error.
    • Process ends but no such message. Instead I get: Total xfer: 1.00x
    • Quick google search showed that this is an error message. Too tired to get angry or brainy at this point so I simply reboot for the heck of it.
    • 1 minute into boot and suddenly I see white light. COULD IT BE...?
    • Sure enough, Google bursts out of boot into first time setup. YAY?!!
    Apologies, if this became a weird wall of text but this is a sum total of my experience in the last couple of weeks. I've no idea if I have done this right or I just got lucky eventually but it somehow worked for me. From installing adb, to fighting with drivers to recognize my phone, to waiting 7 days for bootloader to open, to finally all that I listed above, it was truly a nightmarish experience. But in the end, it was worth it. The default camera was a bit of a letdown but thankfully GCam apk uploaded in this thread by another member was easy enough to install and runs without issues. Unable to move the clock on the wallpaper became a bit of an irritant but nothing Nova Launcher couldn't fix.

    All in all, apart from the installation pangs, I'm loving it. Thank you all for your advice. Truly would have been lost without your inputs.
    2
    Crap. That explains a bloody lot. Thank you for sharing that knowledge. I got hold of the R firmware but... damnnit, TWRP recovery simply won't execute. Screen just freezes. I think I'll have to find a reliable alternative to TWRP..
    Make sure you got the right version of TWRP for your device, you can use Pitch Black Recovery as well, just don't use OrangeFox, it breaks with PE
    1
    can I upload the newest room to the previous one without formatting and new installation?
    Yes, use pe recovery and let ota update it automatically
    1
    firmware first then the pe rom. Otherwise the wifi will not work. I asked many people and they say that to prevent users from going from MIUI ROM xiaomi use broked vendor in Redmi Note 8. So for this after flashing any custom rom in note 8 the wifi doesn't work. Then a solution came that if you flash the MIUI firmware and then the custom rom wifi works. But then the phone stucks at bootloop. Then a solution came that you have to flash the miui firmware first and then custom rom. Then you have to do format data and then reboot the device. The device will actually boot and wifi will also work as a charm
    I did this and it's working great. I'm so happy with this rom, so smooth. Thank you for replying.
    1
    My current version is MIUI Global 12.0.2 Stable 12.0.2.0(QCOINXM). Before installation I scanned through this thread lightly and came across this post by a thread member who explained what Ten Firmware is and how it was necessary for installing PE. So, I made sure to compare mine with the Firmware website and confirmed that mine was the latest, atleast for India that is.

    I apologize again for being completely new at this flashing business but, is R Firmware different than Ten Firmware? If so, which version is it, where can I find it and how do I install it?
    It is always recommended to install a custom rom just like the maintainer says.
    As it is written here to install android 11 firmware so it is better to follow it and install android 11 firmware
    Use TWRP or what you are using to flash it
    Dont use orange fox recovery to flash this rom
    Or you will stuck in orange fox recovery logo

    I tried to flash this rom using orange fox and then stuck at the orange fox boot logo. Then I asked the maintainer and he said to use PE (Pixel experience) recovery or TWRP recovery to flash this rom

    And it doesn't actually matter which countries firmware you are flashing like you can flash the Indian firmware (IN), Chinese firmware (CN), Global firmware (MI), Europe firmware (EU). It doens't make a difference. Like in my country the latest miui firmware is MIUI 12.0.6.0 (QCOMIXM) and I actually flash all types of custom rom using this firmware.
    But it is recommend to flash the firmware which the maintainer suggest just to stay in the safe zone
  • 21
    1615785682437.png


    PixelExperience for Xiaomi Redmi Note 8/8T

    What is this?
    Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)

    Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device

    Based on Android 11



    Whats working?
    Wifi
    RIL
    Mobile data
    GPS
    Camera
    Camcorder
    Bluetooth/Audio
    Fingerprint reader
    Sound / vibration
    DT2W


    Known issues
    You tell.

    How to flash
    Flash Latest Ten firmware
    Wipe system
    Wipe Vendor
    Format Data
    Flash ROM
    Reboot

    Telegram Group
    Link


    DON'T FLASH GAPPS, ALREADY INCLUDED
    Link


    Translation
    Help with project translation

    Stay tuned
    Our Telegram channel
    Our blog






    XDA:DevDB Information
    pixel-experience, ROM for the Xiaomi Redmi Note 8/8T

    Contributors
    iamsaalim
    Source Code: https://github.com/PixelExperience-Devices/device_xiaomi_ginkgo

    ROM OS Version: Android 11
    ROM Kernel: Linux 4.x
    ROM Firmware Required: Ten firmware.
    Based On: AOSP

    Version Information
    Status:
    Stable
    Beta Release Date: 2021-03-13

    Created 2021-03-15
    Last Updated 2021-03-15
    6
    Thank you all who gave their valuable input in my quest to troubleshoot my issues. After immense trial and error with tons of google searches, I was finally able to frankenstien enough knowledge to create one final solution. As a sign of my respect for this community, I'll pen my experience down in hopes it saves the trouble for someone else down the line.

    Foremost, the installation guide linked was easy to understand and the ROM itself is light and extremely responsive. Apart from some minor hiccups here and there, this is a good Pixel Experience. Thank you iamsaalim!

    That being said, if you're an unfortunate person like me who lives in India and a victim of Xiomi's "yea I'll think about you last" attitude, there are a few things that the guide does not cover at the time of writing this post. Not the maintainers fault tbh, it's just bad luck. Here are the steps that I followed:

    • Grabbed both the ROM and Recovery from the link in the original post.
    • Followed the guide to the letter up until the point where I flashed the recovery in via adb.
    • Encountered recovery issue where the phone would just freeze trying to go into recovery via Vol+ and Power buttom. Tried "fastboot erase userdata" command. Freezing issue gone but instead of TWRP, MI Recovery showed up. After much trial and error and thanks to yn4v4s's input(you rock dude), I finally realized I'm on Q firmware which is Android 10 whereas the TWRP in the original post is meant for R firmware which is Android 11. Decided to grab the yn4v4s's recommended Global version.
    • Went to TWRP website and grabbed December 2020 recovery and flashed that via adb. Success as TWRP flares to life.
    • Continued on with the guide all excited thinking the worse is behind me as all I need is to install ROM, right? WRONG.
    • Immediately new problem: Factory Reset/Formatting failure/Wiping Failed. reason? Operation not Permitted
    • Selected Mount and spotted a weird anomaly. Cycling through the storage, noticed Internal storage was marked as (0) capacity. Immediately stuck that as odd. Google search intensified.
    • Went to Wipe> Selecting /data > Advance Wipe > Change file system, I saw that the file system was FTFS by default. Changed it to ext4 and formatted it. Now ftfs is supposed to be better but I noticed all other drive partitions were in ext4 format, so for the sake of simplicity I stuck with ext4 instead of reverting to ftfs.
    • Tried Factory resetting again. This time new error while formatting: Invalid Argument. Proceeded to chuck neighbor's cat out of the window and fight imaginary sharks to vent frustration.
    • Calmed down and went back a few steps. Realized, forgot to clear cache. Went back into Advance wipe and cleared Davlik /ART Cache, Cache, Data, System and Vendor.
    • Proceeded to format once again typing "yes" while praying. Finally, success!!
    • Time to flash and upgrade to Android 11 firmware first before the ROM. Placed the global firmware into the SD card via USB cable. Saw folks flashing ROMs from TWRP as well so placed PE ROM too.
    • Selected Install on TWRP and navigated to the firmware file. Executed the firmware and noticed it installing within seconds. A bit worrying sign but since no errors were thrown I continued on.
    • Navigated to the directory again, selected PE ROM image this time and installed it as well. Installation went without any incidents and returned with a success message. Okay...
    • Moment of Truth. Reboot! 1 minute passes, Google Icon spins up. YES! 2 minute passes, Google bar starts running. Encouraging! 3 minute passes, bar continues running. Erm. 4 minute passes, bar still. Uh oh.
    • Yeap, no cigar yet. I'm now stuck in a boot loop. To make matter worse, TWRP recovery gets overwritten by PE Recovery. Sigh.
    • Decide to grab the latest TWRP from their website and flash that instead since there is no point in using old Android 10 TWRP.
    • Aaand I'm frozen again on REDMI screen. WTF?! I flashed Android 11 global firmware so I'm pretty sure I'm on the new one. Flashed old TWRP again and sure enough I'm into the recovery. Confused as hell now. For the heck of it, I erased Cache again.
    • Noticed an odd new console error in red. Unable to decrypt FBE device
    • More google searches later, I come across discussion where community came to the conclusion that "console output Unable to decrypt FBE device was nothing but to tell us that incompatible operating system flashed"
    • OS can't be an issue, it's made for my Redmi Note 8 and I'm plenty sure I'm on ginkgo.
    • Going through this thread I noticed how folks swore by Chinese firmware. Decided to deviate and flash that firmware instead. Wiped everything again including the OS.
    • Went back to following the guide and decided to sideload selecting Advanced on TWRP and select "Side Load" option. Copied the ROM in my ADB directory on the PC and used the "sideload 'ROM NAME'.zip" command.
    • Waited patiently for the message: If the process succeeds the output will stop at 47% and report adb: failed to read command: Success/No error.
    • Process ends but no such message. Instead I get: Total xfer: 1.00x
    • Quick google search showed that this is an error message. Too tired to get angry or brainy at this point so I simply reboot for the heck of it.
    • 1 minute into boot and suddenly I see white light. COULD IT BE...?
    • Sure enough, Google bursts out of boot into first time setup. YAY?!!
    Apologies, if this became a weird wall of text but this is a sum total of my experience in the last couple of weeks. I've no idea if I have done this right or I just got lucky eventually but it somehow worked for me. From installing adb, to fighting with drivers to recognize my phone, to waiting 7 days for bootloader to open, to finally all that I listed above, it was truly a nightmarish experience. But in the end, it was worth it. The default camera was a bit of a letdown but thankfully GCam apk uploaded in this thread by another member was easy enough to install and runs without issues. Unable to move the clock on the wallpaper became a bit of an irritant but nothing Nova Launcher couldn't fix.

    All in all, apart from the installation pangs, I'm loving it. Thank you all for your advice. Truly would have been lost without your inputs.
    5
    Yes sir, same for me yesterday with Willow. I thought it was caused by flashing DFE after flashing ROM, but so probably it's not the case. I solved flashing the latest stable fastboot MIUI rom from XiaomiAdbFastboot Tools, than flashing OrangeFox, wipe system etc., format data and than flashing the ROM zip. I also enabled the OTA updater settings in OrangeFox (I don't think it serves any purpose, but I'm writing it anyway).

    EDIT: I tried to go to recovery and I got stuck again......so don't try to open it again... @iamsaalim

    EDIT2 - installing Pitch Black Recovery (as said in previous posts) allows to open recovery but it got stuck on bootanimation if I reboot into system
    1. Flash vbmeta.img and recovery.img using adb fastboot
    2. Boot into recovery mode and connect ur phone to the computer using usb cable
    3. Copy the recovery file, ROM, latest 10 fw
    4. (In the recovery mode) flash recovery file
    5. Flash 10 fw
    6. Wipe cache/dalvik, data, vendor, internal storage, system
    7. Format data
    8. Install ROM
    9. Boot to system
    If u using the latest version of PE+ or PE I suggest using pitch black recovery
    3
    Hey guys, I figured out how to stop PE recovery from overwriting TWRP!(Noob here, so ignore if you already know this).

    All you have to do is format the cache partition in fastboot mode before booting to recovery. This can be done by fastboot erase cache , after fastboot flash recovery twrp-3.5.2_9-1-ginkgo.img .
    3
    Thread cleaned

    Please be friendly to each other and also respectful.
    Keep the thread on topic 👍

    If you have bugs, report them to the dev with logs etc. and contribute to make the rom bug-free.
    If you don't want to contribute, use it as it is and say at least thanks to the dev who provided his work freely here on XDA:) The dev owes you absolutely nothing and you're not his customer cause you did not pay him.

    This manner of posting is not tolerated.

    I recommend to read the FORUM RULES especially those:


    2.1 Language: XDA is a worldwide community. As a result, what may be OK to say in your part of the world, may not be OK elsewhere. Please don't direct profanity, sexually explicit language or other offensive content toward Members or their work. Conversely, while reading posts from other members, remember that the word you find offensive may not be offensive to the writer. Tolerance is a two-way street.

    2.3 Flaming / Lack of respect: XDA is about sharing and this does not involve virtual yelling (flaming) or rudeness. Flaming or posting with a lack of respect is unacceptable. Treat new members in the manner in which you would like to have been treated when you were a new member. When dealing with any member, provide them with guidance, advice and instructions when you can, showing them respect and courtesy. Never post in a demanding, argumentative, disrespectful or self-righteous manner.

    2.4 Personal attacks, racial, political and / or religious discussions: XDA is a discussion forum about certain mobile phones. Mobile phones are not racial, political, religious or personally offensive and therefore, none of these types of discussions are permitted on XDA.


    If you come across this just hit the report button and let the mods handle it, do not respond or become part of such a discussion.

    Regards!

    strongst
    Forum Moderator