Develop Bugs

razer phone with pie unofficial

i always keep checking for pie update on my razor phone well i found this but as it aint on xda site im suspicious what u all think
https://www.firmwares.androidinfotech.com/aosp-project-treble-custom-rom/

That is just referring to the fact, that being project treble, we can install generic system images. Pie already runs on our phone, but there aren't any developers (that i have seen at least) working to get pie running for our phone. XDA has a thread about what phones can run the Pie GSI and our phone has been on that list for a long time.

Pie GSI images from
https://forum.xda-developers.com/project-treble
Work alright for me with a few issues like using magisk breaks networking (WiFi, 3g)
I've been playing around with the 8.1 builds and they work great. Pixel experience is by far the best so far.
Just hope razer release pie so we can get an updated kernal that will hopefully fix all the GSI problems on it.

tay200k said:
Pie GSI images from
https://forum.xda-developers.com/project-treble
Work alright for me with a few issues like using magisk breaks networking (WiFi, 3g)
I've been playing around with the 8.1 builds and they work great. Pixel experience is by far the best so far.
Just hope razer release pie so we can get an updated kernal that will hopefully fix all the GSI problems on it.
Click to expand...
Click to collapse
What was your experience with the Pie GSI builds? What, if anything, was broken?
Peace

chris5s said:
What was your experience with the Pie GSI builds? What, if anything, was broken?
Peace
Click to expand...
Click to collapse
Everything Worked that I tried, the only thing I didn't try was NFC.

tay200k said:
Everything Worked that I tried, the only thing I didn't try was NFC.
Click to expand...
Click to collapse
Ok, thanks. One more question, did you flash an a or ab build?
Peace.

