Database Users

Fingerprint with Lineage OS and Ressurection Remix nougat

Hi everyone,
I have a little problem with fingerprint with these 2 roms.
Normally I could add 5 fingers but I can only 3 max. If I try to configure the last 2, all my fingerprints dont work at all.
Moreover I can't delete fingeprints. When I try, they come back.
That is an issue which not occur with 6.0 custom roms.
Someone know how to fx it?
Thanks.

I'd suggest flashing the stock nougat 93-11 or 93-14 firmware (e.g. from the guides section) to resolve your fingerprint issues. Once that's done, future installs of lineage and RR should have fingerprint support for more than 3 fingers.

Thanks for replying.
I have xt1642. Is there a stock firmware Nougat for this device? I didnt find it

Nicozyp said:
Thanks for replying.
I have xt1642. Is there a stock firmware Nougat for this device? I didnt find it
Click to expand...
Click to collapse
I've got an XT1642 (UK - retGB, EMEA baseband) and updated to Nougat 93-11 using the stock files on here okay (now running Lineage with 4 FPs set).
The ROM I used to upgrade was the one linked here: https://forum.xda-developers.com/moto-g4-plus/how-to/guide-install-official-december-nougat-t3518262 This will bring you up to the official 93-11 update via installing from stock recovery - you need Marshmallow build 139-63/64 however.
However, you may like to try either of these guides as well: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612
As long as you can successfully install a Nougat stock ROM onto your device, the updates should mean your fingerprint sensor works properly in the custom ROMs. Bear in mind that updating to Nougat may wipe your data and cause you to lose TWRP/root until you re-install them.

Last question: can I wipe system and internal storage before installing ressurection?

Nicozyp said:
Last question: can I wipe system and internal storage before installing ressurection?
Click to expand...
Click to collapse
Once you've installed Nougat (and I recommend installing TWRP too), if you wish to install Resurrection Remix, only wipe system, data, Dalvik and cache. Don't wipe internal storage, since that's where your ROM zip is stored!
Silesh's initial post on the RR version for Moto G4s has more information on this https://forum.xda-developers.com/moto-g4-plus/development/rom-resurrection-remix-n-5-8-0-t3507275

Unable to flash stock recovery => "image not signed or corrupt"

Nicozyp said:
Unable to flash stock recovery => "image not signed or corrupt"
Click to expand...
Click to collapse
The image is flashed. Boot into recovery and you'll realize.

Nicozyp said:
Unable to flash stock recovery => "image not signed or corrupt"
Click to expand...
Click to collapse
Which file are you flashing? Does it end in OKAY after that error?
EDIT - zeomal is too quick for me

Indeed it's ok.
For the moment I upgrade MM, then gonna flash stock Nougat.

So problem solved.
I've flashed RR and configured fingerprint ==> it works fine
Thanks for ur help and advices

fingerprint option is not displayed in my zuk z1
Hey I have installed official lineage-os on my zuk z1 handset but still I can't find fingerprint option in my zuk
What to do help me

Massive WIFI problem after trying to update to Oreo

Long story short I wanted to update to oreo from the latest version of Oxygen OS so I downloaded the update through a VPN which caused my phone to bootloop. In the process of recovering everything, i had to format all data so I formatted everything and reinstalled a stable version of oxygen os from their site. Now all of a sudden I couldn't connect to wifi as it said it was disabled however I fixed this by defaulting my mac address but apparently that didn't work as it connected to the wifi but nothing actually loads or works. Much help would be appreciated!
Note : Wifi only connects if its set to static IP however when changed to DHCP it gets tuck on obtaining an IP adress.

Same problem... Please help us out, been stuck trying to figure this out for hours now with no success. Thanks

Same here I'm going to look to see if there's a way to reset DHCP then you've given me a clue.
Nope this doesn't seem to be the issue in my case the phone won't even associate with router according to the router.
---------- Post added at 07:29 PM ---------- Previous post was at 07:02 PM ----------
My logcat isn't giving me a lot of clues,
--- redacted ---
Click to expand...
Click to collapse

same problem, downgraded back to nougat and the problem still persists

