Related
Once again I am stuck in same situation.*
I can only boot on restored twrp backup.*
I cant boot on any other custom roms.*
It install perfectly but after i reboot it gets stuck on 1+ boot logo.*
op3lite
saultanised cm
cm14
be it any rom i am already on 3.2.7 firmware.*
Followed mega unbrick guide and restored stock partitions. the phone boots properly. but when i remove encryption via fastboot,phone doesnt boot after that. again i have to go through all unbrick guide. back to stock 3.1.2. none of the roms boot except twrp restore.*
I m totally fed up. Please help.
nikhilsnigam said:
Once again I am stuck in same situation.*
I can only boot on restored twrp backup.*
I cant boot on any other custom roms.*
It install perfectly but after i reboot it gets stuck on 1+ boot logo.*
op3lite
saultanised cm
cm14
be it any rom i am already on 3.2.7 firmware.*
Followed mega unbrick guide and restored stock partitions. the phone boots properly. but when i remove encryption via fastboot,phone doesnt boot after that. again i have to go through all unbrick guide. back to stock 3.1.2. none of the roms boot except twrp restore.*
I m totally fed up. Please help.
Click to expand...
Click to collapse
What twrp version are you using?
Piyush lalwani said:
What twrp version are you using?
Click to expand...
Click to collapse
latest official twrp
nikhilsnigam said:
latest official twrp
Click to expand...
Click to collapse
Can you give a try to nodded twrp and one more thing mount system before flashing any ROM.
Note: after decrypting if you want too boot into OOS you need to Flash SuperSU or otherwise the OOS will force encryption and that may create problem.
Piyush lalwani said:
Can you give a try to nodded twrp and one more thing mount system before flashing any ROM.
Note: after decrypting if you want too boot into OOS you need to Flash SuperSU or otherwise the OOS will force encryption and that may create problem.
Click to expand...
Click to collapse
I did that already. after flashing supersu immediately then also stuck at boot screen. tried with modded twrp too 3.0.2.22
Piyush lalwani said:
Can you give a try to nodded twrp and one more thing mount system before flashing any ROM.
Note: after decrypting if you want too boot into OOS you need to Flash SuperSU or otherwise the OOS will force encryption and that may create problem.
Click to expand...
Click to collapse
okay now after few trial and error method i have come to the conclusion that this happens only after unencrypting the device. after eunencrypting it wont boot any other roms except those which have been already backed up.
So,
can i flash roms on encrypted device? I mean i test a lot of roms and i change frequently.
I guess no, right?
Yes try with encryption as the ROMs doesn't require decrypting the device. Decrypted device is only required if you want to use multirom.
Good Luck.
Piyush lalwani said:
Yes try with encryption as the ROMs doesn't require decrypting the device. Decrypted device is only required if you want to use multirom.
Good Luck.
Click to expand...
Click to collapse
but every time we try to reboot in recovery it asks for password to decrypt.
and if i enter default password storage shows only 32gb. that is strange
nikhilsnigam said:
but every time we try to reboot in recovery it asks for password to decrypt.
and if i enter default password storage shows only 32gb. that is strange
Click to expand...
Click to collapse
In nodded recovery too?
Piyush lalwani said:
In nodded recovery too?
Click to expand...
Click to collapse
going to try with modded recovery this time
nikhilsnigam said:
going to try with modded recovery this time
Click to expand...
Click to collapse
Yeah give a try
Piyush lalwani said:
Yeah give a try
Click to expand...
Click to collapse
how does modded recovery helps in this btw?
hope it works
OK So I am able to flash any rom with encrypted storage and latest modified twrp.
This is working for me right now but still haven't found solution why it wouldn't work on unencrypted storage.
Thank you.
This guide solved everything
http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-decryption-ultimate-guide-t3497940
Getting error 1
I'm on open beta 20
Elimental x kernel
Bluespak recovery
Any solution please
Amar5373 said:
Getting error 1
I'm on open beta 20
Elimental x kernel
Bluespak recovery
Any solution please
Click to expand...
Click to collapse
Well what have you tried? Do you have SuperSU installed? If so you can't flash Magisk over it..
Yes I was flashed super su?
Puddi_Puddin said:
Well what have you tried? Do you have SuperSU installed? If so you can't flash Magisk over it..
Click to expand...
Click to collapse
Bt before that get Same ploblem
Amar5373 said:
Bt before that get Same ploblem
Click to expand...
Click to collapse
I have no clue what you are trying to say.
Do you mean: "When I didn't flash Supersu I got the same problem?". If so dirty flash your rom, flash Magisk and see if it persists. May I also know your Rom setup
I have the same issue with my OP3
I have tried every possible way
I even flashed the rom and then reboot to flash magisk but didnt work either
I could flash v12
but v13.xx didnt work
Anas Qiblawi said:
I have the same issue with my OP3
I have tried every possible way
I even flashed the rom and then reboot to flash magisk but didnt work either
I could flash v12
but v13.xx didnt work
Click to expand...
Click to collapse
Same with me bro....
Magisck 12 working...?
Magisk 13.3 soft brick my phone, after reboot, my oneplus 3 stuck at boot loading. After I uninstall Magisk, everything is OK.
So I rooted and I am having 2 issues.
1. When ever I boot I get a message stating my phone has internal problems?..
How do I fix/remove this message
2. When I chose magisk to test safety net it FC running 14.5 if I update magisk keeps FC won't even update..
How do i check for safety net?.
Thanks in advance.
egren58 said:
So I rooted and I am having 2 issues.
1. When ever I boot I get a message stating my phone has internal problems?..
How do I fix/remove this message
2. When I chose magisk to test safety net it FC running 14.5 if I update magisk keeps FC won't even update..
How do i check for safety net?.
Thanks in advance.
Click to expand...
Click to collapse
The message is actually harmless. It's due to magisk patching the stock kernel. I would flash a custom kernel, like Flash kernel from here....
https://forum.xda-developers.com/pixel-2-xl/development/taimen-flash-kernel-1-00-t3702057
And then flash magisk 16.0. Both of them in TWRP. Disable your lock screen security first before you enter twrp. Then flash the kernel, and then magisk. Then all should be good :good:
Badger50 said:
The message is actually harmless. It's due to magisk patching the stock kernel. I would flash a custom kernel, like Flash kernel from here....
https://forum.xda-developers.com/pixel-2-xl/development/taimen-flash-kernel-1-00-t3702057
And then flash magisk 16.0. Both of them in TWRP. Disable your lock screen security first before you enter twrp. Then flash the kernel, and then magisk. Then all should be good :good:
Click to expand...
Click to collapse
This works?.
egren58 said:
This works?.
Click to expand...
Click to collapse
It's what most of us do all the time. Don't seen why it wouldn't
Badger50 said:
It's what most of us do all the time. Don't seen why it wouldn't
Click to expand...
Click to collapse
Will try
egren58 said:
Will try
Click to expand...
Click to collapse
If it hangs up at the white Google screen for a while, just do a hard reset with the power button :good:
My preference is for the ElementalX kernel - it comes with a cool management app - and battery tracking.
Sent from my Pixel 2 XL using XDA Labs
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
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.