Hi, I used Carbon ROM on XT1670, when I wanted to change ROM I ran:
Code:
fastboot -w
And i got this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I also tried to remove them:
In TWRP I tried to do something but all I get is something similar to this:
Am I missing something? Thanks for your help.
I've been reading the question and answer forum, apparently it's a problem with the encryption.
I don't have the Moto G5 right now, I can try it in a couple of hours, what other solution could I have anyway?
In twrp go to wipe
Then press the option on the right to format data
Reboot to recovery
Note this is different from wipe data from the advanced wipe menu.
The fastboot command would be
fastboot erase userdata
TheFixItMan said:
In twrp go to wipe
Then press the option on the right to format data
Reboot to recovery
Note this is different from wipe data from the advanced wipe menu.
The fastboot command would be
fastboot erase userdata
Click to expand...
Click to collapse
Hello, good (and bad) news
I did and now I have MTP for TWRP.
But still CMD says "Bootloader is logical @@@ not found"
"@@@" is depending on what you are trying to flash, be it system or recovery.
I was also able to change the filesystem I did it for DATA / CACHE / SYSTEM I went from FAT and then to EXT4 again.
Insert a ROM and it flashed without problems but it starts again in fastboot, the same if I do it with ADB Sideload.
I also tried flashing Stock ROM, everything seems to be written without problem but with the first line of "Bootloader logical ... not found" and again start in fastboot.
It makes me believe that something is still encrypted.
I mean this.
I also tried
Code:
fastboot format:ext4 userdata
But I have this:
Bootloader is logical not found - this is normal output
Why are you trying to change formats? You are going to have issues especially with encryption. Use twrp to format not fastboot if you are messing with formatting but make sure you know what you are doing!
TheFixItMan said:
Bootloader is logical not found - this is normal output
Why are you trying to change formats? You are going to have issues especially with encryption. Use twrp to format not fastboot if you are messing with formatting but make sure you know what you are doing!
Click to expand...
Click to collapse
I flash a rom (no apparent problem, even Stock ROM) but it only boots to fastboot or the robot with an open belly.
What exactly should I do, I will follow step by step, I really need to get it back. Thank you very much for your help.
Hello again, I saw you in another post that apparently has the same problem as me, it is this:
Decryption unsuccessfull
Hi guys, I have a problem with my motorola moto g5. It turns out that I upgraded to android oreo and at the time of associating the fingerprint I asked for a pin for security which I put. En el twrp me pide el pin, el cual ingresa y ya podia...
forum.xda-developers.com
I have the same bugs, do you think I should run the command to decrypt?
Dislekzi4 said:
Ok, I'll get to the point.
I flash a rom (no apparent problem, even Stock ROM) but it only boots to fastboot or the robot with an open belly.
What exactly should I do, I will follow step by step, I really need to get it back. Thank you very much for your help.
Click to expand...
Click to collapse
In twrp format data
That is by selecting wipe
Then the option on the right to format data
Reboot to recovery
Everything should now be mountable
Make sure you are flashing stock rom correctly
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
Making sure you are flashing the same or newer firmware version than already on your phone
If your phone keeps booting to recovery (android with an open stomach or twrp) then do this
Boot into twrp then connect phone to PC and in cmd/terminal type
Code:
adb shell dd if=/dev/zero of=/dev/block/platform/soc/7824900.sdhci/by-name/misc
Reboot and your device will boot normally (assuming you have a working rom)
Hi, it work!
Thank you very much for your time and help, I am very grateful, for a moment I thought it was really a hardware problem.
I get device unauthorized. Please check the confirmation dialog on your device. and it won't let me do anything
Rod_Ems said:
I get device unauthorized. Please check the confirmation dialog on your device. and it won't let me do anything
Click to expand...
Click to collapse
Enable adb debugging on your device in dev options
Make sure you are using the latest platform tools
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Unzip
Navigate your cmd window to to the platform tools directory
In cmd type
adb devices
Look on your phone and a window will pop up asking you to confirm authorisation - tick the box to allow always if you want to
Then type
adb devices
And your device is authorised
TheFixItMan said:
In twrp format data
That is by selecting wipe
Then the option on the right to format data
Reboot to recovery
Everything should now be mountable
Make sure you are flashing stock rom correctly
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
Making sure you are flashing the same or newer firmware version than already on your phone
If your phone keeps booting to recovery (android with an open stomach or twrp) then do this
Boot into twrp then connect phone to PC and in cmd/terminal type
Code:
adb shell dd if=/dev/zero of=/dev/block/platform/soc/7824900.sdhci/by-name/misc
Reboot and your device will boot normally (assuming you have a working rom)
Click to expand...
Click to collapse
mine show the following error message: device '(null)' not found
danniel_sx said:
mine show the following error message: device '(null)' not found
Click to expand...
Click to collapse
Either
Your phone is not connected to pc
Faulty cable
You haven't installed Motorola USB drivers
You are using the wrong commands
If in fastboot mode type
fastboot devices
If in recovery mode type
adb devices
Your device should be listed if correctly connected
I found a solution, i'm argentinian so sorry if my english is bad
the fastboot menu of the combination power + volume down have no permissions to all modifications
You have to acces to the recovery fastboot menu, to do this, move to "recovery mode" enter here with power
Now if in the screen appears "No command" you have to press power + volume down for 3 sec and press vol up without press the another 2, then release the 3 buttons
Now go to "fastboot" in the recobery mode, and ta daaa. You have permissions
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!
Can anybody provide with the flashing instruction for moto g5
yolomonkey said:
Can anybody provide with the flashing instruction for moto g5
Click to expand...
Click to collapse
Assuming you have fastboot installed on your pc
Download firmware and unzip to where you have fastboot
Open command prompt at fastboot location with firmware
type the following although I have marked lines that you should not use unless you have to as flashing wrong firmware can damage your device
Code:
fastboot oem fb_mode_set Only required if you wish to relock bootloader - if not skip it
fastboot flash partition gpt.bin Do not use unless you want to repartition your device - incorrect file will damage your phone
fastboot flash bootloader bootloader.img Do not use unless you want to replace the bootloader - flashing wrong file will hard brick
fastboot flash logo logo.bin No need to flash if you are going to flash a custom rom after and have already flashed a modded version
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 Will erase everything on internal storage but you need to do it
fastboot erase customize Not sure about this - might be for other device
fastboot erase clogo Not sure about this - might be for other device
fastboot oem fb_mode_clear Only required to relock bootloader if you used the very first command
fastboot reboot
NOt working
My device keeps booting to the recovery
even though i flashed my recovery. it boots to twrp
yolomonkey said:
My device keeps booting to the recovery
even though i flashed my recovery. it boots to twrp
Click to expand...
Click to collapse
have you read the FAQs on my twrp thread because the answer is there (assuming you have flashed a custom rom and can boot it through the bootloader by selecting start)
TheFixItMan said:
have you read the FAQs on my twrp thread because the answer is there (assuming you have flashed a custom rom and can boot it through the bootloader by selecting start)
Click to expand...
Click to collapse
could you please link it. I am so grateful for you replying this fast
yolomonkey said:
could you please link it. I am so grateful for you replying this fast
Click to expand...
Click to collapse
https://forum.xda-developers.com/g5/development/official-twrp-3-1-1-0-moto-g5-t3699737
FAQs are on 2nd post
Hi everyone I have some questions if here in the forum we can solve them together
Without offending or underestimating the work of forum members and the people I have quoted, I only try to find solutions​
I have the Chinese version of the Motorola Z2 Play Model XT1710-11, so I wanted to remove the default firmware with ZUI!. by 7.1.1_NZS26.71-36
First try Unlocking the bootloader to work clean following the steps of many sites who recommend working with the unlocked bootloader But unfortunately when I tried to unlock it, it told me a message "BAD KEY", Look for this type of problems in the forum and other sites, according to the problem is because the supplier who I buy it in China, should give me the key, since it is likely that the seller has changed it. Unfortunately the seller does not answer me and I do not think he does.
1. So the first question is: Is it possible to do the flash even if you have this kind of problem?
First I use this command as the flash comes, blocked from the factory by the supplier:
fastboot flashing unlock
Click to expand...
Click to collapse
First of all make a backup of the firmware, and all the elements with the TWRP here: https://forum.xda-developers.com/z2-play/development/twrp-3-2-0-0-moto-z2-play-albus-t3715660
Thanks to @Junior Passos , for his post, who helped me to do it, and in case someone has this phone model with the same "BAD KEY" problem. and be afraid of damaging it, it was tested and it worked normally.
The first problem in my head was that I did not like the operating system that brought by default my Z2-XT1710-11, because even if it was in Spanish or English there were places in the Chinese system
So, what I wanted was a clean and operable nougat.
I started looking for this exact model on the Internet and in the forum, I did not find a specific topic of this model, but in the comments of someone who had it, its name is: @LunaTheLuminous Who had a problem with their modems, https://forum.xda-developers.com/z2-play/help/fastboot-xt1710-11-china-mobile-modem-t3801969.
I did not have a modem problem because I had done backup, but I wanted to try to get to a clean rom and try to flash with comments from @KirMit from here: https://forum.xda-developers.com/showpost.php?p=76813587&postcount=3. Unfortunately there were not the exact commands that he use, for avoid some kind of brick in my device.
Then I continued looking for the same model, and I found something similar that I decided to try : https://forum.xda-developers.com/z2-play/development/moto-z2-play-stock-retail-xt710-07-t3669668. The original idea is to try to get a clean Nougat, According to @KirMit he managed to get a Clean nougat by using Two ROM, which I do not know From Here: https://forum.xda-developers.com/showpost.php?p=74833568&postcount=17.
I tried to find a clearer solution, because I had doubts about the exact commands that I use and roms, below in the comments, KirMit explains: that "the best manual is in the post" . I decided to use the @lexie90 tutorial https://forum.xda-developers.com/z2-play/development/moto-z2-play-stock-retail-xt710-07-t3669668 Thanks with this ROM: "ALBUS_NPSS26.118-19-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml"
and These commands:
fastboot oem lock begin
fastboot oem lock begin
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 modem NON-HLOS.bin I DID NOT USE IT
fastboot erase modemst1 I DID NOT USE IT
fastboot erase modemst2 I DID NOT USE IT
fastboot flash fsg fsg.mbn I DID NOT USE IT
fastboot erase cache
fastboot erase userdata
fastboot oem lock
fastboot reboot
Click to expand...
Click to collapse
NOTE: The commands that are In red do not use them, I put them to see, the commands that I use and the ones that you do not have to use
Here I found a problem, because the bootloader has "BAD KEY" I can not close the OEM LOCK, and in the stage of flash recovery and flash boot it showed this message:
"Image signed with key bad key"
Click to expand...
Click to collapse
The flash of the firmware was made, I could go to the Nougat, Stock Running the modem, fingerprint reader, but when I turned on the phone I got a "bad key error message", looking for this type of problem is that the "logo.bin" file was necessary flash it, Unfortunately I could not find the original, but in the forum there are several people who have made their own logo.bin as: https://forum.xda-developers.com/moto-z/themes/logo-bin-to-remove-unlocked-warning-n-t3757030, and https://forum.xda-developers.com/moto-z-play/themes/logo-bin-t3538153 Thanks to @TobiPeter and @flashallthetime .
But when trying to flash it, and since they were from z play, the screen did not look good, therefore after several tests to eliminate this message:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
To delete the message, from the motorola z2 play MODEL: XT1710-11, I did a flash with the logo that I made in the backup of the twrp.
https://drive.google.com/open?id=1OjPxy5k02MrH73SXZoXjI1sZCp83uFAr
With this command:
fastboot flash logo logo.emmc.win
Click to expand...
Click to collapse
2. My question is is there any way to make a flash clean and to install normal without any error with this type of BAD KEY problem?
But I did not just try that Rom, try several Stock Roms which I present to you in this list:
ALBUS_NPSS26.118-19-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
ALBUS_RETAIL_7.1.1_NPSS26.118-19-18_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
ALBUS_NPSS26.118-19-1-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
CHINESE VERSION XT1710-08
XT1710-08_ALBUS_RETCN_7.1.1_NZS26.71-36_cid11_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
XT1710-08_ALBUS_RETCN_7.1.1_NZS26.71-97-41-9_cid11_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Click to expand...
Click to collapse
Also try to change the command to try to see if there was the error, and use these: https://forum.xda-developers.com/z2-play/how-to/close-bootloader-lineageos-losing-imei-t3769479, Thanks to @Kacike27 , Always avoiding:
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
Click to expand...
Click to collapse
In the ROM of China I decided to make a full flash using all the commands, as @KirMit said in one of his comments.
https://forum.xda-developers.com/showpost.php?p=76813587&postcount=3
Hi. Use this https://mirrors.lolinet.com/firmware...LT_CFC.xml.zip
I flashed all using standard set of fastboot commands including modem flashing and erasing. You will boot in Chinese version, but still able to change a language to English in preferences menu (try to find a right menu by logos). It is still Android Nougat 7.1.1 with CH/EN only languages.
After that I flashed this https://mirrors.lolinet.com/firmware...LT_CFC.xml.zip
But skip modem flashing and erasing. You will have multi language Android Oreo.
Enjoy.
Click to expand...
Click to collapse
Unfortunately I did not succeed the result was the same "bad key" errors and commands ("Image signed with key bad key", FAILED) Etc.
But as you will understand, I was not satisfied with the fact of all these mistakes, which were presented to me along the way, so I decided to do an update to OREO of both version ZUI!!!, and Stock of rom 7.1.1 ALBUS_NPSS26.118-19-4.
Then I followed the instructions in this post by @HTCDevil https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-oreo-retail-via-fastboot-t3786153 Thanks!!!
I followed 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 I DID NOT USE IT
fastboot flash fsg fsg.mbn I DID NOT USE IT
fastboot erase modemst1 I DID NOT USE IT
fastboot erase modemst2 I DID NOT USE IT
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
Click to expand...
Click to collapse
Following the advice of KirMit, I do not use the commands that are in red
By @KirMit
I confirm, that all is working after update on XT1710-11 (China Mobile), BUT! do not flash all - skip:
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
If you want your modems and fingerprint sensor are still working!
Click to expand...
Click to collapse
The process that I did for fastboot, it did not work for me, unfortunately the same mistakes appeared in the previous roms, I have to add that when updating to Oreo, in both versions, ZUI and 7.1.1 (Stock ALBUS_NPSS26.118-19-4.), the fingerprint reader stopped working.
The device, started to "encrypt", when I wanted to downgrade to 7.1.1 ALBUS_NPSS26.118-19-4 or ZUI!!. In the command stage:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
Click to expand...
Click to collapse
The commands were throwing error, (failed), now the question is:
3.It is possible that I can not flash the Bootloader, nor do the gpt partition, because the device is encrypted or has the oreo bootloader
?
To finish I try to flash with RSD Lite, without any result, due to the error when it goes in :"fastboot flash partition gpt.bin", it can not execute the flash in the gpt, it stays stuck in that stage.
The testing of RSD lite was with the help of the following post:
https://forum.xda-developers.com/showpost.php?p=76454434&postcount=29 by @St.Nogiel
https://forum.xda-developers.com/moto-z-play/how-to/mini-guide-bricked-special-case-attempt-t3812530 by @KrisM22
https://forum.xda-developers.com/moto-z-play/how-to/addison-factory-stock-images-t3736767/post75236696#post75236696 by @KrisM22
https://forum.xda-developers.com/moto-z-play/how-to/guide-rsd-lite-mini-guide-t3740641#post75334194 by @KrisM22
Click to expand...
Click to collapse
end of the tests,
sorry for my English. greetings friends
I got a z2 play in secondhand.
This phone is from china mobile and the previous owner has flashed 7.1.1 .
Now the phone is stuck in 7.1.1 and it does not get get updated to 9.0.
Is there any way this can be done.
I contacted Lenovo and they say that the build number is not in the database .
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
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.