So I've done some more ground work it appears TWRP can't properly upgrade the phone however the stock recovery can via an ADB sideload.
My suspicion is the DM-verity doesn't actually work right or that magicsk 14.6 is not compatible with our version oreo.
Unfortunately I rely on root for a few important functions so I'm not about to give that up unfortunately it seems the update does something that cause the wifi to stop working.
I'm looking into an update that was floating around during the oreo beta that allowed people to go from Oreo back to Nougat maybe there were some steps in there that fixed your wifi antennas so they weren't perminently broken and you can safely roll back I'm going to try flashing that next wish me luck.

Although I haven't properly solved this issue I decided to flash the no limits rom which is based on oxygen OS and I flashed the stable Oreo version which fixed the wifi problem that I was having, however when flashing this rom I did use the Blu spark TWRP instead of the original and I'm unsure if that made any difference whatsoever.

Ok so I managed to revert back to Nougat proper here's the procedure
1. Flash stock recovery. Stock recovery does apparently more than just flash the system partition during an ADB sideload
2. boot into stock recovery. Wipe everything System, Wipe Cache, Wipe Personal data
3. Enable ADB sideload
4. Flash OxygenOS OTA proper
5. Allow system to boot verify wireless functionality
6. Boot back into stock recovery
7. Flash the roll back build this will fix any wifi driver issues in a hidden partition I bet. It can be found on the oreo beta post here https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-beta-1-android-oreo-t3710003 or just download it direclty here [Here]
8. After the rollback build finishes booting verify wireless functionality (optional)
9. Flash back your recovery and it should all be working again.
I guess those of us that want a working root and descrypted data will have to wait for either a working dm-verity for oreo or an updated magicsk the current 14.6 doesn't seem to be all that reliable. And all this on christmas!

I had the same issue. Flashing the oreo OTA worked for me.
twrp-3.1.1-1-cheeseburger
download oreo from here: https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-5-0-android-8-0-t3724234

RIT35H said:
I had the same issue. Flashing the oreo OTA worked for me.
twrp-3.1.1-1-cheeseburger
download oreo from here: https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-5-0-android-8-0-t3724234
Click to expand...
Click to collapse
I have now flashed this using the blu spark twrp after getting rid of my custom rom and everything seems to work so thanks!
However I seem to be facing a Magisk issue now no matter what ROM I use when flashing magisk i boot into a black screen until i remove it using the uninstaller

Queried and resolved in below thread.
https://forum.xda-developers.com/oneplus-5/help/wifi-completely-broken-t3721004

vortex-5 said:
Ok so I managed to revert back to Nougat proper here's the procedure
1. Flash stock recovery. Stock recovery does apparently more than just flash the system partition during an ADB sideload
2. boot into stock recovery. Wipe everything System, Wipe Cache, Wipe Personal data
3. Enable ADB sideload
4. Flash OxygenOS OTA proper
5. Allow system to boot verify wireless functionality
6. Boot back into stock recovery
7. Flash the roll back build this will fix any wifi driver issues in a hidden partition I bet. It can be found on the oreo beta post here https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-beta-1-android-oreo-t3710003 or just download it direclty here [Here]
8. After the rollback build finishes booting verify wireless functionality (optional)
9. Flash back your recovery and it should all be working again.
I guess those of us that want a working root and descrypted data will have to wait for either a working dm-verity for oreo or an updated magicsk the current 14.6 doesn't seem to be all that reliable. And all this on christmas!
Click to expand...
Click to collapse
Thank you very much. Back on Nougat now without wifi issues!

It seems like it's probably magisk support since 14.6 current build doesn't work on nougat either.

NO FINGERPRINT ON FULMICS AFTER OREO on H870

I explain my situation:
I was on fulmics 4.2 and everything ok.
Tried a flash oreo without format /data
Bootllop
Ok clean install
Still bottloop
Cleaned everything, installed fulmics + ota
Now all ok except the fingerprint, it is like it does not exist, no option in settings at all.
Does someone have a solution without flashing back a kdz?
Maybe a flashable fingerprint driver?

