Database Develop

[Q] HTC One Goole Edition Stuck in Bootloop after 4.4 update. Help please!

Hello-
Here is the fast version:
HTC One GPE with stock JB rom and clockwork mod recovery.
Last night I flashed the recovery to a stock version I found on the boards here. This morning the most recent JB update was ready for installation on the phone. A while after that KitKat was ready and I installed. As soon as I did, the phone entered a boot loop and will not stay on. I've cleared the cache and factory reset with no luck. A kind individual on another thread attempted to help resolve the issue but no such luck.
I tried reinstalling 4.4 (having to relock my bootloader was the only way I could successfully attempt reloading, but it did not work. S-off is ON.
Now, I cannot enter a custom recovery (nor a recovery of any kind at this moment). Any time I select recovery it just reboots the phone.
Here are previous errors I received while attempting fastboot flash:
bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
FAILED (remote: 24 parsing android-info fail)
Here is my fastboot getvar all:
c:\And>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4241mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
I appreciate any help you may be able to offer. I've never had this much trouble with a phone before (somewhat of a novice, but this is beyond me).
Thank you!!!

unlock the bootloader again and install a custom recovery
then install the zip from here using adb sideload: http://forum.xda-developers.com/showthread.php?t=2341395

Right, so your bootloader is locked or unlocked? If locked, are you able to unlock it?

SaHiLzZ said:
Right, so your bootloader is locked or unlocked? If locked, are you able to unlock it?
Click to expand...
Click to collapse
I use the command "fastboot oem lock" and "fastboot oem unlock" to lock and unlock the device (since it's google play edition), unless that is for unlocking something else besides the bootloader.
I cannot open the recovery so I don't know what is on there. I've loaded TWRP with fastboot but every time I select recovery from the menu on the phone it reboots the phone.
Here is what I get when I search for the phone. I assume the adb is not seeing it since I have not set up the phone for that option?
c:\And>adb devices
List of devices attached
c:\And>fastboot devices
HT36JW912382 fastboot

Can you download either CWM or TWRP and try the following from bootloader:
fastboot boot nameofrecovery.img
For example: If you get http://flyhalf205.com/recoveries/recovery-clockwork-touch-6.0.4.5-m7ul.img
then fastboot boot recovery-clockwork-touch-6.0.4.5-m7ul.img in fastboot mode
Does the phone reboot into recovery now?

c:\And>fastboot boot openrecovery-twrp-2.6.3.3-m7.img
downloading 'boot.img'...
OKAY [ 1.202s]
booting...
OKAY [ 0.001s]
This just froze the phone.
It will NOT boot into recovery. Just turns on and shows "Google"
QUOTE=SaHiLzZ;47949555]Can you download either CWM or TWRP and try the following from bootloader:
fastboot boot nameofrecovery.img
For example: If you get http://flyhalf205.com/recoveries/recovery-clockwork-touch-6.0.4.5-m7ul.img
then fastboot boot recovery-clockwork-touch-6.0.4.5-m7ul.img in fastboot mode
Does the phone reboot into recovery now?[/QUOTE]

Try the recovery linked and twrp 2.6.3.0?

fastboot erase cache

damon7620 said:
fastboot erase cache
Click to expand...
Click to collapse
SaHiLzZ said:
Try the recovery linked and twrp 2.6.3.0?
Click to expand...
Click to collapse
I have cleared the cache before and after loading the custom recovery. and I loaded the CWR recovery. Still will not load into recovery. Just turns off and boots to Google.

i was able to successfully re-load the stock recovery. Any suggestions from this point?

How? What recovery did you use?
Go to bootloader and a do a factory reset from bootloader, it should boot into stock recovery and wipe , (should not just get kicked out right away)
What's the result after doing this.?

SaHiLzZ said:
How? What recovery did you use?
Go to bootloader and a do a factory reset from bootloader, it should boot into stock recovery and wipe , (should not just get kicked out right away)
What's the result after doing this.?
Click to expand...
Click to collapse
I used one I found somewhere in this thread. http://forum.xda-developers.com/showthread.php?t=2358781&highlight=recovery
I cannot recall the exact one. It is the same one I installed last night before this morning's update.
I did the wipe and loaded into bootloader. Rebooted the phone and is now in a boot loop.

Hi @The_Doctor_Who here's what I would recommend:
- fastboot oem unlock (if not already in the unlocked state)
- download the latest official ClockworkMod touch recovery for m7ul directly from here: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.4.3-m7ul.img
- fastboot boot recovery-clockwork-touch-6.0.4.3-m7ul.img
Note the use of 'boot' instead of 'flash' for the last command... let's narrow this down and see if you can just boot a well-known/official recovery for this model without flashing anything. Sorry if these steps seem repetitive at this point, but it's a little hard to know what all has been done.

goldenratio said:
Hi @The_Doctor_Who here's what I would recommend:
- fastboot oem unlock (if not already in the unlocked state)
- download the latest official ClockworkMod touch recovery for m7ul directly from here: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.4.3-m7ul.img
- fastboot boot recovery-clockwork-touch-6.0.4.3-m7ul.img
Note the use of 'boot' instead of 'flash' for the last command... let's narrow this down and see if you can just boot a well-known/official recovery for this model without flashing anything. Sorry if these steps seem repetitive at this point, but it's a little hard to know what all has been done.
Click to expand...
Click to collapse
Hey! Thank!
I understand re: not knowing. I've tried using that recovery and cannot get into it. I also tried the fastboot boot and it froze the phone (someone motioned HTC removed the ability to use 'boot' with the hboot 1.54). I tried leting the phone sit in the frozen state but it would not do anything.

The_Doctor_Who said:
I've tried using that recovery and cannot get into it. I also tried the fastboot boot and it froze the phone.
Click to expand...
Click to collapse
I see. Do I understand the the sequence of events correctly:
- you flashed a stock JB ROM
- then flashed the stock recovery (which file exactly? was it for m7ul?)
- the phone booted okay at this point and prompted you for 2 over-the-air system updates:
= an update for JB
= an update to KitKat
- things broke at this point?
The_Doctor_Who said:
someone motioned HTC removed the ability to use 'boot' with the hboot 1.54.
Click to expand...
Click to collapse
Do you have a link for that thread handy? I wonder if it's trivial or not to downgrade the radio (HBOOT)... I haven't tried before.

goldenratio said:
I see. Do I understand the the sequence of events correctly:
- you flashed a stock JB ROM
- then flashed the stock recovery (which file exactly? was it for m7ul?)
I will have to find the file. I believe it was. It was indicated that the stock recovery was from the GPE One.
- the phone booted okay at this point and prompted you for 2 over-the-air system updates:
= an update for JB
= an update to KitKat
- things broke at this point?
The update for JB was fine. I was checking twitter, facebook, etc. Then the KitKat update came in. I selected download and install and that is where the problem started.
Do you have a link for that thread handy? I wonder if it's trivial or not to downgrade the radio (HBOOT)... I haven't tried before.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=47972147&postcount=16
From what I have seen downgrading is not an option, but I could be wrong.

@The_Doctor_Who thanks for the link. It doesn't specifically say you can't use 'fastboot boot' on the GPE version of HBOOT. I'm pretty sure you can (assuming things are working otherwise). At least, I had a version of the 1.54 HBOOT on m7ul which didn't seem to have this restriction... I don't know the exact version number unfortunately.
That aside, it does seem that the recovery partition may be corrupted or in a bad state somehow. I'm going to reply on the other thread since those guys seem to have some good info and have been super helpful. I have a couple of ideas I'll post there.

At this point what I would recommend is to use the factory images for it and attempt to restore it to full stock before trying to go any further.

MODS PLease delete

MODS PLEASE DELETE , cant find solution , thanks anyway
Im a dare to start my own thread to see if i can solve my problem, anyway, i own a xt1063 in wich i unlocked the bootloader in order to install lollipop and root, i have done this in the past with 3 xt1064's with no problem, however im facing a weird problem this time. So after i installed lollipop rom RETUGLB_XT1063_5.0.2_LXB22.46-28_cid9_CFC.xml via fasboot,everything went smooth as always, the phone boots up but after the world and blue m animation the phone goes into a blank (or black) screen and stays there and it goes no further than that, ive waited 20 plus minutes and nothing happens,i know the phone is on because i can see the screen its a bit bright but black, so i went to the original recovery and did a factory reset wich went nice, reboot and same result, so i instaled twrp via the Moto-G-2014-ToolKit-stable i found here, and booted the twrp recovery, wiped davilk cache,cache and after rebooting i got the same result. One thing i notice is, if i want to erase cache via stock recovery, the phone reboots inmediatly as if something went wrong, i twrp i get an error, trying to install the titan rom [ROM][5.0.2][titan][XT1063/64]The Titan Prime ROM[FEB 1](Version 1.1.2 RC) gives me a bunch of errors and nothing happens. Other thing i notice is that if i boot in twrp and mount the usb storage, i get terrible transfer rate speed, also if i copy something,lets say a rom, i can install such rom but once i restart and boot into twrp and mount the usb again, is like nothing was transfered, thres no rom in there, like if it wipes it self . Dont know what ealse to do, wonder if the cache partition its corrupted and dosnt let the phone fully start. Thanks for any help provided, and pardon my bad grammar, english its my second lenguage...
edited to add more details:
Everytime i try to lock the bootloader i get diferent mesages, but it nevers locks the bootloader.
or if i run the boot logo fix, the tool succesfully does the job as i can tell in the command window, but when i reboot i still get the warning logo as if nothing happened.
Click to expand...
Click to collapse

anyone please? im running out of ideas, thanks.

update 2 just in case someone wants to help, i instaled kk 4.4.4 with titan flasher, then instaled twrp, tried to instal any rom in twrp gets stuck in format system partition....

Have you tried to flash any stock firmware with fastboot?

dpdp73 said:
Have you tried to flash any stock firmware with fastboot?
Click to expand...
Click to collapse
Yes, kk 4.4.4 or lollipop 5.0.2 , no go , both gave the same result.

I wonder if theres a way to install a rom,at the same time wipe all the estructure inside the phone, can that be achieved via adb perhaps? as fastboot seems a bit limited. anyway heres a video that shows how the phone boots to a blank screen on a clean fasboot instaled 5.0.2 stock rom www.youtube.com/watch?v=D8CgqNOp-_g
and this is what happens if i try to clean cache with recovery
www.youtube.com/watch?v=oBivRORNH1I

Try things like "fastboot erase cache", "fastboot erase data(/system etc.)".
But it doesn't look good.

dpdp73 said:
Try things like "fastboot erase cache", "fastboot erase data(/system etc.)".
But it doesn't look good.
Click to expand...
Click to collapse
tried too,was a no go.... dont no what ealse to try, i pretty much done everything

another update while someone steps up and helps.
My phone looks like its write protected, but i can install any recovery i want and boot it. so if i install twrp i can boot to it, if i mount the usb system i can copy files to it, but as soon as i reboot, the files get deleted by magic... so next thing i tried, install stock kk 4 or lollipop via stock recover and sideload adb, i get a fingerprint error message, package expects build fingerprint of motorola/titan_retuglb/titan_umts:4.4.4/KXB/21.85-17/14:user/release , but after that i flashed KK rom via fastboot, all goes well , so i reboot and start recovery and tried to install lollipop via adb side load and i get a fingerprint message again, and dont mater how many roms i flash via fasboot and they look like they installed ok, if i restart stock recovery and try to update with any rom , i get this message,
package expects build fingerprint of motorola/titan_retuglb/titan_umts:4.4.4/KXB/21.85-17/14:user/release-keys or motorola/titan_retuglb/titan_umts:5.0/LXB22.39-6/6:user/release-keys; this device has motorola/titan_retuglb/titan_umts:4.4.4/KXB23/25:u
instalation aborted.
even after flashing lollipop, system says device has KK ,wich lead me to think its been wirte protected.
will keep looking and hope for some smart help, thanks.

please help anyone
Code:
C:\mfastboot-v2>fastboot getvar all > command.txt
(bootloader) version: 0.5
(bootloader) version-bootloader: 4807(*)
(bootloader) product: titan
(bootloader) secure: yes
(bootloader) hwrev: 0x8400
(bootloader) radio: 0x1
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Elpida S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: ZX1D3239LM
(bootloader) cid: 0x0009
(bootloader) channelid: 0x8d
(bootloader) uid: D59CBB060F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 359297052588158
(bootloader) meid:
(bootloader) date: 10-23-2014
(bootloader) sku: XT1063
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Dec 2 3:44:40 UTC 2014"
(bootloader) ro.build.fingerprint[0]: motorola/titan_retuglb/titan_umts:
(bootloader) ro.build.fingerprint[1]: 4.4.4/KXB21.85-23/21:user/release-
(bootloader) ro.build.fingerprint[2]: keys
(bootloader) ro.build.version.full[0]: Blur_Version.21.11.23.titan_retug
(bootloader) ro.build.version.full[1]: lb.retuglb.en.US
(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-g668a77b ([email protected]
(bootloader) kernel.version[1]: ilclbld53) (gcc version 4.7 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Tue Aug 26 20:21:50 CDT 2014
(bootloader) sdi.git: git=MBM-NG-V48.07-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V48.07-0-g683cb0c
(bootloader) rpm.git: git=MBM-NG-V48.07-0-g71b1aae-dirty
(bootloader) tz.git: git=MBM-NG-V48.07-0-ga27c415
(bootloader) aboot.git: git=MBM-NG-V48.07-0-ge875a20
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 0/0
(bootloader) productid: ZX1D3239LM
(bootloader) sutinfo:
all: listed above
finished. total time: 0.088s

I have the exact same problem

xGiorgos said:
I have the exact same problem
Click to expand...
Click to collapse
come here and fight with us http://forum.xda-developers.com/moto-g-2014/help/phone-write-protected-freezed-t3030812

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

HTC One Mini 2 constantly rebooting on red triangle?

hi, this phone was rooted and still says unlocked, I have done everything from factory reset, clearing cache, wiping, recovery. nothing works it just simply restarts on to the red triangle.. please can you help me get this phone back up and running I don't know what else to do

A red triangle means no OS loaded in device, make sure you have 100% battery before doing anything, if unsure how much battery exists, leave device on charge for 2 hours.
If it keeps on rebooting it is also possible to be stuck in a bootloop, this wjll need reflashing boot but this cannot be determined until an OS if flashed.
As its unlocked you can flash Stock Nandroid or CM13 or CM14 (LOS)
To find a proper stock Nandrood you need to post getvarall info here without the IMEI

ive never flashed a android device before how do i do that?
i have SDK as i have the full android studios software.
i downloaded adb as well.
but that is as far as ive got

nickpowell said:
ive never flashed a android device before how do i do that?
i have SDK as i have the full android studios software.
i downloaded adb as well.
but that is as far as ive got
Click to expand...
Click to collapse
Turn off device, keep vol down key pressed and prews power key, you will enter bootloader, then select fastboot via vol keys and press power key to enter fastboot.
Now connect device to PC and follow this to getvarall.
http://droider.eu/2013/10/28/using-...to-get-more-information-about-your-htc-phone/
Paste your result here WITHOUT IMEI.
What recovery do you have stock or TWRP ?

no recovery option it just reboots non stop, but before it did any of this it was twrp

nickpowell said:
no recovery option it just reboots non stop, but before it did any of this it was twrp
Click to expand...
Click to collapse
That means its a bootloop, I will still need device getvarall info to provide the appropriate file, however considering your scenario, can i know where did you buy the device from and is it network locked ?
This is an international device boot file, you can try and flash this file and let me know, chances are with TWRP boot flash will fail as the boot file is atock and to flash it all device must be stock, but you have to try to know for sure.
REMEMBER AGAIN IF THE DEVICE IS LOW ON CHARGE IT COULD DIE MIDWAY, IF IT DIES MIDWAY THE DEVICE WILL BE IN A PERMANENT BRICKED STATE.

(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.101.1102.17.0506
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.18.61.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH4CAWR00634
(bootloader) meid: 00000000000000
(bootloader) product: mem_ul
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0P8B20000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: be7179e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
how do i flash it though?

i just flashed a recovery not the international one but another and it still gos to the red triangle, no info,nomessages, nothing, just gos their.

and same for that recovery it still does not let me go into recovery

ive managed to get TWRP recovery back the screen but nothing to install, what do i need now ?

nickpowell said:
ive managed to get TWRP recovery back the screen but nothing to install, what do i need now ?
Click to expand...
Click to collapse
Now I see that you have an Orange device, no nandroid stock is available, you can choose to install CM13 or CM14 links given earlier. CM13 is old and has many bugs fixed, CM14 is new, while I dont have any issues with CM14, there are some reported issues in its thread, make sure to choose which you like after reading through the threads.
What you will need to do is download the rom and place it in SDcard, then enter recovery and choose install and wait till it finishes, reboot and you are good to go, after install make sure to clear cache and dalvik, if install fails then you will need to upgrade twrp to latest version for one mini 2, ver 3.0.2.
Also note that first boot takes quite some time, around 5 mins or so.
YOUR IMEI AND SERIAL IS VISIBLE IN YOUR REPLY, REMOVE IT.
If ou want to go full stock, you can flash this Orange UK ROM or Orange FRANCE rom.
I dont know which country your device from is so I have provided both but I believe your is a UK device thus first try that, cidnum ending 001 are mostly UK.
To flash stock you will have to flash stock recovery snd then install using method explained here
Let me know how it went.
Thats about it.

i have tried the cm13 but i get an error when trying to flash it, im doing the adb sideload way. so imm going to try cm14 los one

alli get is error executing updater binary in zip

cant seem to find the lkatest ersion for twrp/img their just all apps or apk

i tried the stock way, but as soon as i flashed the original rom recovery it said the file size was to big so im really stuck nnow

ok somehow i used a rom utility which failed but it somehow reset the phone back to the cracked version...how do i now get it to the stock version?

nickpowell said:
ok somehow i used a rom utility which failed but it somehow reset the phone back to the cracked version...how do i now get it to the stock version?
Click to expand...
Click to collapse
Latest TWRP version for CM14 https://forum.xda-developers.com/on...recovery-twrp-3-0-2-0-unofficial-htc-t3555343
Stock Recovery, you can try but again this is for International Devices : https://www.androidfilehost.com/?fid=24651430732234876
Method to flash :
PROCESS
Enter bootloader and then enter fastboot, connect phone to PC and type the command in adb ( place recovery file in adb folder) :
Code:
fastboot flash recovery <file-name>.img
fastboot erase cache
To flash stock rom you will need stock recovery and relock bootloader, the stock recovery which is unfortunately unavailable, I believe nobody has posted stock recovery for Orange so you will have to follow method links provided for CM14 through TWRP.
So now you flash twrp, place cm14 rom in sdcard, enter recovery from bootloader, choose install, locate cm14 downloaded file and swipe to flash.
Cracked version ?

i have the cracked version i just want the originally can i not get it back to stock through restore?

nickpowell said:
i have the cracked version i just want the originally can i not get it back to stock through restore?
Click to expand...
Click to collapse
Can you explain what do you mean cracked version ?
Leave the device on charge for 2 hours and I mean electrical charge and NOT USB to PC charge.
I already provided you everything, are you following instructions as supplied ?
Have you updated TWRP to version 3.0.2 ?
On which file flash are you receiving updater binary error, CM13 or CM14 ?
Have tried to flash stock recovery provided ?
You are not providing enough information for me to understand.

TryllZ said:
Can you explain what do you mean cracked version ?
Leave the device on charge for 2 hours and I mean electrical charge and NOT USB to PC charge.
I already provided you everything, are you following instructions as supplied ?
Have you updated TWRP to version 3.0.2 ?
On which file flash are you receiving updater binary error, CM13 or CM14 ?
Have tried to flash stock recovery provided?
You are not providing enough information for me to understand.
Click to expand...
Click to collapse
ok at the moment my phone is running a rooted version, however, im not too sure which one, it may have cm13.
the phone has twrp - not 3.0.2
I tried earlier to get everything back to stock as I have the stock file for the device and i have a boot file too.
but when I tried flashing the original file it just said the file size was too large.
so I was wondering since i have the original stock file on my pc is there any way to revert the htc mini 2 back to original OEM through twrp or some other way like adb sideload?

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!