Hello.
I wanted to install Pixel Experience 12, knowing that the Mi 11 Lite 5G is Treble-Compatible and already had Pixel exp 11.
What i did is that i had Pixel Experience 11, so i backed up everything using TWRP, and i tried to flash the ROM using Fastboot using the "Pixel Experience 11" post, that actually was a success for me. But, TWRP Fastboot didn't work, so i flashed stock rom, to get the stock fastboot, and tried to flash.
I got onto fastboot, and when trying to flash Pixel Exp 12, it says that it cannot find the "system" partition?
But then, what is MIUI using?!!!!
When backing up, i also seen that there were no "system" partition to recover.
I tried to recover that backup, and it also didn't work. So now i have to use MIUI, and i had to reinstall everything.
What i exactly want is just tips or instructions for Pixel Experience 12, if possible.
I also can't show you screenshots, since i actually did that few days ago.
Lolo280374 said:
Hello.
I wanted to install Pixel Experience 12, knowing that the Mi 11 Lite 5G is Treble-Compatible and already had Pixel exp 11.
What i did is that i had Pixel Experience 11, so i backed up everything using TWRP, and i tried to flash the ROM using Fastboot using the "Pixel Experience 11" post, that actually was a success for me. But, TWRP Fastboot didn't work, so i flashed stock rom, to get the stock fastboot, and tried to flash.
I got onto fastboot, and when trying to flash Pixel Exp 12, it says that it cannot find the "system" partition?
But then, what is MIUI using?!!!!
When backing up, i also seen that there were no "system" partition to recover.
I tried to recover that backup, and it also didn't work. So now i have to use MIUI, and i had to reinstall everything.
What i exactly want is just tips or instructions for Pixel Experience 12, if possible.
I also can't show you screenshots, since i actually did that few days ago.
Click to expand...
Click to collapse
Why don't you just use TWRP recovery for flashing the ROM?
Spuffyffet said:
Why don't you just use TWRP recovery for flashing the ROM?
Click to expand...
Click to collapse
Actually, i never used TWRP to flash anything, since i never knew how to do it.
Could you maybe please tell me instructions how to flash Pixel exp. 12 coming from a stock MIUI12 Rom?
Lolo280374 said:
Actually, i never used TWRP to flash anything, since i never knew how to do it.
Could you maybe please tell me instructions how to flash Pixel exp. 12 coming from a stock MIUI12 Rom?
Click to expand...
Click to collapse
It's simple, a thread already exist.
See in particular the post #51 : https://forum.xda-developers.com/t/shared-pixel-experience-plus-v11.4280663/post-85209489
Thoiareg said:
It's simple, a thread already exist.
See in particular the post #51 : https://forum.xda-developers.com/t/shared-pixel-experience-plus-v11.4280663/post-85209489
Click to expand...
Click to collapse
Actually this is what i did. Last time i did it for Pixel 11, it did not work. And now, same thing happening again... (see screenshot.)
Does anybody know maybe if that's possible with TWRP, or idk?
Also, thank you still for your response
Lolo280374 said:
Actually, i never used TWRP to flash anything, since i never knew how to do it.
Could you maybe please tell me instructions how to flash Pixel exp. 12 coming from a stock MIUI12 Rom?
Click to expand...
Click to collapse
I texted you in DMs, let's talk about this there, it's really simple brother.
Related
Hi guys,
I'm new here. I didn't root my S3 yet, but I want to do it and install new rom. But first I would need your help with Rom choosing, as I'm completely blind in this matter
The thing is, I would prefer a ROM which let me choose which application I want to install on my phone and which not - check/uncheck option. This rom should be FAST and stable.
As I have no experience at all, I would like to ask you which ROM will be the best for me? Btw, it would be great if I can choose language (Polish).
Hope you will help me
Regards,
Karol
edit: sorry for typo in the topic, impossible to change it now
Hi, I am in the same boat. Stock standard international S3, but extremely slow. Ram usage on startup is 700mb.
Which rom would you guys suggest that is both stable (no bugs), and fast (using much less ram).
This is my everyday phone, I take a lot of photos, especially the camera should be functioning perfectly.
Any help would be much appreciated.
Edit: Last time I rooted and played around with these things were about 3-4 years ago with my Sony X10 mini. I am slowly getting back into it, reading up on the latest rooting apps etc.
@errolpl: Search in development subforum for 'aroma installer'. Usually these ROMs offer only system apps to choose. 3rd party user apps you'll have to install by your own. You can edit the header with edit-function.
@demozzracy: If you want full camera suport, I recommend NCS-ROM: based on last JB-firmware, but brilliant debloated. So slim, fast, battery friendly and all hardware working. I'm testing many LP-ROMs, but they are primarily newer, hardly better (for S3).
@rp158: Thank you!
I was extremely new just a few weeks back as well. I must say that my attempts on finding a solution for my slow S3 has been a rather hard and bumpy road.
To help you save some time, here is what I've gathered so far:
Last time I flashed phone firmware, a couple of years ago, it required a PC, a cable and some funky software.
Then when I flashed my S3 for the first time, about a year ago, I started out with Cyanogenmod and used their app+cable installer. I think this is still the easiest way to root the phone, and get started with custom roms. Even if you plan to use some other rom than Cyanogenmod.
When the phone is rooted you can install TWRP, simply done via an app on the appstore. TWRP is recovery firmware that can stay on the phone, even though you flash new roms. (The phone is divided into several separate sections, bootloader, recovery, actual system, and data area.... I don't even know much about it yet.) The important part is that it is extremely easy to flash new roms using this tool, and a micro SD-card.
Simply drop the rom zip file onto the card and flash them. (For some roms you need to flash some "GAPPS" as well. These are the google apps, like the play store etc. If you don't flash them you can't really use the phone for much.)
This is where the real problems start. Finding the right ROM.
The S3 is old, and only supported up to Jelly Bean for my 1GB international version, or Kitkat if you have one of the 2gb versions.
This has not stopped developers in providing both Kitkat and Lollipop to any version of the S3. However... as eager they are to provide the newest coolest features, just as lazy do they seem to be with their testing. (Sorry guys, but someone has to say it.)
So I've gone through some roms now... none of them really good.
The first Official Cyanogenmod I flashed half a year ago. I used this for almost a year.. but the camera would crash constantly, and the phone was not able to display video. For example movieclips on facebook.
Second ROM: Cyanogenmod has also stopped developing for the S3, so a few weeks back I switched to some unofficial version. It seemed to work... camera and video was ok, and everything had the nice Lollipop feel to it.
However MMS did not work. I could receive one and send one, next ones would require a reboot for them to work. The problem was brought up in the ROM Q/A tread, but the answer from the developer was: Sorry I don't use MMS so I don't really see a problem.
Third: Onto some next rom. This one was tagged STABLE. It was far from it. In fact it was even easier to discover that this rom had the same MMS problem. Because the message app would crash immediately when trying to send one.
4th attemt was the same rom, but a different kernel... still the same problem.
5th rom was Blisspop... Wau, this was beautiful! Cool webpage, Cool animations.... it was just too bad that the site is dead, and that the rom can't even run for 24 hours without the android keyboard crashing 25 times or so. Also Blisspop has OTA updates... the only problem is that it constantly says that there is a new version for the S3.. but the download fails. Apparently some bad change to the website caused this, and apparently this problem has been going on for 3 months without anyone bothering to fix it.
6th was Archidroid. The second to top ROM for the S3. It looks cool, and has many features... but just as other Lollipop ROMs, sending MMS's without error is not one of them....
I've really tried everything. People always says that the MMS problems are due to APN's not being set up correctly, doing some reboots etc.... but trust me... I've set them up so many times you wouldn't belive it.
7th. After reading this thread and rp158's recommendation of NCS-ROM I'm now running that one. Without a single thing being set up, I was able to send and receive MMS's right away.
However... now I'm stuck back at the ugly kitkat look, and Touch wiz.
tl;dr;
So what do I want to say with all this?
Get root and TWRP and start playing around with ROMs
Lollipop does not look like an option for the S3, at least not right now
Don't let yourself be fooled by nice webpages or [STABLE]-tags, or comments that say: "I've been running this since yesterday.. it's 100% stable!"
Timusius thanks a lot for that post.
Puts things in perspective.
As I said in my post, I am ok with the KitKat look, as long as it is stable, I am always on call at work, and cant afford constant phone crashes.
I am going to try the root/twrp to NCS rom in the next couple of days
@Timusius thank you for your post. You help me a lot!
S5 Sensation
errolpl said:
Hi guys,
I'm new here. I didn't root my S3 yet, but I want to do it and install new rom. But first I would need your help with Rom choosing, as I'm completely blind in this matter
The thing is, I would prefer a ROM which let me choose which application I want to install on my phone and which not - check/uncheck option. This rom should be FAST and stable.
As I have no experience at all, I would like to ask you which ROM will be the best for me? Btw, it would be great if I can choose language (Polish).
Hope you will help me
Regards,
Karol
edit: sorry for typo in the topic, impossible to change it now
Click to expand...
Click to collapse
It's 5 months already that im using S5 Sensation rom for i9300/9305 ( 4.4.4 kitkat). This rom has S5/Note4 features and works great im satisfied. No problems so far, no bugs, etc ^^
It comes with AROMA installer and lets you to choose which apps you want to install and which not.
Cooldato said:
It's 5 months already that im using S5 Sensation rom for i9300/9305 ( 4.4.4 kitkat). This rom has S5/Note4 features and works great im satisfied. No problems so far, no bugs, etc ^^
It comes with AROMA installer and lets you to choose which apps you want to install and which not.
Click to expand...
Click to collapse
How you install those rom?
Pixelzack said:
How you install those rom?
Click to expand...
Click to collapse
Device must be rooted + newest cwm recovery installed. After that you just download custom rom, move it to ur phone memory/sdcard and flash it throught recovery mode
Cooldato said:
Device must be rooted + newest cwm recovery installed. After that you just download custom rom, move it to ur phone memory/sdcard and flash it throught recovery mode
Click to expand...
Click to collapse
My phone already rooted without cwm,can i just install cwm like i did to root my phone?
Pixelzack said:
My phone already rooted without cwm,can i just install cwm like i did to root my phone?
Click to expand...
Click to collapse
https://www.clockworkmod.com/rommanager here is the latest CWM versions for smartphones, but its .img file and u cannt flash it directly from Odin. U need to make .img into .tar.md5 odin flash-able file by some tools, or flash it via adb shell, etc.
Anyway here is Odin rdy .tar file , go to this link http://forum.xda-developers.com/gal...covery-clockworkmod-touch-6-0-3-2-gt-t1719744 download recovery-cwmtouch-6.0.3.2-GTI9300.tar and flash it via Odin / Download mode.
Cooldato said:
https://www.clockworkmod.com/rommanager here is the latest CWM versions for smartphones, but its .img file and u cannt flash it directly from Odin. U need to make .img into .tar.md5 odin flash-able file by some tools, or flash it via adb shell, etc.
Anyway here is Odin rdy .tar file , go to this link http://forum.xda-developers.com/gal...covery-clockworkmod-touch-6-0-3-2-gt-t1719744 download recovery-cwmtouch-6.0.3.2-GTI9300.tar and flash it via Odin / Download mode.
Click to expand...
Click to collapse
Can I use this one?
http://forum.xda-developers.com/gal...covery-clockworkmod-touch-6-0-3-2-gt-t1719744
Pixelzack said:
Can I use this one?
http://forum.xda-developers.com/gal...covery-clockworkmod-touch-6-0-3-2-gt-t1719744
Click to expand...
Click to collapse
Sure, thats what i linked you above.
Cooldato said:
Sure, thats what i linked you above.
Click to expand...
Click to collapse
Hahaha Thanks dude for helping noob like me
Pixelzack said:
Hahaha Thanks dude for helping noob like me
Click to expand...
Click to collapse
No problem Feel free to poke me if u meet some troubles ^^
Cooldato said:
No problem Feel free to poke me if u meet some troubles ^^
Click to expand...
Click to collapse
How to install this?
http://forum.xda-developers.com/galaxy-s3/development/i9300-to-n00t-bring-lte-fun-to-3g-t2886574
just need some detailed guide xD
Pixelzack said:
How to install this?
http://forum.xda-developers.com/galaxy-s3/development/i9300-to-n00t-bring-lte-fun-to-3g-t2886574
just need some detailed guide xD
Click to expand...
Click to collapse
1. Install ClockworkMod(or PhilZ) recovery
2. Put ROM on your SD card
3. Enter recovery mode
4. Perform a full data wipe(except you're running previous versions of back-to-n00t)
5. Flash ROM
6. Flash SuperSU
Cooldato said:
1. Install ClockworkMod(or PhilZ) recovery
2. Put ROM on your SD card
3. Enter recovery mode
4. Perform a full data wipe(except you're running previous versions of back-to-n00t)
5. Flash ROM
6. Flash SuperSU
Click to expand...
Click to collapse
perform a full data wipe means "Factory reset"?
How to flash rom? It's included in the recovery mode?
How to flash SuperSU?
Pixelzack said:
perform a full data wipe means "Factory reset"?
How to flash rom? It's included in the recovery mode?
How to flash SuperSU?
Click to expand...
Click to collapse
yeah this means doing a "Factory reset", must be done throught Recovery mode, wipe data, wipe cache, wipe dalvik cache.
Put ROM on your SD card, then enter Recovery Mode by pressing Home + Volume UP + Power buttons and ull have smth like:
Install Zip -> Choose Zip from /Storage/Sdcard (External SDcard) , Search for ur ROM file and start flashing :X
Flash the SuperSu .zip file same way as flashing ROM.
So I've been rooting all my devices for a while now. I've been able to figure out many issues, including times where I've accidentally soft bricked my device. I've always loved Nexus devices, and have rooted nearly every one I've had. I've had the 7 (2012), 5, 6, and 9, so I'm not new to this. However, the issue I'm having now is something I've never had before...
I rooted my 9 just a couple of days after getting it, and I was successful. I used the nexus root toolkit, which has always been my go to (and yes, I've made sure to configure my drivers and they all function just fine.) I was running CM12 and 12.1. After some time, I decided to try and go back to stock, due to things beginning to slow down on my tablet. I used a stock image from Google (and ensured it was the right one too) and flashed it with the nexus root toolkit. However, just before doing this, I messed up and instead of doing a normal wipe, I also did a full wipe, taking everything off. I figured reverting to stock could undo my error. After flashing stock through my PC, I became shocked to see the CM boot logo and the build being a CM one. I noticed that gapps were installed already (not sure if they were from the factory image, or from a failed wipe) and they crash any time I attempt to log in with my Google account. TWRP is still installed, so I've tried to do a clean install of CM with fresh gapps and continues to be the same issue. It's like it's constantly being dirty flashed. At this point, I'm probably just gonna revert to stock, but have no idea how. Someone please help!
Sent from my Nexus 6 using XDA Free mobile app
Download a stock image, and flash it manually with fastboot. Toolkits are cool for their ease, but honestly, if you're flashing things, you need to know how to do them manually first, so you actually know what's being done.
Sent from my Nexus 9 using Tapatalk
dictionary said:
Download a stock image, and flash it manually with fastboot. Toolkits are cool for their ease, but honestly, if you're flashing things, you need to know how to do them manually first, so you actually know what's being done.
Sent from my Nexus 9 using Tapatalk
Click to expand...
Click to collapse
So even if the tool kit uses fast boot and stuff to flash back, manual flashing will be more successful?
I won't say that that'll solve your problems for sure, but you'll know exactly where your problem is.
dictionary said:
I won't say that that'll solve your problems for sure, but you'll know exactly where your problem is.
Click to expand...
Click to collapse
I appreciate it! I'm waiting for an OTG cable to arrive in the mail because the only Windows machine I have is a tablet.. I like Linux and Hackintosh a tad too much on my daily driver, but don't feel comfortable enough using terminal to try and flash through Linux.. But I'll be sure to report my findings when possible!
So just to update, I used the nexus root toolkit and disabled any checks when reverted to stock. It worked, and it seems to have been related to the boot issue CM originally had. Planning on going to CM again soon
While i was new to the forum after buying my redmi note 3,i was wondering through the different posts of flashing recoveries and stock ROM's. Thats when i came across a thread which said that after wiping the storage(or something like that) while in MIUI i must boot MIUI once and then only my whole storage will be seen otherwise i would not get my whole storage. I don't remember who's post it was. Though i followed the instructions and now am using lineageOS.
Well,but the issue is not with my RN3, instead its with my letv le 1s in which i recently flashed lineage and now i have that error of not getting all the storage. In the guide i referred to,there was no mention of booting back to the Stock ROM,so after a wipe,i simply flashed Lineage OS.
Now i see 29.5gb used of 29.11 gb in storage although I don't have a single thing in there.
I know its off topic in terms if the phone bit I don't think the letv forum has people who will help me or maybe have the ability and experience to help me. So, its a request, before replying that i am not in the right place please help me if you can. Thanks.
Edit: Solved. Check 3rd post.
Sent from my Pixel XL using Tapatalk
deepjyoti30 said:
While i was new to the forum after buying my redmi note 3,i was wondering through the different posts of flashing recoveries and stock ROM's. Thats when i came across a thread which said that after wiping the storage(or something like that) while in MIUI i must boot MIUI once and then only my whole storage will be seen otherwise i would not get my whole storage. I don't remember who's post it was. Though i followed the instructions and now am using lineageOS.
Well,but the issue is not with my RN3, instead its with my letv le 1s in which i recently flashed lineage and now i have that error of not getting all the storage. In the guide i referred to,there was no mention of booting back to the Stock ROM,so after a wipe,i simply flashed Lineage OS.
Now i see 29.5gb used of 29.11 gb in storage although I don't have a single thing in there.
I know its off topic in terms if the phone bit I don't think the letv forum has people who will help me or maybe have the ability and experience to help me. So, its a request, before replying that i am not in the right place please help me if you can. Thanks.
Click to expand...
Click to collapse
Format your data partition.
JLius said:
Format your data partition.
Click to expand...
Click to collapse
Fixed now. I did tried formatting but earlier i wiped the internal storage but this time i wiped it from format data option and its done. Thanks fit the reply
Sent from my Pixel XL using Tapatalk
Currently, I'm using TWRP 3.2.1-0 and I managed to get it to flash a ROM only once so far. I've already done some searching on what this error means which apparently just says that it fails checking for the proper make/model of the device so that it won't flash something its not suppose to. Except, I have a ROM for the device...
When I first flashed, I had no choice but to do a factory reset which is really a given anyway. But now... its another story. Trying to flash a an updated LineageOS ROM for instance to the latest nightly for instance, will always result in an Error 7. I don't really want to do a factory reset again if I can help it though, even though I do have two points of backup just in case... Not sure if anyone else is having issues about this or not, but figured I'd point it out for now.
TwinShadow said:
Currently, I'm using TWRP 3.2.1-0 and I managed to get it to flash a ROM only once so far. I've already done some searching on what this error means which apparently just says that it fails checking for the proper make/model of the device so that it won't flash something its not suppose to. Except, I have a ROM for the device...
When I first flashed, I had no choice but to do a factory reset which is really a given anyway. But now... its another story. Trying to flash a an updated LineageOS ROM for instance to the latest nightly for instance, will always result in an Error 7. I don't really want to do a factory reset again if I can help it though, even though I do have two points of backup just in case... Not sure if anyone else is having issues about this or not, but figured I'd point it out for now.
Click to expand...
Click to collapse
Downgrade to twrp 3.1.1-0 and try again...
No dice. Actually this was the second time I tried doing it like that. Doesn't matter which recovery I use be it 3.1.1, or 3.2.1. Both results in the same error regardless. Its like TWRP downgraded after it hit v3 because never once had I ever encountered a problem when I used it back on 2.8.7 (or 2.8.6, I can't recall back when Moto X (ghost) was my main device).
TwinShadow said:
No dice. Actually this was the second time I tried doing it like that. Doesn't matter which recovery I use be it 3.1.1, or 3.2.1. Both results in the same error regardless. Its like TWRP downgraded after it hit v3 because never once had I ever encountered a problem when I used it back on 2.8.7 (or 2.8.6, I can't recall back when Moto X (ghost) was my main device).
Click to expand...
Click to collapse
What is your exact model - what's written on the box and what is the model shown in Settings on your stock firmware (if you remember).
I have a sneaking suspicion that it may not be the exactly same device as ours - E5823, creating a conflict somewhere between Firmware/Recovery. Generally, it should get the device data from prop files but you never know I guess...
Here is what you can try: Install latest firmware for E5823 from XperiFirm in Flashtool and wipe everything. If you don't wipe old files are still going to stay! Also, make a backup of all your stuff so you don't lose it. There are guides how to do it here and what things to not wipe in any case.
The device model is indeed a E5823. This has been reported as such in the official firmware as well.
Currently I don't have any of the official firmware files, and I would like to avoid having to set up my phone again if I can help it; even with a nandroid of my current install handy... Its simply just a pain to get all that done.
The last 2 nightlys don't work properly!! I have clean installed, wiped everything and gone back to stock and tried and tried again and again!! 20180318 is the one that is true!! Try flashing that build!!
TwinShadow said:
The device model is indeed a E5823. This has been reported as such in the official firmware as well.
Currently I don't have any of the official firmware files, and I would like to avoid having to set up my phone again if I can help it; even with a nandroid of my current install handy... Its simply just a pain to get all that done.
Click to expand...
Click to collapse
The thing is some partitions get updated only in that way - like baseband for example. Ensuring everything is the latest version and on a clean slate will remove the chance of weird bugs that nobody knows about or can help you with.
Well, here's the irony. I reflashed your TWRP again, twice for that matter.. (I've had random cases where fastboot won't flash it the first time even though it said it did) and all of a sudden it started working. Android never ceases to amaze me when things want to work, and when things don't...
TwinShadow said:
Well, here's the irony. I reflashed your TWRP again, twice for that matter.. (I've had random cases where fastboot won't flash it the first time even though it said it did) and all of a sudden it started working. Android never ceases to amaze me when things want to work, and when things don't...
Click to expand...
Click to collapse
Lol. I have never had that :d and that is from years and years of use and multiple Sony devices...
My guess is a bad flash. That happens rly rarely but maybe u have a bad PC or cable that makes an unreliable connection...
Same thing happened on my old Moto X (2013) on my last system and the new tower I built. For some reason its something to do with fastboot for me, I really don't know. Either that, or its just Windows trying to fight me every which way it possibly can before something wants to work. Its a daily thing I have to deal with, no idea why. Must be my disdain for Windows perhaps..
TwinShadow said:
Same thing happened on my old Moto X (2013) on my last system and the new tower I built. For some reason its something to do with fastboot for me, I really don't know. Either that, or its just Windows trying to fight me every which way it possibly can before something wants to work. Its a daily thing I have to deal with, no idea why. Must be my disdain for Windows perhaps..
Click to expand...
Click to collapse
You might wanna ensure you have the latest fastboot drivers installed under 'Disable driver verification' mode.
Can someone help me?
I installed a custom rom last month, instead of using the custom rom recovery I installed TWRP, everything worked correctly, but now I want to reinstall the rom with clean flashes, I managed to clean it and go to factory reset, everything appeared successfully, but when I went to install the rom, TWRP returned the error "Error installing zip file"
I tried a few times to repeat the process, I restarted in twrp, I tried to extract and zip the rom again, nothing works and always this same error.
however when I started the cell phone it started normally with the rom in the old version, but this time it was formatted and everything works normally.
Can someone help me? I'm really scared of doing something wrong when I try again, I want to use my own Custom Rom recovery because TWRP is detected in a game that I play a lot
darkkerr said:
TWRP returned the error "Error installing zip file"
Click to expand...
Click to collapse
there's specific error codes which twrp gives to you... to find the exact issue can you take a screenshot of the error on twrp?
as far i know , only a format data is enough... there is no need to flash the rom again.
darkkerr said:
TWRP is detected in a game that I play a lot
Click to expand...
Click to collapse
never heard about that... maybe you mean root access is detected. apps cannot detect a custom recovery
darkkerr said:
Can someone help me?
Click to expand...
Click to collapse
this must be fixed with a clean miui installation (via MiFlash) and then come back to custom rom but if you can send a screenshot of the error we can make a better diagnostic
alonsoj636 said:
there's specific error codes which twrp gives to you... to find the exact issue can you take a screenshot of the error on twrp?
as far i know , only a format data is enough... there is no need to flash the rom again.
never heard about that... maybe you mean root access is detected. apps cannot detect a custom recovery
this must be fixed with a clean miui installation (via MiFlash) and then come back to custom rom but if you can send a screenshot of the error we can make a better diagnostic
Click to expand...
Click to collapse
I'll send a print when I have a little time to backup everything and be able to do everything.
the game is called Ingress Prime, I don't know how but it seems that it detects TWRP, I've done the whole process to hide the root, safetynet worked, I've deleted the folder that twrp creates and I've also changed the name of that folder, the game it just won't open, and I only see reports of this problem with people using TWRP.
all bank applications that I use work normally, including some government applications that do not accept root, all work, except ingress prime.
do you have any idea what i can do? I really like this game and it's tiring to leave the house with two cell phones with one of them having only the purpose of playing a game
darkkerr said:
do you have any idea what i can do? I really like this game and it's tiring to leave the house with two cell phones with one of them having only the purpose of playing a game
Click to expand...
Click to collapse
well ... i tried the game but sadly it didn't worked for me ... just a black screen
tried with twrp but also with the lineage recovery and also without magisk but was useless.
alonsoj636 said:
well ... i tried the game but sadly it didn't worked for me ... just a black screen
tried with twrp but also with the lineage recovery and also without magisk but was useless.
Click to expand...
Click to collapse
thanks for trying, I really think there's no way if I want to use a custom rom I won't be able to play ingress on the same smartphone
https://www.reddit.com/r/Ingress/comments/f001vh