Same problem
siggey said:
I explain my situation:
I was on fulmics 4.2 and everything ok.
Tried a flash oreo without format /data
Bootllop
Ok clean install
Still bottloop
Cleaned everything, installed fulmics + ota
Now all ok except the fingerprint, it is like it does not exist, no option in settings at all.
Does someone have a solution without flashing back a kdz?
Maybe a flashable fingerprint driver?
Click to expand...
Click to collapse
Same problem with fingerprint with stock version after update.

I solved fkashing stock oreo zip after a full wipe + data.

siggey said:
I explain my situation:
I was on fulmics 4.2 and everything ok.
Tried a flash oreo without format /data
Bootllop
Ok clean install
Still bottloop
Cleaned everything, installed fulmics + ota
Now all ok except the fingerprint, it is like it does not exist, no option in settings at all.
Does someone have a solution without flashing back a kdz?
Maybe a flashable fingerprint driver?
Click to expand...
Click to collapse
with the oreo update there were also update files for the bootloader, you have to flash official nougat to recover the old version of the bootloader because the new bootloader is not compatible with nougat and created problems like the unrecognized fingerprint reader

Mindy07du44 said:
with the oreo update there were also update files for the bootloader, you have to flash official nougat to recover the old version of the bootloader because the new bootloader is not compatible with nougat and created problems like the unrecognized fingerprint reader
Click to expand...
Click to collapse
I have the same problem with lineage 15.1. Flashed Oreo zip to test and now my fingerprint is gone in Lineage. Do you mean flash Nougat kdz to recover old version of the bootloader? or just a nougat zip?
Flashing a Nougat Zip (Open EU)worked for me. No need to flash kdz.

schoeni11 said:
I have the same problem with lineage 15.1. Flashed Oreo zip to test and now my fingerprint is gone in Lineage. Do you mean flash Nougat kdz to recover old version of the bootloader? or just a nougat zip?
Flashing a Nougat Zip (Open EU)worked for me. No need to flash kdz.
Click to expand...
Click to collapse
yes the kdz or otherwise with the zip is possible but check if the files for the bootloader and in the zip

schoeni11 said:
I have the same problem with lineage 15.1. Flashed Oreo zip to test and now my fingerprint is gone in Lineage. Do you mean flash Nougat kdz to recover old version of the bootloader? or just a nougat zip?
Flashing a Nougat Zip (Open EU)worked for me. No need to flash kdz.
Click to expand...
Click to collapse
When you reinstalled lineage did you wipe anything?

Gobrel said:
When you reinstalled lineage did you wipe anything?
Click to expand...
Click to collapse
did a restore of my nandroid backup.

Please explain step by step
So last year i started learning a bit about roms as stuff like that so after searching i saw Fulmics Rom and i chose that one to flash on my device. On that day i was on Oreo. I did all the stuff (format data, wipe...) then flashed the Rom and it was ok But the fingerprint option was there sometimes and sometimes not... After a day or so it expired so i flashed again (after formatting etc) but no fingerprint. So i just gave up, i was happy that i didnt brick my phone so i just accepted it...But today it's kind of annoying i searched a lot and everyone talks about flashing stock Nougat and then the Rom or flash stock Oreo and then Nougat and then the Rom... Well i tried but with no success.
I hope someone can help me with that
Thank you

H918 Stuck on secure startup "decryption unsuccessful" on boot

after doing this https://forum.xda-developers.com/v20/how-to/step-step-guide-lg-v20-h918-unlocking-t3808258
and finally installing a stock based rom, which is Alpha Omega Rom. I get stuck at secure startup and telling that decryption unsuccessful. I tried it with other stock based rom like a prerooted one but the result are still the same. I am never new to this problem and usually this get solved by going to twrp and wiping data(the one you have to type yes) but it did not solve this problem. Really need help badly.

noddledizzy said:
after doing this https://forum.xda-developers.com/v20/how-to/step-step-guide-lg-v20-h918-unlocking-t3808258
and finally installing a stock based rom, which is Alpha Omega Rom. I get stuck at secure startup and telling that decryption unsuccessful. I tried it with other stock based rom like a prerooted one but the result are still the same. I am never new to this problem and usually this get solved by going to twrp and wiping data(the one you have to type yes) but it did not solve this problem. Really need help badly.
Click to expand...
Click to collapse
it seems youre trying to flash a new twrp image that is higher than the allowed 3.2.3-4 in the root process,go to fastboot mode reflash twrp image 3.2.3-4 or an older one.If that's not the issue please provide more information

