Database Develop

Bricked Bootloader

Hey guys,
slowly I really get in trouble. I think the bootloader is bricked and i can use the phone as a door stopper.
I tell you what happens:
Long time ago i decided to root my phone. so I unlocked it via htcdev.com. After success I wanted to S-Off the bootloader with revone. But it failed, because of hboot 1.54.
Then I installed ARHD via TWRP and flashed boot.img via fastboot.
Long time every thing went fine, until yesterday it stoped to work and started bootloops. I managed to start the bootloader but nothing else. No ROM, no recovery (stucks on first twrp screen).
bootloader info says:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 24Ð161Ð╬
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH34PW905197
(bootloader) imei: XXXXXXXXXXX7434 --> deleted just in this thread
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3794mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.043s
Link to photo of the bootloader
What i tried until now (without any results):
"fastboot erase cache" to get access to recovery
"fastboot oem reboot RUU" to install a new hboot --> boots to white "quietly brilliant" screen, reboots then to bootloader
It would be great if someone can help me or can give me some tipps to unbrick this phone.
Thanks to all helpers.
Greetings Bulaktos

What RUU did you flash? Seeing as you're S-off you need to be extremely careful with RUUs and you might have flashed the wrong one, if you've flashed a downgrade then your device is bricked.

I didn't flashed any ruu. I only flashed the recovery and the boot.img for Arhd.
Until now I didn't flashed any firmware.
Sent from my Nexus 4 using xda app-developers app

Bulkatos said:
I didn't flashed any ruu. I only flashed the recovery and the boot.img for Arhd.
Until now I didn't flashed any firmware.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
We dont flash boot.img anymore the bootloader 1.54 does not will the command fastboot flash boot.img. flash ARHD again

Bulkatos said:
Hey guys,
slowly I really get in trouble. I think the bootloader is bricked and i can use the phone as a door stopper.
I tell you what happens:
Long time ago i decided to root my phone. so I unlocked it via htcdev.com. After success I wanted to S-Off the bootloader with revone. But it failed, because of hboot 1.54.
Then I installed ARHD via TWRP and flashed boot.img via fastboot.
Long time every thing went fine, until yesterday it stoped to work and started bootloops. I managed to start the bootloader but nothing else. No ROM, no recovery (stucks on first twrp screen).
bootloader info says:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 24Ð161Ð╬
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH34PW905197
(bootloader) imei: XXXXXXXXXXX7434 --> deleted just in this thread
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3794mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.043s
Link to photo of the bootloader
What i tried until now (without any results):
"fastboot erase cache" to get access to recovery
"fastboot oem reboot RUU" to install a new hboot --> boots to white "quietly brilliant" screen, reboots then to bootloader
It would be great if someone can help me or can give me some tipps to unbrick this phone.
Thanks to all helpers.
Greetings Bulaktos
Click to expand...
Click to collapse
Just
fastboot erase cache
fastboot flash recoveryname.zip
fastboot reboot-bootloader
Select recovery
Flash any rom
Sent from my iPod touch using Tapatalk

@n1234d
Thats all? I will gave it a try, when I have time. What about the bootloader? It seems to me that it is broken on a strange way.
Can I repair it on any way?
Sent from my Nexus 4 using xda app-developers app

Bulkatos said:
@n1234d
Thats all? I will gave it a try, when I have time. What about the bootloader? It seems to me that it is broken on a strange way.
Can I repair it on any way?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Your bootloader is absolutely fine, it's just your recovery/rom. Just reflash both and you'll be good to go.

n1234d said:
Your bootloader is absolutely fine, it's just your recovery/rom. Just reflash both and you'll be good to go.
Click to expand...
Click to collapse
Okay, sounds good.
Another question:
I've read that I need the hboot 1.55 for Android 4.3, and Arhd 30 is based on 4.3. So I have to update the bootloader anyway?
Sent from my Nexus 4 using xda app-developers app

Bulkatos said:
Okay, sounds good.
Another question:
I've read that I need the hboot 1.55 for Android 4.3, and Arhd 30 is based on 4.3. So I have to update the bootloader anyway?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Nope, you don't *need* 1.55 for a 4.3 rom, you'll be good with 1.54. If you OTA or RUU, it'll update automatically.
Sent from my iPod touch using Tapatalk

mh, seems more difficult to be.
fastboot erase cache -> says okay
fastboot flash recovery cwm.img -> says "okay"
fastboot reboot-bootloader -> reboots phone to white HTC bootscreen, then I reboot to hboot manually and choose recovery. twrps want to boot (but freeze)
It seems to me, that the command to flash the recovery didn't worked very well. What can I still do?

Bulkatos said:
mh, seems more difficult to be.
fastboot erase cache -> says okay
fastboot flash recovery cwm.img -> says "okay"
fastboot reboot-bootloader -> reboots phone to white HTC bootscreen, then I reboot to hboot manually and choose recovery. twrps want to boot (but freeze)
It seems to me, that the command to flash the recovery didn't worked very well. What can I still do?
Click to expand...
Click to collapse
try flashing the latest TWRP recovery. It can be found somewhere around here....
You can always try just restoring via RUU too, you just need to be in fastboot mode in order for it to work.

chenchen399 said:
try flashing the latest TWRP recovery. It can be found somewhere around here....
You can always try just restoring via RUU too, you just need to be in fastboot mode in order for it to work.
Click to expand...
Click to collapse
I did so. same results.
Fastboot reboot-bootloader -> reboots phone normal
fastboot flash recovery twrp.img -> twrp won't start

Try re flashing the hboot then, but you have to be s-off to do this. The only other way I can think of is RUU

Bulkatos said:
I did so. same results.
Fastboot reboot-bootloader -> reboots phone normal
fastboot flash recovery twrp.img -> twrp won't start
Click to expand...
Click to collapse
move the twrp.img file on adb folder.. and try again

Bulkatos said:
I did so. same results.
Fastboot reboot-bootloader -> reboots phone normal
fastboot flash recovery twrp.img -> twrp won't start
Click to expand...
Click to collapse
try this version of cwm it's a non touch version
https://www.dropbox.com/s/kbrzunsw0c17cyw/cwmclassic.zip

Slim Shady said:
try this version of cwm it's a non touch version
https://www.dropbox.com/s/kbrzunsw0c17cyw/cwmclassic.zip
Click to expand...
Click to collapse
how to flash a zip in fastboot? flashing the img-file via "fastboot flash recovery name.img" don't work (like all other commands).

