Hello,
I've purchased a Moto Maxx from Puerto Rico with the amxpr firmware.
I want to change my phone region to Retail Latin America (retla), so I did flash the RETLA firmware from here http://forum.xda-developers.com/dro...t/moto-maxx-retlaxt12254-4-4kxg21-50-t2994569
Now Im using that firmware with no problems, but there are some details I would like to know if can be corrected.
1- When I look at the information in the About Phone section of the settings, I see that the system version is retla indeed, but it also shows amxpr (see first attachment)
2- The SIM services app is displayed as "Claro", the mobile network that sells the Moto Maxx in Puerto Rico, but I'm not in that network, and I would like to see that app with a generic name. (see second attachment)
So I would like to know if there is any way to completely remove any references to amxpr in my phone so it completely looks like retla, and no Claro branding.
I come from Samsung phones, where you can change the CSC (Country Specific Code) to do exactly this thing, I have no idea if it's possible with Motorola phones.
Thank you!
Ok
Emisand said:
Hello,
I've purchased a Moto Maxx from Puerto Rico with the amxpr firmware.
I want to change my phone region to Retail Latin America (retla), so I did flash the RETLA firmware from here http://forum.xda-developers.com/dro...t/moto-maxx-retlaxt12254-4-4kxg21-50-t2994569
Now Im using that firmware with no problems, but there are some details I would like to know if can be corrected.
1- When I look at the information in the About Phone section of the settings, I see that the system version is retla indeed, but it also shows amxpr (see first attachment)
2- The SIM services app is displayed as "Claro", the mobile network that sells the Moto Maxx in Puerto Rico, but I'm not in that network, and I would like to see that app with a generic name. (see second attachment)
So I would like to know if there is any way to completely remove any references to amxpr in my phone so it completely looks like retla, and no Claro branding.
I come from Samsung phones, where you can change the CSC (Country Specific Code) to do exactly this thing, I have no idea if it's possible with Motorola phones.
Thank you!
Click to expand...
Click to collapse
how was installed in you phone
Pika71 said:
how was installed in you phone
Click to expand...
Click to collapse
I installed the factory image I linked using fastboot, running all the commands detailed in the flashfile.xml
That would be:
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot bootloader.img
fastboot flash radio radio.img
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 erase cache
fastboot erase userdata
fastboot erase clogo
fastboot oem
For some reason, the System Version (Versión del Sistema) shows the RETLA firmware, but at the end of that text it says AMXPR (the version for Claro Puerto Rico)
And the generic android app for the SIM card services is displayed as Claro.
In Samsung phones you can change that by changing the CSC code, but I don't see that Motorola has something like that in their software.
ok
Emisand said:
I installed the factory image I linked using fastboot, running all the commands detailed in the flashfile.xml
That would be:
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot bootloader.img
fastboot flash radio radio.img
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 erase cache
fastboot erase userdata
fastboot erase clogo
fastboot oem
For some reason, the System Version (Versión del Sistema) shows the RETLA firmware, but at the end of that text it says AMXPR (the version for Claro Puerto Rico)
And the generic android app for the SIM card services is displayed as Claro.
In Samsung phones you can change that by changing the CSC code, but I don't see that Motorola has something like that in their software.
Click to expand...
Click to collapse
tries with RSD lite
Pika71 said:
tries with RSD lite
Click to expand...
Click to collapse
I did actually try with RSD lite too with the same results.
RSD lite just reads the xml file and excecute the commands the same way I did.
I think something else is needed to change that.
Emisand said:
I did actually try with RSD lite too with the same results.
RSD lite just reads the xml file and excecute the commands the same way I did.
I think something else is needed to change that.
Click to expand...
Click to collapse
maybe small partition of carrier
Pika71 said:
maybe small partition of carrier
Click to expand...
Click to collapse
Yeah, maybe.
There is some way to read all partitions in the phone without unlocking the bootloader?
So I can compare with a true RETLA or RETBR phone.
Emisand said:
I did actually try with RSD lite too with the same results.
RSD lite just reads the xml file and excecute the commands the same way I did.
I think something else is needed to change that.
Click to expand...
Click to collapse
You missed this command on fastboot mode :
Fastboot oem fb_mode_clear
This command supposedly changes to oem your phone
Try it
Jaocagomez said:
You missed this command on fastboot mode :
Fastboot oem fb_mode_clear
This command supposedly changes to oem your phone
Try it
Click to expand...
Click to collapse
Yes, I did write that command, forgot to write here the fb_mode_clear part.
I guess it's something like Pika said, about some additional partition in the system that does not come with the retail firmwares.
How can I list all the partitions on the phone?
Ok I have the list of all the partitions in my phone, it looks like it would be a bit complicated to find where is that amxpr variant is set.
Code:
[email protected]_umts:/dev/block/platform/msm_sdcc.1/by-name $ ls
aboot
abootBackup
boot
cache
cid
clogo
ddr
factorytune1
factorytune2
kpan
logo
logs
mdm1dhob
mdm1hob
mdm1m9kefs1
mdm1m9kefs2
mdm1m9kefs3
mdm1m9kefsc
misc
modem
padA
padB
padC
pds
persist
recovery
rpm
rpmBackup
sbl1
sbl1bak
sdi
sec
sp
ssd
system
tz
tzBackup
userdata
utags
utagsBackup
Emisand said:
Ok I have the list of all the partitions in my phone, it looks like it would be a bit complicated to find where is that amxpr variant is set.
Code:
[email protected]_umts:/dev/block/platform/msm_sdcc.1/by-name $ ls
aboot
abootBackup
boot
cache
cid
clogo
ddr
factorytune1
factorytune2
kpan
logo
logs
mdm1dhob
mdm1hob
mdm1m9kefs1
mdm1m9kefs2
mdm1m9kefs3
mdm1m9kefsc
misc
modem
padA
padB
padC
pds
persist
recovery
rpm
rpmBackup
sbl1
sbl1bak
sdi
sec
sp
ssd
system
tz
tzBackup
userdata
utags
utagsBackup
Click to expand...
Click to collapse
developers, his help
Invoking @jcase @Skrilax_CZ @matheus_sc
Can you help me with this?
I think that is stored in your utags. i.e. reboot to fastboot and do "fastboot oem config carrier" to read the current, "fastboot oem config carrier xyz" to write the xyz. Although I don't see how that is used, since there is "ro.fsg-id" property to deal with selecting initial NV parameters.
Skrilax_CZ said:
I think that is stored in your utags. i.e. reboot to fastboot and do "fastboot oem config carrier" to read the current, "fastboot oem config carrier xyz" to write the xyz. Although I don't see how that is used, since there is "ro.fsg-id" property to deal with selecting initial NV parameters.
Click to expand...
Click to collapse
I've tried that fastboot command and got this:
Code:
C:\Users\Emiliano>fastboot oem config carrier
...
(bootloader) <UTAG name="carrier" protected="false">
(bootloader) <value>
(bootloader) </value>
(bootloader) <description>
(bootloader) Carrier IDs, see http://goo.gl/lojLh3
(bootloader) </description>
(bootloader) </UTAG>
OKAY [ 0.010s]
finished. total time: 0.011s
There is no value, so I don't think the problem is there.
Hmm, looks like they changed it then, but mine shows "amxpr".
Skrilax_CZ said:
Hmm, looks like they changed it then, but mine shows "amxpr".
Click to expand...
Click to collapse
Oh, nevermind.
I will wait for cyanogenmod.
Any big differences in the kernel compared with Nexus 6 "shamu"?
It's not based on Nexus 6 (kernel wouldn't boot) and there are HW differences. So for now, CAF based.
Bumping my thread.
Does anybody know now how to do this?
Related
The other day I was just on my phone and restarted it. When I tried to power up the phone again it said "Warning Unlocked Bootloader" just like it does every time, but now it won't go past that screen. I have tried everything I can think of and this is still happening. Is there anything I can do to fix this?!?!
What is everything you can think of? Did you try wiping both cache's
Sent from my PACMAN MATRIX HD MAXX
deeje00 said:
What is everything you can think of? Did you try wiping both cache's
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
Well the only thing I can even to on it is go into fastboot mode. I've tried all the commands in the boot menu and nothing. I tried to use RSD Lite to go back to stock 4.1.1 but that wouldn't work either. I can't think of anything other than that.
MetalKiderific said:
Well the only thing I can even to on it is go into fastboot mode. I've tried all the commands in the boot menu and nothing. I tried to use RSD Lite to go back to stock 4.1.1 but that wouldn't work either. I can't think of anything other than that.
Click to expand...
Click to collapse
Do a full format of /data. You'll lose all internal sd data, but you'll be booting.
Boot into fastboot
Use the fastboot executable linked in the guide stickied in general
fastboot format cache
fastboot format userdata
My guess is you changed from 4.3/4.2 rom to a 4.1 rom or vice a versa.
skeevydude said:
Do a full format of /data. You'll lose all internal sd data, but you'll be booting.
Boot into fastboot
Use the fastboot executable linked in the guide stickied in general
fastboot format cache
fastboot format userdata
My guess is you changed from 4.3/4.2 rom to a 4.1 rom or vice a versa.
Click to expand...
Click to collapse
thats not what i did, but I tried your method. When i typed in any fastboot commands it comes back at me saying
"(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
error: cannot load 'boot.img' : No error"
MetalKiderific said:
thats not what i did, but I tried your method. When i typed in any fastboot commands it comes back at me saying
"(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
error: cannot load 'boot.img' : No error"
Click to expand...
Click to collapse
Download a stock fastboot and extract it
Copy the guides linked fastboot executable into the extracted location and rename it moto-fastboot
Open a command prompt/terminal in the extracted location
Do all of these commands in order exactly as written.
Use ./moto-fastboot on linux
The first line in bold can't be overwritten with an older version, so if you've flashed Mex Retail with fastboot or RSD you'll only be able to use gpt_main0.bin from Mex Retail.
Code:
[B]fastboot flash partition gpt_main0.bin[/B]
moto-fastboot flash sbl1 sbl1.mbn
moto-fastboot flash sbl2 sbl2.mbn
moto-fastboot flash sbl3 sbl3.mbn
moto-fastboot flash rpm rpm.mbn
moto-fastboot flash tz tz.mbn
moto-fastboot flash aboot emmc_appsboot.mbn
moto-fastboot flash modem NON-HLOS.bin
moto-fastboot flash fsg fsg.mbn
moto-fastboot erase modemst1
moto-fastboot erase modemst2
moto-fastboot flash logo logo.bin
moto-fastboot flash boot boot.img
moto-fastboot flash devtree device_tree.bin
moto-fastboot flash cdrom cdrom
moto-fastboot erase tombstones
moto-fastboot erase cache
moto-fastboot erase userdata
This is exactly what I do whenever I brick myself.
If you actually like the unlocked bootloader warning, skip flashing logo.bin
You could possibly use the Myth tool if you're using Windows. You should also read skeevydude's post in the Atrix HD General section, the Unlocked bootloader, what now... and the Beginner's guide. That should have a lot of the resources you'll need to fix the issue. If you can boot into fastboot, you shouldn't panic.
Thanks, I will try that
Did that work for you? I'm having the same issue.
Hi guys, I think I really messed up my new Moto X: and when I say new I mean I bought it yesterday even if used and bricked today.
I had a 4.4 Sprint firmware and I followed the guide to unlock the device (which it seemed to work), since I need it in Europe with a Vodafone sim. After that I decided to get a UK firmware, so I flashed the phone with RSD Lite, but the flash failed and now in boot mode I have the following message: Partition (boot) Security Version Downgraded - Fasboot reason: boot failure. If you have the solution can you explain it step by step, I'm not actually good with this kind of things. Do you think I have to toss the device in the trash bin? Thank you
Jack881 said:
Hi guys, I think I really messed up my new Moto X: and when I say new I mean I bought it yesterday even if used and bricked today.
I had a 4.4 Sprint firmware and I followed the guide to unlock the device (which it seemed to work), since I need it in Europe with a Vodafone sim. After that I decided to get a UK firmware, so I flashed the phone with RSD Lite, but the flash failed and now in boot mode I have the following message: Partition (boot) Security Version Downgraded - Fasboot reason: boot failure. If you have the solution can you explain it step by step, I'm not actually good with this kind of things. Do you think I have to toss the device in the trash bin? Thank you
Click to expand...
Click to collapse
I just want to add that I've altready tried to flash back to the original version, but how you can imagine...nothing to do...
Jack881 said:
I just want to add that I've altready tried to flash back to the original version, but how you can imagine...nothing to do...
Click to expand...
Click to collapse
You shouldn't have attempted to downgrade and/or flash another carriers rom. It's documented many places not to do this. Now you are in a pickle.
This will probably fix you up:
Download the FULL SBF of the ROM you want to flash. It must be the SAME VERSION, or HIGHER than the newest version you have flashed.
Boot into bootloader.
Type:
fastboot flash bootloader motoboot.img
fastboot flash partition gpt.bin
fastboot reboot-bootloader
Now you SHOULD be able to flash the ENTIRE SBF with RSD Lite or Manual method.
Explaination: By doing this, we are JUST flashing the bootloader and partition table (gpt.bin), THEN we reboot back to the bootloader in order to allow the bootloader to LOAD the new partition table before we flash the rest of the partitions.
It fixes people up most of the time, but not all. Good luck, hope it does the trick for you. Next time, heed the warning -- specifically not to downgrade. :good:
samwathegreat said:
You shouldn't have attempted to downgrade and/or flash another carriers rom. It's documented many places not to do this. Now you are in a pickle.
This will probably fix you up:
Download the FULL SBF of the ROM you want to flash. It must be the SAME VERSION, or HIGHER than the newest version you have flashed.
Boot into bootloader.
Type:
fastboot flash bootloader motoboot.img
fastboot flash partition gpt.bin
fastboot reboot-bootloader
Now you SHOULD be able to flash the ENTIRE SBF with RSD Lite or Manual method.
Explaination: By doing this, we are JUST flashing the bootloader and partition table (gpt.bin), THEN we reboot back to the bootloader in order to allow the bootloader to LOAD the new partition table before we flash the rest of the partitions.
It fixes people up most of the time, but not all. Good luck, hope it does the trick for you. Next time, heed the warning -- specifically not to downgrade. :good:
Click to expand...
Click to collapse
You are very kind, but I don't know if I can do it. I downloaded the firmware. But wheere I have to type the command? Sorry I'm really ignorant...
Jack881 said:
You are very kind, but I don't know if I can do it. I downloaded the firmware. But wheere I have to type the command? Sorry I'm really ignorant...
Click to expand...
Click to collapse
Get the latest android SDK from here: http://developer.android.com/sdk/index.html
Install it. It should have a folder called "Platform-tools" inside. Put gpt.bin and motoboot.img from the firmware inside this folder. Then open a command prompt, go to that folder, then run the commands as I outlined in the previous post.
After you "fastboot reboot-bootloader", try to flash the entire firmware zip file using RSD Lite.
I tried, but when I type the device still write Fastboot reason:flash failure. Any idea? Maybe I did something wrong. Thank you.
samwathegreat said:
You shouldn't have attempted to downgrade and/or flash another carriers rom. It's documented many places not to do this. Now you are in a pickle.
This will probably fix you up:
Download the FULL SBF of the ROM you want to flash. It must be the SAME VERSION, or HIGHER than the newest version you have flashed.
Boot into bootloader.
Type:
fastboot flash bootloader motoboot.img
fastboot flash partition gpt.bin
fastboot reboot-bootloader
Now you SHOULD be able to flash the ENTIRE SBF with RSD Lite or Manual method.
Explaination: By doing this, we are JUST flashing the bootloader and partition table (gpt.bin), THEN we reboot back to the bootloader in order to allow the bootloader to LOAD the new partition table before we flash the rest of the partitions.
It fixes people up most of the time, but not all. Good luck, hope it does the trick for you. Next time, heed the warning -- specifically not to downgrade. :good:
Click to expand...
Click to collapse
This is what it writes when I type the commands:
target reported max download size of 805306368 bytes
sending 'bootloader' (1604 KB)...
OKAY [ 0.346s]
writing 'bootloader'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.454s
C:\Users\Giacomo\Desktop\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>f
astboot flash partition gpt.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'partition' (32 KB)...
OKAY [ 0.261s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.146s
C:\Users\Giacomo\Desktop\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>f
astboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.010s
C:\Users\Giacomo\Desktop\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>
Can you help me? thank you.
Jack881 said:
This is what it writes when I type the commands:
target reported max download size of 805306368 bytes
sending 'bootloader' (1604 KB)...
OKAY [ 0.346s]
writing 'bootloader'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.454s
C:\Users\Giacomo\Desktop\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>f
astboot flash partition gpt.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'partition' (32 KB)...
OKAY [ 0.261s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.146s
C:\Users\Giacomo\Desktop\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>f
astboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.010s
C:\Users\Giacomo\Desktop\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>
Can you help me? thank you.
Click to expand...
Click to collapse
You noted that you flashed multiple ROMS. What is the LATEST VERSION of all the roms you tried to flash. You can never go lower, so please advise. Did you flash --any-- 4.4.2 or 4.4.4 ROM? If so, you MUST flash a new rom of the same or higher version.
samwathegreat said:
You noted that you flashed multiple ROMS. What is the LATEST VERSION of all the roms you tried to flash. You can never go lower, so please advise. Did you flash --any-- 4.4.2 or 4.4.4 ROM? If so, you MUST flash a new rom of the same or higher version.
Click to expand...
Click to collapse
I flashed a UK retail 4.4.2 and after a France retail 4.4.2...what should I flash now? I was trying your system on the Sprint 4.4 which was the original firmware of the telephone...
Jack881 said:
I flashed a UK retail 4.4.2 and after a France retail 4.4.2...what should I flash now? I was trying your system on the Sprint 4.4 which was the original firmware of the telephone...
Click to expand...
Click to collapse
That will absolutely not work. You are attempting to downgrade!!! (4.4.2 > 4.4) I already mentioned that you must use the same version or higher than the highest version you flashed previously. You MUST flash the Sprint 4.4.2 ROM, and not 4.4
If you try again, with the 4.4.2 Sprint SBF, you should be able to successfully recover.
Jack881 said:
I flashed a UK retail 4.4.2 and after a France retail 4.4.2...what should I flash now? I was trying your system on the Sprint 4.4 which was the original firmware of the telephone...
Click to expand...
Click to collapse
I also tried the 4.4.2 Sprint now, but same results. Do I have to get the file from the same firmware I flash, right? and when I flash do I have to flash without the getvar string?
Jack881 said:
I also tried the 4.4.2 Sprint now, but same results. Do I have to get the file from the same firmware I flash, right? and when I flash do I have to flash without the getvar string?
Click to expand...
Click to collapse
Please just use the manual method.
Do this:
First extract all the files in the SBF zip file (the 4.4.2 Sprint one!!!!!) to the same folder that includes fastboot & mfastboot (you do have the "mfastboot" binary, right?)
Now do this exactly: (ignore the fact that some of these commands are being run twice - this is intentional. Also notice that we are using "mfastboot" to flash system.img. If you don't have it, get it here [and put it in the same folder as fastboot]: https://docs.google.com/file/d/0B9qC3vvamytkSVp0NXhlSEhZVFU/edit )
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
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
If everything is successful to this point, now do:
fastboot reboot
If something fails, move on with the other commands. If you get stuck, let me know. Pictures of the errors will be helpful if you have any.
Taking timgree
samwathegreat said:
Please just use the manual method.
Do this:
First extract all the files in the SBF zip file (the 4.4.2 Sprint one!!!!!) to the same folder that includes fastboot & mfastboot (you do have the "mfastboot" binary, right?)
Now do this exactly: (ignore the fact that some of these commands are being run twice - this is intentional. Also notice that we are using "mfastboot" to flash system.img. If you don't have it, get it here [and put it in the same folder as fastboot]: https://docs.google.com/file/d/0B9qC3vvamytkSVp0NXhlSEhZVFU/edit )
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
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
If everything is successful to this point, now do:
fastboot reboot
If something fails, move on with the other commands. If you get stuck, let me know. Pictures of the errors will be helpful if you have any.
Click to expand...
Click to collapse
First of all I want to thank you, because I've never med anyone so kind online. Unfortunately I didn't succeed. I explain you exactly what I did:
1) I got from here http://sbf.droid-developers.org/phone.php?device=0 the Sprint 4.4.2 firmware (I had 4.4 originally, so this should be fine according to what you said)
2) I unzipped every file inside sdk/platform-tools
3) I downloaded your mfastboot (since I didn't have it) and stick it inside the same folder sdk/platform tools
4) So now I have this folder with inside all the files I thought you were asking to have there
5) at this point I opened from there the command prompt and started to type the commands you suggested
6) I had this:
C:\Users\Giacomo\Desktop\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>f
astboot partition gpt.bin
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, and if found,
recovery, tos
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
C:\Users\Giacomo\Desktop\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>f
astboot flash motoboot motoboot.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'motoboot' (1604 KB)...
OKAY [ 0.344s]
writing 'motoboot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.027s
C:\Users\Giacomo\Desktop\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>
I got stuck at the second command. Any idea? thank you.
Jack881 said:
First of all I want to thank you, because I've never med anyone so kind online. Unfortunately I didn't succeed. I explain you exactly what I did:
1) I got from here http://sbf.droid-developers.org/phone.php?device=0 the Sprint 4.4.2 firmware (I had 4.4 originally, so this should be fine according to what you said)
2) I unzipped every file inside sdk/platform-tools
3) I downloaded your mfastboot (since I didn't have it) and stick it inside the same folder sdk/platform tools
4) So now I have this folder with inside all the files I thought you were asking to have there
5) at this point I opened from there the command prompt and started to type the commands you suggested
6) I had this:
C:\Users\Giacomo\Desktop\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>f
astboot partition gpt.bin
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, and if found,
recovery, tos
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
C:\Users\Giacomo\Desktop\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>f
astboot flash motoboot motoboot.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'motoboot' (1604 KB)...
OKAY [ 0.344s]
writing 'motoboot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.027s
C:\Users\Giacomo\Desktop\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>
I got stuck at the second command. Any idea? thank you.
Click to expand...
Click to collapse
You also didn't correctly issue the first command. You left out "flash"
You typed "fastboot partition gpt.bin"
Instead of "fastboot flash partition gpt.bin"
Please start over. If it fails at motoboot.img -- don't worry. Just continue with the rest of the commands. If we can get everything else to flash, you may well recover. Sometimes it DOES fail at flashing motoboot, but just continue with the commands.
Be sure to type them EXACTLY as I've listed -- you can't leave off "flash" anymore
Please try and update as to status. If you can get to the very end, with nothing but motoboot.img failing, we should be able to recover you.
samwathegreat said:
You also didn't correctly issue the first command. You left out "flash"
You typed "fastboot partition gpt.bin"
Instead of "fastboot flash partition gpt.bin"
Please start over. If it fails at motoboot.img -- don't worry. Just continue with the rest of the commands. If we can get everything else to flash, you may well recover. Sometimes it DOES fail at flashing motoboot, but just continue with the commands.
Be sure to type them EXACTLY as I've listed -- you can't leave off "flash" anymore
Please try and update as to status. If you can get to the very end, with nothing but motoboot.img failing, we should be able to recover you.
Click to expand...
Click to collapse
Something moving...I repeated every single command, now I have on the phone Fastboot reason: Sticky bit factory_fastboot
What should I do now?
Thank you
Jack881 said:
Something moving...I repeated every single command, now I have on the phone Fastboot reason: Sticky bit factory_fastboot
What should I do now?
Thank you
Click to expand...
Click to collapse
Do this:
fastboot oem fb_mode_clear
fastboot reboot-bootloader
then start over with all the commands I previously listed
I recommend using copy / paste for all the commands just so none get messed up
samwathegreat said:
Do this:
fastboot oem fb_mode_clear
fastboot reboot-bootloader
then start over with all the commands I previously listed
I recommend using copy / paste for all the commands just so none get messed up
Click to expand...
Click to collapse
I did it: fastboot oem fb_mode_clear and fastboot reboot-bootloader and repeated all the commands, but now I have Partition (boot) Security version Downgraded. Fastboot reason: boot failure. Thank you
Jack881 said:
I did it: fastboot oem fb_mode_clear and fastboot reboot-bootloader and repeated all the commands, but now I have Partition (boot) Security version Downgraded. Fastboot reason: boot failure. Thank you
Click to expand...
Click to collapse
OK!
It looks like when you were on one of the other roms, you accepted an OTA to 4.4.3 or 4.4.4.....did this happen?
anyways, do this:
fastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
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
Does it boot?? Hopefully at this point, you boot into android. Fingers crossed.... :fingers-crossed:
samwathegreat said:
OK!
It looks like when you were on one of the other roms, you accepted an OTA to 4.4.3 or 4.4.4.....did this happen?
anyways, do this:
fastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
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
Does it boot?? Hopefully at this point, you boot into android. Fingers crossed.... :fingers-crossed:
Click to expand...
Click to collapse
No, gosh! maybe I have to repeat everything? now I have Partition (boot) Security version Downgraded Fastboot reason: Boot failure
Jack881 said:
No, gosh! maybe I have to repeat everything? now I have Partition (boot) Security version Downgraded Fastboot reason: Boot failure
Click to expand...
Click to collapse
I will have to continue helping you later tonight. Have to leave for a bit. I'm still hoping we will be able to recover you but it will take some more work, and we have to run the commands perfect. I'll post back here when I return.
I just want to update my Moto x 2014 to android 5.1, but i dont know how, i do have unlocked bootloader, and uninstalled my root.
I also cant find the correct file, and i would like some more in depth instructions on exactly how to upgrade, the standard installation wont work BTW.
My info of my phone:
Android Version: 5.0
System Version: 22.121.1.victara_reteu.reteuall.en.EU reteu
Build- Number: LXE22.46-19.1
If anyone needs more info just tell me.
i dont know what to type said:
I just want to update my Moto x 2014 to android 5.1, but i dont know how, i do have unlocked bootloader, and uninstalled my root.
I also cant find the correct file, and i would like some more in depth instructions on exactly how to upgrade, the standard installation wont work BTW.
My info of my phone:
Android Version: 5.0
System Version: 22.121.1.victara_reteu.reteuall.en.EU reteu
Build- Number: LXE22.46-19.1
If anyone needs more info just tell me.
Click to expand...
Click to collapse
The easiest method would be to flash this firmware:
http://www.filefactory.com/file/i8htlx8fqpv/VICTARA_RETEU_XT1092_5.1_LPE23.32-25.3_cid7_CFC.xml.zip
After flashing it you will be on the latest 5.1 firmware.
To flash it, you have to extract the files in the zip. Put the phone into fastboot mode. Then use fastboot to flash the files with these commands:
$ fastboot flash partition gpt.bin
$ fastboot flash motoboot motoboot.img
$ fastboot reboot-bootloader
$ 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 modem NON-HLOS.bin
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot erase userdata
$ fastboot erase cache
The last 2 commands erase your data on the phone. They are optional, but sometimes bugs and errors happen if you don't do it. So if you have any issues after flashing, those last 2 commands usually fix them. Personally I recommend erasing your data(make a backup of course) because you are less likely to have issues.
Sent from my XT1095 using Tapatalk
Hello, im having a similar situación on my Moto X 2014 Pure Edition XT1095_ in which i have a custom recovery installed and xposed obviously with the bootloader unlock and root. As i am told the ota for marschmallow will not be succesful beacause of a modified partition (system) how do i flash the ota? Thanks
nicokeini said:
Hello, im having a similar situación on my Moto X 2014 Pure Edition XT1095_ in which i have a custom recovery installed and xposed obviously with the bootloader unlock and root. As i am told the ota for marschmallow will not be succesful beacause of a modified partition (system) how do i flash the ota? Thanks
Click to expand...
Click to collapse
Same process that I just mentioned. But for the xt1095 use this firmware:
http://www.filefactory.com/file/5d66szhobgmx/VICTARA_TMO_XT1095_5.1_LPE23.32-21.6_cid9_CFC.xml.zip
Sent from my XT1095 using Tapatalk
AGISCI said:
The easiest method would be to flash this firmware:
After flashing it you will be on the latest 5.1 firmware.
To flash it, you have to extract the files in the zip. Put the phone into fastboot mode. Then use fastboot to flash the files with these commands:
$ fastboot flash partition gpt.bin
$ fastboot flash motoboot motoboot.img
$ fastboot reboot-bootloader
$ 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 modem NON-HLOS.bin
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot erase userdata
$ fastboot erase cache
The last 2 commands erase your data on the phone. They are optional, but sometimes bugs and errors happen if you don't do it. So if you have any issues after flashing, those last 2 commands usually fix them. Personally I recommend erasing your data(make a backup of course) because you are less likely to have issues.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Isnt there a faster download?
Hey, i have succesfully updated my moto X, but now i of course want to root it again, how do i do that, because i cant find the right file for my phone.
Marschmallow?
i dont know what to type said:
Hey, i have succesfully updated my moto X, but now i of course want to root it again, how do i do that, because i cant find the right file for my phone.
Click to expand...
Click to collapse
Just flash TWRP. Then start TWRP. When you exit TWRP it will ask if you want to root it. Very simple.
nicokeini said:
Marschmallow?
Click to expand...
Click to collapse
No, it has not been released yet. He upgraded to the latest lollipop.
Sent from my XT1095 using Tapatalk
Ok 6.0 is another story
I've been beating my head against a wall for 12 hours trying to get my device to get cell service again after unlocking the bootloader and installing RR. I've attempted manually re-installing the stock Metro firmware like 20 times, IMEIREPAIR.zip and everything in between. I've searched all over here and Google to little avail. I just got this phone yesterday and the store is 50 miles from my house. I saw little bits and pieces throughout the forums about this issue but no guide or real resolution. Can someone please help me so I can get back to using my phone? This is my only device and need it so my kids get get ahold of me. Thanks in advance!!!
elogikal said:
I've been beating my head against a wall for 12 hours trying to get my device to get cell service again after unlocking the bootloader and installing RR. I've attempted manually re-installing the stock Metro firmware like 20 times, IMEIREPAIR.zip and everything in between. I've searched all over here and Google to little avail. I just got this phone yesterday and the store is 50 miles from my house. I saw little bits and pieces throughout the forums about this issue but no guide or real resolution. Can someone please help me so I can get back to using my phone? This is my only device and need it so my kids get get ahold of me. Thanks in advance!!!
Click to expand...
Click to collapse
download this stock rom
https://mirrors.lolinet.com/firmwar...ubsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml.zip
the unzip it
open wordpad an copy an paste this code
@Echo off
:: Copyright 2012 The Android Open Source Project
::
:: Licensed under the Apache License, Version 2.0 (the "License");
:: you may not use this file except in compliance with the License.
:: You may obtain a copy of the License at
::
:: http://www.apache.org/licenses/LICENSE-2.0
::
:: Unless required by applicable law or agreed to in writing, software
:: distributed under the License is distributed on an "AS IS" BASIS,
:: WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
:: See the License for the specific language governing permissions and
:: limitations under the License.
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash dsp adspso.bin
fastboot flash bootloader bootloader.img
fastboot flash recovery recovery.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
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 erase DDR
fastboot erase cache
fastboot erase userdata
fastboot flash oem oem.img
fastboot flash vendor vendor.img
fastboot oem fb_mode_clear
pause
save it as restore.bat
drag an drop it in the extracted folder
reboot phone to bootloader
an click the restore.bat
wait till its done an you should be 100% stock
brandonlee96 said:
download this stock rom
https://mirrors.lolinet.com/firmwar...ubsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml.zip
the unzip it
open wordpad an copy an paste this code
@Echo off
:: Copyright 2012 The Android Open Source Project
::
:: Licensed under the Apache License, Version 2.0 (the "License");
:: you may not use this file except in compliance with the License.
:: You may obtain a copy of the License at
::
:: http://www.apache.org/licenses/LICENSE-2.0
::
:: Unless required by applicable law or agreed to in writing, software
:: distributed under the License is distributed on an "AS IS" BASIS,
:: WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
:: See the License for the specific language governing permissions and
:: limitations under the License.
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash dsp adspso.bin
fastboot flash bootloader bootloader.img
fastboot flash recovery recovery.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
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 erase DDR
fastboot erase cache
fastboot erase userdata
fastboot flash oem oem.img
fastboot flash vendor vendor.img
fastboot oem fb_mode_clear
pause
save it as restore.bat
drag an drop it in the extracted folder
reboot phone to bootloader
an click the restore.bat
wait till its done an you should be 100% stock
Click to expand...
Click to collapse
Alright. I'm downloading it now. I've ran all of these commands manually and was able to convert to absolute stock but still no SIM radio. Crossing my fingers. I'll keep you posted.
elogikal said:
Alright. I'm downloading it now. I've ran all of these commands manually and was able to convert to absolute stock but still no SIM radio. Crossing my fingers. I'll keep you posted.
Click to expand...
Click to collapse
DUDE!!! It worked! Thanks you a million times. I was getting so freaking aggrivated all day yesterday. Now, is there a guide or script you could provide me to get RR on there with GAPPS and NO root w/o running into encryption errors? Thanks! You're the best!
elogikal said:
DUDE!!! It worked! Thanks you a million times. I was getting so freaking aggrivated all day yesterday. Now, is there a guide or script you could provide me to get RR on there with GAPPS and NO root w/o running into encryption errors? Thanks! You're the best!
Click to expand...
Click to collapse
to fix encryption issues check my hannah and nora guide but it will be rooted
Hello,
I get always the same error for every thing I try to flash " cant write ...... ((no error))
The device have Android 9 stock firmware unsigned security update november 2018
And I try to install PAYTON_OPWS27.57_40_14_XT1900_7_DS_8.0.0_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml.zip
bootloader is open fastboot run,
Flashing works with this pc and OS normaly
since I try to flash my smartfone I have noch basband anymore.
I used this file
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 flash modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.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_b system_other.img
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
PAUSE
fastboot reboot
so you're trying to downgrade from pie to oreo. is the bootloader unlocked?
yes , but the first time I try to flash I forgot it , after that I unlocked the device and I try it again and I have the same error message
Flash just the bootloader "fastboot flash bootloader bootloader.img", then press volume-down multiple times until you see "Log". What is the output?
It might be related to these issues (thread 1, thread 2). Workarounds include using another PC or older version of fastboot.
I try it today , you mean the bootloader from Oreo right?
thanks for support
flashing bootloader was sucessful
here is the log:
cmd:getvar:slot-count
cmd:gevar:has-slot:bootloader
cmd:getvarartiton-type:bootloader
Cmd: getvar:maxdownload-size
cmd: download:0094c100
cmd: flash:bootloader
I try to flash all again it stop at dsp dspo.bin
the status change to official baseband is back but I stilll have android 9
tomtom_38 said:
I try to flash all again it stop at dsp dspo.bin
Click to expand...
Click to collapse
Try flashing again, this time one-by-one. Attach the bootloader log when it stops at dsp.
On the PC side, did flashing dsp resulted in "cant write ...... ((no error))" error. What are the command outputs?
C:\Users\Thomas\Desktop\minimal_adb_fastboot_1.4.3_portable_XT1900>fastboot flash dsp dspso.bin
target reported max download size of 536870912 bytes
sending 'dsp_a' (16384 KB)...
this happens by flashing dsp dspso
and this ist the log
flashing bootloader was sucessful
here is the log:
cmd:getvar:slot-count
cmd:getvar:slot-count
cmd: getvar:has slot:bluetooth
cmd: getvar:current-slot
cmd:getvarartition-type:bluetooth_a
cmd:getvar:max-download-size
cmd:download:0046f100
cmd:flash:bluetooth_a
cmd:getvar:slot-count
cmd:getvar:has-slot:dsp
cmd:getvar:current-slot
cmd:getvarartiton-type:dsp_a
cmd:getvar:max-download-size
cmd:download:01000000
Cmd: getvar:maxdownload-size
cmd: download:0094c100
cmd: flash:bootloader
this makes me perplex
Im erasing modem st1 but Iam not write everything
-------------------------------------------
C:\Users\Thomas\Desktop\minimal_adb_fastboot_1.4.3_portable_XT1900>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.016s]
finished. total time: 0.016s
------------------------------------------------------------------------------------------------------------------
C:\Users\Thomas\Desktop\minimal_adb_fastboot_1.4.3_portable_XT1900>fastboot flash modemst2
unknown partition 'modemst2'
error: cannot determine image filename for 'modemst2'
tomtom_38 said:
>fastboot flash modemst2
unknown partition 'modemst2'
error: cannot determine image filename for 'modemst2'
Click to expand...
Click to collapse
The script you got is incorrect. modemst2 should be erased instead.
I couldn't find the version you have from the mirror. I found another OPWS27.57 zip.
They're both "OPWS27.57" and Android 8.0, so the script should be similar.
If you want to make sure, inspect line 14 onward of the flashfile.xml. Check whether the zip has recovery.img as well.
Unzip the attached file. Put the attached flash_all.bat into the firmware folder and run it.
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
sleep 8
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.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_b system_other.img
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot-bootloader
sleep 8
ok, it worked with clean win 7 .
thanks, but
in no firmware is a recovery .img and I cant do an ota update to pie.
tomtom_38 said:
in no firmware is a recovery .img and I cant do an ota update to pie.
Click to expand...
Click to collapse
If you did "fastboot flash boot boot.img", the stock recovery should be there.
munchy_cool said:
flash stock boot.img.
recovery is built within boot.img.
Click to expand...
Click to collapse
-------------------
Try this guide. But I'm puzzled why you downgrade to Oreo and back to Pie.
btw, "bootloader is open fastboot run" is mentioned in the OP, is the bootloader unlocked?
I will try it,
I do it because I need a official signed version to send my smartpfone to a repair center.
the best sigened version I found is oreo and I downgrade to oreo and upgtade with motrola update services to pie
hey I flashed slot a and b with the same firmware but the message "you loading a different os" still apear.
The bootloader show that the firmware is a official version?! I looking for a solution but I found only the way tto flash both slots
What commands did you use to flash to both slots?
They should be:
fastboot --set-active=a
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_b system_other.img
Ok I use this comand to change the slot
fastboot --set-active=other
and then I flash manually all positions from the flash _all .zip from the first page
one time for each slot
tomtom_38 said:
hey I flashed slot a and b with the same firmware but the message "you loading a different os" still apear.
Click to expand...
Click to collapse
Does it look like this?
tomtom_38 said:
The bootloader show that the firmware is a official version
Click to expand...
Click to collapse
I'm using Havoc and it also shows as "official".
tomtom_38 said:
fastboot --set-active=other
Click to expand...
Click to collapse
you mean "fastboot --set-active=b"?