mikekote666 said:
it seems youre trying to flash a new twrp image that is higher than the allowed 3.2.3-4 in the root process,go to fastboot mode reflash twrp image 3.2.3-4 or an older one.If that's not the issue please provide more information
Click to expand...
Click to collapse
Where does it exactly say that I cannot flash anything higher than 3.2.3-4. All it says is to download the latest twrp from https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239
Do you have a link to 3.2.3-4? It seems like 3.2.3-5 is the lowest twrp I could find in Phoenix591's android filehost https://androidfilehost.com/?w=files&flid=235271
edit: while waiting for responses, I went ahead and installed unofficial LOS15 then I was able to boot without any problem. It seem like this will only happen with stock/stock based roms.

noddledizzy said:
Where does it exactly say that I cannot flash anything higher than 3.2.3-4. All it says is to download the latest twrp from https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239
Do you have a link to 3.2.3-4? It seems like 3.2.3-5 is the lowest twrp I could find in Phoenix591's android filehost https://androidfilehost.com/?w=files&flid=235271
edit: while waiting for responses, I went ahead and installed unofficial LOS15 then I was able to boot without any problem. It seem like this will only happen with stock/stock based roms.
Click to expand...
Click to collapse
You should flash latest after installing this one by installing recovery img in TWRP i am telling you cause i have tried 3.2.3-5+ with the dirty santa process for my phone and thats the message i was getting unless downgrading to 3.2.3-4
Also decryption is unsuccessful comes as a result of not formatting data on twrp after the first install of twrp but you said that you did format data so i thought you were trying to flash newer twrp via the root process of the H918

mikekote666 said:
You should flash latest after installing this one by installing recovery img in TWRP i am telling you cause i have tried 3.2.3-5+ with the dirty santa process for my phone and thats the message i was getting unless downgrading to 3.2.3-4
Also decryption is unsuccessful comes as a result of not formatting data on twrp after the first install of twrp but you said that you did format data so i thought you were trying to flash newer twrp via the root process of the H918
Click to expand...
Click to collapse
do you have 3.2.3-4? I couldn't find it anywhere unfortunately
edit:already solved it by using 3.2.3-0/1 from official twrp website. but the problem is that i get 0mb storage on internal storage on TWRP. I am not exactly new to this problem but even after flashing no verity op encryption zip. I still get it. sigh.

noddledizzy said:
do you have 3.2.3-4? I couldn't find it anywhere unfortunately
edit:already solved it by using 3.2.3-0/1 from official twrp website. but the problem is that i get 0mb storage on internal storage on TWRP. I am not exactly new to this problem but even after flashing no verity op encryption zip. I still get it. sigh.
Click to expand...
Click to collapse
you need to format data first time

noddledizzy said:
after doing this https://forum.xda-developers.com/v20/how-to/step-step-guide-lg-v20-h918-unlocking-t3808258
and finally installing a stock based rom, which is Alpha Omega Rom. I get stuck at secure startup and telling that decryption unsuccessful. I tried it with other stock based rom like a prerooted one but the result are still the same. I am never new to this problem and usually this get solved by going to twrp and wiping data(the one you have to type yes) but it did not solve this problem. Really need help badly.
Click to expand...
Click to collapse
I have this problem too for a couple days a go,
but now it have been fixed.
Flash TWRP 3.2.3 via fastboot
Boot into TWRP
format data
reboot system
done
I think Its TWRP 3.3 bug or something that not decrypt perfectly..
---------- Post added at 01:53 PM ---------- Previous post was at 01:46 PM ----------
noddledizzy said:
do you have 3.2.3-4? I couldn't find it anywhere unfortunately
edit:already solved it by using 3.2.3-0/1 from official twrp website. but the problem is that i get 0mb storage on internal storage on TWRP. I am not exactly new to this problem but even after flashing no verity op encryption zip. I still get it. sigh.
Click to expand...
Click to collapse
Format data