Bulkatos said:
how to flash a zip in fastboot? flashing the img-file via "fastboot flash recovery name.img" don't work (like all other commands).
Click to expand...
Click to collapse
ur experiencing problems so try these two methods:
1.) Extract the zip and flash the recovery the usual way
fastboot erase cache
fastboot flash recovery recoveryname.img
fastboot reboot-bootloader
2.) open the zip file and edit the android text file in accordance to ur mid cid and mainver save and save it.You will need stock recovery for this method if dont have it here is the link https://www.dropbox.com/s/wq2t9fctnn9186j/stockrecovery.img
to flash stock recovery follow the steps in method 1 then follow the steps given below :
fastboot erase cache
fastboot reboot oemRUU
fastboot flash zip zipfilename.zip
then it will fail once
again the same command
fastboot flash zip zipfilename.zip
when it shows it is finished in cmd type
fastboot reboot-bootloader
either of them should lead to a working recovery

Bulkatos said:
how to flash a zip in fastboot? flashing the img-file via "fastboot flash recovery name.img" don't work (like all other commands).
Click to expand...
Click to collapse
yep:
fastboot flash recovery <name of recovery>.img
fastboot erase cache <- if you dont do this after flashing a recovery, it will most like either freeze or reboot without entering recovery
fastboot reboot-bootloader
-> enter RECOVERY
BTW: I took a look at the screenshot, does it really say in red text OS-2.24X161XX (!RR!XXXX) ??
---------- Post added at 01:56 PM ---------- Previous post was at 01:52 PM ----------
Slim Shady said:
2.) open the zip file and edit the android text file in accordance to ur mid cid and mainver
fastboot erase cache
fastboot reboot oemRUU
fastboot flash zip zipfilename.zip
when it shows it is finished in cmd type
fastboot reboot-bootloader
either of them should lead to a working recovery
Click to expand...
Click to collapse
He has S-ON so careful flashing firmware! It has to be signed and it's a one way ticket with S-On, no downgrade possible. And remember "fastboot flash zip zipfilename.zip" usually has to be done twice (the first one usually fails and says "FAILED flush again immediately" the second time it should show success)

nkk71 said:
yep:
fastboot flash recovery <name of recovery>.img
fastboot erase cache <- if you dont do this after flashing a recovery, it will most like either freeze or reboot without entering recovery
fastboot reboot-bootloader
-> enter RECOVERY
BTW: I took a look at the screenshot, does it really say in red text OS-2.24X161XX (!RR!XXXX) ??
---------- Post added at 01:56 PM ---------- Previous post was at 01:52 PM ----------
He has S-ON so careful flashing firmware! It has to be signed and it's a one way ticket with S-On, no downgrade possible. And remember "fastboot flash zip zipfilename.zip" usually has to be done twice (the first one usually fails and says "FAILED flush again immediately" the second time it should show success)
Click to expand...
Click to collapse
thanks for pointing it out actually forgot to mention it again and he is s-on that's why the second method cause that usually works.

Slim Shady said:
thanks for pointing it out actually forgot to mention it again and he is s-on that's why the second method cause that usually works.
Click to expand...
Click to collapse
you mean "edit the android text file in accordance to ur mid cid and mainver save and save it"? He can give it a try but I don't think it will work, as soon as he edits the android.txt file, the firmware.zip will become unsigned, and won't pass with S-On.

Stuck in boot loop.

I have tried to flash the ROM on my M7 with no luck. Just getting a boot. I have used a mates computer and didn't noticed his copy of Hasoons was for the M8 when I changed from TWRP to ClockWorkMod and now I can't get into recovery mode. That's a new problem. The old one is not being able to successfully flash the ROM.
***TAMPERED***
***UNLOCKED***
M7 UL PVT SHIP S-ON RH
HBOOT-1.61.000
OS-7.19.771.21
eMMC-boot 2048MB
adb devises doesn't show up anything anymore but the unit is recognized by Windows.
Thanks in advance. Any help or ideas would be much appreciated.

Out of Boot Loop
OK, I'm out of the boot loop now and just struggling to image the ROM, if nothing I install will not work and I manage to re-install the RUU, is that going to be all I can install?

