I lost my biometric sensor after leaving the test soak and go to a custom rom, how can I recover before leaving the final oreo stock?
eduh9 said:
I lost my biometric sensor after leaving the test soak and go to a custom rom, how can I recover before leaving the final oreo stock?
Click to expand...
Click to collapse
Hi, this happened to me, back to the stock rom (Android 7.0) of the device and do the whole procedure. And your sensor will work
Be careful to do not downgrade your bootloader though.
This tutorial helped me to recover biometrics in my phone (XT1676, reteu, 3/16, DualSIM).
I am not responsible for any damage! If you proceed to follow this, you're doing it at your own risk.
1. Make sure, your adb and fastboot is working.
I recommend using this one https://forum.xda-developers.com/showthread.php?t=2588979 . For me, it's fully working on Win8.1 x64. If you install it (press "Y" for all of 3 questions), but after connecting phone you see "Fastboot cedric S" with yellow exclamation mark in device manager, there's problem with driver: right click on it --> "Update driver software" --> "Browse my computer for driver software" --> "Let me pick from a list of device drivers on my computer" --> "Android devices" --> "Android Bootloader Interface" --> "Next" --> "OK" --> "Close"
(Open cmd and use "cd" command to get to directory, where's adb installed (in this case "cd C:\adb"). Then, press Enter and type "Fastboot devices". If fastboot is properly installed with corresponding drivers, you will see your device listed.)
2. Download this firmware https://drive.google.com/file/d/1hlNzlFhLCEj6xigfKrYcvnwH9jy3f5j3/view and extract it to the same directory as adb is installed.
3. Boot your phone into fastboot mode by pressing and holding power and vol- buttons for few seconds.
4. NOW, THE MOST IMPORTANT PART! Check your bootloader version.
4a. If your bootloader version is B8.25, use these commands to flash:
Code:
fastboot oem fb_mode_set
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
4b. If your bootloader is B8.24 and lower, use these commands:
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
5. Your phone should reboot and sucessfully boot into OS in few minutes with fingerprint working.
DON'T EVEN TRY TO TAKE OTA UPDATES.
6. (optional) However, if you want to update your phone, update it manually with correct files from this site https://forum.xda-developers.com/g5/how-to/cedric-ota-archive-t3795275
Moto g5, has a biometric sensor?
666km666 said:
Moto g5, has a biometric sensor?
Click to expand...
Click to collapse
Of course, it has (fingerprint sensor at the front, under the display).
johnnywilly16 said:
Hi, this happened to me, back to the stock rom (Android 7.0) of the device and do the whole procedure. And your sensor will work
Click to expand...
Click to collapse
Sorry I'm just confirming that I need to go to stock 7.0 first? Will the debloated stock 7.0 be good enough?
eduh9 said:
I lost my biometric sensor after leaving the test soak and go to a custom rom, how can I recover before leaving the final oreo stock?
Click to expand...
Click to collapse
For anyone who finds this there is a flastable Nougat zip for Cedric which fixes finger print scanner, it is in the same thread as the soak 8.1 zip. I hope this saves others trouble as it did me. Find direct answers in telegram:
@cedricNOOBchat
Related
Dear All,
After upgrading to Nougat 7.0 April patch with the following commands:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot.exe flash system system.img_sparsechunk.1
fastboot.exe flash system system.img_sparsechunk.2
fastboot.exe flash system system.img_sparsechunk.3
fastboot.exe flash system system.img_sparsechunk.4
fastboot.exe flash system system.img_sparsechunk.5
fastboot.exe flash system system.img_sparsechunk.6
fastboot.exe flash system system.img_sparsechunk.7
fastboot.exe flash system system.img_sparsechunk.8
fastboot.exe flash system system.img_sparsechunk.9
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
My phone works normally but if i shut down and power on ,the phone boots on fastboot and I have to press on start to boot on OS . Additionally the id status has changed to bad key (previous on n/a status).
I get the update notification to 7.1.1 but because it cannot boot to recovery mode (which is part of the update procedure ) directly and it boots on fastboot mode, the update fails.
Any suggestion?
Looks like you set fastboot mode when you flashed, and just forgot to clear it.
Try rebooting to bootloader
Connect your device to your computer
In the ADB terminal, type 'fastboot oem fb_mode_clear' without the quotes and execute the command.
Reboot and see if that clears the block.
echo92 said:
Looks like you set fastboot mode when you flashed, and just forgot to clear it.
Try rebooting to bootloader
Connect your device to your computer
In the ADB terminal, type 'fastboot oem fb_mode_clear' without the quotes and execute the command.
Reboot and see if that clears the block.
Click to expand...
Click to collapse
you re MY MAN . thx a lot!
A friend unlocked its bootloader and tried to root it with no success.
The phone works but only boots through fastboot, because when I press the power button it enters fastboot mode instead of booting.
I don't know what happened, as I was not the one who tried to root, so I just wanted to know how to revert back to stock and relock the bootloader, since the phone works normally.
freeZbies said:
A friend unlocked its bootloader and tried to root it with no success.
The phone works but only boots through fastboot, because when I press the power button it enters fastboot mode instead of booting.
I don't know what happened, as I was not the one who tried to root, so I just wanted to know how to revert back to stock and relock the bootloader, since the phone works normally.
Click to expand...
Click to collapse
If they flashed twrp and your phone can only be started normally through the bootloader see
https://forum.xda-developers.com/g5/how-to/fix-phone-reboots-recovery-mode-started-t3705325
If you want to root the phone stock can only be rooted with a system root
Most roots now use a systemless root which is not compatible with the stock kernel
You either need a custom rom to use the latest magisk root or if you want to stick with stock use an old version of magisk (can't remember which really old version works) or use supersu but flash the config zip first and set to system as default will be systemless
With regards to flashing stock download firmware and run these fastboot commands assuming you have fastboot set up on your pc
fastboot oem fb_mode_set
fastboot flash partition gpt.bin (do not flash unless you want to repartition the phone)
fastboot flash bootloader bootloader.img (do not flash unless you really need to replace the bootloader)
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize (ignore any error)
fastboot erase clogo (ignore any error)
fastboot oem fb_mode_clear
fastboot reboot
To lock the bootloader do the above and then go back to the bootloader mode & enter these fastboot commands
fastboot oem lock
fastboot oem lock (yes type it again)
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash boot boot.img
fastboot oem lock
Then once restarted refresh all the firmware again with the commands from earlier
I have seen though that some boot.img are not officially signed so it may not lock
TheFixItMan said:
If they flashed twrp and your phone can only be started normally through the bootloader see
https://forum.xda-developers.com/g5/how-to/fix-phone-reboots-recovery-mode-started-t3705325
If you want to root the phone stock can only be rooted with a system root
Most roots now use a systemless root which is not compatible with the stock kernel
You either need a custom rom to use the latest magisk root or if you want to stick with stock use an old version of magisk (can't remember which really old version works) or use supersu but flash the config zip first and set to system as default will be systemless
With regards to flashing stock download firmware and run these fastboot commands assuming you have fastboot set up on your pc
fastboot oem fb_mode_set
fastboot flash partition gpt.bin (do not flash unless you want to repartition the phone)
fastboot flash bootloader bootloader.img (do not flash unless you really need to replace the bootloader)
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize (ignore any error)
fastboot erase clogo (ignore any error)
fastboot oem fb_mode_clear
fastboot reboot
To lock the bootloader do the above and then go back to the bootloader mode & enter these fastboot commands
fastboot oem lock
fastboot oem lock (yes type it again)
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash boot boot.img
fastboot oem lock
Then once restarted refresh all the firmware again with the commands from the first post
I have seen though that some boot.img are not officially signed so it may not lock
Click to expand...
Click to collapse
Yes, thank you.
I was checking the relocking guides here in xda and seems signed boot images are the problem. Anyways, I'll check to see if it works.
freeZbies said:
Yes, thank you.
I was checking the relocking guides here in xda and seems signed boot images are the problem. Anyways, I'll check to see if it works.
Click to expand...
Click to collapse
Also just noticed you are talking about the Moto G5s - this is the Moto G5 Cedric forum
The Moto G5s forum is located
https://forum.xda-developers.com/moto-g5s
TheFixItMan said:
Also just noticed you are talking about the Moto G5s - this is the Moto G5 Cedric forum
The Moto G5s forum is located
https://forum.xda-developers.com/moto-g5s
Click to expand...
Click to collapse
Oh thanks, I'm gonna check it there, because it's indeed a Moto G5S.
Only thing I'd like to say is that on the XDA Labs app the only forum shown when I search for Moto G5S is the Moto G5 forum, no variants are presented, whom should I report this to, so that it can be fixed?
freeZbies said:
Oh thanks, I'm gonna check it there, because it's indeed a Moto G5S.
Only thing I'd like to say is that on the XDA Labs app the only forum shown when I search for Moto G5S is the Moto G5 forum, no variants are presented, whom should I report this to, so that it can be fixed?
Click to expand...
Click to collapse
No idea - don't use the app
The email on the Google play listing says
[email protected]
The thread for the app is
https://forum.xda-developers.com/android/apps-games/labs-t3241866
WARNING: DO NOT FLASH THE GPT.BIN OR THE BOOTLOADER.IMG/MOTOBOOT.IMG ON A NEWER FIRMWARE WHEN DOWNGRADING, BECAUSE IT CAN HARD BRICK YOUR DEVICE E.G. DO NOT FLASH THE GPT.BIN OR THE BOOTLOADER.IMG/MOTOBOOT.IMG MADE FOR 7.0 ON 8.1.0 EVEN IF THE FILES IN THE FOLDER BUT ITS FINE IF YOU FLASH THE SAME FILES MADE FOR ANDROID 8.1.0 AVOID FLASHING THESE FILES AT ALL TIMES
I AM NOT RESPONSIBLE FOR ANY DAMAGE CAUSED TO YOUR DEVICE, DO THIS AT YOUR OWN RISK
so a little backstory,
i unlocked my bootloader because i wanted to downgrade back to android 7.0, and then my imei broke on me, so i attempted to upgrade back to android 8.1.0 but then everytime i rebooted my phone i see;
"your device is unlocked and cant be trusted
ID: bad key
your device will reboot in 5 seconds"
then would just loop into the bootloader
and when flashing the logo back it will just say "bad key" when editing logo.bin (changing the logo_unlocked to logo_boot)
with this guide i will tell you how to revert your device back to OOB state (OOB means out of box for all those idiots out there )
THIS WAS TESTED ON MY XT1675 IT WILL BE DIFFERENT FOR EACH DEVICE
1) grab your stock firmware, for me its "XT1675_CEDRIC_RETGB_SS_8.1.0_OPP28.85-19-4-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml"
2) install minimal ADB and fastboot
3) then once you installed the adb and fastboot drivers we are really just focusing on the fastboot.exe, i will be linking the platform-tools at the bottom of this post
4) extract the firmware to a place and make sure there are no spaces (e.g. C:/Users/Example/Desktop/moto g5 downgrade otherwise cmd will assume its another path to another folder)
5) the most important file is oem.img because this is the signed file by motorola that we will need to relock the bootloader but it should come in the firmware folder, if not PM me and will try my best to find the matching oem.img
6) once you get all your files type these commands to reload the firmware onto the device
fastboot flash gpt gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
what you will find now is it will at least boot into the setup screen
we are not done yet!
7) now if you reboot into the bootloader screen the options will be seriously messed up (they will overlap if you press up and down on the volume keys, i think this tells motorola that you tampered with your device)
8) now still on the bootloader screen connect up your device with cmd still open, then type these commands
fastboot oem lock
fastboot oem lock (you have to type it twice)
fastboot flash oem oem.img (you need this to relock the bootloader)
fastboot flash gpt gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash boot boot.img
fastboot oem lock
now it will say (lock complete! flash signed images after reboot if needed)
type in
fastboot reboot
now when you reboot your device you will get a black screen then it will show the motorola logo, to fix this go into the bootloader mode and reflash your original bootlogo
you got your device up and running like it did OOB!
LINKS:
Minimal adb and fastboot: https://forum.xda-developers.com/showthread.php?t=2317790
platform tools: https://developer.android.com/studio/releases/platform-tools
if your getting "image signed with key bad key when flashing the boot.img and the recovery.img, i found this really helpful tutorial, just do not flash the files on the G5, this is made for the G5 plus but the bootloader commands works for the G5 as well as the G5 plus
Link: https://forum.xda-developers.com/g5-plus/how-to/solution-to-flash-stock-romfactory-t3691396
also if you get "still requires signed system.img and/or boot.img flash all the system sparsechunk files
I can't re-lock bootloader, getting "(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer" when I run "fastboot oem lock" second time. Please, help!
gkornaks said:
I can't re-lock bootloader, getting "(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer" when I run "fastboot oem lock" second time. Please, help!
Click to expand...
Click to collapse
You need to enable oem unlock in developer settings
mattwhite7102 said:
You need to enable oem unlock in developer settings
Click to expand...
Click to collapse
I am having the same error of "Allow OEM unlock" in the android setting, and the option in the developer setting of android is grayed out. I can't switch it.
Sorry for my english, translated by google
Hi. Can someone help or at least tell you in which direction to look. Moto (lenovo) G5 XT1675 cedric RETGB device. CEDRIC_OPP28.85_19_4_2_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml (the latest firm on Android 8.1.0) and over it via tvrp lightweight stock on 7.0 android was flashed. In search of a problem, I went through a lot: I replaced the board with yusb, flashed the Rescue and Smart Assistant program from Lenovo (with the firmware that the program told me), unlocked the bootloader + tvrp and root. I tried a lot of custom, but I didn’t solve the problem. The essence is the phone in the included state. does not see usb (in any way, neither charging nor connecting to a computer) but it is worth rebooting the device with the cable connected and everything works. But if you disconnect the phone cable. It no longer sees it until the next reboot. If the menu is loaded into Factory mode through the fastboot without connecting. cable, then when the bodies are connected, it sees it but only the first time. comp. the bodies are normally charged, stitched, etc., the TVRP also does not see the cable (also resolves with a reboot) I personally think about the bootloader, but having the latest version, there is nothing to update and it is risky to roll back to a version below (you can get a brick that cannot be cured with a simple firmware)
I say the same to most people with these types of issue
If flashing stock firmware via fastboot doesn't solve the problem then it's a hardware issue & not software
Firmware can be downloaded from https://mirrors.lolinet.com/firmware/moto/cedric/official/
If you don't know what to choose then choose the latest retail image
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Note backup any personal files from internal storage to your pc first
TheFixItMan said:
I say the same to most people with these types of issue
If flashing stock firmware via fastboot doesn't solve the problem then it's a hardware issue & not software
Firmware can be downloaded from https://mirrors.lolinet.com/firmware/moto/cedric/official/
If you don't know what to choose then choose the latest retail image
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Note backup any personal files from internal storage to your pc first
Click to expand...
Click to collapse
Thank you. I know about all this. I made the backup first of all after unlocking the bootloader and the TVRP firmware. The first time I stitched with Rescue and Smart Assistant https://www.motorola.com/us/rescue-and-smart-assistant/p. I think that this program knows exactly what firmware I need. But it did not help In the off state, the device responds normally to the cable (it charges, connects to the PC where all the drivers are installed, I flashed it many times and tried various factory firmware) but if you connect the cable after the logo image (logo.bin) , until you reboot the device with the cable connected and if you turn it off. That is, when the android system is loaded, the device stubbornly does not want to see the connection. I think that the problem is not in the hardware type because with the firmware I would get a bunch of errors or just could not connect the device but everything works
Smartphone Killer said:
Thank you. I know about all this. I made the backup first of all after unlocking the bootloader and the TVRP firmware. The first time I stitched with Rescue and Smart Assistant https://www.motorola.com/us/rescue-and-smart-assistant/p. I think that this program knows exactly what firmware I need. But it did not help In the off state, the device responds normally to the cable (it charges, connects to the PC where all the drivers are installed, I flashed it many times and tried various factory firmware) but if you connect the cable after the logo image (logo.bin) , until you reboot the device with the cable connected and if you turn it off. That is, when the android system is loaded, the device stubbornly does not want to see the connection. I think that the problem is not in the hardware type because with the firmware I would get a bunch of errors or just could not connect the device but everything works
Click to expand...
Click to collapse
Like I said - if you flashed stock firmware exactly like I posted above with the latest retail firmware from the site in the link and you still have issues it's a hardware problem - either the board or the USB cable you are using
Recently i install pie 9.0 on z2 play, to try to fix the fingerprint scanner and gestures but still doesnt work, i was reading that is a problem from oreo, so i want to Downgrade to oreo to nougat, it's posible?
Anything below Pie is vulnerable to the X-helper rootkit... we were just talking about it in another thread. It's a real nasty little bugger.
But its posible? I just want to get all the features back, even, i dont know what is that thing, if they have some to hack me i dont have to much to lose anyways, just want to downgrate to fix the fingerprint bug from oreo
Don't know. Hopefully someone with this device can help you.
iMaxwell said:
Recently i install pie 9.0 on z2 play, to try to fix the fingerprint scanner and gestures but still doesnt work, i was reading that is a problem from oreo, so i want to Downgrade to oreo to nougat, it's posible?
Click to expand...
Click to collapse
How exactly did you install it? FP not working is usually just that the fw is needed, but that's only if you are running a custom rom. What specific issue were you facing before and what OS were you running
marcost22 said:
How exactly did you install it? FP not working is usually just that the fw is needed, but that's only if you are running a custom rom. What specific issue were you facing before and what OS were you running
Click to expand...
Click to collapse
Install via "ota", just donwload 9.0 official motorola firmware, put it into internal storage, then go to settings - search for updates, then install.
The problems are, fingerprint doesnt work, but this is a problem from oreo. And i want to go back to nougat
iMaxwell said:
Install via "ota", just donwload 9.0 official motorola firmware, put it into internal storage, then go to settings - search for updates, then install.
The problems are, fingerprint doesnt work, but this is a problem from oreo. And i want to go back to nougat
Click to expand...
Click to collapse
that's probably the worst available way to do it. If your phone didn't originally receive it via OTA, then you are forcing it the wrong way.
If you want to go back to nougat all you need to do is download the official N firmware, then flash everything but bootloader and gpt
What is gpt? I need to unlock bootloader and flash whit wrp? I heard about losing imei or something like that
I follow the steps on this video
iMaxwell said:
I follow the steps on this video
Click to expand...
Click to collapse
Yeah that is just terrible
iMaxwell said:
What is gpt? I need to unlock bootloader and flash whit wrp? I heard about losing imei or something like that
Click to expand...
Click to collapse
Download the official N firmware from https://mirrors-obs-2.lolinet.com/firmware/motorola/2017/albus/official/RETAIL/
Then, extract it and reboot your phone into fastboot (shut it down, hold down volume down and turn it on, you should arrive at fastboot that way)
Install minimal adb and fastboot if you dont have them installed ( https://forum.xda-developers.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790/)
After that, you open a terminal where you extracted the firmware, run fastboot devices to check that A) fastboot is installed and that B) your phone is recognized and then you run
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
This WILL format your phone, but it should leave you with a booting N system(maybe, downgrading not always work and going P->N is really unusual)
I'm gonna be honest i do think all of your issues are caused by forcing an OTA where the phone wasn't supposed to have one, but it's your choice
marcost22 said:
Yeah that is just terrible
Download the official N firmware from https://mirrors-obs-2.lolinet.com/firmware/motorola/2017/albus/official/RETAIL/
Then, extract it and reboot your phone into fastboot (shut it down, hold down volume down and turn it on, you should arrive at fastboot that way)
Install minimal adb and fastboot if you dont have them installed ( https://forum.xda-developers.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790/)
After that, you open a terminal where you extracted the firmware, run fastboot devices to check that A) fastboot is installed and that B) your phone is recognized and then you run
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
This WILL format your phone, but it should leave you with a booting N system(maybe, downgrading not always work and going P->N is really unusual)
I'm gonna be honest i do think all of your issues are caused by forcing an OTA where the phone wasn't supposed to have one, but it's your choice
Click to expand...
Click to collapse
The issues begin on official oreo, i upgrade nougat to oreo then, fingerprint option dissapear, then i upgrade to pie from oficial firmware but issues still remain
It really works? I didnt find any video or post about downgrade like that
Yes it does work, but it's not recommended, that's why you don't find much info
iMaxwell said:
It really works? I didnt find any video or post about downgrade like that
Click to expand...
Click to collapse