gandyprakoso said:
I have this problem too for a couple days a go,
but now it have been fixed.
Flash TWRP 3.2.3 via fastboot
Boot into TWRP
format data
reboot system
done
I think Its TWRP 3.3 bug or something that not decrypt perfectly..
---------- Post added at 01:53 PM ---------- Previous post was at 01:46 PM ----------
Format data
Click to expand...
Click to collapse
I did format data so many times already that it nuked my twrp(just stopped booting into it all of a sudden, still unsure if that caused it though)

noddledizzy said:
I did format data so many times already that it nuked my twrp(just stopped booting into it all of a sudden, still unsure if that caused it though)
Click to expand...
Click to collapse
Yes me too, and it almost make me crazy back in the days ?
the solution (at least for now) is downgrade TWRP it into v3.2.3-4. flash it via adb fastboot command, format data, then reboot. But sorry i dont have TWRP for H918, becoz im using F800L.. and since your TWRP has been nuked, youll have to reflash TWRP again yes? ?
Or, if youbdont want to downgrade TWRP, you can use AOSP based rom such as LOS15.1.. i already tried that rom and it dont have problem with encrypt/decrypt thing like stock based rom.

gandyprakoso said:
Yes me too, and it almost make me crazy back in the days ?
the solution (at least for now) is downgrade TWRP it into v3.2.3-4. flash it via adb fastboot command, format data, then reboot. But sorry i dont have TWRP for H918, becoz im using F800L..
Or, you can use AOSP based rom such as LOS15.1.
i already tried that rom and it dont have problem with encrypt/decrypt thing like stock based rom.
Click to expand...
Click to collapse
I am currently using v3.2.3.0/1 i couldnt find v3.2.3-4 anywhere.
I am using Resurrection Remix, everything was perfect until i stopped receiving sms once the phone goes deep sleep

noddledizzy said:
I am currently using v3.2.3.0/1 i couldnt find v3.2.3-4 anywhere.
I am using Resurrection Remix, everything was perfect until i stopped receiving sms once the phone goes deep sleep
Click to expand...
Click to collapse
Here it is, hope it helps..
TWRP: https://androidfilehost.com/?fid=11410932744536982445
H918 Prerooted Oreo 20g:
https://androidfilehost.com/?fid=11410932744536989567
H918 SIM Unlock:
https://androidfilehost.com/?fid=11410963190603886898
All credits goes to @Phoenix591

gandyprakoso said:
Here it is, hope it helps..
TWRP: https://androidfilehost.com/?fid=11410932744536982445
H918 Prerooted Oreo 20g:
https://androidfilehost.com/?fid=11410932744536989567
H918 SIM Unlock:
https://androidfilehost.com/?fid=11410963190603886898
All credits goes to @Phoenix591
Click to expand...
Click to collapse
Thank you so much, no wonder i wasn't able to find v3.2.3-4 because it's labeled as the release date. What does the sim unlock do? I mean, I can receive messages and stuff but just not get any once in awhile. Will this actually solve that?

noddledizzy said:
Thank you so much, no wonder i wasn't able to find v3.2.3-4 because it's labeled as the release date. What does the sim unlock do? I mean, I can receive messages and stuff but just not get any once in awhile. Will this actually solve that?
Click to expand...
Click to collapse
Yes i knew that. My TWRP 3.2.3-4 IMG file is labeled with same date like that.
About sim unlock, Actually I dont know for sure because in f800l we dont seeing any sim problem at all.. but in my opinion just download it, in case you seeing problem with locked sim after flashing, it will be very useful..
anyway, i found a thread that discussing about h918 sim unlock thing
https://forum.xda-developers.com/v20/how-to/discussion-t-mobile-sim-unlock-t3821051

gandyprakoso said:
Yes i knew that. My TWRP 3.2.3-4 IMG file is labeled with same date like that.
About sim unlock, Actually I dont know for sure because in f800l we dont seeing any sim problem at all.. but in my opinion just download it, in case you seeing problem with locked sim after flashing, it will be very useful..
anyway, i found a thread that discussing about h918 sim unlock thing
https://forum.xda-developers.com/v20/how-to/discussion-t-mobile-sim-unlock-t3821051
Click to expand...
Click to collapse
Thanks, I will try going back to stock roms and will report back to you.
And I forgot to mention that I already got twrp fixed after it got nuked. Sadly, I don't think fastboot flashing works on h918 so I had to do lafsploit method to flash twrp again.