humback said:
OK, I'm out of the boot loop now and just struggling to image the ROM, if nothing I install will not work and I manage to re-install the RUU, is that going to be all I can install?
Click to expand...
Click to collapse
What rom (name + version) are you trying to flash?
What recovery (name + version) are you using?
What is you "fastboot getvar all" ? (don't post imei / serialno)

alray said:
What rom (name + version) are you trying to flash?
What recovery (name + version) are you using?
What is you "fastboot getvar all" ? (don't post imei / serialno)
Click to expand...
Click to collapse
Hi thanks for your reply:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.771.21
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *************
(bootloader) imei: ***************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: H3G__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4158mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

humback said:
Hi thanks for your reply:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.771.21
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *************
(bootloader) imei: ***************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: H3G__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4158mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Since you only answered 1 of the 3 questions asked, the only thing I can suggest you is to relock your bootloader and flash the 7.19.771.21 RUU http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944

alray said:
Since you only answered 1 of the 3 questions asked, the only thing I can suggest you is to relock your bootloader and flash the 7.19.771.21 RUU http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
Click to expand...
Click to collapse
Sorry I didn't relise you asked the other questions, I have been using Hasoon2000 v3.1 and tried both CWM and TWRP. Also multiple ROMS including the reccomended stock one for the preivious carrier for HTCdev and a couple of the latest versions of kitkat and lollipop from this site.
Thanks.

humback said:
Sorry I didn't relise you asked the other questions, I have been using Hasoon2000 v3.1 and tried both CWM and TWRP. Also multiple ROMS including the reccomended stock one for the preivious carrier for HTCdev and a couple of the latest versions of kitkat and lollipop from this site.
Thanks.
Click to expand...
Click to collapse
I would suggest you to avoid using toolkits and instead work directly from a command window using the latest android sdk tools (fastboot and adb). Files that comes with these toolkits, like Hasoon 2000, are outdated.
E.g:
Hasoon 2000 v 3.1
Outdated SU binaries (1.45). Latest is 2.46 and is mandatory for lollipop roms.
Outdated TWRP recovery (2.6.0.1) - Latest twrp recovery for the M7 is 2.8.7.0, all roms requires at least 2.6.3.3, some other like Cyanogenmod requires at lest 2.7.1.1
Outdated CWM recovery (6.0.3.4) - latest cwm for M7 is 6.0.4.8
So setup your android sdk tool folder, download your custom recovery directly from TWRP or CWM website (twrp is preferred for the M7), flash the recovery using fastboot, copy the om to your phone and flash it in recovery.
humback said:
I bought this HTC last Saturday and it was on the 3 network with their software. I am on EE, my intention was to re-image the device with a non branded version O/S and get it unlocked to any network.
Click to expand...
Click to collapse
You need to be on the stock rom to sim unlock the phone so better to relock the bootloader, flash the ruu, unlock the sim using a sim unlock code, unlock the bootloader again and flash the rom you want to use.

alray said:
I would suggest you to avoid using toolkits and instead work directly from a command window using the latest android sdk tools (fastboot and adb). Files that comes with these toolkits, like Hasoon 2000, are outdated.
E.g:
Hasoon 2000 v 3.1
Outdated SU binaries (1.45). Latest is 2.46 and is mandatory for lollipop roms.
Outdated TWRP recovery (2.6.0.1) - Latest twrp recovery for the M7 is 2.8.7.0, all roms requires at least 2.6.3.3, some other like Cyanogenmod requires at lest 2.7.1.1
Outdated CWM recovery (6.0.3.4) - latest cwm for M7 is 6.0.4.8
So setup your android sdk tool folder, download your custom recovery directly from TWRP or CWM website (twrp is preferred for the M7), flash the recovery using fastboot, copy the om to your phone and flash it in recovery.
You need to be on the stock rom to sim unlock the phone so better to relock the bootloader, flash the ruu, unlock the sim using a sim unlock code, unlock the bootloader again and flash the rom you want to use.
Click to expand...
Click to collapse
So I need to use the stock, unlock the sim and then go back and use whatever ROM. That sounds good. Do you know where I could find the command I'm going to need and any examples. So far I only know how to use the all in one tools to move files.

humback said:
So I need to use the stock, unlock the sim and then go back and use whatever ROM. That sounds good. Do you know where I could find the command I'm going to need and any examples. So far I only know how to use the all in one tools to move files.
Click to expand...
Click to collapse
You can find the instructions how to flash the ruu in the link above but here it hus tin case:
lock the bootloader:
Code:
fastboot oem lock
flash the ruu:
Code:
htc_fastboot oem rebootRUU
htc_fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_H3G_UK_7.19.771.21_Radio_4T.35.3218.16_10.33Q.1718.01L_release_430335_signed.zip
htc_fastboot reboot
Then boot the phone and inter your sim unlock code when prompted to after that the sim unlock will be permanent whatever rom you flash.
unlock the bootloader again (instructions at htcdev.com/bootloader):
Code:
fastboot oem get_identifier_token
fastboot flash unlocktoken Unlock_code.bin
then flash the custom recovery:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
Then copy your rom to your phone storage and install it with your recovery.
Don't forget all files you want to flash (RUU, Recovery, Unlock_code) must be saved in the same folder you have adb, fastboot and htc_fastboot installed on your computer.

alray said:
You can find the instructions how to flash the ruu in the link above but here it hus tin case:
lock the bootloader:
Code:
fastboot oem lock
flash the ruu:
Code:
htc_fastboot oem rebootRUU
htc_fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_H3G_UK_7.19.771.21_Radio_4T.35.3218.16_10.33Q.1718.01L_release_430335_signed.zip
htc_fastboot reboot
Then boot the phone and inter your sim unlock code when prompted to after that the sim unlock will be permanent whatever rom you flash.
unlock the bootloader again (instructions at htcdev.com/bootloader):
Code:
fastboot oem get_identifier_token
fastboot flash unlocktoken Unlock_code.bin
then flash the custom recovery:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
Then copy your rom to your phone storage and install it with your recovery.
Don't forget all files you want to flash (RUU, Recovery, Unlock_code) must be saved in the same folder you have adb, fastboot and htc_fastboot installed on your computer.
Click to expand...
Click to collapse
I'm up to the flash zip and getting a error FAILED (remote 02 data lenth is to large) I took this file from the link above 1.6GB

humback said:
I'm up to the flash zip and getting a error FAILED (remote 02 data lenth is to large) I took this file from the link above 1.6GB
Click to expand...
Click to collapse
Are you using the fastboot version linked in the same thread from where you have downloaded the ruu? You must use that version of fastboot, the normal one that comes with the sdk tools can't handle big file like this ruu.

alray said:
Are you using the fastboot version linked in the same thread from where you have downloaded the ruu? You must use that version of fastboot, the normal one that comes with the sdk tools can't handle big file like this ruu.
Click to expand...
Click to collapse
No, I'll re download it when I get home, do I just replace that version in my folder with the other files as an exe?

humback said:
No, I'll re download it when I get home, do I just replace that version in my folder with the other files as an exe?
Click to expand...
Click to collapse
keep both fastboot version, save that one in the same folder as the original fastboot but name it htc_fastboot.exe so you have both fastboot version. When needed, type "htc_fastboot your_command" instead of "fastboot your_command" like when flashing the ruu:
Code:
fastboot oem rebootRUU
htc_fastboot flash zip ruu_file_name.zip
fastboot reboot

alray said:
keep both fastboot version, save that one in the same folder as the original fastboot but name it htc_fastboot.exe so you have both fastboot version. When needed, type "htc_fastboot your_command" instead of "fastboot your_command" like when flashing the ruu:
Code:
fastboot oem rebootRUU
htc_fastboot flash zip ruu_file_name.zip
fastboot reboot
Click to expand...
Click to collapse
Thanks alray, I'm back on stock. Just going to unlock the sim and reload a custom rom.

alray said:
keep both fastboot version, save that one in the same folder as the original fastboot but name it htc_fastboot.exe so you have both fastboot version. When needed, type "htc_fastboot your_command" instead of "fastboot your_command" like when flashing the ruu:
Code:
fastboot oem rebootRUU
htc_fastboot flash zip ruu_file_name.zip
fastboot reboot
Click to expand...
Click to collapse
All done, I got the phone unlocked for a couple of pounds on Ebay, and managed to install the RUU you suggested. Managed to update to a custom ROM today and everything is good. I did try to re-lock the bootloader and ran into another loop, so left it open for now with tampered and security warning for now. Apart from that it's all working fine. Thanks again for your help Alray.

Motorola Moto G (XT1068) - Softbricked?

Hi.
I have black screen after motorola moto g animation (I can see some light, but blank screen).
I can enter on fastboot mode and have the bootloader unlocked. . I tried to reflash the firmware but i have still the same error.
I tried to downgrade from 5.0.2 to 4.4.4 but I can't do it, it displays this error:
"C:\A>mfastboot.exe flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.160s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.472s"
I tried a lot of procedures searching my problem in google, but noone works.
Maybe is a wrong firmware image? can you help me with the correct image or solving the issue?
I'm desperate and need a solution, here you can see some information:
"C:\A>mfastboot.exe getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 4882(*)
(bootloader) product: titan
(bootloader) secure: yes
(bootloader) hwrev: 0x8400
(bootloader) radio: 0x5
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Hynix S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: ZX1D22PPCL
(bootloader) cid: 0x0007
(bootloader) channelid: 0x40
(bootloader) uid: C26F6D070F000000000000000000
(bootloader) securestate: unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: XXXXXXXXXXX
(bootloader) meid:
(bootloader) date: 12-13-2014
(bootloader) sku: XT1068
(bootloader) battid: (null)
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Jul 14 15:45:22 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/titan_retaildsds/titan_um
(bootloader) ro.build.fingerprint[1]: tsds:5.0.2/LXB22.46-28/28:user/rel
(bootloader) ro.build.fingerprint[2]: ease-keys
(bootloader) ro.build.version.full[0]: Blur_Version.22.21.28.titan_retai
(bootloader) ro.build.version.full[1]: ldsds.retaildsdsall.en.03
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-g48d3b85 ([email protected]
(bootloader) kernel.version[1]: ilclbld54) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Tue Jan 6 10:38:33 CST 2015
(bootloader) sdi.git: git=MBM-NG-V48.82-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V48.82-0-g7e74e90
(bootloader) rpm.git: git=MBM-NG-V48.82-0-g20516c3-dirty
(bootloader) tz.git: git=MBM-NG-V48.82-0-g72f9f12
(bootloader) aboot.git: git=MBM-NG-V48.82-0-ge004609
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 0/0
(bootloader) productid: ZX1D22PPCL
(bootloader) sutinfo:
(bootloader) ro.carrier: reteu
all: listed above
finished. total time: 0.101s"
Very thanks guys. :crying:

If you are trying to downgrade from 5.x/6.x to 4.4, remember you do not flash .mbn file. Flashing .mbn will attempt to downgrade your bootloader and might corrupt it, as bootloader downgrade is not supported/advised. I suggest you flash 5.x stock firmware WITH .mbn file and this should solve your problem.
Try firmware from this thread:
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-original-motorola-t3155774

just try to flash a recovery like twrp then install cm like rom first

pank.dhnd said:
If you are trying to downgrade from 5.x/6.x to 4.4, remember you do not flash .mbn file. Flashing .mbn will attempt to downgrade your bootloader and might corrupt it, as bootloader downgrade is not supported/advised. I suggest you flash 5.x stock firmware WITH .mbn file and this should solve your problem.
Try firmware from this thread:
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-original-motorola-t3155774
Click to expand...
Click to collapse
What image should I use for XT1068 Europe Dual Sim ??? in relation with the fastboot vars?

When i Install twrp it won't display errors, but when i access to recovery it access to the stock recovery :/
If I manually boot from twrp whitout flashing it, i get stuck on "teamwin" logo.
vaisakmct said:
just try to flash a recovery like twrp then install cm like rom first
Click to expand...
Click to collapse

lsard said:
When i Install twrp it won't display errors, but when i access to recovery it access to the stock recovery :/
If I manually boot from twrp whitout flashing it, i get stuck on "teamwin" logo.
Click to expand...
Click to collapse
That's what I am saying, flash stock Lollipop, it will restore your bootloader and recovery (if any changes were made during downgrade), and then flash recovery.
---------- Post added at 05:46 AM ---------- Previous post was at 05:37 AM ----------
lsard said:
What image should I use for XT1068 Europe Dual Sim ??? in relation with the fastboot vars?
Click to expand...
Click to collapse
Ohh, for Europe dual sim, you can use image from below thread:
http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-5-0-2-lxb22-46-t3019612
The thread I posted earlier has Indian images mostly, but it won't make much difference.

pank.dhnd said:
That's what I am saying, flash stock Lollipop, it will restore your bootloader and recovery (if any changes were made during downgrade), and then flash recovery.
---------- Post added at 05:46 AM ---------- Previous post was at 05:37 AM ----------
Ohh, for Europe dual sim, you can use image from below thread:
http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-5-0-2-lxb22-46-t3019612
The thread I posted earlier has Indian images mostly, but it won't make much difference.
Click to expand...
Click to collapse
Still the same error, blank screen after motorola animation, reflashing this firmware -> ***NEW*** DOWNLOAD XT1068 5.0.2 LXB22.99-16.3 RETDSDS WITH STAGE FRIGHT FIX RETAIL DUAL SIM DUAL STANDBY (EU/INDIAN/GLOBAL) 26/08/2015 BUILD ***NEW***

Nobody can help me?
Do you think my phone is not recoverable?
:crying:

lsard said:
Nobody can help me?
Do you think my phone is not recoverable?
:crying:
Click to expand...
Click to collapse
Did u try any custom ROM?
And don't worry, your phone boots perfectly that means no issue with it.

pank.dhnd said:
Did u try any custom ROM?
And don't worry, your phone boots perfectly that means no issue with it.
Click to expand...
Click to collapse
I can't install any ROM, I tried to install cm rom by adb but it fails at the installation process. Can't install neither any recovery.
I think is a blocked partition or something like this.

Please help me solving this.... nobody know why I can't install any rom/recovery?

lsard said:
Please help me solving this.... nobody know why I can't install any rom/recovery?
Click to expand...
Click to collapse
You can try to boot into twrp, you have to use the 2.8.5.0 version, newer ones will fail.
Sent from my Moto G 2014 using XDA Free mobile app

Wolfcity said:
You can try to boot into twrp, you have to use the 2.8.5.0 version, newer ones will fail.
Sent from my Moto G 2014 using XDA Free mobile app
Click to expand...
Click to collapse
Hi Wolfcity, thanks for your support.
I installed twrp 2.8.5.0 version as you told me. I'm still with the same problem. When I installer the twrp recovery it will boot from stock recovery. If I manually boot from trwp it will stuck on the Teawin logo.
I installed this iso -> https://dl.twrp.me/titan/twrp-2.8.5.0-titan.img
I'm desperate

You say your bootloader is possibly corrupt, that would be a result of a bad mbn flash in your phones bootloader. Explain to me exactly how you performed the .mbn flashing process so I may formulate a solution. Thanks

GhettoButta said:
You say your bootloader is possibly corrupt, that would be a result of a bad mbn flash in your phones bootloader. Explain to me exactly how you performed the .mbn flashing process so I may formulate a solution. Thanks
Click to expand...
Click to collapse
I tried various processes searching by google, but the last i think was following this thread:
http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-t3018682
Thanks you so much, I can post you all the fastboot vars if you need.

You say your bootloader is possibly corrupt, that would be a result of a bad mbn flash in your phones bootloader. Explain to me exactly how you performed the .mbn flashing process so I may formulate a solution. Thanks
EDIT: Also list your previous motoboot.img version you used for the flashing process.
Tell me your carrier?

http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-5-0-2-lxb22-46-t3019612
go here may be this post will help you for your issue .

GhettoButta said:
You say your bootloader is possibly corrupt, that would be a result of a bad mbn flash in your phones bootloader. Explain to me exactly how you performed the .mbn flashing process so I may formulate a solution. Thanks
EDIT: Also list your previous motoboot.img version you used for the flashing process.
Tell me your carrier?
Click to expand...
Click to collapse
I tried so many proceduress..
I used this posts:
- http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-t3018682
- http://forum.xda-developers.com/moto-g-2014/development/rom-stock-lollipop-rom-t3024800
- http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
Maybe is not the order... i tried like 4 or 5 reflash to stock but nothing changes, i'm getting the exact same error.
Thanks

Can't believe it can't be solved!!
I have a great commitment with this smartphone

go to service center dont mention about ur bootloader unlocked just told them u face this screen at the time of update .dont touch anything else just submit your handset

Updated Back 2 Stock procedure for Motorola G5S+ (Sanders)

There's a really good thread currently in this forum that has the basics for going back to stock ROM, but recently more and more people have followed it WITHOUT reading through all 60+ pages (Don't blame them) and end up with a phone that is not working properly.
This thread aims to provide the most up-to-date stock ROM links, the most current way of restoring your stock ROM, and also clear up some misconceptions about what is required for OTA compatiblity, etc.
First, a few misconceptions:
Q: Do I need to have a locked bootloader in order to get OTAs?
A: NO! You just need a fully stock system image, recovery image, bootloader image, logo.bin, and OEM partition. This means you can have your bootloader unlocked and still take OTAs. The OTA script doesn't check for that, and the OTA tool built into the phone does not check either. HOWEVER, you do need to have matching firmware, bootloader, etc to whatever version you are currently running. If you flashed a custom ROM when you were running June 1 2018 security patch, but then restore back to stock using December 1 2017 security patch, you won't get OTAs via the phone. (You can use the offline OTA download tool to sideload them just fine however)
Q: I can just flash whatever firmware I find as long as the numbers are bigger than what is currently on there, right?
A: NO! This is what a lot of people in the other thread are doing and it's screwing up phones! This thread is here to help clear up that confusion! You MUST flash the correct region for your firmware. There are FOUR kinds of Moto G5S+. All have their own model number and region. Mine is an XT1806 RETUS device. It was sold in the United States. You may have a RETIN, RETLA, RETEU, RETID or some other variant. Flashing RETIN firmware on a RETUS device will mean you won't get OTA updates. Same with flashing RETUS firmware on a RETEU device. It won't even take sideloaded OTAs since your device doesn't match anything Motorola\Lenovo ever sold.
Q: I made a backup of my device with TWRP before rooting, I'm good, right?
A: maybe. I've found that all current versions of TWRP (R20, R22, Treble-Test) do not back up the OEM partition properly. I haven't tried all the builds so far, but all the ones I've tried mount OEM as R\W which breaks OTA, even after a restore via TWRP. (The R22 seems to touch it no matter what on booting TWRP so you'll need to reflash it via Fastboot from a stock image file in order to take OTAs, or use R20 which didn't touch it unless you tried to restore a backup)
Q: I skipped all the above and flashed wrong firmware from the links below, locked my bootloader, and now nothing works.
A: Don't skip the notes next time. See if you can get an unlock code and try again.
Q: I don't know what kind of phone I have?
A: Put the device in fastboot mode (Can either do ADB reboot bootloader, or hold the Volume Down button while turning it on) and on a computer with ADB and Fastboot installed type
Code:
fastboot devices
If you get an output that matches the serial of your phone, type
Code:
fastboot getvar all
Copy that, paste it into a .txt file and upload it here, share it to pastebin, post it here in the CODE tags, just share it so we can see what version your device is and point you in the right direction. Better to do it once than twice, right? It's suggested you read through it and remove your devices IMEI (and serial number if you'd like) for security reasons. I've yet to see anything practical happen to publicly posted IMEI numbers but you never know.
Right, now for the meat of the tutorial.
1: BACKUP YOUR ENTIRE DEVICE USING TWRP. Save that backup. If you don't care about your data, don't back that up, but back up everything. You'll need to back up to something that supports larger than 4GB files (So not FAT32, I believe TWRP supports NTFS, internal storage works too if you've got ~12gb free, USB OTG works). It's best to do this just in case something goes crazy wrong you still have a backup. If you don't backup and then something goes wrong, it's not my fault.
2: Grab the latest firmware for your device so that you know for a fact that it's updating ALL bits of the device. As of this writing (September 4th, 2018) it is June 1 2018 security patch. The links below have the firmware for the 4 major regions: RETEU, RETIN, RETBR, and RETUS
FOR RETEU, RETIN, RETBR, use this link.
For RETUS, use this link.
Once newer full firmware files are available, I will update links accordingly.
3: Install Minimal ADB & Fastboot. This is required to run the fastboot getvar all command, and is required to flash stock firmware.
4: Extract the stock firmware .zip file into the ADB & fastboot directory for ease of use.
5: Run these commands: PLEASE NOTE RUNNING THESE COMMANDS WILL WIPE ALL YOUR DATA FROM YOUR DEVICE. Backup EVERYTHING. Even your pictures & whatnot. Remove your SD card if you're super worried. This will return the device to a completely factory reset device. No pictures, no SMS messages, nothing survives this. Please understand this. If you're running modded stock and want to keep your data, omit the fastboot erase userdata line. these commands will NOT wipe your modem. You will still have an IMEI after. you'll need to follow the tutorial on making sure your persist is intact to get VOLTE working and other issues fixed with your persist & IMEI should you notice issues after flashing.
Code:
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 flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Let your device boot. enjoy the obxnoious Lenovo boot splash they created just to terrify you in the middle of the night when your phone reboots for no reason. If it all went well, your device should reboot to a stock Android 7.1.1 June 1 2018 build.
If you have issues, please share them so we can make sure nobody else gets stuck on the wrong firmware with bad information.

