Related
Hello,
Firstly, I want to thank the community for all of the wonderful information and work they have done. I truly appreciate it.
But, I was wondering if there are any issues going from an android 7.1 rom to a 6.0 rom. Because, I am currently running the MIUI 8 rom that is 6.0 and I love it, I have always been a fan of MIUI. But, I would like to try out nougat and see how some of those roms run.
I have looked quite a bit for any information on this that is specific to the oneplus 2, but I can't seem to find anything. I am totally willing to jump through a bunch of hoops in order to accomplish this goal, I just need to know what these hoops are.
So, if anyone could help me out with this I would really appreciate this.
Thank you for your time and keep up with the good work everyone
MIUI is based on H2OS. I recommend having OOS 3.5.6 firmware for nougat roms. Now I'm not quite sure what the process is for going back to OOS but someone should be able to guide you through it. Then its just as simple as wiping and flashing a nougat rom.
latestduo said:
MIUI is based on H2OS. I recommend having OOS 3.5.6 firmware for nougat roms. Now I'm not quite sure what the process is for going back to OOS but someone should be able to guide you through it. Then its just as simple as wiping and flashing a nougat rom.
Click to expand...
Click to collapse
Well, when I install a new rom, I usually wipe everything but the internal data. So, from that perspective, does it matter what rom I had installed before I performed the wipe?
SumTuusDeus said:
Well, when I install a new rom, I usually wipe everything but the internal data. So, from that perspective, does it matter what rom I had installed before I performed the wipe?
Click to expand...
Click to collapse
No but the firmware matters, aka which modem firmware 3.5.6 or 3.1.0
I'm not sure but I think the h2os modem firmware is different to the 3.5.6 but I could be wrong
Well, I decided to perform an experiment for everyone and instead of reverting to any other rom, I just wiped like I usually do and installed the Cosmic rom. Everything seems to be working
SumTuusDeus said:
Well, I decided to perform an experiment for everyone and instead of reverting to any other rom, I just wiped like I usually do and installed the Cosmic rom. Everything seems to be working
Click to expand...
Click to collapse
Good for you then. But I higly recommend OOS 3.5.8 firmware as it appears to have fixed network drops for a lot of people. Again I'm not really sure how the roms will handle these fixes but it shouldn't pose any issues.
latestduo said:
Good for you then. But I higly recommend OOS 3.5.8 firmware as it appears to have fixed network drops for a lot of people. Again I'm not really sure how the roms will handle these fixes but it shouldn't pose any issues.
Click to expand...
Click to collapse
Three days and still going strong
SumTuusDeus said:
Three days and still going strong
Click to expand...
Click to collapse
Enjoy then ?
Hi all,
I am new to the Axon 7 community and hopefully this isn't a silly question. I have not seen anything to really explain this - maybe its out there and I missed it.
I see many threads on getting a custom recovery loaded on the phone. In some of them, the TWRP image linked is from the TWRP site (twrp.me) and other times the NetHunter site (nethunter.com). Why would I use a TWRP image from NetHunter and not from TWRP themselves?
Thanks for setting me straight
user7743 said:
Hi all,
I am new to the Axon 7 community and hopefully this isn't a silly question. I have not seen anything to really explain this - maybe its out there and I missed it.
I see many threads on getting a custom recovery loaded on the phone. In some of them, the TWRP image linked is from the TWRP site (twrp.me) and other times the NetHunter site (nethunter.com). Why would I use a TWRP image from NetHunter and not from TWRP themselves?
Thanks for setting me straight
Click to expand...
Click to collapse
Use whichever you like, both work
Just be careful about the version, versions lower than 3.1.0 are dangerous and backing up stuff can wreck your phone
Does that mean it is just a case of someone else built the code then rather than being a modification to the code?
user7743 said:
Does that mean it is just a case of someone else built the code then rather than being a modification to the code?
Click to expand...
Click to collapse
Maybe it is a mirror... can't test but you could compare md5
Understood. I mostly wanted to understand if it was forked for one reason or another. It would appear not.
user7743 said:
Understood. I mostly wanted to understand if it was forked for one reason or another. It would appear not.
Click to expand...
Click to collapse
well there are more than one TWRP versions out there it seems. For example when you flash the universal bootloader TWRP displays 3.1.0-N while on stock 7.1 it shows 3 1.0-0
I've got a little issue myself, twrp installed via add 3.1.0.0 it works I've flashed roms and worked perfectly even though there's no official build for our A7 but yes everything works as it should. OK I backed up 3 backups the original rom and resurrection remix official and Tesla rom they all worked and flashed perfectly using twrp. But 2 of these backups will not restore it fails saying no partition selected but the original rom will back up no problem. And help guys this is the first time I've run into this. I've tried doing via the axon 7 tool also. Thanks in advance.
fastjohnson said:
I've got a little issue myself, twrp installed via add 3.1.0.0 it works I've flashed roms and worked perfectly even though there's no official build for our A7 but yes everything works as it should. OK I backed up 3 backups the original rom and resurrection remix official and Tesla rom they all worked and flashed perfectly using twrp. But 2 of these backups will not restore it fails saying no partition selected but the original rom will back up no problem. And help guys this is the first time I've run into this. I've tried doing via the axon 7 tool also. Thanks in advance.
Click to expand...
Click to collapse
The problem I think is data partition.
Every time I swich rom to oficial I have to format data, wipe dont work. Maybe before restore format data in f2fs or ext4 for oficial rom
Enviado desde mi ZTE A2017G mediante Tapatalk
May sound strange but it was because I flashed the ROM and gapps from my USB c style flash drive so I just decided to do the phone over fresh. It's working 100% all fresh install. Thanks for your help but no matter what I did it wasn't going to install those restores.
Happy New Year everyone!
I am out of ideas, I hope you could help me. I tried to flash and install Lineage OS on my Moto X Style.
Unlocking bootloader went fine, I installed new TWRP 3.2.1.0 and so far it was OK. I flashed LineageOS nightly from 25 Dec with GApps but it won't boot. I have booting animation and from time to time there is very short vibration, just fraction of a second every 3-4 sec. I left the phone for an hour, still stuck on booting animation. I tried to wipe data/cache, tried several other builds from December- all have the same issue. I proceed to other ROMs, all behave in the same way, infinite bootloop. I went to find some solutions on XDA, but nothing seems to work.
I tried restore from backup: https://forum.xda-developers.com/moto-x-style/general/nougat-stock-rom-moto-x-style-xt1572-t3718460 Did not work, I still had booting animation form Lineage OS, even that it suppose to be stock rom.
I try below method to restore stock rom: https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110
With this firmware: https://firmware.center/firmware/Motorola/Moto X Style/Stock/XT1572/ and android 7.0 But I constantly have error msg: "(bootloader) Preflash validation failed FAILED (remote failure)"
I tried to look for solutions but at this point it starts to getting quite too difficult to grasp what should I try next, I do not want to brick the phone for good.
Could you please give me any advice and suggestions? I have Lineage OS on three other devices, never had this type of issues before.
which firmware you were on when you unlocked bootloader and flashed Lineage? Marshmallow or Nougat?
antariksh said:
which firmware you were on when you unlocked bootloader and flashed Lineage? Marshmallow or Nougat?
Click to expand...
Click to collapse
Nougat, 7.0 for sure, with October security patch I think.
zonewelld said:
Nougat, 7.0 for sure, with October security patch I think.
Click to expand...
Click to collapse
Flash this TWRP: https://forum.xda-developers.com/showpost.php?p=74235571&postcount=917
Flash this LineageOS: https://forum.xda-developers.com/showpost.php?p=74980159&postcount=1054
It's a pretty stable build, you might able to get it to boot up.
antariksh said:
Flash this TWRP: https://forum.xda-developers.com/showpost.php?p=74235571&postcount=917
Flash this LineageOS: https://forum.xda-developers.com/showpost.php?p=74980159&postcount=1054
It's a pretty stable build, you might able to get it to boot up.
Click to expand...
Click to collapse
Holly! It boots! Thanks a lot!
I tried a lot of ROMs, but all on 3.2.1 TWRP, maybe that was the problem. Anyway it seems to be fine now, I am very grateful for your help with it.
All the best!
zonewelld said:
Holly! It boots! Thanks a lot!
I tried a lot of ROMs, but all on 3.2.1 TWRP, maybe that was the problem. Anyway it seems to be fine now, I am very grateful for your help with it.
All the best!
Click to expand...
Click to collapse
It wasn't only the TWRP issue. From Marshmallow to Nougat was a major update for our device. Once upgraded to Nougat the data partition format is F2FS am not sure, but hope you get my point.
Developers had to compile ROMs based on this new updated Kernel, Modem and Vendor.
I have been using this unofficial builds for a week now and they are stable. No major bugs.
You can also flash the official Nougat firmware image over fastboot, in case you you wanna go back to Stock.
In case you want to try this old ROMs, you have to flash Marshmallow modem and then it will boot.
antariksh said:
From Marshmallow to Nougat was a major update for our device. Once upgraded to Nougat the data partition format is F2FS am not sure, but hope you get my point.
Developers had to compile ROMs based on this new updated Kernel, Modem and Vendor.
I have been using this unofficial builds for a week now and they are stable. No major bugs.
You can also flash the official Nougat firmware image over fastboot, in case you you wanna go back to Stock.
Click to expand...
Click to collapse
Thanks, I will keep that in mind, but I think I am good for now, had enough of messing with this phone for next couple of weeks
Cheers!
zonewelld said:
Thanks, I will keep that in mind, but I think I am good for now, had enough of messing with this phone for next couple of weeks
Cheers!
Click to expand...
Click to collapse
hahahahaha fair enough. I just compiled Nuclea ROM based on LineageOS for Nougat Kernel and Modem. Feel free to try it next week. Uploading....
antariksh said:
hahahahaha fair enough. I just compiled Nuclea ROM based on LineageOS for Nougat Kernel and Modem. Feel free to try it next week. Uploading....
Click to expand...
Click to collapse
You're evil! I... must... resist... temptation....
Thanks for all your hard work for the community!
I have the habit of always asking on a new device no matter how much I think I know!
I have an xt1635-02 (I am US ATT Prepaid)(nano SIM) supposedly here tomorrow so I've been reading tons here.
However, it seems that a lot of the threads are aimed at rooting stock, which I never do.
As a rule, it's trivial:
[!] In this case it seems best to OTA update stock to 7.1.1 if it isn't already. I believe bootloader must be 7.x.x for doing custom Oreo ROMs . Since mine was 6.0 it took about 8 updates OTA and maybe 2 hours(wifi) .
[!]I go to moto site and do the unlock bootloader dance (already carrier unlocked supposedly).
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
[!]Then flash twrp-3.2.1-0-addison.img (Alberto97) using fastboot on my PC. (Ubuntu 17.10 dev 18.04 with adb and fastboot)(dual boot win7)
I do this twice in a row as I have experienced it not working the first time (dead android LOL).(OCD much??? )
https://forum.xda-developers.com/mo...recovery-unofficial-twrp-moto-z-play-t3495629
- - -
[!] -->then flash Alberto's verity patch mentioned at the top of his TWRP thread
https://forum.xda-developers.com/mo...recovery-unofficial-twrp-moto-z-play-t3495629
This modifies stock. Else your backups of stock won't boot. Learned this the hard way!
- - -
[!]Then use TWRP to backup (default settings) stock a couple of times and put copies of both on PC (via USB on stock).(or if for some reason my USB-C doesn't work, via wifi to my router using filezilla FTP and phone app: "wifi file transfer" by "DNL Media UG"(needs permission storage=on..) - I had to redo this twice - redo this twice - kept dropping back to stock recovery.
[!]Then flash the boot logo using fastboot on PC - I usually use TWRP for this but these that I found here are not set up to be TWRP flash compat so will just remove bin from zip and flash using PC. I think I have about 4 possibilities that I found on these threads. Nice! Easy.
[!]Then boot to TWRP and flash Alberto97's AOSP 8.1 arm64 ROM. Why that ROM you may ask. Been using mainly that Alberto97 ROM on my Moto G3 (32bit version of course), and love it. There's plenty of time to try all the others!!!
I usually consider 2 root options; SuperSU 2.82-SR5, or majisk 1520. (for future readers, these are the latest at this time.)(besides I'm very used to them.)
With SuperSU I have had no probs wiping all 4(Dalvik/ART, system, data, cache), flash ROM, flash 8.1 gapps, flash SUperSU, and boot to install.
With majisk I have sometimes had troubles during install if I flash majisk in the first batch so I tend to wipe all 4, flash ROM and gapps, and boot to install. Then when I finally hit desktop, boot back to TWRP and flash 1520 and reboot.
I need root to use TBPro - no restoring on first time with this 64bit ROM- got to do it the hard way!
SO I believe that's it, but if anyone sees a flaw or problem in there, I would appreciate your help.
Thanks!!!
yep look right, i would have added backup EFS and Modem partitions, if you want to be completely safe.
For now, open gapps 8.1 are only unofficial, i would feel a bit unsecure to use that, but it's only me.
fablebreton said:
yep look right, i would have added backup EFS and Modem partitions, if you want to be completely safe.
For now, open gapps 8.1 are only unofficial, i would feel a bit unsecure to use that, but it's only me.
Click to expand...
Click to collapse
Merci! Many thanks for looking in!!!
Yes, forgot to add that - did much xda search on the efs thing and best I found seemed to be a twrp-3.1.1-0-EFS-addison.img which I may very well flash first and do that since no other TWRP that I looked at offers backup efs. Official and squid2 derived (G3) don't. I assume Alberto's doesn't. Seems like I did it very manually on the G3. If you have it it's a pretty good guarantee that you'll never need it! (Murphy axiom)
As to unofficial gapps, I've been testing about 5 different 8.1 ROMs on the Moto G3 over the past couple months and if the gapps aren't built in to the ROM(some pixelexperience roms), all you can get is an unofficial gapps, or do a minor simple hack to an 8.0 so it will accept it. Usually devs will include it. Bless Alberto97 for not including it so I can select my own!!! But I've had no prob with gapps. Open gapps project has 8.0, but of course they won't work on a true 8.1 unless minor hack. I was planning on using open_gapps-arm64-8.1-aroma-20180109-UNOFFICIAL.zip (from https://cloud.kenzoroms.club/?dir=opengapps) unless you have a better idea. I wanted to grab camera from aroma(somebody's idea), but I also have about 5 other cameras and gcams waiting on the Sdcard that I want to test, simply because there seemed to be disagreement on what works on Alberto's new 8.1 build, so wanted to be able to report.
Thanks again!
backup efs / adb way : https://www.reddit.com/r/oneplus/comments/2zq0ff/friendly_reminder_back_up_your_efs_partition_if/
fablebreton said:
backup efs / adb way : https://www.reddit.com/r/oneplus/comments/2zq0ff/friendly_reminder_back_up_your_efs_partition_if/
Click to expand...
Click to collapse
Thanks for great link! yeah I think I used adb as well as an app last time. I'll add recovery this time so that's 3 backups on internal storage (and copied to PC) should be enough! (yes dear readers I am serious about this - 3 times! They are so tiny! And that pretty much guarantees I'll never need it, but if I do, it's childs play to get it back.)
Thanks!!!
If you're wondering about the delay, they sent me a -01 (Droid)(Murphy's law), so they paid for a UPS next day air label back to them(mailed at 4PM) - don't know if I'll get this going before Sat! Oh well!!! Never take these things too seriously!!! Gotta be costing them a chunk! I did briefly turn it on and stuck the SIM in it and it did show LTE on my ATT, but there's a few bands missing that are on the -02, so will wait. Pretty display, though!!! Really looking forward to it!!!
KrisM22 said:
If you're wondering about the delay, they sent me a -01 (Droid)(Murphy's law), so they paid for a UPS next day air label back to them(mailed at 4PM) - don't know if I'll get this going before Sat! Oh well!!! Never take these things too seriously!!! Gotta be costing them a chunk! I did briefly turn it on and stuck the SIM in it and it did show LTE on my ATT, but there's a few bands missing that are on the -02, so will wait. Pretty display, though!!! Really looking forward to it!!!
Click to expand...
Click to collapse
Good plan on sending it back. You would have been SOL trying to root the -01
dandrumheller said:
Good plan on sending it back. You would have been SOL trying to root the -01
Click to expand...
Click to collapse
Yes! I learned about 5 or 6 phones ago NOT to re-invent the wheel!!!
KrisM22 said:
Yes! I learned about 5 or 6 phones ago NOT to re-invent the wheel!!!
Click to expand...
Click to collapse
Okay, refund for that and order another from somebody else! Next week...!
The only thing is no moto mods on non stock (any thing past 7.1.1 or aosp) roms
punkerEVO said:
The only thing is no moto mods on non stock (any thing past 7.1.1 or aosp) roms
Click to expand...
Click to collapse
yes. stock 8.x is a no-no. This one that is coming is 6.0.1 So I will let it ota update to 7.1.1 after giving it a thorough check-out, then try unlocking it, etc. Sound right? I have no interest in any of the hardware-type addons, just the plain phone 3/32 octacore etc. Why this one? - I love the reception (radio) strength of Motos, plus a ton of other things. I stick with them. Plus it's all Albeto97's fault for deving on AOSP 8.1
Lol Alberto97's roms are buttery smooth!
punkerEVO said:
Lol Alberto97's roms are buttery smooth!
Click to expand...
Click to collapse
I think they are. He recently came out with an 8.1 AOSP version for the Moto G3 and I love it. I test others, but that's my daily driver. Sure not perfect, but quite good enough for me!!! So I figure when I get it (Tues?) that's what I'll put on it. There's always plenty of time to test others!
Okay, since I am waiting for phone (Tues) , obviously I am worried about "what-if"s and so researching on what to do, "if".
I succeeded in finding a nice zip for 7.1.1 with the Nov security patch
https://firmware.center/firmware/Motorola/Moto Z Play/Stock/
(I am US)(there are many others at that nice site!!!)
That took a lot of time.
Then I needed to be sure that I could get RSD lite to run, and tried and tried to no avail to get it to recognize my phone (even on my laptop) (I was testing with an old Moto G3 stock zip and my G3 phone) before some post gave me a version number much higher than at the RSD site. google gave me:
http://rsdlite.en.lo4d.com/
version 6.2.4, which worked perfectly.
I really need to write a short guide on this stuff - feels like I'm re-inventing the wheel, even though many folks have written much before I came along!
The reason for the above two is that for a while the last few days I kept running into folks who had taken 7 OTA and wound up with a bricked phone. So, yes, I just did a search for "brick" on xda in moto z play and will start reading them! LOL
Quick EDIT: I think I am wrong in that brick assumption - the first 3 I looked at involved encryption and 2 downgrades to MM (which is a no-no). I will read further.
edit2 - nevermind - most are downgrading to MM. Wish folks would just ask before doing that. That is a no-no of most (all?) phones. -
Hi,
Please share your camera result using Alberto97's roms. I some ROM but i dont like camera result, i think stock ROM still better in camera.
Thank You
wakhidnusa said:
Hi,
Please share your camera result using Alberto97's roms. I some ROM but i dont like camera result, i think stock ROM still better in camera.
Thank You
Click to expand...
Click to collapse
YES! Will do. I have about 5 cameras that I want to try though I will stop at the first one that works. Phone should be here today.
wakhidnusa said:
Hi,
Please share your camera result using Alberto97's roms. I some ROM but i dont like camera result, i think stock ROM still better in camera.
Thank You
Click to expand...
Click to collapse
I have no problem with various cameras getting good image, but sometimes on still first pic doesn't save. ( tried camera MX and Professional camera hd. I'm sure lots work about the same.)
Forgot to flash Alberto's verity patch right after flashing TWRP. So I had to RSD lite 7.1.1 Nov 1 and start over - no big deal! OP corrected.
Hello Kris,
I would like to ask for a link where I can download a working RSD so I can unlocked my bootloader.
Thanks
jeprox said:
Hello Kris,
I would like to ask for a link where I can download a working RSD so I can unlocked my bootloader.
Thanks
Click to expand...
Click to collapse
link to 6.2.4 is in the first post of
https://forum.xda-developers.com/moto-z-play/how-to/guide-rsd-lite-mini-guide-t3740641#post75334194
Fingerprint option missing in "Security" settings after flashing custom ROMs
Hello! I'm trying to install custom ROMs on my OnePlus 8 Pro (IN2020) and have the problem with fingerprint sensor: when I'm using stock firmwares (A10/11, MSM/fastboot) or GSI (kernel doesn't matter), I have an option in "Security" with ability of using fingerprints. But when I'm flashing any custom ROM, I have an option disappeared. I've tried restoring my persist partition, tried kernels from various authors (even CleanSlate 1.2.7 with special fingerprint fix), tried not using Magisk and so on. Nothing helps. I guess there can be different types of fingerprint sensor hardware on our phones, so drivers required. Dev's help will be appreciated, also I'm ready to test and send any info needed. Thanks in advance!
Very common issue, run through the fix persist img position problem thread, at least ask in there.
Bare in mind that custom ROMs like GSI's do not have fingerprint functionality, it allows you to create data but not to use it.
Easy Solution,
MSM to Android 11.
dladz said:
Very common issue, run through the fix persist img position problem thread, at least ask in there.
Bare in mind that custom ROMs like GSI's do not have fingerprint functionality, it allows you to create data but not to use it.
Click to expand...
Click to collapse
I don't think you've read it quite right. I tried fixing persist partition, also GSI ROMs have the fingerprint option for me.
IronSingh said:
Easy Solution,
MSM to Android 11.
Click to expand...
Click to collapse
How can I flash custom ROMs after flashing A11 MSM??? Sounds impossible for me.
Welld1s said:
I don't think you've read it quite right. I tried fixing persist partition, also GSI ROMs have the fingerprint option for me.
Click to expand...
Click to collapse
I've read that the option is there but after enrollment it fails to function.
So you've been through the persist fix?? Have you asked in that said thread?! There's a tonne of people who have had this issue and have got it fixed.
I'm sure they'll know what to do with it
dladz said:
I've read that the option is there but after enrollment it fails to function.
So you've been through the persist fix?? Have you asked in that said thread?! There's a tonne of people who have had this issue and have got it fixed.
I'm sure they'll know what to do with it
Click to expand...
Click to collapse
There is a difference in our situations: their enrollment is failed, but I don't see an option at all. Like the driver or device is not found, so Android thinks I don't have a fingerprint scanner. Tried the persist fix, yes. I'm not a total noob in here, been ROM addict from Samsung S3 stuff I think the problem is we have another fingerprint scanner hardware with different driver needed on some instantnoodlep devices.
Welld1s said:
There is a difference in our situations: their enrollment is failed, but I don't see an option at all. Like the driver or device is not found, so Android thinks I don't have a fingerprint scanner. Tried the persist fix, yes. I'm not a total noob in here, been ROM addict from Samsung S3 stuff I think the problem is we have another fingerprint scanner hardware with different driver needed on some instantnoodlep devices.
Click to expand...
Click to collapse
I know mate, but that's the only thing I could suggest, the GSI and the OOS issues were always different.
Have you changed firmwares, like from regional to global?
I think it would at least be with talking to the person who came up with the persist fix as they obviously know a lot more about this specific issue.
I highly doubt that the hardware is broken.
Not suggesting you're a noob either, just suggesting you've missed something potentially, that could happen to anyone.
Personally I don't know how to fix it as I've never had they issue.
Good luck with it.
dladz said:
I know mate, but that's the only thing I could suggest, the GSI and the OOS issues were always different.
Have you changed firmwares, like from regional to global?
I think it would at least be with talking to the person who came up with the persist fix as they obviously know a lot more about this specific issue.
I highly doubt that the hardware is broken.
Not suggesting you're a noob either, just suggesting you've missed something potentially, that could happen to anyone.
Personally I don't know how to fix it as I've never had they issue.
Good luck with it.
Click to expand...
Click to collapse
I'm not telling you that hardware is broken, I think that hardware is different, because I've read something similar from people who has newer devices.
Welld1s said:
I'm not telling you that hardware is broken, I think that hardware is different, because I've read something similar from people who has newer devices.
Click to expand...
Click to collapse
Right ok, well good luck with that pal.
v.is.for.vladdy said:
Hello! I'm trying to install custom ROMs on my OnePlus 8 Pro (IN2020) and have the problem with fingerprint sensor: when I'm using stock firmwares (A10/11, MSM/fastboot) or GSI (kernel doesn't matter), I have an option in "Security" with ability of using fingerprints. But when I'm flashing any custom ROM, I have an option disappeared. I've tried restoring my persist partition, tried kernels from various authors (even CleanSlate 1.2.7 with special fingerprint fix), tried not using Magisk and so on. Nothing helps. I guess there can be different types of fingerprint sensor hardware on our phones, so drivers required. Dev's help will be appreciated, also I'm ready to test and send any info needed. Thanks in advance!
Click to expand...
Click to collapse
Bro on my op 8 pro my fp option is also missing if u got anything thats works for you pls let me know I'm using my device without fp and it's been 25 days plus... I'm not happy with face unlock..
Bdw i tried fix persist img and msm tool nothing working for me if u got anything brother let me know ... I cant RDA my device no customer service in my city.
Just curious...you're both on 11 right?
The persist fix I believe was originally intended for Android 10 (I know that's when it came out)
My point being, would it be worth downgrading to 10 then running the through the fix?
dladz said:
Just curious...you're both on 11 right?
The persist fix I believe was originally intended for Android 10 (I know that's when it came out)
My point being, would it be worth downgrading to 10 then running the through the fix?
Click to expand...
Click to collapse
Sir, I don't have fingerprint option only on CUSTOM ROMS, which are currently running Android 10 only. I have it perfectly working on STOCK ROMS (A10/A11) and GSI.
Welld1s said:
Sir, I don't have fingerprint option only on CUSTOM ROMS, which are currently running Android 10 only. I have it perfectly working on STOCK ROMS (A10/A11) and GSI.
Click to expand...
Click to collapse
GSI ROMs don't have the fingerprint working mate. .
Thats pretty well known I believe
And a custom ROM would be a complete ROM a GSI is simply a system image, you almost always have to expect issues.. The title of this thread is misleading for that very reason, should have been called "No fingerprint on GSI ROMs"
What happens if you use lineage or Carbon both built for the 1+8pro, my guess is that it'll work.
You could try to flash an actual custom ROM, then wipe system and install the GSI, if that doesn't work then it won't work.
Nothing to do with your hardware, driver, persist or anything else its just a GSI limitation.
Also stop with the patronising attitude, there's no call for it, it doesn't help you, me or anyone else.
dladz said:
GSI ROMs don't have the fingerprint working mate. .
Thats pretty well known I believe
And a custom ROM would be a complete ROM a GSI is simply a system image, you almost always have to expect issues.. The title of this thread is misleading for that very reason, should have been called "No fingerprint on GSI ROMs"
What happens if you use lineage or Carbon both built for the 1+8pro, my guess is that it'll work.
You could try to flash an actual custom ROM, then wipe system and install the GSI, if that doesn't work then it won't work.
Nothing to do with your hardware, driver, persist or anything else its just a GSI limitation.
Also stop with the patronising attitude, there's no call for it, it doesn't help you, me or anyone else.
Click to expand...
Click to collapse
I guess we have a misunderstanding here. What I did and the result - no fingerprint in security options:
1. Flashed stock A10 firmware via MSM, updated to latest A10 version with zip-archive locally
2. Unlocked the bootloader
3. Rebooted to the system once
4. Booted to fastbootd and flashed any custom ROM for both slots (means Lineage OS, Pixel Experience and Carbon ROM) with data/metadata wipes
5. Rebooted to installed system, passed initial setup
6. Set the PIN, got no fingerprint option in settings.
I can repeat: I have it working on stock A10/11 AND GSI, only Lineage, Pixel and Carbon custom ROMs on A10 are affected. Not making something up, not trolling or "patronising", just trying to provide all the useful info that you, for some reason, don't want or can't accept. :/
Edit: my mistake, as I actually didn't try to add any fingerprint on GSI, so can't say that it works for 100% here. I'm just saying, that the option is in place in settings, but not when using custom ROMs like LOS and so on. No offense.
Welld1s said:
I guess we have a misunderstanding here. What I did and the result - no fingerprint in security options:
1. Flashed stock A10 firmware via MSM, updated to latest A10 version with zip-archive locally
2. Unlocked the bootloader
3. Rebooted to the system once
4. Booted to fastbootd and flashed any custom ROM for both slots (means Lineage OS, Pixel Experience and Carbon ROM) with data/metadata wipes
5. Rebooted to installed system, passed initial setup
6. Set the PIN, got no fingerprint option in settings.
I can repeat: I have it working on stock A10/11 AND GSI, only Lineage, Pixel and Carbon custom ROMs on A10 are affected. Not making something up, not trolling or "patronising", just trying to provide all the useful info that you, for some reason, don't want or can't accept. :/
Edit: my mistake, as I actually didn't try to add any fingerprint on GSI, so can't say that it works for 100% here. I'm just saying, that the option is in place in settings, but not when using custom ROMs like LOS and so on. No offense.
Click to expand...
Click to collapse
Then I'm not sure pal.
GSI I would expect it, lineage I haven't installed it but haven't heard anything to suggest it doesn't work.
Carbon ROM I'm pretty sure had the option for me, was a little flakey by it worked..
None taken, sorry I'd barely slept.
PS: seeing as you're on Android 10 why not use twrp? And is born slots necessary? I don't think I did that.
That's the only significant difference I can see between your method and mine.
Also that I set up the phone with a fingerprint each time, not sure if it did or not.
PPS: "don't want or can't accept" yes that's sarcasm pal just saying.
You have a new device. See this thread: https://forum.xda-developers.com/oneplus-8-pro/help/kernel-devs-fingerprint-scanner-t4163005
And this custom kernel fix: https://forum.xda-developers.com/showthread.php?p=83613489
Basically wait for Android 11 custom ROMs to com out.
dladz said:
Then I'm not sure pal.
GSI I would expect it, lineage I haven't installed it but haven't heard anything to suggest it doesn't work.
Carbon ROM I'm pretty sure had the option for me, was a little flakey by it worked..
None taken, sorry I'd barely slept.
PS: seeing as you're on Android 10 why not use twrp? And is born slots necessary? I don't think I did that.
That's the only significant difference I can see between your method and mine.
Also that I set up the phone with a fingerprint each time, not sure if it did or not.
PPS: "don't want or can't accept" yes that's sarcasm pal just saying.
Click to expand...
Click to collapse
Tried with TWRP too, makes no difference for me. Both slots aren't necessary for sure, but that won't hurt too.
I think I tried literally anything except flashing LOS right on A11 OOS, which is a total nonsense. :^(
Welld1s said:
Tried with TWRP too, makes no difference for me. Both slots aren't necessary for sure, but that won't hurt too.
I think I tried literally anything except flashing LOS right on A11 OOS, which is a total nonsense. :^(
Click to expand...
Click to collapse
I didn't suggest flashing Lineage on 11, that's a bad idea wherever said that.
The chap above has a decent idea there, maybe it is hardware.
Give that a shot.
@DJ said:
You have a new device. See this thread: https://forum.xda-developers.com/oneplus-8-pro/help/kernel-devs-fingerprint-scanner-t4163005
And this custom kernel fix: https://forum.xda-developers.com/showthread.php?p=83613489
Basically wait for Android 11 custom ROMs to com out.
Click to expand...
Click to collapse
As I said in the beginning (love quoting myself):
"tried kernels from various authors (even CleanSlate 1.2.7 with special fingerprint fix)"
Doesn't help + gives a distorted image after booting the system on custom ROMs (disappears after locking and unlocking the device again). Looks like the only way is to waaaait. :'c