noddledizzy said:
Thanks, I will try going back to stock roms and will report back to you.
And I forgot to mention that I already got twrp fixed after it got nuked. Sadly, I don't think fastboot flashing works on h918 so I had to do lafsploit method to flash twrp again.
Click to expand...
Click to collapse
Ok then and happy flashing m8 ?

noddledizzy said:
Where does it exactly say that I cannot flash anything higher than 3.2.3-4. All it says is to download the latest twrp from https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239
Do you have a link to 3.2.3-4? It seems like 3.2.3-5 is the lowest twrp I could find in Phoenix591's android filehost https://androidfilehost.com/?w=files&flid=235271
edit: while waiting for responses, I went ahead and installed unofficial LOS15 then I was able to boot without any problem. It seem like this will only happen with stock/stock based roms.
Click to expand...
Click to collapse
Where? Right in the portion where it says Known Issues of the first link.
Downgrading TWRP to 3.2.3-4 will fix it. I had the same issue.

Thanks for the notes. Unfortunately this did not work for me. I ended up in this position after updating Magisk to 20.2, or trying to. My H918 went to being stuck in the fastboot mode. I was able to get to TWRP, and reinstalled H91820h.zip, but then faced with "Decryption unsuccessful" I downgraded TWRP to twrp-3.2.3-0, and deleted everything except the external microsd card, reinstalled H91820h.zip, but still stuck at the "Decryption unsuccessful". Are there other things I should try?
Thanks,
Rob