Im on june security patch, iwant to use soak test but my phone cant get the notification update after flash back to april security patch, and a failed flash of bootloader..
Sorry for my bad english.

jeffrey017 said:
Im on june security patch, iwant to use soak test but my phone cant get the notification update after flash back to april security patch, and a failed flash of bootloader..
Sorry for my bad english.
Click to expand...
Click to collapse
Have you made sure you are on the correct region?

pizzaboy192 said:
I've found that all current versions of TWRP (R20, R22, Treble-Test) do not back up the OEM partition properly. I haven't tried all the builds so far, but all the ones I've tried mount OEM as R\W which breaks OTA, even after a restore via TWRP. (The R22 seems to touch it no matter what on booting TWRP so you'll need to reflash it via Fastboot from a stock image file in order to take OTAs, or use R20 which didn't touch it unless you tried to restore a backup)
Click to expand...
Click to collapse
I think it would be useful to have a procedure to check the status of the OEM partition. And the precedure to set the correct permissions. Can you add it to the 1st post?
pizzaboy192 said:
5: Run these commands:
...
Code:
fastboot oem fbmodeset
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fbmodeclear
fastboot reboot
Click to expand...
Click to collapse
To be able to get OTAs, if the only problem is the state of OEM partition (on an otherwise stock system), I think we can just flash the OEM partition on fastboot and have a proper system to receive OTAs. Am I right? This would be much simpler than downloading a 1.7 GB file and flashing an entire system.

