Hello,
I'm currently using Z00AD -- ZE551ML -- 4GB/2.3GHz bought in Brazil.
In the system update option shows: ASUS_Z00A-2.20.40.198_20160930... as my current build. (Lollipop)
I'd like to know if the steps presented in this video /watch?v=MEF9S_VNtO0&t=377s are safe to follow. I'm not so sure about those LP/MM Blops I've been reading about, although I have some background in flashing another phone.
Is there anything I should know?
In the video the guy do TWRP backup, so, assuming I'm coming from stock, will it really work? (i.e.: I'll be able to restore to the stock version if necessary?)
Thanks in advance.
There are two threads about unlocking the BL and flashing twrp:
1: https://forum.xda-developers.com/zenfone2/general/tool-ze551mlmodder-t3458145
2: https://forum.xda-developers.com/zenfone2/general/root-install-xposed-marshmallow-6-0-1-t3456443
Both of these methods caused me to brick my ze551ml (2gb, 16 GB) running stock MM so be prepared to go through the process of unbricking the phone if necessary. My phone bricked, not because of those unlocking methods, but from something I must have done wrong.
If the custom ROM uses MM blobs, you'll have to be running an MM bootloader on the phone before installing the ROM.
Hello all the people out there.
Im new in the forum and english is not my mother language so, please be kind.
Hardware:
Moto G5 cedric (XT1060)
Situation:
Installed twrp-3.2.1-0-cedric.img without problems
Installed lineage-15.1-20180415-UNOFFICIAL-cedric.zip without problems
Installed open_gapps-arm64-8.1-aroma-20181116.zip without problems
Problem:
When the phone inits, the fingerprint sensor does nothing at all.
When i go to Security > Screen lock the fingerprint option doesnt exists at all. Exploring the coms (Apps > All Apps) i dont see the fingerprint service installed.
I have installed the "Ampare Fingerprint test" app and when run only says "Native Fingerprint API not found!".
Thing done:
Flash all again (TWRP + Lineage 15.1 + gapps) and the situation is the same.
Anyone have an idea and can guide me?
sk8avp said:
Hello all the people out there.
Im new in the forum and english is not my mother language so, please be kind.
Hardware:
Moto G5 cedric (XT1060)
Situation:
Installed twrp-3.2.1-0-cedric.img without problems
Installed lineage-15.1-20180415-UNOFFICIAL-cedric.zip without problems
Installed open_gapps-arm64-8.1-aroma-20181116.zip without problems
Problem:
When the phone inits, the fingerprint sensor does nothing at all.
When i go to Security > Screen lock the fingerprint option doesnt exists at all. Exploring the coms (Apps > All Apps) i dont see the fingerprint service installed.
I have installed the "Ampare Fingerprint test" app and when run only says "Native Fingerprint API not found!".
Thing done:
Flash all again (TWRP + Lineage 15.1 + gapps) and the situation is the same.
Anyone have an idea and can guide me?
Click to expand...
Click to collapse
Did you flash stock 8.1 before?
Andrej_SK said:
Did you flash stock 8.1 before?
Click to expand...
Click to collapse
Hi Andrej_SK, thanks for your reply.
This phone was never flashed.
I had the stock version and it was updated with Android Oreo 8.1, which was updated a few weeks ago.
sk8avp said:
Hi Andrej_SK, thanks for your reply.
This phone was never flashed.
I had the stock version and it was updated with Android Oreo 8.1, which was updated a few weeks ago.
Click to expand...
Click to collapse
If you installed stock Oreo 8.1 using any method (OTA, Fastboot...), you have to downgrade to stock Nougat first (using fastboot image) to make fingerprint work with CustomROMs. However, you need unlocked bootloader to downgrade. Don't flash both gpt and bootloader (if flashed any of these, you will get hardbrick because gpt/bootloader downgrade is not allowed). Also, don't run erase modem commands, they will wipe your IMEI in this case. As soon as you downgrade to stock Nougat, check the fingerprint availibility in Settings. If you can see options related to it, you're good to go - you can install any CustomROM as you normally would and your fingerprint will work.
Andrej_SK said:
If you installed stock Oreo 8.1 using any method (OTA, Fastboot...), you have to downgrade to stock Nougat first (using fastboot image) to make fingerprint work with CustomROMs. However, you need unlocked bootloader to downgrade. Don't flash both gpt and bootloader (if flashed any of these, you will get hardbrick because gpt/bootloader downgrade is not allowed). Also, don't run erase modem commands, they will wipe your IMEI in this case. As soon as you downgrade to stock Nougat, check the fingerprint availibility in Settings. If you can see options related to it, you're good to go - you can install any CustomROM as you normally would and your fingerprint will work.
Click to expand...
Click to collapse
Hi Andrej_SK, really thanks for your help.
Sorry but I'm pretty new flashing android 6+.
Lets see if i have done the correct step.
Flashed 7.x Nougat following this post: https://forum.xda-developers.com/g5/development/official-stock-moto-g5-cedric-firmware-t3733897
IMEI is OK, fingerprint working perfectly.
This has erased TWRP, so, now i can install TWRP and then install any custom rom?
sk8avp said:
Hi Andrej_SK, really thanks for your help.
Sorry but I'm pretty new flashing android 6+.
Lets see if i have done the correct step.
Flashed 7.x Nougat following this post: https://forum.xda-developers.com/g5/development/official-stock-moto-g5-cedric-firmware-t3733897
IMEI is OK, fingerprint working perfectly.
This has erased TWRP, so, now i can install TWRP and then install any custom rom?
Click to expand...
Click to collapse
Yes. Keep in mind that if you want to install any Oreo CustomROM, you need to do it using 64bit TWRP. If you decide to install Gapps alongside with any Oreo CustomROM too, use this tutorial https://forum.xda-developers.com/g5/how-to/how-to-repair-bootloop-oreo-roms-t3791189 to avoid bootloop.
Andrej_SK said:
Yes. Keep in mind that if you want to install any Oreo CustomROM, you need to do it using 64bit TWRP. If you decide to install Gapps alongside with any Oreo CustomROM too, use this tutorial https://forum.xda-developers.com/g5/how-to/how-to-repair-bootloop-oreo-roms-t3791189 to avoid bootloop.
Click to expand...
Click to collapse
Andrej_SK I have no words to thank you for your help.
I decided to continue using the stock rom, at least until Lineage OS is in a more stable state.
Some functions work better and I really need them.
Again thank you very much!
Fingerprint not working
Andrej_SK said:
If you installed stock Oreo 8.1 using any method (OTA, Fastboot...), you have to downgrade to stock Nougat first (using fastboot image) to make fingerprint work with CustomROMs. However, you need unlocked bootloader to downgrade. Don't flash both gpt and bootloader (if flashed any of these, you will get hardbrick because gpt/bootloader downgrade is not allowed). Also, don't run erase modem commands, they will wipe your IMEI in this case. As soon as you downgrade to stock Nougat, check the fingerprint availibility in Settings. If you can see options related to it, you're good to go - you can install any CustomROM as you normally would and your fingerprint will work.
Click to expand...
Click to collapse
Hello,
I'm facing the same problem, I came Stock rom Oreo 8.1 and then fingerprint is not working on any custom rom I've tested.
Detail: Project Treble does not even start the boot for me.
I will perform the procedure that you mentioned and leave the feedback here if the problem was solved since I saw in other forums for this device that many are with the same problem.
Edit
I downgraded to the Nougat stock rom and installation rom Pixel Experience 8.1, fingerprint is working for me now =D
Thanks Andrej_SK for the great help
Hey there, can't get my fingerprint to work on LOS 17.1, it's like it's there, but it doesn't react to anything. When I go to the fingerprint settings, it ask me to touch it in order to setup the thing, but when I place my finger on it, it does nothing. Did anyone ever heard of this issue or any fix for it? Thanks in advance.
jaroulz said:
Hey there, can't get my fingerprint to work on LOS 17.1, it's like it's there, but it doesn't react to anything. When I go to the fingerprint settings, it ask me to touch it in order to setup the thing, but when I place my finger on it, it does nothing. Did anyone ever heard of this issue or any fix for it? Thanks in advance.
Click to expand...
Click to collapse
Did you flash stock Oreo prior to flashing LOS 17.1?
rahimali said:
Did you flash stock Oreo prior to flashing LOS 17.1?
Click to expand...
Click to collapse
Nope coz I use a Galaxy S7 so Oreo is not compatible with it, isn't it?
jaroulz said:
Nope coz I use a Galaxy S7 so Oreo is not compatible with it, isn't it?
Click to expand...
Click to collapse
You are posting in the Moto G5 forum
If you are using a galaxy s7 I suggest that you go and post your question in the correct rom section for your phone as no one here will be able to help you
Goto the following thread for Los 17 on a galaxy s7 & make sure you are using that build
https://forum.xda-developers.com/ga...ta-lineageos-17-0-galaxy-s7-build-1-t3980101/
please delete this post, can't find the option to delete...
Hi guys,
I have a problem I need some advice for. A year ago, I purchased my Amami for the purpose of GPS-navigation on my bicycle. It always worked fine and I was able to charge it with my dynohub without any issues. The charging is giving me a headache now though, and all troubleshooting points at the phone being the problem.
Now, a couple months ago I decided to ditch 4.4 and go for a custom ROM (I've tried Oreo and Pie) which worked fine, but the phone doesn't charge as well as it used to on my bike. I'd like to go back to stock to see if that's what is causing the issue and used the Xperia Flashtool to revert to a stock image, but the ones that used to work on the phone now give me bootloops after I've flashed TWRP and ResurrectionRemix and Lineage OS.
Is there anything I need to know before I flash a stock firmware with the tool? Any input would be appreciated.
Sounds like to have not updated to Lolipop and therefore you do not have real recovery. Is your bootloader unlocked? Then you can try EMMA to update to Lollipop.
jho55 said:
Sounds like to have not updated to Lolipop and therefore you do not have real recovery. Is your bootloader unlocked? Then you can try EMMA to update to Lollipop.
Click to expand...
Click to collapse
My bootloader is unlocked, I have TWRP installed and am currently running Lineage OS (Android 8). It doesn't matter if I flash Sony's original Kitkat or Lollipop; both will have bootloops. No offense, but I'm not sure you understood my original post: I'd like to go back to an old stock ROM, because 4.4 is the one that I'm sure have me no trouble with charging on my bike.
Proper BL relock:
https://forum.xda-developers.com/xperia-z/general/tutorial-relock-xperia-z-bootloader-t2191907https://forum.xda-developers.com/xperia-z/general/tutorial-relock-xperia-z-bootloader-t2191907
If you use twrp in fotakernel partition maybe necassary to write back original fotakernel.sin (inside stock.ftf) before relock with flashtool. Remember! After relock with flastool the new BL unlock key here: DEVICESERIAL \ unlock.txt
I'm running a completely stock OP3T with stock recovery and locked bootloader and latest OOS 9.0.6 installed.
Lately the phone has been unbearable to me and keeps hanging a lot with random crashes so im thinking about downgrading to OOS 4.1.7 as it is more stable. (I prefer OOS over custom roms to maintain stability and keep all the phone features intact).
I've downloaded OOS 4.1.7 from [oneplusupdates dot com] (cant post links cause im still new)
My question is : can I use the built in software update to locally select this file and preform the downgrade directly from pie to nougat?
I read somewhere that this could brick the device so i wanted to make sure.
philipemad said:
I'm running a completely stock OP3T with stock recovery and locked bootloader and latest OOS 9.0.6 installed.
Lately the phone has been unbearable to me and keeps hanging a lot with random crashes so im thinking about downgrading to OOS 4.1.7 as it is more stable. (I prefer OOS over custom roms to maintain stability and keep all the phone features intact).
I've downloaded OOS 4.1.7 from [oneplusupdates dot com] (cant post links cause im still new)
My question is : can I use the built in software update to locally select this file and preform the downgrade directly from pie to nougat?
I read somewhere that this could brick the device so i wanted to make sure.
Click to expand...
Click to collapse
Yes, that would surely brick the device. There are other steps involved before and while downgrading. Search on XDA for the steps.
The simplest solution to your problem is to download the current (9.06) OOS ROM and clean install/sideloading it. Your problem is most likely because of OTAs and not because of 9.06
The phone has replaced your bootloader to the point old roms are no longer compatible. Finding the correct zips and flashing order to downgrade the bootloader is a route i would not advise either. The easiest way to downgrade is find the msmdownloadtool unbrick thread of your specific model and download the version you desire or lower. Use this tool to flash the included files in upgrade mode and you will be on a stock, locked bootloader with the version you chose to download. Flashing always carries a risk, but i had no issues downgrading this way while i did run into issues flashing old zips. I switch between 5.0.8 based roms and the latest roms and its never let me down.
Hello, All
first, thank you for all the great work!!
As for my question. i just rooted my galaxy note 10+ sm-n975f with magisk. everything is fine.
I was wondering if it is possible to flash an older rom (only few months older and 1 that includes mirrorlink) allso with magisk.
I tried it the same way and patchted the rom with magisk, but ODIN is Stuck on DTB.
thank you in advance
greetings,
Tom
Bump!
You can only flash Roms with the same or higher bootloader version, that is what you need to check before attempting to flash what you intend to
Thanks for the reply.
I know the issue with the bootloader. Did not expect that a firmware from a few months before could have a different bootloader.
Both are android 10.
Greetz... Tom
5th number from the right in build number...
If it's the same you should be able to just flash it, however since you rooted your phone this could cause other issues...