frohro said:
Thanks for the notes. Unfortunately this did not work for me. I ended up in this position after updating Magisk to 20.2, or trying to. My H918 went to being stuck in the fastboot mode. I was able to get to TWRP, and reinstalled H91820h.zip, but then faced with "Decryption unsuccessful" I downgraded TWRP to twrp-3.2.3-0, and deleted everything except the external microsd card, reinstalled H91820h.zip, but still stuck at the "Decryption unsuccessful". Are there other things I should try?
Thanks,
Rob
Click to expand...
Click to collapse
From TWRP thread:
Changed one last thing to try to fix stock Oreo decryption.
There were an upstream TWRP change that should fix the issue where formatting was still leaving /data encrypted as well (this was actually in the last build, but I didn't notice it then)
Click to expand...
Click to collapse
If you still have your non-Encryption-supporting TWRP as download mode, wipe data from there. For some reason which was documented in the TWRP thread, most versions of V20 TWRP doesn't remove the encryption flag even on a full wipe. I've gone through the pain several times, but here's roughly what I went through about a month ago. It's possible that using the latest TWRP may allow you to skip straight to step 8. As of this latest wipe, I'm finally at a point again where my phone works properly and TWRP can still see my data.
Basic process to hopefully have a working ongoing phone and TWRP:
1. Reboot to download-mode TWRP
2. Wipe dalvik/cache/data from the older download-mode TWRP
3. Factory reset with YES, still in older download-mode TWRP
4. Reboot to system; it should give you the new-system-setup past the Decryption unsuccessful screen on your wiped device
5. Setup without a Google account or fingerprint
6. Reboot back to recovery, not download TWRP; use download mode to get there if you need to
7. Flash the latest TWRP version from the thread (no older than October 25, 2019)
8. Reboot back to recovery
9. Wipe dalvik/cache/data
10. Reboot back to system
11. Setup as you like
12. Reboot back to recovery and make sure you can see your storage
If it gets a decryption error on latest TWRP at step 12 and you can't see data while in Recovery, try skipping adding a fingerprint during setup (run through steps 8-12, no fingerprint on 11) and see if that fixes it.

frohro said:
Thanks for the notes. Unfortunately this did not work for me. I ended up in this position after updating Magisk to 20.2, or trying to. My H918 went to being stuck in the fastboot mode. I was able to get to TWRP, and reinstalled H91820h.zip, but then faced with "Decryption unsuccessful" I downgraded TWRP to twrp-3.2.3-0, and deleted everything except the external microsd card, reinstalled H91820h.zip, but still stuck at the "Decryption unsuccessful". Are there other things I should try?
Thanks,
Rob
Click to expand...
Click to collapse
My solution turned out to be formatting /data. Wiping it was apparently not really wiping it clean. Formatting it got me back to a working phone, though I had to re-install everything.
Thanks everyone for the help!
Rob

anyone knows how to fix fingerprints not working? h990 oreo rom mk2000 kernel is there any fix?
do i need to return to nougat but than what? please help
edit: was able to fix that by flashing nougat modem
now wifi wont turn on tho anyone know how to fix?

flash potter on xt1687 retus?

Just got the xt1687 usa model retus software channel... Is it safe to flash potter roms on here?

itcanbdone said:
Just got the xt1687 usa model retus software channel... Is it safe to flash potter roms on here?
Click to expand...
Click to collapse
What firmware? 7.0 or 8.1? If you are on 8.1 it's as safe as it ever is to flash a custom ROM.
If you're still on 7.0 you should update first and in any case make a full nandroid backup incl. Persist and EFS before you flash anything.
Sent from my Moto G5 Plus using XDA Labs

Currently on 7.0 so unlock bootloader n twrp after update? Thanks

itcanbdone said:
Currently on 7.0 so unlock bootloader n twrp after update? Thanks
Click to expand...
Click to collapse
Yes. If you can update via OTA that should be the way to go. If you can't flash full Motorola signed fastboot 8.1 firmware:
https://mirrors.lolinet.com/firmware/moto/potter/official/
Unlock the BL on Motorola website, boot to or flash TWRP and make a full nandroid incl. persist.
After that you shoud be good to go and flash custom ROMS. Check whether the selected ROM needs 7.0 or 8.1 as base, almost all of them need stock Oreo.
Sent from my Moto G5 Plus using XDA Labs

Oh yeah, I'm rusty.. Software channel duh, linux gets its stuff there... I guess it is potter xt1687, which is odd though as a website said it wasn't potter.. Anyway, looking in the gsm arena and checking against other variants of our g5 plus, it seems that everything but the radios are the same so is it safe to flash variants backing up the original radio? Thank you very much

itcanbdone said:
Oh yeah, I'm rusty.. Software channel duh, linux gets its stuff there... I guess it is potter xt1687, which is odd though as a website said it wasn't potter.. Anyway, looking in the gsm arena and checking against other variants of our g5 plus, it seems that everything but the radios are the same so is it safe to flash variants backing up the original radio? Thank you very much
Click to expand...
Click to collapse
You wrote you're on the retus channel and model is 1687. Here are the firmwares for your device, the second one ( OPS28.85-17-6-2) is the latest and last build, flash that one and everything should be fine:
https://mirrors.lolinet.com/firmware/moto/potter/official/RETUS/
You still know how to fastboot flash? Unzip firmware to ADB/Fastboot folder etc.?
Here's a post I made for someone else, it includes a link to a flashall.bat, put in in there too so you don't have to manually flash all partitions, just double-click it and it'll run all the commands for you.
https://forum.xda-developers.com/g5...solve-imei0-explanation-t3825147/post80478329
Sent from my Moto G5 Plus using XDA Labs

So I was on stock and flashed twrp after successful unlock of bootloader. After backing up, got stuck at bootloader before any further changes made, yet it was booting fine with bootloader before that.. Saw in a post to flash stock after re locking bootloader, then unlick again...
I skipped that just to get a rom on, now running havoc 9.0 but cannot seem to root as the two su & magisk arent cuttin it in twrp.
Are you really telling me I gotta revert back to stock and flash root in stock to get root?
If so, couldnt i just flash havoc 8.1 and root that way.
Yes i still remember how to flash via adb. Thank you very much

itcanbdone said:
So I was on stock and flashed twrp after successful unlock of bootloader. After backing up, got stuck at bootloader before any further changes made, yet it was booting fine with bootloader before that.. Saw in a post to flash stock after re locking bootloader, then unlick again...
I skipped that just to get a rom on, now running havoc 9.0 but cannot seem to root as the two su & magisk arent cuttin it in twrp.
Are you really telling me I gotta revert back to stock and flash root in stock to get root?
If so, couldnt i just flash havoc 8.1 and root that way.
Yes i still remember how to flash via adb. Thank you very much
Click to expand...
Click to collapse
I'm not sure that I understand everything. After flashing (official) TWRP and making a nandroid you weren't able to boot to system, only to bootloader?
Have you updated to 8.1 stock Oreo before?
Havoc needs that definitely:
https://forum.xda-developers.com/g5-plus/development/rom-havoc-os-v2-2-t3906282/post79018816
It won't make any sense to revert to stock and root it because after flashing havoc root will be lost anyway. What do you mean with "the two su & Magisk aren't cuttin it in TWRP"? (English is not my native language)
Why two? There should be magisk only to flash.
So the goal seems to be making TWRP work correctly when running havoc to be able to flash magisk.zip and boot to system.
Can you post a recovery log after the attempt to flash magisk from TWRP (the function is in TWRP/ advanced/log.)
Can you boot to havoc directly now?
Are you able to reach TWRP?
I need the error message that appears when you try to flash magisk, should be in the log.
And what is it about two things, su AND magisk?
Magisk.zip is the su binary.
Please provide some more information and sorry if it's me who don't understand something.
Sent from my Moto G5 Plus using XDA Labs

- I got root after all. Seems I was just flashing no verity before root and it was suppise to be after.
- there was a super su which I'd rather have to mod things with but neither worked until i figured out as mentioned above
- now I'm trying to get gaps to work..
- also having problem flashing rom withou encryption, it keeps forcing it encrypted.
- here is link to 3 images of what i've got currently:
https://mega.nz/#F!q3pVQIDJ!kwfNgjMEEssa97rrZJjWHg
Thanks

itcanbdone said:
- I got root after all. Seems I was just flashing no verity before root and it was suppise to be after.
- there was a super su which I'd rather have to mod things with but neither worked until i figured out as mentioned above
- now I'm trying to get gaps to work..
- also having problem flashing rom withou encryption, it keeps forcing it encrypted.
- here is link to 3 images of what i've got currently:
https://mega.nz/#F!q3pVQIDJ!kwfNgjMEEssa97rrZJjWHg
Thanks
Click to expand...
Click to collapse
Never use SuperSU alongside with magisk but I think you know that now.
To remove encryption: It's not enough to wipe data in TWRP, you have to format it (the option where you have to confirm with "Yes" and not just wipe). That will wipe your internal storage too.
Only formatting data in TWRP will remove the encryption and the Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip will keep it decrypted. Make sure usb debugging is enabled.
Boot to TWRP and flash ROM and Gapps (both in one action without a reboot in between).
Now flash the no verity-force encryption.zip.
You can reboot to system now but you can also flash the magisk.zip directly afterwards, it helps to keep the data partition encrypted too.
I flash everything in a row.
Check that thread: https://forum.xda-developers.com/g5-plus/how-to/guide-how-to-remove-device-encryption-t3863586
(page 2)
Sent from my Moto G5 Plus using XDA Labs

Thanks for the encryption link.. Any idea on the pros n cons on encryption in the world of flashing zips and modding?
I see pros n cons on google search for encryption but not from developments perspective

itcanbdone said:
Thanks for the encryption link.. Any idea on the pros n cons on encryption in the world of flashing zips and modding?
I see pros n cons on google search for encryption but not from developments perspective
Click to expand...
Click to collapse
I decrypt my device, for example to have access to /data in case of a bootloop because of a magisk module. I don't like the idea of not physically seeing parts of my partitions or even not being able to edit it.
From the sight of security it's better to encrypt naturally. It depends a bit how old your device is and what you want to do with it.
I never lost my device or it was getting stolen so as long it's in my pocket I don't need encryption.
But that's just my personal opinion.
Sent from my Moto G5 Plus using XDA Labs

Hey so I found a really cool way to decrypt but ROM after it's already been encrypted and you have all your stuff in it, I figured it out on accident. What I did was simply did a backup through TWRP and formatted the drive. When I restored the drive it was decrypted! And all this time everyone ever told me that you cannot decrypt. Pretty cool. Actually found this out by switching to a ROM and then going back anyway maybe people should know this? Hope it helps thanks for all the pointers