Don DD said:
I think it would be useful to have a procedure to check the status of the OEM partition. And the precedure to set the correct permissions. Can you add it to the 1st post?
Click to expand...
Click to collapse
I'm not sure how to check besides running the OTA. If it errors out almost immediately after starting then you can view the log in stock recovery and see if it errors on the OTA partition. It's a rather obvious warning at the end of the log.
To be able to get OTAs, if the only problem is the state of OEM partition (on an otherwise stock system), I think we can just flash the OEM partition on fastboot and have a proper system to receive OTAs. Am I right? This would be much simpler than downloading a 1.7 GB file and flashing an entire system.
Click to expand...
Click to collapse
If you're running completely stock, not rooted, etc, then you can just go and flash OTAs. If you've rooted, you can probably just flash recovery, boot, and OEM and it should just take. You don't need to flash System unless you've modified it (If you're using magisk you shouldn't be modifying System)

Very nice tutorial my friend. I have qustion tho... which RETXX works for my phone?
Here's my entire log from adb
Code:
C:\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C2.07
(bootloader) product: sanders
(bootloader) board: sanders
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX1BMB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 3GB SAMSUNG LP3 DIE=6Gb M5=01 M6=05 M7=00 M8=7B
(bootloader) cpu: MSM8953
(bootloader) cid: 0x0032
(bootloader) channelid: 0x1c
(bootloader) uid: 0465D74300000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) meid:
(bootloader) date: 11-10-2017
(bootloader) sku: XT1800
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Jan 27 12:42:19 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/sanders_n/sanders_n:7.1.1
(bootloader) ro.build.fingerprint[1]: /NPS26.116-61/74:user/release-keys
(bootloader) poweroffalarm: 1
(bootloader) ro.build.version.full[0]: Blur_Version.26.231.74.sanders.re
(bootloader) ro.build.version.full[1]: tail.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-03800-89xx.0
(bootloader) version-baseband: M8953_27.36.07.41e SANDERS_LATAM_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-gb124d12-0002
(bootloader) kernel.version[1]: 1-gf059fc9 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.9 20150123 (prerelease) (GCC) ) #
(bootloader) kernel.version[3]: 1 SMP PREEMPT Wed Dec 6 20:34:57 CST 201
(bootloader) kernel.version[4]: 7
(bootloader) sbl1.git: git=MBM-NG-VC2.07-0-gb564bed
(bootloader) rpm.git: git=MBM-NG-VC2.06-0-g5578f74
(bootloader) tz.git: git=MBM-NG-VC2.06-0-g82f94af-dirty
(bootloader) devcfg.git: git=MBM-NG-VC2.06-0-g82f94af-dirty
(bootloader) keymaster.git: git=MBM-NG-VC2.06-0-g82f94af-dirty
(bootloader) cmnlib.git: git=MBM-NG-VC2.06-0-g82f94af-dirty
(bootloader) cmnlib64.git: git=MBM-NG-VC2.06-0-g82f94af-dirty
(bootloader) prov.git: git=MBM-NG-VC2.06-0-g82f94af-dirty
(bootloader) aboot.git: git=MBM-NG-VC2.07-0-g37f20e1
(bootloader) qe: qe 1/1
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retcl
all: listed above
Finished. Total time: 0.148s

