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
Related
Hello guys,
As stated in the title, I can not boot into recovery since I flashed CM 14.1. I already tried reflashing TWRP, booting TWRP via fastboot, using another, more recent TWRP image.
This is rather urgent, since, although I can boot CM 14.1 without any problem, I forgot to do a Titanium Backup of two apps, so I have to restore a nandroid backup to get those back, which is kind of hard, without access to TWRP. Using TWRP Explorer is out of question, since that, as far as I know, does not work with encrypted backups.
Flashing via Flashify does not work either.
I just tried with the most recent CM Recovery, that does work, but that does not really help, since that won't restore TWRP Backups..
Greetings
jcgruenhage
delete
Just flash twrp again!?
Flash the twrp in the following link https://www.androidfilehost.com/? using flashify from play store .This helped me
daleski75 said:
Just flash twrp again!?
Click to expand...
Click to collapse
That did not work, at least not with the official TWRP. Flashing this TWRP gave me TWRP back, but now restoring the Backup somehow did not work as expected, the old CM 14.1 unofficial build that is in that backup won't boot.
I'll try only restoring the data part onto the official build, is there anything else you can recommend? Another firmware? Something?
Oh and by the way, thank you, for helping here and for you CM 14.1 builds, somehow I couldn't build CM 14.1 and 14, so having your builds was really helpful.
What version of OOS was you on prior to flashing CM14.1?
daleski75 said:
What version of OOS was you on prior to flashing CM14.1?
Click to expand...
Click to collapse
Directly upon receiving my OP3 I flashed CM13, that was in August, so 3.2.4 I guess, and I flashed the firmware of 3.2.6 before flashing Takers and your CM14 and later 14.1 builds.
TWRP behaves funny, the progress of restoring Data is already at 138%, 6800MB of 4899MB, the calculation is not taking compression into account I guess?
LOOOL, I have booted into the official CM14.1 with the old data, no fc or anything, but my pattern does not work anymore. same pattern as before, won't be accepted.
Never seen that issue before what happens if you reboot into the bootloader and then connect the phone to your pc and type fastboot boot <name of recovery> does it boot up?
Of course replace the < > with the name of the img file.
daleski75 said:
Never seen that issue before what happens if you reboot into the bootloader and then connect the phone to your pc and type fastboot boot <name of recovery> does it boot up?
Of course replace the < > with the name of the img file.
Click to expand...
Click to collapse
Yes, TWRP works now, but the backed up unofficial CM 14.1 does not boot.
But, only this TWRP works, booting the official TWRP does not work.
I could probably just use the TWRP file manager to extract the few files from the data partition that I need, but this is a workaround and not a fix, and that is not desired in most cases. Fixing it is hard without someone that still has a broken system.
jcgruenhage said:
Yes, TWRP works now, but the backed up unofficial CM 14.1 does not boot.
But, only this TWRP works, booting the official TWRP does not work.
I could probably just use the TWRP file manager to extract the few files from the data partition that I need, but this is a workaround and not a fix, and that is not desired in most cases. Fixing it is hard without someone that still has a broken system.
Click to expand...
Click to collapse
Yup thats the one I am using as well.
daleski75 said:
Yup thats the one I am using as well.
Click to expand...
Click to collapse
Do you know how one would debug something like that? I have nothing but the splash screen in the beginning and then a black screen
I will just flash CM 14.1 and manually extract my OTP tokens from the data backup, so I don't really need to debug that, but it would probably help determine the cause and properly fix it for the future.
Ask for the link
daleski75 said:
Yup thats the one I am using as well.
Click to expand...
Click to collapse
May I ask which one? the link is dead ...
I am having the same problem, i can't boot into recovery and cant find a way to flash it.
Can someone explain me how to?
ChrisDiM said:
I am having the same problem, i can't boot into recovery and cant find a way to flash it.
Can someone explain me how to?
Click to expand...
Click to collapse
Sorry to hear that. You have to use Qualcomm Drivers to reset your cellphone
Same issue here. Whenever I try to boot into recovery it just goes straight back to the bootloader/fastboot.
**** me, what do I do?
I try "fastboot format userdata" but after i have the same problem with TWRP-3.0.2-1.28
jackalsin said:
Sorry to hear that. You have to use Qualcomm Drivers to reset your cellphone
Click to expand...
Click to collapse
I just found a guide to reset my phone using Qualcomm but my phone doesn't show up on device manager + since this morning my op3 doesn't start up anymore and doesn't react when i plug the charger in.
ChrisDiM said:
I just found a guide to reset my phone using Qualcomm but my phone doesn't show up on device manager + since this morning my op3 doesn't start up anymore and doesn't react when i plug the charger in.
Click to expand...
Click to collapse
Hold power button for at least a minute. It's what I did and fixed it.
DevSquad said:
Hold power button for at least a minute. It's what I did and fixed it.
Click to expand...
Click to collapse
after doing this it showed the OP logo for a few seconds and shut off again :/
Its really a bad moment for me because i had to call a lot a people today and now i can't even start up my phone
ChrisDiM said:
after doing this it showed the OP logo for a few seconds and shut off again :/
Its really a bad moment for me because i had to call a lot a people today and now i can't even start up my phone
Click to expand...
Click to collapse
Can you get into fastboot?
If so, you can sideload a working TWRP via there.
So I've been trying to get magisk working for a while on Pixel XL and magisk version 11 still gives the unable to mount /system error.
Anyone find a workaround yet? Not being able to use Android Pay is annoying...
wireaudio said:
So I've been trying to get magisk working for a while on Pixel XL and magisk version 11 still gives the unable to mount /system error.
Anyone find a workaround yet? Not being able to use Android Pay is annoying...
Click to expand...
Click to collapse
Hey... Check the last paragraph of this post: https://forum.xda-developers.com/showpost.php?p=71502787&postcount=17 named "What's Next"
Cheers...
I've also been curious about this but everything I've read says it's just a matter of the dev of Magisk being able to implement into how the Pixel works. Looking forward to that *hopefully* happening sometime in the future!
bravesfan171 said:
I've also been curious about this but everything I've read says it's just a matter of the dev of Magisk being able to implement into how the Pixel works. Looking forward to that *hopefully* happening sometime in the future!
Click to expand...
Click to collapse
This is the exacts developer's words. It's been posted 23 hours ago:
topjohmwu said:
For the long awaited Pixel support, I think I'll start working on it, but the complexity of that device might take a very long time for me to understand, since I do not own the device. I can only borrow my friend's device for not that long of a period of time, so progress shall be really slow. I'll not get the Pixel device now, because I don't think it is worth the price and the hassle for me to import it into Taiwan, but I'll definitely get the Pixel 2 to replace my current daily driver lol.
Click to expand...
Click to collapse
Thanks guys! Much appreciated!
wireaudio said:
Thanks guys! Much appreciated!
Click to expand...
Click to collapse
Hello... Maybe take a look at this: https://forum.xda-developers.com/showpost.php?p=71573863&postcount=1029
Cheers...
Works perfectly. March Pure Nexus w/ PN kernel. Installed the V4A module too. Mario works. Pay works. Safety net passes 100%. Use TWRP RC2 and make sure to flash TWRP again after flashing Magisk.
funkybrunk said:
Works perfectly. March Pure Nexus w/ PN kernel. Installed the V4A module too. Mario works. Pay works. Safety net passes 100%. Use TWRP RC2 and make sure to flash TWRP again after flashing Magisk.
Click to expand...
Click to collapse
I'm getting an error when installing Magisk 11.6 on the Pixel, says:
"Updater process ended with Error: 1
Error installing zip file Magisk-v11.6-Pixel.zip"
Anyone else run into this with a fix?
----------------------------------------------------
Just wiped everything, still no go.
Getting the exact same error. This seems like an error with TWRP or the zip file I'm using.
The error pops up during the "Unpacking boot image" stage.
You need to used TWRP RC2. Your errors are because you are on RC1
funkybrunk said:
You need to used TWRP RC2. Your errors are because you are on RC1
Click to expand...
Click to collapse
So I'm using PN with EX kernel. Does magisk work with EX? Just flash the rc 2 zip while on RC 1?
318sugarhill said:
So I'm using PN with EX kernel. Does magisk work with EX? Just flash the rc 2 zip while on RC 1?
Click to expand...
Click to collapse
Yes it works on PN, and yes it will work with EX but EX doesn't give you the same options in aroma (as SuperSU) because it isn't recognizing magisk root.
pcriz said:
Yes it works on PN, and yes it will work with EX but EX doesn't give you the same options in aroma (as SuperSU) because it isn't recognizing magisk root.
Click to expand...
Click to collapse
Ok thanks. Will flashing the PN Rom switch the kernel back. or will I have to flash that manually
318sugarhill said:
Ok thanks. Will flashing the PN Rom switch the kernel back. or will I have to flash that manually
Click to expand...
Click to collapse
PN has its own kernel so I am assuming yes it will.
pcriz said:
PN has its own kernel so I am assuming yes it will.
Click to expand...
Click to collapse
Ok. Hopefully dirty flashing will just reset the kernel
318sugarhill said:
Ok. Hopefully dirty flashing will just reset the kernel
Click to expand...
Click to collapse
I should've been more definitive in my answer. Yes it will replace the kernel when you flash the rom, my bad.
I was using pure Nexus with Ex kernel....I flashed PN Rom (dirty flash) just to reset kernel....Flashed TWRP RC1 zip zip....Reboot system, then reboot recovery and flashed TWRP RC2 zip, reboot system, reboot to recovery flashed Magisk then reboot system again. Reboot to recovery flashed vendor img for PN and all is good. Enabled magisk hide in magisk app settings.....Then under magisk hide I hid it from DirecTV Now app. All safety net tests pass. Needed a build prop edit for directTV now to work correctly but all other apps blocked because of root are now working.
Thanks for the assistance
Does magisk work on 7.1.2?
Sent from my Pixel XL using Tapatalk
bb12489 said:
Does magisk work on 7.1.2?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Working fine for me with Latest ElementalX Kernel
liam_davenport said:
Working fine for me with Latest ElementalX Kernel
Click to expand...
Click to collapse
Good deal. What do you think would be the best way to update to 7.1.2? I have TWRP recovery and elementalX at the moment. Should I flash stock boot.img, then update? I Imagine I would have to flash magisk again though.
Sent from my Pixel XL using Tapatalk
has anyone gotten any of the modules to work ?
Hello,
This one is a funny one, as on my OnePlus 2 rooting was easy but ever since I got my OnePlus 5T I've always had issues, rooting it in the first place was troublesome but managed to get Magisk running with OOS and I have decided to migrate to Resurrection Remix (What I used to run on OnePlus2) when I format my data and flash RR and gapps it runs perfectly fine, but when I flash Magisk it states it has successfully changed the boot.img and when I restart the system it ends up going to the bootloader, I can then run the Magisk uninstaller and my RR will run normally again.
Magisk definitely seems to be the issue but I don't know why, I have gone back to stock firmware and locked my bootloader and tried again from stock and still, after installing the latest RR with Magisk after the first initialisation I get no errors it just doesn't boot.
Has anyone got any idea of what I could do wrong, I have found myself following guides online with no luck. As no one seems to have an issue similar.
An advice?
As far as I know.magisk should be flashed only after booting into system and completing the initial setup
Hi dude,
maybe you will find your answer in this thread!
https://forum.xda-developers.com/on...x-os-6-0-0-t3747038/post76922486#post76922486
rakuyo said:
As far as I know.magisk should be flashed only after booting into system and completing the initial setup
Click to expand...
Click to collapse
I do install it after the intial set up and it still doesn't load :/
nicorvienne said:
Hi dude,
maybe you will find your answer in this thread!
https://forum.xda-developers.com/on...x-os-6-0-0-t3747038/post76922486#post76922486
Click to expand...
Click to collapse
Thanks this was my solution, just needed to flash a custom kernel.
NarcoticNoble said:
Thanks this was my solution, just needed to flash a custom kernel.
Click to expand...
Click to collapse
You are welcome!
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.
/!\ DISCLAIMER
I'am not responsible for bricked device, dead eMMC or anythings else
and if you flash TWRP, your warranty is now void (Not if you live in Europe and the breakage is not because of the root).
If you have a problem, I am regularly here and a whole forum can help you.
(Pls dont blame my english it isnt my fisrt language)
We know, rooting this phone is kinda..... difficult, he as the imei problem, magisk wont work if u flash it on twrp.
But i will show you in this thread how to root him sucessfully and install a gsi and root it. Lets go
I have 2 method : flash from twrp (for keeping the stock firmware) or flashing magisk with odin3 (for GSI)
1. Lets go on the first method:
You need to install TWRP --> TWRP
You need to download magisk CANARY ( At the end of the post)
Put it in your phone and boot TWRP
Flash it, format data and reboot your phone
(With the A325FXXU2AVC2 firmware you probably dont gonna have problem but if your imei die -->IMEI fix)
Install the magisk app and in settings, select canary channel
Update magisk app and the root
2. The second method :
You need to root your device with odin and magisk
-> Take your firmware on samfw (A325FXXU2AVC2 if u can) patch the AP on the magisk app and flash it in odin with BL,CP,CSC without auto reboot
Shutdown your phone and reboot in DL mode and flash TWRP
Reboot into TWRP
Flash a GSI (Go in "install", "install image" click on your .img and flash to system image), I give here one --> crDroid (if you dont have a sdcard, just pull gsi in the storage via MTP on twrp)
Format data
(If you want Gapps and your GSI dont have it, you need to flash it (open gapps, etc) but the system partition is too small, do that in a linux shell : e2fsck -f <your gsi.img> and resize2fs <your gsi.img> 4G and reflash the GSI)
Install magisk app
And voila, you sucessfully root your Samsung Galaxy A32
I hope this post can help anyone
Edit: I forgot to say : Go in phh settings and select "Use alternate way to detect headphone" in Misc, for 90Hz display go to Misc and select "Force FPS" and select 90Hz, go to Samsung and enable "Extend Brightness range", "Use alternate audio policy" and (for better photo) "Access to all camera" and finally go to Misc and enable "Force enable Camera2API HAL3" and "Expose aux camera".
What doesnt work:
Fingerprint reader
MTP (use adb instead, app with a GUI : Python adb file explorer GUI
GSI dont boot with encryption enabled
Credit and thanks to :
@Prove N. for his TWRP (you saved us)
Magisk developers for the root
@dronkit for fix the imei issue
And XDA developers and all the staff
Have a good day and bye bye
Do in need a SD card so that i can put the gsi to the sd card?
Franzyy said:
Do in need a SD card so that i can put the gsi to the sd card?
Click to expand...
Click to collapse
you dont need because you flash the and after you format data, you can just pull it on the phone storage via MTP TWRP
how well does crDroid performs on this device? does it lag? do you have any screenshots?
bmDomianatezz said:
how well does crDroid performs on this device? does it lag? do you have any screenshots?
Click to expand...
Click to collapse
I'm actually using crDroid on this phone and its almost perfect, no lag, its working nice, the style is good. Tell if you want more screenshot.
Can you port lineage os?
Hilmi Ridho said:
Can you port lineage os?
Click to expand...
Click to collapse
youre meaning the GSI?
kilam9900 said:
I'm actually using crDroid on this phone and its almost perfect, no lag, its working nice, the style is good. Tell if you want more screenshot.
Click to expand...
Click to collapse
huh? no lag? wtf its lagging intensely for me. what did you flash tell me everything i hate one ui for the lag on this phone i am gonna switch back!
Captain_cookie_200 said:
huh? no lag? wtf its lagging intensely for me. what did you flash tell me everything i hate one ui for the lag on this phone i am gonna switch back!
Click to expand...
Click to collapse
i tried Arrow OS 12.1, Crdroid 8.8, Crdroid 8.9, lineageos 19.1, Xdroid and many other roms. They all lag alot.
Captain_cookie_200 said:
i tried Arrow OS 12.1, Crdroid 8.8, Crdroid 8.9, lineageos 19.1, Xdroid and many other roms. They all lag alot.
Click to expand...
Click to collapse
what? they doesnt lag, i tried lineage too, lineage is not the best but crdroid doesnt lag
kilam9900 said:
what? they doesnt lag, i tried lineage too, lineage is not the best but crdroid doesnt lag
Click to expand...
Click to collapse
what the hell? you use gesture navigation right? it doesnt lag while scrolling or when coming to home screen? im using the exact same model so why is it like that for me...? what firmware are you on and did you flash anything extra?
Captain_cookie_200 said:
what the hell? you use gesture navigation right? it doesnt lag while scrolling or when coming to home screen? im using the exact same model so why is it like that for me...? what firmware are you on and did you flash anything extra?
Click to expand...
Click to collapse
its lagging to a point where the phone just feels like a 30Hz phone
kilam9900 said:
what? they doesnt lag, i tried lineage too, lineage is not the best but crdroid doesnt lag
Click to expand...
Click to collapse
do you clean flash
Captain_cookie_200 said:
what the hell? you use gesture navigation right? it doesnt lag while scrolling or when coming to home screen? im using the exact same model so why is it like that for me...? what firmware are you on and did you flash anything extra?
Click to expand...
Click to collapse
Yes i use gesture, it doesnt lag while scrolling, i have flash crdroid 8.9 slim and magisk with some module but not for performance (except ram swapper)
Captain_cookie_200 said:
its lagging to a point where the phone just feels like a 30Hz phone
Click to expand...
Click to collapse
Are you forcing 90Hz display? do you clean flash?
i dont know if magisk help but i dont think so
kilam9900 said:
i dont know if magisk help but i dont think so
Click to expand...
Click to collapse
what i did is download the non slim version i'll try to slim version today. but yeah it was a total clean flash on the latest firmware as well. i also have magisk and i dont have ram swapper installed. i'll try to slim version and give an update hopefully it becomes smoother
Captain_cookie_200 said:
what i did is download the non slim version i'll try to slim version today. but yeah it was a total clean flash on the latest firmware as well. i also have magisk and i dont have ram swapper installed. i'll try to slim version and give an update hopefully it becomes smoother
Click to expand...
Click to collapse
okay
kilam9900 said:
youre meaning the GSI?
Click to expand...
Click to collapse
I mean custom rom
Hilmi Ridho said:
I mean custom rom
Click to expand...
Click to collapse
Actually A32 havent custom rom (i think) but you can use gsi. Lineage for exemple : https://sourceforge.net/projects/an...UNOFFICIAL-arm64_bgS-vndklite.img.xz/download
kilam9900 said:
okay
Click to expand...
Click to collapse
hey where did you get the swap ram module from? i just want to make sure i install the same. i installed crdroid 8.9 while the animations are better they are not the smoothest and the glitching still happens.