Stock rom issues, BL unlocked no more OTA updates [Help/Advice?] - Lenovo P2 Questions & Answers

Hi guys,
I am using the stock rom now since the day I got it and unlocked the BL and installed Magisk for root and SafetyNet. Phone worked fine all the time (lazy me never changed the rom) until recent.
Most applications like Instagram, Snapchat (and all that garbage) and others randomly crash recently.. Application stopped working or process.media whatever stopped. Did try to do the usual stuff removing cache, but now this also does not work anymore. Also it's time to update because the WiFi driver has this RCE flaw(CVE-2017-13292) in it and well, lots of other bugs in the rom. The most irritating bugs that all my android devices had. The flashlight stops working because of the camera initialization or something, need to reboot the phone in order to use the flashlight again (when I was with a hot soldering iron in my car waiting for the device to reboot to solder some ****ing wires under the dashboard pissed me off really good. Though long time ago, but you get the idea... )
I did try to update my device using OTA (I knew it wasn't going to work, because mine is rooted). I did try it and the update failed(lol), luckily the phone still booted :cyclops:
What should I do now, can I just flash a stock rom using twrp or is there another stable rom that is clean like the lenovo roms without all the garbish? Which ones are advised?
The version of the rom I am using as of now is in my signature. I do not really need Magisk anymore for now, I had it installed mostly for NFC emulator but the company I emulated the card for no longer exists so meh.. No need for emulating anymore Pachting ads away with luckypatcher is also not worth it and there's like no proper way of blocking ads so I'll rather live with it instead of messing around and putting effort in it.

NiTrOwow said:
Hi guys,
I am using the stock rom now since the day I got it and unlocked the BL and installed Magisk for root and SafetyNet. Phone worked fine all the time (lazy me never changed the rom) until recent.
Most applications like Instagram, Snapchat (and all that garbage) and others randomly crash recently.. Application stopped working or process.media whatever stopped. Did try to do the usual stuff removing cache, but now this also does not work anymore. Also it's time to update because the WiFi driver has this RCE flaw(CVE-2017-13292) in it and well, lots of other bugs in the rom. The most irritating bugs that all my android devices had. The flashlight stops working because of the camera initialization or something, need to reboot the phone in order to use the flashlight again (when I was with a hot soldering iron in my car waiting for the device to reboot to solder some ****ing wires under the dashboard pissed me off really good. Though long time ago, but you get the idea... )
I did try to update my device using OTA (I knew it wasn't going to work, because mine is rooted). I did try it and the update failed(lol), luckily the phone still booted :cyclops:
What should I do now, can I just flash a stock rom using twrp or is there another stable rom that is clean like the lenovo roms without all the garbish? Which ones are advised?
The version of the rom I am using as of now is in my signature. I do not really need Magisk anymore for now, I had it installed mostly for NFC emulator but the company I emulated the card for no longer exists so meh.. No need for emulating anymore Pachting ads away with luckypatcher is also not worth it and there's like no proper way of blocking ads so I'll rather live with it instead of messing around and putting effort in it.
Click to expand...
Click to collapse
Android Pie ROMs are pretty stable and usable now (everything works but be aware that all custom ROMs will have darker video recording in comparison to stock)
ROMs of choice:
On Oreo: RR(Unofficial final builds by fullbustah),CrDroid,Arrow or Xtended
On Pie: CrDroid(has an extended desktop bug), SuperiorOs,ArrowOs,AospExtented
I also recommend installing a modded Gcam version because that will significantly boost your camera quality without any throwback or setback.
To install a pie ROM, I have written a tutorial somewhere in our guides section. You will find it pretty quickly.
Also Magisk 18.1 (latest for now) and Adaway still blocks ads perfectly. (Systemless hosts enabled in Magisk settings needed)
I recommend joining Lenovo P2 telegram group for latest news, support and download links.

sm00th4f3 said:
Android Pie ROMs are pretty stable and usable now (everything works but be aware that all custom ROMs will have darker video recording in comparison to stock)
ROMs of choice:
On Oreo: RR(Unofficial final builds by fullbustah),CrDroid,Arrow or Xtended
On Pie: CrDroid(has an extended desktop bug), SuperiorOs,ArrowOs,AospExtented
I also recommend installing a modded Gcam version because that will significantly boost your camera quality without any throwback or setback.
To install a pie ROM, I have written a tutorial somewhere in our guides section. You will find it pretty quickly.
Also Magisk 18.1 (latest for now) and Adaway still blocks ads perfectly. (Systemless hosts enabled in Magisk settings needed)
I recommend joining Lenovo P2 telegram group for latest news, support and download links.
Click to expand...
Click to collapse
Alright thanks for the information. I will try to flash my phone next week. I do have one more question. Is there a hardware selftest or test menu in the stock recovery or bootloader because I have a bad feeling that my board might be about to fail. I think this because all kinds of funky things did happen the last few days (I hope the mainboard is still fine, fingers crossed).. I know my old Lenovo had this menu and this way I found out it was dead. Well it was obviously dead but for sure after the test failed because Android didn't boot anymore, and was not able to flash another rom and get that one to boot up.

NiTrOwow said:
Alright thanks for the information. I will try to flash my phone next week. I do have one more question. Is there a hardware selftest or test menu in the stock recovery or bootloader because I have a bad feeling that my board might be about to fail. I think this because all kinds of funky things did happen the last few days (I hope the mainboard is still fine, fingers crossed).. I know my old Lenovo had this menu and this way I found out it was dead. Well it was obviously dead but for sure after the test failed because Android didn't boot anymore, and was not able to flash another rom and get that one to boot up.
Click to expand...
Click to collapse
I'm not sure if the p2 owns a menu like that.
You might wanna boot to bootloader and navigate through the small menu via volumekeys.
But otherwise...no idea.
Good luck!

Related

Google-free ROM with working phone encryption wanted

Hi,
I have a LG G4 and use the stock ROM but want to get rid of google's observation and bloatware. I am looking for a custom ROM that focuses on privacy and runs stable on the LG G4.
It must
- be usable without Google
- provide a working full-phone encryption + SD card encryption like the stock ROM does
- provide fast updates (my stock rom has security level january 17 which is ridiculous)
I already tried LineageOS with the newest version and it worked well with one exception: I could not encrypt my phone. I tried it several times but I either got into a boot loop or Lineage OS booted but all my preferences and apps were lost (like I did a factory reset, but I didn't). When I then started TWRP recovery it asked me for my password and declined it altough it was 100% correct. The only possibility was to wipe all data and install LineageOS again. Very strange: I could also "encrypt" my phone without providing a PIN, password or something else. I would expect an error message to be displayed but there was none.
I also tried Ressurection Remix but the encryption failed as well (boot loop after encryption finished).
Could it be that TWRP causes these problems? Has anyone successfully intalled a custom ROM and encrypted the LG G4? Maybe another ROM? I am very open for new suggestions
For now I had to reinstall the stock ROM because that's the only way I can encrypt my phone...
Regards
maasG4
Does nobody care for encryption?
1984 is real, how can somebody just don't care?
How can encryption protect your privacy?
But you can use stock rom too.
Just reset phone, set it up without google account (you have to delete the accout before resetting fyi)
root it, use afwall and jdisable the common lg and google stuff.
Use floss open source apps from froid.
Thats it.
If you want to use stuff like network location without gapps the you have to use LOS. If you want more google stuff without google you have to use crdroid rom.
But I already tried and its a pain on the ass.
Lol yes encryption is something where many people say it's completely useless! I love those discussions where people say why do you care about encryption? Well it's their fault not mine I encrypt everything and always that's why I build TWRP with decryption support because no one else cares.
I use RR marshmallow plus FDE but I am about to switch to LOS 13 because of the security patches inside
Iirc (it's more than 1 year ago) it was a little bit tricky to set up because as you already noted nobody cares about encryption! everything like rooting or custom ROMs have all one thing in mind disable encryption and that's what's happening when you install root or when you use a custom ROM normally.
If you can wait until I have switched to LOS I could tell you more but I have no time frame for this so if you don't want to wait you should investigate the fstab file and if you're using Super su the installer scripts as well
.
Sent from my LG-H815 using XDA Labs
maasG4 said:
Hi,
I have a LG G4 and use the stock ROM but want to get rid of google's observation and bloatware. I am looking for a custom ROM that focuses on privacy and runs stable on the LG G4.
It must
- be usable without Google
- provide a working full-phone encryption + SD card encryption like the stock ROM does
- provide fast updates (my stock rom has security level january 17 which is ridiculous)
I already tried LineageOS with the newest version and it worked well with one exception: I could not encrypt my phone. I tried it several times but I either got into a boot loop or Lineage OS booted but all my preferences and apps were lost (like I did a factory reset, but I didn't). When I then started TWRP recovery it asked me for my password and declined it altough it was 100% correct. The only possibility was to wipe all data and install LineageOS again. Very strange: I could also "encrypt" my phone without providing a PIN, password or something else. I would expect an error message to be displayed but there was none.
I also tried Ressurection Remix but the encryption failed as well (boot loop after encryption finished).
Could it be that TWRP causes these problems? Has anyone successfully intalled a custom ROM and encrypted the LG G4? Maybe another ROM? I am very open for new suggestions
For now I had to reinstall the stock ROM because that's the only way I can encrypt my phone...
Regards
maasG4
Click to expand...
Click to collapse
Only one name in cellular phone is black phone 2 it uses military type encryption and if you lose it you can call up and make it explode........ Lol
Updates Mid 2018
Hi,
as I had no success last year when I wrote this post, I lost it out of sight. Now I would like to give it another try.
Unfortunately I cannot find any custom ROM with a current version that also supports LG G4. LineageOS supports a lot of phones but no G4, the same for RR OS.
Is there another alternative that officially supports LG G4 and also works with encryption?
If not, I think it is time to move from my loved G4 to another phone. I do not feel comfortable with a phone that got no updates for almost two years. This time, I would directly focus on finding a phone that gets regular updates (like the new Nokias, as far as I know) or has good support for custom ROMs (like Nexus/Pixel). Are there any suggestions for a phone that is comparable to my G4 (I especially love the camera) but supports current custom ROMs or has regular updates from the manufacturer?
Looking forward to any recommendations!
steadfasterX said:
If you can wait until I have switched to LOS I could tell you more but I have no time frame for this so if you don't want to wait you should investigate the fstab file and if you're using Super su the installer scripts as well
Click to expand...
Click to collapse
Have you already tried it?
Thanks!
maasG4 said:
Hi,
as I had no success last year when I wrote this post, I lost it out of sight. Now I would like to give it another try.
Unfortunately I cannot find any custom ROM with a current version that also supports LG G4. LineageOS supports a lot of phones but no G4, the same for RR OS.
Is there another alternative that officially supports LG G4 and also works with encryption?
If not, I think it is time to move from my loved G4 to another phone. I do not feel comfortable with a phone that got no updates for almost two years. This time, I would directly focus on finding a phone that gets regular updates (like the new Nokias, as far as I know) or has good support for custom ROMs (like Nexus/Pixel). Are there any suggestions for a phone that is comparable to my G4 (I especially love the camera) but supports current custom ROMs or has regular updates from the manufacturer?
Looking forward to any recommendations!
Have you already tried it?
Thanks!
Click to expand...
Click to collapse
Officially - cypher os supports your G4
Unofficially (but maintained by myself, @steadfasterX and @kessaras) you can choose from LineageOS, AICP, Cypher (newer versions with more patches - @kessaras is also the official Cypher maintainer so no difference there) and RR
Anything Oreo supports encryption - anything nougat doesn't
However, Oreo has a bug with BT calling - Calling through a BT headset doesn't work

Switching from SuperSU to MagiskSU

Okay so after getting tired of safetynet and other issues Google has put on us I'm wanting to switch to magiskSU but Everytime I tried I bootloop and have to clean flash my rom. This is what I'm doing
1. Flashed unSU in twrp
2.flashed stock boot.img
3. Flashed the magisk.zip
4.got an error saying it failed to install magisk.zip
But whenever I try to reboot to system (I've tried reinstalling SuperSU and without reinstalling as well) I got a bootloop Everytime can someone instruct me or tell me what I'm doing wrong?
WeUseLord- said:
Okay so after getting tired of safetynet and other issues Google has put on us I'm wanting to switch to magiskSU but Everytime I tried I bootloop and have to clean flash my rom. This is what I'm doing
1. Flashed unSU in twrp
2.flashed stock boot.img
3. Flashed the magisk.zip
4.got an error saying it failed to install magisk.zip
But whenever I try to reboot to system (I've tried reinstalling SuperSU and without reinstalling as well) I got a bootloop Everytime can someone instruct me or tell me what I'm doing wrong?
Click to expand...
Click to collapse
What carrier/rom/update/etc?
WeUseLord- said:
Okay so after getting tired of safetynet and other issues Google has put on us I'm wanting to switch to magiskSU but Everytime I tried I bootloop and have to clean flash my rom. This is what I'm doing
1. Flashed unSU in twrp
2.flashed stock boot.img
3. Flashed the magisk.zip
4.got an error saying it failed to install magisk.zip
But whenever I try to reboot to system (I've tried reinstalling SuperSU and without reinstalling as well) I got a bootloop Everytime can someone instruct me or tell me what I'm doing wrong?
Click to expand...
Click to collapse
In Short. Currently for our device to have magisk, you need to use the boot image that @joemossjr and @Uzephi developed with Magisk support. Then install the magisk app. No zip install.
Refer to Joe's thread for the boot image at this link
https://forum.xda-developers.com/z2-force/how-to/how-to-root-moto-z2-force-t-mobile-t3672933
I would have went into detail and used a short link, but my head is currently throbbing so this is easier lol.
Edit: then realized your replied a minute before I Uzephi haha.
Uzephi said:
What carrier/rom/update/etc?
Click to expand...
Click to collapse
Spring stock rom on the original August update
Sent from my Moto Z (2) Force using XDA Labs
Acoustichayes said:
In Short. Currently for our device to have magisk, you need to use the boot image that @joemossjr and @Uzephi developed with Magisk support. Then install the magisk app. No zip install.
Refer to Joe's thread for the boot image at this link
https://forum.xda-developers.com/z2-force/how-to/how-to-root-moto-z2-force-t-mobile-t3672933
I would have went into detail and used a short link, but my head is currently throbbing so this is easier lol.
Click to expand...
Click to collapse
I know but when I tried that method and just installing the boot.img through twrp it failed and gave me a boot loop as well
Sent from my Moto Z (2) Force using XDA Labs
WeUseLord- said:
Spring stock rom on the original August update
Click to expand...
Click to collapse
I would suggest updating to November. I have a rooted magisk image, but you need to flash the decryption zip to get it to boot. If you update to November, I am going to release a flash-all type zip sometime today (after I fiddle with getting 4.4.107 upstream done) and working on a Google Pixel 2 skinned ROM for us here shortly with oem bloat completely removed
WeUseLord- said:
I know but when I tried that method and just installing the boot.img through twrp it failed and gave me a boot loop as well
Sent from my Moto Z (2) Force using XDA Labs
Click to expand...
Click to collapse
Have to ask this general base question of course lol. are you trying to dirty flash or did you do a full clean install?
But in general, what Uzephi said, as this is his project. I'll let him go ahead and take over. Goodluck
WeUseLord- said:
I know but when I tried that method and just installing the boot.img through twrp it failed and gave me a boot loop as well
Click to expand...
Click to collapse
You using stock kernel? To get crypto changes in 4.4.101-103 added, it breaks encryption on our phones and will cause a boot loop due to Motorola's dirty code. Hopefully when Oreo ROM drops (since Google is kinda telling oems to stay upstreamed) it will fix those issues in our stock ROMs.
Uzephi said:
I would suggest updating to November. I have a rooted magisk image, but you need to flash the decryption zip to get it to boot. If you update to November, I am going to release a flash-all type zip sometime today (after I fiddle with getting 4.4.107 upstream done) and working on a Google Pixel 2 skinned ROM for us here shortly with oem bloat completely removed
Click to expand...
Click to collapse
That's nice I think I'm gonna stick with SuperSU for now this phone is confusing
But one thing I must ask will we have a customisable rom like CM or something like that soon?
Sent from my Moto Z (2) Force using XDA Labs
WeUseLord- said:
That's nice I think I'm gonna stick with SuperSU for now this phone is confusing
But one thing I must ask will we have a customisable rom like CM or something like that soon?
Click to expand...
Click to collapse
Hard to say. Those of us that have tried hard bricked the device. Not readable via USB and wouldn't boot anything after the flash.
WeUseLord- said:
That's nice I think I'm gonna stick with SuperSU for now this phone is confusing
But one thing I must ask will we have a customisable rom like CM or something like that soon?
Sent from my Moto Z (2) Force using XDA Labs
Click to expand...
Click to collapse
To build off what Uzephi said. It's not that rom's wont be capable. It's just working with new things that are being implemented and changed until something starts going right. The jump to Nougat changed a lot of things with security and the switch to Oreo is changing even more that Google is wanting to push for android that inadvertently also affect security and compatibility.
This is speculation, but since they introduced Kotlin, I feel like they are trying to alter everything over the long run to become more streamline and compatible around it. Especially given they can control the progress of the script language to help them better. Which will really show true or false come mid next year.
We are lucky that Motorola sticks to a super close to stock experience because it's one less issue to deal with when playing with the new code and functions to try to get things to work. I'm really optimistic on this stuff because I like doing things that people think can't be done. So I believe that there will for sure be more customization and capabilities as we figure things out. Just takes time and effort. We worked for months and months on the S8 where people said impossible, and ended up getting it. So i have faith on this.
Acoustichayes said:
To build off what Uzephi said. It's not that rom's wont be capable. It's just working with new things that are being implemented and changed until something starts going right. The jump to Nougat changed a lot of things with security and the switch to Oreo is changing even more that Google is wanting to push for android that inadvertently also affect security and compatibility.
This is speculation, but since they introduced Kotlin, I feel like they are trying to alter everything over the long run to become more streamline and compatible around it. Especially given they can control the progress of the script language to help them better. Which will really show true or false come mid next year.
We are lucky that Motorola sticks to a super close to stock experience because it's one less issue to deal with when playing with the new code and functions to try to get things to work. I'm really optimistic on this stuff because I like doing things that people think can't be done. So I believe that there will for sure be more customization and capabilities as we figure things out. Just takes time and effort. We worked for months and months on the S8 where people said impossible, and ended up getting it. So i have faith on this.
Click to expand...
Click to collapse
Motorola already admitted the Z series will not be a part of Project treble meaning we need to try different vendor files to see if builds work. Sadly the ones used for the Z1 and wahoo mixed together cause the phone to go haywire and brick itself.
Uzephi said:
Motorola already admitted the Z series will not be a part of Project treble meaning we need to try different vendor files to see if builds work. Sadly the ones used for the Z1 and wahoo mixed together cause the phone to go haywire and brick itself.
Click to expand...
Click to collapse
And I understand that this means lack of simplicity in developing custom rom's. But it doesn't mean incapability. From what I understand as well, that treble can be implemented at a later date even though it will not be included with the initial Oreo update. You are working on a pixel rom conversion if I am correct right? Because I might have an idea...
But treble is still def exciting to think about being able to have one rom work on many different phones without modification. I honestly haven't divulged too far into it, but what are the odds of tearing apart the code and possible making support for it ourselves? I'm all for ridiculously long spans of working towards absurd goals hah
Acoustichayes said:
And I understand that this means lack of simplicity in developing custom rom's. But it doesn't mean incapability. From what I understand as well, that treble can be implemented at a later date even though it will not be included with the initial Oreo update. You are working on a pixel rom conversion if I am correct right? Because I might have an idea...
But treble is still def exciting to think about being able to have one rom work on many different phones without modification. I honestly haven't divulged too far into it, but what are the odds of tearing apart the code and possible making support for it ourselves? I'm all for ridiculously long spans of working towards absurd goals hah
Click to expand...
Click to collapse
Unless Motorola can repartition the phone, Treble won't come out, it needs a vendor partition. I can say at least on my Sprint phone the OEM block is about 1.5 GB when there is only about 200 MB of data on it, so they can splice that to save user data. Only other way is to repartition /system or /userdata for the space needed for the new partition.
Yes, I am doing a pixel conversion ROM. Tried just booting the pixel /system and it didn't work. I am taking assets from the Tamien and putting them into our November update using SuperR.
Uzephi said:
Unless Motorola can repartition the phone, Treble won't come out, it needs a vendor partition. I can say at least on my Sprint phone the OEM block is about 1.5 GB when there is only about 200 MB of data on it, so they can splice that to save user data. Only other way is to repartition /system or /userdata for the space needed for the new partition.
Yes, I am doing a pixel conversion ROM. Tried just booting the pixel /system and it didn't work. I am taking assets from the Tamien and putting them into our November update using SuperR.
Click to expand...
Click to collapse
I know there are few devs out there working on making it work on non treble phones. Repartitioning and adding a vendor partiion wouldn't be the issue with making it work. Rather trying to get the vendor source for drivers to add to it, and if they need to be reworked to add support. I've been off for a few months with health issues so I'm still getting back into things with oreo, but that seems to be the biggest issue at the moment that I could find.
When my health is back to 100 percent within a couple weeks I will dive into work with you and aid in any way possible for this. To me, trying to get driver source and make it work sounds fun. but we are far off topic now for this post so I'll leave this here haha.

Has Anyone Flashed LineageOS 16 On Samsung Galaxy Tab S4 (SM-T830) (No GAPPS)

I have flashed LineageOS on my old Samsung Galaxy S6 phone and I like it a lot. But I want this ROM on my Tablet and I want everything to be working.
WiFi
Bluetooth
Front Camera
Back Camera
Software Buttons (Apps, Home, Back)
Volume Buttons
Power Button
Sound
Etc
I could not find any official builds nor any unofficial builds of LineageOS for this device. Has anyone successfully flashed this ROM on the Tab S4 without GAPPS and it works like a charm? I have the SM-T830 model.
Any success?
trymeout said:
I have flashed LineageOS on my old Samsung Galaxy S6 phone and I like it a lot. But I want this ROM on my Tablet and I want everything to be working.
WiFi
Bluetooth
Front Camera
Back Camera
Software Buttons (Apps, Home, Back)
Volume Buttons
Power Button
Sound
Etc
I could not find any official builds nor any unofficial builds of LineageOS for this device. Has anyone successfully flashed this ROM on the Tab S4 without GAPPS and it works like a charm? I have the SM-T830 model.
Click to expand...
Click to collapse
Hi Mate, I am looking for the same thing. Have you had any success?
_d4Mn_ said:
Hi Mate, I am looking for the same thing. Have you had any success?
Click to expand...
Click to collapse
I have not tried it yet since it is an expensive tablet and I do not want to screw it up. I did more research and I heard it can be buggy with LineageOS
I plan on flashing my phone this fall when my contract expires and I could care less if it bricks my phone then but I want my tablet to last at least 5 years and I would like my tablet to be De-Googled with LineageOS and no GAPPs.
trymeout said:
I have not tried it yet since it is an expensive tablet and I do not want to screw it up. I did more research and I heard it can be buggy with LineageOS
I plan on flashing my phone this fall when my contract expires and I could care less if it bricks my phone then but I want my tablet to last at least 5 years and I would like my tablet to be De-Googled with LineageOS and no GAPPs.
Click to expand...
Click to collapse
Hi mate,
I've been playing with this tablet for a while and I thing I have messed it up in every different way you can imagine. At one point with Odin I even flashed the BL bit to the AP and AP to BL. There I thought that's it, it didn't even bring up TWRP or anything after that. With the button combination you can get to download mode if the USB is plugged in. I believe there is no way you can overwrite the "download-mode" bit so you can get in there always, no matter what you do. This meant that I could flash the original stock stuff back onto the tablet. So don't worry, you cant mess it up.
_d4Mn_ said:
you cant mess it up.
Click to expand...
Click to collapse
you can in fact.
https://forum.xda-developers.com/galaxy-tab-s4/help/unbrick-image-t835-t3928912
https://forum.xda-developers.com/galaxy-tab-s4/help/accidentally-deleted-os-flash-stock-os-t3884633
Bumping this post. Also looking for lineageos for the samsung galaxy tab s4.
Hoping to get mine this week - I know you can flash any Treble based image, but will the Spen still work on other roms?
No luck so far getting anything to boot - just gets stuck on the logo
Lineage 16 works fine, haven't test everything, but it boots super quickly and the camera and even spen work.
veekay said:
Lineage 16 works fine, haven't test everything, but it boots super quickly and the camera and even spen work.
Click to expand...
Click to collapse
Hey, Do you have a link I haven't been able to find it. Thanks
https://forum.xda-developers.com/pr...i-lineageos-16-0-gsi-arm64-ab-how-to-t3908029
Use the arm64-a version
veekay said:
https://forum.xda-developers.com/pr...i-lineageos-16-0-gsi-arm64-ab-how-to-t3908029
Use the arm64-a version
Click to expand...
Click to collapse
Hey, Thanks for this I installed it and ran it for about a day and it was pretty cool and worked . However it is unstable and is pretty much a ticking time bomb and I cannot recommend this to anybody wanting a stable ROM for their Tab S4. If you're looking for a good stable ROM go check out WETA it has great modifications and is kept up to date. That being said these are the following problems I had using this GSI.
List of things broken or not working
- Screen Locks (Any Pin,Pattern or Password will cause the UI to bootloop)
- Speakers (Only two of the four speakers will work causing audio to be low.)
- Root Access (Root only worked for a select set of apps.)
- Digital Wellbeing
- Unable to fully complete setup. (I.E Android Setup will often crash)
- Incorrect Battery Levels Shown
Im sure there are other things that do not work but these are what I primarily experienced.
Part of the problem of not having anyone who is willing to develop a custom rom for this device - being stuck with crappy stock samsung.
I have wondered if there would be enough interest to warrant setting up a pool for a developer to get something fully working - I'd certainly be willing to donate.
veekay said:
Part of the problem of not having anyone who is willing to develop a custom rom for this device - being stuck with crappy stock samsung.
I have wondered if there would be enough interest to warrant setting up a pool for a developer to get something fully working - I'd certainly be willing to donate.
Click to expand...
Click to collapse
Agreed, I would be willing to donate a bit as well. Saddens me to see LOS for the S3 and S5e but not for the S4. Hopefully one day that will change.
You may want to test this one out as well -
https://forum.xda-developers.com/pr...vice-development/aosp-9-0-phh-treble-t3831915
I ended up with a shutdown issue after every boot, if that happens to you then just wipe the data partition.
I only know so far that it has an issue with the brightness, haven't tested anything else yet.
I tried installing LineageOS 16 and 17 using arm64-a, but I always end with bootloop. There is some extra step I must do?
For now I done:
- Installing latest firmware version
- Installing TWRP
- Installing image.
- Format Data + Factory Reset.
Thanks!
WalterCool said:
I tried installing LineageOS 16 and 17 using arm64-a, but I always end with bootloop. There is some extra step I must do?
For now I done:
- Installing latest firmware version
- Installing TWRP
- Installing image.
- Format Data + Factory Reset.
Thanks!
Click to expand...
Click to collapse
(after format data,try to flash "DM-VERITY - FORCEENCRYPT DISABLER" + Magisk - remove accounts google & samsung before beginning)
_ Just,read carefully-General Info GSI : https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
https://developer.android.com/topic/generic-system-image#download-gsi
https://forum.xda-developers.com/pr...aosp-10-0-quack-phh-treble-t3992559?nocache=1
*(maybe you need) : https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
https://github.com/topjohnwu/Magisk
_ Read carefully all posts,especially the newest: https://forum.xda-developers.com/galaxy-tab-s4/development/recovery-twrp-3-3-0-sm-t83x-t3928278
I'm not sure if it will work on android 10 gsi rom, just try it...
Even if it works, many things may not work on this device. There will definitely be many errors... Gl
daitalos said:
(after format data,try to flash "DM-VERITY - FORCEENCRYPT DISABLER" + Magisk - remove accounts google & samsung before beginning)
_ Just,read carefully-General Info GSI : https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
https://developer.android.com/topic/generic-system-image#download-gsi
https://forum.xda-developers.com/pr...aosp-10-0-quack-phh-treble-t3992559?nocache=1
*(maybe you need) : https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
https://github.com/topjohnwu/Magisk
_ Read carefully all posts,especially the newest: https://forum.xda-developers.com/galaxy-tab-s4/development/recovery-twrp-3-3-0-sm-t83x-t3928278
I'm not sure if it will work on android 10 gsi rom, just try it...
Even if it works, many things may not work on this device. There will definitely be many errors... Gl
Click to expand...
Click to collapse
Thanks! Yeah, seems like my failure was related to encryption. GSI really dislikes encryption on our S4 Tab, you can't even set a screenlock, as an exception happens from the CryptoProvider.

[ROM][10] Lineageos 17.1 [Official] Pixel 3a "Sargo"

Does anyone have experience with this Official LineageOS Rom in Pixel 3a?
Official Device Info/Wiki:
https://wiki.lineageos.org/devices/sargo
Official Installation instructions:
Install LineageOS on sargo | LineageOS Wiki
wiki.lineageos.org
Official Download Link for LineageOS ROM and Lineage RECOVERY:
LineageOS Downloads
download.lineageos.org
Horninho10 said:
Does anyone have experience with this Official LineageOS Rom in Pixel 3a?
Official Device Info/Wiki:
https://wiki.lineageos.org/devices/sargo
Official Installation instructions:
Install LineageOS on sargo | LineageOS Wiki
wiki.lineageos.org
Official Download Link for LineageOS ROM and Lineage RECOVERY:
LineageOS Downloads
download.lineageos.org
Click to expand...
Click to collapse
Yes, it runs nice and smooth, I was recently on LOS.
The post I'm about to make is not related to anything technical, so I'm not sure if it's appropriate on this forum, but I'm going to post it anyway...
Is there any advantages lineage has over stock? Seems like it's not really worth it. Right? What do you guys think about build?
pojr said:
The post I'm about to make is not related to anything technical, so I'm not sure if it's appropriate on this forum, but I'm going to post it anyway...
Is there any advantages lineage has over stock? Seems like it's not really worth it. Right? What do you guys think about build?
Click to expand...
Click to collapse
I personally am running stock for SafetyNet purposes at the moment. I do think it's worth checking out if you want a few more options for customization. It was a very smooth ROM, but LOS in specific is not my cup of tea.
MoistPicklez said:
I personally am running stock for SafetyNet purposes at the moment. I do think it's worth checking out if you want a few more options for customization. It was a very smooth ROM, but LOS in specific is not my cup of tea.
Click to expand...
Click to collapse
That is a very good point actually. That is one thing I was never a big fan of with the stock OS, is just the lack of options you have to customize your device. Might be worth getting it, even though it's a downgrade to Android 10
pojr said:
That is a very good point actually. That is one thing I was never a big fan of with the stock OS, is just the lack of options you have to customize your device. Might be worth getting it, even though it's a downgrade to Android 10
Click to expand...
Click to collapse
Test it out if you're interested, but A11 ROMs are likely around the corner. I bet we'll get a build or two of something else down the road. Cheers!
I've personally had GPS issues (while using OpenGapps Pico) with the official release. Hoping A11 builds fix it.
Aah, a much needed rom option for sargo/pixel 3a ! There has been a lot of silence around the pixel 3a in this regard.
I'm trying it out now. First thing I noticed is SIM manager keeps crashing every minute or so (I'm in the Netherlands on the Ben/T-mobile network). If there is a dev out there I can supply a logcat or something like it if needed.
Meanwhile I disabled the SIM manager to get rid of the constant crash notifications. I'll try and report back any issues I encounter (But if there are too many of them, I'll have to revert back to Dirty Unicorns, although that rom development seems to have stalled pretty much).
I seem to have overcome my GPS woes! My installation process was the following:
Install the last Android Q factory image
Flash LOS boot, go to recovery
Factory reset
Install update > adb sideload LOS zip
Very important(?) - go back to main menu, advanced, reboot to recovery
Install update > adb sideload opengapps pico zip > yes, install anyway
Sign in to your Google account during the initial setup process
Test GPS with an app (Google Maps, Waze, OSMAnd, Pokémon Go... )
The only issue I seem to have now is that the Google Fi app doesn't seem to get that my Fi service is ESIM based, and prompts me to order a physical SIM card, but playing with the mobile service settings seems to have gotten my service set up anyway.
EDIT: After talking with Google Fi support, going to Settings > System > Reset Options > Reset Wi-Fi, mobile & Bluetooth, check erase downloaded SIMs, then trying to activate Google Fi again in the app, it worked.
In addition to the helpful tips from @Mokura3rd. My two cents: I had some gps issues as well, but didn't test it to great extent. Here's a description of my (rather weird issue):
When I first installed Lineageos (jan16 - my previous comment), Google maps and Gps status were able to find gps signal (and quicky), but strava didn't find any gps signal (it didn't even ask for permission, which I granted manually - to no avail).
Some time after the first OTA update, I checked strava again. And it worked without issue. So there might have been merged some bugfixes that fixed gps issues on recent builds.
guys, is it true you have to jump down to Android 10 in order to get the latest lineage? that doesn't make sense. Don't you have to wipe your phone in order to switch from stock to custom anyway? seems pointless to downgrade to stock 10 first. what's your guys stance on this?
pojr said:
guys, is it true you have to jump down to Android 10 in order to get the latest lineage? that doesn't make sense. Don't you have to wipe your phone in order to switch from stock to custom anyway? seems pointless to downgrade to stock 10 first. what's your guys stance on this?
Click to expand...
Click to collapse
Because lineageos 17.1 is based on Android 10, you have to revert to stock Android 10 before you install it. The same goes for any ROM that is based on Android 11.
MoistPicklez said:
Because lineageos 17.1 is based on Android 10, you have to revert to stock Android 10 before you install it. The same goes for any ROM that is based on Android 11.
Click to expand...
Click to collapse
Thank you for clearing that up with me. Now I at least have an answer on that. With that said, why would that be? Don't you have to wipe your phone in order to switch from stock to custom anyway? Is the ROM gonna say "we have somehow detected the you once had Android 11 before you wiped your OS"
pojr said:
Thank you for clearing that up with me. Now I at least have an answer on that. With that said, why would that be? Don't you have to wipe your phone in order to switch from stock to custom anyway? Is the ROM gonna say "we have somehow detected the you once had Android 11 before you wiped your OS"
Click to expand...
Click to collapse
Android changes quite a bit between versions like dynamic partitions and other jazzy stuff. For example TWRP. It works on Android 9, but changes to our device made TWRP incompatible with A10 and A11. (Good news on that though, we just got TWRP 3.5.0_9-0, though I have not tested it.)
MoistPicklez said:
Android changes quite a bit between versions like dynamic partitions and other jazzy stuff. For example TWRP. It works on Android 9, but changes to our device made TWRP incompatible with A10 and A11. (Good news on that though, we just got TWRP 3.5.0_9-0, though I have not tested it.)
Click to expand...
Click to collapse
did not realize we got a new twrp version. thats a step in the right direction. with that said, that info is good to know. i'm a lazy ass and prolly not gonna test out lineage os until it gets on 11 lmao.
For whoever needs it. I sure did after a derped update last week!
tl;dr install update, disable all modules before booting, get the latest recovery image and patch it, install with fastboot. long version below, just in case.
How To OTA With Magisk, Painlessly:
Open updater and download the OTA.
Press install and let it do its thing, but DON'T REBOOT YET.
Go to Magisk and disable all your modules.
Okay, you can reboot now. It might take longer than usual, it's a system update.
Open Magisk and note that it's no longer installed, don't panic.
Download the recovery image matching your update from here: https://download.lineageos.org/sargo
Open Magisk and patch the img you just downloaded.
Copy the magisk_patched_(random).img to a folder on your computer where you're able to access fastboot.
Reboot your phone to bootloader: either by the advanced power menu, enabled in developer settings, or by restarting and holding Volume Down while the phone boots up.
Open up your terminal/commandline/etc where you moved the image file.
Type the command "fastboot flash boot magisk_patched_*****.img", where the last part is the random string that got generated in the patching process. Press Enter.
After the command finishes, use the volume keys to scroll through the bootloader menu until you see "Start". Press the power button.
Your phone should reboot back to the OS, you can now go back to Magisk and re-enable your modules at your leisure.
So the one problem 'I've been having is with custom kernels. I've tried Elemental X & Gats Gulch. With both I lose wifi capability. Once I restore my lineage kernel viola problem solved. Now I've used both these kernels in the past on different builds so I know it isn't the kernel itself rather something related to the lineage build itself & the act of installing a custom kernel. Both kernels returned exactly the same type of error. WIFI attempts to turn on but returns to the off Position. If one attempts to activate the Wifi Icon dropdown during the System UI Crashes. Any input would be great. Other than this little hiccup
Lineage is running absolutely great. Best battery life of any custom OS by far. Sargo stays snappy, my kernel tweaks remain in place. Root maintains over system restores. Love it.
EDIT: ## By the way using Elemental X Kernel Manager App to flash ##
harryharryharry said:
Aah, a much needed rom option for sargo/pixel 3a ! There has been a lot of silence around the pixel 3a in this regard.
I'm trying it out now. First thing I noticed is SIM manager keeps crashing every minute or so (I'm in the Netherlands on the Ben/T-mobile network). If there is a dev out there I can supply a logcat or something like it if needed.
Meanwhile I disabled the SIM manager to get rid of the constant crash notifications. I'll try and report back any issues I encounter (But if there are too many of them, I'll have to revert back to Dirty Unicorns, although that rom development seems to have stalled pretty much).
Click to expand...
Click to collapse
Just go into app settings and kill now & disable. I noticed that if you installl gapps, get rooted, setup the phone you prefer. Backup with google backup....use the lineage recovery to do a factory reinstall. Once you recover all the sim issues, installation issues simply stop.
nylar357 said:
So the one problem 'I've been having is with custom kernels. I've tried Elemental X & Gats Gulch. With both I lose wifi capability. Once I restore my lineage kernel viola problem solved. Now I've used both these kernels in the past on different builds so I know it isn't the kernel itself rather something related to the lineage build itself & the act of installing a custom kernel. Both kernels returned exactly the same type of error. WIFI attempts to turn on but returns to the off Position. If one attempts to activate the Wifi Icon dropdown during the System UI Crashes. Any input would be great. Other than this little hiccup
Lineage is running absolutely great. Best battery life of any custom OS by far. Sargo stays snappy, my kernel tweaks remain in place. Root maintains over system restores. Love it.
EDIT: ## By the way using Elemental X Kernel Manager App to flash ##
Click to expand...
Click to collapse
The kernel issues might be because they're targeted toward Android 11, and LOS 17.1 is based on Android 10.
harryharryharry said:
[...] First thing I noticed is SIM manager keeps crashing every minute or so (I'm in the Netherlands on the Ben/T-mobile network). [...]
Meanwhile I disabled the SIM manager to get rid of the constant crash notifications.[...]
Click to expand...
Click to collapse
It happened to me the same way. I am in the German T-Mobile network. I also disabled 'SIM Manager'.
Unfortunately, I do not receive any 'missed call'-SMS in case the mobile phone was in flight mode.
I think the app could have something to do with it because everything fits on the ISP side. So far, I haven't found an option to reactivate the App in the settings. Apparently it's some kind of hidden app. Can someone help please?
EDIT: There is a "hidden" "System-apps" option in the app settings. Unfortunately the error still occurs.

Getting Android 13 On Your N10 By Flashing Pixel Experience GSI

Hello, my fellow Nord N10 owners and other potential readers!​===========================================​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​​Pixel Experience is a custom rom (in this case, we're using a GSI made by ponces) which has a lot of Pixel goodies (incl. Gapps, Pixel Launcher, etc). I've used some GSIs (many of which had trouble with calling, using calling in some apps like Signal, and general issues.) However, for me, this is a better suited GSI for this phone as, even though I've had to tweak it, it wasn't as bad as the other GSIs.​Plus, flashing this GSI brings ANDROID 13 to your Nord N10! (Nord N10, as you know, is stuck at A11) with the May Security Patch already on the GSI.
(as of writing this guide)
Why I Made This Guide:
Simply put, I didn't enjoy the fact that the N10 was not only getting Android 11 as its only update, but also the fact that custom rom development is slow for this device.
Therefore, I wanted to make a guide informing my fellow N10 owners how to get Android 13 on their N10 devices!
DISCLAIMER:
Please do know that you, the reader, are responsible for what you do with your phone.
I'm simply providing the instructions which worked for me.
I also can't dive in too deep in code as I'm just a dude with a phone who likes to do cool stuff with it.
I also would like to point out the fact that I did NOT make any of the attached files here OR the GSI itself. I am simply gathering them here for the purpose of easier availability for the people who wish to follow this guide. Thanks to the people that I've credited in the main post along subsequent updates who've uploaded these files around different threads.
Also think of this guide as how I, mouseracer, successfully flashed the GSI. I don't know the best practices of flashing a GSI. I am simply sharing what WORKED for me.
Extra Info:
This is being done with a BE2029 OnePlus Nord N10 5G.
Pre-requisites:​
An updated, stock N10! (11.0.13 as of typing out this guide.)
A laptop/desktop with android tools (incl. fastboot) on it.
A USB cable
The Pixel Experience GSI itself: https://github.com/ponces/treble_build_pe/releases (I USED THE ARM64 -- NO VNDKLITE AND SLIM -- VERSION OF THE GSI) (In other words, I used the first option out of the three versions of the GSI.)
The Provided Recovery (It is attached at the very bottom of this post. It is named "recovery.zip". Shouldn't be hard to miss.)
First of all, unlocking the bootloader WILL erase your data! (Your photos, videos, et cetera!). Thus, make a backup of EVERYTHING.
Now, grab a cup of coffee and let's get right to the flashing!
The first thing you need to do is open your preferred terminal (cmd, linux terminal, anything that allows you to use fastboot) and check if fastboot is working for you.
Then, after the GSI image has been downloaded to your PC, you need to unzip it and retrieve the IMG file.
Now, hop over to your phone and enable developer options and then enable OEM unlocking.
Then, reboot your phone and hold the VOL down button to enter recovery. Enter your passcode (I hope to GOD that you are securing your phone with one) and tap on advanced -> reboot to fastboot.
Your phone will now boot to the bootloader and this is where you connect your phone to the PC and enter the following commands on your PC:
Code:
fastboot oem unlock
On your phone, you will see a warning message followed by two options. Use the vol keys and select the UNLOCK option for the bootloader.
Now, your data will be wiped.
After it is wiped, reboot to the recovery again and this time, reboot to fastboot mode. You will now be at the bootloader and this is where you unzip the recovery zip file ("recovery.zip") that I have provided at the bottom of this post.
After the recovery zip file's unzipped, enter the following:
Code:
fastboot flash recovery [recovery file you have unzipped]
fastboot reboot fastboot
Your phone will now reboot to fastbootd mode.
Once it does enter fastbootd mode, type in the following commands now:
Code:
fastboot erase system_a
fastboot delete-logical-partition product_a
fastboot delete-logical-partition system_ext_a
fastboot flash system (ENTER GSI YOU UNZIPPED HERE)
fastboot -w
Once it's done, do not reboot just yet. While in fastbootd mode and using the volume keys of your N10, enter recovery and factory reset your phone from there.
AFTER factory resetting your phone from the recovery menu, Press VOL UP to get to the back arrow symbol and reboot your phone.
( Also, sometimes, the phone may get stuck on the "bootloader unlocked" message. Keep calm and reboot your phone again. The Google 'G' SHOULD come on after some seconds of the warning message.)
And it is here that your phone now has the Pixel Experience GSI!
(btw, if this is your first time flashing a GSI on a phone, pat yourself on the back! )
Root it (via @andreas__ 's guide), use it, do whatever!
I'll add some general optimizations later.
For now, you should know that you need to enable some Fixes in the Phh Treble Settings menu.
PHH Treble Settings Options You MUST ENABLE (includes calling and other things)
Qualcomm features --> Enable both (Use Alternate audio policy & Disable stereo support on VoIP)
Misc features -> Force FPS (CHOOSE 90 FPS and then tap on RESTART SYSTEMUI), Enable (Use System Wide BT HAL)
IMS Features -> Install IMS APK from the notification bar after tapping on the Install IMS APK option (After which, enable both request IMS network and Force presence of 4G Calling and FINALLY create IMS APN. Reboot your phone afterwards)
OnePlus features -> Optionally, enable (Enable DT2W) for that cool double tap to wake feature.
I also recommend that, once your phone has rebooted after doing IMS changes, to change from 3G to LTE!
You can also have a go at Wifi Calling as well!
Now, since this is a GSI that you -- the reader -- are flashing, please know that it will have some bugs since it wasn't tailor-made for our devices.
For some reason, battery life has been good for my usage. (Sometimes watching yt vids and general tasks)
...and there we go!
You've just flashed the Pixel Experience GSI on your Nord N10 phone!
Both Play Integrity and Safetynet pass on this GSI, even when rooted! (at the time of typing this guide out, at least.)
Incoming calls and outgoing calls work well!
====================================================
If you successfully followed this guide, let me know how helpful this guide was and give some feedback as well!
That's all for now!
Good luck!
- Mouseracer
ISSUE 1: SIM OPTION STUCK/NOT WORKING IN GSI
==================================
TEMPORARY FIX: REBOOT THE PHONE AND CHECK THE OPTION AGAIN. IF OCCURS AGAIN, REPEAT (worked for me.)
IMPORTANT UPDATE 1: AUTO BRIGHTNESS
This is for the current users of the GSI who want to use Auto Brightness function on the GSI.
Please enable USB Debugging in the settings and download the overlay file by @Generic123. below.
Enter the following code:
Code:
adb root
adb shell avbctl disable-verification --force
adb reboot
The phone will now reboot and after reboot, enter the following code again after unlocking the phone:
Code:
adb root
adb remount
adb push (overlay file I have provided) /vendor/overlay
adb reboot
The phone will now reboot again for the final time and after the reboot, you should now see a big auto brightness button near the brightness slider.
CONGRATULATIONS, you now have the auto brightness function in the GSI!
Thanks @Generic123. for the overlay file!
Enjoy!
- mouseracer
is this rom better than stock rom ? ( like smoother or smth )
pxxell said:
is this rom better than stock rom ? ( like smoother or smth )
Click to expand...
Click to collapse
Hey there, @pxxell . That's a great question!
So, I've been using this GSI for some time now and have not noted any significant breakage of daily functions.
Sure, you may face some issues, but those are usually minor.
Compared to stock? Oh man, call me biased but I love it!
On stock, there was this one issue that bugged the ever loving heck outta me. That being the share function between work profile and personal profile.
This GSI, doesn't have that.
Also, if your talking about the "Smoother" display rate (90hz), unlike stock rom, you can force the phone to operate at 60fps or at 90fps. At 90fps, it won't switch between 60 and 90. It'll just stay at 90.
Of course, compared to Stock Rom, your camera may be affected on this GSI. And also, since this is a GSI (Generic System Images. Basically, you can flash them on ANY Treble Supported Device but this is sort of like a GENERAL rom. Unlike Custom Roms made for a particular device, GSIs are made for a wide variety of devices so they may be lacking in a few aspects when running on some devices. Some GSIs may not even boot! However as we've established, this Pixel Experience GSI does boot and also works.), there may be some issues.
However, I just use the GCAM I've talked about and it works well provided I don't need 4K video. ([email protected] seems to be the highest for that gcam before it just doesn't work while recording.)
And of course, you get the newest Android 13 on your phone. No more will your phone be capped to a version that OnePlus gave us with this phone (Android 11).
I obviously have also rooted my phone (Magisk Delta) using @andreas__ 's rooting N10 guide (first flashed Magisk then Magisk Delta. For process simplification, made some boot patches. If you need guide then I'll make one later) and EQ apps like Viper4Android REALLY make me love listening to music! I also am using shelter to isolate those apps which seem to detect root at all stages.
(I also use my phone for watching YT videos and listening to music and etc.)
Since this GSI tries to be like a Pixel, it passes SafetyNet as well as Play Integrity (obviously, you can't pass STRONG yet bc your bootloader's unlock but up till now, most banks dont seem to check for it..)
TLDR: I daily drive this GSI and like it a lot.
Sure, it may have some bugs (battery drain may be higher. Don't know how or why I don't have it but eh.) But, compared to other GSIs (no incoming call/outgoing calls, stuttering videos, other issues), this is a bit more stable. At least for me, that is.
and it makes apps that were inoperable on stock to run on this GSI!
Take for example, CAPods, an app which essentially shows you battery info and helps to give you functions for your airpods such as pausing when you take out airpods and tapping on one of them to stop music and more.
On stock, you would see none of the airpods you've paired show up. (at least, for me!)
On this GSI, you see the paired AirPods, just like you were always supposed to but couldn't!
It's so cool that we can run GSIs like this and keep things fresh for our phones and even experience updates that, while our phones can run them, we wouldn't even get at all. Especially when you consider this phone has 6GB of RAM!
Even WhatsApp and other essential apps run!
And this is why I wanted to make this guide, so I can share this knowledge with other people who also feel the same as me and also want to try the latest version of Android!
You are welcome to try flashing the GSI on your phone. Personally, I love it!
and remember...
Have Fun!
- mouseracer
mouseracer said:
Hey there, @pxxell . That's a great question!
So, I've been using this GSI for some time now and have not noted any significant breakage of daily functions.
Sure, you may face some issues, but those are usually minor.
Compared to stock? Oh man, call me biased but I love it!
On stock, there was this one issue that bugged the ever loving heck outta me. That being the share function between work profile and personal profile.
This GSI, doesn't have that.
Also, if your talking about the "Smoother" display rate (90hz), unlike stock rom, you can force the phone to operate at 60fps or at 90fps. At 90fps, it won't switch between 60 and 90. It'll just stay at 90.
Of course, compared to Stock Rom, your camera may be affected on this GSI. And also, since this is a GSI (Generic System Images. Basically, you can flash them on ANY Treble Supported Device but this is sort of like a GENERAL rom. Unlike Custom Roms made for a particular device, GSIs are made for a wide variety of devices so they may be lacking in a few aspects when running on some devices. Some GSIs may not even boot! However as we've established, this Pixel Experience GSI does boot and also works.), there may be some issues.
However, I just use the GCAM I've talked about and it works well provided I don't need 4K video. ([email protected] seems to be the highest for that gcam before it just doesn't work while recording.)
And of course, you get the newest Android 13 on your phone. No more will your phone be capped to a version that OnePlus gave us with this phone (Android 11).
I obviously have also rooted my phone (Magisk Delta) using @andreas__ 's rooting N10 guide (first flashed Magisk then Magisk Delta. For process simplification, made some boot patches. If you need guide then I'll make one later) and EQ apps like Viper4Android REALLY make me love listening to music! I also am using shelter to isolate those apps which seem to detect root at all stages.
(I also use my phone for watching YT videos and listening to music and etc.)
Since this GSI tries to be like a Pixel, it passes SafetyNet as well as Play Integrity (obviously, you can't pass STRONG yet bc your bootloader's unlock but up till now, most banks dont seem to check for it..)
TLDR: I daily drive this GSI and like it a lot.
Sure, it may have some bugs (battery drain may be higher. Don't know how or why I don't have it but eh.) But, compared to other GSIs (no incoming call/outgoing calls, stuttering videos, other issues), this is a bit more stable. At least for me, that is.
and it makes apps that were inoperable on stock to run on this GSI!
Take for example, CAPods, an app which essentially shows you battery info and helps to give you functions for your airpods such as pausing when you take out airpods and tapping on one of them to stop music and more.
On stock, you would see none of the airpods you've paired show up. (at least, for me!)
On this GSI, you see the paired AirPods, just like you were always supposed to but couldn't!
It's so cool that we can run GSIs like this and keep things fresh for our phones and even experience updates that, while our phones can run them, we wouldn't even get at all. Especially when you consider this phone has 6GB of RAM!
Even WhatsApp and other essential apps run!
And this is why I wanted to make this guide, so I can share this knowledge with other people who also feel the same as me and also want to try the latest version of Android!
You are welcome to try flashing the GSI on your phone. Personally, I love it!
and remember...
Have Fun!
- mouseracer
Click to expand...
Click to collapse
Thanks for helping me, btw how can i contact u if i faced any error when i install this rom, like telegram or discord.
pxxell said:
Thanks for helping me, btw how can i contact u if i faced any error when i install this rom, like telegram or discord.
Click to expand...
Click to collapse
Hello, @pxxell .
I don't exactly have telegram or discord.
But feel free to post issues you may have and I'll attempt to diagnose or find a fix for them.
But ultimately, just know that I'm a guy with a phone along with some ambition but not a developer. I don't delve deep into code and just use what options I am provided with to try to find a workaround of sorts.
I may NOT be able to fix your problem 100% and if that problem is a massive deal to you, I recommend you to be on stock as even though I have a tendency to sometimes be a bit frustrated with stock, it is at least made for this phone as opposed to this GSI which isn't.
Ultimately, stock is the best at reliability. If you have to make critical calls or are using the phone as your only phone, I recommend to be on stock since at least OnePlus is giving N10 owners the occasional security patch update for the next year or so.
However, if you do know that ultimately there'll be a few issues and are still willing to go for it, then its up to you. Sometimes incoming call audio stays blank or smth. For that, I restart the phone and call works.
Other than those hiccups, I generally have minor issues.
But yeah, if you are giving your phone for repairs or something of the sort, I'd recommend flashing the stock rom back using MSMDownloadTool as provided by some of the folks here for this phone.
Ultimately, I'd also say that you don't need root nowadays. (unless you are on a custom rom for which you may need to have some sort of play integrity bypass). If debloating is your question, ADB is the answer to it! (Even works on NON ROOTED phones and doesn't trigger any bad things to happen on your phone as long as your smart about it and not uninstall System Webview or Android System or some other important component like them.)
Personally, I just root my phone for systemwide ad blocker, audio tweaks and for having the option to do some other things not possible without root.
So yeah, that's all.
Hope you got some questions of yours answered!
- mouseracer
I have the metro variant, will it work with that?
mirzanuman6612 said:
I have the metro variant, will it work with that?
Click to expand...
Click to collapse
Hello there, @mirzanuman6612!
Now, I don't know about the metro variant or other variants. But, if possible, make a backup if you do want to try it.
I'll state again though that my phone model's a BE2029 non carrier version of the phone.
I do think that it may work, but please do make a backup and try. Also, please lmk if it does work.
I hope that it goes well for you!
-mouseracer
(ps, love the meme as your dp. )
IMPORTANT UPDATE 1
I've added an additional tutorial on how to enable AUTO BRIGHTNESS in the GSI.
Check the main post.
mouseracer said:
Hello, @pxxell .
I don't exactly have telegram or discord.
But feel free to post issues you may have and I'll attempt to diagnose or find a fix for them.
But ultimately, just know that I'm a guy with a phone along with some ambition but not a developer. I don't delve deep into code and just use what options I am provided with to try to find a workaround of sorts.
I may NOT be able to fix your problem 100% and if that problem is a massive deal to you, I recommend you to be on stock as even though I have a tendency to sometimes be a bit frustrated with stock, it is at least made for this phone as opposed to this GSI which isn't.
Ultimately, stock is the best at reliability. If you have to make critical calls or are using the phone as your only phone, I recommend to be on stock since at least OnePlus is giving N10 owners the occasional security patch update for the next year or so.
However, if you do know that ultimately there'll be a few issues and are still willing to go for it, then its up to you. Sometimes incoming call audio stays blank or smth. For that, I restart the phone and call works.
Other than those hiccups, I generally have minor issues.
But yeah, if you are giving your phone for repairs or something of the sort, I'd recommend flashing the stock rom back using MSMDownloadTool as provided by some of the folks here for this phone.
Ultimately, I'd also say that you don't need root nowadays. (unless you are on a custom rom for which you may need to have some sort of play integrity bypass). If debloating is your question, ADB is the answer to it! (Even works on NON ROOTED phones and doesn't trigger any bad things to happen on your phone as long as your smart about it and not uninstall System Webview or Android System or some other important component like them.)
Personally, I just root my phone for systemwide ad blocker, audio tweaks and for having the option to do some other things not possible without root.
So yeah, that's all.
Hope you got some questions of yours answered!
- mouseracer
Click to expand...
Click to collapse
can you create one ? Cuz we have a telegram channel but only @kronflux dev rom, maybe u can be second dev for our phone.
pxxell said:
can you create one ? Cuz we have a telegram channel but only @kronflux dev rom, maybe u can be second dev for our phone.
Click to expand...
Click to collapse
Oh yeah, @kronflux .
Ngl, I also was going to use his ROM after @jnelle stopped development of official roms for this phone.
But I eventually decided to stay put and figure out how to run a GSI on this phone.
I think the unofficial recovery rom came from his thread.
Sometime later, I did but had several issues with the way I was going about it.
This is now my other attempt at flashing this GSI and this time, I haven't seen much instability.
I doubt that I'll be a second dev for this phone. Unlike devs like @kronflux or @jnelle, I don't know much coding aside from tinkering around with my phone with adb and fastboot and some good ol' Stack Overflow. I also don't really know how to port roms and I've a low RAM HDD laptop.
I, however, can volunteer as a rom tester of sorts. So if any developer for this device wants to test a Custom ROM, I'll try to run that on my phone.
I, like other people on XDA, like having the newest features and also dislike the fact that phone manufacturers keep doing this trend of either discontinuing updates or having a VERY short update cycle (except for security updates) for a clearly capable phone.
So, out of frustration, I decided to post any information about this device having A13 that I could try on my own on this device's forum. (GCam post, asking about running GSIs and etc.)
I also would like to point out that I did NOT make any of the items in the main post by myself at all. (I simply get the attached files from around different threads for this Device's Forum and gather them for availability for people to use them. I do not take credit for any of the things which help people flash this GSI or improve their experience using it. I credit the makers of these files in the main thread itself.)
I am still thinking about trying other GSIs as well and sort of ranking them based on how well I found them to be (severity of the inevitable bugs on the GSIs, etc)
About the telegram thingy, I may consider it but for now, I am happy to discuss any potential issues which do arise from using this GSI on this thread itself.
Btw, lemme know how was the experience of using the GSI?
Bye!
- mouseracer
Does your phone have poor wifi connection on this GSI PE rom? I remembered last time I flashed it with @twindragon6's guide and daily drove it for a while, my wifi connection was really bad like, when I'm on the first floor of my house, stock rom would have excellent or good signal strength, while on this GSI rom, it dropped to only poor and sometimes fair.
redabrao said:
Does your phone have poor wifi connection on this GSI PE rom? I remembered last time I flashed it with @twindragon6's guide and daily drove it for a while, my wifi connection was really bad like, when I'm on the first floor of my house, stock rom would have excellent or good signal strength, while on this GSI rom, it dropped to only poor and sometimes fair.
Click to expand...
Click to collapse
Hello there, @redabrao .
No, not really. Either I don't notice it or something but for me, I don't have poor wifi connection on the GSI PE.
I find it almost similar to stock, if I have to compare it to stock.
Now, if the problem persists, I highly recommend you root and flash the "Wifi Bonding" magisk module if you can. Just follow the instructions while doing so.
It claims to improve wifi bandwidth for phone. Haven't tried it but seems safe to use.
But please do test it out and see if the connection's better.
Also, remember to backup!
Personally, I don't really game on my device apart from sometimes emulating some old game.
But eh, that's my experience using this GSI.
Good Luck!
mouseracer said:
Hello there, @redabrao .
No, not really. Either I don't notice it or something but for me, I don't have poor wifi connection on the GSI PE.
I find it almost similar to stock, if I have to compare it to stock.
Now, if the problem persists, I highly recommend you root and flash the "Wifi Bonding" magisk module if you can. Just follow the instructions while doing so.
It claims to improve wifi bandwidth for phone. Haven't tried it but seems safe to use.
But please do test it out and see if the connection's better.
Also, remember to backup!
Personally, I don't really game on a device apart from sometimes emulating some old game.
But eh, that's my experience using this GSI.
Good Luck!
- mouseracer
Click to expand...
Click to collapse
Thank you very much for your experience. I guess I might give this another try using your method.
redabrao said:
Thank you very much for your experience. I guess I might give this another try using your method.
Click to expand...
Click to collapse
No problem, man!
It makes me happy that we can prolong the use of this device through GSI like Ponces' Pixel Experience.
We've had custom roms that were at one point in development but which are now either N/A or not being developed at all.
This GSI, while it has its quirks, feels like an almost good custom rom alternative to this phone.
That being said, it is still up to you if you wanna decide to flash Ponces' GSI.
If you ARE going to go with it, then good luck bro!
Also, lemme know if it worked for you!
i have wifi issu its not working at all

Categories

Resources