pizzaboy192 said:
Have you made sure you are on the correct region?
Click to expand...
Click to collapse
Yes. XT1805. This is the 2nd time i flash back to 7.1. lately im on soaktest and go back to april security, and upgrade to june security , then i go back to april again coz i want back to soaktest.. and no luck to upgrade again.

hi, I'm on RETUS, but I have NPSS26.116-45-17 instead of NPSS25.116-48-18, and I have the patch of June 1 2018, will I have to upgrade or is the same?

jeffrey017 said:
Yes. XT1805. This is the 2nd time i flash back to 7.1. lately im on soaktest and go back to april security, and upgrade to june security , then i go back to april again coz i want back to soaktest.. and no luck to upgrade again.
Click to expand...
Click to collapse
Was soak test sent to you from Motorola?
Try the Motorola offline tool linked above. Use the manual settings instead of the auto ones. It may get you the OTA to sideload.

SandorG said:
hi, I'm on RETUS, but I have NPSS26.116-45-17 instead of NPSS25.116-48-18, and I have the patch of June 1 2018, will I have to upgrade or is the same?
Click to expand...
Click to collapse
June 1 2018 is latest. I'll see if I can get that version of the firmware though.

BlueDragonHans said:
Very nice tutorial my friend. I have qustion tho... which RETXX works for my phone?
Here's my entire log from adb
Code:
C:\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C2.07
(bootloader) product: sanders
(bootloader) board: sanders
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX1BMB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 3GB SAMSUNG LP3 DIE=6Gb M5=01 M6=05 M7=00 M8=7B
(bootloader) cpu: MSM8953
(bootloader) cid: 0x0032
(bootloader) channelid: 0x1c
(bootloader) uid: 0465D74300000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) meid:
(bootloader) date: 11-10-2017
(bootloader) sku: XT1800
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Jan 27 12:42:19 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/sanders_n/sanders_n:7.1.1
(bootloader) ro.build.fingerprint[1]: /NPS26.116-61/74:user/release-keys
(bootloader) poweroffalarm: 1
(bootloader) ro.build.version.full[0]: Blur_Version.26.231.74.sanders.re
(bootloader) ro.build.version.full[1]: tail.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-03800-89xx.0
(bootloader) version-baseband: M8953_27.36.07.41e SANDERS_LATAM_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-gb124d12-0002
(bootloader) kernel.version[1]: 1-gf059fc9 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.9 20150123 (prerelease) (GCC) ) #
(bootloader) kernel.version[3]: 1 SMP PREEMPT Wed Dec 6 20:34:57 CST 201
(bootloader) kernel.version[4]: 7
(bootloader) sbl1.git: git=MBM-NG-VC2.07-0-gb564bed
(bootloader) rpm.git: git=MBM-NG-VC2.06-0-g5578f74
(bootloader) tz.git: git=MBM-NG-VC2.06-0-g82f94af-dirty
(bootloader) devcfg.git: git=MBM-NG-VC2.06-0-g82f94af-dirty
(bootloader) keymaster.git: git=MBM-NG-VC2.06-0-g82f94af-dirty
(bootloader) cmnlib.git: git=MBM-NG-VC2.06-0-g82f94af-dirty
(bootloader) cmnlib64.git: git=MBM-NG-VC2.06-0-g82f94af-dirty
(bootloader) prov.git: git=MBM-NG-VC2.06-0-g82f94af-dirty
(bootloader) aboot.git: git=MBM-NG-VC2.07-0-g37f20e1
(bootloader) qe: qe 1/1
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retcl
all: listed above
Finished. Total time: 0.148s
Click to expand...
Click to collapse
your ro.carrier: says RETCL which is one I haven't seen yet (I also haven't come across an XT1800 before). The Internet says it should be a Latin America variant but I am not 100% certain if the firmware file for RETLA would flash on your device. If you are already running stock, I would not suggest flashing it. I'll see if I can find more information for you on this model to help make sure we can get you the correct firmware.

