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,
today my Moto G7 Play XT1952-1 seems to be bricket. It got stuck at fastboot. The Motorola/Lenovo Rescue tool did not recognize my phone. Seems the bootloader is defective? I will have an try with blank-flash, but i always get an error message: ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error.
Flashing the bootloader gives that result:
$ fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (32768 KB)...
OKAY [ 1.187s]
writing 'boot'...
(bootloader) Invalid partition name boot
FAILED (remote failure)
finished. total time: 1.187s
Are the partitions damaged somehow?
Any suggestions to fix my phone?
Regards,
Ben
I solved the problem - sometimes it is better to use native windows instead of linux ran it under windows and now i was able to install TWRP again.
Hi
im trying to flash the twrp on recovery (fastboot flash recovery twrp.img) but im getting
Sending 'recovery' (29108 KB) OKAY [ 0.742s]
Writing 'recovery' FAILED (remote: 'Cannot flash this partition in unlocked state')
fastboot: error: Command failed
my bootloader is unlocked and phone is rooted
thanks for the help.
Hello,
I'm a beginner in the field of flasing custom roms but I would really like to abandon using google on my phone and find your work here really awesome. So yeah, I hope my question doesn't sound stupid but I'm seriously stuck and hope I didn't completely break my phone.
I am using a Redmi Note 8 (2021) and wanted to flash lineageOS. So I unlocked the bootloader via my mi account, booted into fastboot mode (usb-debugging was of course enabled) and tried to flash twrp to recovery using the cmd-window via platform-tools.
This didn't work because when I typed:
./fastboot flash recovery twrp.img
I got the reply:
Sending 'recovery' (65536 KB) OKAY [ 1.743s]
Writing 'recovery' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
I therefore started googling and found a threat on xda where someone had solved the problem by replacing 'recovery' with 'boot':
./fastboot flash boot twrp.img
What I got was:
Sending 'boot_a' (65536 KB) OKAY [ 1.818s]
Writing 'boot_a' OKAY [ 0.827s]
Finished. Total time: 2.681s
After that my phone was bricked. I cannot enter recovery mode anymore and even fastboot mode appears a bit different (I don't see the bunny anymore, all I see is the word 'fastboot' in orange letters on a black screen). When I enter fastboot mode, the device is detected by my computer - the only sign that still gives me an inch of hope. When I'm not in fastboot mode my phone keeps vibrating and then turning of, then suddenly it vibrates again and turns on, the logo 'redmi' appears and then it suddenly turns off again - and it just keeps repeating this procedure.
I downloaded the mi flash tool and tried to flash the Xiaomi ROM, but that didn't work either - after about five minutes of waiting I get an error. I tried different versions of MIUI but keep getting errors. When I try to flash the Xiaomi ROM via cmd-window, as suggested here ( https://www.droidwin.com/unbrick-redmi-note-8-fastboot-commands/ ) I get this:
fastboot flash xbl xbl.elf
Sending 'xbl' (3449 KB) OKAY [ 0.105s]
Writing 'xbl' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
Is there anything left for me to do or should I give up and save money for a new phone? I am also wondering why the command-window keeps talking about 'boot_a'. Is there a 'boot-b' also? And should I write something onto it? When I try to boot the twrp.img by typing:
fastboot boot twrp.img
I get:
Sending 'boot.img' (65536 KB) OKAY [ 1.592s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
I would be very, very grateful for help
Try this
https://www.getdroidtips.com/twrp-recovery-redmi-note-8-2021-root/
I guess you have used a wrong recovery file, maybe one for another device
The problem is that the command 'flash recovery' does not work, because it says th partition does not exist....
Norah1838 said:
I am using a Redmi Note 8 (2021)
Click to expand...
Click to collapse
wrong forum ! , see Biloba forum
on some devices, boot+recovery are on the same partition, but not for Biloba
boot partition (+dtbo on some cases) is the kernel
i think you should look for official install of miui rom since it has IMG of most partitions ...
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