Hey guys,
Anyone knows if the stock Android 12 version for this phone is supposed to be this one: HANOIP_RETAIL_S2RIS32.32_20_7_2_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml ?
The only thing that strikes me as potentially not ok is the RETAIL part (shouldn't it be RETIN?) and the DEFAULT CFC.
Can anyone from india confirm this is what it's supposed to be delivered to users in India?
@Raghu varma could you help with some feedback on this, please?
This is not for my phone, by the way. But a friend of mine got into botoloop on his G60 (XT2135-2) ro.carrier: retin, without even unlocking the bootloader (it's all stock). And I was trying to help him get his phone back working. But looks like, so far, no success.
Flashing stock ROM works fine...but, it doesn't fix the actual issue. Factory Resetting also no result.
When trying to boot, the phone shows this:
AP Fastboot Flash Mode (Secure)
No bootable A/B slot
Failed to boot Linux, falling back to fastboot
Fastboot Reason: Fall-through from normal boot mode
Getvar also confirms no bootable slots. So it bootloops for a couple of times, then it shows this error.
So I was thinking maybe LMSA is providing the wrong version. Unlikely, I know. But when I saw "RETAIL" that's what I was thinking.
So...I'm curious. Is this the right version for India? And, if anybody else got this issue, how did you guys fix it?
arsradu said:
Hey guys,
Anyone knows if the stock Android 12 version for this phone is supposed to be this one: HANOIP_RETAIL_S2RIS32.32_20_7_2_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml ?
The only thing that strikes me as potentially not ok is the RETAIL part (shouldn't it be RETIN?) and the DEFAULT CFC.
Can anyone from india confirm this is what it's supposed to be delivered to users in India?
@Raghu varma could you help with some feedback on this, please?
This is not for my phone, by the way. But a friend of mine got into botoloop on his G60 (XT2135-2) ro.carrier: retin, without even unlocking the bootloader (it's all stock). And I was trying to help him get his phone back working. But looks like, so far, no success.
Flashing stock ROM works fine...but, it doesn't fix the actual issue. Factory Resetting also no result.
When trying to boot, the phone shows this:
AP Fastboot Flash Mode (Secure)
No bootable A/B slot
Failed to boot Linux, falling back to fastboot
Fastboot Reason: Fall-through from normal boot mode
Getvar also confirms no bootable slots. So it bootloops for a couple of times, then it shows this error.
So I was thinking maybe LMSA is providing the wrong version. Unlikely, I know. But when I saw "RETAIL" that's what I was thinking.
So...I'm curious. Is this the right version for India? And, if anybody else got this issue, how did you guys fix it?
Click to expand...
Click to collapse
Hi ,
For Indian units we too don't have any official RETIN software. but unfortunately even LMSA redirects to RETAIL software to flash forcefully after i enter my IMEI number to check for latest firmware sadly.
So it's all about phone should work on any firmware but yes make sure the bootloader unlock mandatory to do experiments.
Raghu varma said:
Hi ,
For Indian units we too don't have any official RETIN software. but unfortunately even LMSA redirects to RETAIL software to flash forcefully after i enter my IMEI number to check for latest firmware sadly.
So it's all about phone should work on any firmware but yes make sure the bootloader unlock mandatory to do experiments.
Click to expand...
Click to collapse
Thank you very much for your feedback!
Question: if we try the previous version (S2RI32.32_20_7) should it work without unlocking the bootloader? I'm trying to avoid unlocking bootloader, because that also means losing the warranty. And i'd like to keep that in case he sends the device for repair.
I think the bootloader should refuse flashing in case it cannot flash that version, right? So...it shouldn't hurt to try. What do you think?
arsradu said:
Thank you very much for your feedback!
Question: if we try the previous version (S2RI32.32_20_7) should it work without unlocking the bootloader? I'm trying to avoid unlocking bootloader, because that also means losing the warranty. And i'd like to keep that in case he sends the device for repair.
I think the bootloader should refuse flashing in case it cannot flash that version, right? So...it shouldn't hurt to try. What do you think?
Click to expand...
Click to collapse
50% chances but no hopes. but LMSA has permissions to flash on locked bootloader if i remember correctly. Correct me if i am wrong. so blindly flash recommended firmware by LMSA after your friend enter his IMEI to get back to working state. So that service centre is the final cutting edge work to accomplish straight away.
Raghu varma said:
50% chances but no hopes. but LMSA has permissions to flash on locked bootloader if i remember correctly. Correct me if i am wrong. so blindly flash recommended firmware by LMSA after your friend enter his IMEI to get back to working state. So that service centre is the final cutting edge work to accomplish straight away.
Click to expand...
Click to collapse
Yeah.... The problem is not the flashing itself. That works fine. It's that, with the ROM downloaded by LMSA (the one in my initial post), no matter if it's flashed by LMSA or manually with fastboot commands, the issue still occurs.
Yes, there are some differences between the ROMs in different regions. This time I did not flash the original European ROM, which made me unable to use China Unicom 4g by default. I entered 4636 from the dialer and found that the default frequency band selected is gsm. Switching to evdo I got a normal network connection. But the phone settings interface shows it's 3g and when I switch it back to 4g I lose the network connection again. . . .
{
"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"
}
xindefenggan said:
Yes, there are some differences between the ROMs in different regions. This time I did not flash the original European ROM, which made me unable to use China Unicom 4g by default. I entered 4636 from the dialer and found that the default frequency band selected is gsm. Switching to evdo I got a normal network connection. But the phone settings interface shows it's 3g and when I switch it back to 4g I lose the network connection again. . . .
View attachment 5730067View attachment 5730069
Click to expand...
Click to collapse
According to my analysis, the carrier configuration is something which is restricted from hardware level. We call it as Carrier bands ( in india the moto g60 has certain bands which can survive almost every local carrier. ) So the bands for europian moto g60 models are limited. On & all changing different version stock doesn't hamper anything profit Unless we enable through motherboard. So only way is all about visit service centre and ask them to change the motherboard to global version which can survive any carrier network over the world
@arsradu @xindefenggan
Yeah, I wasn't planning on flashing a ROM from another region. I was only curious if the retail version of this build is the correct one for India.
Cause...with Android 11, according to the mirror site, the build are indeed retin specific.
What's interesting, si that we've got this exact build number S2RIS32.32_20_7_2 in Europe. And...while it's also under "retail" instead of "reteu" like the previous ones, it does have Europe CFC. As where with the build above, for India, it's still on Default CFC.
That's why I thought maybe the build is wrong. But I guess it's not, and the problem is probably somewhere else.
Thank you very much for all your feedback guys!
Raghu varma said:
According to my analysis, the carrier configuration is something which is restricted from hardware level. We call it is Carrier bands ( in india the moto g60 has certain bands which can survive almost every local carrier. ) So the bands for europian moto g60 models are limited. On & all changing different version stock doesn't hamper anything profit Unless we enable through motherboard. So only way is all about visit service centre and ask them to change the motherboard to global version which can survive any carrier network over the world
@arsradu @xindefenggan
Click to expand...
Click to collapse
Mine is not a retail version, it shows that the software update channel is North America, obviously it is a North American engineering machine
xindefenggan said:
Mine is not a retail version, it shows that the software update channel is North America, obviously it is a North American engineering machine
Click to expand...
Click to collapse
Yup the base motherboard belongs to North American then.
@Raghu varma, for reference, this is what happens if you try to flash an older version (in this case S2RI32.32-20-7), with a locked bootloader. I only selected the errors/warnings where applicable. Rest of the files are flashed successfully.
So, basically nothing was broken, but also, nothing was fixed either. Unfortunately. Next step would be unlocking the bootloader.
fastboot flash vbmeta vbmeta.img
Sending 'vbmeta_a' (8 KB)
OKAY [ 0.010s]
Writing 'vbmeta_a'
(bootloader) WARNING: vbmeta_a anti rollback downgrade, 10 vs 11
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
fastboot flash vbmeta_system vbmeta_system.img
Sending 'vbmeta_system_a' (4 KB)
OKAY [ 0.000s]
Writing 'vbmeta_system_a'
(bootloader) WARNING: vbmeta_system_a anti rollback downgrade, 10 vs 11
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
fastboot flash boot boot.img
Sending 'boot_a' (65536 KB)
OKAY [ 1.450s]
Writing 'boot_a'
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
fastboot flash vendor_boot vendor_boot.img
Sending 'vendor_boot_a' (65536 KB)
OKAY [ 1.461s]
Writing 'vendor_boot_a'
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
fastboot flash dtbo dtbo.img
Sending 'dtbo_a' (8192 KB)
OKAY [ 0.190s]
Writing 'dtbo_a'
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
fastboot flash super super.img_sparsechunk.0
Sending 'super' (459112 KB)
OKAY [ 10.282s]
Writing 'super'
(bootloader) *****************************************************
(bootloader) WARNING: Flashing vbmeta image is required prior to
(bootloader) flashing super image.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote: '')
fastboot: error: Command failed
fastboot flash super super.img_sparsechunk.1
Sending 'super' (524208 KB)
OKAY [ 11.710s]
Writing 'super'
(bootloader) *****************************************************
(bootloader) WARNING: Flashing vbmeta image is required prior to
(bootloader) flashing super image.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote: '')
fastboot: error: Command failed
fastboot flash super super.img_sparsechunk.2
Sending 'super' (524232 KB)
OKAY [ 11.722s]
Writing 'super'
(bootloader) *****************************************************
(bootloader) WARNING: Flashing vbmeta image is required prior to
(bootloader) flashing super image.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote: '')
fastboot: error: Command failed
fastboot flash super super.img_sparsechunk.3
Sending 'super' (524252 KB)
OKAY [ 11.761s]
Writing 'super'
(bootloader) *****************************************************
(bootloader) WARNING: Flashing vbmeta image is required prior to
(bootloader) flashing super image.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote: '')
fastboot: error: Command failed
fastboot flash super super.img_sparsechunk.4
Sending 'super' (524248 KB)
OKAY [ 11.639s]
Writing 'super'
(bootloader) *****************************************************
(bootloader) WARNING: Flashing vbmeta image is required prior to
(bootloader) flashing super image.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote: '')
fastboot: error: Command failed
fastboot flash super super.img_sparsechunk.5
Sending 'super' (495328 KB)
OKAY [ 11.011s]
Writing 'super'
(bootloader) *****************************************************
(bootloader) WARNING: Flashing vbmeta image is required prior to
(bootloader) flashing super image.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote: '')
fastboot: error: Command failed
fastboot flash super super.img_sparsechunk.6
Sending 'super' (524248 KB)
OKAY [ 11.721s]
Writing 'super'
(bootloader) *****************************************************
(bootloader) WARNING: Flashing vbmeta image is required prior to
(bootloader) flashing super image.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote: '')
fastboot: error: Command failed
fastboot flash super super.img_sparsechunk.7
Sending 'super' (484372 KB)
OKAY [ 10.731s]
Writing 'super'
(bootloader) *****************************************************
(bootloader) WARNING: Flashing vbmeta image is required prior to
(bootloader) flashing super image.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote: '')
fastboot: error: Command failed
fastboot flash super super.img_sparsechunk.8
Sending 'super' (513244 KB)
OKAY [ 11.437s]
Writing 'super'
(bootloader) *****************************************************
(bootloader) WARNING: Flashing vbmeta image is required prior to
(bootloader) flashing super image.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote: '')
fastboot: error: Command failed
fastboot flash super super.img_sparsechunk.9
Sending 'super' (524200 KB)
OKAY [ 11.658s]
Writing 'super'
(bootloader) *****************************************************
(bootloader) WARNING: Flashing vbmeta image is required prior to
(bootloader) flashing super image.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote: '')
fastboot: error: Command failed
fastboot flash super super.img_sparsechunk.10
Sending 'super' (173852 KB)
OKAY [ 3.882s]
Writing 'super'
(bootloader) *****************************************************
(bootloader) WARNING: Flashing vbmeta image is required prior to
(bootloader) flashing super image.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote: '')
fastboot: error: Command failed
Related
The bootloader are unlocked. But, when I decide to rollback, I started the flash process using "fastboot oem lock begin"; then, every try of flash give me this kind of error, showed bellow.
So, for example, I got this when I tried to flash stock over a lineage rom:
Code:
target reported max download size of 536870912 bytes
sending 'partition' (45 KB)...
OKAY [ 0.014s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.184s
What should I do? I have tried to flash bootloader.img and use "fastboot oem fb_mode_set", but stay in the same situation.
Obviously, I'm using the exactly stock versions to my device.
Thank you guys! :laugh:
motafoca55 said:
The bootloader are unlocked. But, when I decide to rollback, I started the flash process using "fastboot oem lock begin"; then, every try of flash give me this kind of error, showed bellow.
So, for example, I got this when I tried to flash stock over a lineage rom:
What should I do? I have tried to flash bootloader.img and use "fastboot oem fb_mode_set", but stay in the same situation.
Obviously, I'm using the exactly stock versions to my device.
Thank you guys! :laugh:
Click to expand...
Click to collapse
All I can say is you should have pulled ur stock ROM
With the help of @Nirbhay2 I managed to block my bootloader, however what I wanted to share here is that to block the bootloader of the Brazilian variant it is necessary the last ROM with january security patch POTTER_NPNS25.137-92-4. Here you will find the guide to block your Brazilian device.
Have minimal ADB
Have Motorola drivers installed on your PC
Have the january patch ROM stock: https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Extract the ROM to any folder and paste the minimal ADB along with the extracted ROM.
Open a command prompt in the folder and with the device in fastboot mode make a flash of the entire ROM stock on your device, to facilitate copying all the commands at once and paste at the command prompt and it will install automatic to your ROM , then do the same with the commands to re-block the bootloader and at the end of this process your device will be started with bootloader locked.
Commands to re-lock bootloader, do this after the full ROM flash
fastboot oem lock
fastboot oem lock
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
Command link for flash ROM stock
https://pastebin.com/ZWTaWuyr
We thank @Nirbhay2 for this great guide.
I have a problem relocking bootloader:
...
[email protected] at 12:34:24 ~/tmp/potter/POTTER_NPNS25.137-35-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml> fastboot flash boot boot.img
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.870s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.465s]
finished. total time: 1.335s
...
[email protected] at 12:36:36 ~/tmp/potter/POTTER_NPNS25.137-35-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml> fastboot oem lock
...
(bootloader) Still require signed boot.img
OKAY [ 0.002s]
finished. total time: 0.002s
So, bootloader remains unlocked.
Moreover:
[email protected] at 12:36:38 ~/tmp/potter/POTTER_NPNS25.137-35-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml> fastboot flash bootloader bootloader.img(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.271s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image tz failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image devcfg failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.551s
How can I flash original bootloader, boot and lock bootloader?
pss34 said:
I have a problem relocking bootloader:
...
[email protected] at 12:34:24 ~/tmp/potter/POTTER_NPNS25.137-35-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml> fastboot flash boot boot.img
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.870s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.465s]
finished. total time: 1.335s
...
[email protected] at 12:36:36 ~/tmp/potter/POTTER_NPNS25.137-35-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml> fastboot oem lock
...
(bootloader) Still require signed boot.img
OKAY [ 0.002s]
finished. total time: 0.002s
So, bootloader remains unlocked.
Moreover:
[email protected] at 12:36:38 ~/tmp/potter/POTTER_NPNS25.137-35-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml> fastboot flash bootloader bootloader.img(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.271s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image tz failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image devcfg failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.551s
How can I flash original bootloader, boot and lock bootloader?
Click to expand...
Click to collapse
friend, you need to use this ROM that I made available on the link, if you have a moto G5 plus brazilian you can get the lock, but use this link ROM.
Enviado de meu XT1683 usando Tapatalk
I tried the same thing.
I had TWRP and SuperSu on my phone a few days back. But weirdly, I lost network connectivity and after a botched attempt at installing V4A, the audio died as well. Even the camera and the flash had stopped working. More weirdly, the Root Checker app I had now showed me that root access was not properly installed.
SInce my phone was on the November patch (25-137-92), I found the stock ROM of it online and flashed it with the Moto G5 Plus ToolKit.
Now all the issues I've had are fixed. Everything works perfectly. TWRP has been removed along with SuperSu.
But the bootloader still shows me that software status is modified. The warning on boot-up which tells that the device has been unlocked is still there.
I don't know if it's related but I've got WiFi speed issues now, apps won't download quickly or is it my damn internet?
The bootloader IS locked, though. That I can say confidently because the bootloader unlock option in developer options is now not selected.
Moto G(5) Plus XT1686 4/32 GB Indian Version
hELLO..
I have had a moto g5 with oreo and magisk installed I tried to unistall magisk from magisk app after reboot it told me that startup failed then flashed an nougat rom and it worked perfectly but without imei numbers so i deleted cache from twrp recovery and tried to install the same software again but it gave me the error at the end ..what should I know now to fix the mobile knowing that when i try to select recoverymode it tells me ersing and then takes m back to fastboot
note the first time i just opened a bat file with the software that installed the software automatically..
the bat file told me that
<bootloader> slot-count not found
<bootloader> slot suffixes not found
<bootloader>has-slot:fsg not found
Flash this firmware https://drive.google.com/file/d/1cESQyuRpeUAmmEn67_to0sQ0KLhkMnWM/view (Oreo 8.1, February 2019 security patch) using fastboot and commands below. All the data in the internal storage of the phone will be erased.
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 erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Hi. Mine G5 is bricked as well.
When I`m trying to do what u said Andrej I got that:
C:\platform-tools>fastboot oem fb_mode_set
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash partition gpt.bin
(bootloader) is-logicalartition: not found
Sending 'partition' (45 KB) OKAY [ 0.169s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
Any ideas?
pablito1984 said:
Hi. Mine G5 is bricked as well.
When I`m trying to do what u said Andrej I got that:
Any ideas?
Click to expand...
Click to collapse
The firmware you are trying to flash is too old hense the security downgrade error
You must use firmware that is equal to or newer than what was previously flashed on it
Firmware available at
https://mirrors.lolinet.com/firmware/moto/cedric/official/
TheFixItMan said:
The firmware you are trying to flash is too old hense the security downgrade error
You must use firmware that is equal to or newer than what was previously flashed on it
Firmware available at
Click to expand...
Click to collapse
Thank you for your reply.
I`ve downloaded XT1675_CEDRIC_RETGB_SS_8.1.0_OPPS28.85-13-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
as my phone model is XT1675.
I don`t know why, but when I`m trying to put fastboot oem fb_mode_set and it gives me that error
pablito1984 said:
Thank you for your reply.
I`ve downloaded XT1675_CEDRIC_RETGB_SS_8.1.0_OPPS28.85-13-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
as my phone model is XT1675.
I don`t know why, but when I`m trying to put fastboot oem fb_mode_set and it gives me that error
Click to expand...
Click to collapse
That command is just to tell the phone you are about to flash firmware and the clear command at the end exists this mode
You don't need to use these commands it's just a way of telling the phone what you are doing and to start the phone normally after the flashing
You should be able to start with gpt (presuming you have found a firmware that is the same or newer than what you have on the phone already)
TheFixItMan said:
That command is just to tell the phone you are about to flash firmware and the clear command at the end exists this mode
You don't need to use these commands it's just a way of telling the phone what you are doing and to start the phone normally after the flashing
You should be able to start with gpt (presuming you have found a firmware that is the same or newer than what you have on the phone already)
Click to expand...
Click to collapse
Thanks for explaining me that
I`ve downloaded now CEDRIC_RETAIL_8.1.0_OPPS28.85-16-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
And this time it`s not saying anything about downgrade, but I got this:
C:\platform-tools>fastboot flash partition gpt.bin
(bootloader) is-logical: partition: not found
Sending 'partition' (45 KB) OKAY [ 0.169s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
pablito1984 said:
Thanks for explaining me that
I`ve downloaded now CEDRIC_RETAIL_8.1.0_OPPS28.85-16-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
And this time it`s not saying anything about downgrade, but I got this:
Click to expand...
Click to collapse
I presume you can get into the bootloader without using a sdcard for a hard bricked device
If so skip gpt and bootloader parts of the firmware - these don't need to be flashed unless your phone was hard bricked (just get a red flashing led if mmcblk0 sdcard not inserted)
Also make sure you have the Motorola drivers installed and that you are using the latest fastboot drivers from the android sdk
TheFixItMan said:
I presume you can get into the bootloader without using a sdcard for a hard bricked device
If so skip gpt and bootloader parts of the firmware - these don't need to be flashed unless your phone was hard bricked (just get a red flashing led if mmcblk0 sdcard not inserted)
Also make sure you have the Motorola drivers installed and that you are using the latest fastboot drivers from the android sdk
Click to expand...
Click to collapse
Yes. I can get into bootloader, but I can`t do anything over there except restarting and checking logs.
After checking the logs I can see :
Start up failed:
Your device didn`t start up successfully.
Use the Software Repair Assistant on computer to repair your device.
Connect your device to your computer to get Software Repair Assistant.
AP Fastboot Flash Mode (Secure)
Fastboot Reason: Last time flashing failed
USB Connected
failed to validate recovery iumage
ERROR: Failed to pass validation, backup to fastboot
Boot up failed
Click to expand...
Click to collapse
Tried to use Lenovo Moto smart assistant to fix it, but it doesn`t see the device.
I`ve got all drivers, sdk, etc.
When tried to use fastboot I got this:
C:\platform-tools>fastboot oem fb_mode_set
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash partition gpt.bin
(bootloader) is-logicalartition: not found
Sending 'partition' (45 KB) OKAY [ 0.170s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash bootloader bootloader.img
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (5179 KB) OKAY [ 0.331s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition aboot
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash logo logo.bin
(bootloader) is-logical:logo: not found
Sending 'logo' (2242 KB) OKAY [ 0.240s]
Writing 'logo' (bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash boot boot.img
(bootloader) is-logical:boot: not found
Sending 'boot' (16384 KB) OKAY [ 0.689s]
Writing 'boot' (bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash recovery recovery.img
(bootloader) is-logical:recovery: not found
Sending 'recovery' (16484 KB) OKAY [ 0.694s]
Writing 'recovery' (bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash dsp adspso.bin
(bootloader) is-logical:dsp: not found
Sending 'dsp' (16384 KB) OKAY [ 0.688s]
Writing 'dsp' (bootloader) Failed to erase partition
(bootloader) Failed to flash partition dsp
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash oem oem.img
(bootloader) is-logicalem: not found
Sending 'oem' (148900 KB) OKAY [ 4.969s]
Writing 'oem' (bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.0
(bootloader) is-logical:system: not found
Sending 'system' (256537 KB) OKAY [ 8.462s]
Writing 'system' (bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.1
(bootloader) is-logical:system: not found
Sending 'system' (256653 KB) OKAY [ 8.529s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.2
(bootloader) is-logical:system: not found
Sending 'system' (257978 KB) OKAY [ 8.446s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.3
(bootloader) is-logical:system: not found
Sending 'system' (260705 KB) OKAY [ 8.488s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.4
(bootloader) is-logical:system: not found
Sending 'system' (257421 KB) OKAY [ 8.464s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.5
(bootloader) is-logical:system: not found
Sending 'system' (257865 KB) OKAY [ 8.506s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.6
(bootloader) is-logical:system: not found
Sending 'system' (252667 KB) OKAY [ 8.402s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.7
(bootloader) is-logical:system: not found
Sending 'system' (253700 KB) OKAY [ 8.409s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.8
(bootloader) is-logical:system: not found
Sending 'system' (250301 KB) OKAY [ 8.271s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash modem NON-HLOS.bin
(bootloader) is-logical:modem: not found
Sending 'modem' (66366 KB) OKAY [ 2.329s]
Writing 'modem' (bootloader) Failed to erase partition
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot erase modemst1
Erasing 'modemst1' (bootloader) Failed to erase partition
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot erase modemst2
Erasing 'modemst2' (bootloader) Failed to erase partition
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash fsg fsg.mbn
(bootloader) is-logical:fsg: not found
Sending 'fsg' (2956 KB) OKAY [ 0.258s]
Writing 'fsg' (bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot erase cache
Erasing 'cache' (bootloader) Failed to erase partition
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot erase userdata
Erasing 'userdata' (bootloader) Failed to erase partition
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot erase customize
Erasing 'customize' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot erase clogo
Erasing 'clogo' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot oem fb_mode_clear
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.004s
Click to expand...
Click to collapse
pablito1984 said:
Yes. I can get into bootloader, but I can`t do anything over there except restarting and checking logs.
After checking the logs I can see :
Tried to use Lenovo Moto smart assistant to fix it, but it doesn`t see the device.
I`ve got all drivers, sdk, etc.
When tried to use fastboot I got this:
Click to expand...
Click to collapse
Either your setup is wrong - try another pc USB cable etc or you have a motherboard fault & need to replace it
TheFixItMan said:
That command is just to tell the phone you are about to flash firmware and the clear command at the end exists this mode
You don't need to use these commands it's just a way of telling the phone what you are doing and to start the phone normally after the flashing
You should be able to start with gpt (presuming you have found a firmware that is the same or newer than what you have on the phone already)
Click to expand...
Click to collapse
im having the same issue with moto e5play xt1921-1 i dont know what the latest fw is
ghettozo said:
im having the same issue with moto e5play xt1921-1 i dont know what the latest fw is
Click to expand...
Click to collapse
Neither do i as I don't own your phone
Go to your own phone forum or Google for firmware for your device
To flash gpt and bootloader it must be the same or newer than version on device and an unlocked bootloader to avoid permissions errors especially if has been unlocked before
TheFixItMan said:
Neither do i as I don't own your phone
Go to your own phone forum or Google for firmware for your device
To flash gpt and bootloader it must be the same or newer than version on device and an unlocked bootloader to avoid permissions errors especially if has been unlocked before
Click to expand...
Click to collapse
thanks. yes im using the forum here and google but im having issues
thankyou\
Hello,
I'm using the AOSiP 9 ROM on my moto z play, and i want to go back to stock rom.
I'm tried this tutorial but when i do the command:
Code:
.\fastboot.exe flash partition gpt.bin
i got the error:
Code:
(bootloader) has-slot:partition: not found
(bootloader) is-logical:partition: not found
Sending 'partition' (45 KB) OKAY [ 0.170s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
My MZP model is XT-1635-02.
Somebody can help-me to go back to stock MZP rom?
Thanks! :good:
Download and extract this firmware and then follow the flashing order from this GUIDE
I would recommend to use minimal adb and fastboot to execute those commands, and exactly how the guide describes
It worked! I will try to use this article to block the bootloader again.
Thanks for the help!
SOLVED I will make a topic about it https://forum.xda-developers.com/g5/help/how-to-revert-moto-g5-xt1670-to-stock-t4183425
Hello, how are you all over there? I here in trouble with this XT1670. I have installed several roms but now i want to go back to the official one, but it dont lock the bootloader.
Tried the following command (twice) to lock the bootloader: fastboot oem lock
And i get the following result:
Code:
(bootloader) Flash valid Android images now
(bootloader) Then re-run this command to lock
OKAY [ 0.016s]
finished. total time: 0.016s
Now i use the following command: fastboot flash boot boot.img
And the following was obtained:
Code:
target reported max download size of 535822336 bytes
sending 'boot' (16384 KB) ...
OKAY [0.545s]
writing 'boot' ...
(bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.747s
I have already tried several. Boot, gpt, oem with official rom. All showing the error "Security version downgrade"
I also tried Lenovo's Rescue & Smart app, but it says the SKU is wrong and doesn't recognize the mobile phone.
I don't know how to continue. I could put an official rom, but when you restart the phone the bootloader appears. It only starts when press start.
Not only does that happen. Every so often, the phone turns itself off and remains in the bootloader. And then when you start up, bug reports pop up to share with who knows what.
I do not know what to do. You are the experts.
Ty in advance