BlueDragonHans said:
Very nice tutorial my friend. I have qustion tho... which RETXX works for my phone?
Here's my entire log from adb
Code:
sku: XT1800
ro.build.fingerprint[0]: motorola/sanders_n/sanders_n:7.1.1
ro.build.fingerprint[1]: /NPS26.116-61/74:user/release-keys
ro.build.version.full[0]: Blur_Version.26.231.74.sanders.re
ro.build.version.full[1]: tail.en.US
ro.build.version.qcom: LA.UM.5.6.r1-03800-89xx.0
version-baseband: M8953_27.36.07.41e SANDERS_LATAM_CUST
kernel.version[0]: Linux version 3.18.31-perf-gb124d12-0002
kernel.version[1]: 1-gf059fc9 ([email protected]) (gcc ver
kernel.version[2]: sion 4.9 20150123 (prerelease) (GCC) ) #
kernel.version[3]: 1 SMP PREEMPT Wed Dec 6 20:34:57 CST 201
kernel.version[4]: 7
frp-state: protected (77)
ro.carrier: retcl
Click to expand...
Click to collapse
There is some discussion here about Latin America XT1800 model:
https://forum.xda-developers.com/moto-g5s-plus/help/install-security-patch-updates-manually-t3800734

Don DD said:
There is some discussion here about Latin America XT1800 model:
https://forum.xda-developers.com/moto-g5s-plus/help/install-security-patch-updates-manually-t3800734
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=76834762&postcount=20 This guys is running a latin American device and has a 116-26 firmware which is in the RETEU folder. Very interesting.

pizzaboy192 said:
https://forum.xda-developers.com/showpost.php?p=76834762&postcount=20 This guys is running a latin American device and has a 116-26 firmware which is in the RETEU folder. Very interesting.
Click to expand...
Click to collapse
That person doesn't say running a Latin America device or his model number or his software channel. He only says "I'm from Latin America".
Most probably has a european model and is thinking the OTA updates are received depending on the region you use your phone. Just a guess.

Don DD said:
That person doesn't say running a Latin America device or his model number or his software channel. He only says "I'm from Latin America".
Most probably has a european model and is thinking the OTA updates are received depending on the region you use your phone. Just a guess.
Click to expand...
Click to collapse
Valid point. I would still suggest the retbr firmware, as it would fit retla regions

Hi pizzaboy192 and Don DD. Thanks for the fast answers.
I already installed some roms on my cellphone and of course I wanted to go back to stock. Actually idk if I flashed the correct file the last week. It was
Code:
SANDERS_NPS26.116-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Which seems to run ok on my cellphone, but I'm not sure if is the correct stock rom.
Just in case, I have a XT1800 model and I'm from Latin America (Chile)
Oh, and just in case, I already tried RETBR... don't do it, doesn't works.

BlueDragonHans said:
Hi pizzaboy192 and Don DD. Thanks for the fast answers.
I already installed some roms on my cellphone and of course I wanted to go back to stock. Actually idk if I flashed the correct file the last week. It was
Which seems to run ok on my cellphone, but I'm not sure if is the correct stock rom.
Just in case, I have a XT1800 model and I'm from Latin America (Chile)
Oh, and just in case, I already tried RETBR... don't do it, doesn't works.
Click to expand...
Click to collapse
You've installed the India variant. I'll see if I can find links to RETLA since I know I've seen them in the past. They may not be June 1st but at least newer and should allow OTA

