Which one do you guys recommend the most?
I'm on stock Oreo (soak 4) and I'm curious about PE.
What can you guys tell me about it?
Pixel Experience!! Because it gives you some pixel like features. And I've noticed that stock ROMs usually have problems with Root!! When I had rooted my device the camera had stopped working. I tried everything but the only way to get it to work was uninstalling magisk!
S4xk said:
Pixel Experience!! Because it gives you some pixel like features. And I've noticed that stock ROMs usually have problems with Root!! When I had rooted my device the camera had stopped working. I tried everything but the only way to get it to work was uninstalling magisk!
Click to expand...
Click to collapse
But how am I getting sure that don't ruin my IMEI or persist in the process of trying Pixel Experience?
eder5jga said:
But how am I getting sure that don't ruin my IMEI or persist in the process of trying Pixel Experience?
Click to expand...
Click to collapse
Just make sure you backup those partitions on TWRP preferably on an external drive for safekeeping. Or if you loose them there's a guide here on xda that allows you to restore it but you'll end up getting your internal storage wiped in the process. I'd rather advice you to backup system, data( if you want ), persist, efs, and maybe even oem (for when you use treble ROMs in future).
Related
Recently I made a backup before installing a ROM on my oneplus 2. When I was doing it I selected the Boot, System, Data partitions. Then after I restored it everything was working fine except when I was trying to type in my password(not SIM password) it seemed to just restart the UI, but the strange thing was that the Finger print sensor was working I could unlock it that way. So I tried to go in to security setting after that and that also made my UI restart and just threw me back to the home screen. So my question is what mistake did I make when making the backup and how not to make it again?
Perhaps your persistant-partition (where fingerprint data and other security stuff is stored) is damaged. There's an persistant.img which you can flash in fastboot to restore it somewhere here on the op2 forum which you can find if you search.
Best regards
Peter
pitrus- said:
Perhaps your persistant-partition (where fingerprint data and other security stuff is stored) is damaged. There's an persistant.img which you can flash in fastboot to restore it somewhere here on the op2 forum which you can find if you search.
Best regards
Peter
Click to expand...
Click to collapse
But when I install oxygen OS image it works, it just doesn't work when I restore it from a backup.
winVIP said:
Recently I made a backup before installing a ROM on my oneplus 2. When I was doing it I selected the Boot, System, Data partitions. Then after I restored it everything was working fine except when I was trying to type in my password(not SIM password) it seemed to just restart the UI, but the strange thing was that the Finger print sensor was working I could unlock it that way. So I tried to go in to security setting after that and that also made my UI restart and just threw me back to the home screen. So my question is what mistake did I make when making the backup and how not to make it again?
Click to expand...
Click to collapse
Were you on CM13 and installed the H2OS MM firmware? If so, I ran into a similiar thing. You'll may need to flash the Revert2Lollipop to fix.
unremarked said:
Were you on CM13 and installed the H2OS MM firmware? If so, I ran into a similiar thing. You'll may need to flash the Revert2Lollipop to fix.
Click to expand...
Click to collapse
No, I was making a backup of oxygen OS 2.2.1 before installing Resurrection Remix.
Recently, I purchased this phone & like all previous Android devices, I usually look to root them for more control & better performance.
The program I used: Moto G5+ Toolkit (TWRP & root). Phone is running Android version 7.0 Baseband version: M8953_13.20.07.21R POTTER_NA_CUST Kernel version: 3.18.31-perf-gb921c2f-dirty [email protected] #1
After the phone flashed, everything was working except the camera & the flashlight.
I've tried everything I know from clearing the caches to uninstalling the camera, reinstalling, updating, different camera apps & safe mode to no avail. The camera worked great prior to unlocking the bootloader/root.
Some further research from around the web shows this has been a major issue yet there appears to be no solutions (possibly reflashing a different OS).
I've backed up the original phone files but I'm not able to reflash it as when I reconnect the Moto G5+ toolkit, I'm given the message "ADB Unauthorized."
Anyone know if there are any solutions/possible patches?
Thank you.
I have the same issue. I'm going to flash the stock rom again and be unrooted for the present, just clean install, with unlocked bootloader. I don't want to risk bricking my device!
OK redid everything, rooted, followed all steps, I"M ROOTED but camera still doesn't work, closes everytime I try to open it, I tried wiping cache thru TWRP recovery but that did nothing.
Same here
With the time I'm spending on this, I am thinking about shooting this phone, literally, and just getting something else. I thought it was just me that can't figure it out as a novice, but it's even looking like the super smart tech people can't figure this one out either. I think I'm going to try one of these custom roms and pray....If you hear a loud shot, it's just me killin my g5.
Greeneyedblackpanther said:
I think I'm going to try one of these custom roms and pray
Click to expand...
Click to collapse
Did it work after installing any custom ROM? I am facing the same issue here.
Greeneyedblackpanther said:
With the time I'm spending on this, I am thinking about shooting this phone, literally, and just getting something else. I thought it was just me that can't figure it out as a novice, but it's even looking like the super smart tech people can't figure this one out either. I think I'm going to try one of these custom roms and pray....If you hear a loud shot, it's just me killin my g5.
Click to expand...
Click to collapse
I fixed this problem for my Moto G5 Plus. If your device is indian version (XT1686), install stock ROM. I was facing same issue. Installed below stock rom.
https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/
File Name - POTTER_NPN25.137-92_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Folllow steps given in this video -
https://www.youtube.com/watch?v=-FszZOx2pWU
Hi, I'm here to ask for your help because I don't know what to do.
Since the update to xXx 9.6 no limits my Oneplus 5 runs in slow motion, the applications take a lot of time to open it is unusable. Even the startup animation is slow.
I've already reformatted everything, flash with unbrick tool but it's the same.
I have the impression that only when I format in F2FS it works normally but I can't find a compatible Rom. Thank for your help.
Have you tried another aosp rom or just the stock rom some tweaks of the xxx might be causing some issues
Thesuprememonkey said:
Have you tried another aosp rom or just the stock rom some tweaks of the xxx might be causing some issues
Click to expand...
Click to collapse
I have try xXx, Stock Rom and Lineage OS
mrsachou said:
I have try xXx, Stock Rom and Lineage OS
Click to expand...
Click to collapse
That's weird do you have any heavy syncing apps ?? When did you start noticing the problem ? immediately after 9.6xxx update or after installing a certain app ? Have you tried changing the kernels ? Try decrypting and then Omni since it's a stable 8.1 rom
Thesuprememonkey said:
That's weird do you have any heavy syncing apps ?? When did you start noticing the problem ? immediately after 9.6xxx update or after installing a certain app ? Have you tried changing the kernels ? Try decrypting and then Omni since it's a stable 8.1 rom
Click to expand...
Click to collapse
I start notice when i install the new Snapchat.
I'm gonna try thanks
You formatted the data (which wipes everything on your device ) or just wiped the partitions? If you completely formatted and are experiencing the exact same issue on LOS and xXx there are several possibilities -- 1) You have a hardware issue; 2) You are using corrupt or mismatched firmware; 3) A third party app is causing the issue. The last one is very easy to check--just boot your OP5 into Safe Mode and see if the issue persists. If you encountered the issue on stock OOS and did a clean install after formatting your data then it shouldn't be a firmware issue.
It's very important that you completely format all the data on your phone--not wipe the partitions or format them individually because you need a fresh start in case it's just an issue with corrupted data. My guess based on everything you wrote is that you have a hardware problem and need to have your phone serviced.
It appears that a couple of people tried flashing the Pixel 2 XL system.img onto the Essential PH-1, and was able to boot it, and have (almost) everything working:
https://forum.xda-developers.com/es...ashed-img-pixel-2-xl-opm2-171026-006-t3805921
This didn't used to be the case when the PH-1 was on 8.0. The people there mentioned that they went directly from having official Essential 8.1 June firmware installed and just flashing the Pixel system.img. All it took from that point on was a data wipe and it (allegedly) booted (almost) flawlessly. Some folks there also mentioned that Pixel 2's Android P DP3 system.img booted successfully as well.
@phhusson thoughts?
It boots the same right after oreo or P. There is no mobile data, so no calls or text. I fixed the camera, which was the other bug. I tried flashing my phones vendor images and modem over top of this and it still doesnt fix it. Must be in the system some place. I may try to swap out some lib, or hw files. Then maybe look at the build prop
i have done thins as well...boots flawlessly but as stated, no service or wifi for me...how was the camera fixed?
BakedTator said:
i have done thins as well...boots flawlessly but as stated, no service or wifi for me...how was the camera fixed?
Click to expand...
Click to collapse
I kept a folder of all camera related lib files from our Android p stock, then after booting this, i just used trial and error till i got the camera working. I am certain i could replicate but until we fix the no service probs i stopped messing with it. Just wasnt worth it. I moved on to flashing as many treble gsi's as i could. They all work mostly except for play store issues.
it also works on the Leeco Pro 3 X7272/720
Everything works. Except for call sound
tsongming said:
it also works on the Leeco Pro 3 X7272/720
Everything works. Except for call sound
Click to expand...
Click to collapse
Flash Pixel2XL's A/B system.img to A-only LePro3 directly???
qqzwc said:
Flash Pixel2XL's A/B system.img to A-only LePro3 directly???
Click to expand...
Click to collapse
System A only
However, unless this file has been updated you are better off following the GSI instructions in my signature.
or here: https://forum.xda-developers.com/le...nstall-gsi-t3843142/post77636477#post77636477
Fingerprint Scanner Null after Pie ROM Flash - Custom ROM won't fix. Stock Only
Ok, the story.... Moto G5+ retail, running 8.1 Oreo, Bootloader Unlocked, rooted using Magisk 16.7 and was able to backup my Stock Oreo ROM once rooted, or I'd be dead in the water.
So wanting to stay ahead, I tried my hand at RR v7's Pie version, which, after some troubleshooting, was able to install successfully; but I don't much care for the google bar and other hard-coded "pure android" features. Same thing with Pixel Exp. Not to mention that Pie disallows call recording among a few other things Google decided to stifle its customers with. Deal breaker. So - moving on...or back for that matter.
I proceeded to download RRv6, which is btw running nicely on a 2nd G5+, same GApps, installs perfect except - FingerPrint Reader is not acknowledged. Period. No Security settings, No RR Config to access it, Nada. No matter what ROM I flash outside of the StockROM I backed up, it won't recognize the fp reader upon boot up. Whether I clear Dalvik/Cache, All DATA, do a full Wipe, DATA WIPE, REPAIR, FORMAT, nothing allows me to install RR v6.0 or any other flavor, Oreo or Pie, even while trying a dirty flash over Stock Oreo on this Moto G5+. Tried with several SD Cards, downloading fresh zip files from RR. I even went so far as to image the working G5+, then copy into the 2nd G5's SN folder, and do a restore, just loops - even after repairing the partition. I managed to work around that, Restored the image, but still no FP recognized by the initial Google startup/setup. It's almost as if the phone's been "firmwared" or "tagged".
Any ideas what could be lingering from Android Pie that would survive a F2FS/exT Format? Because something updated some kind of firmware on the phone during a Pie ROM flash, that now won't let me go back to anything below Pie, with a working fingerprint reader. The only difference between the G5 that works and this one is the working one has never seen Android 9. And it's staying that way til we come up with a way to hack the google crap.
Any help would be - awesome to say the least.
Thanks for looking.
Hello,
The issue with fingerprint is that after flashing stock Oreo ROM it replaces some files related to fingerprint sensor.
Hence all the newer custom ROM builds use the Oreo firmware related files. Hence it worked on the Pie ROM.
RR v6 would be still using the old nougat firmware hence you need to flash a file for it work. Which will replace the fingerprint related files for Nougat Stock firmware:
https://androidfilehost.com/?fid=1322778262904029634
In case you want to revert the changes and use Pie ROMs:
https://androidfilehost.com/?fid=1322778262904029635
sharan.nyn said:
Hello,
The issue with fingerprint is that after flashing stock Oreo ROM it replaces some files related to fingerprint sensor.
Hence all the newer custom ROM builds use the Oreo firmware related files. Hence it worked on the Pie ROM.
RR v6 would be still using the old nougat firmware hence you need to flash a file for it work. Which will replace the fingerprint related files for Nougat Stock firmware:
https://androidfilehost.com/?fid=1322778262904029634
In case you want to revert the changes and use Pie ROMs:
https://androidfilehost.com/?fid=1322778262904029635
Click to expand...
Click to collapse
That would make sense if PHONE1 manifested the same thing. But I went from StockOreo to RRv6-Oreo w/out losing anything and having to flash any FP Firmware. I used the RRv6 Official from 18-0911. Which is what's been leading me to believe there's something awry with this 2nd G5. I wonder is it possible PHONE2 has some slight firmware variance that is simply ignoring during the RR flash? Anyway, I'll give this a shot. this is TWRP flash, not fastboot, yes? Just being clear as I'm not proficient at this just yet.
Thanks Sharan!
DJScribe said:
That would make sense if PHONE1 manifested the same thing. But I went from StockOreo to RRv6-Oreo w/out losing anything and having to flash any FP Firmware. I used the RRv6 Official from 18-0911. Which is what's been leading me to believe there's something awry with this 2nd G5. I wonder is it possible PHONE2 has some slight firmware variance that is simply ignoring during the RR flash? Anyway, I'll give this a shot. this is TWRP flash, not fastboot, yes? Just being clear as I'm not proficient at this just yet.
Thanks Sharan!
Click to expand...
Click to collapse
Yeah, give it a try. And yes it's to be flashed via TWRP.
[SOLVED]
sharan.nyn said:
Yeah, give it a try. And yes it's to be flashed via TWRP.
Click to expand...
Click to collapse
Sweet! I had to reflash from scratch as for some reason it wouldn't let me update the ROM already running. But once I re-flashed RRv6-8.1, then flashed FP, it's now back. You rock Sharyn - nice work!
Now if only we found a way to cleanup that Pie - hate the perpetual time stamp, search bar and inability to record voice. Which is why I'm staying on Oreo til further notice. I know it was Google who took it away on v9.
Thanks again Shar!
:good::victory:
DJScribe said:
Sweet! I had to reflash from scratch as for some reason it wouldn't let me update the ROM already running. But once I re-flashed RRv6-8.1, then flashed FP, it's now back. You rock Sharyn - nice work!
Now if only we found a way to cleanup that Pie - hate the perpetual time stamp, search bar and inability to record voice. Which is why I'm staying on Oreo til further notice. I know it was Google who took it away on v9.
Thanks again Shar!
:good::victory:
Click to expand...
Click to collapse
Crap - so turns out this solution was short-lived. FingerPrint Scanner is back to inactive and FPzip isn't fixing it. Only StockOreo brings it back. Tried a plethora of ROMs from Nougat to Oreo, nothing but Pie and stock Oreo. Symptoms say it's the ROM, but a ROM that is currently working on the 1st G5 won't work either. Still looking for solutions, anyone...