chris5s said:
Ok, thanks. One more question, did you flash an a or ab build?
Peace.
Click to expand...
Click to collapse
AB Build.
Flashed factory image booted to OS enabled USB debugging rebooted bootloader booted twrp (don't flash it just boot) flash image via twrp to system wipe data and boot. It will ask for a password on first boot just type stuff until it asks to factory reset do it and allow default recovery to wipe data and after it should boot.
(Sorry rushed this reply as I'm at work)

tay200k said:
AB Build.
Flashed factory image booted to OS enabled USB debugging rebooted bootloader booted twrp (don't flash it just boot) flash image via twrp to system wipe data and boot. It will ask for a password on first boot just type stuff until it asks to factory reset do it and allow default recovery to wipe data and after it should boot.
(Sorry rushed this reply as I'm at work)
Click to expand...
Click to collapse
Is the issue with getting kicked to download mode fixed? Can i reboot multiple times without going into download?

iliais347 said:
Is the issue with getting kicked to download mode fixed? Can i reboot multiple times without going into download?
Click to expand...
Click to collapse
I never had that problem myself so far maybe something to do with the fact I never flash twrp to the device maybe? Not sure.

tay200k said:
I never had that problem myself so far maybe something to do with the fact I never flash twrp to the device maybe? Not sure.
Click to expand...
Click to collapse
Oh so you flash magisk with stock recovery?

iliais347 said:
Oh so you flash magisk with stock recovery?
Click to expand...
Click to collapse
No in the bootloader I just "fastboot boot twrp.img" not flash it so it temporary boots it then flash magisk and don't bother with flashing twrp installer.

iliais347 said:
Oh so you flash magisk with stock recovery?
Click to expand...
Click to collapse
Edit - nevermind, didn't see the answer above
Peace.

tay200k said:
Pie GSI images from
https://forum.xda-developers.com/project-treble
Work alright for me with a few issues like using magisk breaks networking (WiFi, 3g)
I've been playing around with the 8.1 builds and they work great. Pixel experience is by far the best so far.
Just hope razer release pie so we can get an updated kernal that will hopefully fix all the GSI problems on it.
Click to expand...
Click to collapse
Can i know if Bluetooth audio works with u in anyway?

Haithamraid said:
Can i know if Bluetooth audio works with u in anyway?
Click to expand...
Click to collapse
BT Audio works. BT Calls don't.

linuxct said:
BT Audio works. BT Calls don't.
Click to expand...
Click to collapse
In Oreo or Pie? I can't stream audio to a BT speaker in either....
Peace

[ROM] MIUI 10 Official STABLE OS Update (Public Release) for Redmi 5 Plus (GLOBAL)

MIUI 10 has been released OFFICIALLY for Redmi 5 Plus (Global)
This is a Public Release now.
Recovery ROM (1.38 GB): http://bigota.d.miui.com/V10.0.2.0.OEGMIFH/miui_HM5PlusGlobal_V10.0.2.0.OEGMIFH_dc9f1b974c_8.1.zip
Fastboot ROM (2.18 GB): http://bigota.d.miui.com/V10.0.2.0....FH_20180914.0000.00_8.1_global_018f1e352d.tgz
Preferred method: Fastboot mode via MiFlash Tool
Note: It's better to flash Recovery ROM via updater app, flashing Recovery ROM using Recovery can set the region to China by default.
Steps to change region to India:
1. Download and install Build Prop Editor app.
2. Click on there dots from top right and choose new to add the following 2 system properties.
1st one:
Name -> ro.miui.cust_variant
Value -> EN
(click save)
2nd one:
Name -> ro.miui.region
Value -> in
(click save)
3. Now reboot ur device
4. DONE
HAPPY FLASHING Friends

Discover.RDG said:
Recovery ROM: http://bigota.d.miui.com/V10.0.2.0.OEGMIFH/miui_HM5PlusGlobal_V10.0.2.0.OEGMIFH_dc9f1b974c_8.1.zip
Fastboot ROM: http://bigota.d.miui.com/V10.0.2.0....FH_20180914.0000.00_8.1_global_018f1e352d.tgz
Click to expand...
Click to collapse
The recovery file has to be flashed via twrp or ??. Orangefox recovery??

ibbi.ir7 said:
The recovery file has to be flashed via twrp or ?. Orangefox recovery??
Click to expand...
Click to collapse
Anyone, but Orange fox 8.0 is preferred. Because 8.1 fails to patch dm verity, unless you flash magisk.

I am on MiuiPro latest beta , can i just flash this via whatever and not worry about ARB ?

stole38 said:
I am on MiuiPro latest beta , can i just flash this via whatever and not worry about ARB ?
Click to expand...
Click to collapse
Anti Roll back will not be an issue unless you go to a nougat based rom

stole38 said:
I am on MiuiPro latest beta , can i just flash this via whatever and not worry about ARB ?
Click to expand...
Click to collapse
Vince doesn't have ARB

jes0411 said:
Vince doesn't have ARB
Click to expand...
Click to collapse
Yes, and it doesn't matter unless someone goes to older OS variant.

Discover.RDG said:
Anyone, but Orange fox 8.0 is preferred. Because 8.1 fails to patch dm verity, unless you flash magisk.
Click to expand...
Click to collapse
Hmm ... actually, no! OrangeFox R8.1 is far better than R8.0 at patching dm-verity. And it is also far better at giving detailed reports of how successful was that exercise (plus a warning if certain dm-verity settings were not found (they do not all need to be there - but a warning is good anyway)). I have never needed to flash magisk on vince after flashing miui - even though R8.1 now gives a warning (which was not given in R8.0 in the same situations) that you may wish to flash magisk.

Discover.RDG said:
MIUI 10 has been released OFFICIALLY for Redmi 5 Plus (Global)
This is a Public Release now.
Recovery ROM (1.38 GB): http://bigota.d.miui.com/V10.0.2.0.OEGMIFH/miui_HM5PlusGlobal_V10.0.2.0.OEGMIFH_dc9f1b974c_8.1.zip
Click to expand...
Click to collapse
Have you installed this ROM? Does it boot? The mounting of /system is commented out in /vendor/etc/fstab.qcom ...

DarthJabba9 said:
Have you installed this ROM? Does it boot? The mounting of /system is commented out in /vendor/etc/fstab.qcom ...
Click to expand...
Click to collapse
You need to keep this ROM in a location without space, for example:
C:\ROM
The location must be in the first page of any drive and the name of folder must not have any space. Else only errors.

DarthJabba9 said:
Hmm ... actually, no! OrangeFox R8.1 is far better than R8.0 at patching dm-verity. And it is also far better at giving detailed reports of how successful was that exercise (plus a warning if certain dm-verity settings were not found (they do not all need to be there - but a warning is good anyway)). I have never needed to flash magisk on vince after flashing miui - even though R8.1 now gives a warning (which was not given in R8.0 in the same situations) that you may wish to flash magisk.
Click to expand...
Click to collapse
Everytime I MIUI 9 or 10 from Orangefox 8.1, it always failed to patch dm verity but 8.0 always patched it successfully, so I said that. Magisk is important for removing system junk, such as Analytics and MSA which steals data and displays system ads.

just need xposed to work in miui 10.

Discover.RDG said:
You need to keep this ROM in a location without space, for example:
C:\ROM
The location must be in the first page of any drive and the name of folder must not have any space. Else only errors.
Click to expand...
Click to collapse
Thanks. But this is not my question. My question relates to the fact that the fstab doesn't mount /system (because the relevant line is commented out). So I was asking whether the ROM boots up normally (ie, without mounting the system partition).

DarthJabba9 said:
Thanks. But this is not my question. My question relates to the fact that the fstab doesn't mount /system (because the relevant line is commented out). So I was asking whether the ROM boots up normally (ie, without mounting the system partition).
Click to expand...
Click to collapse
I am going to try this today, will let you know after I try.

Discover.RDG said:
Everytime I MIUI 9 or 10 from Orangefox 8.1, it always failed to patch dm verity but 8.0 always patched it successfully, so I said that...
Click to expand...
Click to collapse
I think I just explained what is really happening. R8.1 gives a warning in exactly the same circumstances in which R8.0 kept quiet. In our view, that (ie, the warning) constitutes progress. But it doesn't necessarily mean that anything is wrong. Recoveries give warnings in all sorts of situations (eg, when backing up /data, etc) just so that the user may be aware of some things.

DarthJabba9 said:
I think I just explained what is really happening. R8.1 gives a warning in exactly the same circumstances in which R8.0 keeps quiet.
Click to expand...
Click to collapse
Yes, I understand that, and I just mentioned the difference I noticed.

DarthJabba9 said:
I think I just explained what is really happening. R8.1 gives a warning in exactly the same circumstances in which R8.0 kept quiet. In our view, that (ie, the warning) constitutes progress. But it doesn't necessarily mean that anything is wrong. Recoveries give warnings in all sorts of situations (eg, when backing up /data, etc) just so that the user may be aware of some things.
Click to expand...
Click to collapse
Maybe the mounting of /system is done by fstab in ramdisk of boot.img.

jes0411 said:
Maybe the mounting of /system is done by fstab in ramdisk of boot.img.
Click to expand...
Click to collapse
I also thought that this might be the case - but there is no fstab of any sort in the ramdisk.

I hate the new notification system where it blurs out the background. Can I change it back to the old one?

Hi.
How is Redmi 5 Plus battery performance after the Global MIUI 10 compared to Global MIUI 9.6 ?

Project Treble & S10+

So I have spent a bit of time testing out project treble roms, cant get any to boot unfortunately. It might be a twrp thing who at this point knows?
Hopefully some Roms & possibly kernels will pop up In the coming weeks or months
Was worth a try, if anyone has had success with GSI's and getting them to boot, please share your method......:good:

I got my S10E to boot phh's v112 gsi, backlit broken so screen very dim, some other bugs to: some settings and apps crash.
How to:
Make sure you have an exynos version
Have an stock rom installed, bootloader unlocked and rebooted into stock and make sure oem unlocking in greyed out in dev settings.
Install recovery (latest fixed version)
Use multidisabler and format data (https://forum.xda-developers.com/galaxy-s10/development)
Reboot recovery
Install GSI, A/B version
Mount system and use TWRP file explorer to delete rw-system.sh in system/bin
Reboot , may need to press power, volume up and bixby few sec in inital boot.

Successfully flashed ......just transitional animation bug, brightness can't be adjusted....but it's not dim....Pixel Experience Rom.

Pixel Dust ......
Just testing out one more, they both boot fine (Pixel Experience & Pixel Dust). ..
Obviously Fingerprint Scanner is non functional also the same brighteness bug (cannot adjust).
Here are some screens of Pixel Dust.
I'm guessing with a little bit of work these roms will be just fine....:good:
Root also works as it should, as your booting to a rooted system....

Thanks to you both for your testing on GSI roms.
If you report the bugs with logcat to phh telegram group i suppose he will fix it for sure.

NisseGurra said:
I got my S10E to boot phh's v112 gsi, backlit broken so screen very dim, some other bugs to: some settings and apps crash.
How to:
Make sure you have an exynos version
Have an stock rom installed, bootloader unlocked and rebooted into stock and make sure oem unlocking in greyed out in dev settings.
Install recovery (latest fixed version)
Use multidisabler and format data (https://forum.xda-developers.com/galaxy-s10/development)
Reboot recovery
Install GSI, A/B version
Mount system and use TWRP file explorer to delete rw-system.sh in system/bin
Reboot , may need to press power, volume up and bixby few sec in inital boot.
Click to expand...
Click to collapse
So its the A/B not the A only version right?
I was getting bootloops every time i try to install a GSi.

uvitor said:
So its the A/B not the A only version right?
I was getting bootloops every time i try to install a GSi.
Click to expand...
Click to collapse
Yes, s10X uses a/b gsi's

NisseGurra said:
Yes, s10X uses a/b gsi's
Click to expand...
Click to collapse
Thanks. By the way, do we stilll have the magisk after GSi? In other words, as of S10 now have restriction on installation of magisk into system partition and it has to be installed into recovery partition, (the Method using Ian's patched TWRP and Magisk), how GSi interact with root and TWRP?
Thanks in advance.

uvitor said:
Thanks. By the way, do we stilll have the magisk after GSi? In other words, as of S10 now have restriction on installation of magisk into system partition and it has to be installed into recovery partition, (the Method using Ian's patched TWRP and Magisk), how GSi interact with root and TWRP?
Thanks in advance.
Click to expand...
Click to collapse
Gsi do not touch recovery or magisk, maybe needed to patch recovery.img with magisk to be able to boot tho

Duncan1982 said:
Pixel Dust ......
Just testing out one more, they both boot fine (Pixel Experience & Pixel Dust). ..
Obviously Fingerprint Scanner is non functional also the same brighteness bug (cannot adjust).
Here are some screens of Pixel Dust.
I'm guessing with a little bit of work these roms will be just fine....:good:
Root also works as it should, as your booting to a rooted system....
Click to expand...
Click to collapse
You can control thé brightness with modifying a build.prop setting just check the git issue on phh site.
Do you mean with last (fixed ?) twrp, can we power off the phone without bootloop ? [emoji16]

thebigtross said:
You can control thé brightness with modifying a build.prop setting just check the git issue on phh site.
Do you mean with last (fixed ?) twrp, can we power off the phone without bootloop ? [emoji16]
Click to expand...
Click to collapse
Yes booting is fine. Can you link the issue please, i cant seem to find it. Thanks.

sir-harlekin said:
Yes booting is fine. Can you link the issue please, i cant seem to find it. Thanks.
Click to expand...
Click to collapse
+1, i don't think it can be fixed by build.prop.

NisseGurra said:
+1, i don't think it can be fixed by build.prop.
Click to expand...
Click to collapse
Tweak
/sys/class/backlight/panel0-backlight/brightness
/sys/class/leds/lcd-backlight/brightness
Or Try
setprop persist.sys.qcom-brightness 255
And reboot
Or getprop |grep brightness to get value

thebigtross said:
Tweak
/sys/class/backlight/panel0-backlight/brightness
/sys/class/leds/lcd-backlight/brightness
Or Try
setprop persist.sys.qcom-brightness 255
And reboot
Or getprop |grep brightness to get value
Click to expand...
Click to collapse
How do you get root after flash GSI? I used the TWRP(and Magisk) pached by Ian's method and got root on Stock after install the MAgisk Mananger also patched by ian. After flash any GSi, i loose root and im not able to install any magisk manager.

uvitor said:
How do you get root after flash GSI? I used the TWRP(and Magisk) pached by Ian's method and got root on Stock after install the MAgisk Mananger also patched by ian. After flash any GSi, i loose root and im not able to install any magisk manager.
Click to expand...
Click to collapse
Twrp is root, so if you reboot by the method you should be aware of then you'll be booted into a rooted system :good:

uvitor said:
How do you get root after flash GSI? I used the TWRP(and Magisk) pached by Ian's method and got root on Stock after install the MAgisk Mananger also patched by ian. After flash any GSi, i loose root and im not able to install any magisk manager.
Click to expand...
Click to collapse
Flash magisk ou supersu from twrp as usally.
Not the patched or prepatched provided file lol.
Else some aosp roms are prerooted with supersu. They are tagged *-su* in filename

NisseGurra said:
Gsi do not touch recovery or magisk, maybe needed to patch recovery.img with magisk to be able to boot tho
Click to expand...
Click to collapse
does that mean the Snapdragon USA version can try it?
sorry, I am new to rooting

vonDubenshire said:
does that mean the Snapdragon USA version can try it?
sorry, I am new to rooting
Click to expand...
Click to collapse
No, all us snapdragons have locked bootloaders, no root.

In the meantime, is someone running GSI as a daily driver?

sir-harlekin said:
In the meantime, is someone running GSI as a daily driver?
Click to expand...
Click to collapse
I am. BUT there are several bugs to be addressed such:
Not working:
Bluetooh/NFC
Fingerprint
Proximity sensor
Auto brightness (manual does)
MTP
Force closes on any app info in settings
Im using because the progect is very promising and phhusson is open to user's reports so, im trying exactly to do that feedback and speed up the development.

General Found TWRP 3.5.0 for Redmi K40 (POCO F3)

So I just found a TWRP 3.5.0 file (I don't know who made this) from QQ ydss (China). Yeah I actually doing a leaking this file for you guys so you could have a try if you want to
Download here (GDrive)
Translated from Chinese:
The model structure is the factory (OEM) Android 11's structure. Partition structure is the latest virtual-A/B and doesn't have recovery partition, this is a special point.
Support latest Magisk Root.
This is the first beta build, please use the command "fastboot boot xxxx.img" to start using the recovery.
Support Dynamic Partition Plugins, auto-decrypt is not supported, you need to format Data to access to Data manually.
Sorry for bad English!
P/S: I will not response as your device is bricked, do it at YOUR OWN RISK

Link is working now, I forgot to enable public sharing, sorry guys

now not unlock phone still wait unlock to test

waiting for the 7-day restriction xiaomi bleat lifting

twrp boots up but this IT does not support decryption yet. You can't install anything yet

Chinese K40 users have done twrp3.5. They can swipe the temporary image of twrp into the mobile phone, but they can't decrypt it. I try to format the data and use the computer's ADB push / sacrd/ xx.zip It will prompt that the mobile phone is out of space

And does the version work?

bringchen said:
Chinese K40 users have done twrp3.5. They can swipe the temporary image of twrp into the mobile phone, but they can't decrypt it. I try to format the data and use the computer's ADB push / sacrd/ xx.zip It will prompt that the mobile phone is out of space
Click to expand...
Click to collapse
It just the interface test for sure, and flash is pretty useless right now until there would be a ROM support it
And that's could be a long while that we have to waiting for big-hands devs

CHGICEMAN said:
And does the version work?
Click to expand...
Click to collapse
Of course bruh, how could I put here if it doesn't work??

DumbHokage said:
Of course bruh, how could I put here if it doesn't work??
Click to expand...
Click to collapse
and why is everyone saying that this twrp has no decryption and does not work? who is lying?

any update to this version sir?

Hey, guys, has anyone tried this twrp to read USB devices?

T-HeaD said:
and why is everyone saying that this twrp has no decryption and does not work? who is lying?
Click to expand...
Click to collapse
And don't u read the italic description above???

Hopefully there is an official twrp

This recovery working properly, I got the phone on March 4 and unlocked it on March 13 and used this to flash into magisk.
It can't unlock the data partition, but you can use otg to flash zip.

Alpha Another said:
This recovery working properly, I got the phone on March 4 and unlocked it on March 13 and used this to flash into magisk.
It can't unlock the data partition, but you can use otg to flash zip.
Click to expand...
Click to collapse
Wow how can you get the phone that early, is literally the sametime those reviewers are getting the phone to be tested.

When do we can expect an offical TWRP version?

bl3d2death said:
When do we can expect an offical TWRP version?
Click to expand...
Click to collapse
It probably never will,
they are not even for older models

DeathStroke47 said:
This twrp is ****. It can't flash xiaomi.eu rom from otg.
Click to expand...
Click to collapse
Ure stupid, it's a fastboot option not a flashable rom.
Please applaud me

............delete

Development [CLOSED] Deleted

Deleted

Does this need a12 firmware? If so you should post dtbo and vendor_boot images.

gillim74 said:
Does this need a12 firmware? If so you should post dtbo and vendor_boot images.
Click to expand...
Click to collapse
wait for official Update

The boot image isnt working at all, after restarting into recovery mode i end up in bootloader. im on the latest oos 11 (11.2.10.10 BA)
edit:
sadly there are no install instructions on how to flash, found out that oos 12 is needed and the flash files are in the download repo (Image files folder)

A - Reboot to bootloader
fastboot flash dtbo "dtbo.img"
fastboot flash vendor_boot "vendor_boot.img"
fastboot flash boot "boot_img"
B - Fastboot reboot recovery
Perform factory data reset
Apply update from sideload
adb sideload "file name.zip"
C -Reboot system

OnePlus 9 Pro (lemonadep) of Project Elixir has been dropped due to bad behavior of the maintainer.
So no more official support and we recommend not to flash builds which isn't available in OFFICIAL website.

Flashed yesterday without any issues. To get the boot, vendor_boot, and dtbo i used payload extraction. Changelog states CTS to pass by default, however it fails until Zygisk is enabled. Custom FOD icons are not working. Audio & mic (oos12) bug is present. Flashed BluSpark kernel about an 1hr. ago. Without issue.
Overall seems to be very stable with many options! Great Job! LE2125.

Flashed this but was having issues with haptic/vibrate feedback, they're not working.

Fyi BluSpark kernel fixes this

Advali said:
Flashed this but was having issues with haptic/vibrate feedback, they're not working.
Click to expand...
Click to collapse

cave.man1908 said:
Fyi BluSpark kernel fixes this
Click to expand...
Click to collapse
Bluspark doesn't work on LE2120. Already tried this 3x and it f'd up my phone and had to reinstall again.

Absolutely gorgeous ROM! Do I understand that I can flash this coming from OOS12 without the need to downgrade to android 11?
If so, can somebody please explain what changed since the first A12 ROMs were released as they warned against flashing from OOS12 directly.

Reremoll said:
Absolutely gorgeous ROM! Do I understand that I can flash this coming from OOS12 without the need to downgrade to android 11?
If so, can somebody please explain what changed since the first A12 ROMs were released as they warned against flashing from OOS12 directly.
Click to expand...
Click to collapse
Yes you flash this over OS12. make sure u have OS12 on both slots(if ur on c48 just download and local update once again to have on both sides). Then u have to download this rom, extract it on ur pc, so u can flash(in fastboot) dtbo, vendor_boot and boot. Then boot to recovery, wipe and adb sideload rom.

blu-spark kernel doesn't work on this rom, tried it. But it seem unfortunately it doesn't work on this rom.

break.cold said:
blu-spark kernel doesn't work on this rom, tried it. But it seem unfortunately it doesn't work on this rom.
Click to expand...
Click to collapse
I flashed BluSpark to elixir yesterday without issue. Weird. Im le2125

I've tried 4 roms yday and blu spark sometimes make you bootloop or doesn't want to flash which is weird.
After a few rom re-installs it worked on every rom I tried.

cave.man1908 said:
I flashed BluSpark to elixir yesterday without issue. Weird. Im le2125
Click to expand...
Click to collapse
I tried blu-spark of StagOS, Pixel Extended, Project ELixir, it keep sending me back to fastboot menu, however, its works on riceDroid without issue.

OnePlus 9 Pro (lemonadep) of Project Elixir has been dropped due to bad behavior of the maintainer.
So no more official support and we recommend not to flash builds which isn't available in OFFICIAL website.

sourav24071999 said:
OnePlus 9 Pro (lemonadep) of Project Elixir has been dropped due to bad behavior of the maintainer.
So no more official support and we recommend not to flash builds which isn't available in OFFICIAL website.
Click to expand...
Click to collapse
Well, I wouldn't have had "bad behavior" if you weren't trying to control what I did with my own Telegram group.

MOD ACTION:
Thread closed since OP has been edited removing content.