Firstly, this is a great tutorial. No rubbish, no jabbering on, just the pure meat.
Can you link the retGB firmware for June 1? I want to be able to upgrade to Oreo by the time it comes out, and I have some other issues I need to fix.

lankthedank said:
Firstly, this is a great tutorial. No rubbish, no jabbering on, just the pure meat.
Can you link the retGB firmware for June 1? I want to be able to upgrade to Oreo by the time it comes out, and I have some other issues I need to fix.
Click to expand...
Click to collapse
I'll see what I can find. Motorola kinda sucks about getting the latest firmware but I'm trying to build a list of all firmware variants even if they're not june 1 that we can then OTA to latest.

pizzaboy192 said:
You've installed the India variant. I'll see if I can find links to RETLA since I know I've seen them in the past. They may not be June 1st but at least newer and should allow OTA
Click to expand...
Click to collapse
Once again, many thanks pizzaboy192... I'm trying to find the rom for the RETLA channel too, but Google doesn't help me (only shows stuff for the G5 Plus, not the G5S Plus lol)
If I find something, I will share it
Thanks again!

Moto E5 bootloader relock

anyone know how to relock the bootloader and start from stock via adb commands (without the moto assistant software)?
EDIT:
ok this works for me:
download the stock img files for YOUR PHONE VERSION (XT1924-1, XT1924-4, XT1921-6 or whatever you have...) !!!
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 logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
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 oem oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot erase DDR
fastboot flash fsg fsg.mbn
fastboot oem fb_mode_clear
fastboot oem lock XXXXXXXXXXXXXXXXXX (XXX... is your unlock key which you used to unlock the bootloader)
fastboot oem lock XXXXXXXXXXXXXXXXXX (XXX... is your unlock key which you used to unlock the bootloader)
fastboot flash boot boot.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 oem oem.img
fastboot flash vendor vendor.img
fastboot flash logo logo.bin
fastboot oem lock XXXXXXXXXXXXXXXXXX (XXX... is your unlock key which you used to unlock the bootloader)

For the MetroPCS Variant (1924-7), I keep getting the following error when flashing GPT.bin
"target reported max download size of 535822336 bytes
sending 'partition' (45 KB)...
OKAY [ 0.004s]
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.067s"
Any help on this? No amount of Google searching has gotten me far.

DragonfireEX402 said:
For the MetroPCS Variant (1924-7), I keep getting the following error when flashing GPT.bin
"target reported max download size of 535822336 bytes
sending 'partition' (45 KB)...
OKAY [ 0.004s]
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.067s"
Any help on this? No amount of Google searching has gotten me far.
Click to expand...
Click to collapse
Are you trying to relock the bootloader?
Sent from my PH-1 using Tapatalk

sd_shadow said:
Are you trying to relock the bootloader?
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
Yes I am. Thanks for the response.

DragonfireEX402 said:
Yes I am. Thanks so much for responding here. I tried to get help on Discord, but I was subject to personal attacks and a mod banned me for defending myself.
Click to expand...
Click to collapse
I would skip the gpt.bin and skip the relock step
Run the other commands, reboot if flash seems to work, retry the process from the beginning.
If not may need to find a different firmware version or the copy you have may be corrupt.
Sent from my PH-1 using Tapatalk

sd_shadow said:
I would skip the gpt.bin and skip the relock step
Run the other commands, reboot if flash seems to work, retry the process from the beginning.
If not may need to find a different firmware version or the copy you have may be corrupt.
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
Thanks again, man. Will try the T-Mobile Roms.
For the record, this is where I got it from. https://mirrors.lolinet.com/firmware/moto/hannah/official/Metropcs/
Tried both links listed and neither of these worked.

DragonfireEX402 said:
Thanks again, man. Will try the T-Mobile Roms.
For the record, this is where I got it from. https://mirrors.lolinet.com/firmwar...ubsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Of course Motorola devices are notoriously bad at relocking bootloaders.
I recommend leaving the bootloader unlocked
Sent from my PH-1 using Tapatalk

sd_shadow said:
Of course Motorola devices are notoriously bad at relocking bootloaders.
I recommend leaving the bootloader unlocked
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
That would be more convenient if nothing else.
EDIT: Bootloader relocked now. All good.

Some duplicated commands near the bottom of the list. Are you saying that all those commands need to be issued and in that order just to re-lock the bootloader?

THANKS
It works. Thanks man, after a few months of search i finally found something that works. :good: :good:

I can't do it
C:\Users\\Desktop\platform-tools>fastboot oem lock
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.005s]
finished. total time: 0.006s
in the developer menu cannot be activate
Could someone please help me?

caruro said:
I can't do it
C:\Users\\Desktop\platform-tools>fastboot oem lock
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.005s]
finished. total time: 0.006s
in the developer menu cannot be activate
Could someone please help me?
Click to expand...
Click to collapse
Firmware is stock, not rooted?
Sent from my Pixel XL using Tapatalk

caruro said:
I can't do it
C:\Users\\Desktop\platform-tools>fastboot oem lock
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.005s]
finished. total time: 0.006s
in the developer menu cannot be activate
Could someone please help me?
Click to expand...
Click to collapse
It's likely your phone cannot be unlocked if the unlock bootloader is grayed out. You can go to Motorola's site and enter the code from the phone and they will either give you an unlock code or tell you it's ineligible to be unlocked. Here's how to do it:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a

sd_shadow said:
Firmware is stock, not rooted?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Thx, phone have stock rom and not root, but it is a E5 plus hannah maybe that is the wrong model.
that's why it doesn't work

bouuman said:
anyone know how to relock the bootloader and start from stock via adb commands (without the moto assistant software)?
EDIT:
ok this works for me:
download the stock img files for YOUR PHONE VERSION (XT1924-1, XT1924-4, XT1921-6 or whatever you have...) !!!
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 logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
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 oem oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot erase DDR
fastboot flash fsg fsg.mbn
fastboot oem fb_mode_clear
fastboot oem lock XXXXXXXXXXXXXXXXXX (XXX... is your unlock key which you used to unlock the bootloader)
fastboot oem lock XXXXXXXXXXXXXXXXXX (XXX... is your unlock key which you used to unlock the bootloader)
fastboot flash boot boot.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 oem oem.img
fastboot flash vendor vendor.img
fastboot flash logo logo.bin
fastboot oem lock XXXXXXXXXXXXXXXXXX (XXX... is your unlock key which you used to unlock the bootloader)
Click to expand...
Click to collapse
love you amasing