Related
My OnePlus is running on Cyanogenmod 13 by @Grarak. It is so good, that i don't want to shift to any other rom. Thank you @GRArek. But a small problem persists. I can't receive calls. And when i receive a call, the phone reboots. And i don't get any notification about the call. I am pretty sure it's something to do with my phone. Because i tried Resurrection Remix too. The Problem still persisted. I can switch to Oxygen OS but i don't want to. Has anyone experienced the same error or does anyone have the fix?
Thank You very much.
Are you sure you were running OxygenOS 2.2.1 before flashing Graraks latest? Sounds like some of the partitions for the modem must be wrong, I'm using Graraks latest workout calling problems. Once suggestion is to use the Qualcomm restore method to restore back to 2.2.1 and then flash TWRP and clean flash Graraks.
First use twrp to flash full oxygen 2.2.1.
And start again installation of cm13.
If don't work then use fastboot images method.
Sent from my ONE A2005 using Tapatalk
Hi good fellas, so a week back, I flashed mokee build everything was perfect until I received a WhatsApp message from my friend asking me why the hell am I not picking call when it's ringing. I was like what ? Dude send me screenshot and I got roasted. So I tried finding the root cause and got to know sim selection was grayed out.
Issues were,
1. Not able to select sim selection for calls as nothing happens when you click on the selection area. Data works fine for both Sims, I have not tested with SMS.
2. First sim slot works fine for both incoming and outgoing however on the top it shows the second sim name. For example, in my case I'm using Vodafone (first slot) and Tata DoCoMo, so when I make or get a call to Vodafone, it shows me Tata Docomo.
3. There is no way of making calls from second sim.
What did I do?
1. Downloded NucleaRom latest 1.4.1 did a Clean flash (wipe data, cache, dalvik and system) - Did not work.
2. My saviour in flashing, TWRP backups.
Restored NucleaRom 1.3.5 (which was working fine before) - did not work.
3. Restored NucleaRom MM final version 3.0. did not work.
4. Flashed COS 12.1, Bingo got the selection back ( Damn, it has good battery backup) so used it for couple of days.
7. I couldn't take COS Anymore, so downloded last nightly of cm13, clean flash- success
8. Since I'm so addicted to Nougat I wanted to try my luck, tried lates mokee, NucleaRom, RR, sudamod, Cr Droid but it didn't work in any ROM.
9. Back to COS, clean flash, flashed MM Firmware, then Nougat Roms - did not work.
10. Got some update on Nougat ZUI in its XDA post (thanks to developer), downloded both zip and OTA update,clean flashed. Bingo- selection is back. However ZUI still has force close issues
11. Clean flashed NucleaRom, bingo - selection came back.
Not sure what exactly is the root cause since it persists even after clean flash of other ROMS (which were working before) and also backups. If it happens in one ROM, it happens in most or all the Roms. Even in China based ROM.
So, this is the only solution I found, it worked for me. Let me know if it works or if you have any questions.
Thanks to all the developers of Z1. ?
Thanks.
But I think a have found another solution for it.
When I Flash Gapps mini, I have the problem.
But when I Flash Gapps Stock, The default dialer is replaced and then I go to settings and change default dialer to phone(by Google) and sim selection perfect.
Can anyone confirm?
SidthConquerer said:
Thanks.
But I think a have found another solution for it.
When I Flash Gapps mini, I have the problem.
But when I Flash Gapps Stock, The default dialer is replaced and then I go to settings and change default dialer to phone(by Google) and sim selection perfect.
Can anyone confirm?
Click to expand...
Click to collapse
Could be. I had tried with Pico and super. Did not work for me
Sent from my Zuk Z1 using XDA Labs
None of the above two mentioned solutions worked.... can anybody tell me any other way???? i am too disappointed with this problem...
Fahad305 said:
None of the above two mentioned solutions worked.... can anybody tell me any other way???? i am too disappointed with this problem...
Click to expand...
Click to collapse
Is sim selection working on COS, cm13 nightly? What happened when you have flashed zui?
Sent from my Zuk Z1 using XDA Labs
SidthConquerer said:
Thanks.
But I think a have found another solution for it.
When I Flash Gapps mini, I have the problem.
But when I Flash Gapps Stock, The default dialer is replaced and then I go to settings and change default dialer to phone(by Google) and sim selection perfect.
Can anyone confirm?
Click to expand...
Click to collapse
I tried to flash Gapps Stock but it didn't work, Sim selection was still grayed out.
Flashed zui 2.5 Nougat and then clean flashed other Los Nougat ROMs and now Sim selection is working fine.
Thanks for the solution.
SidthConquerer said:
Thanks.
But I think a have found another solution for it.
When I Flash Gapps mini, I have the problem.
But when I Flash Gapps Stock, The default dialer is replaced and then I go to settings and change default dialer to phone(by Google) and sim selection perfect.
Can anyone confirm?
Click to expand...
Click to collapse
I've a same problem haunting me in LOS 14.1, I'll try your solution first...will let you know...
Sent from my ZUK Z1 using Tapatalk
Narasimha12 said:
Is sim selection working on COS, cm13 nightly? What happened when you have flashed zui?
Sent from my Zuk Z1 using XDA Labs
Click to expand...
Click to collapse
my file was corrupt i downloaded it again and bingo. working fine.
thanks
Narasimha12 said:
Hi good fellas, so a week back, I flashed mokee build everything was perfect until I received a WhatsApp message from my friend asking me why the hell am I not picking call when it's ringing. I was like what ? Dude send me screenshot and I got roasted. So I tried finding the root cause and got to know sim selection was grayed out.
Issues were,
1. Not able to select sim selection for calls as nothing happens when you click on the selection area. Data works fine for both Sims, I have not tested with SMS.
2. First sim slot works fine for both incoming and outgoing however on the top it shows the second sim name. For example, in my case I'm using Vodafone (first slot) and Tata DoCoMo, so when I make or get a call to Vodafone, it shows me Tata Docomo.
3. There is no way of making calls from second sim.
What did I do?
1. Downloded NucleaRom latest 1.4.1 did a Clean flash (wipe data, cache, dalvik and system) - Did not work.
2. My saviour in flashing, TWRP backups.
Restored NucleaRom 1.3.5 (which was working fine before) - did not work.
3. Restored NucleaRom MM final version 3.0. did not work.
4. Flashed COS 12.1, Bingo got the selection back ( Damn, it has good battery backup) so used it for couple of days.
7. I couldn't take COS Anymore, so downloded last nightly of cm13, clean flash- success
8. Since I'm so addicted to Nougat I wanted to try my luck, tried lates mokee, NucleaRom, RR, sudamod, Cr Droid but it didn't work in any ROM.
9. Back to COS, clean flash, flashed MM Firmware, then Nougat Roms - did not work.
10. Got some update on Nougat ZUI in its XDA post (thanks to developer), downloded both zip and OTA update,clean flashed. Bingo- selection is back. However ZUI still has force close issues
11. Clean flashed NucleaRom, bingo - selection came back.
Not sure what exactly is the root cause since it persists even after clean flash of other ROMS (which were working before) and also backups. If it happens in one ROM, it happens in most or all the Roms. Even in China based ROM.
So, this is the only solution I found, it worked for me. Let me know if it works or if you have any questions.
Thanks to all the developers of Z1. ?
Click to expand...
Click to collapse
COS 12.1 sim selection was working out of the box.
CM 13 selection was working
LOS 14.1 selection stopped working
Flashed ZUI selection is back
& then clean flashed LOS again selection keeps working
Thanks a lot.
It must be radio baseband issue.
Sent from my ZUK Z1 using Tapatalk
Suggestion
Simply I tried this at my own,
And it worked!
Steps :
1. Install Lineage OS ROM from TWRP. (don't install Gapps)
2. Restart your android.
3. Skip all the startup steps after booting-up.
4. Now go to SIM settings and you see, you are able to select SIM for calls.
5. Select any SIM of your choice.
6. Reboot again into TWRP & install Gapps.
7. Reboot into system.
Now you see, you are able to select any SIM of your choice. :good:
Well...try updating kernel...it worked for me...try radioactive kernel(Radioactive reborn acuicultor) for nougat....here is the process
1)Go to twrp/cwm recovery
2)Perform factory reset and wipe dalvik,data,cache,system
3)first install any nougat rom then install any gapp package for nougat and finally the radioactive reborn kernel for nougat
4)reboot
Bam you are there...should work fine
https://forum.xda-developers.com/zuk-z1/help/network-solution-grayed-solved-t3545218
Can anyone help me in camera issue on nougat....after the clean flash when i open default camera app it works fine in auto mode but when switched to hdr mode then it crashes and says unknown error or cannot connect to camera this error occured in all the nougat rom excpet for los 14.1...Now for los 14.1 camera app works fine for few hours then it lags lije hell touch focus doesnt respond....plzz help
Hello! Im in a bit of a pickle! I have installed the [TWRP]ZUI v2.5.306 through TWRP in hopes to fix the Sim2 slot. Now I cannot access TWRP to try installing Nuclearom back! Now I am stuck with this nougat ZUI. How do I get TWRP back, do I have to ADB Fastboot again? Is it possible that ZUI overwrote my TWRP recovery? Hardware button combination to access TWRP is Vol + and Power at the same time right?
happyflyingipis said:
Hello! Im in a bit of a pickle! I have installed the [TWRP]ZUI v2.5.306 through TWRP in hopes to fix the Sim2 slot. Now I cannot access TWRP to try installing Nuclearom back! Now I am stuck with this nougat ZUI. How do I get TWRP back, do I have to ADB Fastboot again? Is it possible that ZUI overwrote my TWRP recovery? Hardware button combination to access TWRP is Vol + and Power at the same time right?
Click to expand...
Click to collapse
To access the Recovery you have to press the three buttons at the same time (vol+ / vol- / power).
Enviado desde mi ZUK Z1 mediante Tapatalk
happyflyingipis said:
Hello! Im in a bit of a pickle! I have installed the [TWRP]ZUI v2.5.306 through TWRP in hopes to fix the Sim2 slot. Now I cannot access TWRP to try installing Nuclearom back! Now I am stuck with this nougat ZUI. How do I get TWRP back, do I have to ADB Fastboot again? Is it possible that ZUI overwrote my TWRP recovery? Hardware button combination to access TWRP is Vol + and Power at the same time right?
Click to expand...
Click to collapse
Just use "adb reboot recovery" in CMD with USB debugging enabled. Won't have to bother with key combinations. ZUI is installed on system, boot partition, and updates modem partition. Doesn't touch the recovery partition.
I have an SM-N900V (Note 3, Verizon variant, hltevzw).
Detailed timeline:
- I flashed it back to firmware OB6 using Odin 3.09.
- I rooted it using ArabicToolApp.
- I used this tool to unlock the bootloader
- I installed a build of LineageOS 14.1 for hlte
- It didn't recognize the SIM so I did a dirty flash of this build of LineageOS 15.1 for hltetmo on top (hltetmo actually has different hardware than hlte, and the correct one for SM-N900V)
- Messed around with the APNs until it recognized and connected to Verizon's network. I DO have functioning SMS and LTE data, but I have not tested phone calls yet
- Messed around some with SuperSU in system- and systemless-mode. Bricked my device more times than I could count, then unbricked over and over using SuperSU's impeccable installer. Messed around with this quite a bit
- Also messed around with Xposed some. The OS is too unstable to run Xposed Installer correctly, so I uninstalled it
- Removed SuperSU, installed Magisk. Phone now passes SafetyNet
So, my phone now runs 8.1 and a Lineage build from 9 days ago. Cool. But, if I was satisfied I wouldn't be making this post. There are multiple instances of the same kind of "app freeze" - App screen freezes, sometimes it'll go completely black. Interactivity doesn't work, obviously, the app is completely frozen. Hold Back to kill doesn't work (Application Killed toast shows, but nothing happens). ANR (when it comes up) Close doesn't work. Home button works and brings me away from the app, but it's still there. Swipe away in Overview doesn't actually kill the app. Even in App Info, Force Stop doesn't work. The app is forever frozen. Tapping the icon from the launcher no longer does anything, it doesn't even bring up the app. The app is permanently crashed and inaccessible until a reboot.
Issues:
- Sometimes when booting the phone will not recognize the SIM until a reboot. As in, "No SIM" message and everything
- Sometimes it will get stuck at boot, I have foxy-boot installed, so I can see the logs. I don't remember what it was all about, if it comes up again I'll update the post
- Google Chrome sometimes crashes when trying to download a file. I've gotten my phone to self-host before, but this issue always seems to come back, and when it does Google Chrome ALWAYS crashes when trying to download a file. App Freeze
- Netflix installs and logs in but freezes at the "can't connect to service (-9)" message. App Freeze
- Certain apps like NativeScript Playground get stuck at the splash screen. App Freeze
- Xposed Installer did this when opening the Settings, whether Xposed was installed or not. App Freeze
- F-Droid also sometimes crashes, although it's somewhat arbitrary, I can't reproduce it reliably. App Freeze
I have tried reflashing the ROM, flashing Xposed uninstaller, reinstalling Magisk, none of it seems to work. I have TWRP 3.3.0 so I can do pretty much anything that doesn't involve the SD card (the SD card is probably broken in hardware, it's so read-only that Android and TWRP both can't write to it at all, but they can both read the same half-broken filesystem).
I fear that this OS is just too unstable for the phone and there's nothing I can do. I sincerely hope this is not the case.
Try other ROMs or perform a clean installation.
Make sure you are on PL1 bootloader/modem.
Currently using Resurrection Remix v5.8.5 Nougat because it was the last Android version for this device with working Bluetooth calls but if you don't use that feature you could use their Pie version as well.
RR ROMs are solid and work extremely well.
Do a clean installation via TWRP if you go this route.
terminator911 said:
Try other ROMs or perform a clean installation.
Make sure you are on PL1 bootloader/modem.
Currently using Resurrection Remix v5.8.5 Nougat because it was the last Android version for this device with working Bluetooth calls but if you don't use that feature you could use their Pie version as well.
RR ROMs are solid and work extremely well.
Do a clean installation via TWRP if you go this route.
Click to expand...
Click to collapse
I did a clean installation of RR 6.0.0 (Android 8.1) and it works a lot better than LineageOS did, with even more configuration options. I really really hate Pie and its gesture-based gimmicks (Screw you Google for copying more of Apple's bad design decisions), so I assumed Oreo would be more stable, but the ROM I installed still has crashing apps. Google Chrome still won't download most things (I've gotten it to download before), trying to change the accent color crashes the 'LineageOS Settings' app, and F-Droid is seriously messed up, but most other things are stable, including the Verizon network which required no pesky APN setup.
I'm on the OB6 bootloader/modem, is that a problem? I doubt that would be an issue, but I can always back up and reflash via Odin. The cool thing is that I installed a patch to TWRP which backs up /data/media along with everything else, after installing the custom ROM. So, really, I can do anything and be perfectly fine. There's, AFAIK, no way to ruin the phone unless something exploits the eMMC brick bug.
If there's another ROM you'd recommend me install, I'd be happy to try it out. I would really like to have a stable OS on here, where Chrome will work and download files. I'd also love Camera2 API since the phone has the chip for it (Snapdragon 800), but none of the ROMs I have support it and there's been no discussion online other than some years-old threads with no answers. I know there have been some articles online listing Note 3 as a phone that'd support Camera2 API with a software update. Would updating the bootloader/modem do anything on that front?
I would upgrade to PL1 bootloader/modem for your device. This is what I have and have had 0 issues. I'd recommend you trying the Samsung Internet browser over Google Chrome; it's much better in my opinion.
You can find the modem here:
https://androidfilehost.com/?w=files&flid=160694
As far as ROMs are concerned you can either try the Nougat version of RR which is what I am currently using as my daily driver with no issues at all including Bluetooth calls:
[ROM][HLTE\TMO\CHN][OFFICIAL]*** Resurrection Remix N 5.8.5 ***[13.03.2018]
https://forum.xda-developers.com/ga...-resurrection-remix-n-v5-8-3-vanilla-t3615227
See here to check whether or not your phone has the Camera2 API capabilities; if not use OpenCamera.
https://www.androidexplained.com/camera2-api-support/
terminator911 said:
I would upgrade to PL1 bootloader/modem for your device. This is what I have and have had 0 issues. I'd recommend you trying the Samsung Internet browser over Google Chrome; it's much better in my opinion.
You can find the modem here:
https://androidfilehost.com/?w=files&flid=160694
As far as ROMs are concerned you can either try the Nougat version of RR which is what I am currently using as my daily driver with no issues at all including Bluetooth calls:
[ROM][HLTE\TMO\CHN][OFFICIAL]*** Resurrection Remix N 5.8.5 ***[13.03.2018]
https://forum.xda-developers.com/ga...-resurrection-remix-n-v5-8-3-vanilla-t3615227
See here to check whether or not your phone has the Camera2 API capabilities; if not use OpenCamera.
https://www.androidexplained.com/camera2-api-support/
Click to expand...
Click to collapse
Excuse me but custom ROMs don't have "the Samsung Internet browser". Additionally the modem shouldn't cause app crashes (if it does, correct me please).
I might try the Nougat ROM. Bluetooth calls don't matter to me, but stability does. I just kinda really like Oreo and all its customization options but it may be too new for this old phone from 2013. It still works as a phone though, Messages and phone calls work fine, so I may just deal with it.
I use Open Camera, and I've tried multiple Camera2 API enablers. The phone has a Qualcomm Snapdragon 800 and the necessary links (in hardware, between the camera/other things) to support Camera2, but nobody seems to have tried it. Probably because the Verizon Note 3 is really locked down, and can only be rooted on a special version of the samsung ROM, and can only be bootloader-unlocked via the eMMC brick bug... There are Magisk modules for Camera2 on Exynos-based devices, but none for the Verizon Note 3 AFAIK.
I just found out that RR 7 officially supports `hltetmo`, but RR 6 doesn't. That's kinda sad, I hate Pie, but I might try it...
I've had the SEPL stuff before, that's the one that can't be rooted. I suppose I didn't consider upgrading again after I unlocked my bootloader. I'll try SEPL1 firmware again, but with a custom ROM...
You can install the Samsung browser from the Play Store. Again, highly recommended.
As far as SEPL1 just update the modem to it; that shouldn't cause any issues but it will ensure your SIM is recognized and data works with the latest ROMs. That is one requirement you will see listed on all of these ROMs.
Not sure which one you are trying to install but here are all the Resurrection Remix versions:
Nougat:
https://forum.xda-developers.com/ga...-resurrection-remix-n-v5-8-3-vanilla-t3615227
Oreo:
https://forum.xda-developers.com/galaxy-note-3/development/rom-resurrection-remix-n-6-0-0-t3748689
Pie:
https://forum.xda-developers.com/galaxy-note-3/development/rom-resurrectionremix-v7-0-0-t3894244
If you don't care about Bluetooth audio during calls then you can safely use Oreo and Pie options.
terminator911 said:
You can install the Samsung browser from the Play Store. Again, highly recommended.
As far as SEPL1 just update the modem to it; that shouldn't cause any issues but it will ensure your SIM is recognized and data works with the latest ROMs. That is one requirement you will see listed on all of these ROMs.
Not sure which one you are trying to install but here are all the Resurrection Remix versions:
Nougat:
https://forum.xda-developers.com/ga...-resurrection-remix-n-v5-8-3-vanilla-t3615227
Oreo:
https://forum.xda-developers.com/galaxy-note-3/development/rom-resurrection-remix-n-6-0-0-t3748689
Pie:
https://forum.xda-developers.com/galaxy-note-3/development/rom-resurrectionremix-v7-0-0-t3894244
If you don't care about Bluetooth audio during calls then you can safely use Oreo and Pie options.
Click to expand...
Click to collapse
Yeah but, data and calling worked fine on the LineageOS and RR roms, so there's no reason to update the modem.
Besides, I flashed SEPL1 6 times using Odin (multiple times by flashing, rebooting directly into download mode and flashing it once more) and it doesn't want to update. Still on OB6. On the latest (official Pie) RR rom, data worked on first boot but doesn't work anymore (I'm going to mess around with the data settings until it works), but I have no reason to believe that my phone needs a modem update to function.
I did, many times, make calls to various phone numbers and they all worked flawlessly. SEPL1 is therefore not needed if that's all it does.
And I do know about all the Resurrection Remix versions: One is Nougat from their archive, one is the Oreo version I had installed just yesterday before flashing Pie, and the other one is Pie which is now officially supported.
I am currently working on getting RR7 to work, it's only crashed a few times, and I don't even remember what those times were (I think it was using the Back button in Overview/Recents at the same time as the Overview button?)
When updating modem via Odin you have to pull the battery and don't let it reboot the phone for it to stick (disable that option in Odin) and flash it again and then reboot. If you look at the ROM threads for anything newer than Android v5 they all recommend updating to the latest bootloader & modem for your device which in this case is PL1. This can be to prevent crashes/no signal /no SIM, etc...
Are you dirty flashing these ROMs? I have never experienced any crashes with any of the RRs on my phone but I always do a clean install and make sure to also delete the "Android" folder on my SD Card via TWRP after doing the "Advanced" wipe and deleting everything listed there except for the External SD Card.
terminator911 said:
When updating modem via Odin you have to pull the battery and don't let it reboot the phone for it to stick (disable that option in Odin) and flash it again and then reboot. If you look at the ROM threads for anything newer than Android v5 they all recommend updating to the latest bootloader & modem for your device which in this case is PL1. This can be to prevent crashes/no signal /no SIM, etc...
Are you dirty flashing these ROMs? I have never experienced any crashes with any of the RRs on my phone but I always do a clean install and make sure to also delete the "Android" folder on my SD Card via TWRP after doing the "Advanced" wipe and deleting everything listed there except for the External SD Card.
Click to expand...
Click to collapse
"pull the battery and don't let it reboot the phone for it to stick (disable that option in Odin) and flash it again and then reboot"
So...
- Reboot phone into Download mode
- Pull battery while in Download mode
- Flash thingy
- Reboot back into Download mode
- Flash thingy again
? That will be very difficult to do with my dodgy charging cable that doesn't like being repositioned...
I do that without pulling the battery, but I could try it with.
I'm downloading the full SEPL stock image to flash. Once that's done, I'll flash it, reflash TWRP, restore my backup, and see if the baseband has updated.
And no, never dirty flashed the ROM. Always completely wiped data, system, cache and everything. I always backup first. I currently have 3 backups: Lineage OS (before installing RR), RR6 (Oreo), and RR7 (right now before that stock image I'm going to flash).
My external SD card is nonfunctional and read-only with some trash files from the previous phone.
I flashed the stock SEPL ROM. Baseband still didn't change. Restored from backup, SIM now works. Network is detected, SMS and data both work reliably on all reboots.
I will mention that I did brick my phone by using Odin to erase the eMMC, but I fixed that from TWRP, and now everything works flawlessly. There are still some app crashes, but most things are very stable. Camera2 API still nonexistent, which is sad because I got used to it on my old phone, but I shouldn't hope for it.
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...
SOLVED!
First I apologize for the English, I'm using google translator.
Hi everyone, I really need help. Yesterday I used adb to reinstall the stock rom oreo 8.1 (XT1683 POTTER RETRO 8.1.0_OPS28.85) everything went well, until the cell phone started... After installing the rom, I realized that my 4G doesn't work anymore, only the network 3G. When I put on the LTE(4G) network, the network is without signal. I installed more than 4 custom roms in an attempt to restore the 4G signal, but none of them worked. Reading some things here on the forum, I saw that it may have corrupted something in the file system, but I didn't find any solution. My IMEI is normal, the only problem is the 4G network that doesn't work anymore. Anyone have a solution? I don't have any files backed up. I'm currently using the custom rom (dotOS-R-v5.1.1-potter-GAPPS-20210614-0527) and I still have the same problem.
Anyone have a solution? If there is a solution and it is on video, even better. But it can be in text too. thanks in advance
Edit: Now I'm totally out of signal, just Wifi. My IMEI is normal, but I don't have a SIM card signal.
Edit²:
Problem solved.
How did I solve the problem?
I kept installing and reinstalling several roms and nothing worked. So I decided to install the Nougat 7 flashable rom, that's when after installing I realized that the 4g network was re-established. I immediately restarted the phone in recovery mode, accessed TWRP and saved the EFS file to the memory card and a pendrive. I reinstalled the custom rom I wanted and the network stopped working again, I checked and the IMEI was 0 so I restored the EFS file that I had backed up on Nougat 7, and it worked perfectly in the custom rom.
But another problem appeared, the fingerprint did not work. So I reinstalled the custom rom and it didn't work, I reinstalled the Nougat 7 flashable and the fingerprint came back, but when I installed the custom rom again, the fringerprint was disabled again.
To solve the fingerprint issue, I installed the Oreo 8.1 Flashable Rom and then installed the custom rom and the fingerprint issue was resolved.
NOTE: My LTE/4G network was only re-established because my IMEI was not reset, for this reason I managed to save the EFS file and restore it to the custom rom. I don't know it will work on devices with IMEI RESET.
Flashable Roms used:
Nougat 7 Flashable - POTTER
potter-twrp-flashable-NPNS25.137-93-18-aroma
Stock rom Flashable Oreo 8.1 - POTTER
potter-twrp-flashable-OPSS28.85-17-6-2-aroma
I used the roms from this topic: https://forum.xda-developers.com/t/nougat-stock-rom-twrp-flashable-stock-builds.3813351/
Thank you so much @NZedPred , your topic saved me.